Re: networking problem encountered while installing "Woody"
Aurélien,
Thank you for your prompt and insightful reply. I'll
get a move on learning to compiling my own kernel.
Hopefully, that'll get the networking functioning. In
the mean time, I'd still like to learn exactly how my
setup isn't working and what I am fixing. The
following is the info you asked for:
ifconfig
--------
eth0 Link encap:Ethernet HWaddr
00:A0:CC:D7:51:A4
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
frame:0
TX packets:65 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:22230 (21.7
KiB)
Interrupt:12 Base address:0x6c00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0
frame:0
TX packets:16 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:1056 (1.0 KiB) TX bytes:1056 (1.0
KiB)
-------
lspci -v
--------
00:00.0 Host bridge: Intel Corp. 430TX - 82439TX MTXC
(rev 01)
Flags: bus master, medium devsel, latency 64
00:07.0 ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev
01)
Flags: bus master, medium devsel, latency 0
00:07.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE
(rev 01) (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 64
I/O ports at f000
00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB
(rev 01) (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 6400
00:07.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev
01)
Flags: medium devsel
00:09.0 VGA compatible controller: 3Dfx Interactive,
Inc. Voodoo Banshee (rev 03) (prog-if 00 [VGA])
Subsystem: Diamond Multimedia Systems Monster Fusion
Flags: fast devsel, IRQ 10
Memory at e0000000 (32-bit, non-prefetchable)
Memory at e2000000 (32-bit, prefetchable)
I/O ports at 6800
Capabilities: [60] Power Management version 1
00:0b.0 Ethernet controller: Lite-On Communications
Inc LNE100TX (rev 20)
Subsystem: Netgear FA310TX
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at 6c00
Memory at e4000000 (32-bit, non-prefetchable)
-------
Additionally, here is the content of my
/etc/network/interfaces:
-------
# /etc/network/interfaces -- configuration file for
ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created
during the Debian installation
# (network, broadcast and gateway are optional)
auto eth0
iface eth0 inet dhcp
-------
I know the following from the system console indicates
that I have the DHCP client running in some form. I
just don't know the meaning or cause of the behavior:
-------
Mar 21 21:59:22 debian dhclient-2.2.x: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 5
Mar 21 21:59:27 debian dhclient-2.2.x: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 6
Mar 21 21:59:33 debian dhclient-2.2.x: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 13
Mar 21 21:59:46 debian dhclient-2.2.x: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 14
Mar 21 22:00:00 debian dhclient-2.2.x: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 21
Mar 21 22:00:21 debian dhclient-2.2.x: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 2
Mar 21 22:00:23 debian dhclient-2.2.x: No DHCPOFFERS
received.
Mar 21 22:00:23 debian dhclient-2.2.x: No working
leases in persistent database.
Mar 21 22:00:24 debian dhclient-2.2.x: Sleeping.
-------
Whatever is the matter, Eth0 seems to at least be
healthy. Is there something else I'm not seeing? Any
insights are apreciated.
Thanks again.
-Ren
--- Aurélien_Campéas <aurelien.aa@wanadoo.fr> wrote:
> First, you should tell us the output of `ifconfig'
> and `lspci -v'.
>
> Then... I've observed that sometimes, debian
> pre-made ultra-modularized
> kernels don't work wrt networking. It's because of
> some stupid IRQ
> conflict. The only solution I found in those cases
> is to make your own
> kernel with network drivers compiled in (NOT
> modular). Then it works,
> presumably because the drivers check the hardware
> early enough and get
> over the (potential) conflict.
>
> Hope that helps.
>
> Le sam 20/03/2004 à 02:31, Renhao Zhang a écrit :
> > I'm trying to dual boot an old Pentium box with
> Debian
> > "Woody" and win98. The few bugs I've encountered
> are
> > falling one by one as I work on the new
> installation.
> > However, one persistant mystery has remained
> stuborn.
> > Here is the problem: booting from Windows, I can
> get
> > onto my home LAN and reach the internet just fine
> with
> > a dial-up gateway (the Actiontec dual pc modem) as
> the
> > DHCP server. But if the Linux partition boots,
> the
> > network vanishes. It pauses for an unusually long
> > time at "configuring network interfaces......" By
> all
> > indications, networking on the box is functional:
> > there are no hardware related error messages
> during
> > boot or in the kernel logs. loop-back is fine
> when I
> > ping 127.0.0.1, but no other IPs are reachable.
> > conversely, the box can't be pinged by any other
> > machines on the network either. Flashing LEDs on
> my 8
> > port switch seems to indicate there is a signal
> > present, but nothing is getting through in either
> > direction when Woody is running. The NIC is a
> netgear
> > FA 310TX for which I'm using the tulip driver.
> >
> > In addition to Windows, KNOPPIX networks just fine
> > with no problems.
> >
> > An experienced collegue suggested that there might
> be
> > a IRQ conflict with another device. Debian boot
> lists
> > the NIC as using IRQ 12. In windows, the
> diagnostic
> > tool AIDA32 returned the following:
> >
> > IRQ 0C shared NETGEAR FA310TX fast
> > ethernet PCI adapter
> > IRQ 0C shared IRQ Holder for PCI
> > Steering
> >
> > First of all, what is PCI steering? Is there a
> way to
> > uncouple the two so they use different IRQs?
> >
> > My own suspicion is that an old USR Sportster ISA
> > winmodem might have something to do with it. The
> > thing is useless with Linux but I don't want to
> trash
> > it because it still works well under Win98. I
> think
> > it is worth keeping for those rare emergencies.
> does
> > anyone know if an IRQ would be assigned by Linux
> to
> > hardware it doesn't recognize?
> >
> > The last time I handled Linux was when Redhat 5.2
> was
> > new. Back then I don't remember having much
> hardware
> > headaches. At the end of my ropes, I even tried a
> few
> > days ago to explicitly declare an IP, hoping the
> DHCP
> > server might back down and just let the damn NIC
> talk
> > to somebody-anybody.
> >
> > After some googling, I found one other account of
> > almost the same problem:
> >
>
http://www.linuxquestions.org/questions/showthread.php?threadid=110910
> > the only difference is the router being used.
> >
> > The guy who started the thread never said if his
> > problem was solved. I've tried everything
> suggested
> > to him to no avail. Everthing that is, except the
> > last one, which I didn't quite understand. I
> quote
> > the following:
> >
> > "I have the exact same network card that you do,
> and
> > have had the same problem. I have never been able
> to
> > do a net install with dhcp using the bf2.4 kernel.
> So
> > what I do is just install the base system with the
> > vanilla kernel. Then just apt-get the 2.4.18
> kernel
> > source and compile it with the tulip driver and
> MAKE
> > SURE you also have packet filtering and socket
> > filtering enabled as well. They are under the
> network
> > options. You must have those two options enabled
> for
> > dhcp to work with that card. So the bf2.4 kernel
> > probably doesn't have them enabled."
> >
> > I'm not sure I understand what is being said. Are
> you
> > supposed to apt-get the 2.4.18 kernel with the
> 'Woody'
> > iso disc set as the source? I'll try to learn how
> to
> > recompile the kernel to see if that solves the
> > problem, but I wanted to see if anyone else has
> > encountered similar problems and suceeded in
> solving
> > it.
> >
> > Thanks in advance for any new insight.
> > -Ren
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail - More reliable, more storage, less
> spam
> > http://mail.yahoo.com
> You'll feel much better once you've given up hope.
>
__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
Reply to: