Hello,

after configuring the nic's in system settings it looks like this:

-----------------------------
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface eth0 inet dhcp
auto eth0
----------------------------

I don't know what it looked like before these changes, but it has been a
frech installation, so it should have been default.

I'm using eth0, which is the onboard-nic (VIA-Rhine). There is also a
wireless card with Atheros chip, but this is only used every few months
(not at home). Here's the output of lshw for this cards:

*-network:0
   description: Wireless interface
   product: AR5212/AR5213 Multiprotocol MAC/baseband processor
   vendor: Atheros Communications, Inc.
   physical id: 7
   bus info: [EMAIL PROTECTED]:00:07.0
   logical name: wifi0
   version: 01
   serial: 00:80:c8:11:fd:ed
   width: 32 bits
   clock: 33MHz
   capabilities: bus_master cap_list logical ethernet physical wireless
   configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 
mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g

*-network:1
   description: Ethernet interface
   product: VT6102 [Rhine-II]
   vendor: VIA Technologies, Inc.
   physical id: 12
   bus info: [EMAIL PROTECTED]:00:12.0
   logical name: eth0
   version: 74
   serial: 00:10:dc:76:d3:24
   width: 32 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical
   configuration: broadcast=yes driver=via-rhine driverversion=1.4.3 
ip=192.168.1.3 latency=32 maxlatency=8 mingnt=3 module=via_rhine multicast=yes


But today I experienced the same problem without network-manager (disabled at 
the moment). Again the connection to the router was not established at boot, 
only after disabling and restarting the card in system settings the connection 
was established.


And there are some strange (at least to me) message about network-manager in 
/var/log/syslog. I'm not sure if this has anything to do with the problem, but 
it seems very strange - what's the connection between network-manager and 
storage, usb-devices, etc.?

--------------------------------------------------
Oct  4 10:35:51 ralf01 NetworkManager: <debug> [1191486951.409978] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/volume_part1_size_2059278848'). 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.481539] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/usb_device_839_1050_noserial_if0_scsi_host_scsi_device_lun0_scsi_generic').
 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.491591] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/storage_serial_SAMSUNG_Samsung_Digital_Camera'). 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.494895] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/usb_device_839_1050_noserial_if0_scsi_host_scsi_device_lun0').
 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.496779] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/usb_device_839_1050_noserial_if0_scsi_host'). 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.503734] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/usb_device_839_1050_noserial_usbraw'). 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.510085] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/usb_device_839_1050_noserial_if0'). 
Oct  4 10:36:00 ralf01 NetworkManager: <debug> [1191486960.514165] 
nm_hal_device_removed(): Device removed (hal udi is 
'/org/freedesktop/Hal/devices/usb_device_839_1050_noserial'). 


If there are more tests or information needed, please let me know.


Regards,

Ralf

-- 
KDE network-manager problem
https://bugs.launchpad.net/bugs/148482
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to