HOWTO setting up ubuntu 8.10 intrepid on the HP tx2z tablet pc

[Favux]

Hi Vincent,

It's recommended, if you are going to do suspend, that /swap be 1.5x (up to as much as 2x) your RAM. So I think you would want your /swap to be about 6 GB. It's possible that having it a 4 GB (/swap=RAM) may be part of your problem.

Good, thanks for the output. I'll take a look. Does touch (finger or fingernail) on your screen work for you?

[Vincent_Lin]

Hi Favux,

I did hear that swap should be set to around 1.5 times of actual physical memory, but I don't know that it is related to suspend. I guess it is worth a try.

Regarding the tablet functions, I can say - YEAH!!

I have those scripts and some are even one-liners to be packed to icons in a drawer of gnome panel, so that not only I can use the functionality but my little girls (4 and 6 years olds) can boot the machine and use it by themselves. They are taking up too much time using my T42 playing simply tuxpaint. But now I can show them to draw stuff on inkscape and the likes, but not gimp, just not yet.

These icons will do rotation-right(toggle), rotation-up-side-down(toggle), no-touch, and both-touch-and-pen. When touch is not that much used as stylus, I simply disable it, by issuing xsetwacom commands, to prevent the interfering when my palm is touching the screen.

Pressure sensitive works in both gimp and inkscape. I went though documentation of linuxwacom and it is all there.

This machine is actually very sweet. I was eye-ing on Lenovo X200, but it is expensive enough to put off my purchase decision, until I saw this tx2z.

Thanks. Will let you know if increasing swap will help solving resume issues.

Cheers,

Vincent

[Favux]

Hi Vincent,

That is cool. Your tablet has turned into sort of a family activity!

If everything is working well, we should probably leave well enough alone. The reason I wanted the output (thanks again) is because gurgle's xorg.conf confused me. Everything was on the same input path. As far as I know touch should have a different input path. But since the TX2z uses a N-trig digitizer I could easily be wrong. I was surprised that dmesg did not return some pci paths with the wacom stuff. Would you mind terribly attaching your xorg.conf?

I agree, HP tablets are a great bargain. Good luck on suspension. Don't take my word on the 1.5x thing, check around first.

[Vincent_Lin]

Favux,

gparted is resizing my data partition to yield some more hd space for swap. It is taking very very long time now. I guess I will see what comes out tomorrow morning.

Please find my attached xorg.conf. It is a mixed copy of here and there, etc.., mostly based on what glurgle posted here.

Cheers,

Vincent

[Vincent_Lin]

Hi Favux,

OK. Here is the thing. Resume after suspend now is working, after I added i8042.reset to the end of the actual kernel line, instead of #kopt line. I suppose adding options on the #kopt line is to add "generic" options that would be applied to and and all kernels you would boot from, resulting in the options to survive and upgrade/change of kernels.

Yet, I did remember I once tried that but it did not work at that time. And this time it works. Strange isn't it?

BUT, there is always a big but, wired networking stopped working, and yet wireless networking IS working.

How bizarre is that!!

catting /var/log/pm-suspend.log (suspend and resume log) would show exactly the same before and after this change, both are success.

Initial commandline parameters:
Sat Feb 7 13:07:01 CST 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00clear suspend: success.
/usr/lib/pm-utils/sleep.d/01PulseAudio suspend: success.
/usr/lib/pm-utils/sleep.d/05led suspend: not applicable.
/usr/lib/pm-utils/sleep.d/10NetworkManager suspend: Welcome to PulseAudio! Use "help" for usage information.
>>> success.
/usr/lib/pm-utils/sleep.d/48hid2hci suspend: not applicable.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend: not applicable.
/usr/lib/pm-utils/sleep.d/50modules suspend: success.
/usr/lib/pm-utils/sleep.d/90clock suspend: success.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend: success.
/usr/lib/pm-utils/sleep.d/95anacron suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend: not applicable.
/usr/lib/pm-utils/sleep.d/96laptop-mode suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend: success.
Sat Feb 7 13:07:04 CST 2009: performing suspend
Sat Feb 7 13:07:20 CST 2009: Awake.
Sat Feb 7 13:07:20 CST 2009: Running hooks for resume
/usr/lib/pm-utils/sleep.d/99video resume: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume: success.
/usr/lib/pm-utils/sleep.d/96laptop-mode resume: success.
/usr/lib/pm-utils/sleep.d/95led resume: not applicable.
/usr/lib/pm-utils/sleep.d/95anacron resume: success.
/usr/lib/pm-utils/sleep.d/94cpufreq resume: success.
/usr/lib/pm-utils/sleep.d/90clock resume: success.
/usr/lib/pm-utils/sleep.d/50modules resume: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume: not applicable.
/usr/lib/pm-utils/sleep.d/48hid2hci resume: No devices in HID mode found
Returned exit code 1.
/usr/lib/pm-utils/sleep.d/10NetworkManager resume: success.
/usr/lib/pm-utils/sleep.d/05led resume: not applicable.
/usr/lib/pm-utils/sleep.d/01PulseAudio resume: Welcome to PulseAudio! Use "help" for usage information.
>>> success.
/usr/lib/pm-utils/sleep.d/00clear resume: success.
Sat Feb 7 13:07:21 CST 2009: Finished.


