Re: Network manager not handling interfaces

[Githin Alapatt <githin gmail com>]

Thanks.

This is what I got -

lrwxrwxrwx 1 root root 0 Nov 22 07:33
/sys/class/net/eth0/device/driver -> ../../../../bus/pci/drivers/sky2

This is what I got. I remember seeing elsewhere that sky2 was my eth0 driver.

I did not build the kernel myself.It is a standard kernel. And, I am
not sure if I upgraded the kernel when I went from lenny to squeeze.

uname -a
Linux debian-githin 2.6.26-2-686 #1 SMP Wed Sep 21 04:35:47 UTC 2011
i686 GNU/Linux



On 11/21/11, Dan Williams <dcbw redhat com> wrote:
> On Mon, 2011-11-21 at 19:28 -0500, Githin Alapatt wrote:
>> Thanks Dan!
>> Those are very much possible. I recently upgraded from lenny to
>> squeeze using apt-get dist upgrade.
>>
>> However, if I configure my eth0 card using the
>> /etc/network/interfaces, things work perfectly.
>
> Hmm, this is quite odd.  It's not showing the hierarchy that we'd expect
> here.  Try this:
>
> ls -al /sys/class/net/eth0/device/driver
>
> and lets see what you get.  You should see something like this:
>
> lrwxrwxrwx. 1 root root 0 Nov 21 13:24 /sys/class/net/eth0/device/driver
> -> ../../../bus/pci/drivers/e1000e
>
> which is where udev should be getting the 'driver' link from.  Did you
> build the kernel yourself, or is it the standard distro kernel?
>
> Dan
>
>> I used ndiswrapper previously to get my wlan working in lenny. Worked
>> perfectly for 2 years until the upgrade.
>>
>> May be I did not upgrade correctly.
>>
>> Here are the outputs.
>>
>> Looking at device '/class/net/eth0':
>>     KERNEL=="eth0"
>>     SUBSYSTEM=="net"
>>     DRIVER==""
>>     ATTR{addr_len}=="6"
>>     ATTR{dev_id}=="0x0"
>>     ATTR{iflink}=="2"
>>     ATTR{ifindex}=="2"
>>     ATTR{features}=="0x10803"
>>     ATTR{type}=="1"
>>     ATTR{link_mode}=="0"
>>     ATTR{address}=="00:23:ae:0c:99:f4"
>>     ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
>>     ATTR{carrier}=="1"
>>     ATTR{dormant}=="0"
>>     ATTR{operstate}=="up"
>>     ATTR{mtu}=="1500"
>>     ATTR{flags}=="0x1003"
>>     ATTR{tx_queue_len}=="1000"
>>
>>   looking at parent device '/class/net':
>>     KERNELS=="net"
>>     SUBSYSTEMS=="subsystem"
>>     DRIVERS==""
>>
>>   looking at device '/class/net/wlan0':
>>     KERNEL=="wlan0"
>>     SUBSYSTEM=="net"
>>     DRIVER==""
>>     ATTR{addr_len}=="6"
>>     ATTR{dev_id}=="0x0"
>>     ATTR{iflink}=="3"
>>     ATTR{ifindex}=="3"
>>     ATTR{features}=="0x1000"
>>     ATTR{type}=="1"
>>     ATTR{link_mode}=="0"
>>     ATTR{address}=="00:23:4e:36:29:0a"
>>     ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
>>     ATTR{operstate}=="down"
>>     ATTR{mtu}=="1500"
>>     ATTR{flags}=="0x1002"
>>     ATTR{tx_queue_len}=="1000"
>>
>>   looking at parent device '/class/net':
>>     KERNELS=="net"
>>     SUBSYSTEMS=="subsystem"
>>     DRIVERS==""
>>
>>
>> 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040
>> PCI-E Fast Ethernet Controller (rev 12)
>> 0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g
>> LP-PHY (rev 01)
>>
>>
>> On 11/21/11, Dan Williams <dcbw redhat com> wrote:
>> > On Thu, 2011-11-17 at 09:25 -0500, Githin Alapatt wrote:
>> >> I recently upgraded from lenny to squeeze. I used to manage my
>> >> networks using the gnome applet.
>> >>
>> >> In the new installation, network manager fails to show up any of my
>> >> network device. I made sure that the interfaces are not listed in
>> >> /etc/network/interface (I commented them out). Still the network
>> >> manager fails to show any device (eth0 and wlan0)
>> >>
>> >> I can use eth0 by configuring it with the /etc/network/interface. That
>> >> works fine.  But, I would like to use the network manager, whenever I
>> >> need to use my laptop on an wi-fi connection.
>> >>
>> >> What else could be wrong?
>> >
>> > These two  lines are the problem:
>> >
>> > Nov 17 23:40:15 debian-githin NetworkManager[3085]: <warn>
>> > /sys/class/net/eth0: couldn't determine device driver; ignoring...
>> > Nov 17 23:40:15 debian-githin NetworkManager[3085]: <warn>
>> > /sys/class/net/wlan0: couldn't determine device driver; ignoring...
>> >
>> > This indicates a problem with either udev or that the kernel network
>> > drivers you're using are buggy.  What kinds of devices are the ethernet
>> > card and the wifi card?  One thing you can do to figure it out is:
>> >
>> > udevadm info --query=all --attribute-walk --path=/sys/class/net/eth0
>> > udevadm info --query=all --attribute-walk --path=/sys/class/net/wlan0
>> >
>> > and reply with the results.
>> >
>> > Dan
>> >
>> >
>>
>>
>
>
>


-- 
http://www.ces.clemson.edu/~galapat/