Michael

Linux-kernel drivers, I believe.  They are compiled from Debian's linux-2.6 source package.

ls -la /sys/class/net/wlan0/device
lrwxrwxrwx 1 root root 0 2010-02-09 14:28 /sys/class/net/wlan0/device -> ../../../devices/pci0000:00/0000:00:1c.1/0000:02:00.0

ls -la /dev/sys/net/eth0/device
ls: cannot access /dev/sys/net/eth0/device: No such file or directory

also:

ls -la /sys/class/net/eth0/device
lrwxrwxrwx 1 root root 0 2010-02-09 14:28 /sys/class/net/eth0/device -> ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0

The drivers worked OK until yesterday's update, which did not involve the kernel.

John

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQU...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Can't you install an original Debian kernel in parallel and test it.

Sorry for the typo, please run

ls -la /sys/class/net/wlan0/device/
ls -la /sys/class/net/eth0/device/

The point is, that network-manager is using udev now, for device enumeration.

I'll wait for your output of ls -la, but be prepared that I'm going to close
this bug, as this is not a network-manager, but a driver issue. And as you don't
use a Debian kernel, I can't reassign this bug report.

Cheers,
Michael

--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

signature.asc < 1K Hämta

Micheal,

If you mean a Debian stock kernel, the problem is that these kernels make
extensive use of modular drivers, which I do not use at all.  Hence, I suspect,
using one of these kernels would involve me in extensive reconfiguration.
I suspected it was a typo, which is why I already sent the one you wanted.

lrwxrwxrwx 1 root root 0 2010-02-09 14:28 /sys/class/net/wlan0/device ->
../../../devices/pci0000:00/0000:00:1c.1/0000:02:00.0

lrwxrwxrwx 1 root root 0 2010-02-09 14:28 /sys/class/net/eth0/device ->
../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0

Are these the symlinks you were expecting?

In what way is it not a Debian kernel?  It is compiled in the Debian way using
Debian packages from a Debian source.

If NetworkManager cannot work with in-kernel drivers then surely that in itself
is a bug.

Cheers

John

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQU...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Michael

Even if I did it would not help.  Presumably NetworkManager works with a
kernel that uses external kernel modules.  The problem I have is that it
is not working with a kernel that has the drivers compiled into it.

It seems as if the interface is present, it is just that NetworkManager
is not finding it.  Presumably, since "The point of NetworkManager is to
make networking configuration and setup as painless and automatic as
possible." it should find any network devices if they are present.

In my case it seems as if NetworkManager is not following the symlink:

So if I look at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0 I get:

ls -la /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0
total 0
drwxr-xr-x 3 root root     0 2010-02-10 05:04 .
drwxr-xr-x 7 root root     0 2010-02-10 05:04 ..
-rw-r--r-- 1 root root  4096 2010-02-10 06:40 broken_parity_status
lrwxrwxrwx 1 root root     0 2010-02-10 06:40 bus -> ../../../../bus/pci
-r--r--r-- 1 root root  4096 2010-02-10 06:40 class
-rw-r--r-- 1 root root  4096 2010-02-10 06:40 config
-r--r--r-- 1 root root  4096 2010-02-10 06:40 device
lrwxrwxrwx 1 root root     0 2010-02-10 06:40 driver ->
../../../../bus/pci/drivers/r8169
-rw------- 1 root root  4096 2010-02-10 06:40 enable
lrwxrwxrwx 1 root root     0 2010-02-10 06:40 firmware_node ->
../../../LNXSYSTM:00/device:00/PNP0A08:00/device:12/device:13
-r--r--r-- 1 root root  4096 2010-02-10 06:40 irq
-r--r--r-- 1 root root  4096 2010-02-10 06:40 local_cpulist
-r--r--r-- 1 root root  4096 2010-02-10 06:40 local_cpus
-r--r--r-- 1 root root  4096 2010-02-10 06:40 modalias
-rw-r--r-- 1 root root  4096 2010-02-10 06:40 msi_bus
lrwxrwxrwx 1 root root     0 2010-02-10 06:40 net:eth0 ->
../../../../class/net/eth0
drwxr-xr-x 2 root root     0 2010-02-10 06:40 power
--w--w---- 1 root root  4096 2010-02-10 06:40 remove
--w--w---- 1 root root  4096 2010-02-10 06:40 rescan
-r--r--r-- 1 root root  4096 2010-02-10 06:40 resource
-rw------- 1 root root   256 2010-02-10 06:40 resource0
-rw------- 1 root root  4096 2010-02-10 06:40 resource2
-rw------- 1 root root  4096 2010-02-10 06:40 resource2_wc
-rw------- 1 root root 65536 2010-02-10 06:40 resource4
-rw------- 1 root root 65536 2010-02-10 06:40 resource4_wc
-r-------- 1 root root 65536 2010-02-10 06:40 rom
lrwxrwxrwx 1 root root     0 2010-02-10 06:40 subsystem ->
../../../../bus/pci
-r--r--r-- 1 root root  4096 2010-02-10 06:40 subsystem_device
-r--r--r-- 1 root root  4096 2010-02-10 06:40 subsystem_vendor
-rw-r--r-- 1 root root  4096 2010-02-10 06:40 uevent
-r--r--r-- 1 root root  4096 2010-02-10 06:40 vendor
-rw------- 1 root root 32768 2010-02-10 06:40 vpd

Which seems to be what you were looking for.

John

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQU...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

reopen 568977
reassign 568977 network-manager
thanks

Indeed. Let's reopen the bug report and reassign it to network-manager for now.
Now we need to find out it that is a problem in udev/libgudev or the way NM is
using libgudev.

Could you send me the versions of udev/libudev/libgudev you are using, please.

Thanks,
Michael

--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

signature.asc < 1K Hämta