Bug#322324: ifplugd: Fails to ifup eth0 at boot time

2005-09-12 Thread Libor Klepac
hello,
i have the same problem here

my configuration
i use discover to load modules for pci devices (both on laptop and desktop)
i have hotplug pci subsystem disabled
on laptop, i use udev to rename eth0->lan, on desktop eth0 is eth0 ;)
i have ifplugd configured to watch all hotplug interfaces and no static
interface

i noticed it, when i switched from hotplug for pci to discover on my
desktop (maybe it wasn't working before, but i don't restart my desktop
offten so i didn't notice

after boot, i have ifplugd running for lan interface, but it's not up, i
was searching why, and it seems, that problem is, when you have
/etc/networking/run/ifstate linked to /dev/shm ... appearently, it's not
available, when hotplug launches ifplugd
i created regular directory and file and lan is up after boot

i fiddled a little with sequence of commands in rcS ... now it's
S33mountall.sh
S34mountvirtfs (we need /dev/shm mounted)
S35ifupdown (we need /dev/shm/network/run/ifstate)
S36discover (it loads e100, it seems to emit hotplug action -> launches
ifplugd which ifups lan, so we need /dev/shm/network/run/ifstate)
S40hotplug (is not important)

(old sequence was
S35mountall.sh
S36discover
S36mountvirtfs
S39ifupdown
S40hotplug
)

and it also boots with lan ifuped

what do you think? i think, it should work this way, maybe this bug
should be assigned to another package (maybe it's complete gibberish,
but it fixed my problem, it seems)

well as i look on sequence of commands in rcS, it seem, that when e100
module was loaded by hotplug pci, ifupdown was already finished, so
ifstate file existed

cu

libor


signature.asc
Description: OpenPGP digital signature


Bug#322324: ifplugd: Fails to ifup eth0 at boot time

2005-08-11 Thread David Kågedal
Oliver Kurth <[EMAIL PROTECTED]> writes:

>> It is as if ifplugd doesn't even notice eth0.
>
> Is there any information in the log files? Did ifplugd tell anything?

No.  Or actually, the only thing in /var/log/syslog is that it
discovers the interface "sit0"

  Aug 10 09:53:08 fidgit ifplugd.hotplug[6643]: Invoking ifplugd for sit0
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: ifplugd 0.26 initializing.
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: Using interface 
sit0/00:00:00:00:00:00
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: Using detection mode: IFF_RUNNING
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: Initialization complete, link 
beat detected.
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: Executing 
'/etc/ifplugd/ifplugd.action sit0 up'.
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: client: Ignoring unknown 
interface sit0=sit0.
  Aug 10 09:53:08 fidgit ifplugd(sit0)[6656]: Program executed successfully.

> Also, do you remember any change to your system that my have caused the
> problem? A kernel update, for example?

I do not remember exactly, but it could very well have been related to
a kernel update.  Or any other update, since there have been lots of
updates to sarge.

> What happens when you do
> ifup eth0
> after boot, when it did not work?

"ifup eth0" always works when I run it manually.  I don't think
ifplugd tries to run it at boot.  If I unplug the cable and plug it
back in, ifplug will up the interface.

> Do you use dhcp?

Yes.  Below is my /etc/network/interfaces file.

  auto lo

  iface lo inet loopback

  iface eth0 inet dhcp

  mapping eth1
  script /sbin/ifscheme-mapping

  iface eth1-open inet dhcp

  iface eth1-home inet dhcp
  wireless-key 

lspci | grep Eth gives me this:

  :02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] 
(rev 78)

-- 
David Kågedal



Bug#322324: ifplugd: Fails to ifup eth0 at boot time

2005-08-10 Thread Oliver Kurth
On Wed, 2005-08-10 at 10:46 +0200, David Kågedal wrote:
> Package: ifplugd
> Version: 0.26-2
> Severity: important
> 
> I have a laptop with a built-in eth0 interface, and a wireless card that I 
> sometimes plug in.  This means that sometimes I boot with a cable in eth0, 
> and sometimes not.  So I disabled the autoconfiguration of eth0 in 
> /etc/network/interfaces and added eth0 to INTERFACES in /etc/defaults/ifplugd.
> 
> This used to work a couple of months ago, but now, it doesn't work anymore.  
> If I plug in the cable after ifplugd has started, it works fine.
> 
> It is as if ifplugd doesn't even notice eth0.

Is there any information in the log files? Did ifplugd tell anything?

Also, do you remember any change to your system that my have caused the
problem? A kernel update, for example?

What happens when you do
ifup eth0
after boot, when it did not work?

Do you use dhcp?

Greetings,
Oliver

> -- System Information:
> Debian Release: 3.1
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.11-1-686
> Locale: LANG=C, LC_CTYPE=sv_SE.iso88591 (charmap=ISO-8859-1)
> 
> Versions of packages ifplugd depends on:
> ii  debconf 1.4.30.13Debian configuration management 
> sy
> ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries 
> an
> ii  libdaemon0  0.7-1lightweight C library for daemons
> 
> -- debconf information:
> * ifplugd/interfaces: eth0
> * ifplugd/hotplug_interfaces: all
> * ifplugd/args: -q -f -u0 -d10 -w -I
>   ifplugd/suspend_action: stop
> 
-- 
  .''`.
 : :' :Oliver Kurth [EMAIL PROTECTED]
 `. `'   Debian GNU/Linux maintainer - www.debian.org
   `-
today in my TODO list: prove the Goldbach conjecture



signature.asc
Description: This is a digitally signed message part


Bug#322324: ifplugd: Fails to ifup eth0 at boot time

2005-08-10 Thread David Kågedal
Package: ifplugd
Version: 0.26-2
Severity: important

I have a laptop with a built-in eth0 interface, and a wireless card that I 
sometimes plug in.  This means that sometimes I boot with a cable in eth0, and 
sometimes not.  So I disabled the autoconfiguration of eth0 in 
/etc/network/interfaces and added eth0 to INTERFACES in /etc/defaults/ifplugd.

This used to work a couple of months ago, but now, it doesn't work anymore.  If 
I plug in the cable after ifplugd has started, it works fine.

It is as if ifplugd doesn't even notice eth0.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=C, LC_CTYPE=sv_SE.iso88591 (charmap=ISO-8859-1)

Versions of packages ifplugd depends on:
ii  debconf 1.4.30.13Debian configuration management sy
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libdaemon0  0.7-1lightweight C library for daemons

-- debconf information:
* ifplugd/interfaces: eth0
* ifplugd/hotplug_interfaces: all
* ifplugd/args: -q -f -u0 -d10 -w -I
  ifplugd/suspend_action: stop


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]