PDA

View Full Version : [kubuntu] Info and help for HP TX2500 Series



Pages : [1] 2 3

isachan
July 1st, 2008, 07:48 AM
I just got my brand-spanking new HP TX2500 CTO this morning, and after several hours of uninstalling the bloatwares, defragging, and partitioning, I finally got to install Kubuntu 8.04.

Immediately I stumbled into the problem of booting from a LiveCD. An hour later I found out why.

By pressing Ctrl+Alt+F1, I could see boot messages. It turns out that as soon as the kernel loads, it detects overtemp, and starts to shut down the machine. The message line reads "Critical temperature (xxC) reached: shutting down".

Funny thing is that this happens even the temp is reasonably low (even around 60).

After a few search on the forums I tried the kernel parameter "acpi=off", and lo and behold, it works !

So I installed Hardy and several other essential applications (Radeon drivers through EnvyNG, etc) and realized there is no sound. No wonder, because ACPI interrupts control the sound chip. Irony is that I wanted to watch some HD video on this machine (surprisingly, the playback is slow) !

However, this parameter is the only thing that's working so far. I also tried noapic, nolapic, noacip, irqpoll, irqfixup, acpi_irq_balance, noirqdebug, but no avail.

I need some serious help here, but my hunch is that I have to wait for BIOS updates from HP for the next several months.

I post this new thread, hoping this one parameter can help some others to get going on Linux with this tablet PC.

Isao

sergiom99
July 1st, 2008, 03:59 PM
please post your detailed laptop specs and the output of lspci.


Thanks.

wabre
July 1st, 2008, 08:47 PM
check this thread, first post. i'm not sure if it works, see the sound section in the first post. it helped me on my tx2120, though not sure if it works on your (me jealous...) puma..

http://georgia.ubuntuforums.org/showthread.php?t=792669


oh, something else..mainly hope: i installed ubuntu 8.10 intrepid ibex alpha 1...sound works out of the box!

isachan
July 2nd, 2008, 06:58 PM
wabre, thanks for the link, but adding that line didn't make any difference, since TX2500 uses different combination of integrated chipset and the same Realtek chip. So, it shows up as "HDA ATI SB". I'll do some search on it to see what I can find.

sergiom99, here is my lspci -v output :

00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 0
Capabilities: [c4] HyperTransport: Slave or Primary Interface
Capabilities: [54] HyperTransport: UnitID Clumping
Capabilities: [40] HyperTransport: Retry Mode
Capabilities: [9c] HyperTransport: #1a
Capabilities: [f8] HyperTransport: #1c

00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: d2200000-d23fffff
Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff
Capabilities: [44] HyperTransport: MSI Mapping
Capabilities: [b0] Subsystem: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)

00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=07, sec-latency=0
I/O behind bridge: 00003000-00004fff
Memory behind bridge: d1200000-d21fffff
Prefetchable memory behind bridge: 00000000d0000000-00000000d0ffffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+) IRQ 0
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [b0] Subsystem: Hewlett-Packard Company Unknown device 30f1
Capabilities: [b8] HyperTransport: MSI Mapping

00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
Memory behind bridge: d1100000-d11fffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+) IRQ 0
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [b0] Subsystem: Hewlett-Packard Company Unknown device 30f1
Capabilities: [b8] HyperTransport: MSI Mapping

00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: b0000000-b00fffff
Prefetchable memory behind bridge: 00000000d1000000-00000000d10fffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+) IRQ 0
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [b0] Subsystem: Hewlett-Packard Company Unknown device 30f1
Capabilities: [b8] HyperTransport: MSI Mapping

00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (prog-if 01 [AHCI 1.0])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
I/O ports at 6038 [size=8]
I/O ports at 604c [size=4]
I/O ports at 6030 [size=8]
I/O ports at 6048 [size=4]
I/O ports at 6010 [size=16]
Memory at d2409000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [60] Power Management version 2
Capabilities: [70] #12 [0010]

00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
Memory at d2408000 (32-bit, non-prefetchable) [size=4K]

