networking/tulip driver problems on Redhat 7.2 system

networking/tulip driver problems on Redhat 7.2 system

Post by John Lewo » Tue, 18 Dec 2001 23:45:40



All,

I seem to be having some problems with my networking.

Here's the background (as memory serves):

I had a VA Linux system running for a while with the 2.2
version of the kernel and I was subscribed to earthlink via
a modem.  I eventually decided to cancel the earthlink
account and move up the food chain by hooking up with the
local cable modem (roadrunner) folks.   They told me that
officially they "don't support" linux, and the installer
knew nothing about it personally, but the transition went
through without a hitch.  I went into linuxconf and selected
dhcp, did a /sbin/ifup eth0, and I was in business.   The
only drawback was that I couldn't find a way to have it
bring up the interface at boot time.

At some point I started having a problem.   After starting
the machine I noticed that I couldn't start the eth0
interface and that the messages that I remember at the time
referred to the machine's inability to find the tulip
module.

So I decided to go out and buy the latest version (7.2) of
the Redhat distribution since I had started playing around
with modules and I wanted to play in a more advanced
sandbox.

The installation went superbly.   I chose the DHCP option at
installation time and the interface came up cleanly.   Time
and time again. (About a month time span).

And then it stopped doing so.   Suddenly. (at least that's
how this linux newbie perceives it).

I thought that maybe my module playing could have had
something to do with it so I reinstalled the system
completely.

No network interface.

I finally got /usr/sbin/netconfig to let me set DHCP
manually and I was able to bring up the eth0 interface.   I
then remembered that during the installation process I
wasn't queried about DHCP, but thinking that I had found a
work-around (via netconfig), I felt somewhat confident in
shutting off the machine (after about a week).   Just for
paranoia's sake, I immediately turned it back on to see if
the process would work as expected.   It did.   So I went
sleepy-bye with full confidence that the system would
perform properly the next morning. (NOTE: since the new
re-installation I have *not* been playing with modules)

No such luck.   I tried the old netconfig trick about a
dozen times.   I've used neat several times to remove and
reinstall the device.   I've followed the documentation on
the manual configuration of a DHCP client, but I still can't
get the thing to work.

Here are some particulars:

uname -a:

Linux localhost 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown

dmesg:

