I've installed CentOS 4.3 effortlessly, that is without being able to create a dual boot system but I'm over that now. Everything works except of course for my wireless network.
It's a Linksys (WMP11v4) 802.11b network, lspci tells me there is an appropriate ethernetcard but the OS can't find a wireless network.
I've done some homework on this and it seems to me the only way to get this to work is by using Linksys drivers with Ndiswrapper and recompiling the Kernel. Sounds very interesting but I'm too n00b for that atm.

- Q1: is there no other way to get my Linksys wireless to work?

- Q2: if I would attempt to get Ndiswrapper to work, I'm gonna need the sources from the kernel. Being on CentOS 4.3 (a RH clone) and typing "rpm -q kernel-source" gives me "package kernel-source is not installed". Would that mean bad luck for me or do I need to look for another package with sources on CentOS 4.3?

The local situation is such that simply laying a cable to the router would be more complicated than trying to customize the system. I also couldn't re-install Windows (CD did boot but didn't install anything) to use the wireless via Windows so I'm a bit caught between a rock and a hard place.


Edit: wrong forum, excuse me. Is there a mod who wants to move this to the wireless networking forum?

My guess is kernel-source is probably the name of the rpm package. When installed, it is generally installed in /usr/src, in a directory whose name reflects the version of the kernel in question. So might just look there. You also might check your installation CD(s) to see if maybe the kernel-source RPM exists there, in which case you can just install it.

Sorry, I can't help you with the rest of your questions.

Can you possibly afford a new card with a Reaktek chipset. I think you're going to have a hard time with that one even using ndiswrapper, which IMO is a bad idea anyway.

Thank you, that's where I indeed found it. I got confused by using a book and some RH docs.

Thank you for your answer. I think you mean "Realtek, or any other supported chipset"? That makes very much sense as it would get me where I want without jumping through hoops. It's annoying because it was a working network and all it would take was more support from Linksys, I gather.
I don like the ndiswrapper idea either but that's mainly because it seems a hassle and rather difficult. You don't seem to like the ndiswrapper route for other reasons, care to enlighten me?

Hi, I'd not recommend ndiswrapper (this is "just" a stub for usind your Wondows drivers under Linux), I had good success with madwifi-driver, its worth to checkout, whether madwifi supports your card !!

I've taken the 'easy' way:
- long discussion with landlord,
- powerdrill (several bits + extension cord),
- bucket of sweat,
- couple of hours,
- some bruises & curses,
- folding body(parts) in highly unusual ways,
- meeting some creatures I never knew existed.
Several walls and tunnels later I was able to click the ethernet cable into the router and my installed OS wanted to update. Problem solved.
It's what I like about computing, you sit relaxed, nice and dry, only move your arms and hands unless you have to go to the fridge/toilet....

I was about to suggest that you first check if there isn't an RPM of ndiswrapper already built for your distro version that is known to work with (a specific Windows driver for) this card. Some guides out there are written for older distros where a needed kernel option was available but not enabled, or for lean/mean kernels where only the bare minimum is enabled by default. Your distro may already have the required kernel option enabled and a ndiswrapper package available.

But you've gone with ethernet - at least you won't have to face any problems of poor wireless signal and choppy connection.