Re: xorg-server-1.5.3_7, /usr/ports/UPDATING, mouse
On Wed, 2009-03-25 at 03:45 +0100, Polytropon wrote: > On Tue, 24 Mar 2009 20:29:35 -0600, Tim Judd wrote: > > So I don't think the hal has the concept of joining the keyboard and > > mouse together to a single usb device. The pair works beautifully in > > the console... so I'm not sure if this is a bug worthy of reporting, or > > if I should research it more and try to discover the solution with a > > logitech pair that is known to work in the console to work in hal. s/single usb device/single usb plug/ > > Does the combination result in two devices (ukbd0, ums0)? Maybe > it's possible to instruct HAL to use the devices explicitely, by > "hard coding" them into some configuration file? Yes, FreeBSD/devd/devfs had created a kbd0 and ums0 HAL just didn't seem to recognize ums0 being listed too.. maybe because before it setup kbd0, ums0 appeared and it just got left behind? maybe because it already linked kbd0 to the plug/jack it was plugged into, it ignored the second device (this case, the mouse)? I even tried (by of course powerdown first) the USB+Mouse PS2 plug (both as original plug onto the Logitech pair) in case it might have picked up the PS2 and let it run with that --- it didn't find the PS2 mouse (by "found" I mean Xorg adding/enabling that device so the cursor moves). I was more concerned today (@work) to get my desktop operational. I can try later to diagnose, pick apart, etc etc the flaws of dbus and/or hal to submit a report. I felt it was necessary to announce this shortcoming, in case the OP was trying to use the same kind of device. ___ 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-server-1.5.3_7, /usr/ports/UPDATING, mouse
On Tue, 24 Mar 2009 20:29:35 -0600, Tim Judd wrote: > So I don't think the hal has the concept of joining the keyboard and > mouse together to a single usb device. The pair works beautifully in > the console... so I'm not sure if this is a bug worthy of reporting, or > if I should research it more and try to discover the solution with a > logitech pair that is known to work in the console to work in hal. Does the combination result in two devices (ukbd0, ums0)? Maybe it's possible to instruct HAL to use the devices explicitely, by "hard coding" them into some configuration file? -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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-server-1.5.3_7, /usr/ports/UPDATING, mouse
I worked around in circles again and again today with the same problem. My problem came down to that the Logitech keyboard/mouse combo (to single USB receiver) saw the keyboard (by hal) but not the mouse. Slapping a individual mouse in with the Logitech keyboard/mouse pair (so 1 keyboard, 2 mice) let the 2nd mouse work. So I don't think the hal has the concept of joining the keyboard and mouse together to a single usb device. The pair works beautifully in the console... so I'm not sure if this is a bug worthy of reporting, or if I should research it more and try to discover the solution with a logitech pair that is known to work in the console to work in hal. Thank you! $0.02 ___ 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-server-1.5.3_7, /usr/ports/UPDATING, mouse
On Mon, 23 Mar 2009, Neal Hogan wrote: Well, recently I deinstalled all of my third party apps . . . long story (some of which is documented on this list) . . . but the short story is that some were added via the ports tree and others via pkg_add. When it came time to portupdate, I was having problems and it was brought to my attention that, among other things, mixing ports and packages may lead to problems. Also, I didn't do the massive deinstall until after I had portupgraded all of my packages individually and the mouse/keyboard didn't work with X (it did at the console). Once this happened I felt compelled to wipe the slate. So, with no ports/packages installed and starting with a fresh ports tree, I began installing them one-by-one: 1) cd /usr/ports/path/port 2) make && make install && make clean I started with xorg. After it was installed, I tried to start X (startx) . . . no dice . . . no big deal. I created the basic xorg.conf (Xorg -configure), tried it (Xorg -config xorg.conf.new). X started, but no mouse activity and ctrl+alt+backspace did not quit X. I had moused enable in rc.conf and, as I say above the mouse worked (i.e., it moved when asked) at the console. /usr/ports/UPDATING says that some mouse issues were cleared up: "20090124: 241 AFFECTS: users of x11-servers/xorg-server, sysutils/hal 242 AUTHOR: rnol...@freebsd.org 243 244 sysutils/hal has been updated and should now properly detect 245 mice for use in Xorg. Use of AllowEmptyInput should no longer 246 be needed for most users and moused should now work fine." But, as I say, I have no mouse under X. Adding hal alone is not enough, you have to enable it both when you build xorg-server and in /etc/rc.conf. I use moused also, and have no AllowEmptyInput or AutoAddDevices or mouse or keyboard sections in xorg.conf. -Warren Block * Rapid City, South Dakota USA ___ 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-server-1.5.3_7, /usr/ports/UPDATING, mouse
Message: 25 Date: Mon, 23 Mar 2009 15:51:54 -0500 From: Adam Vandemore Subject: Re: xorg-server-1.5.3_7, /usr/ports/UPDATING, mouse To: freebsd-questions@freebsd.org Message-ID: <49c7f66a.7040...@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Neal Hogan wrote: > > Well, recently I deinstalled all of my third party apps . . . long story > > (some of which is documented on this list) . . . but the short story is that > > some were added via the ports tree and others via pkg_add. When it came time > > to portupdate, I was having problems and it was brought to my attention > > that, among other things, mixing ports and packages may lead to problems. > > Also, I didn't do the massive deinstall until after I had portupgraded all > > of my packages individually and the mouse/keyboard didn't work with X (it > > did at the console). Once this happened I felt compelled to wipe the slate. > > > > So, with no ports/packages installed and starting with a fresh ports tree, I > > began installing them one-by-one: > > > > 1) cd /usr/ports/path/port > > 2) make && make install && make clean > > > > I started with xorg. After it was installed, I tried to start X (startx) . . > > . no dice . . . no big deal. I created the basic xorg.conf (Xorg > > -configure), tried it (Xorg -config xorg.conf.new). X started, but no mouse > > activity and ctrl+alt+backspace did not quit X. I had moused enable in > > rc.conf and, as I say above the mouse worked (i.e., it moved when asked) at > > the console. /usr/ports/UPDATING says that some mouse issues were cleared > > up: > > > > "20090124: > > 241 AFFECTS: users of x11-servers/xorg-server, sysutils/hal > > 242 AUTHOR: rnol...@freebsd.org > > 243 > > 244 sysutils/hal has been updated and should now properly detect > > 245 mice for use in Xorg. Use of AllowEmptyInput should no longer > > 246 be needed for most users and moused should now work fine." > > > > But, as I say, I have no mouse under X. So, I try adding: > > > > Option "AllowEmptyInput" "off" > > > > in my xorg.conf and "Hey! We gotta mouse!" > > > > I just rebooted and the mouse still works in X, but just before rebooting I > > disabled moused (in rc.conf -> moused_enable="NO"). So, adding the above > > line to xorg.conf helped with/without moused. Note that prior to this whole > > portupgrade deal I was running 7.1-RELEASE without an xorg.conf, put with an > > older xorg. > > > > At this point, I'm not upset b/c everything seems to be working fine. Just > > curious what might be going on. Thanks for you time. Below is my dmesg. > > > > 1 Copyright (c) 1992-2009 The FreeBSD Project. > > 2 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > 3 The Regents of the University of California. All rights > > reserved. > > 4 FreeBSD is a registered trademark of The FreeBSD Foundation. > > 5 FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 > > 6 n...@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC > > 7 Timecounter "i8254" frequency 1193182 Hz quality 0 > > 8 CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) > > 9 Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > 10 > > Features=0x383f9ff > > V,PAT,PSE36,MMX,FXSR,SSE> > > 11 AMD Features=0xc0480800 > > 12 real memory = 468647936 (446 MB) > > 13 avail memory = 444530688 (423 MB) > > 14 kbd1 at kbdmux0 > > 15 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > > RF5413) > > 16 acpi0: on motherboard > > 17 acpi0: [ITHREAD] > > 18 acpi0: Power Button (fixed) > > 19 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > 20 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > > 21 acpi_ec0: port 0x62,0x66 on acpi0 > > 22 pcib0: port 0xcf8-0xcff on acpi0 > > 23 pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid > > 24 pci0: on pcib0 > > 25 agp0: on hostb0 > > 26 pcib1: at device 1.0 on pci0 > > 27 pci1: on pcib1 > > 28 vgapci0: port 0x9000-0x90ff mem > > 0xe000-0xefff,0xd010-0xd010 irq 10 at device 5.0 on pci1 > > 29 ohci0: mem > > 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 > > 30 ohci0: [GIANT-LOCKED] > > 31 ohci0: [ITHREAD] > > 32 usb0: OHCI version 1.0, legacy support > > 33 usb0: SMM does not res
Re: xorg-server-1.5.3_7, /usr/ports/UPDATING, mouse
Neal Hogan wrote: Well, recently I deinstalled all of my third party apps . . . long story (some of which is documented on this list) . . . but the short story is that some were added via the ports tree and others via pkg_add. When it came time to portupdate, I was having problems and it was brought to my attention that, among other things, mixing ports and packages may lead to problems. Also, I didn't do the massive deinstall until after I had portupgraded all of my packages individually and the mouse/keyboard didn't work with X (it did at the console). Once this happened I felt compelled to wipe the slate. So, with no ports/packages installed and starting with a fresh ports tree, I began installing them one-by-one: 1) cd /usr/ports/path/port 2) make && make install && make clean I started with xorg. After it was installed, I tried to start X (startx) . . . no dice . . . no big deal. I created the basic xorg.conf (Xorg -configure), tried it (Xorg -config xorg.conf.new). X started, but no mouse activity and ctrl+alt+backspace did not quit X. I had moused enable in rc.conf and, as I say above the mouse worked (i.e., it moved when asked) at the console. /usr/ports/UPDATING says that some mouse issues were cleared up: "20090124: 241 AFFECTS: users of x11-servers/xorg-server, sysutils/hal 242 AUTHOR: rnol...@freebsd.org 243 244 sysutils/hal has been updated and should now properly detect 245 mice for use in Xorg. Use of AllowEmptyInput should no longer 246 be needed for most users and moused should now work fine." But, as I say, I have no mouse under X. So, I try adding: Option "AllowEmptyInput" "off" in my xorg.conf and "Hey! We gotta mouse!" I just rebooted and the mouse still works in X, but just before rebooting I disabled moused (in rc.conf -> moused_enable="NO"). So, adding the above line to xorg.conf helped with/without moused. Note that prior to this whole portupgrade deal I was running 7.1-RELEASE without an xorg.conf, put with an older xorg. At this point, I'm not upset b/c everything seems to be working fine. Just curious what might be going on. Thanks for you time. Below is my dmesg. 1 Copyright (c) 1992-2009 The FreeBSD Project. 2 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 3 The Regents of the University of California. All rights reserved. 4 FreeBSD is a registered trademark of The FreeBSD Foundation. 5 FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 6 n...@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC 7 Timecounter "i8254" frequency 1193182 Hz quality 0 8 CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) 9 Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 10 Features=0x383f9ff 11 AMD Features=0xc0480800 12 real memory = 468647936 (446 MB) 13 avail memory = 444530688 (423 MB) 14 kbd1 at kbdmux0 15 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) 16 acpi0: on motherboard 17 acpi0: [ITHREAD] 18 acpi0: Power Button (fixed) 19 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 20 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 21 acpi_ec0: port 0x62,0x66 on acpi0 22 pcib0: port 0xcf8-0xcff on acpi0 23 pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid 24 pci0: on pcib0 25 agp0: on hostb0 26 pcib1: at device 1.0 on pci0 27 pci1: on pcib1 28 vgapci0: port 0x9000-0x90ff mem 0xe000-0xefff,0xd010-0xd010 irq 10 at device 5.0 on pci1 29 ohci0: mem 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 30 ohci0: [GIANT-LOCKED] 31 ohci0: [ITHREAD] 32 usb0: OHCI version 1.0, legacy support 33 usb0: SMM does not respond, resetting 34 usb0: on ohci0 35 usb0: USB revision 1.0 36 uhub0: on usb0 37 uhub0: 4 ports with 4 removable, self powered 38 pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff irq 5 at device 6.0 on pci0 39 pcm0: 40 pcm0: [GIANT-LOCKED] 41 pcm0: [ITHREAD] 42 isab0: at device 7.0 on pci0 43 isa0: on isab0 44 pci0: at device 8.0 (no driver attached) 45 pci0: at device 9.0 (no driver attached) 46 cbb0: irq 11 at device 10.0 on pci0 47 cardbus0: on cbb0 48 pccard0: <16-bit PCCard bus> on cbb0 49 cbb0: [ITHREAD] 50 fwohci0: mem 0xd0009000-0xd00097ff,0xd000-0xd0003fff irq 10 at device 12.0 on pci0 51 fwohci0: [FILTER] 52 fwohci0: OHCI version 1.10 (ROM=1) 53 fwohci0: No. of Isochronous channels is 4. 54 fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a 55 fwohci0: Phy 1394a available S400, 1 ports. 56 fwohci0: Link S400, max_rec 2048 bytes. 57 firewire0: on fwohci0 58 fwe0: on firewire0 59 if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a 60 fwe0: Ethernet address: 02:0d:9d:43:0c:6a 61 fwip0: on firewire0 62 fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe, S400, maxrec 2048 63 sbp0: on firewire0 64 dcons_crom0: on firewire0 65 dcons_crom0: bus_addr 0x12bc000 66 fwohci0: Initiate bus reset 67 fwohci0: BUS reset 68
