Christian Perrier <[EMAIL PROTECTED]> writes: >> I've done a bit more testing. The problem only occurs if I boot using >> 'linux26', if I boot using 'linux' the network detection and >> configuration work fine. Looking in the syslog for 2.4 I see > > Well, maybe the driver to be loaded is different in 2.6 and 2.4. Is > that what the pci-26.lst file is for, Joshua ?
One more thing. Now that I have a 2.6 installation, when it boots the tulip module is loaded automatically. At first this was because tulip was listed in /etc/modules (by the installer), but I have since removed tulip from that file and it still gets loaded. During the boot I see the yenta module for the CardBus socket get loaded and then I see Cleaning: /etc/network/ifstate Starting hotplug system: input Nov 30 17:05:15 localhost kernel: Linux Tulip driver version 1.1.13 (May 11, 2002) Nov 30 17:05:15 localhost kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0003) Nov 30 17:05:15 localhost kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64 Nov 30 17:05:15 localhost kernel: tulip0: EEPROM default media type Autosense. Nov 30 17:05:15 localhost kernel: tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. Nov 30 17:05:15 localhost kernel: tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block. Nov 30 17:05:15 localhost kernel: tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block. Nov 30 17:05:15 localhost kernel: tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block. Nov 30 17:05:15 localhost kernel: eth0: Digital DS21143 Tulip rev 65 at 0x4000,00:A0:0C:90:6D:9A, IRQ 10. So the installed system does detect my card automatically, it's just the installer itself that has a problem. -- Philip Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
