Hi, as the NetworkManager package is not capable of supporting my prism54 card (bug 148210), does someone now whether there are plans for supporting ndiswrapper through NetworkManager? If not, the market for 10.1 will shrink substantially, as at least most notebooks come with wlan cards requiring ndiswrapper for proper function. FMF
On Tue, Mar 07, 2006 at 08:06:17AM +0100, Frank-Michael Fischer wrote:
Hi, as the NetworkManager package is not capable of supporting my prism54 card (bug 148210), does someone now whether there are plans for supporting ndiswrapper through NetworkManager? If not, the market for 10.1 will shrink substantially, as at least most notebooks come with wlan cards requiring ndiswrapper for proper function.
Well, reading the changelog it does support ndiswrapper already. Ciao, Marcus
Marcus Meissner wrote:
Well, reading the changelog it does support ndiswrapper already.
Ciao, Marcus
The problem is getting more complicated: Following my tests, NetworkManager works somehow with ndiswrapper (somehow, as Network Manager supports only DHCP setups), but the ndiswrapper module is not part of the distribution anymore, appearently for license reasons. Which renders ndiswrapper unusable. FMF
Am Dienstag, 7. März 2006 08:06 schrieb Frank-Michael Fischer:
Hi, as the NetworkManager package is not capable of supporting my prism54 card (bug 148210), does someone now whether there are plans for supporting ndiswrapper through NetworkManager? If not, the market for 10.1 will shrink substantially, as at least most notebooks come with wlan cards requiring ndiswrapper for proper function.
Most notebooks came with centrino cards last time I checked MediaMarkt. Do you have market data you want to share with us? Greetings, Stephan
Am Dienstag, 7. März 2006 09:37 schrieb Stephan Kulow:
Am Dienstag, 7. März 2006 08:06 schrieb Frank-Michael Fischer:
Hi, as the NetworkManager package is not capable of supporting my prism54 card (bug 148210), does someone now whether there are plans for supporting ndiswrapper through NetworkManager? If not, the market for 10.1 will shrink substantially, as at least most notebooks come with wlan cards requiring ndiswrapper for proper function.
Most notebooks came with centrino cards last time I checked MediaMarkt. Do you have market data you want to share with us?
Greetings, Stephan
Centrino is an Intel product, so any laptops not using a Pentium M/Core Solo/Core Duo processor (E.g. AMD Turion) won't have a Centrino chipset. Also some Intel laptops don't use Centrino, so they would probably have a 3rd party chipset. And there are still many older laptops out there that are pre-Centrino or don't have built in wireless and use PC Cards for wireless access, and Intel don't sell a PC Card with the wireless chipset from the Centrino collection. I guess it is a case of buying a laptop with a chipset that is supported by Linux if you want to use it with Linux - same as graphics chips, I'll never buy another ATi based laptop for example! Although I must say in SUSE 10.0 (and it is Centrino) is a lot easier to configure and a lot more reliable on the wireless connection front than Windows, SUSE boots up and connects to my WPA-PSK access point, whilst under Windows it sometimes finds, sometimes not, and if you search for it and try and connect, Windows deletes the WPA-PSK configuration information and asks for a WEP passphrase :-( Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck
Frank-Michael Fischer wrote:
Hi, as the NetworkManager package is not capable of supporting my prism54 card (bug 148210), does someone now whether there are plans for supporting ndiswrapper through NetworkManager? If not, the market for 10.1 will shrink substantially, as at least most notebooks come with wlan cards requiring ndiswrapper for proper function.
FMF
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first. FMF
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285 The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case). And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away. -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
On Tuesday 07 March 2006 11:33, James Ogley wrote:
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285
The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case).
And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
Ok, this isn't making much sense to me now. Maybe I'm misunderstanding something here. I thought *proprietary* drivers were being removed, and issued as kmp packages. Now, open source, GPL'd software that gets linked to proprietary software is removed as well? Joseph M. Gaffney aka CuCullin
On Tue, Mar 07, 2006 at 11:45:42AM -0500, Joseph M. Gaffney wrote:
On Tuesday 07 March 2006 11:33, James Ogley wrote:
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285
The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case).
And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
Ok, this isn't making much sense to me now. Maybe I'm misunderstanding something here.
I thought *proprietary* drivers were being removed, and issued as kmp packages. Now, open source, GPL'd software that gets linked to proprietary software is removed as well?
ndiswrapper is in factory and I think on CD1. It has not been removed. Ciao, Marcus
Marcus Meissner wrote:
On Tue, Mar 07, 2006 at 11:45:42AM -0500, Joseph M. Gaffney wrote:
On Tuesday 07 March 2006 11:33, James Ogley wrote:
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285
The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case).
And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
Ok, this isn't making much sense to me now. Maybe I'm misunderstanding something here.
I thought *proprietary* drivers were being removed, and issued as kmp packages. Now, open source, GPL'd software that gets linked to proprietary software is removed as well?
ndiswrapper is in factory and I think on CD1. It has not been removed.
Ciao, Marcus
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org
Marcus, ndiswrapper is out of function if the module is not there, isn't it? So, it does not really matter, whether ndiswrapper is included or not, it's not usable. FMF
Joseph M. Gaffney wrote:
On Tuesday 07 March 2006 11:33, James Ogley wrote:
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285
The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case).
And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
Ok, this isn't making much sense to me now. Maybe I'm misunderstanding something here.
I thought *proprietary* drivers were being removed, and issued as kmp packages. Now, open source, GPL'd software that gets linked to proprietary software is removed as well?
Joseph M. Gaffney aka CuCullin
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org
Exactly, this you can read in bug 155723. Seems some very experienced lawyer went into open source programming here ;-) FMF
James Ogley wrote:
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285
The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case).
And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
Thanks, James, I've tried it already, it works, however, ndiswrapper as module is off the distro. So I've got a workaround for the prism54 problem. So the "standard" user will find prism54 not supported under the present version of NetworkManager. FMF
James Ogley wrote:
As I've just filed bug 155723 - "ndiswrapper module missing" it would be difficult for NetworkManager to support ndiswrapper. Let's wait for the ndiswrapper fix first.
Please note bug #155285
The package you want is ndiswrapper-kmp-<flavour> where <flavour> is the type of kernel you have (smp in my case).
And NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
AJ fixed it right now! Therefore: problem gone, great! It's part of the factory tree already and therefore part of the distro: rug search ndiswrapper S | Catalog | Bundle | Name | Version | Arch --+---------+--------+-------------------------+--------------------------+----- | factory | | ndiswrapper | 1.10-5 | i586 | factory | | ndiswrapper-debuginfo | 1.10-5 | i586 | factory | | ndiswrapper-kmp-bigsmp | 1.10_2.6.16_rc5_git2_3-5 | i586 | factory | | ndiswrapper-kmp-debug | 1.10_2.6.16_rc5_git2_3-5 | i586 | factory | | ndiswrapper-kmp-default | 1.10_2.6.16_rc5_git2_3-5 | i586 | factory | | ndiswrapper-kmp-smp | 1.10_2.6.16_rc5_git2_3-5 | i586 | factory | | ndiswrapper-kmp-xen | 1.10_2.6.16_rc5_git2_3-5 | i586 | factory | | ndiswrapper-kmp-xenpae | 1.10_2.6.16_rc5_git2_3-5 | i586
On Tuesday 07 March 2006 19:07, Frank-Michael Fischer wrote:
It's part of the factory tree already and therefore part of the distro
In my opinion it should be on the cds to be considered part of the distro. Ndiswrapper *and* kmp's (at least ndiswrapper-kmp-default) are crucial to many people. Will everything that's in factory now be on 10.1-final inst-sources? James Ogley wrote:
NetworkManager supports whatever network devices the kernel does, so all you need to do is setup the NDIS driver in ndiswrapper and you're away.
I believe this to be true, but I can't get my Linksys (bcm4306 chipset, using ndiswrapper) to connect using (k)networkmanager - if I choose traditional method via ifup in yast nic module it connects fine (For testing purposes I'm using no encryption and dhcp - should be simple enough). Whether this problem is networkmanager<>ndiswrapper, networkmanager or knetworkmanager I don't have the slightest idea - but something isn't working right. I suspect some of the other people in this thread have had similar problems. cb400f
On Wed, Mar 08, 2006 at 04:50:12PM +0100, Martin Schlander wrote:
On Tuesday 07 March 2006 19:07, Frank-Michael Fischer wrote:
It's part of the factory tree already and therefore part of the distro
In my opinion it should be on the cds to be considered part of the distro.
I see it differently, especially with the amount of files. You could also argue that it is on the boxed set (most likely) and thus is part of the distro. Also CD's and floppies came after network installation.
Ndiswrapper *and* kmp's (at least ndiswrapper-kmp-default) are crucial to many people.
If it is crucial to get a working network, then it should be on CD1. I would call things crucial for the OS, not crucial for the user, because that will be completely different for each person. So if it is crucial and needed to get the OS working in the way it is intended, then it should be available on CD1. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau
I believe this to be true, but I can't get my Linksys (bcm4306 chipset, using ndiswrapper) to connect using (k)networkmanager - if I choose traditional method via ifup in yast nic module it connects fine (For testing purposes I'm using no encryption and dhcp - should be simple enough).
http://bugzilla.novell.com then - file it as a bug. Include the contents of /var/log/NetworkManager (and add me as a Cc: entry - I'd be interested to monitor it) -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
On 3/8/06, James Ogley
I believe this to be true, but I can't get my Linksys (bcm4306 chipset, using ndiswrapper) to connect using (k)networkmanager - if I choose traditional method via ifup in yast nic module it connects fine (For testing purposes I'm using no encryption and dhcp - should be simple enough).
http://bugzilla.novell.com then - file it as a bug.
Include the contents of /var/log/NetworkManager
(and add me as a Cc: entry - I'd be interested to monitor it) -- excuse me for butting in, but i'm running 10.0 and do
NOT have this file: NetworkManager or knetworkmanager. am i missing something? Peace.....................ed -- Edward Dunagin-Dunigan 4646 Glenwood Drive Bozeman, MT 59718 mobile 406-570-0992
Edward Dunagin wrote:
NOT have this file: NetworkManager or knetworkmanager. am i missing something?
Peace.....................ed
-- Edward Dunagin-Dunigan 4646 Glenwood Drive Bozeman, MT 59718 mobile 406-570-0992
Not missing anything, it hasn't been part of earlier than 10.1 distros. FMF
Include the contents of /var/log/NetworkManager excuse me for butting in, but i'm running 10.0 and do NOT have this file: NetworkManager or knetworkmanager. am i missing something?
No, you're not, versions of SUSE before 10.1 log NetworkManager information to /var/log/messages -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
Martin Schlander wrote:
I believe this to be true, but I can't get my Linksys (bcm4306 chipset, using ndiswrapper) to connect using (k)networkmanager - if I choose traditional method via ifup in yast nic module it connects fine (For testing purposes I'm using no encryption and dhcp - should be simple enough).
Whether this problem is networkmanager<>ndiswrapper, networkmanager or knetworkmanager I don't have the slightest idea - but something isn't working right. I suspect some of the other people in this thread have had similar problems.
One thing I might help with: After installing ndiswrapper and loading the module I did not manage to get NetworkManager working with the WLAN device right away. A reboot was necessary, not even init 1 -> init 3 helped. Didn't have time to figure out why. FMF
participants (9)
-
David Wright -
Edward Dunagin -
Frank-Michael Fischer -
houghi -
James Ogley -
Joseph M. Gaffney -
Marcus Meissner -
Martin Schlander -
Stephan Kulow