KNetworkManager and Dell Truemobile 1450 wireless

Hi all,

With the previous versions of SuSE I used to install ndiswrapper to have
the wireless card running. Now, after an amazing installation of
opensuse 10.2, I see my wireless network card's module already in the
kernel and ready to be used. The problem is that actually I can't use
it. Firstly, it's recognized as eth1 which makes it impossible to
managed through "iw" and "iwlist". Secondly it doesn't work if I
configure it via YaST. Does anyone experienced that? Should I get back
to ndiswrapper and forget about the kernel module?

TIA,
Jan Kalcic

jan kalcic wrote:

> Hi all,
>
> With the previous versions of SuSE I used to install ndiswrapper to have
> the wireless card running. Now, after an amazing installation of
> opensuse 10.2, I see my wireless network card's module already in the
> kernel and ready to be used. The problem is that actually I can't use
> it. Firstly, it's recognized as eth1 which makes it impossible to
> managed through "iw" and "iwlist". Secondly it doesn't work if I
> configure it via YaST. Does anyone experienced that? Should I get back
> to ndiswrapper and forget about the kernel module?

Just because the wireless adapter is found doesn't mean the drivers are
properly loaded. Since you didn't mention which wireless card you've got,
either Google for "name-of-card + openSUSE 10.3" or just use ndiswrapper.

Malke
--
Keep to the code.

jan kalcic wrote:

> Hi all,
>
> With the previous versions of SuSE I used to install ndiswrapper to have
> the wireless card running. Now, after an amazing installation of
> opensuse 10.2, I see my wireless network card's module already in the
> kernel and ready to be used. The problem is that actually I can't use
> it. Firstly, it's recognized as eth1 which makes it impossible to
> managed through "iw" and "iwlist". Secondly it doesn't work if I
> configure it via YaST. Does anyone experienced that? Should I get back
> to ndiswrapper and forget about the kernel module?
>
> TIA,
> Jan Kalcic

What you need to do now is cut the firmware out of the driver you used for
ndiswrapper and put the file in your /var/lib directory ... the cutter is
called bcm43xxfwcutter ... look for it in yast software management... if
its not there then a google search will find it ... I have the dell TM 1300
card in my laptop that I have been using ndiswrapper with in 9.2 - 10.1 ...
or you can still use ndiswrapper ..

Malke wrote:
> jan kalcic wrote:
>
>> Hi all,
>>
>> With the previous versions of SuSE I used to install ndiswrapper to have
>> the wireless card running. Now, after an amazing installation of
>> opensuse 10.2, I see my wireless network card's module already in the
>> kernel and ready to be used. The problem is that actually I can't use
>> it. Firstly, it's recognized as eth1 which makes it impossible to
>> managed through "iw" and "iwlist". Secondly it doesn't work if I
>> configure it via YaST. Does anyone experienced that? Should I get back
>> to ndiswrapper and forget about the kernel module?
>
> Just because the wireless adapter is found doesn't mean the drivers are
> properly loaded. Since you didn't mention which wireless card you've got,
> either Google for "name-of-card + openSUSE 10.3" or just use ndiswrapper.
>
> Malke

The wireless card name is in Subject.

EMG wrote:
> jan kalcic wrote:
>
>> Hi all,
>>
>> With the previous versions of SuSE I used to install ndiswrapper to have
>> the wireless card running. Now, after an amazing installation of
>> opensuse 10.2, I see my wireless network card's module already in the
>> kernel and ready to be used. The problem is that actually I can't use
>> it. Firstly, it's recognized as eth1 which makes it impossible to
>> managed through "iw" and "iwlist". Secondly it doesn't work if I
>> configure it via YaST. Does anyone experienced that? Should I get back
>> to ndiswrapper and forget about the kernel module?
>>
>> TIA,
>> Jan Kalcic
>
> What you need to do now is cut the firmware out of the driver you used for
> ndiswrapper and put the file in your /var/lib directory ... the cutter is
> called bcm43xxfwcutter ... look for it in yast software management... if
> its not there then a google search will find it ... I have the dell TM 1300
> card in my laptop that I have been using ndiswrapper with in 9.2 - 10.1 ...
> or you can still use ndiswrapper ..
>
>

mmm... good to know. I'll try it.

Jan

Malke wrote:

> properly loaded. Since you didn't mention which wireless card you've got,
> either Google for "name-of-card + openSUSE 10.3" or just use ndiswrapper.

i got so sick and tired of making wireless cards work under linux. so
now ndiswrapper is the only thing i use. it's easy, takes 3 minutes...
and blam i got wifi everytime...

--
dan stephenson :: linux/perl/xml <> http://spydev.ath.cx
irc_ #perl @ freenode.net <> email_ ispyhumanfly@gmail.com

jan kalcic wrote:
> EMG wrote:
>> jan kalcic wrote:
>>
>>> Hi all,
>>>
>>> With the previous versions of SuSE I used to install ndiswrapper to have
>>> the wireless card running. Now, after an amazing installation of
>>> opensuse 10.2, I see my wireless network card's module already in the
>>> kernel and ready to be used. The problem is that actually I can't use
>>> it. Firstly, it's recognized as eth1 which makes it impossible to
>>> managed through "iw" and "iwlist". Secondly it doesn't work if I
>>> configure it via YaST. Does anyone experienced that? Should I get back
>>> to ndiswrapper and forget about the kernel module?
>>>
>>> TIA,
>>> Jan Kalcic
>> What you need to do now is cut the firmware out of the driver you used for
>> ndiswrapper and put the file in your /var/lib directory ... the cutter is
>> called bcm43xxfwcutter ... look for it in yast software management... if
>> its not there then a google search will find it ... I have the dell TM 1300
>> card in my laptop that I have been using ndiswrapper with in 9.2 - 10.1 ...
>> or you can still use ndiswrapper ..
>>
>>
>
> mmm... good to know. I'll try it.
>
> Jan

OK guys, I tried it but didn't work for me. Anyway, holy ndiswrapper is
always close to me and I can keep on writing you from kitchen, bathroom
and etc etc...

However, there's still a problem. The module bcm43xx, the one which is
automatically loaded at boot time, is removed using blacklist.
Ndiswrapper instead doesn't load automatically at boot but only manually
using modprobe even though its configuration file seems properly placed
in /etc/modprobe.d/ndiwrapper.
Idea?

Jan

jan kalcic wrote:

> in /etc/modprobe.d/ndiwrapper.
> Idea?

You have to either add it to yast or tell the module to load on boot. Look
the the section labeled "Making the connection perminant" with the
following document.
https://secure-support.novell.com/Ka...AL_Public.html

linuxjoe wrote:
> jan kalcic wrote:
>
>> in /etc/modprobe.d/ndiwrapper.
>> Idea?
>
> You have to either add it to yast or tell the module to load on boot. Look
> the the section labeled "Making the connection perminant" with the
> following document.
> https://secure-support.novell.com/Ka...AL_Public.html

Thanks. But why do I have to do that when it is configured in modprobe?
I don't understand why it's necessary to add the module in that string
whereas with the previous version it was not.