Page 162 of 169 FirstFirst ... 62112152160161162163164 ... LastLast
Results 1,611 to 1,620 of 1689

Thread: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

  1. #1611
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    So... I installed quantal KDE on to an SD card (I was just running the installation CD off of an SD card before). It boots up to a black screen. CTRL+ALT+F1 lands me in a console on tty1. A simple restart of KDM makes X restart and this time it comes to life.
    Have you tried some of the kernel line switches like nomodeset to see if it will boot directly into the gui instead of requiring you to restart X?

    Hmm. Seems to be using the VESA driver for Screen0.
    [ 110.591] (II) LoadModule: "vesa"
    [ 110.591] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 110.592] (II) Module vesa: vendor="X.Org Foundation"
    [ 110.592] compiled for 1.11.3, module version = 2.3.1
    [ 110.592] Module class: X.Org Video Driver
    [ 110.592] ABI class: X.Org Video Driver, version 11.0
    [ 110.592] (II) LoadModule: "fbdev"
    [ 110.592] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 110.593] (II) Module fbdev: vendor="X.Org Foundation"
    [ 110.593] compiled for 1.11.3, module version = 0.4.2
    [ 110.593] ABI class: X.Org Video Driver, version 11.0
    [ 110.593] (II) VESA: driver for VESA chipsets: vesa
    [ 110.593] (II) FBDEV: driver for framebuffer: fbdev
    [ 110.593] (++) using VT number 8

    [ 110.602] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 110.602] vesa: Ignoring device with a bound kernel driver
    [ 110.602] (WW) Falling back to old probe method for vesa
    [ 110.602] (II) Loading sub module "fbdevhw"
    [ 110.602] (II) LoadModule: "fbdevhw"
    [ 110.604] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 110.604] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 110.604] compiled for 1.11.3, module version = 0.0.2
    [ 110.604] ABI class: X.Org Video Driver, version 11.0
    [ 110.604] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 110.604] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 110.606] (**) FBDEV(1): claimed PCI slot 0@0:2:0
    [ 110.606] (II) FBDEV(1): using default device
    [ 110.607] (II) FBDEV(1): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 110.607] (==) FBDEV(1): Depth 24, (==) framebuffer bpp 32
    [ 110.607] (==) FBDEV(1): RGB weight 888
    [ 110.607] (==) FBDEV(1): Default visual is TrueColor
    [ 110.607] (==) FBDEV(1): Using gamma correction (1.0, 1.0, 1.0)
    [ 110.607] (II) FBDEV(1): hardware: psbfb (video memory: 2400kB)
    [ 110.607] (II) FBDEV(1): checking modes against framebuffer device...
    [ 110.607] (II) FBDEV(1): checking modes against monitor...
    [ 110.607] (--) FBDEV(1): Virtual size is 1024x600 (pitch 1024)
    [ 110.607] (**) FBDEV(1): Built-in mode "current"
    [ 110.607] (==) FBDEV(1): DPI set to (96, 96)
    [ 110.607] (II) Loading sub module "fb"
    [ 110.607] (II) LoadModule: "fb"
    [ 110.608] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 110.609] (II) Module fb: vendor="X.Org Foundation"
    [ 110.609] compiled for 1.11.3, module version = 1.0.0
    [ 110.609] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 110.609] (**) FBDEV(1): using shadow framebuffer
    [ 110.609] (II) Loading sub module "shadow"
    [ 110.609] (II) LoadModule: "shadow"
    [ 110.610] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 110.611] (II) Module shadow: vendor="X.Org Foundation"
    [ 110.611] compiled for 1.11.3, module version = 1.1.0
    [ 110.611] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 110.611] (II) UnloadModule: "vesa"
    [ 110.611] (II) Unloading vesa
    [ 110.611] (==) Depth 24 pixmap format is 32 bpp
    [ 110.862] (==) FBDEV(0): Backing store disabled
    [ 110.863] (==) FBDEV(0): DPMS enabled
    [ 110.863] (==) RandR enabled
    [ 110.863] (II) Initializing built-in extension Generic Event Extension
    [ 110.863] (II) Initializing built-in extension SHAPE
    [ 110.863] (II) Initializing built-in extension MIT-SHM
    [ 110.863] (II) Initializing built-in extension XInputExtension
    [ 110.863] (II) Initializing built-in extension XTEST
    [ 110.863] (II) Initializing built-in extension BIG-REQUESTS
    [ 110.864] (II) Initializing built-in extension SYNC
    [ 110.864] (II) Initializing built-in extension XKEYBOARD
    [ 110.864] (II) Initializing built-in extension XC-MISC
    [ 110.864] (II) Initializing built-in extension SECURITY
    [ 110.864] (II) Initializing built-in extension XINERAMA
    [ 110.864] (II) Initializing built-in extension XFIXES
    [ 110.864] (II) Initializing built-in extension RENDER
    [ 110.864] (II) Initializing built-in extension RANDR
    [ 110.864] (II) Initializing built-in extension COMPOSITE
    [ 110.864] (II) Initializing built-in extension DAMAGE
    [ 110.884] (II) AIGLX: Screen 0 is not DRI2 capable
    [ 110.885] (II) AIGLX: Screen 0 is not DRI capable
    [ 110.917] (II) AIGLX: Loaded and initialized swrast
    [ 110.917] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [ 110.947] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
    Last edited by Favux; May 30th, 2012 at 06:20 PM.

  2. #1612
    Join Date
    Jul 2008
    Beans
    50

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Well, to make sure I booted the SD card off of an SD card reader in the USB port on the TX2. Which didn't work. Kernel wouldn't see it once it had loaded. So copying and fumbling a bit forth and back later...

    Booted the same thing off of my TX2, touch works fine there. Cursor follows touch there. So there is something strange going on. And I have honestly no idea what or why...

    I could give you the Xorg logs off of the slate and the TX2 if it's any help. But it's just a guessing game from here I suppose.

    I'll try the nomodeset in a bit. Also, I found that ubuntu has an experimental kernel for Intel graphics stuff. I'll try that as well.
    http://kernel.ubuntu.com/~kernel-ppa...ental/current/ (look at CHANGES).

  3. #1613
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Clever. Since you knew the N-Trig digitizer was the same (PID = 0001) the obvious difference is the video chipset and its driver. Given the cursor does track the finger on the TX2z I'm inclined to agree with you that the cursor tracking bug is in the video driver. So the Xorg.0.logs likely won't do us much good.

    So the Slate has an Intel video chipset? I thought from the other thread it was something else.

    So probably the best hope is the Intel video driver cutting edge PPA. And almost for sure they'll be updating the Quantal Quetzal KDE with newer Intel drivers anyway.

    Does the cursor jump to the second finger when it comes down? A third if it touches? Or do multiple cursors appear?
    Last edited by Favux; May 30th, 2012 at 08:03 PM.

  4. #1614
    Join Date
    Jul 2008
    Beans
    50

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Only one cursor. Which finger it goes to seems a bit random. Jumping forth and back a bit sometimes also seems a bit random. Sometimes it's not sure of which finger to go with (but it only goes to fingers, i.e. it doesn't triangulate, if you understand what I mean? In other words, it doesn't see three fingers as one large finger and try to find the middle spot, but it doesn't seem to sure of what finger to stick to, sometimes it is sure though and stays with one finger, even when I touch four to the screen).

    Also, kde.org has an xorg.conf file for the slate 500.

    http://community.kde.org/Plasma/Acti...n#HP_Slate_500

    It reads as follows:

    Code:
    Section "ServerLayout"
    	Identifier "Default Layout"
    	Screen 0 "Screen0" 0 0
    EndSection
    
    Section "Device"
    	Identifier "Intel_EMGD"
    	Driver "emgd"
    	VendorName "Intel(R) DEG"
    	BoardName "Embedded Graphics"
    	BusID "0:2:0"
    	Screen 0
    	VideoRAM 131072
    #	Option "RenderAccel" "false"
    	Option "PcfVersion" "1792"
    	Option "ConfigId" "1"
    	Option "PortDrivers" "lvds"
    	Option "ALL/1/name" "Integrated"
    	Option "ALL/1/General/PortOrder" "40000"
    	Option "ALL/1/General/DRI" "1"
    	Option "ALL/1/General/DRI2" "1"
    	Option "ALL/1/General/DisplayConfig" "1"
    	Option "ALL/1/General/DisplayDetect" "1"
    	Option "ALL/1/General/Accel" "1"
    	Option "ALL/1/General/VideoRAM" "131072"
    #	Option "ALL/1/General/shadowfb" "1"
    	Option "ALL/1/General/FbBlendOvl" "1"
    	
    	Option "ALL/1/Port/4/General/name" "LVDS"
    	Option "ALL/1/Port/4/General/EdidAvail" "0"
    	Option "ALL/1/Port/4/General/EdidNotAvail" "4"
    #	Option "ALL/1/Port/4/General/Rotation" "0"
    	Option "ALL/1/Port/4/General/Edid" "1"
    	Option "ALL/1/Port/4/FpInfo/Height" "600"
    	Option "ALL/1/Port/4/FpInfo/Width" "1024"
    	Option "ALL/1/Port/4/FpInfo/BkltMethod" "0"
    	Option "ALL/1/Port/4/Dtd/1/PixelClock" "53900"
    	Option "ALL/1/Port/4/Dtd/1/HorzActive" "1024"
    	Option "ALL/1/Port/4/Dtd/1/HorzSync" "75"
    	Option "ALL/1/Port/4/Dtd/1/HorzSyncPulse" "32"
    	Option "ALL/1/Port/4/Dtd/1/HorzBlank" "476"
    	Option "ALL/1/Port/4/Dtd/1/VertActive" "600"
    	Option "ALL/1/Port/4/Dtd/1/VertSync" "1"
    	Option "ALL/1/Port/4/Dtd/1/VertSyncPulse" "4"
    	Option "ALL/1/Port/4/Dtd/1/VertBlank" "22"
    #	Option "ALL/1/Port/4/Dtd/Flags" "0xc000000"
    	Option "ALL/1/Port/4/Attr/70" "0"	
    EndSection
    
    Section "DRI"
    	Mode 0666
    EndSection
    
    Section "Screen"
    	Identifier "Screen0"
    	Device "Intel_EMGD"
    	Monitor "LVDS"
    #	Option "DamageEvents" "True"
    #	Option "RenderAccel" "True"
    #	Option "AllowGLXWithComposite" "True"	
    	SubSection "Display"
    		Depth 24
    		Modes "1024x600"
    	EndSubSection
    	SubSection "Display"
    		Depth 32
    		Modes "1024x600"
    	EndSubSection
    	SubSection "Display"
    		Depth 16
    		Modes "1024x600"
    	EndSubSection
    	SubSection "Display"
    		Depth 8
    		Modes "1024x600"
    	EndSubSection
    EndSection
    
    Section "Monitor"
    	Identifier "LVDS"
    	ModelName "Integrated LVDS"
    #	ModeLine "1024x768@75" 63.2 1024 1080 1184 1344 600 601 604 627
    EndSection
    
    Section "Extensions"
    	Option "Composite" "enable"
    #	Option "DAMAGE" "True"
    #	Option "RENDER" "True"
    EndSection
    This goes to /etc/X11/xorg.conf.d/09-emgd.conf

    Funny thing. After having run (ran?) this SD card on the TX2 it now boots straight in to X on the slate. I haven't changed anything.

    I did add the kernel, as I mentioned. I just get panics all the time, so no go.

    I guess adding the xorg.conf as mentioned above fixes the X server not loading properly, if anyone has any troubles with that. I haven't tried it out though, so I'm just guessing. Will try it out in a second.

    Cursor still stands still on the slate though. Is there some edge X server I can try from somewhere? In a neat debian package? Since this is just a try-and-wipe install I don't mind. Let's have some fun and really go crazy with experimenting.

    Ok. I just mv'ed the .kde folder and restarted X. There is a notification, "System Notification Helper", "System upgrade notifications are available" (what a strange thing to say, not "system upgrades are available", but "notifications are available").
    Touching that square, which seems to be of a different layout than the rest (QT?) the cursor follows my finger, even as I drag it around the desktop. But touching somewhere on the desktop other than that message (which doesn't go away, btw), nothing. Doesn't follow my finger at all.
    So it's just some strange bug.
    Now I can't select anything at all with a regular finger touch. I can highlight what ever I want, but I can not select anything. Curioser and curioser...
    Last edited by tannalv; May 30th, 2012 at 09:09 PM.

  5. #1615
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Well, they're using the 3.2 kernel on that wiki page so presumably the xorg.conf is for a slightly older "Intel_EMGD"? That might be a problem.

  6. #1616
    Join Date
    Apr 2008
    Beans
    110

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Quote Originally Posted by tannalv View Post
    Only one cursor. Which finger it goes to seems a bit random. Jumping forth and back a bit sometimes also seems a bit random. Sometimes it's not sure of which finger to go with (but it only goes to fingers, i.e. it doesn't triangulate, if you understand what I mean? In other words, it doesn't see three fingers as one large finger and try to find the middle spot, but it doesn't seem to sure of what finger to stick to, sometimes it is sure though and stays with one finger, even when I touch four to the screen).
    Hey tannalv. I've been using the slate 500 for slightly over a year now. I've been using 11.10 mostly. If I get a chance I'll try to catch up on this thread and give my input... but for now:

    Your finger pointer jumping issues sounds like the evdev driver is being assigned to the multi-touch. I can post you my wacom configs later when I get a chance.

    For the most part, I gave up on using the emgd and poulsbo drivers. They're better for graphics (i.e. they have hardware 3d accel) but they cause a lot of other problems. I need to read everything you've done, but when I was trying to use the emgd driver it required me to downgrade the kernel because it didn't support the latest x11 ABI. This in turn lead to n-trig driver issues (namely, the ones you're experiencing).

    The psb-gfx driver is what I've been using. It has no 3d acceleration, but I made the comprimise since the thing I really wanted was decent inking. Touch works too but since there's no 3d you don't get compiz and so the touch is limited to a couple of window-manage ment tasks (for me). I use 5-finger to close, three swipe down to minimize, three swipe up to maximize. I know the slate only has 4-finger support, but somehow the 5-finger works with touchegg.

    Also, the kernel level wacom driver shipped with 11.10 has agressive filtering. Actually, it's only like 3 or 5 samples (I can't remember, but I looked at the code and I remember it was small) but it leads to significant delay in the pointer. This is why I think the n-trig does hardware filtering (averaging). There's a driver parameter you can set to reduce the number of samples to 1. I do that and it eliminates the jumpiness of my pen input.

    HTH

    Edit: I found this that I made: http://cheshirekow.com/redmine/proje...ate-clare/wiki I was recording notes here when I was screwing around with the slate. It's not up to date but it may include some information that you find useful.
    Last edited by cheshirekow; May 30th, 2012 at 09:24 PM.

  7. #1617
    Join Date
    Jul 2008
    Beans
    50

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Favux: Yeah, uhm, I noticed that after I made my post. It seems like more hassle than I would like to go through just to try out.

    cheshire: Oh, hi there! I'm just playing around really. I would love to get (K)Ubuntu working on it, it seems like I get a quicker and more responsive slate in ubuntu than I do in Windows. To me it's more of a surfboard and video-watching thing than anything serious. I just got it because it was cheap. Also, it's something new to play around with, so I just had to... Dissapointed by the speed (or lack there of) on it though.
    Seems like you have done some serious work getting it working with ubuntu. Quiet well done!
    Seems like Quantal has most issues worked out. Or the newer kernel I guess. Except for the "black screen of death" and the touch. Oh, and 3D, still. But seems like the next kernel (3.5) will have those issues addressed. Or, the 3D issue at least.

    I'll see if I can find some cutting edge experimental X server somewhere and try that out as well.

  8. #1618
    Join Date
    Jul 2008
    Beans
    50

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    To add to the confusion, I tried the pure ubuntu CD, quantal, no KDE, no LXDE or anything else. Just Gnome. That works fine though. Touch works without a problem. Awww :-/ So it's KDE that's messing up things.

    I can't get ubuntu to install though. The installer just crashes. But then again, this isn't even alpha, so.

  9. #1619
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Plus the 3.5 kernel should be coming.

  10. #1620
    Join Date
    Jun 2012
    Beans
    3

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Hello everybody. I took the plunge and installed kubuntu 12.04 on my TX2. Everything works fine including the touchscreen and the pen with pressure sensitivity. I have only one problem...java applications seem not to work correctly.
    What I'm seeing is that if I touch the screen the mouse tracking in Java apps is messed up. This behaviour continues until I reboot. If I never touch the screen after a reboot, Java apps work fine.
    I need to use this laptop for development and my IDE is Netbeans, so this is pretty much a biggie for me.
    Any pointers as to what might be happenning?

Page 162 of 169 FirstFirst ... 62112152160161162163164 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •