Re: Latest Ndiswrapper

2006-04-07 Thread Paul Stodghill
Perfect. You have the same card as me (I think). Let's see if I can reproduce your success on my machine. Could you post your recipe for configuring/compiling/installing NetworkManager and ndiswrapper? What version of the Windows driver are you using? Also, could you post the output of "Netw

Re: Latest Ndiswrapper

2006-04-06 Thread Paul Stodghill
Joseph Harnish wrote: All, I have been experiencing issues with ndiswrapper, NetworkManager, and wpa_supplicant. As of today's ndiswrapper-1.12 release the issues I have been experiencing have gone away. NM still doesn't work with my ndiswrapper card. Can you tell me how you have configure

What wireless manager for FC5? [was Re: NetworkManager FC5 -- No WEP key]

2006-03-27 Thread Paul Stodghill
Nathaniel McCallum wrote: Done: http://bugzilla.gnome.org/show_bug.cgi?id=336221 Any chance of getting the workaround patch in the next NM package for FC5? This would at least give ndiswrapper, etc a chance to get their act together without punishing the end users (ie. make it clear the patch i

Troubleshooting NM

2006-03-21 Thread Paul Stodghill
I just upgraded to FC5, and NM no longer works for my ndiswrapper-enabled wireless card. I looked, but I can't seem to find a troubleshooting guide for NM. Is there such a beast? Thanks. ___ NetworkManager-list mailing list NetworkManager-list@gnome.

Re: NM 0.5.1 and ndiswrapper fails (with workaround)

2005-11-12 Thread Paul Stodghill
Tchak wrote: I don't have command "tree", and I don't know what is it. If you point my in the right direction I would gladly send output to the list. On a Fedora system, you might try "yum install tree". Good luck. barney-lx$ rpm -q --info tree Name: tree Reloca

Re: NM 0.5.1 and ndiswrapper fails (with workaround)

2005-11-12 Thread Paul Stodghill
Dan Williams wrote: So, next command: tree /sys/class/net/wlan0/../../../devices/pci:00/:00:1e.0/:02:01.1/1.0 I did not get anything for that command - I don't have any "02:01.1" on my PCI bus. "02:01.0" is my ethernet card. However, my wireless card is on 02:02.0. Hope this h

Re: NM 0.5.1 generates bogus resolv.conf (with fix)

2005-11-12 Thread Paul Stodghill
Dan Williams wrote: Yep, that's in HEAD. We need to yell at Chris to push an update to FC-4 updates... Dan Excellent. Thanks. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanage

Re: NM 0.5.1 and ndiswrapper fails (with workaround)

2005-11-12 Thread Paul Stodghill
Dan Williams wrote: This is actually a bug in ndiswrapper. With the card in, can you do: tree /sys/class/net/wlan0 and send the output to this list? Thanks! Dan Here it is. Hope this helps. barney-lx# tree /sys/class/net/wlan0 /sys/class/net/wlan0 |-- addr_len |-- address |-- broadcast |

NM 0.5.1 generates bogus resolv.conf (with fix)

2005-11-11 Thread Paul Stodghill
NetworkManager 0.5.1 generates an /etc/resolv.conf in which the IP of the primary name server is used for _all_ name servers. If the primary name server is unavailable for some reason, then the network connection is, err, less than useful. This problem is the result of a small bug in nm-named-

NM 0.5.1 and ndiswrapper fails (with workaround)

2005-11-10 Thread Paul Stodghill
Summary: NM 0.5.1 does not recognize some(all?) ndiswrapper drivers as "supported". Workaround is described My wireless network interface is a Dell 1300 or 1400 PC Card (BCM4306). Since an appropriate native Linux driver is not available for this card, I am using ndiswrapper and the native Win