RE: hotplug error at boot time
--- "Broughton, Derek" <BroughtonD@mar.dfo-mpo.gc.ca>
a écrit : >
> Miky J wrote:
> > Sent: April 27, 2004 8:36 AM
> >
> > I tryed this solution but it didn't work.
> > Actually my Intel wireless card seems to be pci
> > when i added HOTPLUG_RC_pci=no I couldn't have my
> card
> > working anymore
> > With HOTPLUG_RC_net=no
> >
> > Starting hotplug subsystem:
> > input
> > pci
> > ignore pci display device on 01:00.0
> > ipw2100: Intel(R) PRO/Wireless 2100 Network
> Driver,
> > 0.41
> > ipw2100: Copyright(c) 2003-2004 Intel Corporation
> > Detected ipw2100 PCI device at 0000:02:0a.0, dev:
> > eth1, mem:
> > 0xC2005000-0xC2005FFF -> e08e6000, irq: 11
> > Setting up IP spoofing protection: rp_filter.
> > Ignoring unknown interface eth1=hotplug.
> > ipw2100: loaded sucessfully
> >
> >
> > Any ideas ?
>
> You were given the answer. Do you expect somebody
> else to do the work?
>
> Look at /etc/network/interfaces. Look for hotplug.
> Use common sense.
>
>
> --
> To UNSUBSCRIBE, email to
> debian-laptop-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
I Have NO hotplug devices !!!!
The only way to make my driver work was to add hotplug
support in my kernel, otherwise it just crashes.
I don't expect someone to do the work but after
numerous attempts, i'm asking on this list.
here's the /etc/network/interfaces file
auto eth1
#iface eth1 inet dhcp
iface eth1 inet static
address 192.168.0.21
netmask 255.255.255.0
network 192.168.0.0
broadcast 195.168.0.255
wireless_essid NETGEAR
wireless_mode Managed
#wireless_rate auto
#wireless_channel 11
wireless_key s:lacle
wireless_nick Laptop
Maybe the hotplug reacts because of "auto" but it
shouldn't or there might be a way to disable this behavior.
Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com
Reply to: