Re: Graphics tablet / Xorg / mouse problems
I think it should be sufficient to set hald_enable=FALSE in etc/rc.conf to deactivate hald instead of chmod usr/local/etc/rc.d/hald. Rainer Am 04.02.2009 05:23 (UTC+1) schrieb Antonio Rieser: Hi, Thanks a million for your help. Many thanks to Bartosz, too! Just to be sure I understood how to deactivate hald, I ran (as root) the command chmod -x /usr/local/etc/rc.d/hald which should prevent it from running in the future, then, for this session pkill hald That should do it, right? Also, I reported earlier that everything seems to be normal if I boot with the tablet plugged in, but that's not always true. I now think that if I log in and out enough I get the same error messages. I have enclosed my Device Section of /etc/X11/Xorg.conf below. All the best, Tony - Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor# [bool] #Option ColorKey# i #Option CacheLines # i #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option ShowCache # [bool] #Option XvMCSurfaces# i #Option PageFlip# [bool] Identifier Card0 Driver intel VendorName Intel Corporation BoardName 82852/855GM Integrated Graphics Device BusID PCI:0:2:0 Option Accel On EndSection On Mon, Feb 2, 2009 at 4:36 AM, Dominic Fandrey kamik...@bsdforen.de wrote: Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: ... Just to keep you up to date, Bartosz is on it. Of course, I cannot give you a schedule. With the involvement of hald things seem to get much more complicated. It might be a temporary solution to deactivate hald support. Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Graphics tablet / Xorg / mouse problems
Hi, Whatever I did before, it had no effect. The temporary fix, for some reason, has been to deactivate kdm. Can anyone explain this? All the best, Tony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphics tablet / Xorg / mouse problems
On Wed, 2009-02-04 at 23:32 -0500, Antonio Rieser wrote: Hi, Whatever I did before, it had no effect. The temporary fix, for some reason, has been to deactivate kdm. Can anyone explain this? For starters hald should probably be disabled in rc.conf: hald_enable=NO. That said; how are you disabling kdm? Whats working now? This could be a case of root and user permissions, once one has a hold of the device another may not be able to control it and permissions are not passed on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphics tablet / Xorg / mouse problems
Hi, Thanks a million for your help. Many thanks to Bartosz, too! Just to be sure I understood how to deactivate hald, I ran (as root) the command chmod -x /usr/local/etc/rc.d/hald which should prevent it from running in the future, then, for this session pkill hald That should do it, right? Also, I reported earlier that everything seems to be normal if I boot with the tablet plugged in, but that's not always true. I now think that if I log in and out enough I get the same error messages. I have enclosed my Device Section of /etc/X11/Xorg.conf below. All the best, Tony - Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor # [bool] #Option ColorKey # i #Option CacheLines# i #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option ShowCache # [bool] #Option XvMCSurfaces # i #Option PageFlip # [bool] Identifier Card0 Driver intel VendorName Intel Corporation BoardName 82852/855GM Integrated Graphics Device BusID PCI:0:2:0 Option Accel On EndSection On Mon, Feb 2, 2009 at 4:36 AM, Dominic Fandrey kamik...@bsdforen.de wrote: Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: ... Just to keep you up to date, Bartosz is on it. Of course, I cannot give you a schedule. With the involvement of hald things seem to get much more complicated. It might be a temporary solution to deactivate hald support. Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphics tablet / Xorg / mouse problems
Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: ... Just to keep you up to date, Bartosz is on it. Of course, I cannot give you a schedule. With the involvement of hald things seem to get much more complicated. It might be a temporary solution to deactivate hald support. Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphics tablet / Xorg / mouse problems
Antonio Rieser said: 2) If I remove the tablet from the computer (I've only tried it during an X session), the system panics and shuts down, whether or not I stop the wacom driver before removing the tablet. Can you replicate this while viewing the console [ctrl+alt+f1] rather than an X session, to see exactly what the kernel is panicing from? (I know systems don't really like being forcibly paniced, but it may help figure out what is happening.) -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphics tablet / Xorg / mouse problems
Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: 1) If I boot without the tablet plugged in, then plug it in later and restart X, the error message (EE) intel(0): [DRI] Unlocking inconsistency: Context 676684348 trying to unlock lock held by context 2 (EE) intel(0): [DRI] Locking deadlock. Already locked with context 676684348, trying to lock with context 2. is written to Xorg.0.log and kdm-bin.log so many times that it fills my /var partition and locks my system. Note that if I boot with the tablet already plugged in, this error doesn't appear, and everything works fine. This is actually not connected to the tablet in my opinion, it's a problem with 3D-acceleration of your video card, which apparently does not like being reset/restarted. Can you show us your Device Section? I loading the driver via the line 'uwacom_load=YES in /boot/loader.conf 2) If I remove the tablet from the computer (I've only tried it during an X session), the system panics and shuts down, whether or not I stop the wacom driver before removing the tablet. OK, this sounds like a serious kernel problem. 3) If I stop the wacom driver, then start it again, I cannot simply restart X and have the tablet work. I have to reboot in order for the tablet to be recognized, even in mouse mode. That's because the driver can not start a rescan of the hardware. It can only hook in when the tablet gets first detected. This is why the module has to be loaded from loader.conf. 4) Occasionally the pointer refuses to stay put and drifts to the top of the screen. Controlling the pointer with the mouse becomes difficult at this point, too, since it wants to float upwards. Unfortunately, I have difficulty reproducing this reliably. Once it starts, though, it doesn't stop until I end the X session. If the problem starts and then I stop the wacom driver without restarting X, it continues anyway. I have that with a cheap optical mouse sometimes, I plug it out and back in and the problem is gone. Since that panics your system this is hardly an acceptable solution. Anyway it looks to me like that is a hardware problem. 5) Xorg.0.log contains the following error (also included below): pad Wacom X driver can't grab event device, errno=1005 (I haven't honestly noticed any strange behavior on the 'pad' device, however.) Well, I have taken the liberty to forward this mail to Bartosz, he might be able to do something with that. Obviously the driver does not handle all data generated by the pad. Regarding 1) - and maybe 3) 4) - my guess is that the tablet is fighting with the mouse for control of the pointer, but I don't know how to check if that's the case or how to fix it if it is. No, that's not the way things work. I think you are facing two distinct problems here. One with your video card and one with the tablet driver. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Graphics tablet / Xorg / mouse problems
Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: 1) If I boot without the tablet plugged in, then plug it in later and restart X, the error message (EE) intel(0): [DRI] Unlocking inconsistency: Context 676684348 trying to unlock lock held by context 2 (EE) intel(0): [DRI] Locking deadlock. Already locked with context 676684348, trying to lock with context 2. is written to Xorg.0.log and kdm-bin.log so many times that it fills my /var partition and locks my system. Note that if I boot with the tablet already plugged in, this error doesn't appear, and everything works fine. I loading the driver via the line 'uwacom_load=YES in /boot/loader.conf 2) If I remove the tablet from the computer (I've only tried it during an X session), the system panics and shuts down, whether or not I stop the wacom driver before removing the tablet. 3) If I stop the wacom driver, then start it again, I cannot simply restart X and have the tablet work. I have to reboot in order for the tablet to be recognized, even in mouse mode. 4) Occasionally the pointer refuses to stay put and drifts to the top of the screen. Controlling the pointer with the mouse becomes difficult at this point, too, since it wants to float upwards. Unfortunately, I have difficulty reproducing this reliably. Once it starts, though, it doesn't stop until I end the X session. If the problem starts and then I stop the wacom driver without restarting X, it continues anyway. 5) Xorg.0.log contains the following error (also included below): pad Wacom X driver can't grab event device, errno=1005 (I haven't honestly noticed any strange behavior on the 'pad' device, however.) Regarding 1) - and maybe 3) 4) - my guess is that the tablet is fighting with the mouse for control of the pointer, but I don't know how to check if that's the case or how to fix it if it is. Thanks in advance for any help! All the best, Tony Rieser PS This post is a repost/summary of a recent thread posted under a less transparent subject line. I apologize for the redundancy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg mouse problems
I had similar issues with Xorg and moused on an Apex Outlook KVM. I sumply disabled moused.. and just use the device section6 of my Xorg.conf to enable the mouse. You could also try compiling the kernel with device hints and add hint.psm.0.flags=0x100 to your hint file T - Original Message - From: Alexander Chamandy [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Sunday, March 27, 2005 5:39 PM Subject: Xorg mouse problems Hi all, I've got a PS/2 Labtech optical mouse with and Xorg 6.8.2 running on FreeBSD 5.4PR with an AMD Athlon and a GeForce 2 MX and I'm having some strange problems with Xorg and moused. This all worked fine under NetBSD (1.6.x and 2.0) with the wsmouse driver, but strangely, now when I use Xorg and/or moused on FreeBSD the mouse skips on verticle or horizontal movement all the way across the screen. I've tried changing the resolution, disabling ACPI, using different protocols and nothing has resolved the problem. Has anyone experienced this before and if so, how have they resolved it? dmesg included: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-PRERELEASE #0: Sun Mar 27 08:12:11 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ambrosia Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1343.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x644 Stepping = 4 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 805224448 (767 MB) avail memory = 782417920 (746 MB) npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 9 Entries on motherboard $PIR: BIOS IRQ 15 for 0.4.INTC is not valid for link 0x3 pci0: PCI bus on pcib0 $PIR: ROUTE_INTERRUPT failed. agp0: VIA 82C8363 (Apollo KT133x/KM133) host to PCI bridge mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 7 at device 4.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 7 at device 4.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 4.4 (no driver attached) pci0: multimedia, audio at device 4.5 (no driver attached) xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xd580-0xd580007f irq 7 at device 13.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:e3:6d:42 atapci1: Promise PDC20265 UDMA100 controller port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xd500-0xd501 irq 10 at device 17.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 orm0: ISA Option ROMs at iomem 0xd-0xd07ff,0xcc000-0xce7ff,0xc-0xcb7ff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNPb002 can't assign resources (irq) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0303 can't assign resources (port) Timecounter TSC frequency 1343055484 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDROM CRD-8320B/1.24 at ata0-master PIO4 ad4: 76319MB WDC WD800JB-00CRA1/17.07W17 [155061/16/63] at ata2-master UDMA100 Mounting root from ufs:/dev/ad4s1a -- Best wishes, Alexander G. Chamandy Webmaster www.bsdfreak.org Your Source For BSD News! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED
Xorg mouse problems
Hi all, I've got a PS/2 Labtech optical mouse with and Xorg 6.8.2 running on FreeBSD 5.4PR with an AMD Athlon and a GeForce 2 MX and I'm having some strange problems with Xorg and moused. This all worked fine under NetBSD (1.6.x and 2.0) with the wsmouse driver, but strangely, now when I use Xorg and/or moused on FreeBSD the mouse skips on verticle or horizontal movement all the way across the screen. I've tried changing the resolution, disabling ACPI, using different protocols and nothing has resolved the problem. Has anyone experienced this before and if so, how have they resolved it? dmesg included: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-PRERELEASE #0: Sun Mar 27 08:12:11 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ambrosia Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1343.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x644 Stepping = 4 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 805224448 (767 MB) avail memory = 782417920 (746 MB) npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 9 Entries on motherboard $PIR: BIOS IRQ 15 for 0.4.INTC is not valid for link 0x3 pci0: PCI bus on pcib0 $PIR: ROUTE_INTERRUPT failed. agp0: VIA 82C8363 (Apollo KT133x/KM133) host to PCI bridge mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 7 at device 4.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 7 at device 4.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 4.4 (no driver attached) pci0: multimedia, audio at device 4.5 (no driver attached) xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xd580-0xd580007f irq 7 at device 13.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:e3:6d:42 atapci1: Promise PDC20265 UDMA100 controller port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xd500-0xd501 irq 10 at device 17.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 orm0: ISA Option ROMs at iomem 0xd-0xd07ff,0xcc000-0xce7ff,0xc-0xcb7ff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNPb002 can't assign resources (irq) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0303 can't assign resources (port) Timecounter TSC frequency 1343055484 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDROM CRD-8320B/1.24 at ata0-master PIO4 ad4: 76319MB WDC WD800JB-00CRA1/17.07W17 [155061/16/63] at ata2-master UDMA100 Mounting root from ufs:/dev/ad4s1a -- Best wishes, Alexander G. Chamandy Webmaster www.bsdfreak.org Your Source For BSD News! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