Linux version 2.4.7-10 (bhcomp...@stripples.devel.redhat.com) (gcc
version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #1 Thu Sep 6
17:27:27 EDT 2001
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000007fe0000 (usable)
 BIOS-e820: 0000000007fe0000 - 0000000007ff8000 (ACPI data)
 BIOS-e820: 0000000007ff8000 - 0000000008000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
Scanning bios EBDA for MXT signature
On node 0 totalpages: 32736
zone(0): 4096 pages.
zone(1): 28640 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=linux ro root=303
BOOT_FILE=/boot/vmlinuz-2.4.7-10
Initializing CPU#0
Detected 399.106 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 796.26 BogoMIPS
Memory: 125140k/130944k available (1269k kernel code, 4520k reserved,
90k data, 220k init, 0k highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
CPU: Before vendor init, caps: 0183f9ff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0183f9ff 00000000 00000000 00000000
CPU:     After generic, caps: 0183f9ff 00000000 00000000 00000000
CPU:             Common caps: 0183f9ff 00000000 00000000 00000000
CPU: Intel Celeron (Mendocino) stepping 05
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgo...@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfdb91, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
PCI: Found IRQ 9 for device 00:0e.0
PCI: Sharing IRQ 9 with 00:0c.0
PCI: Failed to allocate resource 0(0-ffffffff) for 00:0e.0
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
mxt_scan_bios: enter
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10d
block: queued sectors max/low 83058kB/27686kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz PCI bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
hda: QUANTUM FIREBALL CX6.4A, ATA DISK drive
hdc: ATAPI CDROM, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 12594960 sectors (6449 MB) w/418KiB Cache, CHS=784/255/63,
UDMA(33)
ide-floppy driver 0.97
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
ide-floppy driver 0.97
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 322k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 220k freed
Adding Swap: 257000k swap-space (priority -1)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.259 $ time 17:36:49 Sep  6 2001
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 10 for device 00:07.2
usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.251:USB Universal Host Controller Interface driver
EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,3), internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
ip_conntrack (1023 buckets, 8184 max)
Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
PCI: Device 00:0e.0 not available because of resource collisions
tulip: Cannot enable tulip board #0, aborting
es1371: version v0.30 time 17:36:47 Sep  6 2001
PCI: Found IRQ 9 for device 00:0c.0
PCI: Sharing IRQ 9 with 00:0e.0
es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x04
es1371: found es1371 rev 4 at io 0xef00 irq 9
es1371: features: joystick 0x0
ac97_codec: AC97 Audio codec, id: 0x4352:0x5903 (Cirrus Logic CS4297)
ide-floppy driver 0.97
hdc: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
PCI: Device 00:0e.0 not available because of resource collisions
tulip: Cannot enable tulip board #0, aborting
Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
PCI: Device 00:0e.0 not available because of resource collisions
tulip: Cannot enable tulip board #0, aborting

As you can see, the module tulip cannot be loaded, for
reasons I don't quite understand.  

If anyone can give me some pointers, I'd really appreciate
it.

Thanks a load.

--John

 
 
 

networking/tulip driver problems on Redhat 7.2 system

Post by Michael Muelle » Fri, 21 Dec 2001 08:21:43


Hi John,


> Here are some particulars:
[...]
> PCI: Failed to allocate resource 0(0-ffffffff) for 00:0e.0
[...]
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting

> As you can see, the module tulip cannot be loaded, for
> reasons I don't quite understand.

Hopefully you see the cause of the driver failing now, after removing a
huge amount of text beetween the two error messages.

I am not sure about a fix. Try experimenting with the kernel parameter
"pci=". Try values like "bios", "nobios", "conf1" and "conf2". See
/usr/src/linux/Documentation/kernel-parameters.txt for a short
description of this parameter.

The bahaviour during the PCI detection phase can be change by a compile
time option of the kernel too. Under "General Setup"/"PCI access method"
you can choose 3 different methods. Updating to a more recent version of
the 2.4 tree would be worth to think about too.

Michael

 
 
 

networking/tulip driver problems on Redhat 7.2 system

Post by Karl Heye » Fri, 21 Dec 2001 09:01:32



> Here are some particulars:

> uname -a:

> Linux localhost 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown

Worth upgrading your kernel and modules if you can.

...

Quote:> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting
> es1371: version v0.30 time 17:36:47 Sep  6 2001
> PCI: Found IRQ 9 for device 00:0c.0
> PCI: Sharing IRQ 9 with 00:0e.0
...
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting

What does the /proc/pci file say.  It sounds like the BIOS has given
it incorrect settings.

karl.

 
 
 

networking/tulip driver problems on Redhat 7.2 system

Post by Jason Boerne » Fri, 21 Dec 2001 16:14:36


I have had problems with the tulip driver when using the older tulip
chipsets.  I don't know if this is what you are running into, but you
may want to check out the tulip development site on sourceforge.  There
is a bug report on the tulip driver not working with some hubs which
contains a detailed description of supported chipsets.
John Lewocz wrote:
> All,

> I seem to be having some problems with my networking.

> Here's the background (as memory serves):

> I had a VA Linux system running for a while with the 2.2
> version of the kernel and I was subscribed to earthlink via
> a modem.  I eventually decided to cancel the earthlink
> account and move up the food chain by hooking up with the
> local cable modem (roadrunner) folks.   They told me that
> officially they "don't support" linux, and the installer
> knew nothing about it personally, but the transition went
> through without a hitch.  I went into linuxconf and selected
> dhcp, did a /sbin/ifup eth0, and I was in business.   The
> only drawback was that I couldn't find a way to have it
> bring up the interface at boot time.

> At some point I started having a problem.   After starting
> the machine I noticed that I couldn't start the eth0
> interface and that the messages that I remember at the time
> referred to the machine's inability to find the tulip
> module.

> So I decided to go out and buy the latest version (7.2) of
> the Redhat distribution since I had started playing around
> with modules and I wanted to play in a more advanced
> sandbox.

> The installation went superbly.   I chose the DHCP option at
> installation time and the interface came up cleanly.   Time
> and time again. (About a month time span).

> And then it stopped doing so.   Suddenly. (at least that's
> how this linux newbie perceives it).

> I thought that maybe my module playing could have had
> something to do with it so I reinstalled the system
> completely.

> No network interface.

> I finally got /usr/sbin/netconfig to let me set DHCP
> manually and I was able to bring up the eth0 interface.   I
> then remembered that during the installation process I
> wasn't queried about DHCP, but thinking that I had found a
> work-around (via netconfig), I felt somewhat confident in
> shutting off the machine (after about a week).   Just for
> paranoia's sake, I immediately turned it back on to see if
> the process would work as expected.   It did.   So I went
> sleepy-bye with full confidence that the system would
> perform properly the next morning. (NOTE: since the new
> re-installation I have *not* been playing with modules)

> No such luck.   I tried the old netconfig trick about a
> dozen times.   I've used neat several times to remove and
> reinstall the device.   I've followed the documentation on
> the manual configuration of a DHCP client, but I still can't
> get the thing to work.

> Here are some particulars:

> uname -a:

> Linux localhost 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown

> dmesg:

> Linux version 2.4.7-10 (bhcomp...@stripples.devel.redhat.com) (gcc
> version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #1 Thu Sep 6
> 17:27:27 EDT 2001
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 0000000007fe0000 (usable)
>  BIOS-e820: 0000000007fe0000 - 0000000007ff8000 (ACPI data)
>  BIOS-e820: 0000000007ff8000 - 0000000008000000 (ACPI NVS)
>  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
>  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
>  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> Scanning bios EBDA for MXT signature
> On node 0 totalpages: 32736
> zone(0): 4096 pages.
> zone(1): 28640 pages.
> zone(2): 0 pages.
> Kernel command line: auto BOOT_IMAGE=linux ro root=303
> BOOT_FILE=/boot/vmlinuz-2.4.7-10
> Initializing CPU#0
> Detected 399.106 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 796.26 BogoMIPS
> Memory: 125140k/130944k available (1269k kernel code, 4520k reserved,
> 90k data, 220k init, 0k highmem)
> Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
> Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
> Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
> CPU: Before vendor init, caps: 0183f9ff 00000000 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 128K
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 0183f9ff 00000000 00000000 00000000
> CPU:     After generic, caps: 0183f9ff 00000000 00000000 00000000
> CPU:             Common caps: 0183f9ff 00000000 00000000 00000000
> CPU: Intel Celeron (Mendocino) stepping 05
> Enabling fast FPU save and restore... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch (rgo...@atnf.csiro.au)
> mtrr: detected mtrr type: Intel
> PCI: PCI BIOS revision 2.10 entry at 0xfdb91, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
> PCI: Found IRQ 9 for device 00:0e.0
> PCI: Sharing IRQ 9 with 00:0c.0
> PCI: Failed to allocate resource 0(0-ffffffff) for 00:0e.0
> Limiting direct PCI/PCI transfers.
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
> mxt_scan_bios: enter
> Starting kswapd v1.8
> VFS: Diskquotas version dquot_6.5.0 initialized
> pty: 2048 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT
> SHARE_IRQ SERIAL_PCI ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> Real Time Clock Driver v1.10d
> block: queued sectors max/low 83058kB/27686kB, 256 slots per queue
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz PCI bus speed for PIO modes; override with
> idebus=xx
> PIIX4: IDE controller on PCI bus 00 dev 39
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
>     ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
> hda: QUANTUM FIREBALL CX6.4A, ATA DISK drive
> hdc: ATAPI CDROM, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 12594960 sectors (6449 MB) w/418KiB Cache, CHS=784/255/63,
> UDMA(33)
> ide-floppy driver 0.97
> Partition check:
>  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> ide-floppy driver 0.97
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 8192 bind 8192)
> Linux IP multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 322k freed
> VFS: Mounted root (ext2 filesystem).
> Journalled Block Device driver loaded
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Freeing unused kernel memory: 220k freed
> Adding Swap: 257000k swap-space (priority -1)
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb-uhci.c: $Revision: 1.259 $ time 17:36:49 Sep  6 2001
> usb-uhci.c: High bandwidth mode enabled
> PCI: Found IRQ 10 for device 00:07.2
> usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 10
> usb-uhci.c: Detected 2 ports
> usb.c: new USB bus registered, assigned bus number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb-uhci.c: v1.251:USB Universal Host Controller Interface driver
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,3), internal journal
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,1), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,5), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,2), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> ip_conntrack (1023 buckets, 8184 max)
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting
> es1371: version v0.30 time 17:36:47 Sep  6 2001
> PCI: Found IRQ 9 for device 00:0c.0
> PCI: Sharing IRQ 9 with 00:0e.0
> es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x04
> es1371: found es1371 rev 4 at io 0xef00 irq 9
> es1371: features: joystick 0x0
> ac97_codec: AC97 Audio codec, id: 0x4352:0x5903 (Cirrus Logic CS4297)
> ide-floppy driver 0.97
> hdc: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.12
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting

