Home > Cannot Locate > Cannot Locate A Core Pointer Device Gentoo

Cannot Locate A Core Pointer Device Gentoo

Since xorg-server 1.5 X uses hal+evdev for autoconfiguration of the mouses and keyboards, in my opinion it's not ready as you can see, but that's the way that things are going It should also be listed in /proc/bus/input/devices. Attachments: signature.asc (0.19 KB) dhkuhl at optonline Dec4,2009,11:39AM Post #3 of 12 (5308 views) Permalink Re: X fails after new install [In reply to] Neil Bothwick wrote: > On Thu, 03 Dec 2009 Or even move xorg.conf out of the way and let xorg work it out for itself. -- Neil Bothwick Don't just do something, sit there! have a peek here

when I make that "emerge -pv xorg-server" I get one ebuild N and one ebuild R. Knoppix is running 32bit kernel. > > > > Also, I noticed that Knoppix picks up additional devices (webcam, etc) > > under KEYBOARD. Any suggestions before I rip all this out and have a go at the ATI proprietary drivers is most welcome. -- Regards, Mick Attachments: Xorg.0.log.zip (8.72 KB) signature.asc (0.19 KB) Could this be related? their explanation

Please specify busIDs for all framebuffer devices Please consult the The X.Org Foundation support at http://wiki.X.Org for help. I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=9 B: EV=b B: KEY=6420 30000 0 0 0 0 B: ABS=260800011000003 It says: '$DISPLAY is not set' > What's the problem? Any ideas?

It now boot, I long in on cosole and via ssh and all is fine > except the gui (X+kde4+evdev/hal/ati/....) What's the problem? Could this have something to do with it? with the extra vga parameter on the kernel line as follows: default 0 timeout 30 splashimage=(hd0,0)/grub/splash.xpm.gz title=Gentoo Linux 2.4.26-r6 root (hd0,0) kernel /kernel-2.4.26-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 vga=791 real_root=/dev/hda3 initrd /initrd-2.4.26-gentoo-r6 Thanks problem [In reply to] On Wed, 15 Jul 2009 11:43:00 +0000 (UTC), James wrote: > I'm using 'startx' to start kdm (xdm has been removed from rc auto startx starts and

Entry deleted from font path. (Run 'mkfontdir' on "/usr/share/fonts/misc/"). (WW) The directory "/usr/share/fonts/TTF/" does not exist. PS sounds like you might have problems with frame buffer support that is not compiled into some packages. That's fine, we'll fix that later.. 04-23-2009 #6 hj3lmen View Profile View Forum Posts Private Message View Articles Just Joined! Nifty little tool.

It's been my experience with ATI that > you may find 2 "cards" listed, so look carefully. Select Add Filter From Device and select your tablet (e.g. The file is re-created each time you fire up xorg. 04-23-2009 #8 hj3lmen View Profile View Forum Posts Private Message View Articles Just Joined! No synaptics driver loaded?” after reboot.

Depending on hal is nice and dandy in theory. xf86-input-wacom is the only package you need to install the X11 drivers. If it is not hal, then people will now that it is not the problem and can help you try something else. You are trying to use the kbd and mouse > drivers, instead of letting HAL take care of it.

An easy way to proceed is to temporarily assign keystrokes to your tablet's buttons like this: $ xsetwacom --get "Wacom Bamboo 16FG 4x5 Finger pad" Button 1 'key a' $ xsetwacom navigate here In those cases it is possible to run a script that configures the device calling xsetwacom every time the device is plugged in. If it doesn't, then you got a problem with something else. The general mapping syntax (extracted from the source code) for xsetwacom 0.17.0 is the following.

But I have already emerge that one time before.. Just put it in package.use or something, recompile xorg and see if it works. The inputattach command allows to bind serial device into /dev/input tree, for example with: # inputattach --w8001 /dev/ttyS0 See man inputattach for help about available options. Check This Out If it is hal, people can try to help you get it going if you want to.

Join Date Apr 2009 Posts 13 i mounted usb flash drive and took it over to my other PC - so here it is.. Comparing with Knoppix > which works nicely, I see that in my logs the lines: > ========================================== > (II) LoadModule: "ati" > (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so > (II) Module ati: vendor="X.Org Foundation" You could do it on the command line to, just for testing. michaelkintzios at gmail Mar7,2010,2:33AM Post #8 of 13 (1842 views) Permalink Re: Can't get Xorg going on Radeon HD R730 4670

You are trying to use the kbd and mouse drivers, instead of letting HAL take care of it.

Entry deleted from font path. (WW) The directory "/usr/share/fonts/OTF" does not exist. This is done by setting the Rotate option for all devices. Knoppix is running 32bit kernel. Privacy policy About ArchWiki Disclaimers Register Help Remember Me?

This is doing my head in ... >> > fglrx won't have any influence on your INPUT DRIVER based problem. There isn't and xorg.conf file, but I don't think I need one anymore; also X -configure fails. The x-axis is the input pressure you apply to the pen; the y-axis is the output pressure the application is given. (example curve) You can immediately test your desired values for http://ecoflashapps.com/cannot-locate/cannot-locate-a-core-pointer-device-ubuntu.html ideas?

Here is what I have now: ati-drivers-9.6 Missing digest for '/usr/portage/sys-kernel/gentoo-sources/gentoo-sources-2.6.29-r6.ebuild' NOT sure where this is coming from, as the latest kernel on the system is linux-2.6.29-gentoo-r5 (maybe a newer kernel Then you need to know what is the ID of your tablet. $ xsetwacom --list devices WALTOP International Corp. Any idea what I should tweak now to get this > > going? > > mesa. time....) the only way to get out of one of the GUI is to take the power-core.

TwinView Setup If you are going to use two Monitors the aspect ratio while using the Tablet might feel unnatural. Finding out the button IDs Sometimes it needs some trial&error to find the correct button IDs. Below, maybe you can whittle down my xorg.conf to what I still needs. You can find out additional info about these devices through /proc, for example: $ cat /proc/bus/input/devices ...

What's not clear about this statement? –slm♦ Jan 21 '15 at 0:05 | show 1 more comment Your Answer draft saved draft discarded Sign up or log in Sign up