Date: Mon, 13 Apr 2009 20:38:28 +0200 From: piotr.smyrak@heron.pl To: Michal Varga <varga.michal@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: no USB mice detected on GA-MA74GM-S2 Message-ID: <20090413104255.M2582@heron.pl> In-Reply-To: <3f1fd1ea0904121735t3220cf7dyfce5221a35d7944@mail.gmail.com> References: <20090408190805.GA1368@smyrak.com> <20090408224925.3dd1f8ab@zelda.local> <20090409104532.M16424@heron.pl> <20090412151547.M42910@heron.pl> <3f1fd1ea0904121512m21cfb40crb2e16fa1841f3cb5@mail.gmail.com> <20090412224548.M53466@heron.pl> <3f1fd1ea0904121735t3220cf7dyfce5221a35d7944@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Apr 2009 02:35:37 +0200, Michal Varga wrote > 2009/4/13 <piotr.smyrak@heron.pl>: > >> ). A quick workaround is to attach your mouse (or any > >> other USB device that dies during boot - mices, keyboards, > >> card readers, etc. do this with FreeBSD 6/7's usb1 and > >> Gigabyte boards) -after- all USB drivers are loaded and > >> initialized. That always works. > > > > Unfortunately not in my case. I have tried this path before > > without success. > > Are you sure you plugged the mouse out, then powered the > computer on, and plugged the mouse back in only after > FreeBSD fully finished booting? To make it perfectly > redundantly safe, let's say, plugged mouse in at the login > prompt? Because I'm 100% positive (well, me and everyone > else with any recent Gigabyte board that I know) that > plugging the device in after the USB drivers are fully initialized > will prevent the lockup and port timeout, always. Yes, I'm 100% positive I tried plugging mouse after the boot up had finished. Honestly I am late asking here. I was struggling with this and looking for cases online for more than 2 weeks at least. And I came across your thread from 2007, too. > >> Still, having it properly fixed in usb1 drivers wouldn't > >> hurt, of course, > > > > How do you go about that? I mean fixing a device in usb1.1. > > > Well, I guess that would need someone with both FreeBSD > USB expertise and some interest in fixing that bug (and > probably an access to particular Gigabyte hardware, though > as it seems so far, anything recent from Gigabyte and > probably AMD6xx/7xx based will do it). Anyway, I tried > reporting it back then in 2007, all I got was a bunch of > arguments about power source fluctuations, carbon > footprints, Windows, PS/2 mices (for christ sake..), and > well, being a lazy coward, I gave up. Maybe you'll be > luckier this time. Well, I don't like the idea of giving up. I have been using the OS since the 90's, almost exclusively and that's the first time I got such unresolvable problems. But I need a functional work environment. -- Piotr Smyrak piotr.smyrak@heron.pl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090413104255.M2582>