|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
My Mouse Don't Work ???
... and they never did. Could someone please tell me how do I make my mouse work on my Gigabytes running FreeBSD. It works for Windows-7 but these machines are to be dedicated to FreeBSD so I dd out Winodws long ago and they been sitting around doing nothing for months. I have these two boards and neither of will run the mouse on any version of FreeBSD including current-9.0
Board-1 "Gigabyte GA-890GPA-UD3H" Board-2 "Gigabyte GA-880GA-UD3H" These mother board has only one standard mouse/keyboard port and a bunch of USB-2 and USB-3. If I use both PS2 keyboard and mouse plugged in the standard single port with a split cable the mouse will not work. If I plug the mouse in the usb port, the mouse will not work. If I switch them around the mouse STILL will not work. This is what happens; the mouse pointer ARROW will show up on the screen, but the second I type a key on the keyboard to log-in, the ARROW DISAPPEAR, like Houdini. These are stand-along machines. This has been going on from day1, back in October 2010 when I purchased these two Gigabyte Mother Boards. Fedora not installing was my first issue. Never did get it installed to date. I tried everything I could think of to make the mouse work. Now I'm running the latest and the Greatest FreeBSD current-9.0 with mouse support enabled properly, which works on all my other systems, old and new. I ask Gigabyte for help but they don't have a clue. I'm sure it's a BIOS issue. There all kinds of BIOS issues at their forum but the giant corporation seem to be on the hush-hush for reasons that makes cent" to me. It can't install ANY version of Fedora, the BIOS do not have NUM-LOCK and now no mouse for FreeBSD and I bust them all because I am a FreeBSDsor. But this is "BSD" and there may be a work-around. Maybe timing or something because you touch the keyboard the mouse loss focus ... the mouse arrow will show up after booting but it don't move like it can on other machines when you move the mouse around. It just show up completely FROZE waiting for you to touch the working keyboard. Gosh! Would anyone have any ideas that I can try. Imagine your first Dream-Machines EVER, with BIOS build from h*ll. WHY ME!!! Thanks again in advance Sorry about back-to-back threads but this one is about to make me crack. |
|
|||
I'm still crying ... I should have mention this; I had PcBSD installed at one time on these machines and they worked just fine. But now they only run FBSD because one is going to be a kick booty gateway running pf and such (thanks due only to this daemon-forums) and the other is going to be a dedicated web-server for all my projects and such. My Webprogramming, networking, JAVA, C++, etc classes are soon OVER and I'm ready for some hand-on experience. All I had time for was reading, working, while my battle-axe complained for two years that she needs a new pair of shoes. I gave that money to Gigabyte, now she bare footed and got to stay home with me. heehee
Anyway, my 3rd machine is also a AMD, but it has a real mother-board that runs PcBSD where I can sooon build all from there for those goofy Gigabyte machines but they got the juice. It's still a dream come true, I just have not got around to using what I learn yet (some networking) which I already forgot all about. Thanks Beastie, I'm ok now. It just drove me nuts and finals is due next Friday. I fought hard to stay two weeks ahead this semester but it all went down the drain because I got nothing deal because of a darn mouse problem and such. That hurt me BAD! |
|
|||
After eight months I think I found a clue. I been blaming Gigabyte hardware for this problem, now with 2-strikes against them, but last night I notice this while playing with FBSD-9.0-current GENERIC.
The GIANT has been removed from the file (and since 7.2 i bet). Whatever it was replaced with don't seem to be work-around-the-board. I been telling the world for eight months that absolutely no Fedora OS versions will install on these boards and that FreeBSD mouse is gone. I guest nobody got the hint so would someone of conversation report this thread to FreeBSD-Development. Proof is in there own effort to investigate and test unless they already know. Being more into AMD from jump-street, FreeBSD 7.2 - 8.0 would not install on newer AMD machines back than, if any. I read thousands of questions with no solution in sight while googing for years. Eventually, it was solved on it own when FreeBSD 8.1 was released. That was just like yesterday to me. We just found our solution! One year later, now I step into the same sh*t again? Am I'm the only person who own the great Gigabyte GA-890GPA not intended for Windows-7? ADAPTIVE_GIANT and/or friend is MISSING: Code:
## options ADAPTIVE_GIANT # Giant mutex is adaptive. ## options STOP_NMI # Stop CPUS using NMI instead of IPI ## device psm # PS/2 mouse -- need [GIANT-LOCKED] ??? It my bet that the FreeBSD manual won't tell anyone what GIANT was replaced with, how it works and why... and you better not ask at their forum ... but, sir, it's the only clue I got. Last edited by sharris; 3rd May 2011 at 04:01 AM. |
|
|||
For a lot of kernels, SMP was an afterthought.. and for the most part a lot of kernel code, including drivers, are confined to a single core.
http://en.wikipedia.org/wiki/Giant_lock It's a lack of fine grained locking, and it's tricky to get right.. no clue what your problem is exactly, but it's no conspiracy. |
|
|||
The word GIANT is only used twice in my log-message. That is where I got the idea. This is a 4-core AMD
Code:
kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ................... psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 My main concern is not to let stuff like this slip by or else we all are in trouble. <Edit acting up> .. .. Last edited by sharris; 3rd May 2011 at 07:46 AM. |
|
|||
Now I'll shut-my-trap
Sorry code posted above with [GIANT-LOCKED] is from log-messages on another AMD motherboard "T series TA790GX" that runs 8.1 - 9.0 perfectly from day one, so don't get confuse from this point. Sorry about that but this mistake just paided-off.
Check this out: Here's the complete log-message from the Gigabyte mother-board running Phenom X4-3200 ... Suprize again... notice there is no [GIANT-LOCKED] or even the word lock in this file like it is in the non-gigabyte AMD board with the word(LOCK) I posted above... This along should tell us something. Quote:
options ADAPTIVE_GIANT is missing from current 9.0. Don't take my word, just download FreeBSD-AMD64 current and compare GENERIC with older versions. My questions was; Where is it or what has it been replace with? My statement was; You'll never find it in FreeBSD documentation. My reason was; To save my date future and sanity. I don't like surprised That's my story and I'm sticking to it coppers! Anyway I see NO LOCK in this file. Thanks BSDfan666, but you can't ever know the problem or help me with-out using the same/model Mother-Boards (GA-***GPA), build in the back alleys of the HONG-KONG blackmarkets. But you can put 2+2 together just by comparing what I just wrote. It's a higher-up problem and THIS IS PROOF of the beginnings of every-machine and every-OS for itself. No more standard, ever... Now you get your FBSD in 464 flavors. Just make sure you pick the correct one to install or kaBoom ... with no-refund for hardware out the cracker-jack box. Like I said, lucky for me, I'm only using these GIGABYTES for my home network routers, servers and such, mainly to gain some hands-on experience. Being an over-priced, over-kill for such a small operation is not an issue to me .. but how about other user and the future of FBSD. This is one sure way to take BSD out the game (desktop), leaving only LINUX and Windows in the picture. I guest it time to do my LINUX-C++ HW FINALS since my BSD degree is doom to die. Just kidding log-messages GA-880 Code:
## messages - Gigabyte GA-880GA-UD3H May 1 14:59:48 MACH-0 newsyslog[2336]: logfile first created May 1 14:59:48 MACH-0 syslogd: kernel boot file is /boot/kernel/kernel Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT-201101 #0: Mon Jan 3 22:15:39 UTC 2011 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 WARNING: WITNESS option enabled, expect reduced performance. CPU: AMD Phenom(tm) II X4 955 Processor (3214.25-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLU SH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x802009<SSE3,MON,CX16,POPCNT> AMD Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x37ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT> TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1789272064 (1706 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <GBT GBTUACPI> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 2 ioapic0 <Version 2.1> irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <GBT GBTUACPI> on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 6fcf0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 cpu2: <ACPI CPU> on acpi0 cpu3: <ACPI CPU> on acpi0 acpi_button0: <Power Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0 pci1: <ACPI PCI bus> on pcib1 vgapci0: <VGA-compatible display> port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xfdee0000-0xfdeeffff,0xfdd00000-0xfddfffff irq 18 at device 5.0 on pci1 pci1: <multimedia, HDA> at device 5.1 (no driver attached) pcib2: <ACPI PCI-PCI bridge> irq 17 at device 9.0 on pci0 pci2: <ACPI PCI bus> on pcib2 pci2: <serial bus, USB> at device 0.0 (no driver attached) pcib3: <ACPI PCI-PCI bridge> irq 18 at device 10.0 on pci0 pci3: <ACPI PCI bus> on pcib3 re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xce00-0xceff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 18 at device 0.0 on pci3 re0: Using 1 MSI messages re0: Chip rev. 0x28000000 re0: MAC rev. 0x00000000 miibus0: <MII bus> on re0 rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 1c:6f:65:4a:85:a7 atapci0: <ATI IXP700/800 SATA300 controller> port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 19 at device 17.0 on pci0 atapci0: AHCI v1.20 controller with 4 6Gbps ports, PM supported ata2: <ATA channel 0> on atapci0 ata3: <ATA channel 1> on atapci0 ata4: <ATA channel 2> on atapci0 ata5: <ATA channel 3> on atapci0 ohci0: <OHCI (generic) USB controller> mem 0xfe02e000-0xfe02efff irq 18 at device 18.0 on pci0 usbus0: <OHCI (generic) USB controller> on ohci0 ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe02d000-0xfe02d0ff irq 17 at device 18.2 on pci0 usbus1: EHCI version 1.0 usbus1: <EHCI (generic) USB 2.0 controller> on ehci0 ohci1: <OHCI (generic) USB controller> mem 0xfe02c000-0xfe02cfff irq 18 at device 19.0 on pci0 usbus2: <OHCI (generic) USB controller> on ohci1 ehci1: <EHCI (generic) USB 2.0 controller> mem 0xfe02b000-0xfe02b0ff irq 17 at device 19.2 on pci0 usbus3: EHCI version 1.0 usbus3: <EHCI (generic) USB 2.0 controller> on ehci1 pci0: <serial bus, SMBus> at device 20.0 (no driver attached) atapci1: <ATI IXP700/800 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0 ata0: <ATA channel 0> on atapci1 ata1: <ATA channel 1> on atapci1 pci0: <multimedia, HDA> at device 20.2 (no driver attached) isab0: <PCI-ISA bridge> at device 20.3 on pci0 isa0: <ISA bus> on isab0 pcib4: <ACPI PCI-PCI bridge> at device 20.4 on pci0 pci4: <ACPI PCI bus> on pcib4 re1: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port 0xbe00-0xbeff mem 0xfdcff000-0xfdcff0ff irq 20 at device 6.0 on pci4 re1: Chip rev. 0x10000000 re1: MAC rev. 0x00000000 miibus1: <MII bus> on re1 rgephy1: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re1: Ethernet address: 00:14:d1:1b:ab:b6 re2: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port 0xbc00-0xbcff mem 0xfdcfe000-0xfdcfe0ff irq 23 at device 8.0 on pci4 re2: Chip rev. 0x10000000 re2: MAC rev. 0x00000000 miibus2: <MII bus> on re2 rgephy2: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus2 rgephy2: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re2: Ethernet address: 00:14:d1:1d:8d:da fwohci0: <Texas Instruments TSB43AB23> mem 0xfdcfd000-0xfdcfd7ff,0xfdcf8000-0xfdcfbfff irq 22 at device 14.0 on pci4 fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:13:1f:78:00:1c:6f:65 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: <IEEE1394(FireWire) bus> on fwohci0 fwe0: <Ethernet over FireWire> on firewire0 if_fwe0: Fake Ethernet address: 02:13:1f:1c:6f:65 fwe0: Ethernet address: 02:13:1f:1c:6f:65 fwip0: <IP over FireWire> on firewire0 fwip0: Firewire address: 00:13:1f:78:00:1c:6f:65 @ 0xfffe00000000, S400, maxrec 2048 sbp0: <SBP-2/SCSI over FireWire> on firewire0 dcons_crom0: <dcons configuration ROM> on firewire0 dcons_crom0: bus_addr 0x6c91c000 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode ohci2: <OHCI (generic) USB controller> mem 0xfe02a000-0xfe02afff irq 18 at device 20.5 on pci0 usbus4: <OHCI (generic) USB controller> on ohci2 pcib5: <ACPI PCI-PCI bridge> at device 21.0 on pci0 pci5: <ACPI PCI bus> on pcib5 atapci2: <JMicron JMB363 UDMA133 controller> port 0xaf00-0xaf07,0xae00-0xae03,0xad00-0xad07,0xac00-0xac03,0xab00-0xab0f mem 0xfd9fe000-0xfd9fffff irq 17 at device 0.0 on pci5 atapci3: <AHCI SATA controller> on atapci2 atapci3: AHCI v1.00 controller with 2 3Gbps ports, PM supported ata6: <ATA channel 0> on atapci3 ata7: <ATA channel 1> on atapci3 ata8: <ATA channel 0> on atapci2 pcib6: <ACPI PCI-PCI bridge> at device 21.1 on pci0 pci6: <ACPI PCI bus> on pcib6 ohci3: <OHCI (generic) USB controller> mem 0xfe029000-0xfe029fff irq 18 at device 22.0 on pci0 usbus5: <OHCI (generic) USB controller> on ohci3 ehci2: <EHCI (generic) USB 2.0 controller> mem 0xfe028000-0xfe0280ff irq 17 at device 22.2 on pci0 usbus6: EHCI version 1.0 usbus6: <EHCI (generic) USB 2.0 controller> on ehci2 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x73 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 orm0: <ISA Option ROM> at iomem 0xc0000-0xcefff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range hwpstate0: <Cool`n'Quiet 2.0> on cpu0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 ad4: 76293MB <Seagate ST380013AS 8.12> at ata2-master UDMA100 SATA 1.5Gb/s ugen0.1: <ATI> at usbus0 uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 ugen1.1: <ATI> at usbus1 uhub1: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 ugen2.1: <ATI> at usbus2 uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2 ugen3.1: <ATI> at usbus3 uhub3: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3 ugen4.1: <ATI> at usbus4 uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4 ugen5.1: <ATI> at usbus5 uhub5: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5 ugen6.1: <ATI> at usbus6 uhub6: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6 GEOM: ad4s1: geometry does not match label (255h,63s != 16h,63s). GEOM: ad4s2: geometry does not match label (255h,63s != 16h,63s). GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s). uhub4: 2 ports with 2 removable, self powered uhub5: 4 ports with 4 removable, self powered uhub0: 5 ports with 5 removable, self powered uhub2: 5 ports with 5 removable, self powered GEOM: ufsid/4dbbdc8f8958f084: geometry does not match label (255h,63s != 16h,63s). uhub6: 4 ports with 4 removable, self powered uhub1: 5 ports with 5 removable, self powered uhub3: 5 ports with 5 removable, self powered ugen2.2: <Chicony> at usbus2 ukbd0: <Chicony USB Keyboard, class 0/0, rev 1.10/3.90, addr 2> on usbus2 kbd2 at ukbd0 uhid0: <Chicony USB Keyboard, class 0/0, rev 1.10/3.90, addr 2> on usbus2 SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad4s1a [rw]... May 1 15:03:00 MACH-0 login: ROOT LOGIN (root) ON ttyv0 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! I been watching that and re-boot syncer being out of sequence forever and now it's fixed. It's the kind of thing only someone like me who has nothing better to do would notice. That's why I don't know jack. All I ever done was to try to find ways to bench-mark something. If more or all mach spec's are needed, just let me know, than you can do the real math. .. .. Again, even without the "options ADAPTIVE_GIANT", that may be now be build-in or replaced by something like the new "tick-less kernel" ... just remember, FreeBSD-AMD 8.1 thru 9.0 current may run perfect on other mother-boards like my "T series TA790GX" but all functions may not work on newer mother-boards like: Board-1 "Gigabyte GA-890GPA-UD3H" Board-2 "Gigabyte GA-880GA-UD3H" because even the mother-board can screwed things up by changing the rules or in the BIOS to help the all-mighty-Windows. This is a thing that the FreeBSD developers must start looking into. It is out of our hands. PcBSD install will work, but the only thing I'm going to miss is the easy cut-and-paste in FreeBSD terminal mode until things get worse in the future. If I would have had a heads-ups about a darn MB, I would have two new "T series" right now bye Last edited by sharris; 3rd May 2011 at 11:21 PM. |
|
|||
I have no idea what you're rambling about, it's very incoherent.. I don't know anything about the FreeBSD forums or their policies, I was just trying to clear up some of the confusion you have.
The PS/2 mouse and keyboard was originally controlled by a chip called the 8042, these days it is emulated by the chipset.. sometimes it can be buggy or not entirely compatible. It is not beyond the realm of possibility for problems to be introduced in the driver, indeed quirks exist for all sorts of hardware.. What I was trying to explain to you was that the phrase "GIANT LOCK" is a technical term for a temporary locking solution for data concurrency.. when SMP is being implemented it is often easier to work on the issue of fine-grained locking as a goal for the future. Computers and operating systems are complex, at least in the BSD community, there is some expectation of the desire to learn about how both things work.. at least on a greater than elementary level. Good luck. Last edited by BSDfan666; 3rd May 2011 at 11:45 PM. |
|
|||
BSDfan666, I'm sorry. I was not complaining for the help you provided, but I shouldn't been complaining about FreeBSD documentation that badly. There are fourty-years worth of technical issues on the net with many solutions. But some are near to impossible to find so I talk just to keep from giving up. I crack jokes so others can laugh and maybe come back latter to see what I'm taking about. I know that people got things to do .
Anyway a old thread came to mind that said " This is FreeBSD, it can configure anything to work" ... right than I thought, if PS2 is not working for this MB, lets search USB possibilities ... than found these and still at it. It took a looong time for the light blub to turn on this round: http://lists.freebsd.org/pipermail/f...ne/050663.html http://www.freebsddiary.org/usb-mouse.php Now I got the USB mouse running in the terminal, but not cut-and-paste. Both threads seem to be out dated because there is no /etc/usbd.conf anymore. Another link say use /etc/devd.conf ... but these lines are not in there and I'm afraid to try just anything because I might mess up my install. Any ideas? Code:
attach "/usr/sbin/moused -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" attach "/usr/sbin/moused -m 2=3 -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" |
|
|||
This is really strange but it worked.
I already had this in my rc.conf for the Gigabyte machine and it never worked ... but it DID on all my other machines for over two years: http://www.unixguide.net/freebsd/fbs..._clear_tmp.htm Code:
moused_enable="YES" moused_port="/dev/psm0" moused_type="auto" moused_flags="-m 2=3" I just found a link that sent me to the right part of FreeBSD Hand Book that said go here <ee /boot/loader.conf> and type these two lines: Code:
include /boot/loader.4th start It worked, now I have cut-and-paste on my Gigabyte. But before I posted this solution, I had to make sure that this is a way to do it so that other may not have any problems. I just commented out those two lines in the boot loader.conf, than reboot and GUEST WHAT ... I still had PS2 with copy-and-paste. My guest is, it must had integrated into the system somehow .. but whatever the case, I am HAPPY again! No need for all that wild stuff to get the USB mouse to work. Sorry Gigabye. It was a configuration issue, but obviously the new technology in Gigabyte BIOS must have forced some kind of change from standard methods that did FreeBSD no favors. Sorry FreeBSD, but your Hand-Book is still out of date, and if I ask you how something works under the hood, don't tell me "don't waste your time ... if it don't like you, it won't work". This is suppose to be open-source, now you guys need a (life-time) driver writer. But like Humphrey Bogart, I never meant to break your heart. http://www.youtube.com/watch?v=nwbqBdghh6E Just another driver issue that can be overcome by FreeBSD for FREE. Add that to Linuxisms like GEM/KMS and INTEL dropping support for the driver that works for FreeBSD because it's FREE. That should be againce the law of computing, with real-life legal consequences Just a thought .. FreeBSD might be able to do it for FREE as long as INTEL driver-writers don't add blocking procedures to stop the FreeBSD loader. Nine out of ten I am wrong, but who can prove it! I hope you find this. OK.. May I be sane again Thank you <EDIT>but it DID on all my other machines for over two years: Last edited by sharris; 7th May 2011 at 02:30 AM. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Xorg & ps/2 mouse | Lumi | NetBSD General | 13 | 20th January 2010 09:38 PM |
USB mouse, ums and wsmouse | useche | OpenBSD General | 5 | 27th July 2009 01:08 AM |
mouse freezes in X | spiderpig | OpenBSD Installation and Upgrading | 0 | 20th April 2009 09:05 AM |
Not nice PS/2 mouse :/ | latorion | FreeBSD General | 21 | 11th October 2008 06:02 PM |
help with usb mouse?? | renej | FreeBSD General | 14 | 18th September 2008 01:25 PM |