hello,
we are trying since weeks to get a 3c597 (eisa version) working in a HP D-
Class Server 9000. [TCM5970 -> is a 3com 3c597]
Kernel:
2.4.26-pa7 & 2.6.7-pa14
2.4.26-pa7: dmesg ->
**** schnipp *****
Searching for devices...
Two devices have hardware path 8. Please file a bug with HP.
In the meantime, you could try rearranging your cards.
Found devices:
1. Phantom PseudoBC GSC+ Port (7) at 0xffc00000 [8], versions 0x504, 0x0, 0x0
2. UL 350 Lasi Core BA (11) at 0xffd00000 [8/16], versions 0x2e, 0x0, 0x81,
additional addresses: 0xffd0c000 0xffc00000
3. UL 350 Core Centronics (10) at 0xffd02000 [8/16/0], versions 0x2e, 0x0,
0x74, additional addresses: 0xffd01000 0xffd03000
4. UL 350 Lasi Core RS-232 (10) at 0xffd05000 [8/16/4], versions 0x2e, 0x0,
0x8c
5. UL 350 Core SCSI (10) at 0xffd06000 [8/16/5], versions 0x2e, 0x0, 0x82
6. UL 350 Core LAN (802.3) (10) at 0xffd07000 [8/16/6], versions 0x2e, 0x0,
0x8a
7. UL 350 Core PS/2 Port (10) at 0xffd08000 [8/16/7], versions 0x2e, 0x0, 0x84
8. UL 350 Core PS/2 Port (10) at 0xffd08100 [8/16/8], versions 0x2e, 0x0, 0x84
9. UL 350 Core Wax BA (11) at 0xffe00000 [8/20], versions 0x30, 0x0, 0x8e
10. UL 350 Wax Core RS-232 (10) at 0xffe02000 [8/20/2], versions 0x30, 0x0,
0x8c
11. UL 350 Wax EISA BA (11) at 0xfc000000 [8/20/5], versions 0x30, 0x0, 0x90,
additional addresses: 0xffc88000
12. UL L2 160 (813/D220,D320) (0) at 0xfffbe000 [62], versions 0x513, 0x0, 0x4
13. Memory (1) at 0xfffbf000 [63], versions 0x80, 0x0, 0x9
CPU(s): 1 x PA7300LC (PCX-L2) at 160.000000 MHz
Lasi version 0 at 0xffd00000 found.
LED display at ffd0c000 registered
Wax at 0xffe00000 found.
Wax EISA Adapter found at 0xfc000000
EISA EEPROM at 0xffc88000
Enumerating EISA bus
EISA slot 1: TCM5970 EISA ioports 1000-1010 IRQ 10
EISA slot 2: INP0500 EISA IRQ 11
EISA slot 3 a configured board was not detected ( expected ___FFFF)
**** schnipp *****
eth0: 82596 at 0xffd07000, 08 00 09 55 02 53 IRQ 87.
**** schnipp *****
2.4.26-pa7: dmesg ->
**** schnipp *****
EISA bus registered
Searching for devices...
Two devices have hardware path 8. Please file a bug with HP.
In the meantime, you could try rearranging your cards.
Found devices:
1. Phantom PseudoBC GSC+ Port at 0xffc00000 [8] { 7, 0x0, 0x504, 0x00000 }
2. UL 350 Lasi Core BA at 0xffd00000 [8/16] { 11, 0x0, 0x02e, 0x00081 },
additional addresses: 0xffd0c000 0xffc00000
3. UL 350 Core Centronics at 0xffd02000 [8/16/0] { 10, 0x0, 0x02e, 0x00074 },
additional addresses: 0xffd01000 0xffd03000
4. UL 350 Lasi Core RS-232 at 0xffd05000 [8/16/4] { 10, 0x0, 0x02e, 0x0008c }
5. UL 350 Core SCSI at 0xffd06000 [8/16/5] { 10, 0x0, 0x02e, 0x00082 }
6. UL 350 Core LAN (802.3) at 0xffd07000 [8/16/6] { 10, 0x0, 0x02e, 0x0008a }
7. UL 350 Core PS/2 Port at 0xffd08000 [8/16/7] { 10, 0x0, 0x02e, 0x00084 }
8. UL 350 Core PS/2 Port at 0xffd08100 [8/16/8] { 10, 0x0, 0x02e, 0x00084 }
9. UL 350 Core Wax BA at 0xffe00000 [8/20] { 11, 0x0, 0x030, 0x0008e }
10. UL 350 Wax Core RS-232 at 0xffe02000 [8/20/2] { 10, 0x0, 0x030, 0x0008c }
11. UL 350 Wax EISA BA at 0xfc000000 [8/20/5] { 11, 0x0, 0x030, 0x00090 },
additional addresses: 0xffc88000
12. UL L2 160 (813/D220,D320) at 0xfffbe000 [62] { 0, 0x0, 0x513, 0x00004 }
13. Memory at 0xfffbf000 [63] { 1, 0x0, 0x080, 0x00009 }
CPU(s): 1 x PA7300LC (PCX-L2) at 160.000000 MHz
Lasi version 0 at 0xffd00000 found.
LED display at ffd0c000 registered
Wax at 0xffe00000 found.
Wax EISA Adapter found at 0xfc000000
EISA EEPROM: cannot register misc device.
Enumerating EISA bus
EISA slot 1: TCM5970 EISA ioports 1000-1010 IRQ 10
EISA slot 2: INP0500 EISA IRQ 11
EISA: Probing bus 0 at parisc8:20:5
EISA: Mainboard HWPC010 detected.
Cannot allocate resource for EISA slot 1
EISA: slot 2 : INP0500 detected.
EISA: Detected 1 card.
**** schnipp *****
eth0: 82596 at 0xffd07000, 08 00 09 55 02 53 IRQ 87.
**** schnipp *****
The cards are configured in a HP 11i.
We had used different Kernel versions, differend slots, build modules and
read.. read ..read.
Have anybody an idea??
thanks fdo
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
