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".

Here's the driver's site:

http://ozlabs.org/people/dgibson/dldwd/

Cheers,

Finegan

Everything seems to be on track now, thanks a lot Finegan. You're my hero.

ARG~

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.

thanks,
andrew

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.

Cheers,

Finegan

Ok~

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