On Thursday 15 September 2005 16:51, Eberhard Moenkeberg wrote: > It is the same chip and even the same revision as mine. > So why don't you simply try to discard ndiswrapper and start YaST2, > Network, Network card?
I think you misunderstood my post with another. I never used/tried ndiswrapper. I knew my nic was supported via the madwifi driver, regardless of the source of the driver (whether the driver came from the non-gpl kernel rpm or the madwifi source package). I tried the non-gpl kernel rpm. I did not try the madwifi source package -- as I said previously. I didn't have the time to fix the errors in the make file. But I digress... > This way you would not even need to say "modprobe ath_pci" - YaST2 would > do it for you. And modprobing ath_pci didn't help. There is a button on this machine that 'activates' the wireless devices, both wlan and bluetooth. I've read where others have managed to get both bluetooth and wireless working; however, most have had problems due to that button (when to press the button during installation/configuration). And, the installations that I've read about all detailed Fedora Core and/or Ubuntu, not SUSE. -- Christopher Shanahan
pgpn3yMz8oYGa.pgp
Description: PGP signature
