[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Cable Modem Blues...
- From: "Bennie L. Caldwell" <bennie-caldwell home com>
- To: <redhat-install-list redhat com>
- Subject: Re: Cable Modem Blues...
- Date: Thu, 4 May 2000 07:51:00 -0700
Scott,
Here is that info you requested.
/proc/interrupts :
CPU0
0: 12679 XT-PIC timer
1: 274 XT-PIC keyboard
2: 0 XT-PIC cascade
6: 9 XT-PIC floppy
8: 1 XT-PIC rtc
12: 9 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 44356 XT-PIC ide0
15: 4 XT-PIC ide1
NMI: 0
/proc/pci :
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel 440BX - 82443BX Host (rev 3).
Medium devsel. Master Capable. Latency=32.
Prefetchable 32 bit memory at 0xf8000000 [0xf8000008].
Bus 0, device 1, function 0:
PCI bridge: Intel 440BX - 82443BX AGP (rev 3).
Medium devsel. Master Capable. Latency=128. Min Gnt=140.
Bus 0, device 7, function 0:
ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
Medium devsel. Fast back-to-back capable. Master Capable. No
bursts.
Bus 0, device 7, function 1:
IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0x1050 [0x1051].
Bus 0, device 7, function 2:
USB Controller: Intel 82371AB PIIX4 USB (rev 1).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0x1060 [0x1061].
Bus 0, device 7, function 3:
Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
Medium devsel. Fast back-to-back capable.
Bus 0, device 10, function 0:
Ethernet controller: LiteOn LNE100TX (rev 32).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0x1400 [0x1401].
Non-prefetchable 32 bit memory at 0xf4000000 [0xf4000000].
Bus 0, device 12, function 0:
Multimedia audio controller: Unknown vendor Unknown device (rev 0).
Vendor id=127a. Device id=4320.
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0x1080 [0x1081].
Bus 0, device 12, function 1:
Communication controller: Unknown vendor Unknown device (rev 0).
Vendor id=127a. Device id=4321.
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
Non-prefetchable 32 bit memory at 0xf4010000 [0xf4010000].
Bus 0, device 12, function 2:
Input device controller: Unknown vendor Unknown device (rev 0).
Vendor id=127a. Device id=4322.
Medium devsel. Fast back-to-back capable. Master Capable. No
bursts.
Non-prefetchable 32 bit memory at 0xf4001000 [0xf4001000].
Bus 1, device 0, function 0:
VGA compatible controller: ATI Mach64 GB (rev 92).
Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable.
Latency=66. Min Gnt=8.
Non-prefetchable 32 bit memory at 0xf5000000 [0xf5000000].
I/O at 0x2000 [0x2001].
Non-prefetchable 32 bit memory at 0xf4100000 [0xf4100000].
Bennie
"Scott A. Zanke" <szanke america net> wrote in message
news:00050222313200 00667 mango
> Hola,
> The following three lines from your /var/log/messages are similar to mine
except
> for the IRQ 0. That isn't right:(
> IRQ 0 is system timer. My Linksys card on this box is IRQ5
> Try cat /proc/interrupts to see what your iRQs are.
> You might need to set the pci irq's in your bios.
> Also try cat /proc/pci to see more detailed info....
>
> Let me know what the output of the above is and I may be able to help.
> Once you can ping , telnet, ftp and such between boxen, you can share your
> cable modem connection several ways.
> You can set up a linux box as a gateway router with ipchains (ipmasq) or
use a
> hardawre router or use a Win98 software solution such as WinProxy.
>
>
> Laterz,
> <<zank>>
>
>
> On Wed, 03 May 2000, Bennie L. Caldwell wrote:
> > I tried to ping my other computer and got "network is unreachable".
> >
> > This is the output from my /var/log/messages after I log on as root.
> >
>
> > May 3 00:24:13 cj49180-a kernel: tulip.c:v0.89H 5/23/98
> > becker cesdis gsfc nasa gov
> > May 3 00:24:13 cj49180-a kernel: eth0: Lite-On 82c168 PNIC at 0x1400,
00 a0
> > cc 28 52 cd, IRQ 0.
> > May 3 00:24:13 cj49180-a kernel: eth0: MII transceiver found at MDIO
> > address 1, config 3100 status 7829.
>
> > Bennie
> > "Scott A. Zanke" <szanke america net> wrote in message
> > news:00043020280000 27694 mango
> > > Hello,
> > > The etho: Lite-On 82C168 is correct. It's the same message I get with
my
> > > Linksys LNE100TX cards. The IRQ 0 isn't right though.
> > > The MII transceiver message is the same as mine also.
> > > I have 3 boxes networked with Linksys 10/100 cards, 1 win box, 1 RH6.1
box
> > and
> > > one dual boot box. with a 10/100 autosensing hub. Works fine with
Samba
> > and
> > > Win98 networking.
> > > I had cable modem for a few months and was sharing it. Wasn't really
> > impressed
> > > with it. I'm waiting on asdl.
> > > Can you ping and telnet to the other boxes?
> > > Any other pertinent info in /var/log/messages?
> > >
> > > Laterz,
> > > <<zank>>
> > >
> > >
> > > On Thu, 27 Apr 2000,
> > > Bennie L. Caldwell wrote: > I didn't see eth0 comming up in
> > /var/log/boot.log
> > > for my hostname. > I checked /var/log/messages and found:
> > > >
> > > > Apr 27 10:23:24 Hstname kernel: eth0: Lite-On 82c168 PNIC at
0x1400, 00
> > a0
> > > > cc 28 52 cd, IRQ 0.
> > > > Apr 27 10:23:24 Hstname kernel: eth0: MII transceiver found at MDI0
> > address
> > > > 1, config 3100 status 7829.
> > > >
> > > > This doesn't look like my ethernet card. Is there anyway I can
determine
> > > > what the card address is?
> > > >
> > > >
> > > >
> > > > Bennie
> > > >
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Karl Pearson" <karlp colubs com>
> > > > To: "Bennie L. Caldwell" <bennie-caldwell home com>
> > > > Sent: Thursday, April 27, 2000 1:40 PM
> > > > Subject: Re: Cable Modem Blues...
> > > >
> > > >
> > > > > Check /var/log/boot.log for eth0 and see if it comes up okay
during
> > the
> > > > > bootup, unless you watch closely and see it coming up. It should
if
> > the
> > > > > card is working. Also check /var/log/messages and see if there's
a
> > line
> > > > > that says something like:
> > > > >
> > > > > Apr 27 10:23:24 Hstname kernel: eth0: NE2000 found at 0x300, using
IRQ
> > 9.
> > > > >
> > > > > That's what comes up on my box.
> > > > >
> > > > > If there are errors there, you can probably deduce why it's
failing by
> > > > > seeing what the message says.
> > > > >
> > > > > Karl L. Pearson
> > > > > Senior uniVerse Database Analyst
> > > > > Senior Unix/NT/Win Analyst
> > > > > karlp colubs com
>
>
> --
> To unsubscribe: mail redhat-install-list-request redhat com with
> "unsubscribe" as the Subject.
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]