...

read more »

 
 
 

networking/tulip driver problems on Redhat 7.2 system

Post by unMAS » Thu, 27 Dec 2001 13:06:51


Version 0.9.15 of the tulip driver seems to be a bit of a problem child.
FWIW here I have two SMC Etherpower cards, one of which works perfectly and
the other returns the same errors that you're seeing. Going back to v 0.9.14
of the tulip driver sorted it all out. Have a look at
http://sourceforge.net/projects/tulip/ . There's more info there.

Ooroo
Mark F...

"John Lewocz" <jlew...@poczta.wprost.pl> wrote in message

news:89cc5656.0112170645.39329e97@posting.google.com...
> All,

> I seem to be having some problems with my networking.

> Here's the background (as memory serves):

> I had a VA Linux system running for a while with the 2.2
> version of the kernel and I was subscribed to earthlink via
> a modem.  I eventually decided to cancel the earthlink
> account and move up the food chain by hooking up with the
> local cable modem (roadrunner) folks.   They told me that
> officially they "don't support" linux, and the installer
> knew nothing about it personally, but the transition went
> through without a hitch.  I went into linuxconf and selected
> dhcp, did a /sbin/ifup eth0, and I was in business.   The
> only drawback was that I couldn't find a way to have it
> bring up the interface at boot time.

