*** This bug is a duplicate of bug 256054 ***
    https://bugs.launchpad.net/bugs/256054

Hi,

I don't think the bug is a duplicate of bug #256054, because:
1. I tried the workaround described at bug #256054, that means I disabled the 
NetworkManager completely. It isn't loaded anymore (does not appear in boot 
log, or whatever the name of the output ist, that you get when you give 
nosplash at boot prompt) and 'ps aux | grep net' does not show any running 
instances (of course after a reboot after disabling the NetworkManager). 
Although NetworkManager can't do anything anymore, the dmesg-output is the same 
(not exactly, NetworkManager does not appear in dmesg, but it didn't appear 
around the PCMCIA-probes before, anyway, as I point out later), eth0 does not 
appear in ifconfig-output, and lspcmcia-vv gives exactly the same output. Or in 
short: It didn't change anything.

2. The problem arises far earlier than NetworkManager is being loaded.
The problem arises during the stage in booting process when the hardware
drivers are being loaded. That is before any runlevel. After that, when
entering runlevel 2, roughly, ifup is excuted (without any special
impact, as /dev/eth0 does not exist) and way after that (when entering
runlevel 5), NetworkManager is executed and /could/ indeed interfere
with any settings, if there would even be a network device. But there is
none, and there are no special settings, it would just work fine with
DHCP, if NM would set any device to that, but there is no networking
device (virtually, physically it is sitting there blinking).
Furthermore, before removing NetworkManager I could access
NetworkManager and it was reporting "No ethernet device" or something
like this. That means I can confirm that NetworkManager did not find any
devices and can therefore not mess the configuration of these.

So I would say this is not a duplicate of bug #256054.

-- 
[intrepid-beta] PCMCIA network-card working in hardy does not work
https://bugs.launchpad.net/bugs/278350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Reply via email to