So I gain some and lose some. Afterall, I can live with no-wire-networking as long as wireless networking is working, in addition to suspend works.

Cheers,

Vincent Lin

[Favux]

Hi Vincent,

Great! So maybe giving swap a little more room did the trick.

All the kernel mods I had to do before the 2.6.27 kernel, were always at the end of the actual kernel line. Why that would break wired networking is beyond me. I agree, bizarre!

Oh well glad it is working. One more favor. Could you attach the output of:

more /proc/bus/input/devices

I have found some more stuff about N-trig. There should be at least two sections in the output that start with something looking like:

I: Bus=0003 Vendor=056a Product=0093 Version=0330
N: Name="Wacom ISDv4 93"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.3/2-2.3:1.0/input/input10

Also could you repeat the:

dmesg | grep [Ww]acom

command and see if you get pci/usb paths in it. Even try changing wacom to n-trig (or N-trig or N-Trig, etc.). Basically I'm trying to do appendix 1 of:
http://ubuntuforums.org/showthread.p...12#post6546012
of the kernel driver HOW TO for N-trig. Thank you.

[Vincent_Lin]

Favux,

So stupid me.

1. After a reboot, wired and wireless networking both work.

2. I forgot I resized/increased swap partition. That might be it. gparted works pretty well, except that the time it took was so long that it actually worried me a bit.

Now I have attached the output of the those commands you requested.
Glad to help and showoff the status of a working 8.10 on tx2z.

Thanks again.

Cheers,


Vincent Lin

[Favux]

Hi Vincent,

Outstanding!

So still no output from Wacom. Darn. Say you misspelled trig. Could you please try again using:

dmesg | grep [Nn]-[Tt]rig

instead of:

dmesg | grep [Nn]-[Tt]ring

Oh and please try it without the hypen. "[Nn][Tt]rig". Thank you so much.

[Vincent_Lin]

Favux,

No sign of [Nn]-[Tt]rig nor [Nn][Tt]rig when I ran dmesg.

vincent@tx2z:~$ dmesg | grep [Nn]-[Tt]rig
vincent@tx2z:~$ dmesg | grep [Nn][Tt]rig
vincent@tx2z:~$ dmesg | grep N-Trig
vincent@tx2z:~$ dmesg | grep N-trig
vincent@tx2z:~$ dmesg | grep n-Trig
vincent@tx2z:~$ dmesg | grep n-trig
vincent@tx2z:~$ dmesg | grep NTrig
vincent@tx2z:~$ dmesg | grep Ntrig
vincent@tx2z:~$ dmesg | grep nTrig
vincent@tx2z:~$ dmesg | grep ntrig
vincent@tx2z:~$


Yet, the wired networking is rather unstable. I suspended this machine and open it after a few hours, wired networking was not working again.

After a fresh reboot, and closed the lid then open it, wired networking is still working.

On either case above, i checked /var/log/pm-suspend.log and both had
10Networkmanager resume: success.

I certainly hope that my network card is not mal-functioning. I will play more with it over the weekend.

Cheers,

Vincent

[Favux]

Hi Vincent,

Well, something strange is going on. But the current version of Network Manager (0.70) seems to have a fair number of problems. Maybe it will improve with Jaunty. And so should your N-trig support. Kernel 2.6.28 is suppose to have more support for it. And Rafi already has a patch out for it.

Thank you very much for checking on the N-trig stuff! I can't figure out why there isn't any input paths. I come back to maybe there is a problem with the N-trig patch. I think the Dell latitude user was using event 3 as his touch input path. It has me confused. Oh well.