For some reason the Network Manager chooses the wrong driver. I was just wondering if anybody knows why and if there’s a way to correct it. It’s supposed to be using a rndis driver; but occasionally it recognizes it as an eth device.
The rndis driver is a a modified driver that allows me use the 3G connection on my cell phone for internet via usb tethering. Which is pretty much the only I can get online at the moment.
psyber.netik@bitslip:~> lsmod |grep -i ndis
rndis_host 7236 0
cdc_ether 9064 1 rndis_host
usbnet 15608 2 rndis_host,cdc_ether
usbcore 165892 9 rndis_host,cdc_ether,usbnet,usb_storage,usbhid,uvcvideo,ehci_hcd,uhci_hcd
psyber.netik@bitslip:~> ps -ef |grep -i network
root 3371 1 0 09:21 ? 00:00:00 /usr/sbin/NetworkManager
root 3379 1 0 09:21 ? 00:00:00 /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf
1000 3801 1 0 09:21 ? 00:00:38 /opt/kde3/bin/knetworkmanager
root 10038 3371 0 09:44 ? 00:00:00 /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-rndis0.pid -lf /var/lib/dhcp/dhclient.leases -cf /var/run/nm-dhclient-rndis0.conf rndis0
psybernetik wrote:
> For some reason the Network Manager chooses the wrong driver. I was just
> wondering if anybody knows why and if there’s a way to correct it. It’s
> supposed to be using a rndis driver; but occasionally it recognizes it
> as an eth device.
What makes you think that NetworkManager chooses a driver? Drivers are
always selected based on the PCI or USB ID codes. If your system is
getting the wrong one, you need to blacklist it and load the correct
one. Both topics have been discussed many times in these forums. You
can do some reading and figure it out.
Have a look at this general guide regarding ndiswrapper and blacklisting other drivers:
Wireless LAN in Linux - Linux Forums
Sorry all… It wasn’t Suse’s fault…
Info:
Acer Aspire 5610Z
2GB RAM
Suse 11.1
Modified NDIS driver (HOWTO: Tether AT&T Fuze to Ubuntu [Archive] - Ubuntu Forums)
Device:
AT&T HTC Fuze (P-4600)
Modified registry (HOWTO: Tether AT&T Fuze to Ubuntu [Archive] - Ubuntu Forums)
The problem was that my phone can behave in two different modes; Storage device (SD) and Cell Phone (ActiveSync). Linux pretty much disregards the “operating methods” for both when connected. The fix is to pretty much kill KNetworkManager, unmount the disk if it was mounted, IFDOWN the interface if still up, and physically disconnect it.
Depending on what you want to do; access the SD card or tether for internet, you have to change the START>SETTINGS>CONNECTONS>USB TO PC setting. If you want to tether then select ActiveSync. If you want to access the SD card then select Disk Drive. If you are already on the setting you want to be on then select the other option hit okay and go back in and change it; WM sometimes needs to be reminded on what to do. 
After that connect it via the USB/Mini USB cable.
The issue I was having was that I had it set to be used as a Disk Drive and the KNM was that it was a possible networking device and acted accordingly. But, since it was set to Disk Drive there was mismatch of protocols. So, it set it as your generic/common networking device; i.e. eth* devices.
If you have trouble feel free post a new thread and PM me the thread so I know.
P.S. Keep an eye on the IFCONFIG and DMESG… It’ll tell you what its… thinking?
Thanks for the update. I’m sure it will be useful to others. 