Hello everybody... I already asked this on efwsupport.com, but maybe this list is the better way. Don't worry about this kind of cross-posting, if you have a solution for me I'll post it to the forum and vice-versa. So everyone profits. ;-)
I ran EFW for more than a year as a virtual machine under Xen (DomU). There's a PCI quad-NIC in the system that is hidden from Dom0 and given directly to the EFW-DomU. Everything was fine until last weekend I changed the mainboard and CPU in the computer. The quad-NIC has new IRQs now, and the PCI address changed. I reconfigured my kernel boot line, and the configuration of the Endian-DomU. Now, with lspci I can see that there is the card visible for the Endian: 00:00.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22) 00:01.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22) 00:02.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22) 00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22) The driver (tulip) loads without error messages, in dmesg output I see: Linux Tulip driver version 1.1.13 (May 11, 2002) PCI: Enabling device 0000:00:00.0 (0000 -> 0003) PCI: Enabling device 0000:00:01.0 (0000 -> 0003) PCI: Enabling device 0000:00:02.0 (0000 -> 0003) PCI: Enabling device 0000:00:03.0 (0000 -> 0003) There was more output when the card still did work, but I don't have it anymore. This is the similar output from my plain Debian test system: Linux Tulip driver version 1.1.13-NAPI (May 11, 2002) PCI: Enabling device 0000:00:00.0 (0000 -> 0003) tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: MII transceiver #1 config 3100 status 7849 advertising 0101. eth0: Digital DS21140 Tulip rev 34 at 0001ec00, 00:00:D1:1D:43:EF, IRQ 21. PCI: Enabling device 0000:00:01.0 (0000 -> 0003) [...] But on EFW, ifconfig doesn't show the interfaces (eth0 to eth3) anymore. I tried giving the card to another virtual machine (plain Debian), and there I can use the NIC without any problems. So I think there's everything fine with the hardware and the host system. Somehow, Endian did recognize the change in hardware and doesn't accept it. What can I do? Thanks in advance! Ciao, Ronald. -- Ronald Schaten :: http://www.schatenseite.de -- Larkinson's Law: All laws are basically false. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
