Bug 2467
| Summary: | Installer not recognizing Tulip NIC Cards | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | ken |
| Component: | installer | Assignee: | David Lawrence <dkl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | nagel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1999-09-24 15:58:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
ken
1999-05-01 17:46:01 UTC
What brand on NIC is this? There are several cards based on the Tulip chipset. Discarded due to lack of response. I've had this problem as well. The card is a D-Link 530CT. The chip is a DEC 21041. This problem may have something to do with bug #2582 but I'm not sure. Just make sure that the Reopen bug choice is selected and click on Commit. What does 'lspci -v' say your card is? (alternatively, 'cat /proc/pci') I tried to install again last night and this is what I found. While
the install was going I switched over to vc2 and did a cat /proc/pci.
These are the bus and ethernet card entries. I left out the video card
and ide interface.
PCI devices found:
Bus 0, device 0, Function 0:
Host bridge: VIA Technologies VT 82C576 3V (rev 2)
Fast devsel. Master Capable. No bursts.
Bus 0, device 10, Function 0:
Ethernet controller: DEC DC21041 (rev 33).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0x6100 [0x6100].
Non-prefetchable 32 bit memory at 0xf0800000 [0xf0800000].
This machine is a P150. I have another machine at work which uses the
same card and it was detected just fine by the installer. Here's it's
pci info.
PII 350MHz
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel 440BX - 82443BX Host (rev 2).
Medium devsel. Master Capable. Latency=64.
Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
Bus 0, device 1, function 0:
PCI bridge: Intel 440BX - 82443BX AGP (rev 2).
Medium devsel. Master Capable. Latency=64. Min Gnt=136.
Bus 0, device 13, function 0:
Ethernet controller: DEC DC21041 (rev 33).
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Latency=64.
I/O at 0x6800 [0x6801].
Non-prefetchable 32 bit memory at 0xe9000000 [0xe9000000].
Anyway... during the install I was jumping around between vc's and saw
some interesting things. Here is what it said when it detected the
etherenet card.
VC3
*pci probing for ethernet devices
*pci probe found 1 ethernet devices
*found driver for Digital 21040 (Tulip)
*picked driver Digital 21040 (Tulip)
*running: /bin/insmod /bin/insmod /modules/tulip.o
*insmod failed!
I think we found the problem. insmod also fails to load
/modules/loop0.o. The install fails to create a boot floppy and
install the bootloader because it can't access /dev/loop0.
One more thing. I didn't pay much attention to VC4 but I did manage to
see something that might be useful.
VC4
<6>install uses obsolete /proc/pci interface
I don't know what step this was from. Sorry. Hope all this info helps
track down the problem.
That shouldn't be a problem. It looks like you're using a boot disk with a different kernel than the modules on the install image; if so, make sure you boot with 'linux supp'. |