> At some point I started having a problem.   After starting
> the machine I noticed that I couldn't start the eth0
> interface and that the messages that I remember at the time
> referred to the machine's inability to find the tulip
> module.

> So I decided to go out and buy the latest version (7.2) of
> the Redhat distribution since I had started playing around
> with modules and I wanted to play in a more advanced
> sandbox.

> The installation went superbly.   I chose the DHCP option at
> installation time and the interface came up cleanly.   Time
> and time again. (About a month time span).

> And then it stopped doing so.   Suddenly. (at least that's
> how this linux newbie perceives it).

> I thought that maybe my module playing could have had
> something to do with it so I reinstalled the system
> completely.

> No network interface.

> I finally got /usr/sbin/netconfig to let me set DHCP
> manually and I was able to bring up the eth0 interface.   I
> then remembered that during the installation process I
> wasn't queried about DHCP, but thinking that I had found a
> work-around (via netconfig), I felt somewhat confident in
> shutting off the machine (after about a week).   Just for
> paranoia's sake, I immediately turned it back on to see if
> the process would work as expected.   It did.   So I went
> sleepy-bye with full confidence that the system would
> perform properly the next morning. (NOTE: since the new
> re-installation I have *not* been playing with modules)

> No such luck.   I tried the old netconfig trick about a
> dozen times.   I've used neat several times to remove and
> reinstall the device.   I've followed the documentation on
> the manual configuration of a DHCP client, but I still can't
> get the thing to work.

> Here are some particulars:

> uname -a:

> Linux localhost 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown

> dmesg:

> Linux version 2.4.7-10 (bhcomp...@stripples.devel.redhat.com) (gcc
> version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #1 Thu Sep 6
> 17:27:27 EDT 2001
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 0000000007fe0000 (usable)
>  BIOS-e820: 0000000007fe0000 - 0000000007ff8000 (ACPI data)
>  BIOS-e820: 0000000007ff8000 - 0000000008000000 (ACPI NVS)
>  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
>  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
>  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> Scanning bios EBDA for MXT signature
> On node 0 totalpages: 32736
> zone(0): 4096 pages.
> zone(1): 28640 pages.
> zone(2): 0 pages.
> Kernel command line: auto BOOT_IMAGE=linux ro root=303
> BOOT_FILE=/boot/vmlinuz-2.4.7-10
> Initializing CPU#0
> Detected 399.106 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 796.26 BogoMIPS
> Memory: 125140k/130944k available (1269k kernel code, 4520k reserved,
> 90k data, 220k init, 0k highmem)
> Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
> Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
> Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
> CPU: Before vendor init, caps: 0183f9ff 00000000 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 128K
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 0183f9ff 00000000 00000000 00000000
> CPU:     After generic, caps: 0183f9ff 00000000 00000000 00000000
> CPU:             Common caps: 0183f9ff 00000000 00000000 00000000
> CPU: Intel Celeron (Mendocino) stepping 05
> Enabling fast FPU save and restore... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch (rgo...@atnf.csiro.au)
> mtrr: detected mtrr type: Intel
> PCI: PCI BIOS revision 2.10 entry at 0xfdb91, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
> PCI: Found IRQ 9 for device 00:0e.0
> PCI: Sharing IRQ 9 with 00:0c.0
> PCI: Failed to allocate resource 0(0-ffffffff) for 00:0e.0
> Limiting direct PCI/PCI transfers.
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
> mxt_scan_bios: enter
> Starting kswapd v1.8
> VFS: Diskquotas version dquot_6.5.0 initialized
> pty: 2048 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT
> SHARE_IRQ SERIAL_PCI ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> Real Time Clock Driver v1.10d
> block: queued sectors max/low 83058kB/27686kB, 256 slots per queue
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz PCI bus speed for PIO modes; override with
> idebus=xx
> PIIX4: IDE controller on PCI bus 00 dev 39
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
>     ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
> hda: QUANTUM FIREBALL CX6.4A, ATA DISK drive
> hdc: ATAPI CDROM, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 12594960 sectors (6449 MB) w/418KiB Cache, CHS=784/255/63,
> UDMA(33)
> ide-floppy driver 0.97
> Partition check:
>  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> ide-floppy driver 0.97
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 8192 bind 8192)
> Linux IP multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 322k freed
> VFS: Mounted root (ext2 filesystem).
> Journalled Block Device driver loaded
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Freeing unused kernel memory: 220k freed
> Adding Swap: 257000k swap-space (priority -1)
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb-uhci.c: $Revision: 1.259 $ time 17:36:49 Sep  6 2001
> usb-uhci.c: High bandwidth mode enabled
> PCI: Found IRQ 10 for device 00:07.2
> usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 10
> usb-uhci.c: Detected 2 ports
> usb.c: new USB bus registered, assigned bus number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb-uhci.c: v1.251:USB Universal Host Controller Interface driver
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,3), internal journal
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,1), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,5), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,2), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> ip_conntrack (1023 buckets, 8184 max)
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device 00:0e.0 not available because of resource collisions
> tulip: Cannot enable tulip board #0, aborting
> es1371: version v0.30 time 17:36:47 Sep  6 2001
> PCI: Found IRQ 9 for device 00:0c.0
> PCI: Sharing IRQ 9 with 00:0e.0
> es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x04
> es1371: found es1371 rev 4 at io 0xef00 irq 9
> es1371: features: joystick 0x0
> ac97_codec: AC97 Audio codec, id: 0x4352:0x5903 (Cirrus Logic CS4297)
> ide-floppy driver 0.97
> hdc: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.12
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> PCI: Device

...

read more »