00:12.1 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI1 Controller (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
Memory at d2407000 (32-bit, non-prefetchable) [size=4K]

00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 7
Memory at d2409500 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Capabilities: [e4] Debug port

00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
Memory at d2406000 (32-bit, non-prefetchable) [size=4K]

00:13.1 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI1 Controller (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
Memory at d2405000 (32-bit, non-prefetchable) [size=4K]

00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 4
Memory at d2409400 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Capabilities: [e4] Debug port

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: 66MHz, medium devsel
Capabilities: [b0] HyperTransport: MSI Mapping

00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller (prog-if 80 [Master])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 6000 [size=16]
Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/1 Enable-

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, slow devsel, latency 64, IRQ 5
Memory at d2400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2

00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 0

00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=80, subordinate=8f, sec-latency=64
I/O behind bridge: 00001000-00001fff

00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller (prog-if 10 [OHCI])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
Memory at d2404000 (32-bit, non-prefetchable) [size=4K]

00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 11h HyperTransport Configuration (rev 40)
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h Address Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 11h DRAM Controller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 11h Miscellaneous Control
Flags: fast devsel
Capabilities: [f0] #0f [0010]

00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 11h Link Control
Flags: fast devsel

01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Unknown device 30f1
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at c0000000 (32-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=256]
Memory at d2300000 (32-bit, non-prefetchable) [size=64K]
Memory at d2200000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

08:00.0 Network controller: Broadcom Corporation BCM4310 USB Controller (rev 01)
Subsystem: Hewlett-Packard Company Unknown device 137c
Flags: bus master, fast devsel, latency 0, IRQ 7
Memory at d1100000 (64-bit, non-prefetchable)%2

corwinspyre
July 3rd, 2008, 12:48 AM
edit: nevermind

isachan
July 7th, 2008, 05:47 AM
New findings and a few updates :

Web cam works with "Cheese". Install it with "sudo apt-get install cheese" and enjoy. I haven't tried with Skype or Ekiga yet.

If your machine is cool enough, you can boot without "acpi=off" boot option. You only have 3 to 4 minutes though until the machine shuts itself down again, and the keyboard and the touchpad don't work without it.

For the wireless, it seems like we just have to wait until the bugs in "wl" driver will be fixed. According to these threads :

http://ubuntuforums.org/showthread.php?p=5326382#post5326382
http://ubuntuforums.org/showthread.php?t=848622&page=3
the last update has broken the driver. Let's wait and see what happens.

I have been thinking to fix up some DSDT problem with this machine, by following instructions on this thread :
http://ubuntuforums.org/showthread.php?t=623633
but now I just found out I can't even type anything from keyboard.
My hope to get Linux going on this machine is getting slim.

Is anybody else out there have any other ideas to tackle this ?

Isao

isachan
July 7th, 2008, 08:54 AM
Okay, so I verified that the webcam works for Skype and Ekiga.

For Ekiga, just type in a command line :
sudo apt-get install ekiga libpt-1.11.2-plugins-v4l2
After everything is installed, run Ekiga.
Go to Edit Menu -> Preferences -> Under Devices, Video Devices -> Set Video Plugin to V4L2.
Wait a few minutes, and you should be able to see yourself in the video.

For Skype :
Go to this page, and follow the direction :
https://help.ubuntu.com/community/Medibuntu#Adding%20the%20Repositories
Then, do sudo apt-get install skype

That should be it.

As you know, at this point it's meaningless because the sound is not working. Well, someday...

Isao

TomtheWombat
July 10th, 2008, 01:47 PM
You could try "noapic nolapic irqfixup" as suggested in http://ubuntuforums.org/showthread.php?t=837657

That thread also contains a tip for the sound card and a link to instructions for the touch screen.

The webcam is is v4l2 device so it won't work with version 1 v4l programs (like adobe's flash). There is a bridge for v4l2->v4l, but I forgot what it's called.

isachan
July 12th, 2008, 01:45 AM
Thanks, but those kernel options didn't work.

I'm trying to set a higher trip-points with a script from another Ubuntu forum thread. It's still not working.

I don't have sound, but playing back some high def video with MPlayer and fglrx driver with OpenGL direct rendering is so smooth ! Image quality is just great.

Isao

kv11
July 12th, 2008, 11:25 AM
isachan, could you please describe what other problems do you have with tx2500 ? Does touchscreen (and pressure sensitivity) work ? Does it suspend/resume properly ?

isachan
July 13th, 2008, 04:43 AM
So far, I haven't tested those features yet, as I haven't got a screen protector on the screen. I've been researching which one would be the best one.

I haven't tried it either, but I can only see the hibernate option. I believe we really need ACPI to enable suspending.

I'm gonna employ tx2000 tactics to try once I got my screen protector. I'll let you know later.

Isao

AstronomyDomine
July 14th, 2008, 06:12 AM
Well it's nice to see I'm not the only one having troubles. I've figured out that the critical trip point problem lies within the thermal module which is loaded with the initramfs, so for now we have three choices: We can boot with acpi=off, we can compile a custom kernel without the thermal module, or we can recreate our initramfs without the thermal module.

I opted for the third option, and it is working pretty well so far. I still don't have audio, wireless, or touchscreen support, but it runs for hours without problems. I have no idea why I don't have any touchscreen support, but no matter what I try, I can't seem to get it working. Also, the wireless doesn't seem to want to work at all, even with ndiswrapper.

isachan
July 14th, 2008, 07:46 AM
This could be the reason :
http://forum.tabletpcreview.com/showpost.php?p=115568&postcount=2

Also, see the last post, written on 2008-04-25
https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/111460

I'm confused now. Is it the BIOS, or the kernel being the cause ?
Or the combination of both ? Or the new CPU and the chipset (Puma platform) ?

Only once before, I got lucky and had enough time to look the thermal parameters in /proc/acpi/thermal_zone/THRM/ directory. And I remember the trip point was -127C. So that's why I thought it's because of a bug in DSDT. I think I got the sound only for that time.

This morning was very cool at my place and I tried without acpi=off again, and saw the wireless light was blue. But a minute after I got to see the desktop, it shut down. With acpi=off, the light stays red no matter what you do.

So, we just have to be patient and wait for a long time for updates ?
For my TX1000, it took approx. 11 months to be fully usable.

Isao

fbdelivers
July 14th, 2008, 04:10 PM
I am really happy to see this post. I've been trying and trying to get things to work following all of the tx2000 instructions. The wireless issue just about made my wife shoot me as I've been sitting in front of this computer for days now.

Short description - I just purchased the tx2500 and have been following all of the tx2000 instructions to try and get the wireless to work. No luck just like this thread. I too have the acpi=off setting on boot. I put the tablet in a cold place for a couple of hours, enabled acpi, booted and BAM the wireless started working.

I'd be happy to get at least the wireless working and will start working on the acpi setting to see if I can get past that. I've tried getting wacom to work but haven't had any luck.

Thanks for the post!

David

AstronomyDomine
July 14th, 2008, 05:21 PM
I put the tablet in a cold place for a couple of hours, enabled acpi, booted and BAM the wireless started working.


The wireless started working meaning that the light was blue, or that you were actually able to connect to a network?

I don't need to boot with acpi=off since I removed thermal from the initramfs, but I still can't use the wireless. The light is blue, but there is no interface for the device. Even ndiswrapper doesn't seem to work.

fbdelivers
July 14th, 2008, 07:11 PM
The wireless started working meaning that the light was blue, or that you were actually able to connect to a network?

I don't need to boot with acpi=off since I removed thermal from the initramfs, but I still can't use the wireless. The light is blue, but there is no interface for the device. Even ndiswrapper doesn't seem to work.

Good question and maybe I got ahead of myself. I just had the light turn blue which was a good sign. I haven't had it run long enough to try the wireless other then the fact that it did scan and wireless networks were available.

I'll work on removing the thermal from initramfs. Did you do that by just removing that from the hooks directory?

David

AstronomyDomine
July 15th, 2008, 12:15 AM
Here's how I removed the module thermal from my initramfs:



sudo su -
cd /boot
mkdir /tmp/directory.cpio
zcat initrd.img-2.6.24-19-generic > /tmp/directory.cpio/initrd.cpio
cd /tmp/directory.cpio
cpio -idv < initrd.cpio
rm lib/modules/2.6.24-19-generic/kernel/drivers/acpi/thermal.ko
nano conf/modules

Remove the line "thermal" from the file (if this file is blank, something wrong happened, post here), then hit CTRL+X, Y, to save the file.


rm initrd.cpio
find . -print0 | cpio -o0 -H newc -v > /tmp/initrd.img.cpio
gzip -9c /tmp/initrd.img.cpio >/tmp/initrd.img-2.6.24-19-generic
mv /boot/initrd.img-2.6.24-19-generic /boot/initrd.img-2.6.24-19-generic.bak
mv /tmp/initrd.img-2.6.24-19-generic /boot/
nano /boot/grub/menu.lst


Now you can find the boot line for your kernel and remove the acpi=off option. I'd also suggest removing quiet and splash if they're still there, that way you can see what's happening. Mine looks like:


kernel /vmlinuz-2.6.24-19-generic root=UUID=ba05d9a0-8436-400d-9a6f-f0d041fb94e3 ro noapic

Your UUID won't be the same as mine, don't change anything in this line except for the bolded text.

Best of luck. Post with any progress.

fbdelivers
July 15th, 2008, 06:03 AM
Thanks for the detailed instructions. I gave it a shot and unfortunately it didn't work. I'm still getting the critical trip_point message on boot at (71 degrees). I've been running the computer for a while and will let it cool down.

I didn't receive any errors when running your options and the boot loads just fine up to starting acpid.

Let me know if there is any log that you'd like to see and I'll post. I'll also try again when my machine cools down.

AstronomyDomine
July 15th, 2008, 06:20 AM
Found a few errors in my post. I've corrected them. Please try to run through it again, and post back with your results.

tC_Crazy
July 15th, 2008, 07:09 AM
I tried the code, but had some problems. First, I believe... wait, I think you edited the code... b/c I copied down /tmp/initrd.cpio instead of /tmp/directory.cpio/initrd.cpio.

Then, I made the stupid mistake of not sudo-ing every step, so the rm didn't work and thermal.ko was not deleted... among other things. So thermal shutdown resulted. So i went back in, tried repeating all the steps (bad idea), and now I get a kernel panic on boot for not being able to mount the fs to "unknown media (0,0(" or something like that. No worries, I'll just reinstall ubuntu tomorrow (I just installed it today.. haven't done anything since) and try the instructions again. By the way, thanks for instructions... esp if they work! I was looking exactly for this.

fbdelivers
July 15th, 2008, 07:22 AM
I tried the steps one more time. (I did the original initrd to make sure that I removed the thermal file.

I'm still getting the trip_point issue on boot at (69 C). If I go back and set the boot to acpi=off again the new kernel loads fine (minus the acpi / wireless).

I appreciate the time you have taken - I won't be able to reply for about a day.

I have the tx2525nr - latest ubuntu
uname -r 2.6.24-19-generic

The only thing different in my menu file is:


kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=8c5aa53d-de77-4cb9-8a7d-9190d4a90d9c ro xforcevesa noapic

kv11
July 15th, 2008, 10:03 AM
You could also try altering parameters of thermal module:

$ modinfo thermal
filename: /lib/modules/2.6.24-19-generic/kernel/drivers/acpi/thermal.ko
license: GPL
description: ACPI Thermal Zone Driver
author: Paul Diefenbaugh
srcversion: 484C09AEA5B2FE85E9747E6
alias: acpi*:LNXTHERM:*
depends: processor
vermagic: 2.6.24-19-generic SMP mod_unload 586
parm: act:Disable or override all lowest active trip points. (int)
parm: crt:Disable or lower all critical trip points. (int)
parm: tzp:Thermal zone polling frequency, in 1/10 seconds. (int)
parm: nocrt:Set to take no action upon ACPI thermal zone critical trips points. (int)
parm: off:Set to disable ACPI thermal support. (int)
parm: psv:Disable or override all passive trip points. (int)


Parameters like nocrt seems to be relevant. You could try altering them by editing /etc/modprobe.d/options file in the root filesystem or in initrd.

kv11
July 15th, 2008, 10:09 AM
EDIT: Please see more detailed explanation here (http://ubuntuforums.org/showpost.php?p=5417491&postcount=69).


You could also try the following boot options (i.e. arguments for kernel command line, *NOT* for options file):


thermal.act= [HW,ACPI]
-1: disable all active trip points in all thermal zones
<degrees C>: override all lowest active trip points

thermal.crt= [HW,ACPI]
-1: disable all critical trip points in all thermal zones
<degrees C>: lower all critical trip points

thermal.nocrt= [HW,ACPI]
Set to disable actions on ACPI thermal zone
critical and hot trip points.

thermal.off= [HW,ACPI]
1: disable ACPI thermal control

thermal.psv= [HW,ACPI]
-1: disable all passive trip points
<degrees C>: override all passive trip points to this value

thermal.tzp= [HW,ACPI]
Specify global default ACPI thermal zone polling rate
<deci-seconds>: poll all this frequency
0: no polling (default)

tC_Crazy
July 15th, 2008, 05:26 PM
kv11, this seems like an even more direct approach to the thermal module... plus it's completely nondestructive so I'll try the auto detailer's saying of "the least aggressive method first."

I'll try the following boot options when I get off of work (should be very redundant but sometimes that is necessary like with noacpi acpi=off):

thermal.act=-1
thermal.crt=-1
thermal.nocrt= (wait a sec, what value do i put here?.. sorry if this is a newb question)
thermal.psv=-1
thermal.off=-1

If that fails, I'll try editing the thermal module...and if that fails I'll try Astronomy's method... btw did that actually work for booting up with wifi/sound/anything else that require acpi?

Oh, does anyone get a kernel panic if they boot with JUST noapic? I can only get it to work properly with both noapic AND acpi=off. Just acpi=off results in the shutdwon. I've got a CTO tx2500z with the 2.4Ghz ZM-86 processor, 3GB RAM.

isachan
July 15th, 2008, 07:59 PM
kv11, you're a God send !

I added the following lines to /etc/modprobe.d/options file :
(Edit: corrected options from option as per tC_Crazy)

options thermal.act=-1
options thermal.crt=-1
options thermal.nocrt=1
options thermal.psv=-1

(I removed the line "option thermal.off=-1 later on)
(tC_Crazy - a bit of googling lead me to how to specify .nocrt value)

Also, I added noapic to kernel boot option.

Now bluetooth is working ! No more full-speed fan noise ! Yeah !

I can see suspend icon on the log-off window (haven't tried).

My machine became a bit sluggish, I suppose some other services / processes are now turned on and running.

Wireless light is blue, and you can turn on and off, but it is wrongly recognized as a BCM4315. I don't see any AP with Wicd.
After sudo modprobe wl, do a dmesg and you'll see it is assigned as eth1.
For some reason, I still see ndiswrapper as a loaded module, despite of the fact I completely removed. What's with ? Let me tweak around a bit more...

No sound yet. I'm gonna try irq_debug, irq_balance, irqfixup, etc.

My TX2500 is much better than before ! Thanks !

Isao

tC_Crazy
July 15th, 2008, 09:08 PM
isachan, I'm not positive if this is correct, but since the tx2000 and tx2500 use the same RealTek driver, I'm going to assume that they have the same sound card. If so, the info in this tx2000 sound card thread may help... http://ubuntuforums.org/showthread.php?t=585909

By the way, any luck with the active digitizer (pen) or touchscreen?

pluckster
July 15th, 2008, 10:01 PM
I hate to sound rude but I'm just having trouble following all these threads. I can't really understand whats going on. So can we start from the beginning. I have a tz2524ca and I would like to install Ubuntu. I am getting errors but can I just get an an in one explanation covering everything that people have encountered starting with just getting it installed.

tC_Crazy
July 15th, 2008, 11:47 PM
I'll give you the run-down. The tx2500z has a problem in a component called ACPI which causes it to report very very high temperatures to Ubuntu. Ubuntu, in turn, shuts the system down to save the processor from overheating and damage. However, the processor isn't really overheating... it's just sending the wrong temperature.

So, if we turn off a component called ACPI (the one that deals with thermal management, among other things), we can boot into Ubuntu. The way to do this is insert the CD, select English, and Press F6 (this lets you add boot options). Add "noapic nolapic acpi=off" to the end of that line, and hit enter.

This will let you install and run Ubuntu. HOWEVER, turning ACPI off disables many things, including the sound card, touch screen, wireless, blutooth. Plus, the fan will run at 100% all the time.

In order to remedy this situation, we follow the instructions given by isachan to change the settings within the THERMAL MODULE that is a part of ACPI. By overriding the Thermal Module settings, we will keep ACPI (and our Wifi, BT, sound, etc.) and avoid the premature shutdown and high fan speeds... I am about to test isachan/kv11's instructions and will report back soon if it worked for me or not.

Good luck.

tC_Crazy
July 16th, 2008, 01:00 AM
After much fanfare, I believe I'm at the same point as isachan here. After trying his settings for /etc/modprobe.d/options (by the way, each line should read OPTIONS not OPTION... that threw errors in boot and the lines were ignored).

Next I tried the initrd method exactly as described earlier in this thread. Still nothing. Then I went into /etc/modprobe.d/blacklist and added the line blacklist thermal.

My only boot option was nolapic (noapic throws a kernel panic)

BT works, WLAN light is on (still needs drivers), it displays battery conditions, and fan speed is reduced. :KS

fbdelivers
July 16th, 2008, 05:49 AM
Outstanding!! Thanks everyone for the help.

In order for me to disable acpi option I followed the initrd instructions to remove thermal.

Added the thermal options to /modprobe.d/options file

I too had to also add blacklist thermal to get things to boot.

I can no boot with acpi=off.

Wireless is working as well (BTW I followed these instructions using the 2d option - https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

Sound still isn't working - I tried the following:
1. Open alsa-base configuration file:
gksu gedit /etc/modprobe.d/alsa-base

2. Add this as last row of file:
options snd-hda-intel model=hp

The mute button is working but still no sound.

Once I get sound and the touchscreen (anyone have any luck?) I can say buh bye to the vista partition.

Thanks
David

pluckster
July 16th, 2008, 07:32 PM
Thank you Crazy for the nice and neat rundown. I tried what you gave me but I'm still getting two errors in the install process. I can't tell if they are related but I don't think they are. One is that it cannot configure my DHCP network something or other. The other is it cannot find an installable kernel in the defined APT sources. This one seems to be the deal breaker. It says I could install one later but it says I shouldn't unless I know what I'm doing. Is this normal or is this just an error I'm getting?

EDIT: It wouldn't let me install a boot loader either, which is probably because of the kernel error or at least I think.

tC_Crazy
July 16th, 2008, 09:24 PM
Those seem to be unrelated. Have you run the CD error check yet? You may have to F6 and add the boot options noapic nolapic acpi=off with the CD error check selected.

Did you download the newest release HH? Also, did you download the 32-bit or 64-bit version? I'm using 32-bit. It sounds like a problem with the data on the CD, but I could be wrong. If you do try to burn a new CD, keep in mind that lower speed = less errors.

One more question, did you boot into the LiveCD and hit install, or install directly from the CD boot menu? Did it ever actually boot into Ubuntu? (wait, that's two questions... oh well!)

pluckster
July 16th, 2008, 09:45 PM
Yeah I've made three new CDs (Line, Alt and a Live 64) after my original failed. I even downloaded Ibex Alpha 2.

But I really should have checked the CD for errors. I'll do that right now.

...


well there we go, 1 error found in 1 file. Guess its back to the burning machine.

tC_Crazy
July 17th, 2008, 02:34 AM
slow 'n steady wins the race... if you still have trouble, try some different media.

isachan
July 17th, 2008, 07:15 AM
Another discovery today.

I've found out I've been running with only one core with noapic boot option !I took a deep breath and tried without it this morning. Now I got my dual core back ! You can see this with the power applet (the small battery icon), just by moving the mouse cursor over it. Or you can install and see with htop app. CPU dynamic frequency thing is not working though. Maybe it works with cpufreqd ?

tC_Crazy, it's funny my machine doesn't like nolapic option and yours does. I lose my wired network connection with nolapic.

I tried suspend yesterday, and it does power down with flashing power light. However, after a recovery, the screen just stays turned-off. It's not in my urgent priority list right now, so I haven't dig deeper into troubleshooting this yet.

I'm getting tired with no sound. I even installed ALSA 1.0.17 final with a script from this thread :
http://ubuntuforums.org/showthread.php?t=820959
and it's still not working ! I had to do some driver file copying after installing from source codes, so I don't recommend for anybody. Well, it's not working anyway, so...

Isao

isachan
July 17th, 2008, 08:59 AM
Miracle ! I have sound !

The last 2 lines of my /etc/modprobe.d/alsa-base file is like this :
options snd-cmipci mpu_port=0x330 fm_port=0x388
options snd-hda-intel index=0 model=toshiba position_fix=1

That's right, it's toshiba !

Try it with the current version of ALSA driver first to be safe.
I'm not really sure it's because I'm using ALSA 1.0.17 final ?

Make sure Master, Headphone, PCM, Front channels are not muted, and volumes are up.

I hope this works for you guys too !

Isao

pluckster
July 17th, 2008, 09:14 AM
Still no go on the kernel installing. The DCHP(?) error still comes up to. Its weird because these CDs work on my other computer just fine but as soon as those things are disabled on the laptop, everything breaks down.

I tried installing Ubuntu Studio of its DVD but that also didn't work. Same errors as before. Is it that hard to manually install a kernel?

EDIT: Okay well it let me finish the install this time. Still as far as I know no kernel was installed. I booted up and it let me start Ubuntu Studio. It went through to the kernel log daemon, stopped for a bit, then went to quickly through the next screen and shut itself down. Not to sure what happened but it probably has to do with the fact there is no kernel.

corwinspyre
July 17th, 2008, 04:29 PM
Thanks to everyone in this thread!

corwinspyre
July 17th, 2008, 05:42 PM
kv11, you're a God send !

I added the following lines to /etc/modprobe.d/options file :
(Edit: corrected options from option as per tC_Crazy)

options thermal.act=-1
options thermal.crt=-1
options thermal.nocrt=1
options thermal.psv=-1


This didn't work for me. /var/log/daemon.log shows (this is also what I see at boot time):

Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 9: ignoring bad line starting with 'options'
Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 10: ignoring bad line starting with 'options'
Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 11: ignoring bad line starting with 'options'
Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 12: ignoring bad line starting with 'options'

I copy/pasted it in from your post, so I know it's not a typo.


For the heck of it, I tried removing "options" so that it says:
thermal.act=-1
thermal.crt=-1
thermal.nocrt=1
thermal.psv=-1
but that yields a similar error:

Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 14: ignoring bad line starting with 'thermal.act=-1'
Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 15: ignoring bad line starting with 'thermal.crt=-1'
Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 16: ignoring bad line starting with 'thermal.nocrt=1'
Jul 17 12:21:46 deathstar modprobe: WARNING: /etc/modprobe.d/options line 17: ignoring bad line starting with 'thermal.psv=-1'

Any ideas? Thanks in advance.

corwinspyre
July 17th, 2008, 05:50 PM
Still no go on the kernel installing. The DCHP(?) error still comes up to. Its weird because these CDs work on my other computer just fine but as soon as those things are disabled on the laptop, everything breaks down.

I tried installing Ubuntu Studio of its DVD but that also didn't work. Same errors as before. Is it that hard to manually install a kernel?

EDIT: Okay well it let me finish the install this time. Still as far as I know no kernel was installed. I booted up and it let me start Ubuntu Studio. It went through to the kernel log daemon, stopped for a bit, then went to quickly through the next screen and shut itself down. Not to sure what happened but it probably has to do with the fact there is no kernel.

If it's booting up at all, it has a kernel. It sounds like you have the overheat issue. You should edit the grub boot line to say acpi=off at the end, as shown in this thread, and then do one of the three various fixes (also given in this thread).

pluckster
July 17th, 2008, 07:25 PM
I think it was just Ubuntu Studio doing something weird because it still doesn't work. I'm trying to reinstall a vanilla Ubuntu but it will not let me install the kernel or grub.

phrygius
July 17th, 2008, 07:47 PM
I'll give you the run-down. The tx2500z has a problem in a component called ACPI which causes it to report very very high temperatures to Ubuntu. Ubuntu, in turn, shuts the system down to save the processor from overheating and damage. However, the processor isn't really overheating... it's just sending the wrong temperature.

So, if we turn off a component called ACPI (the one that deals with thermal management, among other things), we can boot into Ubuntu. The way to do this is insert the CD, select English, and Press F6 (this lets you add boot options). Add "noapic nolapic acpi=off" to the end of that line, and hit enter.

This will let you install and run Ubuntu. HOWEVER, turning ACPI off disables many things, including the sound card, touch screen, wireless, blutooth. Plus, the fan will run at 100% all the time.

In order to remedy this situation, we follow the instructions given by isachan to change the settings within the THERMAL MODULE that is a part of ACPI. By overriding the Thermal Module settings, we will keep ACPI (and our Wifi, BT, sound, etc.) and avoid the premature shutdown and high fan speeds... I am about to test isachan/kv11's instructions and will report back soon if it worked for me or not.

Good luck.

Thank you for explaining the situation!

I just received my tx2510z on Tuesday, and was frustrated by the ACPI overheating issue before finding this thread.

I was wondering though, since I bought this tablet based on the success stories of tx2000 owners, did theirs have the same overheating problems too? I noticed a few of those threads mention noacpi as a boot parameter, yet I don't remember reading anything about how turning that off yields no functionality for sound, wacom, bluetooth, etc.

Thanks,
phrygius

tC_Crazy
July 17th, 2008, 08:32 PM
phrygius, the tx2000 is considerably different in this case, because it used a different chipset/processor/video card. The tx2500z has the new Turion 64 X2 Ultra (griffin) processors, a part of the Puma platform. I haven't looked very deep into the exact cause of the problem, but something causes ACPI to read very very high temps, and trigger a thermal shutdown. AFAIK, the tx2000 did not have thermal shutdown problems. ACPI is spidered into many components, and is pretty much essential for a USEFUL computer environment on the 2500.

pluckster, if you have blacklisted thermal, I suggest you try futzing around with boot options. As we now see, tx2500z's react differently to different options. (mine will not work with noapic, isachan's will) The three I have messed with are noapic, nolapic, acpi=off.

isachan,
That's really interesting about the sound card... and noapic... and the fact that nolapic kills the wired connection seems to make sense to me now. My wired NIC wasn't working with nolapic, but I assumed no one's was. I followed some guide on the forums for the same NIC, and after compiling/patching a driver, it DID work. not worth the work, IMO, since wifi is probably easier to install.

corwinspyre,
I noticed after i turned off quiet and splash boot options that I also got those "ignoring bad line" messages on boot... so I removed them. Definitely try editing /etc/modprobe.d/blacklist. Add this line
blacklist thermal
if that doesn't work, keep the blacklist and follow the initial instructions in this thread (page 2 i think). The combination of those two (or maybe just the blacklist, idk for sure) worked for me. Oh, and nolapic in the boot options, but again I'm not sure if that really did it. I'll get more evidence as to what exactly worked on my machine when i reinstall this weekend.

btw, I think this thread has a ton of great info and collaboration... great job everyone. I'm sure many will be able to use this as a resource to get a fully-functional tablet running Ubuntu (btw2, has anyone installed the digitizer drivers yet?? that's the scary recompile-and-potentially-break-everything-wasting-your-hard-work one. Backup first!!

corwinspyre
July 17th, 2008, 09:55 PM
phrygius, the tx2000 is considerably different in this case, because it used a different chipset/processor/video card. The tx2500z has the new Turion 64 X2 Ultra (griffin) processors, a part of the Puma platform. I haven't looked very deep into the exact cause of the problem, but something causes ACPI to read very very high temps, and trigger a thermal shutdown. AFAIK, the tx2000 did not have thermal shutdown problems. ACPI is spidered into many components, and is pretty much essential for a USEFUL computer environment on the 2500.

pluckster, if you have blacklisted thermal, I suggest you try futzing around with boot options. As we now see, tx2500z's react differently to different options. (mine will not work with noapic, isachan's will) The three I have messed with are noapic, nolapic, acpi=off.

isachan,
That's really interesting about the sound card... and noapic... and the fact that nolapic kills the wired connection seems to make sense to me now. My wired NIC wasn't working with nolapic, but I assumed no one's was. I followed some guide on the forums for the same NIC, and after compiling/patching a driver, it DID work. not worth the work, IMO, since wifi is probably easier to install.

corwinspyre,
I noticed after i turned off quiet and splash boot options that I also got those "ignoring bad line" messages on boot... so I removed them. Definitely try editing /etc/modprobe.d/blacklist. Add this line
blacklist thermal
if that doesn't work, keep the blacklist and follow the initial instructions in this thread (page 2 i think). The combination of those two (or maybe just the blacklist, idk for sure) worked for me. Oh, and nolapic in the boot options, but again I'm not sure if that really did it. I'll get more evidence as to what exactly worked on my machine when i reinstall this weekend.

btw, I think this thread has a ton of great info and collaboration... great job everyone. I'm sure many will be able to use this as a resource to get a fully-functional tablet running Ubuntu (btw2, has anyone installed the digitizer drivers yet?? that's the scary recompile-and-potentially-break-everything-wasting-your-hard-work one. Backup first!!

Got it to work! blacklist thermal itself didn't, so I ran through the steps on page 2, and it did. I didn't do anything else, including nolapic. Thank you.

tC_Crazy
July 18th, 2008, 01:57 AM
Well, I have experienced a (minor) miracle. My ubuntu partitions have NOT been wiped by the HP image =). Windows just wiped the MBR record, which was a 3 line fix using the grub console. :guitar:

I am working on wifi and sound right now.

phrygius
July 18th, 2008, 02:09 AM
Hrm, I just tried the "options" additions to /etc/modprobe.d/options and it did not work when I removed the "acpi=off" boot option.

I do have the "blacklist thermal" fix in place as well :(

isachan
July 18th, 2008, 02:25 AM
Alright guys, I got the digitizer PARTIALLY working. I got my screen protector today, so as soon as I applied, I rushed myself to go over this place :
http://sourceforge.net/project/showfiles.php?group_id=69596

and got linuxwacom-dev 0.8.1 July 9, 2008 driver.

There is a handy place for TX2000 linux info here :
http://mirosol.kapsi.fi/tx2020/tx2000howto.htm
and scroll down to the sub-topic says "Using Wacom Active Digitizer with pen".

I kinda sorta followed the instruction loosely, but let me post how I did as follows :

1. Extract the linuxwacom-0.8.1.tar.bz2 source tarball to a directory. I extracted in ~/hp-tx2500/digitizer/

2. In terminal (command line), cd to the directory created by extraction, like, "cd ~/hp-tx2500/digitizer/linuxwacom-0.8.1"

3. I had to install some more supporting libraries, as :
"sudo apt-get install libx11-dev libxi-dev x11proto-input-dev input-utils"

4. After that, do "./configure --enable-wacom --enable-hid --enable-usbmouse --enable-input" (Maybe I enabled too many things)
Check everything went good.

5. make
You may get errors depending on which supporting libraries are not installed. I'd try installing those libraries described in the TX2000 info page one by one, and recompile by typing make again.

6. sudo make install
6a. sudo rmmod wacom (For the first time around, you shouldn't have to do this)

7. sudo cp src/2.6.24/wacom.ko /lib/modules/2.6.24-19-generic/kernel/drivers/input/tablet/wacom.ko

8. sudo depmod -e

9. sudo modprobe wacom

10. Edit your /etc/X11/xorg.conf file as follows :

*** Add these lines to the beginning of the file:

Section "InputDevice"
Identifier "TabletPCStylus"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "stylus"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
Option "Button2" "3" # make side-switch a right button
Option "TopX" "225"
Option "TopY" "122"
Option "BottomX" "26365"
Option "BottomY" "16488"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus2"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "stylus"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/wacom"
Option "TopX" "01429"
Option "TopY" "01150"
Option "BottomX" "25300"
Option "BottomY" "15300"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus3"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "eraser"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
EndSection

*** And change "ServerLayout" and "Modules" sections to match the settings above :

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
Inputdevice "Synaptics Touchpad"
Inputdevice "TabletPCStylus"
Inputdevice "TabletPCStylus2"
Inputdevice "TabletPCStylus3"
EndSection

Section "Module"
Load "wacom"
Load "glx"
EndSection


11. Reboot, pen should work PARTIALLY.

---

Here are the reasons why I said PARTIALLY :

Pressure sensitivity is, well, extremely sensitive. I can't draw a long stroke at all if I apply a just a bit more of extra pressure. You'll need a super-human sensitive touch. This is confirmed with Gimp. Forget about writing on CellWriter, you'll just confuse the training session.

Acts a bit funny, almost a similar experience with pressing and releasing the mouse button at the same time.

Eraser acts just like the pen.

The side button is working, acts as the right mouse button.

---

Well, it's good to see the mouse cursor follows your pen point, when it is hovering 1/4inch over the screen.

I just had to jot down my findings here quickly, so we can be headed in the right direction.

Isao

phrygius
July 18th, 2008, 03:01 AM
As an aside, do you all think a screen protector is necessary?

corwinspyre
July 18th, 2008, 03:21 AM
As an aside, do you all think a screen protector is necessary?I never had one on my tx1000, and it wasn't a problem, but it can't hurt /shrug

tC_Crazy
July 18th, 2008, 03:38 AM
bah, I can't get wifi to work. I had previously installed step 2b from those instructions. After doing a reinstall of ndiswrapper and then a ndiswrapper -r bcmwl5, I did the whole process again with step 2d... but even after a restart it's not detecting any new interfaces. any ideas?

corwinspyre
July 18th, 2008, 03:58 AM
bah, I can't get wifi to work. I had previously installed step 2b from those instructions. After doing a reinstall of ndiswrapper and then a ndiswrapper -r bcmwl5, I did the whole process again with step 2d... but even after a restart it's not detecting any new interfaces. any ideas?
It sets it up with the wl driver automatically. You shouldn't need ndiswrapper. I don't know the steps you took to use ndiswrapper, but maybe try blacklisting it and un-blacklisting wl if you did when installing ndiswrapper.

isachan
July 18th, 2008, 04:09 AM
If you'd choose to use ndiswrapper, you have to remove wl driver, and vice versa.

Also, I like screen protector from my past experience. I can see all kinds of scratches on the protector, be it on PDA, my TX1000, etc. I think it's better than exposed. Especially on TX1000, I had to touch the screen rather hard to write on it.

I'm still waiting for the next version of wl driver to be posted on the regular repository. The current one is not really working on other computers with the same wireless device either. I heard about a 2 weeks ago that it has been updated on the proposal repository, and that one should be the working version. If you search on this Ubuntu forum, you may get updates on the status of wl driver.

Isao

corwinspyre
July 18th, 2008, 04:12 AM
If you'd choose to use ndiswrapper, you have to remove wl driver, and vice versa.

Also, I like screen protector from my past experience. I can see all kinds of scratches on the protector, be it on PDA, my TX1000, etc. I think it's better than exposed. Especially on TX1000, I had to touch the screen rather hard to write on it.

I'm still waiting for the next version of wl driver to be posted on the regular repository. I heard about a 2 weeks ago that it has been updated on the proposal repository. If you search on this Ubuntu forum, you may get updates on the status of wl driver.

Isao
Yep, if you enable hardy-proposed, you get the update. I'm posting wireless from Ubuntu on my TX2500 right now, actually. I know the dev said because of the simplicity of the fix and the positive results posted in the bug report about the fix, it got fast-tracked, so hopefully you'll have it sooner than later.

AstronomyDomine
July 18th, 2008, 04:19 AM
Basically, inside of the acpi subsystem is a module called thermal which reads temperatures from thermal sensors in the hardware, and shuts down the computer if the temperatures reach a certain trip point. Because the chipsets in the tx2500 are so new, thermal doesn't correctly read the sensors, and acpi shuts down the machine after the kernel is loaded.

Blacklisting thermal in /etc/modprobe.d/blacklist most likely won't solve the issue because thermal is loaded in the initramfs, so the only way to stop thermal from loading is to remove it from your initrd. My instructions on page 2 should remove thermal from the initramfs, but this is only a temporary fix. It will need to be done every time the kernel is upgraded until the problem is fixed.

There was also a mention of raising or eliminating the trip points in the thermal module, but I never attempted this, so I can't say whether it will work or not.

fbdelivers
July 18th, 2008, 05:15 AM
Miracle ! I have sound !

The last 2 lines of my /etc/modprobe.d/alsa-base file is like this :
options snd-cmipci mpu_port=0x330 fm_port=0x388
options snd-hda-intel index=0 model=toshiba position_fix=1

That's right, it's toshiba !

Try it with the current version of ALSA driver first to be safe.
I'm not really sure it's because I'm using ALSA 1.0.17 final ?

Make sure Master, Headphone, PCM, Front channels are not muted, and volumes are up.

I hope this works for you guys too !

Isao

Sweet - your fix worked for me as well. Thanks!

phrygius
July 18th, 2008, 12:18 PM
Has anyone else had negative results from the /etc/modprobe.d/options fix? I will try Astronomy's fix after work today and let you know how it goes.

(once again, mine is the tx2510)

Thanks,
phrygius

tC_Crazy
July 18th, 2008, 03:53 PM
phrygius,
I didn't have a negative result per se, but Ubuntu reported on startup that it was ignoring all those lines anyway, as "bad." For me, the winning combo was AstronomyDomine's page 2 instructions, plus blacklisting thermal. I don't understand why that worked, but I know it did. Afterwards i was able to boot with no added boot options.

Now about wireless... I never got the wl driver. Even before ndiswrapper, there was no mention of wl in the restricted drivers, and there was no wireless interface if i did an ifconfig or iwconfig. I'm pretty sure it showed up in lspci, so it does see the card.

isachan
July 18th, 2008, 04:23 PM
tC_Crazy, what kind of wireless device came with your machine ?

You may have to use b43-fwcutter driver and firmwares.
Doing some search on Ubuntu forums may lead you to an answer.

isachan
July 18th, 2008, 05:44 PM
I just updated my ATI fglrx graphics driver to 8.6 via EnvyNG, and man ! it's pleasing my eyes. :)

Combined with Mplayer, I can play HD 1080p content almost flawlessly with some slowdown spots.

Now I can play HD 720p content on Kaffeine player ! Before this update this movie player was too slow, and unusable. As this is my primary video content player, I was disappointed but no more !

Have you guys played racing simulation game on this machine, called Torcs ? I use that as a nice and quick benchmark tool. It's a fun way to check the performance of 3D acceleration.

phrygius
July 18th, 2008, 05:45 PM
phrygius,
I didn't have a negative result per se, but Ubuntu reported on startup that it was ignoring all those lines anyway, as "bad." For me, the winning combo was AstronomyDomine's page 2 instructions, plus blacklisting thermal. I don't understand why that worked, but I know it did. Afterwards i was able to boot with no added boot options.

Update: I tried AstronomyDomine's page 2 instructions as well, and they seem to fix the ACPI+Thermal problem!

THANK YOU Astronomy!!

I guess I wouldn't mind too much having to do this over again with new kernel updates, but it'd be awesome if a permanent fix came around.

Now, I'll have to occupy myself with attempting to get the touchscreen to work.

Thanks,
phrygius

isachan
July 18th, 2008, 05:50 PM
Phew, I'm getting tired tweaking digitizer and the touch screen.
I'm gonna just post my in-progress results.

So now I got my touch screen part of the same wacom digitizer PARTIALLY working as well ! :)

The pressure sensing got much better, but still it releases the drag if I apply pressure slightly more. I started to get some long strokes, but still not good enough for CellWriter.

Touch screen must be calibrated, but I don't know how. I just played around with the numbers in Top X,Y and Bottom X,Y parameters, but it was a moving target. The result was just confusing by calibrating this way.

Here's my /etc/X11/xorg.conf :

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
# Option "SendCoreEvents" "true"
# Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"# USB ONLY
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
Option "Button2" "3"# make side-switch a right button
Option "TopX" "225"
Option "TopY" "122"
Option "BottomX" "26365"
Option "BottomY" "16488"
Option "PressCurve" "17,0,100,83"# Firmer Curve
Option "Threshold" "-140"# sensetivity to do a "click"
Option "Speed" "8.0"
# Option "PressCurve" "50,0,100,50"
# Option "PressCurve" "0,5,95,100" #Softer Curve
# Option "PressCurve" "2"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
# Option "SendCoreEvents" "true"
# Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"# USB ONLY
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
Option "TopX" "01429"
Option "TopY" "01150"
Option "BottomX" "25300"
Option "BottomY" "15300"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
# Option "SendCoreEvents" "true"
# Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "USB" "on"# USB ONLY
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "touch"
# Option "SendCoreEvents" "true"
# Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
Option "Device" "/dev/input/wacom"
Option "Type" "touch"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
Option "USB" "on"# USB ONLY
Option "TopX" "0"
Option "TopY" "0"
Option "BottomX" "1280"
Option "BottomY" "800"
Option "KeepShape" "on"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
Inputdevice "Synaptics Touchpad"
Inputdevice "stylus" "SendCoreEvents"
Inputdevice "eraser" "SendCoreEvents"
Inputdevice "cursor" "SendCoreEvents"
Inputdevice "touch" "SendCoreEvents"
EndSection

Section "Module"
Load "wacom"
Load "glx"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "ServerFlags"
# Option "AIGLX" "Off"
EndSection

Section "Extensions"
# Option "Composite" "Enable"
Option "Composite" "Enable"
EndSection

AstronomyDomine
July 18th, 2008, 10:23 PM
Awesome job isachan. This is the best news I've heard in a while.

I'm downloading the daily build of Intrepid right now. I'll post back with all of my results soon. From the sound of it, we should now have touchscreen, active digitizer, audio, and possibly wireless support now.

To those with working wireless: Which wireless chipset do you have? I believe that there were a few different options, one with only a/b/g, and one with a/b/g/n.

I'm also going to try to make my instructions for removing thermal on page 2 into a generic shell script so it'll be easier to run after a kernel upgrade. I'm not exactly sure how to tell it to remove the line "thermal" from conf/module. Anyone know how I would go about doing this?

isachan
July 18th, 2008, 10:57 PM
Thanks, AstronomyDomine. It was truly worthwhile.

This machine really shines with Linux (Kubuntu 8.04), that I haven't boot up Vista partition for the last several days now. Ha ! I'll keep Vista until I won't see any BIOS updates from HP, like my old TX1000. I'm gonna take off Vista sticker from my TX1000 soon.

I refined my digitizer tweak with a handy tool called "Gnome Graphics Tablet Apps" : http://alexmac.cc/tablet-apps/
You can tweak and see pressure sensitivity and pressure curve very intuitively, instead of guessing values and restarting X several dozen times. For 64bit, you have to compile from the source code. It's not that hard to do.

Other very good link is here : https://help.ubuntu.com/community/Wacom

And here's my updated /etc/X11/xorg.conf :


Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
# Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on" # USB ONLY
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
Option "Button2" "3" # make side-switch a right button
Option "TopX" "225"
Option "TopY" "122"
Option "BottomX" "26365"
Option "BottomY" "16488"
Option "PressCurve" "20,0,100,100" # Firmer Curve
Option "Threshold" "0" # sensetivity to do a "click"
Option "Speed" "8.0"
Option "ClickForce" "21"
# Option "PressCurve" "50,0,100,50"
# Option "PressCurve" "0,5,95,100" #Softer Curve
# Option "PressCurve" "2"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
# Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"# USB ONLY
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
Option "TopX" "01429"
Option "TopY" "01150"
Option "BottomX" "25300"
Option "BottomY" "15300"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
# Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "USB" "on" # USB ONLY
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "touch"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
# Option "Device" "/dev/input/event0" # USB ONLY
# Option "Device" "/dev/input/wacom"
Option "Type" "touch"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
Option "USB" "on"# USB ONLY
Option "TopX" "0"
Option "TopY" "0"
Option "BottomX" "1280"
Option "BottomY" "800"
Option "KeepShape" "on"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
Inputdevice "Synaptics Touchpad"
Inputdevice "stylus" "SendCoreEvents"
Inputdevice "eraser" "SendCoreEvents"
Inputdevice "cursor" "SendCoreEvents"
Inputdevice "touch" "SendCoreEvents"
EndSection

Section "Module"
Load "wacom"
Load "glx"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Extensions"
# Option "Composite" "Enable"
Option "Composite" "Disable"
EndSection

Enjoy.

AstronomyDomine
July 18th, 2008, 11:43 PM
I have some great news. With the daily build of intrepid, the system installs and boots without acpi=off.

However, because it's a daily build, it's far from perfect. Ubuntu-desktop did not install, so it booted to a terminal, and I'm in the process of installing ubuntu-desktop through apt. I'll update with progress along the way.

Weststar
July 19th, 2008, 01:53 AM
Thanks for all of this info! =)

Would someone be able to make a Step by Step for people like me who suck at linux?

AstronomyDomine
July 19th, 2008, 03:32 AM
Thanks for all of this info! =)

Would someone be able to make a Step by Step for people like me who suck at linux?

No problem. I'll throw together a howto if needed once we get the last few things figures out. Right now we've fixed the acpi shutdown problems in Hardy by removing the thermal module from the initramfs. There's a step by step on page 2 for that.

We've also got sound working. It only involves adding two lines to a file (more info on page 3 or 4), so that's not too bad.

Finally, we've got basic touchscreen and active digitizer support on page 5, but make sure to use isachan's latest xorg.conf posted on page 7.




I've been having some great success using today's daily of Intrepid. The acpi issues must be solved in 2.6.26 because I never once had to use acpi=off. I was easily able to boot and install, so things are going pretty well.

I'm having some troubles getting fglrx installed and running, but it seems to be because of bugs in Intrepid, nothing to do with the hardware.

I also couldn't get the wireless working. I tried following the instructions on the link posted on page 3, but it didn't work for me. I have the Broadcom BCM4322 a/b/g/n card.

Finally, following isachan's instructions, I was able to get the active digitizer working very well. There are definitely some touch sensitivity problems, but we should be able to get those ironed out pretty soon. I wasn't as lucky with the resistive digitizer (touchscreen). It seems to work, but needs a lot of calibration. It doesn't move the cursor anywhere near my finger.

We've made great progress everybody. Just a few weeks ago I was seriously considering returning this tablet because of all of the problems I was having. Now I love it! Lets keep pushing forward and we'll have the last few problems fixed in no time.

I'm going to get back to trying to get fglrx working in Intrepid. I'll post back with any more results.

thegnark
July 19th, 2008, 03:55 AM
Thanks for all of this info! =)

Would someone be able to make a Step by Step for people like me who suck at linux?



Wait until Oct 30, 2008
Install Intrepid Ibex

;)

Honestly it sounds like it might be a little easier to wait for Intrepid... I'm going to consider installing once Alpha 3 comes out and see how it goes... I don't mind tweaking around, and reinstalls don't bother me much.

tC_Crazy
July 19th, 2008, 04:55 AM
Astronomy, I have the same bcm4322ag a/b/g/n/BT card. I'm going to play with it for a little while today and see if I can get wl or ndiswrapper to pick it up.

kv11
July 19th, 2008, 04:29 PM
A little explanation about changing trip points of thermal module (it seems that my previous post was a bit confusing). There are two ways of doing it:

1. First method: module options. Add the following lines to /etc/modprobe.d/options


options thermal psv=-1 act=-1 crt=-1 nocrt=1

(note the space after thermal, not a dot!). You could also try experimenting with different numerical values to retain the ability to automaticaly control fan speed and shutdown on overheat:


# psv is passive trip point value in degrees C
# act is active trip point value in degrees C
# crt is critical trip point value in degrees C
# nocrt should *not* be included in this line
#
# actual values in the following line are random,
# you should try-and-select them yourself (probably based on
# values of temperature in /proc/acpi/thermal_zone/*/*) and
# post here in case of success !
#
options thermal psv=60 act=100 crt=150


2. Second method: kernel boot parameters (should always work independing of whether thermal module is loaded from initrd or root). Add the following to your kernel command line (along with nolapic noapic and other options in /boot/grub/menu.lst):


thermal.psv=-1 thermal.act=-1 thermal.crt=-1 thermal.nocrt=1

(note the dot after thermal, not a space). As with previous method you could also try setting numerical values.

pluckster
July 19th, 2008, 11:20 PM
Well I almost had it.

After finding out what my problem was with the kernel, I found this thread explaining how to install the kernel manually, http://ubuntuforums.org/archive/index.php/t-3444.html. I followed the instructions and the kernel happily loaded.

On rebooting I entered the usual commands(noacpi noapic etc) and I got to a login screen for the first time(Hooray!). Logged in fine and other than screen resolution, lack of any sort of network connection and the other usual problem you've been having, it seemed to work fine. Then I ran through Astronomy's steps to getting the thermal off and boot ready.

Rebooted and wouldn't boot up Ubuntu anymore. I think my first error was a kernel panic. I tried other boot options but they came back with either kernel panics or just other errors

isachan
July 19th, 2008, 11:36 PM
pluckster,

I don't think you'd need any of kernel boot option if you're using a new kernel version above 2.6.26, as per AstronomyDomine's previous post. I'm not using any boot option other than the regular ones, like "ro quiet splash" after following the instruction to remove thermal module from kernel. Also, I thought AstronomyDomine has successfully ran Ibex which comes with kernel 2.6.26 without any boot option ?

Anyway, I think you have to run "sudo update-initramfs -u" from recovery boot-up. You have to somehow get to command line to run it. Then reboot, and see how it goes. I had the same problem when I was using Gutsy, and that was after a regular kernel update !

Isao

corwinspyre
July 20th, 2008, 12:54 AM
Plukster, if you get it booted up again, enabling the restricted driver and restarting (or restarting the x server with ctrl-alt-backspace) will set it to the right resolution automagically

neutronstar21
July 20th, 2008, 01:09 AM
Hi all,

Ive just got myself a new HP TX2500 and I love this machine. Ive followed some of the instructions in this thread and my machine is running Ubuntu 8.04 very well after the initial thermal issues. You guys have been awesome at seeking and destroying the barriers to Ubuntu joy so a big thank you from me.

Just for the record Ubuntu Hardy is running well after:
- Installing from Ubuntu 8.04 64-bit install with acpi=off in boot line
- Removing the module thermal from my initramfs as per page 2, post #17 of this thread
- NOT adding specific thermal options as per page 3, post #24
- Blacklisting the thermal control, same thread, page 5, post #43
- NOT requiring nolacpi in boot line
- Sound working after specific post on page 4, post #46
- Wireless Broadcom 4328 rev 03 showing blue light after all this but requiring the instructions in this link -- https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

The following is not working (but i havent worked on it yet):
- Wacom touchscreen

You guys are doing a great job. Keep it up. Until I work out to send official thanks, consider yourselves THANKED!

corwinspyre
July 20th, 2008, 04:57 AM
Hi all,

Ive just got myself a new HP TX2500 and I love this machine. Ive followed some of the instructions in this thread and my machine is running Ubuntu 8.04 very well after the initial thermal issues. You guys have been awesome at seeking and destroying the barriers to Ubuntu joy so a big thank you from me.

Just for the record Ubuntu Hardy is running well after:
- Installing from Ubuntu 8.04 64-bit install with acpi=off in boot line
- Removing the module thermal from my initramfs as per page 2, post #17 of this thread
- NOT adding specific thermal options as per page 3, post #24
- Blacklisting the thermal control, same thread, page 5, post #43
- NOT requiring nolacpi in boot line
- Sound working after specific post on page 4, post #46
- Wireless Broadcom 4328 rev 03 showing blue light after all this but requiring the instructions in this link -- https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

The following is not working (but i havent worked on it yet):
- Wacom touchscreen

You guys are doing a great job. Keep it up. Until I work out to send official thanks, consider yourselves THANKED!

To add to the list, the b/g (a/b/g?--I don't know for sure; whatever the basic one is) card is bcm4310 rev2, and it works as of a patch currently in hardy-proposed.

pluckster
July 20th, 2008, 06:02 AM
Ibex wont even start for me. Can't get a desktop or install even with the boot params. It just hangs with a flashing cursor. I have to do a hard shutdown to restart.

Also having a problem with temp still. Even with acpi off its still catching the temp and shutting me down.

I tried "sudo update-initramfs -u" but I'm not sure what to think. I booted up and did some new things like try to connect through Ethernet. But when I tried to shut down it wouldn't go all the way. Trying a reboot now. And it fails. With all boot params it still fails.

AstronomyDomine
July 20th, 2008, 05:31 PM
Ibex wont even start for me. Can't get a desktop or install even with the boot params. It just hangs with a flashing cursor. I have to do a hard shutdown to restart.

Also having a problem with temp still. Even with acpi off its still catching the temp and shutting me down.

I tried "sudo update-initramfs -u" but I'm not sure what to think. I booted up and did some new things like try to connect through Ethernet. But when I tried to shut down it wouldn't go all the way. Trying a reboot now. And it fails. With all boot params it still fails.

Wait for Alpha 3. It should be out in four days. Maybe.

wabre
July 20th, 2008, 07:28 PM
sorry guys for "spamming" with an older model of the tx..i've got the tx2120us and also trying the 64bit version of Ibex now (k-/and ubuntu).

the only way i managed to start it (installing and then booting after install) is to move the hard reset shutdown button. BUT, not until it fully shuts down. Here is the strange thing, just a second before it actually should shut down, the boot up continues!! i am so surprised.

now i'm playing around with BIOS settings as well, the tx2000 series has another platform as the tx2500, but from what i can read, the problems are actually similar.

and yes, hopefully alpha 3 will be better in this regard. at least hoping we get the chance to install it without any big issues

corwinspyre
July 20th, 2008, 07:50 PM
sorry guys for "spamming" with an older model of the tx..i've got the tx2120us and also trying the 64bit version of Ibex now (k-/and ubuntu).

the only way i managed to start it (installing and then booting after install) is to move the hard reset shutdown button. BUT, not until it fully shuts down. Here is the strange thing, just a second before it actually should shut down, the boot up continues!! i am so surprised.

now i'm playing around with BIOS settings as well, the tx2000 series has another platform as the tx2500, but from what i can read, the problems are actually similar.

and yes, hopefully alpha 3 will be better in this regard. at least hoping we get the chance to install it without any big issues

the tx2500 never stops booting alone, it shuts down half way through the boot or soon thereabouts, so if I'm reading correctly, they aren't similar problems. Plus, it was reported that that problem doesn't happen in Ibex. I know there's a really long tx2000 thread (either 18 or 26 pages--I forget) on here, so i'd check that out if you haven't already

It could also be something with Ibex. Have you tried Hardy, and does it do the same thing?

pluckster
July 21st, 2008, 12:20 AM
Okay I just have to make sure I'm doing this right becasue I'm not getting to anywhere close to what you guys are getting so here are the steps I'm taking

Start Alternate Installer with acpi=off noapic nolapic
Go through installation
Install the kernel using aptitude just after it configures the APT sources becasue it cannot find one
Finish installation
Reboot and boot with acpi=off noapic nolapic
Login
Type in the steps given by Astronomy on page two
blacklist thermal
reboot
leave in only noapic nolapic
Hangs while running through boot sequence
Hard shutdown and sigh


Am I missing something or should I just wait for alpha 3?

P.S. Does acpi=off disable ethernet connections too because mine will not work.

tC_Crazy
July 21st, 2008, 01:15 AM
OK, I have wireless! My whole wireless driver situation was screwed up, so I decided to just reinstall ubuntu. Now pluckster, this is exactly what I did from initial startup. I put in the Ubuntu standard CD (not alternate), added boot options nolapic noapic acpi=off. I started up, ran through the installer. When finished, I started up with the same boot options. Ubuntu loaded, i logged in, and followed Astronomy's instructions exactly. I then added the line "blacklist thermal" to /etc/modprobe.d/blacklist. I rebooted, this time without the boot options, and everything (including wired LAN) worked fine.

Then to get the bcm4322ag card working, I installed ndiswrapper (both packages in synaptic--common and utils). I also blacklisted b43 and ssb, although that was on my own and idk if it was necessary. I downloaded an HP driver for the broadcom card, here: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=447687&swItem=ob-60549-1&mode=3


Next, I installed cabextract (sudo apt-get install cabextract). I ran "cabextract sp39243.exe". This gave me the driver files necessary for ndiswrapper. I then ran the following in the directory of the driver files:


sudo ndiswrapper -i bcmwl5.inf
sudo ndiswrapper -l


At which point I received: bcmwl5 : driver installed
device (14E4:432B) present

Then,
sudo depmod -a
sudo modprobe ndiswrapper
sudo cp /etc/network/interfaces /etc/network/interfaces.orig
echo -e 'auto lo\niface lo inet loopback\n' | sudo tee /etc/network/interfaces
sudo ndiswrapper -m
echo 'ndiswrapper' | sudo tee -a /etc/modules
echo 'ENABLED=0' | sudo tee -a /etc/default/wpasupplicant


At this point, I could (finally) see wireless networks, and ifconfig showed wlan0. I input my WEP key and within seconds was associated to the AP. I then unplugged my ethernet cable, and was browsing! I hope this helps you guys having trouble with the bcm4322ag (a/b/g/n/BT).

corwinspyre
July 21st, 2008, 02:48 AM
Okay I just have to make sure I'm doing this right becasue I'm not getting to anywhere close to what you guys are getting so here are the steps I'm taking

Start Alternate Installer with acpi=off noapic nolapic
Go through installation
Install the kernel using aptitude just after it configures the APT sources becasue it cannot find one
Finish installation
Reboot and boot with acpi=off noapic nolapic
Login
Type in the steps given by Astronomy on page two
blacklist thermal
reboot
leave in only noapic nolapic
Hangs while running through boot sequence
Hard shutdown and sigh


Am I missing something or should I just wait for alpha 3?

P.S. Does acpi=off disable ethernet connections too because mine will not work.

Maybe try without noapic and nolapic. I never used those.

And, acpi=off disables wireless but not wired networking.

AstronomyDomine
July 21st, 2008, 03:21 AM
Okay I just have to make sure I'm doing this right becasue I'm not getting to anywhere close to what you guys are getting so here are the steps I'm taking

Start Alternate Installer with acpi=off noapic nolapic
Go through installation
Install the kernel using aptitude just after it configures the APT sources becasue it cannot find one
Finish installation
Reboot and boot with acpi=off noapic nolapic
Login
Type in the steps given by Astronomy on page two
blacklist thermal
reboot
leave in only noapic nolapic
Hangs while running through boot sequence
Hard shutdown and sigh


Am I missing something or should I just wait for alpha 3?

P.S. Does acpi=off disable ethernet connections too because mine will not work.

Are you using Alpha 2 or a daily build? Either way, it'd probably be easiest to wait for alpha 3. With Intrepid, you should never need to set acpi=off. It should just work, or I'm just really lucky.


tC: Awesome news. Following your instructions I was able to get the device recognized. I'm having trouble getting it to connect to a network, but since you didn't have a problem, I'm guessing it has something to do with Intrepid. I'll keep working at it.

Has anyone tried to run on batter power? When I do, I get about an hour and a half battery life on my 8 cell battery. We should be able to improve this somehow. Any ideas?

tC_Crazy
July 21st, 2008, 04:46 AM
I too noticed that battery life is quite horrendous right now. I think some serious power management is in order.

pluckster
July 21st, 2008, 04:48 AM
Are you using Alpha 2 or a daily build? Either way, it'd probably be easiest to wait for alpha 3. With Intrepid, you should never need to set acpi=off. It should just work, or I'm just really lucky.


This happens with both Hardy and Intrepid, well the not working part at least. Hardy will at least realize its broken and shutdown while Intrepid just hangs.

I will take another crack at TCs instructions once more then if that fails I will just wait for Alpha 3

@corwinspyre - So my ethernet should be working? Ill have to try some other cables or something because it doesn't seem to work right now.

corwinspyre
July 21st, 2008, 04:52 AM
This happens with both Hardy and Intrepid, well the not working part at least. Hardy will at least realize its broken and shutdown while Intrepid just hangs.

I will take another crack at TCs instructions once more then if that fails I will just wait for Alpha 3

@corwinspyre - So my ethernet should be working? Ill have to try some other cables or something because it doesn't seem to work right now.

yeah, ethernet should be working

Weststar
July 21st, 2008, 07:40 PM
Good to see Wifi working, tC! So what else is left? Just more touchscreen stuff?

isachan
July 21st, 2008, 08:25 PM
Touchscreen / digitizer has a few bugs in the wacom linux driver 0.8.1-dev version. I have received a reply from author in email, that he is releasing next version soon to address some critical issues.

I'll post how it goes as soon as I install it.

chdist_gentoo
July 22nd, 2008, 02:44 AM
Thank you all very kindly for your support with this laptop, I've been able to establish a usable system because of your help.

Currently, my only kernel parameter is: "lapic_timer_c2_ok"

I recently realized that "nolapic" was disabling my second core; so, I looked in to the apic sources for additional parameters that wouldn't strictly disable LAPIC and I found the aforementioned parameter.

This seems to remove the kernel panic I was experiencing with full LAPCI enabled (timer issue) and allows the laptop to power down when halted.

Every other subsystem seems to work like a charm.
My remaining issues are:
-Better performance/battery consumption
-Functional webcam driver
-Working IR remote
-Display rotation (presumably under F/OSS driver) coupled with tablet input rotation

corwinspyre
July 22nd, 2008, 04:11 AM
Thank you all very kindly for your support with this laptop, I've been able to establish a usable system because of your help.

Currently, my only kernel parameter is: "lapic_timer_c2_ok"

I recently realized that "nolapic" was disabling my second core; so, I looked in to the apic sources for additional parameters that wouldn't strictly disable LAPIC and I found the aforementioned parameter.

This seems to remove the kernel panic I was experiencing with full LAPCI enabled (timer issue) and allows the laptop to power down when halted.

Every other subsystem seems to work like a charm.
My remaining issues are:
-Better performance/battery consumption
-Functional webcam driver
-Working IR remote
-Display rotation (presumably under F/OSS driver) coupled with tablet input rotation

The webcam should be working. Try installing cheese to test it out (if you haven't already)

tC_Crazy
July 22nd, 2008, 03:22 PM
Thank you all very kindly for your support with this laptop, I've been able to establish a usable system because of your help.

Currently, my only kernel parameter is: "lapic_timer_c2_ok"

I recently realized that "nolapic" was disabling my second core; so, I looked in to the apic sources for additional parameters that wouldn't strictly disable LAPIC and I found the aforementioned parameter.

This seems to remove the kernel panic I was experiencing with full LAPCI enabled (timer issue) and allows the laptop to power down when halted.

Every other subsystem seems to work like a charm.
My remaining issues are:
-Better performance/battery consumption
-Functional webcam driver
-Working IR remote
-Display rotation (presumably under F/OSS driver) coupled with tablet input rotation

Try scanning through the tx2000 threads for the rotation instructions. They had it down to a couple scripts, I think.

corwinspyre
July 22nd, 2008, 03:46 PM
Try scanning through the tx2000 threads for the rotation instructions. They had it down to a couple scripts, I think.

I believe the tx2000 uses an nvidia video card, which has a function built into the driver for screen rotation and which is what they used. If that's true, it won't work for us.

kg6gfq
July 22nd, 2008, 08:26 PM
I believe the tx2000 uses an nvidia video card, which has a function built into the driver for screen rotation and which is what they used. If that's true, it won't work for us.

The tx2000 does use an nVidia card, but they were using xrandr for the screen rotation, which ought to work just as well with the ATI Radeon card in the tx2500.

Here are some links to info on xrandr, info on rotating the wacom input, and a few scripts put together for the tx2000:
http://www.thinkwiki.org/wiki/Xorg_RandR_1.2
http://ubuntuforums.org/showthread.php?p=4731847&highlight=xrandr#post4731847
http://ubuntuforums.org/showthread.php?p=4812335&highlight=xrandr#post4812335
http://ubuntuforums.org/showthread.php?p=4910414&highlight=xrandr#post4910414
http://ubuntuforums.org/showthread.php?p=4923527&highlight=xrandr#post4923527
http://ubuntuforums.org/showthread.php?p=5020078&highlight=xrandr#post5020078
The first one is general information, the rest are solutions which become both more complex and more polished toward the end of the list.

I would try to sort this out myself, but I don't yet have a tx2500. I'm considering getting one, though, so thank you to everyone who has posted here with info about the laptop. One question: Does anyone know if the S-video and VGA ports work properly?

Thanks for all the info and solutions!

tC_Crazy
July 23rd, 2008, 04:03 PM
kg,
I assume the ports are working properly, since I'm using an ATI restricted driver. I can check for you tonight.

kv11
July 24th, 2008, 09:51 AM
Have anyone got touchscreen working ? How precise is the navigation using the pen ? For me, the actual position of the click could be 1-3 mm away from the position of the end of the stylus, nomater how I calibrate the screen (i.e. it's precise at the points where is was calibrated, but not precise at another points). The same issue is also seen in pre-installed windows. Is it normal for tx2500 or I just have broken screen ?

corwinspyre
July 24th, 2008, 01:42 PM
Have anyone got touchscreen working ? How precise is the navigation using the pen ? For me, the actual position of the click could be 1-3 mm away from the position of the end of the stylus, nomater how I calibrate the screen (i.e. it's precise at the points where is was calibrated, but not precise at another points). The same issue is also seen in pre-installed windows. Is it normal for tx2500 or I just have broken screen ?

Mine isn't like that. However, I did notice the sensor is in the pen, not the tip, so holding it straight up is different than holding it at an angle (as one normally holds a pen). At first I made the mistake of calibrating it with the pen straight up, so when I used it regularly, it seemed off. If you calibrated it with the pen held in a way other than which you normally use it, try again with that in mind.

tC_Crazy
July 24th, 2008, 05:53 PM
My pen is quite precise after calibration in Windows... I usually calibrate once daily, since it only takes a few seconds. Make sure you hold the pen exactly as you do when inking. The only place where I noticed a drop in accuracy is around the edges (for example, it's difficult to use taskbar tray icons with the pen.

ungermax
July 25th, 2008, 04:55 PM
I have a tx2510us, I was able to boot without ACPI=OFF by compiling a custom kernel without including the thermal zone option. Instantly, the Wifi works with ndiswrapper 1.53 and the light is blue! Still working on the touchscreen and sound however. I realize that isn't an ideal solution, but it hasn't blown up on me yet.

pluckster
July 25th, 2008, 07:52 PM
So I've downloaded Ibex Alpha 3 and tried it out. Its working quite a bit better than the others I've tried so far. It can now boot into a desktop without noapic and nolapic but I still have to use acpi=off otherwise it will hang with a blinking cursor. I haven't tested any of the features yet, I'll try an install soon instead then see what works and what doesn't.

corwinspyre
July 25th, 2008, 08:45 PM
I have a tx2510us, I was able to boot without ACPI=OFF by compiling a custom kernel without including the thermal zone option. Instantly, the Wifi works with ndiswrapper 1.53 and the light is blue! Still working on the touchscreen and sound however. I realize that isn't an ideal solution, but it hasn't blown up on me yet.

The sound fix is in this thread

corwinspyre
July 25th, 2008, 08:46 PM
So I've downloaded Ibex Alpha 3 and tried it out. Its working quite a bit better than the others I've tried so far. It can now boot into a desktop without noapic and nolapic but I still have to use acpi=off otherwise it will hang with a blinking cursor. I haven't tested any of the features yet, I'll try an install soon instead then see what works and what doesn't.

Did you try Hardy without noapic and nolapic? Because it was fine for me without those.

pluckster
July 25th, 2008, 08:55 PM
Did you try Hardy without noapic and nolapic? Because it was fine for me without those.

Yeah, I tried all the combinations possible and I think the only time it worked without one of those is with acpi=off nolapic.

But I did an install and I'm in the same spot as usual. I'll have to disable thermal and that but my ethernet is non responsive still. Had to boot with acpi=off to get to desktop. But now I don't need to enable GNOME fail safe to get the desktop to work.

tC_Crazy
July 25th, 2008, 10:50 PM
nolapic kills ethernet. If you have wireless, try using ndiswrapper with the instructions I posted before... it's much easier than compiling the ethernet driver. Put the tarball on a USB drive or find another way to get ndiswrapper onto your laptop, as well as the HP executable.. and cabextract.

pluckster
July 26th, 2008, 08:34 AM
Even without nolapic my ethernet will not work.

As for the wireless I'm sure it will work but my dorm doesn't have wifi (The rest of the campus does, go figure) so I want to get this ethernet problem solved.

On another note, after following Astronomy's directions for thermal and boot options, it will not shutdown. It will go through all the stuff and then just end with a System Halted line and stays on. And also when I restart it just hangs without acpi=off.

isachan
July 26th, 2008, 09:15 AM
pluckster, would you list the content of your /etc/network/interfaces file by doing "cat /etc/network/interfaces" ?

If you see eth0 for wired network interface, try "sudo ifup eth0" and "dhclient eth0".

pluckster
July 26th, 2008, 09:26 AM
Lets see here...


auto lo
iface lo inet loopback

Hmm no sign of eth0 or much of anything

isachan
July 26th, 2008, 09:46 AM
pluckster,

Append the following lines in /etc/network/interfaces file after the two lines you already have :

auto eth0
iface eth0 inet dhcp

save, and do "sudo ifup eth0", and let me know how it goes.

pluckster
July 26th, 2008, 10:22 AM
Still no good.

Did something along the lines of...


already a pid file
removed it

started listening and sending
did 5 DHCPDISCOVERs
No DHCPOFFERS
sleeping
grep /etc/resolv.conf (didnt exist)
grep /etc/network/run/ifstate (didn't exist) x2

Thats it. Odd

isachan
July 26th, 2008, 10:35 AM
Seems like some important config files are missing from the Ibex Alpha 3.

Alternatively, let me suggest using "Wicd" GUI network config app.
Download it and follow the installation guide.
http://wicd.sourceforge.net/download.php

This thing is much better than networkmanager. In fact networkmanager destroys some very crucial config files, that I hate it and avoid like a plague.

I'm sure searching and setting up network from command line is necessary at this point. There is a how-to on the Ubuntu forum.

AstronomyDomine
July 26th, 2008, 05:58 PM
sudo dhclient eth0

How's the touchscreen progress going isachan? I saw there was a minor revision to the linuxwacom project dev files. Is that what we were waiting for, or are we waiting for the next official release?

Has anyone had any luck getting fglrx working in Intrepid? I can't seem to get 8.6 or 8.7 to install.

isachan
July 26th, 2008, 09:16 PM
AstronomyDomine,
Yeah, it's been a while since last time said something about the latest wacom development driver, hasn't it ? Well, the reason is that 0.8.1-1 is not working well. The previous version was much better. The pen no longer register any clicks, so I can't write / draw anything. The touch screen is unchanged, works like before, with off-calibration.

By using wacomdump version 0.7.4 utility, I can see the pressure sensitivity bug has been sorta fixed, but looks strange in raw value. Eraser is recognized, not as another pen tip like the previous version.

I sent off 2 emails to the author asking questions but so far, I haven't received any reply. The documentation on the web site is quite old that only few of the information is applicable. I heard somewhere that so many protocols in the driver has been straighten out, and there are many more to fix.

I've found the bug in the source code from the previous version 0.8.1, so maybe I can try that when I have some time.

pluckster
July 26th, 2008, 11:47 PM
Okay well I tried running it without acpi=off and it seems to keep going until it reaches this line


[0.004000] SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

I'm looking in to what it might mean but does anyone here have any ideas?

isachan
July 27th, 2008, 09:39 AM
pluckster,
I think your LiveCD has been corrupted at some point.
I'm writing this post from Kubuntu 8.10 Alpha 3 I just downloaded.
It has booted successfully without any kernel boot option, and KDE 4.1 looks so pretty. I can see many little bugs, but hey, it sure looks good.

I suggest downloading the CD image again and verify the checksum with md5 command.

Since Hardy has long term support, I don't think I'll go into any version above it. And I don't know why some people are trying to use Ibex already ? Especially now that we already conquered the thermal issue ? I prefer the stable LTS version.

thegnark
July 27th, 2008, 03:23 PM
This has been posted as a HOWTO in the Tutorial & Tips forum. I will be updating that post instead of this one. Take me there! (http://ubuntuforums.org/showthread.php?t=873188)

I spent a long time configuring everything, and I thought I'd compile a quick writeup. I decided to re-install to meticulously document each step. This guide assume that you have at least basic working knowledge of using Ubuntu. If this is your first time using Linux, I'm recommending that you do not attempt to install Hardy Heron on the tx2500 at this time.

This is based on Ubuntu 8.04.1 (http://cdimage.ubuntu.com/releases/hardy/release/) x64 (Hardy Heron LTS). It probably works for 32-bit, but I haven't tested and don't see a specific reason to go with 32-bit over 64-bit.

Known issues:


Digitizer mostly works (but not 100%)
CPU scaling is NOT supported by current kernel
Suspend/sleep is a bit flaky

Installation (http://ubuntuforums.org/showpost.php?p=5426140&postcount=80)


Boot installation disc
Highlight your language and press [Enter]
Highlight"Install Ubuntu"
Press F6
Press F6 (again)
Highlight "acpi=off" and press [Enter]. small "x" should appear to the left of this option
Press [Esc]
Press [Enter]
This should boot to a graphical installer
Install as normal
After installation is complete, reboot as instructed

First boot (http://ubuntuforums.org/showpost.php?p=5426140&postcount=80)


Highlight the first boot option (Ubuntu 8.04.1, kernel 2.6.24-19-generic)
Press 'e' to edit the boot options
Scroll down to the line that starts with "kernel"
Press 'e' to edit this command
Scroll to the end of the line and add the following option (no quotes): "acpi=off". The boot options should have the following options listed: "ro quiet splash acpi=off"
Press '[Enter]' to confirm you are done editing the line
Press 'b' to boot
This should boot you to a graphical display prompt.

Configuring Ubuntu
This should get your Wireless working with an update to wl; also, a slightly newer kernel version is here.


Blacklist thermal (http://ubuntuforums.org/showpost.php?p=5426140&postcount=80)

Open a terminal
Run "sudo gedit /etc/modprobe.d/blacklist"
Add this text on its own line at the bottom of the file:
blacklist thermal
Save and close


Enable sound (http://ubuntuforums.org/showthread.php?p=5402251#post5402251)

Open a terminal
Run "sudo gedit /etc/modprobe.d/alsa-base"
Add the following line to the bottom of the file:
options snd-hda-intel index=0 model=toshiba position_fix=1
Save
Close


Update to proposed updates (http://ubuntuforums.org/showpost.php?p=5408040&postcount=53) (Fixes wireless and updates to kernel 2.6.24-20)
Note: Once these updates are moved from proposed to the standard repository, enabling "proposed" may not be required. In this case, skip this step.

Plug in to an ethernet port
Verify that you have internet access
Open up Synaptic

System
Administration
Synaptic Package Manager


Enable Hardy Proposed to your repositories

Settings
Repositories
Updates
Check "Pre-released updates (hardy-proposed)
Click the "Close" button
Confirm the message box that pops up warning you to reload


Click "Reload"
Click "Mark All Upgrades"

Click "Mark"


Click "Apply"

Click "Apply"


After updates are complete, click "Close"


Enable the digitizer (http://ubuntuforums.org/showthread.php?p=5469447#post5469447). Instructions are somewhat complicated, so I'm just providing a link to the thread instead of replicating here.
Install ATI restricted driver

Go to your restricted drivers manager

System
Administration
Hardware Drivers


Check "ATI restricted driver

Click "Enable"




Reboot as normal

If there's anything you would like to add or correct, post and I'll try to update as appropriate. Also, feel free to check out HP Pavilion tx2000 series laptop runnign (sic) Ubuntu 8.04 - My Howto (http://mirosol.kapsi.fi/tx2020/tx2000howto.htm).

AstronomyDomine
July 27th, 2008, 07:50 PM
Great instructions thegnark. Did you try booting at first without apci=off? The reason I ask is because thermal is loaded in the initramfs, so blacklisting it really shouldn't prevent it from loading. I'm wondering if perhaps our apic problems have been fixed in 8.04.1. Perhaps it was a kernel update from Hardy Proposed. I'm think I'll install 8.04.1 and see what I can find.

Thanks again!

pluckster
July 27th, 2008, 07:56 PM
pluckster,
I think your LiveCD has been corrupted at some point.
I'm writing this post from Kubuntu 8.10 Alpha 3 I just downloaded.
It has booted successfully without any kernel boot option, and KDE 4.1 looks so pretty. I can see many little bugs, but hey, it sure looks good.

I suggest downloading the CD image again and verify the checksum with md5 command.

Since Hardy has long term support, I don't think I'll go into any version above it. And I don't know why some people are trying to use Ibex already ? Especially now that we already conquered the thermal issue ? I prefer the stable LTS version.

I don't think its likely. This is pretty much the same outcome on the many distros I've tested, new and old. I popped in fedora last night and it ends at the exact same line. I'll have to bust out my other Ubuntu machine to download and test the MD5 sums.

isachan
July 27th, 2008, 09:01 PM
pluckster,

What is your BIOS setting on "Virtualization Technology" ?
Is it enabled or disabled ? Mine is disabled.

"Fan Always On" is certainly disabled.

fbdelivers
July 28th, 2008, 12:50 AM
I'm not a huge fedora fan - but did anyone else notice this post or tried fedora with the 2500?

http://forum.tabletpcreview.com/showthread.php?p=121795

From the post it looks like everything works out of the box...

thegnark
July 28th, 2008, 01:23 AM
I'm not a huge fedora fan - but did anyone else notice this post or tried fedora with the 2500?

http://forum.tabletpcreview.com/showthread.php?p=121795

From the post it looks like everything works out of the box...

Actually, based on that post, I downloaded Fedora 9 with intent to test compatibility...

Turns out that it never boots to installation... Freezes at some point and just sits there forever :confused:

thegnark
July 28th, 2008, 03:55 AM
AstronomyDomine: I tried the following additional boot options:


<nothing>
noapic
nolapic
noapic nolapic
pci=conf1
acpi=off

The only option to successfully boot was "acpi=off"

Also, I tried a couple of different configurations trying to boot into a fresh installation. Here are my findings:
2.6.24-20 fresh FAIL
2.6.24-20 blacklist thermal FAIL
2.6.24-20 remove thermal from initramfs FAIL
2.6.24-20 remove thermal from initramfs and blacklist thermal BOOT


I've update my guide with my re-installation findings. I hope it helps someone ><

pluckster
July 28th, 2008, 04:05 AM
Okay well I tried another install of 8.04.1 and it went a bit differently than yours and my other previous ones.

I had to use acpi=off and nolapic to get the install started, which if I remember right disables my LAN.

I used the same commands to start after the install as well.

When I did get to the desktop, for the first time it asked if I wanted to install video drivers and it also told me there were updates available. I tried to update but it then gave me an error saying it couldn't connect. Go figure. Also I noticed my touch pad scroll decided to start working to. Awesome.

I followed your first two steps but then I didn't change grub because I wasn't going to be able to do the step after.

Rebooted without any extra commands and my XServer failed and probably some other things I didn't catch. I also keep seeing thermal trips as well

Tried with nolapic. Seem that the temp shut it down again.

Tried again with acpi=off nolapic. Still no sound.

I'm really starting to think this laptop is much different from all for yours'.


EDIT: D'oh! I see you revised your instructions while I was doing this. I'll try the new ones.

EDITEDIT: I guess I can't do those ones either because I don't have LAN.

AstronomyDomine
July 28th, 2008, 04:45 AM
Thanks thegnark. I just installed 8.04.1, and I did need acpi=off to install. I upgraded then tried blacklisting thermal and rebooting, and that didn't work. With thermal still blacklisted, I ran dpkg-reconfigure for linux-headers-2.6.24-20 linux-headers-2.6.20-generic linux-image-2.6.24-20-generic linux-libc-dev linux-restricted-modules-2.6.24-20-generic linux-ubuntu-modules-2.6.24-20-generic

I think that by reconfiguring the kernel with thermal blacklisted caused thermal not to be built into the initramfs, so now I'm able to boot with no special boot options.

Now the only thing I need working is the touchscreen and active digitizer. Hopefully there's an update to the linuxwacom driver soon which fixes all of our problems.

thegnark
July 28th, 2008, 04:50 AM
If you install and boot first time with only "acpi=off", you still don't have LAN? Not once did I ever boot with noapic or nolapic.

If you can't get LAN working for some reason, I would skip the part where you update packages (as if you have a choice), but remember to update references from -20 to -19... If anyone can reply and tell me how to get (uname -r) integrated into those command, it would make things a little simpler. At this point, the only thing that updating it gives you is the fixed wl... which should be in the standard repo eventually... or you could download it directly and install it from flash drive...

Anyways, here are my network devices per lspci:

08:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)Completely unrelated, but I would like to get CPU scaling working... that should be a huge boon to battery life and heat reduction. I know nothing about it, so I have no idea what to test...

pluckster
July 28th, 2008, 05:24 AM
I guess I didn't really clarify that.

After the install I tried booting without any params. It did not but and shut itself down.

I then tried booting with just acpi=off which cased a kernel panic but no temp trips.

Then I tried with just nolapic. It ran like it should but with temp trpis all the time during it, it also comes up with a blue screen telling me xserver failed in the middle of the boot sequence. It then shuts down.

On another note just noapic also causes a kernel panic at what looks to be the same spot as acpi=off.

As to the update, I have -19 so how would I update that with -20?

I doubt this is an issue but are you dual booting your laptops or are you all going full on Ubuntu.

AstronomyDomine
July 28th, 2008, 09:33 AM
Yeah, I suppose I should have used some "uname -r"s in my original post. Anyway, it'd be "zcat initrd.img-`uname -r` > /tmp/directory.cpio/initrd.cpio" instead of "zcat initrd.img-2.6.24-20-generic > /tmp/directory.cpio/initrd.cpio"

The ` around uname -r is the character to the left of the number 1, it's not an apostrophe.

Also, did you try running dpkg-reconfigure on those packages I mentioned a few posts up with thermal blacklisted? I never removed thermal from my initramfs and I'm running perfectly.

Pluckster: Your LAN should work with acpi=off and noapic, mine did. What are the outputs of "ifconfig" "lspci | grep Ethernet" and "sudo dhclient eth0"?

thegnark
July 28th, 2008, 02:28 PM
pluckster:
2.6.24-20 is in the proposed repos
Also, yeah, I'm dual booting Vista Ultimate 32 with Hardy 64

AstronomyDomine:
No, I didn't run dpkg-reconfigure... however, I'm booting in now and performing these steps:

cd /boot
sudo mv initrd.img-`uname -r` initrd.img-`uname -r`.nothermal
sudo mv initrd.img-`uname -r`.bak initrd.img-`uname -r`Attempted boot and failed due to thermal trip (as expected), so I booted with acpi=off and ran:

sudo dpkg-reconfigure linux-headers-`uname -r`Attemped to boot and failed :( Boot with acpi=off again and ran:

sudo dpkg-reconfigure linux-headers-`uname -r` linux-image-`uname -r` linux-restricted-modules-`uname -r` linux-ubuntu-modules-`uname -r` linux-libc-devBooted as normal succesfully... so it would seem that you are correct, after blacklisting thermal, we can jsut run a dpkg-reconfigure and things should be fine... I'm updating guide

AstronomyDomine
July 28th, 2008, 08:03 PM
thegnark: It seems that once a module is blacklisted, any generated initramfs won't contain that module. This is really awesome because now we really just need to install with acpi=off and noapic, boot with acpi=off and no apic, blacklist thermal, enable hardy-proposed, then upgrade.

Because the kernel's going to be upgraded anyway, and it will generate a new initramfs, we probably don't even need to run a dpkg-reconfigure as long as we upgrade the kernel after we blacklist thermal.

Your guide is going to help a lot of people. Is there any way we could put it on the first page? Maybe isachan could edit his first post and put your guide there, as well as any other helpful tips and information for newcomers.

Has anybody tried using Catalyst 8.7? I'm interested in trying to improve my battery life by following these instructions: https://help.ubuntu.com/community/BinaryDriverHowto/Fglrx_lowpower but when I run "aticonfig --lsp" I recieve the error "POWERplay is not supported on your hardware" although I think it should be. Any ideas?

thegnark
July 28th, 2008, 11:51 PM
Hrm... did you try booting with only acpi=off? I never had to supply nolapic or noapic. I'll see if I can post a HOWTO.

And regarding battery life, I think we might be SOL until a kernel that supports the Turion processor is released. I posted a METOO at https://bugs.launchpad.net/bugs/231534

edit: updated guide on page 12 and submitted a HOWTO for approval

pluckster
July 29th, 2008, 08:32 PM
I feel like somewhat of an idiot right now.

I just realized that I have been using/downloading 32bit versions of all my ISOs. So I downloaded 64bit and would you look at this, I works just fine. Still odd though that 32 bit won't work at all.

Just running through your instructions now. I have ethernet now so it seems to be doing its job.

Edit: everything is good to go except sound for me. Thanks for helping me out. I'll look to see if I mistyped those lines.

thegnark
July 30th, 2008, 12:33 AM
Edit: everything is good to go except sound for me. Thanks for helping me out. I'll look to see if I mistyped those lines.

Oh yay! Glad someone confirms it all works in that order. The only thing I can think of regarding the sound... is tghat I only included 1 of 2 lines detailed in the original post, because when I checked the bottom of alsa-base, the first line was already there... maybe it's getting added as part of the updates to hardy-proposed and our fix needs to come after update.

Can you verify if "options snd-cmipci mpu_port=0x330 fm_port=0x388" exists in alsa-base towards the bottom? If not, add it - but it was there for me when I last wrote the guide.

fbdelivers
July 30th, 2008, 04:08 AM
AstronomyDomine,
Yeah, it's been a while since last time said something about the latest wacom development driver, hasn't it ? Well, the reason is that 0.8.1-1 is not working well. The previous version was much better. The pen no longer register any clicks, so I can't write / draw anything. The touch screen is unchanged, works like before, with off-calibration.

By using wacomdump version 0.7.4 utility, I can see the pressure sensitivity bug has been sorta fixed, but looks strange in raw value. Eraser is recognized, not as another pen tip like the previous version.

I sent off 2 emails to the author asking questions but so far, I haven't received any reply. The documentation on the web site is quite old that only few of the information is applicable. I heard somewhere that so many protocols in the driver has been straighten out, and there are many more to fix.

I've found the bug in the source code from the previous version 0.8.1, so maybe I can try that when I have some time.

Thanks isacan for the post. I'm not really understanding the wacdump command. I try the following:

wacdump /dev/input/by-id/usb-Tablet_ISD-V4-event-mouse

but it isn't giving me any feedback when I use the stylus. I'm probably just doing something dumb.

On another note I do seem to be having a little more success with the stylus with the following pressure setting.

Option "PressCurve" "0,15,85,100"

Thanks everyone!

gali98
July 30th, 2008, 04:09 AM
isachan
I have the tx2000z, but I think the wacom on our tablets is similar if not exact.
That being said I have everything working in 0.8.1-1 (stylus eraser touch) with the exception of the pressure still not working, but I submited and email on the mailing lists at sourceforge and ping (one of the devs) replied back.
Here is the tutorial if you want to try it....
http://ubuntuforums.org/showthread.php?p=5469447#post5469447

if would be interested in that bug you are talking about..
I'm no coder, but I think I could fix the source given a while :)
Kory

Weststar
July 30th, 2008, 06:53 AM
I feel like somewhat of an idiot right now.

I just realized that I have been using/downloading 32bit versions of all my ISOs. So I downloaded 64bit and would you look at this, I works just fine. Still odd though that 32 bit won't work at all.

Just running through your instructions now. I have ethernet now so it seems to be doing its job.

Edit: everything is good to go except sound for me. Thanks for helping me out. I'll look to see if I mistyped those lines.

Hmm, I didn't realize that this only works for 64 bit! =|

Is switching from 32 to 64 much of a big deal? I hear about many compatibility issues =(

vokesalex
July 30th, 2008, 08:46 AM
Cheers guys for all the help you've given on this thread. It's been a great help getting things working using Kubuntu 8.04 KDE4 Remix 64Bit.

I also managed to get the touchscreen working on my tx2520ea last night using the same guide as posted in #131. I compiled version 7.9-11 as I've heard this version is better.

I was just wondering how I should best go about calibrating my stylus. I've read that some people have used wacomcpl to achieve this but others have said there are problems with it. Is it just a matter of editing the TopX, TopY, BottomX, and BottomY values in xorg.conf until the stylus matches the cursor.

Apologies for my noob'ness, but all my experiences with linux so far have been with OpenSUSE and i'm not familiar with the equivalent tools in Ubuntu.

pluckster
July 30th, 2008, 08:49 AM
Its all good actually. Your instructions are right on. I mistyped position so after I fixed that everything was good to go.

Now on to the tablet.

gali98
July 30th, 2008, 02:34 PM
Cheers guys for all the help you've given on this thread. It's been a great help getting things working using Kubuntu 8.04 KDE4 Remix 64Bit.

I also managed to get the touchscreen working on my tx2520ea last night using the same guide as posted in #131. I compiled version 7.9-11 as I've heard this version is better.

I was just wondering how I should best go about calibrating my stylus. I've read that some people have used wacomcpl to achieve this but others have said there are problems with it. Is it just a matter of editing the TopX, TopY, BottomX, and BottomY values in xorg.conf until the stylus matches the cursor.

Apologies for my noob'ness, but all my experiences with linux so far have been with OpenSUSE and i'm not familiar with the equivalent tools in Ubuntu.

Well I'm glad my tutorial is being used.
Yes 7.9-11 will probably work better until the folks at linux wacom release a new package.. (I think it will be very soon)
Really the only thing wrong is the pressure sensitivty.

And yes just editing those four values will do it. Be careful though, using the wacomcpl to calibrate after calibrating using xorg.conf will mess everything up.
i.e. don't use both to calibrate, just use one....
Kory

pluckster
July 30th, 2008, 10:12 PM
Been playing around with some stuff and one thing I've noticed is that I can't get any more than one workspace at a time. I noticed this when trying to set up a desktop cube and other compiz stuff. any ideas?

corwinspyre
July 30th, 2008, 10:59 PM
Been playing around with some stuff and one thing I've noticed is that I can't get any more than one workspace at a time. I noticed this when trying to set up a desktop cube and other compiz stuff. any ideas?

install compizconfig-settings-manager, and go to general options->desktop size and set horizontal virtual size to 4 (the others should be 1) if you want a cube

pluckster
July 31st, 2008, 10:00 PM
Yeah I had all that going but my problem is even without the cube I only seem to be able to access one workspace. It shows four in the bottom right but I can't click on them or use any of the shortcuts to change workspace.

AstronomyDomine
July 31st, 2008, 10:11 PM
Download to desktop:

http://sourceforge.net/tracker/download.php?group_id=69596&atid=525126&file_id=275579&aid=1949610

http://internap.dl.sourceforge.net/sourceforge/linuxwacom/linuxwacom-0.7.9-11.tar.bz2


sudo rmmod wacom
cd ~/Desktop
tar -xf linuxwacom-0.7.9-11.tar.bz2
cd linuxwacom-0.7.9-11
patch -p1 < ~/Desktop/unified-patch-w-eraser_k22-k24.txt
sudo apt-get update
sudo apt-get install linux-headers-`uname -r` build-essential x11proto-core-dev libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libx11-dev x11proto-xext-dev libxext-dev libxi-dev linux-libc-dev libc6-dev libncurses5-dev xserver-xorg-dev tk-dev tcl-dev tcl8.4-dev tk8.4-dev libncurses5-dev xserver-xorg-dev -y
./configure --enable-wacom
make
sudo make install
sudo rm /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko
sudo cp src/2.6.24/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko
sudo depmod -ae
sudo modprobe wacom
gksudo gedit /etc/X11/xorg.conf



Section "Module"
Load "glx"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
InputDevice "Synaptics Touchpad"
InputDevice "TabletPCStylus"
InputDevice "TabletPCStylus2"
InputDevice "TabletPCStylus3"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "stylus"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
Option "Button2" "3" # make side-switch a right button
# Option "TopX" "225"
# Option "TopY" "122"
# Option "BottomX" "26365"
# Option "BottomY" "16488"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus2"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "stylus"
Option "SendCoreEvents" "true
Option "Device" "/dev/input/by-path/pci-0000:00:14.5-usb-0:2:1.1-event-"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus3"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "eraser"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
EndSection


Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Option "RandRRotation" "on"
Driver "fglrx"
BusID "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection


Reboot or restart X. Post with results. :)

Edit: All credit goes to Andrew Zappacky who not only wrote the TabletPC kernel-level code, but also guided me through setting it up, step by step.

fbdelivers
August 1st, 2008, 01:27 AM
Reboot or restart X. Post with results. :)

Edit: All credit goes to Andrew Zappacky. He coded the Tablet PC driver from scratch.

I just gave it a shot - and when I rebooted the tablet pen no longer worked. I went back trough your steps and noticed the following.



patch -pl < ~/Desktop/unified-patch-w-eraser_k22-k24.txt
patch: **** strip count l is not a number


I'll double check to see what I did wrong.

Update - I just noticed that wacom module didn't load so something must have gone wrong when booting.

AstronomyDomine
August 1st, 2008, 08:04 AM
That should be patch -p1 (one) not -pl. Let me know if there are any other problems.

fbdelivers
August 1st, 2008, 05:59 PM
That should be patch -p1 (one) not -pl. Let me know if there are any other problems.

I'm an idiot :)

The patch works great! Xjournal / gimp all work with no problem. Thank you thank you thank you!

Your steps worked fine.

pluckster
August 1st, 2008, 07:59 PM
Anyone played around with the media buttons on the screen? I know a couple work (as in are recognized) but I can't get some of them to work. Is this something we'll just have to live with?

thegnark
August 1st, 2008, 08:13 PM
Anyone played around with the media buttons on the screen? I know a couple work (as in are recognized) but I can't get some of them to work. Is this something we'll just have to live with?

No real answer for you, but I thought I'd toss in some info about it that might help someone else debug the situation:

To get them to work in Vista, you have to install special HP software (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=ob-61528-1&lang=en&cc=us&idx=3&mode=4&). It seems to launch some hard-coded locations... which stinks, but fortunately people have worked around this by replacing the EXEs with ones that run a simple batch files... follow the thread (http://forum.tabletpcreview.com/showthread.php?t=18651&page=2) on it...

corwinspyre
August 2nd, 2008, 01:47 AM
Anyone played around with the media buttons on the screen? I know a couple work (as in are recognized) but I can't get some of them to work. Is this something we'll just have to live with?

do you mean the play, stop, next, and previous buttons? they work in totem, rhythbox, and exaile (the only media players i've tried).

on another note, i've been working on the remote but haven't had much luck yet.

pluckster
August 2nd, 2008, 08:18 AM
do you mean the play, stop, next, and previous buttons? they work in totem, rhythbox, and exaile (the only media players i've tried).

on another note, i've been working on the remote but haven't had much luck yet.

No I mean the other four buttons on that corner; DVD, quicklaunch, rotate and that gear one. The DVD and quicklaunch ones work while the other two don't (At least I think its those two, I know two don't work).

Funk Phenomena
August 2nd, 2008, 06:21 PM
Hi AstronomyDomine, what do we do with those two files and code listed on post #139? Or anyone else that knows...??

Thanks to everyone here and the efforts you've put towards this project. It is so nice to be able to put Ubuntu 64 on this tablet. I also tried the Fedora 9 route with no success, it hung on trying to recognize the processor...

fbdelivers
August 2nd, 2008, 07:58 PM
Hi AstronomyDomine, what do we do with those two files and code listed on post #139? Or anyone else that knows...??

Thanks to everyone here and the efforts you've put towards this project. It is so nice to be able to put Ubuntu 64 on this tablet. I also tried the Fedora 9 route with no success, it hung on trying to recognize the processor...

Follow his step by step in the code section.

BTW cell writer works great with the patch.

When I try to do screen rotation I get the following.



xrandr -o left
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 160 (RANDR)
Minor opcode of failed request: 2 (RRSetScreenConfig)
Serial number of failed request: 12
Current serial number in output stream: 12


I've seen some posts stating that ATI driver doesn't support rotation. Others say one needs to disable just a few settings in the xorg.conf like disabling compiz.

corwinspyre
August 2nd, 2008, 11:39 PM
No I mean the other four buttons on that corner; DVD, quicklaunch, rotate and that gear one. The DVD and quicklaunch ones work while the other two don't (At least I think its those two, I know two don't work).
Oh. I just tried out xbindkeys and got them working. Here are the steps:

1. sudo apt-get install xbindkeys xbindkeys-config
2. xbindkeys --defaults >> ~/.xbindkeysrc
3. xbindkeys-config
4. Hit the "New" button at the bottom.
5. On the right, fill out the name and action with whatever you want, and to bind the button, click on "Get Key" and once a new box/window comes up, hit the button you want to bind.

Unfortunately, it only works for the DVD button and the rotate button, not the other two :(

corwinspyre
August 2nd, 2008, 11:44 PM
Follow his step by step in the code section.

BTW cell writer works great with the patch.

When I try to do screen rotation I get the following.



xrandr -o left
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 160 (RANDR)
Minor opcode of failed request: 2 (RRSetScreenConfig)
Serial number of failed request: 12
Current serial number in output stream: 12


I've seen some posts stating that ATI driver doesn't support rotation. Others say one needs to disable just a few settings in the xorg.conf like disabling compiz.

I haven't messed with rotation myself, but I googled around and came across this post saying it's possible to rotate with compiz (well, you have to restart it): http://forum.compiz-fusion.org/showthread.php?t=2908

Funk Phenomena
August 3rd, 2008, 08:43 AM
Touch and the stylus work. Thanks for putting this all together. In what way can we use the eraser?

So for calibrating the digitizer and touch screen... does it matter the xorg.conf file differs from this one, post 5: http://ubuntuforums.org/showthread.php?p=5469447#post5469447? Specifically, I was hoping to edit the four values as referenced earlier here... but got confused as there is no "touch" in this new config file.

Also, after mucking about in alsamixer, skype, and cheese, I can't get my microphone to work. Skype and cheese take video fine, albeit no audio. Sound output works and I tried playing around with the alsamixer mic settings without any luck. Anyone have suggestions?

gali98
August 5th, 2008, 03:37 AM
I have updated my tutorial (the one Funk references to)
and now everything is working great (the pressure is fixed)
see here:
http://ubuntuforums.org/showthread.php?p=5469447#post5469447

also on the sound I am on the same boat as you.. I think we need to play with the settings in the alsa config file (the one where you put
snd-hda-intel model=hp
or something similar... that may need some work... that is my next project :))

Kory

ownaginatious
August 5th, 2008, 06:31 PM
Okay, here's what I've got working so far after I've been through absolutely everything in this thread.


WORKING:

Temperature Problem - Completely fixed by removing the thermal module from the kernel, as someone posted earlier here.

Sound - Works perfectly through speakers and headphones. Have not tested the microphone.

Webcam - Tested through Cheese after rebooting. Works perfectly, excellent quality and speed.

Wireless - After fixing the kernel, which at the same time upgraded me to the .20 version, wireless appeared. It's kind of slow to connect, but works fine when it does. This may be because I have a WPA secured network.

SORT OF WORKING


Tablet - Almost working. Active digitizer works properly and seems to be automatically calibrated. Eraser isn't really recognized as an eraser. Seems to do the exact same thing as the other end. Also, pressure sensitivity doesn't seem to work when I tried it in GIMP. The pressure seems to be either full, or non-existent, nothing in between. Pressure-operated digitizer is completely uncalibrated, but at least works.

STILL BROKEN

Standby - Computer is able to go to sleep, but when it awakens, the display forgets to turn back on.

STUFF I HAVEN'T GOTTEN TO YET

Pretty much all the buttons - I'm assuming this is exactly the same as the tx2000. I'll work on it later.

- In conclusion, it looks like almost everything in the computer works :). Only a bit further to go before we can tell Vista to kiss our asses.

thegnark
August 5th, 2008, 07:25 PM
I just want to reiterate that the notion that the "temperature problem" is fixed is a misnomer... We've really only got a workaround... truth is that the CPU doesn't scale and the fans blow at full 100% of the time

We're still in need of a kernel fix that actually recognizes and correctly controls the hardware

chees
August 5th, 2008, 08:43 PM
Well, with the kernel fix, the computer does regain some control of the fan, as well as all of the other hardware. The only problem is that it can no longer tell when to increase fan speed, unless the motherboard can handle that regardless of the operating system. Right now it's stuck somewhere around normal speed. Definitely not 100% though. I'm assuming that the computer still cannot do CPU scaling.

By the way, has anyone noticed the computer completely locking up when using GIMP with the stylus? Maybe this is a result of the computer lacking any control of the fan, and thus overheating.

pluckster
August 10th, 2008, 07:55 AM
Download to desktop:

http://sourceforge.net/tracker/download.php?group_id=69596&atid=525126&file_id=275579&aid=1949610

http://internap.dl.sourceforge.net/sourceforge/linuxwacom/linuxwacom-0.7.9-11.tar.bz2


sudo rmmod wacom
cd ~/Desktop
tar -xf linuxwacom-0.7.9-11.tar.bz2
cd linuxwacom-0.7.9-11
patch -p1 < ~/Desktop/unified-patch-w-eraser_k22-k24.txt
sudo apt-get update
sudo apt-get install linux-headers-`uname -r` build-essential x11proto-core-dev libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libx11-dev x11proto-xext-dev libxext-dev libxi-dev linux-libc-dev libc6-dev libncurses5-dev xserver-xorg-dev tk-dev tcl-dev tcl8.4-dev tk8.4-dev libncurses5-dev xserver-xorg-dev -y
./configure --enable-wacom
make
sudo make install
sudo rm /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko
sudo cp src/2.6.24/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko
sudo depmod -ae
sudo modprobe wacom
gksudo gedit /etc/X11/xorg.conf



Section "Module"
Load "glx"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
InputDevice "Synaptics Touchpad"
InputDevice "TabletPCStylus"
InputDevice "TabletPCStylus2"
InputDevice "TabletPCStylus3"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "stylus"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
Option "Button2" "3" # make side-switch a right button
# Option "TopX" "225"
# Option "TopY" "122"
# Option "BottomX" "26365"
# Option "BottomY" "16488"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus2"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "stylus"
Option "SendCoreEvents" "true
Option "Device" "/dev/input/by-path/pci-0000:00:14.5-usb-0:2:1.1-event-"
EndSection

Section "InputDevice"
Identifier "TabletPCStylus3"
Driver "wacom"
Option "ForceDevice" "ISDV4"
Option "Type" "eraser"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/by-id/usb-Tablet_ISD-V4-event-mouse"
EndSection


Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Option "RandRRotation" "on"
Driver "fglrx"
BusID "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection


Reboot or restart X. Post with results. :)

Edit: All credit goes to Andrew Zappacky who not only wrote the TabletPC kernel-level code, but also guided me through setting it up, step by step.

Seems to work for me. The sensitivity is a little sensitive(god that sounds stupid) but it does work in GIMP and such, you just have to make sure you enable and configure it.

On a side note your xorg is a bit different from mine. You seem to have a lot of stuff referencing ATI. Thought maybe that's why my rotation wasn't working.

sandlidl
August 10th, 2008, 08:46 AM
Ok, first of all, thanks to everyone for clearing up all the problems. I only just purchased the tx2500 a couple days ago and a lot of the problems are ironed out thanks to you!

However, I'm still running into this problem that I can't get the pointer to line up with the pen. So I'm going to mess around with the xorg.conf to try to see if I can make it work myself, but if someone has a more informed method, I would really appreciate it.

This is my first experience with wacom so forgive me if I sound green.

sandlidl
August 10th, 2008, 01:33 PM
Ok, nevermind. I just found another place that specified that all the Wacom info had to be placed BEFORE any Synaptics information in the Xorg.conf file. So I moved everything around and now I have a working wacom! Works great too!

Maybe this information will help someone else with the same problem.

gali98
August 10th, 2008, 06:46 PM
pluckster, What model laptop do you have?
If you have a tx2000 series then don't worry about ati...
tx2000 series has nvidia and tx2500 has ati.
If you have a tx2000 (it may even work for tx2500) go here to get rotation working:
http://mirosol.kapsi.fi/tx2020/tx2000howto.htm
Cheers :)
Kory

pluckster
August 11th, 2008, 03:17 AM
Nah I've got a tz2524ca so it is ATI. I tried some of the stuff in that page that I was hoping would work but the suspend didn't seem to work to well for me. Anyone else tried it?

fbdelivers
August 11th, 2008, 05:14 AM
This is a side note on a couple of statements earlier.

Screen Protector - Recommendations?

Thanks!

tC_Crazy
August 11th, 2008, 05:13 PM
Wow, I go away from this thread for a week or two and it nearly doubles! OK, well I'm glad that there's been some progress on the digitizer part. I'm going to have to try that when I get some free time (if ever!). I think it's important to note that 32-bit Ubuntu does work (at least for me... dual-booting with 32-bit Vista Home Premium btw).

fbdelivers,
I'm rockin a Photodon.com anti-glare (they have a fitted size for the tx2500!). It is working very well for me. However, you may have a personal preference for anti-glare vs. clear. They have both for similar prices. I was hoping the anti-glare would help with the reflections, and it did. It seems to diffuse reflections a lot, but the screen is pretty much useless outdoors in direct sunlight. Check out their site, the protectors are cheap (under $11 each!).

kg6gfq
August 12th, 2008, 07:05 AM
Just opened my tx2500 yesterday, finished all the howtos this afternoon, and everything that has a documented fix seems to work! Thanks so much to everyone who's been working on this!

I tinkered with the screen rotation, and apparently xrandr doesn't work properly with the fglrx (proprietary ATI) driver. I expected it to work with the (open source) Radeon or ATI drivers as it did on my previous laptop, but apparently the card is from a newer series and therefore won't work with either of those. There's a new oss driver in development called RadeonHD that ought to support the newer cards, but I haven't had a chance to properly look into it yet.

A while back I read something that might help with the two extra buttons on the screen that aren't working right now. I'll try to hunt down the howto for that also.

I did discover that aticonfig allows the use of multiple monitors, though it does something strange to the calibration of the wacom stylus.

Thanks again to everyone who's posted here!

WACOMalt
August 19th, 2008, 12:21 AM
Hey there, and thanks everyone who is putting in their effort to make everything run smoothly,

I am having trouble with my wireless still though. I followed thegnark's guide, and the wireless light neither turns blue, nor can I browse any wireless access points.

my Ethernet works fine though.

wireless is the main thing I want working.

so to summarize:

Not working for me are:
-wireless
-the touch screen/digitizer
-the quick launch buttons
-thumbprint reader
-battery information (ubuntu sees it as always on AC power)
-screen brightness control (using the addable panel control)

Working:
-touchpad, including scroll areas
-graphics driver
-sound output, and the volume/mute buttons (mute doesn't turn orange -though)
-dvd drive (reading)
-usb devices
-camera, using cheese. (Havent tried in skype yet)

Not tested yet:
-bluetooth
-dvd drive writing
-line in and spdif

If someone could contact me who can help me get through some of this stuff. I am fairly used to linux, this is about my 5th distro and setup, but I still could use some help.

If we could talk over and instant messenger, that would be the best. Here are my contact infos

AIM: wacomalt
YIM: wacomalt
MSN: wacomalt@gmail.com
skype: wacomalt
googletalk: wacomalt@gmail.com

please, if you think you can help, contact me!

thegnark
August 19th, 2008, 12:30 AM
Things that you should be able to get working for sure (there may be others) are:

wireless
digitizer
battery indicator (it drops like a rock due to no cpu scaling, but hey, it works!)

hit up the link in my sig and see if that's any help

WACOMalt
August 19th, 2008, 06:13 PM
thegnark, your tutorial is th eone I tried. (great tutorial btw, it just didnt work out for me)

in fact, following your tutorial is the only thing I have done so far. Were there any other methods for getting the wireless to work? Or what can I test to help find the problem?

thegnark
August 19th, 2008, 06:33 PM
What the tutorial does to get wireless working, is enable hardy-proposed, which updated the driver to a newer less-broken one. It seems that those proposed updates have been pushed to the standard repos, and therefore hardy-proposed contains newer (possibly broken?) packages. The only thing I can think of off the top of my head is to manually downgrade linux-restricted-modules (I assume this is the package that provides the wl driver) to 2.6.24-20 and see if that works. If so, we can skip Step 3 in the future. I can do some extra testing tonight and see what I turn up.

Can you report which version of linux-restricted-modules-common you're using? If it's -21, right-click it, switch to the Versions tab and downgrade from there. I can give more detailed intsructions when I'm next to a power outlet (I wish ACPI and CPU scaling was correctly working :()

WACOMalt
August 19th, 2008, 07:19 PM
...Can you report which version of linux-restricted-modules-common you're using? If it's -21, right-click it, switch to the Versions tab and downgrade from there...

How do I check which version I am running? :confused: sorry, still fairly new to this stuff...

EDIT: nm, in the synaptics package manager, it lists 2.6.24.14-21.47 which is the newest reported version as well. I do not see 2.6.24-20 as an option on the versions tab.

corwinspyre
August 19th, 2008, 11:50 PM
your fingerprint reader should be working out of the box, so to speak

gali98
August 20th, 2008, 12:24 AM
your fingerprint reader should be working out of the box, so to speak

How so?

You would first need to install fprint and all.
It is a very new project.. doesn't always work.
Kory

corwinspyre
August 20th, 2008, 02:35 AM
How so?

You would first need to install fprint and all.
It is a very new project.. doesn't always work.
Kory
fprint is just a library of APIs to access it. libfprint is used by some fingerprint programs but not all.

the only problem is there really isn't any useful programs that use fingerprints, and it isn't integrated into the gnome or gdn

thegnark
August 20th, 2008, 04:12 AM
How do I check which version I am running? :confused: sorry, still fairly new to this stuff...

EDIT: nm, in the synaptics package manager, it lists 2.6.24.14-21.47 which is the newest reported version as well. I do not see 2.6.24-20 as an option on the versions tab.

Sorry, take a look at linux-restricted-modules-generic. I'm at 2.6.24.20.22, which should now be part of the standard repos... hardy-proposed contains 2.6.24.21.23. I'll update and report back what happens. In the meantime, you could manually downgrade and see if that helps.

EDIT: I'm fully updated with hardy-proposed enabled and wireless still works. Can you also confirm that "wl" is checked and "In use" in System->Administration->Hardware Drivers?

WACOMalt
August 20th, 2008, 04:34 AM
... hardy-proposed contains 2.6.24.21.23...

...Can you also confirm that "wl" is checked and "In use"...?

For some reason, in the properties on synaptics package manager, It says the current hardy proposed version is 2.6.24.14-21.47. This is different than yours reports (2.6.24.21.23). am I looking in the right place? Could my repositories be added incorrectly?
EDIT: nm, I just now noted that you told me to check a different package this time :P and my version for generic is 2.6.24.21.23, so same as yours. Still no luck though...

Also "wl" is check and in use in my hardware driver thingy.

This very odd... Where are you checking your version number? I have just been looking in synaptic's package properties. (never mind :P)

EDIT: thegnark, can you please contact me? my infos are:
AIM: wacomalt
YIM: WACOMalt
MSN: wacomalt@gmail.com
gtalk: wacomalt@gmail.com
skype: wacomalt
email: wacomalt@gmail.com

martinjochimsen
August 20th, 2008, 10:55 AM
Hi

I have been following this thread for some time now. I just bought a tx2590oe a week ago, and I too have had ALL the same problems as you guys. Many things are working now but I still have a problem with my wireless. I followed the guide from tC_Crazy (#80) and my wireless card (BCM4322) seems to work. It finds my wireless router, but when it tries to connect it just keeps on searching and searching and searching and finally it doesn't connect. I've got two other laptops in the house which connects to the router without any problems, so it must be something with my laptop.
Has anybody had the same problem, and is there anything I can do?

best regards
Martin

gali98
August 20th, 2008, 05:50 PM
First... Does this router have encryption? (WEP WPA etc....)
Have you done a soft reset on the router? (Unplug it, replug it)
Are you sure the wireless is on?
If you still have Windows on this laptop can you connect with it?
When It "finds" the router, does is show a strong signal strength?
Are you up to date? (on updates with update manager)
What program are you using to connect? The default GNOME Network Manager?

Just some things you might want to check.

If you can test the laptop on another router. The problem may be fixed by updating the firmware of the router.

Kory

martinjochimsen
August 20th, 2008, 11:45 PM
Hi

Good questions to answer:

First... Does this router have encryption? (WEP WPA etc....)
- no

Have you done a soft reset on the router? (Unplug it, replug it)
- yes

Are you sure the wireless is on?
- well, the blue "wireless-light" has turned blue after I went through the guide. It was orange before. We don't live close to other houses, so my "linksys" was the only name that turned up, so I guess it's on

If you still have Windows on this laptop can you connect with it?
- yes. I have Vista, and it connects without problems

When It "finds" the router, does is show a strong signal strength?
- yes. Almost 75%

Are you up to date? (on updates with update manager)
- yes

What program are you using to connect? The default GNOME Network Manager?
-yes

I went to my brothers house tonight to test if it could connect there...but it couldn't.
I don't think it's the router. I have tried with two other laptops (and my own Vista) and they connect perfect.
It's a stupid problem, and the biggest problem is probably sitting in front of the laptop!!!! :-)
I just can't figure it out.

Martin

martinjochimsen
August 20th, 2008, 11:48 PM
...and by the way. When the laptop tries to connect nothing else is working. Everything hangs!!!!!

Martin

WACOMalt
August 21st, 2008, 01:45 AM
Hmm, I still am having no luck, it seems all of my packages are the propper version (or at least the same as thegnark's and his are working) my blue wireless light doesn't even come on. is there some command I can run to dump some info that might help me/you-guys figure this out?

AstronomyDomine
August 21st, 2008, 03:22 PM
WACOMalt: The wireless light on the front of the computer (to the far right of the power switch) isn't even on? It's not even red? Does it work from Vista? What does "lspci | grep Network" return?

martinjochimsen: First run iwconfig to determine what network interface your wireless netowrk is on. All of the others should say "no wireless extensions" then there should be one that says "IEEE 802.11" etc.

Once you know your wireless interface (mine is eth1 so replace eth1 with yours from now on), try connecting manually with iwconfig. Run "sudo iwconfig eth1 essid "NETWORK"" Of coruse, replace "NETWORK" with your essid, and don't use any quotes. Run "iwconfig" every once in a while after that until you can see that it is connected to the network (It should list your network as the essid). Then finally run "sudo dhclient eth1" to receive an IP from your router. Hopefully that should work. Post with results.

WACOMalt
August 21st, 2008, 09:12 PM
AstronomyDomine: sorry, the light is on, just it is orange and not blue.

I also ran the iwconfig command to see if that listed anything useful. i got:


lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Nickname:""
Access Point: Not-Associated
Link Quality:5 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid crypt:0 invalid misc:0
so my wireless is recognized to a point so I decided to try what you told martinjochimsen to do, and I got


$ sudo iwconfig eth1 essid WACOMaltWireless
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth1 ; Invalid argument.

also a question for those of you with working wireless, are you able to toggle it with the wireless slide-button on the front? Just wondering, I use that a lot as I fly quite a bit.

martinjochimsen
August 23rd, 2008, 12:29 AM
Hi Astronomy

Thanks for Your input.
Before I saw Your reply I followed a brand new guide only 1 or 2 days old
http://ubuntuforums.org/showthread.php?t=896713
Everything is working perfect now.

Best regards
Martin

corwinspyre
August 23rd, 2008, 02:23 PM
AstronomyDomine: sorry, the light is on, just it is orange and not blue.

I also ran the iwconfig command to see if that listed anything useful. i got:


lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Nickname:""
Access Point: Not-Associated
Link Quality:5 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid crypt:0 invalid misc:0
so my wireless is recognized to a point so I decided to try what you told martinjochimsen to do, and I got


$ sudo iwconfig eth1 essid WACOMaltWireless
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth1 ; Invalid argument.

also a question for those of you with working wireless, are you able to toggle it with the wireless slide-button on the front? Just wondering, I use that a lot as I fly quite a bit.

i have the abg wireless version, but yep, it works perfectly for me (meaning the light even turns red when it's off).

were_wolf
August 23rd, 2008, 11:16 PM
fedora 9 works great with the tx2500.
-touchscreen works very well
-stylus works very well
-rotation works but with cmd line
-wireless works very well with ndiswrapper
-finger printer not tested
-camera not tested
-buttons not tested

thegnark
August 24th, 2008, 05:05 AM
Has anyone seen the thread on AMD "Puma" Laptops and C-states (http://ubuntuforums.org/showthread.php?t=844754)?

It seems that 2.6.26 better supports the new chipsets. I compiled and booted the new kernel and immediately noticed a difference in heat output (no more 100% fan either). I hadn't bothered to get the graphics and touchscreen working, but I'm sure it would be trivial.

Looks like we should just have to wait until Intrepid Ibex with a newer kernel (currently 2.6.27 (http://blog.phunnypharm.org/2008/08/intrepid-ibex-810-moves-to-2627.html)) to expect easy configuration.

thegnark
August 24th, 2008, 05:09 AM
fedora 9 works great with the tx2500.

That's strange, because I tried Fedora 9 and just like Ubuntu Hardy, I couldn't boot by default.

vokesalex
August 25th, 2008, 11:08 AM
I read the "AMD "Puma" Laptops and C-states" thread too.

I tried Intrepid Kubuntu Alpha 2, as I noticed that it had the 2.6.26 kernel. There were a few odd things after the install had finished and it booted for the first time. The x server didn't seem to want to start but flickered back and forward between a totally black screen and the terminal based login. Once this had settled down I managed to get it to stay in terminal mode and did an apt-get dist-upgrade and then the graphical logon interface would then start properly the next boot.

I immediately noticed that the fans were quieter and there was a battery icon at the bottom of the KDE "taskbar" which wasn't present in Hardy. Hovering my mouse over the battery icon gave me some information about current battery life and power saving but I wasn't sure whether it was accurate as the CPU frequencies were blank. Remaining battery time started at 4hrs, then dropped to 15 minutes and then up to 1hr 40 mins.

I managed to get the touchscreen working with the same instructions as for Hardy. The main problem I had was that intrepid uses the newest version of xserver and there is currently no ATI driver that supports it that I could find.

Still looks promising for the final release of Intrepid...

morbyte
August 25th, 2008, 12:01 PM
first things first: i have a HP tx2550eg.

after playing around with distros and configuration i want to add the following:

ubuntu intrepid alpha (1,2,3, dunno) worked out of the box. yet i installed debian lenny beta 2 with acpi=off. but for the modprobe stuff i was playing with it doesnt matter afaik. so here are my results:

blacklist thermal is not needed. i added "options thermal nocrt=1" to /etc/modprobe.d/options . this was enough to switch off the emergency shutdown.

furthermore i want to post my /proc/acpi/thermal_zone information with you:



# cat /proc/acpi/thermal_zone/THRM/*
<setting not supported>
<polling disabled>
state: ok
temperature: 64 C
critical (S5): -273 C <disabled>
hot (S4): 105 C <disabled>
passive: 95 C: tc1=2 tc2=3 tsp=30 devices=CPU0 CPU1

# cat /sys/module/thermal/parameters/act
0
# cat /sys/module/thermal/parameters/crt
0
# cat /sys/module/thermal/parameters/psv
0
# cat /sys/module/thermal/parameters/tzp
0

jambaiscool
August 25th, 2008, 02:23 PM
Hi,

I'm going to uni next month and I'm going to get a laptop before I go. I came across the tx2520ea (which I believe is almost (if not completely) identical to the tx2500z) and really liked the look of it. Then I searched "ubuntu tx2500" and came across a handfull of horror stories about linux on this laptop. :(

anyway, from reading this thread the whole way through things are starting to look a bit more positive. I really like the look of the laptop (small, fairly powerful, tablet, good price), so do you guys think it's worthwhile getting despite the issues?

hopefully everything will be fine for intrepid? and i can live with a few hacks until then.

cheers,

jamie

thegnark
August 25th, 2008, 02:55 PM
Just so everyone is clear, tx2500 is the generic name for any tx25?? model. We could more clearly say "tx2500 series", but the idea is the same.

And here's my take on your situation: If (1) your primary OS is Ubuntu, (2) comfortable with manual tweaking until Intrepid (and who knows - even maybe after Intrepid is out), and (3) planning on having the laptop plugged in most of the time, then I say go for it.

The battery life is just not acceptable IMO right now to be mobile constantly. I personally don't mind the hacks... but at the same time, I'm still dual-booting another OS until battery life is better.

isachan
August 25th, 2008, 02:57 PM
jambaiscool,
Other than the initial thermal problem, many things are very Linux friendly on TX2500 series. If you can live with no CPU scaling, some tablet function inconvenience due to the state of driver development, suspend / hibernate, and power management issues.

I haven't tried some other things, like screen rotation, compile older digitizer driver to get the inking going.

You should be getting it going with acpi=off boot option and after the boot, adding "options thermal nocrt=1" to /etc/modprobe.d/options as per morbyte's post. That's what I have got it going without completely removing the thermal module.

I like especially after the last ATI driver update to version 8.6, 720p High Def contents are super fluid.

Still this machine needs a lot of software updates, and that takes time and patience. I'm in a waiting mode for a while.

isachan
August 25th, 2008, 03:10 PM
Has the new wl driver in proposed repository released yet ?

I'm still waiting for the updated wl driver to come down to the release repository from proposed repository.

Right now, I can scan WLAN routers, but I can't really connect. I have to "sudo kwifimanager" to somehow connect to my router but it just flashes back and forth between "out of range" and "good link". Never stable. When I launch kwifimanager from GUI, everything is crossed out and I can't do anything. My WEP setting is good, and eth1 as the interface.

Wicd can see my router but can't connect to it either. My WEP setting is good, and eth1 as the interface.

How do I check the version for drivers ? Especially how do I compare what I have right now and the one in proposed / testing repository ?

I'm avoiding ndiswrapper as much as possible.

Help !

jambaiscool
August 25th, 2008, 07:26 PM
thanks for the advice. I'm fairly competent with linux so I'll be able to handle a bit of hacking to get stuff working. I'll probably be getting the tx2520ea within a couple of weeks, so when I do I'll let yous know how it works. :)

martinjochimsen
August 27th, 2008, 09:38 AM
Hi isachan

Try to use this guide for your wireless http://ubuntuforums.org/showthread.php?t=896713 . I had some of the same problems (with wl), but now it works PERFECT!!!

Martin :-)

martinjochimsen
August 27th, 2008, 09:46 AM
...and I'm on a Ubuntu 8.04.1 (tx2590)

Martin

thegnark
August 29th, 2008, 02:38 PM
https://bugs.launchpad.net/@@/person Leann Ogasawara (https://bugs.launchpad.net/%7Eleannogasawara) wrote 11 hours ago: (permalink) (https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/231534/comments/19)
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.



https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/231534/comments/19

martinjochimsen
August 29th, 2008, 07:46 PM
Great. Thanks for the update. I will try it next week.

Martin :-)

_francis
September 2nd, 2008, 09:28 PM
this is a review of my first days with my new hp tx2550eg tablet

getting ubuntu up and running:

i read thegnark's howto in this post (page 12), downloaded the daily build of 8.04.1 (august 28th) and tried to install ubuntu - without success due to "Error. Kernel panicking" (don't remember the exact message). after a lot of reading through the post I found that somewhere the boot options noapic and nolapic were mentioned and so I tried once more with the boot options:
acpi=off noapic nolapic

It worked and I installed hardy without any problems, but after starting up I had no wireless nor any wired connection.

another session of flicking through the forum pages followed and somewhere a successful installation with 8.10 alpha 3 is mentioned. I downloaded the daily build of alpha 4 and gave it a try. no success without manipulating the bootoptions, but this time acpi=off alone did it. the installation worked without any problems again and after manipulating the boot options at the first boot I couldn't wait to see the fruits of my work. after logging in my heart nearly stopped when I saw the white screen. I googled the problem, again, and found out about the "white screen of death" I solved this by pressing alt+F2 after login, typing "metacity --replace" and hitting Enter. Voila!
I followed thegnark's guide to get sound work and also added thermal to the blacklist but no success, I cannot boot without changing the bootoptions.
I also tried AstronomyDomine's approach from this post (page 2) to remove the thermal module from the initramfs, but still no success.

Now I just tried the 2.6.27 kernel and it workes without any boot option or modifying the blacklist or initramfs. Wireless device is light blue instead of red and my spirit is up again. only problem is that i cannt see any proprietary drivers listed. in hardy i had proprietary drivers for the ati hd 3200 mobility card and the wl driver. iwconfig is just showing lo and eth0 without wireless extension. i ll try to figure this out tomorrow and maybe install wl manually.

hope the info about the 2.6.27 kernel is useful to some of you.

martinjochimsen
September 2nd, 2008, 09:44 PM
Hi _francis

After I blacklisted thermal in /etc/modprobe.d/blacklist I added these 4 lines to /etc/modprobe.d/options

options thermal.act=-1
options thermal.crt=-1
options thermal.nocrt=1
options thermal.psv=-1

So now my /etc/modprobe.d/options looks like this

# Enable double-buffering so gstreamer et. al. work
options quickcam compatible=2

# Default hostap to managed mode
options hostap_pci iw_mode=2
options hostap_cs iw_mode=2
options thermal.act=-1
options thermal.crt=-1
options thermal.nocrt=1
options thermal.psv=-1

and I can boot up without nolapi noapi acpi=off
I'm still useing kernel 2.6-24-21-generic

Martin :-)

By the way I used this really easy guide for my wireless from mike_1
http://ubuntuforums.org/showthread.php?t=896713

jambaiscool
September 5th, 2008, 12:41 AM
has anyone tried alpha 5 then?
EDIT: Seems like the alpha 5 wasn't released today? Am I being an idiot?

Also, I understand that battery life is rubbish at the mo, but how rubbish is it? In hours? (or even minutes if they're a more suitable measurement:lolflag:)

WACOMalt
September 5th, 2008, 04:20 AM
Well, sadly minutes IS a better scale. I at most get an hour. Of course I use this computer tot he max all the time. (3d redering, Visual Effects, gaming, video editing etc...)

I would say maybe an hour and a half if you are only listening to music or something.

btw, I got the 8 cell battery, the default is 6 cell.

zujenbe
September 5th, 2008, 06:00 PM
hi, im getting sound... but thing isnt quite as loud as it was with windows... anyone else have this too? im wondering if the sound is actually only coming out of one speaker...

Afief.h
September 6th, 2008, 10:52 AM
Hello,

I have an HP tx2520ej(the model sold in Israel) and here are my results after installing Ibex Alpha 5:

What works:
Booting without the overheating error(no extra options needed:) simply boot)
Ethernet(didn't work in 8.04)
Screen resolution detected correctly
Wireless(I see the entry in Network Manager and iwconfig, but I don't have any networks around to test with. the light is blue)
The sound buttons(sound-, mute, sound+)
Memory card reader(tested with SD card)

What does not work:
Sound
Touchscreen(not with pen, not with fingers)
Buttons on the screen(DVD, rotate and settings, but that's expected)

Anyhow there are lots of updates out already, perhaps they'll fix some of the stuff here, and I will try the sound fix mentioned in this thread, but does anybody know how to get the touchscreen to work?

Edit: Sorry if there is stuff I haven't tested. If there is anything you'd like me to test please mention it and I'll do my best to test it.

zujenbe
September 6th, 2008, 01:20 PM
http://ubuntuforums.org/showthread.php?t=870640

this will more than likely help u fix ur problem with thouchscreen
gd luck!

martinjochimsen
September 6th, 2008, 01:28 PM
Yes. Follow gali98's (#5 ) guide from the link above. It worked perfect for my tx2590oe.

Martin

zujenbe
September 6th, 2008, 02:42 PM
oh god, im having some more problems now...
i can no longer reboot or shutdown let alone hibernate or standby... up until recently, these two buttons worked fine. now whenever i try, i just get a blackscreen... which proceeds to absolutely nothing...
anyone any ideas?

lord_phantom
September 6th, 2008, 09:39 PM
Hi!

First of all - thanks to all in this thread, especially Pluckster for describing his problems and saying that 64-bit version fixed his all problems. I got my tx2550ew working perfectly on Ubuntu 8.04.1 64-bit.

Now I decided to upgrade from 8.04.1 to 8.10 alpha5. I've encountered a problem. During the configuration of the new packages, suddenly my computer launched the shutdown procedure in the middle of the process. The reason was too high CPU temperature. Now i must finish the whole procedure within the good old terminal.

If someone of you would try this upgrade, I recommend to try boot the kernel with acpi=off. I don't know if this can prevent this crash, but it's worth trying.

Update: My upgrade failed. Fglrx (version from AMD's site) made most problems. Now I'll do a clean install of alpha 5. I'll try tomorrow.

Ps. It was my first post on this forum, also my English isn't good - so sorry for any language mistakes!

Afief.h
September 7th, 2008, 07:53 AM
http://ubuntuforums.org/showthread.php?t=870640

this will more than likely help u fix ur problem with thouchscreen
gd luck!

Thanks, I will try it this afternoon.

Any chance this will be integrated into the default Ubuntu 8.10 or will it have to wait until 9.04?

I got sound to work with the two lines of ALSA configuration, but when using earphones only one phone(left one in my case) works. Anybody encountered this?

martinjochimsen
September 7th, 2008, 08:02 AM
Hi Afief.h

Which two lines did You put into the ALSA conf.?
Did You get the microphones to work?

Martin

Afief.h
September 7th, 2008, 09:20 AM
Hi Afief.h

Which two lines did You put into the ALSA conf.?
Did You get the microphones to work?

Martin

added this to /etc/modprobe.d/alsa-bas :
options snd-hda-intel index=0 model=toshiba position_fix=1

dunno why it appears to be one line now, but I'm not complaining:)

The microphone doesn't seem to work though

isachan
September 7th, 2008, 09:44 AM
Well, I meant to say that make sure the last two lines of /etc/modprobe.d/alsa-base file are as follows:

options snd-cmipci mpu_port=0x330 fm_port=0x388
options snd-hda-intel index=0 model=toshiba position_fix=1

...where this line "options snd-cmipci mpu_port=0x330 fm_port=0x388"
should be already there.

By looking at some posts in the past, I think I have confused some people.

Anyway, Afief.h, try right-clicking the sound icon on the bottom panel, and select the configuration menu. The KMixer config window should show up an look for the screen with a lot of check boxes where you can select which sound channel you can bring up on the volume setting screen.

Check Front, PCM, Headphones, etc., and go back to mixer volume setting and you should be able to crank up the left / right volumes or altogether.

Also, check your headphone plug is all the way in.

I tried 8.10 Alpha 5 just today and that's how I brought up my sound.

Isao

zujenbe
September 8th, 2008, 11:52 AM
hi, what doesnt work on ibex so far? im thinking about upgrading.

Afief.h
September 8th, 2008, 02:52 PM
Well, I meant to say that make sure the last two lines of /etc/modprobe.d/alsa-base file are as follows:

options snd-cmipci mpu_port=0x330 fm_port=0x388
options snd-hda-intel index=0 model=toshiba position_fix=1

...where this line "options snd-cmipci mpu_port=0x330 fm_port=0x388"
should be already there.

By looking at some posts in the past, I think I have confused some people.

Anyway, Afief.h, try right-clicking the sound icon on the bottom panel, and select the configuration menu. The KMixer config window should show up an look for the screen with a lot of check boxes where you can select which sound channel you can bring up on the volume setting screen.

Check Front, PCM, Headphones, etc., and go back to mixer volume setting and you should be able to crank up the left / right volumes or altogether.

Also, check your headphone plug is all the way in.

I tried 8.10 Alpha 5 just today and that's how I brought up my sound.

Isao

Done that, still only getting sound from one earphone(it works correctly on windows so it's not a hardware problem)

Did you get the touchscreen to work on Alpha5? I followed the guide that was given to me, but couldn't bring it to work(was planning to try again after Ibex release)

zujenbe
September 10th, 2008, 03:02 AM
@WACOMalt

thats very strange, i managed to push 2hrs! i was quite impressed. I think if i had the balls to attempt any acpi changes, i could get it far longer...

by the way, has anyone worked on getting suspend mode fixed? this would be great!

_francis
September 10th, 2008, 09:14 PM
Hi _francis

After I blacklisted thermal in /etc/modprobe.d/blacklist I added these 4 lines to /etc/modprobe.d/options

options thermal.act=-1
options thermal.crt=-1
options thermal.nocrt=1
options thermal.psv=-1

So now my /etc/modprobe.d/options looks like this

# Enable double-buffering so gstreamer et. al. work
options quickcam compatible=2

# Default hostap to managed mode
options hostap_pci iw_mode=2
options hostap_cs iw_mode=2
options thermal.act=-1
options thermal.crt=-1
options thermal.nocrt=1
options thermal.psv=-1

and I can boot up without nolapi noapi acpi=off
I'm still useing kernel 2.6-24-21-generic

Martin :-)

By the way I used this really easy guide for my wireless from mike_1
http://ubuntuforums.org/showthread.php?t=896713

This worked great and I everythings working just fine now - thx!

tC_Crazy
September 11th, 2008, 07:52 PM
Has anyone else had an issue with the 2.6.24-21 kernel/wl and wpa2?
I recently upgraded to that kernel, and it started using the wl driver for wifi (which works great for unprotected networks). However, when attempting to connect to my university's WPA2 network (bypasses slow login screens), and I submit my information the first time, it causes the entire system to lock up and I have to do a manual power-off. I didn't have this problem in 2.6.24-19. Any ideas?

gali98
September 11th, 2008, 11:23 PM
I used the wl driver (on a tx2000 but I think it is the same card...) and connected to a wpa1 ap.... Not sure if that helps you at all.
Oh and I am on the -21 kernel...
Kory

tC_Crazy
September 12th, 2008, 05:53 AM
Thanks, but I'm pretty sure it's a different wireless card (this one is a/b/g/n/BT). I think it's bcm4315 or 2315 or something of that nature... the exact model escapes me.

Not a huge issue for me, just an annoyance. It may be worse for people who utilize WPA2 for their home networks.

phormix
September 12th, 2008, 11:44 PM
What happened to the rest of the posts in this thread? I seem to remember a lot more, and the google cache shows 19+ pages...

Edit:: They just came back. It was stuck with only two pages for awhile... weird.

tx2524ca (tx2500 series).
Ubuntu Hardy 8.04/32bit - kernel 2.6.26.5

- Ethernet: working
- Wireless [BCM4322 802.11a/b/g/n]: b43 doesn't work, ndiswrapper doesn't work, wl (broadcomm closed-source driver) works intermittently
- touchpad: working
- sound [Azalia]: working (Intel HD Audio /w Realtek driver, options model=toshiba)
- bluetooth: working
- CPU scaling: not working
- Remote control: not working
- Tablet/digitizer: working (not sure about pressure-sensitivity, no rotation yet)
- graphics [ATI fglrx driver]: working
- media buttons: (volume only)
- webcam: working (v4l2)
- cardreader: working

phormix
September 12th, 2008, 11:46 PM
Has anyone else had an issue with the 2.6.24-21 kernel/wl and wpa2?
I recently upgraded to that kernel, and it started using the wl driver for wifi (which works great for unprotected networks). However, when attempting to connect to my university's WPA2 network (bypasses slow login screens), and I submit my information the first time, it causes the entire system to lock up and I have to do a manual power-off. I didn't have this problem in 2.6.24-19. Any ideas?

On mine when using WL the wireless cuts in out and regularly. It doesn't freeze the system though...

What's your actual card show up as in lspci?

phormix
September 14th, 2008, 09:43 PM
Did anyone manage to get the microphone working on theirs? Sound's fine but I noticed that:

a) No luck with the internal mic at all
b) With external mic, I can turn up the pass-through volume and hear it through the speakers, but get no input when recording.

Also, as some others have mentioned, it seems the max volume is lower in 'nix than in Windows?

kg6gfq
September 21st, 2008, 04:44 PM
I've been running Intrepid for a month or so, and things work pretty well, for the most part.

- Ethernet: Working
- Wireless (the b/g card): Working with wl driver
- touchpad: Working
- sound: Working (except built-in mic)
- CPU scaling: Working (with this howto: http://ubuntuforums.org/showthread.php?t=844754)
- Remote control: not working
- Tablet/digitizer: working (with pressure sensitivity and rotation)
- graphics: working (see below for details
- media buttons: volume works, play/pause/etc work intermittently (though that may be a problem with banshee
- webcam: working
- cardreader: untested
- suspend: nearly working (see below for details)
- hibernate: not working

Graphics issues: I've been using the radeon driver, since fglrx doesn't work with the latest version of X. I can use a second monitor with xinerama, but it doesn't support rotation. I can use rotation but not the second monitor with xrandr, which is unusual because xrandr ought to support the second monitor. When I turn it on using xrandr on the command line or a gui like "Screen Resolution" or grandr, however, the external monitor goes blank. the mouse can move off the builtin screen, but it does not appear on the other monitor. Any ideas on the reason for this?

Suspend issues: The computer suspends fine and wakes fine, but upon waking the builtin keyboard doesn't work. An external USB keyboard works fine, but not the builtin one. I'm going to try changing my xorg.conf to see if it helps.

jubej
September 22nd, 2008, 07:32 PM
Hi kg6gfq!

My laptop: hp tx2510us
OS: Ubuntu Intrepid ibex alpha5 and i have these results:
Kernel: 2.6.27-3

- Ethernet: Working
- Wireless (the b/g card): Working with wl driver
- touchpad: Working
- sound: Working (except built-in mic)
- CPU scaling: Working OOTB its running OnDemand from 500MHz to max :=)
- Remote control: not working
- Tablet/digitizer: not working i dont know how the wacom drivers is not uppdated to the new kernel)? how did u do?
- graphics: working? (I dont have 3d acceleration)
- media buttons: volume works, play/pause/etc work exept the ones on the lcd botton right corner.
- webcam: (Not Working, i dont know how everyone has their cameras working please help)
- cardreader: untested
- suspend: nearly working
- hibernate: not working



How did u get the camera and Tablet/digitizer: working (with pressure sensitivity and rotation) with the new kernel? I have sound when looking movies or listening to music, but in ekiga it seem that it wont recognise the camera or the sound. do u have 3d aceleration?

I tried to install cheese to see if the camera started to work but nothing. any tips here?

By the way ubuntu 8.10 its awsome, i dont have to do the acpi=off or anything everything its great, even the cpu scaling.


i just dont get the other stuff that works for you working for me.

Thnx for any help





lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 11h HyperTransport Configuration (rev 40)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 11h DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 11h Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 11h Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics]
08:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

kg6gfq
September 22nd, 2008, 09:49 PM
Well, I guess I hadn't tested the webcam on the -3 kernel; I'm having issues with it too. I'll tinker with that after updating to the -4 kernel.

Audio in ekiga works fine for me, with the exception of the internal mic which never worked.

To get wacom working again you have to repeat the steps of the tutorial; this seems to be required for each kernel update, unfortunately. I finally got tired of it and threw together a script for the procedure, which I've attached. It ought to work, but if it gives any errors or doesn't work after restarting X you should check the script or just follow the tutorial again: http://ubuntuforums.org/showthread.php?p=5469447#post5469447

Because you have to re-install the driver after each kernel update, you may want to wait until you update to the -4 kernel that just came out. I'm doing that right now, and I'll report back when I've tested it.

Hibernate works if you do "sudo /etc/acpi/hibernate.sh force", but I would like to have a working keyboard after suspend because hibernating (at least that way) is rather slow. I've tried the uswsusp package for hibernate/suspend with no success.

Other issues: Pidgin is segfaulting at startup. Skype is missing a .so file, I'm taking a look at that now.

I must agree that Intrepid is great!

gali98
September 23rd, 2008, 01:37 AM
k6kfq
Nice script. When Intrepid comes out, I think I am going to put together a script that does the same thing, but has troubleshooting info and stuff. It will help with tutorial time and and when people come to the thread they will already have the info I need to help them.
Kory

jubej
September 23rd, 2008, 03:22 AM
hi kg6gfq

I run the script and it ended with no errors. but still i did not work. here is what i did:

downloaded the script made it executable. and then in the terminal i typed:
./wacominstall.sh

everything whent oki. and in the tutorial its said that after run the modprobe wacom
ill get the touch screen and digitizer to work but uncalibrated. but nothing happen.

another thing i did was to upgrade to de kernel 2.6.27-4 and then restarted and then run the script again and it seems to work bacause everything runs until everything finished and im again at the terminal.with no errors, but still i cant get the mouse to move with my fingeer or the pen.

i dont know what im doing wrong, please help.

here I attached the terminal output and my xorg.conf

but as I understand even with the xorg not configured Ill still be able to move the cursor right?

gali98
September 23rd, 2008, 03:41 AM
As far as I was aware, it does not work on the .27 kernel yet. Am I wrong?
I simply tried it on the livecd (did not want another patition to worry about) and I could insmod it, but it did nothing.... Like you are describing... Has anybody got it working on the .27 kernel?
Kory

jubej
September 23rd, 2008, 12:28 PM
Hello!

gali im happy to say that its working in my ubuntu 8.10 kernel .27!!! yeahhhh

its really good i just run the script and then editet the xorg like in the tutorual then restarted the X-server and it work really good.

TNX kg6gfq for the help.

But I wonder somthing:

its working with the digitizer really good I did not have to calibrate or anything. but It wont move with the finger. is it somthing in the xorg.conf that i did wrong? maybe in the touch section?

Another thing how did you get skype to work on ubuntu 8.10 x64? i tryed to download and install from the webpage and its says it the wrong architecture.

Anyway thnx, and the camera its working with cheese :) but not with ekika :(

kg6gfq
September 23rd, 2008, 04:39 PM
I've got the digitizer working on the .27-4 kernel with no trouble. I don't normally enable the touchscreen, so that may not work... jubej, are you sure you have the devices set correctly in xorg.conf?

The camera is working in the .27-4 kernel, no idea what the issue was in -3. In ekiga, you should make sure it's set to use v4l2 rather than v4l.

gali, that script sounds like a good idea. I would do something similar, but I don't really know enough to make it output the correct troubleshooting info.

I still can't figure out why the keyboard stops responding after returning from suspend.

There is currently no 3d acceleration for us in 8.10 because, though we now have an fglrx driver, it doesn't seem to work. Anyone know if this will be fixed soon?

Skype's web site does not have a 64bit version for download, it seems. Instead, add the medibuntu repositories (https://help.ubuntu.com/community/Medibuntu). Right now, though, there seems to be a problem either with that package or with a supporting library.

gali98
September 23rd, 2008, 11:33 PM
jubej just upload your xorg.conf and do the command:
ls -lR /dev/input

and post its output as well and I can help you get it straightened out...
Anything special to get the 27 kernel to work? Also what folder does the module build in? (2.6.24 or 2.6.26)
Wow that stinks about the video driver... I'm sure it will get fixed sooner or later, hopefully sooner.

Kory

jubej
September 24th, 2008, 07:26 AM
hi Gali 98!!

moving the mouse with the pen works. the thing that dont work is moving the mouse with the finger, I supose that it is the touchscreen right? because moving the mouse with the mouse is the stylus option right?

what about the eraser how does it work? i writed something with the pen and then I turn it around like you do when you have a eraser, I tryed to erase but nothing happen. Or maybe Im using the eraser in a very stupid way?

here in this tarfile is my xorg.txt and a text file with the
ls -lR /dev/input.


Another thing i think about is this:


Does your screen get really warm at the right side of the lcd screen? if I put my hand on the right side i feel that its really warm, while the others sides are cold. is that normal? I dont remember feeling it this warm when i bougth it with vista? is it something that linux make the lcd really warm? is it dangerous?

thnx for any help.

gali98
September 24th, 2008, 11:40 PM
Okay one more question... What model laptop do you have?
Do you have restricted drivers(yes that was two:))
Kory

jubej
September 25th, 2008, 10:01 AM
hi
My laptop is a hp tx2510us
OS: Ubuntu Intrepid ibex alpha5 and i have these results:
Kernel: 2.6.27-3

by the way did you feel that the right side of the lcd panel is really hot? is that normal?

gali98
September 25th, 2008, 11:41 PM
Yes mine gets relatively hot.... But I am pretty sure it did that in vista too..
You're probably just on ubuntu longer :)

Okay after looking at your xorg.conf for a very long time, I finally found the one little mistake..
you need to change
Option "Device" "/dev/input/by-path/pci-0000:00:14.5-usb-0:2:1.1-event"
under touch to:
Option "Device" "/dev/input/by-path/pci-0000:00:14.5-usb-0:2:1.1-event-"

(the "-" at the end) and that should work.
Also what linux wacom version do you have. Another thing to check is to run wacomcpl and see if touch shows up there.
Kory

martinjochimsen
September 25th, 2008, 11:54 PM
Hi

I dualboot with Ubuntu 8.04.1 and Vista on my tx2590. In Vista there is a small "onscreen"-keyboard which I can use with either the stylus or my finger. I think I once saw a program for a similar keyboard for Ubuntu, but now I can't remember the name or find anything about such a program.
Does anybody now the name for that kind of app or am I just make stuff up in my sick brain!!!

Martin :-)

martinjochimsen
September 26th, 2008, 12:01 AM
...nevermind!!!
Ofcourse right after asking I find this thread ( http://ubuntuforums.org/showthread.php?t=236405) an "onBoard" seems to do the thing for me.
Over and Out.

Martin :-)

tC_Crazy
September 26th, 2008, 05:38 PM
Have any of you figured out how to solve the updating problem on Intrepid Ibex? I tried a clean install of Ibex Alpha 5 and it installed smoothly. However, when I tried to update, it went into thermal shutdown midway through. I had to do a dpkg from the recovery boot option to try to fix it. Now it starts, but there's a problem in X... after logging in, I get a white screen and nothing else. tty still works. For the time being, I just reverted back to an image of my Hardy partition I made before the upgrade.

The main reason I'm trying to upgrade to Ibex is b/c of the horrendous battery life on Hardy. It's impossible to get anything done with that much battery life. I'm on Vista right now, and have been working for 2:40 with 15% battery life remaining. If I can pull 2:15 on Ubuntu, I will be satisfied.

fbdelivers
September 27th, 2008, 03:42 AM
I was just about to do an upgrade as well to intrepid. What does everyone recommend? Upgrade from 8.04 or do a clean install?

Thanks

kg6gfq
September 27th, 2008, 06:11 AM
The problem you're having with X is a result of compiz trying to start when 3D acceleration isn't supported. I forget where you can change this... Anyone know? You may also be able to do a Ctrl-Alt-F1 to get to a terminal. Run "sudo killall compiz" and "sudo metacity," perhaps? I'm not quite sure about that. If you can get from compiz back to metacity I would suggest installing the compiz settings applet, running it, and using it to switch your window manager from compiz to metacity.

Hopefully that works, if you like I can hunt down the exact config files you need to edit.

tC_Crazy
September 27th, 2008, 07:52 PM
I assume this has to do with the video drivers not being supported by the new kernel? Maybe it's best to wait until the final build of intrepid is released.

fbdelivers
September 27th, 2008, 08:59 PM
I just did a clean install of alpha 6 for intrepid. After running the clean install I went through and marked everything to update. This got me to kernel version 2.6.27-4. I tried to back track through this thread (used to have most everything working with hardy) and haven't had a lot of luck.

System boots -
WLAN doesn't work. WL shows up in the restricted driver mode but I get no blue light for wireless. Do I need to disable acpi=off on boot to get this to work again? Do I still need to disable all of the thermal modules still?

WACOM - doesn't work either. I tried the above script and it didn't generate any errors but so far no luck. I tried an older xorg.conf file from when it worked earlier for me but I must be missing something. Do the earlier tutorials still work for intrepid?

Thanks

kg6gfq
September 27th, 2008, 09:22 PM
A note on the script: it does nothing to your xorg.conf! You need working inputdevice sections in xorg.conf for the script to do anything worthwhile. For that I would recommend gali98's tutorial (http://ubuntuforums.org/showthread.php?p=5469447#post5469447).

Update on the video drivers:

radeonhd from git: I can use my external monitor with xrandr now, but rotation doesn't work.

radeon: The external monitor does work with xinerama, though there are some issues setting the resolution. Screen rotation works.

fglrx: Still no luck, and no idea what the source of the problem might be.


@fbdelivers:

The script is merely a compilation of all the commands used in gali's tutorial, so the tutorial should work as well. Just watch for an error in the step that copies the .ko file, because when it is compiled it seems to go into a different directory now. The following command should work no matter where the .ko file has been placed after the installation:


sudo cp ./src/2.*/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko

I have acpi=off in the boot parameters, though I haven't tried changing it, and I don't think thermal is disabled... But my wireless works fine, so long as I don't forget to switch it on. I've had it configured since around Alpha 3, though, and at that time it couldn't be done through restricted driver manager.

fbdelivers
September 28th, 2008, 03:49 AM
Thanks for the suggestion - I'm still struggling with Alpha 6. I ran through the script for enabling wacom. After doing a reboot during boot I get stuck with powernowd trying to start.

Not sure what part of the wacom tutorial would cause me problems in that section.

tC_Crazy
September 28th, 2008, 05:52 PM
If you are running Intrepid, then you should not have to use any boot parameters, nor should you have to blacklist the thermal module. It should be a normal install, just like any other computer.

kg: where did you get that radeonhd driver from?

fbdelivers
September 28th, 2008, 10:49 PM
I think that it's the xorg.conf file that I'm using that is causing the issues on boot. I used an earlier version prior to making the switch to intrepid alpha 6.

jubej
September 30th, 2008, 12:52 AM
Hi gali98 and kg6gfq

i jsut wanted to say thank you for all your help. the script worked really god on my hp tx2500us.so thnx kg6gfq.

and gali98 thnx for finding the error in my xorg.conf file, now i can move the arrow with my fingers to. is not so calibrated yet but i gues ill just haave to do the calibration in the tutorial.

by the way, has anyone make the bottons on the down right corner of the screen work? for exampel rotation, and to launch elisa?

and the infrared control, is there any way to make it work?

kg6gfq
September 30th, 2008, 02:48 AM
powernowd has been causing problems for me too. The pattern I've found is that unless I've had to do a hard reboot powernowd will start so long as the power cable is unplugged. You can plug it back in immediately after powernowd has started, though. I don't know why it happens, but I guess I should post a bug report one of these days...

Update on radeonhd: It's no longer working properly with the second monitor... xrandr extends the desktop onto the second monitor, but the colors are wrong and the image is not clear. I'm going to try putting an entry for the second monitor in xorg.conf, though, and see if that helps.

(tC_Crazy: I got the radeonhd driver from the git repository listed here (http://www.x.org/wiki/radeonhd#head-107f8ec30e84804907b4af6cdb20fbdd0056eefb) and compiled it. Thanks for the hint on boot options and the thermal module; I'll tinker with that as soon as I have time.)

@jubej: As mentioned earlier in the thread, only some of those buttons work properly; the others require a driver that hasn't yet been written. I've been tinkering with the IR remote and can't figure out how it works either; I suspect it too may require special, as-yet-unwritten drivers.

gali98
September 30th, 2008, 02:26 PM
For me the control worked out of box, but I have the tx2000 so I really couldn't help you on that. The bottom two buttons do not work. They are not recognized as keys, so to work, someone would have to write a driver for them.
Edit: I just now read kg6gfq's post... anyway...
Um... try using xev and see if the infrared controller picks up events... then maybe you can map the keycodes to something.
Kory

jingtra
October 4th, 2008, 08:23 PM
kg6gfq: Could you post the xorg.conf file? Is really struggling with installing the drivers and using the external screen

kg6gfq
October 5th, 2008, 10:40 PM
@jingtra: The important parts of the xorg.conf for multiple monitors are as follows:

Section "Screen"
Identifier "Default Screen"
Device "Radeon"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display" # <--Add this subsection if you don't have it already.
Depth 24
Virtual 1280 1824 # <--Change these values to set the maximum size of both your screens put together.
EndSubSection
EndSection

Driver "radeonhd" # <--Make sure this is set in your "Device" section. If X won't start with this set you probably don't have the newest driver from git (or the version you downloaded is broken).
I've also attached the scripts I use to switch the external monitor on and off. Read the comments in those files for more info. Have you managed to install the radeonhd driver from their git repository?

Remote Control: Picked up by xev. Thanks gali!! Many of the buttons are the same as their counterparts on the laptop itself, so if you've already mapped volume, media, and side-of-screen buttons they should work. The two bottom-of-screen buttons aren't picked up by xev though, as gali said. Neither is the act of rotating the screen, unfortunately.

"acpi=off": as tC_Crazy pointed out, this is not a necessary boot parameter and in fact should probably not be used in intrepid. Remove it by editing /boot/grub/menu.lst.

powernowd: With the newer kernel powersaved seems to work far better than powernowd - I've only had it hang once during boot, and that was after a hard shutdown. If you're having difficulty with powernowd I would recommend installing powersaved to replace it.

jubej
October 6th, 2008, 02:45 PM
Hello

Gali98 you are right the remote control works really good. i just have to map the others bottons that don work, but i have to learn how.

By the way Im experience something really wierd. on the screen the left dvd button and the media button was working before but now they don work, nothing happens on xev. it had the keycode 200 and 201. but now it seem that the mousepad on and off button is mapped 200 for off and 201 for on. so when i activate the mouse pad it will launch like 15 instans of the mdeia player elisa. i tryed the xev and when I turn the On or off button you will see the keycod 201 go on like forever. do you have the same problem? Any ideas?