Bug#303812: Fwd: Bug#303812: net ok at stage 1, absent after reboot
Here are the answers to the latest questions.
In addition, I tried the computer on an entirely different network,
and the problem was unchanged.
> It's strange that /etc/network/interfaces has 'auto eth0' in it since
> this is a pcmcia card and pcmcia cards should not have an auto statement
> generally, since pcmcia-cs ifups them when it detects the card. It would
> be interesting to see if removing the 'auto eth0' line fixed the
> problem, though I don't see how it could.
It does not fix the problem.
>It would at least eliminate
> the above ugliness at boot.
> > Thu Apr 14 13:24:49 2005: Starting PCMCIA services: cardmgr:
> > watching 2 sockets Thu Apr 14 13:24:50 2005: done.
> This is where the interface should come up; pcmcia should run the
> command "ifup eth0" at this point. What happens if you run that command
> after boot but before bringing up the interface by hand?
The network comes up, apparantly just as it does when I run dhclient.
> What do you see if you grep for 'cardmgr' in /var/log/daemon.log?
(The 'unsupported card' was an experiment with another pcmcia network
card; I've only included the last few boots.)
Apr 14 15:36:42 localhost cardmgr: watching 2 sockets
Apr 14 15:36:42 localhost cardmgr: starting, version is 3.2.5
Apr 14 15:36:42 localhost cardmgr: unsupported card in socket 1
Apr 14 15:36:42 localhost cardmgr: product info: "Belkin", "11Mbps-Wireless-Notebook-Network-Adapter"
Apr 14 15:36:42 localhost cardmgr: manfid: 0x01bf, 0x3302 function: 6 (network)
Apr 14 15:39:26 localhost cardmgr: exiting
Apr 15 08:08:29 localhost cardmgr: watching 2 sockets
Apr 15 08:08:29 localhost cardmgr: starting, version is 3.2.5
Apr 15 08:08:29 localhost cardmgr: socket 1: CardBus hotplug device
Apr 15 08:10:16 localhost cardmgr: exiting
Apr 18 09:41:31 localhost cardmgr: watching 2 sockets
Apr 18 09:41:31 localhost cardmgr: starting, version is 3.2.5
Apr 18 09:41:31 localhost cardmgr: socket 1: CardBus hotplug device
> Your installation report doesn't say what version of Debian you
> or exactly when,
My first attempt was March 31 or April 1
> so I guess one possibilty might be you have
> the unstable version of ifupdown and it could be broken.
> What does "dpkg -l ifupdown" say?
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
ii ifupdown 0.6.4-4.12 high level tools to configure network interf