Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I gotcha, is dmesg spammed with timeout errors to the firmware? I think -110 cannot connect to BAP or somesuch? Its a firmware timing bug with the prism2.5-esque firmware. Its been more or less solved in the .13x series of the orinoco driver, you've got .11b if your running RH stock kernels.
This almost always makes quick with a simple "make", "make install".
Well, my wireless nic works fine, but since I downloaded these new modules I've been having serious boot problems. After I try to load Slackware from Lilo, it echos that it is loading linux, but all of a sudden the little dots stop.
i'm assuming this means that i'm supposed to pass the kernel some special option for these drivers, but i have no idea what.
I doubt they're related... that's a little, well... odd. You can use the Slack CD as a boot disk and just pass it root options at the prompt, then take a look at lilo, maybe re-run it and see if it spits errors. There's an outside chance that the orinoco update might have confused hotplugging support... might want to run a "depmod -a", but I think that was part of "make install". Offhand I think they're unrelated... probably.
I removed the orinoco modules, and it booted up fine, so I think the problem was definitely the modules. Anyway, I checked depmod and was getting some unresolved symbols. I figured this might have been because these modules had the same name as the old ones, but were actually different.
I recompiled my kernel, then inserted the modules I needed, and (so far) everything is workking according to plan.
Thanks a lot finegan,
Andrew
PS> I just got done reading about the farm. kersweeeeeeeet
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.