|
|
|
|
||||||
| linux.debian.user debian-user@lists.debian.org. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hope someone out there can me with this one, cause I'm stumped.
Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, onboard Intel Ethernet adapter) that when Etch boots on it, will detect an installed network card, but when networking is configured to start, will not start it. Here's the output of some commands from a fresh boot: dmesg | grep eth0 e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB ifconfig eth0 up eth0: ERROR while getting interface flags: No such device Similar messages showing the network card being detected at boot, but not configured will also occur if I disable the onboard Intel Ethernet adapter, and install a PCI network card (I've tried a 3Com and a tulip-based card). This box had previously been used as an IPCop firewall running a 2.4 kernel, so I know the hardware works. If I put the hd in another system, networking works properly. I've tried the noapic and nolapic boot options, as well as updating to the last BIOS release, but to no effect. Any ideas? Thanks, Ken -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
On Thu, Jun 14, 2007 at 08:20:08 -0400, Ken McCord wrote:
> Hope someone out there can me with this one, cause I'm stumped. > > Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, onboard > Intel Ethernet adapter) that when Etch boots on it, will detect an > installed network card, but when networking is configured to start, will > not start it. Here's the output of some commands from a fresh boot: > > dmesg | grep eth0 > e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB > > ifconfig eth0 up > eth0: ERROR while getting interface flags: No such device > > Similar messages showing the network card being detected at boot, but not > configured will also occur if I disable the onboard Intel Ethernet adapter, > and install a PCI network card (I've tried a 3Com and a tulip-based card). > > This box had previously been used as an IPCop firewall running a 2.4 > kernel, so I know the hardware works. If I put the hd in another system, > networking works properly. I've tried the noapic and nolapic boot options, > as well as updating to the last BIOS release, but to no effect. > > Any ideas? Try to boot with the "acpi=off" and/or the "pci=routeirq" option. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Florian Kulzer wrote:
> On Thu, Jun 14, 2007 at 08:20:08 -0400, Ken McCord wrote: > >> Hope someone out there can me with this one, cause I'm stumped. >> >> Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, onboard >> Intel Ethernet adapter) that when Etch boots on it, will detect an >> installed network card, but when networking is configured to start, will >> not start it. Here's the output of some commands from a fresh boot: >> >> dmesg | grep eth0 >> e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB >> >> ifconfig eth0 up >> eth0: ERROR while getting interface flags: No such device >> >> Similar messages showing the network card being detected at boot, but not >> configured will also occur if I disable the onboard Intel Ethernet adapter, >> and install a PCI network card (I've tried a 3Com and a tulip-based card). >> >> This box had previously been used as an IPCop firewall running a 2.4 >> kernel, so I know the hardware works. If I put the hd in another system, >> networking works properly. I've tried the noapic and nolapic boot options, >> as well as updating to the last BIOS release, but to no effect. >> >> Any ideas? >> > > Try to boot with the "acpi=off" and/or the "pci=routeirq" option. > > Tried both of these options separately and together, no change. I tried booting Knoppix 5.1 (using a 2.6.19 kernel and no boot options), and networking is running as normal. Ken -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
On 14.06.07 08:20, Ken McCord wrote:
> Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, > onboard Intel Ethernet adapter) that when Etch boots on it, will detect > an installed network card, but when networking is configured to start, > will not start it. Here's the output of some commands from a fresh boot: > > dmesg | grep eth0 > e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB > > ifconfig eth0 up > eth0: ERROR while getting interface flags: No such device didn't you turn it off in BIOS setup? -- Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. There's a long-standing bug relating to the x86 architecture that allows you to install Windows. -- Matthew D. Fuller -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
On Sat, Jun 16, 2007 at 12:32:21 -0400, Ken McCord wrote:
> Florian Kulzer wrote: > >On Thu, Jun 14, 2007 at 08:20:08 -0400, Ken McCord wrote: > > > >>Hope someone out there can me with this one, cause I'm stumped. > >> > >>Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, onboard > >>Intel Ethernet adapter) that when Etch boots on it, will detect an > >>installed network card, but when networking is configured to start, will > >>not start it. Here's the output of some commands from a fresh boot: > >> > >>dmesg | grep eth0 > >>e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB > >> > >>ifconfig eth0 up > >>eth0: ERROR while getting interface flags: No such device > >> > >>Similar messages showing the network card being detected at boot, but not > >>configured will also occur if I disable the onboard Intel Ethernet > >>adapter, and install a PCI network card (I've tried a 3Com and a > >>tulip-based card). > >> > >>This box had previously been used as an IPCop firewall running a 2.4 > >>kernel, so I know the hardware works. If I put the hd in another system, > >>networking works properly. I've tried the noapic and nolapic boot > >>options, as well as updating to the last BIOS release, but to no effect. > >> > >>Any ideas? > > > >Try to boot with the "acpi=off" and/or the "pci=routeirq" option. > > > Tried both of these options separately and together, no change. I tried > booting Knoppix 5.1 (using a 2.6.19 kernel and no boot options), and > networking is running as normal. Then I would boot Knoppix again and compare the dmesg output for the card with the one you get for Debian. Also check what you get for "modinfo e100" in both cases; Knoppix might simply have a newer version of the module. It might also be ful to know if Knoppix loads the module with any parameters/options; check if the directory /sys/module/e100/parameters/ exists after you boot Knoppix. If it does exist then you should post the output of grep -r '.*' /sys/module/e100/parameters/ -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
On Sat, Jun 16, 2007 at 12:32:21PM -0400, Ken McCord wrote:
> Florian Kulzer wrote: > >On Thu, Jun 14, 2007 at 08:20:08 -0400, Ken McCord wrote: > >>Hope someone out there can me with this one, cause I'm stumped. > >> > >>Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, > >>onboard Intel Ethernet adapter) that when Etch boots on it, will detect > >>an installed network card, but when networking is configured to start, > >>will not start it. Here's the output of some commands from a fresh boot: > >> > >>dmesg | grep eth0 > >>e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB > >> > >>ifconfig eth0 up > >>eth0: ERROR while getting interface flags: No such device > >> What happens if you eliminate possible /etc/network misconfiguration and try to configure it manually with ifconfig instead of eth0 up. Doug. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
Matus UHLAR - fantomas wrote:
> On 14.06.07 08:20, Ken McCord wrote: > >> Have an IBM NetVista 6341-64U system (1.0 GHz Celeron, 512 MB RAM, >> onboard Intel Ethernet adapter) that when Etch boots on it, will detect >> an installed network card, but when networking is configured to start, >> will not start it. Here's the output of some commands from a fresh boot: >> >> dmesg | grep eth0 >> e100: eth0: e100_probe: addr 0xfebff000, irq 5, MAC addr 00:02:55:25:65:FB >> >> ifconfig eth0 up >> eth0: ERROR while getting interface flags: No such device >> > > didn't you turn it off in BIOS setup? > Nope, the onboard card is enabled in BIOS. I also receive the same 'eth0: ERROR while getting interface flags: No such device' message when using PCI cards. Thanks, Ken -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#8 |
|
Messages: n/a
Hébergeur: |
Douglas Allan Tutty wrote:
> On Sat, Jun 16, 2007 at 12:32:21PM -0400, Ken McCord wrote: > >> Florian Kulzer wrote: >> >>> On Thu, Jun 14, 2007 at 08:20:08 -0400, Ken McCord wrote: >>> <snip> >>>> <snip> >>>> >>>> > > What happens if you eliminate possible /etc/network misconfiguration and > try to configure it manually with ifconfig instead of eth0 up. > > Doug. > > > I tried what you suggested, but same effect. I also pulled the hard drive and put it into two different systems - both times networking came up as expected and I was able to access network resources. Thanks, Ken -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
![]() |
| Outils de la discussion | |
|
|