Results 1 to 2 of 2
Hi I'm a total linux novice but have been doing my best in reading up to try and acheive what I've been trying to acheive for over a week! I ...
- 10-25-2006 #1Just Joined!
- Join Date
- Mar 2005
- Posts
- 8
Help - STILL can't get ndiswrapper working on Suse10.1!
Hi I'm a total linux novice but have been doing my best in reading up to try and acheive what I've been trying to acheive for over a week! I have a new Asus A6M series laptop which came with XP Home, I wanted a dual boot with Suse 10.1.
I have managed to install Suse but am having a few key problems. I believe that many of these problems could be ironed out if I was just able to connect my Suse boot to the internet and then effect some YUM (for instance I'm having nVIDIA problems but would rather fix via Yast than mess about with my kernels).
I have followed as many threads as possible regarding setting up my WLAN (using the bcmwl5 driver .inf & .sys for my Broadcom BCM4318 802.11g WLAN) and have installed the ndiswrapper via Yast. Although I follow the instructions down to the letter, and when I ask:
ndiswrapper -l
Installed ndis drivers
bcmwl5 installed, hardware present
when I then do
modprobe ndiswrapper
iwconfig
I have no wireless connections available. I have been through Yast to try and force it to recognise some by putting in the configs but to no avail and am banging my head against the wall to figure what is going wrong! I am 99% sure I am using the right versions of ndiswrapper and drivers.....
any ideas before my head goes through the wall??
oh yeah, I've also added the:
alias wlan0 ndiswrapper
into my modprobe.conf file - although I realise this is a bit of a nonsense when my box can't see a wlan0!
On another related note, I haven't been able to get my laptop working even via direct ethernet plug in, Suse 10.1 doesn't seem to want to recognise an eth0 either! I needn't add that both ethernet connection and WLAN are working just fine in XP.
- 10-25-2006 #2
After "ndiswrapper -l" you must type (and the driver and hardware are present):
then you should do:Code:ndiswrapper -m
Did you take that step? Cus that's a crucial one...Code:modprobe ndiswrapper


Reply With Quote