Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*2\.6\.4\-rc1\s+\+\s+hp100\s+EISA\,\s+not\s+working\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*2\.6\.4\-rc1\s+\+\s+hp100\s+EISA\,\s+not\s+working\s*$/: 20 ]

Total 20 documents matching your query.

1. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Marc Zyngier <mzyngier@xxxxxxxxxxx>; Date: Mon, 01 Mar 2004 11:12:06 +0100; Try passing 'eisa_bus.enable_dev=2' to your kernel parameters. Your card is tagged as unconfigured by BIOS, and thus is skipped by the probing logic. See Documentation/eisa.txt for details. M. -- Pl; /archives/netdev/2004-03/msg00002.html (9,073 bytes)
2. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Marc Zyngier <mzyngier@xxxxxxxxxxx>; Date: Mon, 01 Mar 2004 11:25:25 +0100; Note that hp100 in 2.6.4-rc1 is still broken wrt EISA probing, since it lacks the terminating entry in the EISA ID list. This one-liner should take care of random crashes that are often reported to; /archives/netdev/2004-03/msg00003.html (9,461 bytes)
3. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Mon, 01 Mar 2004 13:45:21 -0500; /archives/netdev/2004-03/msg00008.html (8,442 bytes)
4. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Pawel Sokolowski <falcon@xxxxxxxxxxxxxxx>; Date: Tue, 2 Mar 2004 00:04:11 +0100 (CET); I've seen things you people wouldn't believe. You writing: This machine has RAM BIOS booted from floppy. I ran it and EISA configure utility to check this once more. Card is enabled and not locked. I; /archives/netdev/2004-03/msg00011.html (10,175 bytes)
5. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Pawel Sokolowski <falcon@xxxxxxxxxxxxxxx>; Date: Thu, 4 Mar 2004 06:04:24 +0100 (CET); I've seen things you people wouldn't believe. You writing: [...] With eisa_bus.enable_dev=2 I'm getting: eisa_bus_match dev sig='HWPC061' state=0x1 eids=HWPF180 eisa_bus_match dev sig='HWP1940' state; /archives/netdev/2004-03/msg00037.html (11,009 bytes)
6. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Thu, 4 Mar 2004 09:26:50 -0800; The name HWP1940 is in the table, so that looks okay. Can you build with HP100_DEBUG defined?; /archives/netdev/2004-03/msg00044.html (9,307 bytes)
7. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Paweł Sokołowski <falcon@xxxxxxxxxxxxxxx>; Date: Fri, 5 Mar 2004 01:07:13 +0100 (CET); I've seen things you people wouldn't believe. You writing: OK. I builded module from 2.6.4-rc2 with HP100_DEBUG defined. During compilation: drivers/net/hp100.c: In function `hp100_eisa_probe': drive; /archives/netdev/2004-03/msg00072.html (10,660 bytes)
8. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: >; Date: Mon, 08 Mar 2004 22:55:32 +0100; Ok, found it. It really looks like the new EISA probing code in hp100 never got tested, since a precious offset has disappeared during the rewriting process. Please note that you still need to enabl; /archives/netdev/2004-03/msg00125.html (11,070 bytes)
9. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: >; Date: Mon, 08 Mar 2004 21:26:01 -0500; /archives/netdev/2004-03/msg00133.html (8,846 bytes)
10. 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: xxxxxxxxxxxxxxx>; Date: Sun, 29 Feb 2004 22:06:16 +0100 (CET); I have HP 10/100VG AnyLan EISA card. My machine is a HP Netserver 4d/66LE. 486, EISA only. After latest changes in hp100 driver, it stopped working for me. It oopsed as module on 2.6.2 (and I experi; /archives/netdev/2004-02/msg00721.html (8,396 bytes)
11. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Marc Zyngier <mzyngier@xxxxxxxxxxx>; Date: Mon, 01 Mar 2004 11:12:06 +0100; Try passing 'eisa_bus.enable_dev=2' to your kernel parameters. Your card is tagged as unconfigured by BIOS, and thus is skipped by the probing logic. See Documentation/eisa.txt for details. M. -- Pl; /archives/netdev/2004-03/msg00666.html (9,211 bytes)
12. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Marc Zyngier <mzyngier@xxxxxxxxxxx>; Date: Mon, 01 Mar 2004 11:25:25 +0100; Note that hp100 in 2.6.4-rc1 is still broken wrt EISA probing, since it lacks the terminating entry in the EISA ID list. This one-liner should take care of random crashes that are often reported to; /archives/netdev/2004-03/msg00667.html (9,599 bytes)
13. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Mon, 01 Mar 2004 13:45:21 -0500; applied; /archives/netdev/2004-03/msg00672.html (8,516 bytes)
14. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Pawel Sokolowski <falcon@xxxxxxxxxxxxxxx>; Date: Tue, 2 Mar 2004 00:04:11 +0100 (CET); I've seen things you people wouldn't believe. You writing: This machine has RAM BIOS booted from floppy. I ran it and EISA configure utility to check this once more. Card is enabled and not locked. I; /archives/netdev/2004-03/msg00675.html (10,290 bytes)
15. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Pawel Sokolowski <falcon@xxxxxxxxxxxxxxx>; Date: Thu, 4 Mar 2004 06:04:24 +0100 (CET); I've seen things you people wouldn't believe. You writing: [...] With eisa_bus.enable_dev=2 I'm getting: eisa_bus_match dev sig='HWPC061' state=0x1 eids=HWPF180 eisa_bus_match dev sig='HWP1940' state; /archives/netdev/2004-03/msg00701.html (11,219 bytes)
16. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Thu, 4 Mar 2004 09:26:50 -0800; The name HWP1940 is in the table, so that looks okay. Can you build with HP100_DEBUG defined?; /archives/netdev/2004-03/msg00708.html (9,540 bytes)
17. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Pawe Sokoowski <falcon@xxxxxxxxxxxxxxx>; Date: Fri, 5 Mar 2004 01:07:13 +0100 (CET); I've seen things you people wouldn't believe. You writing: OK. I builded module from 2.6.4-rc2 with HP100_DEBUG defined. During compilation: drivers/net/hp100.c: In function `hp100_eisa_probe': drive; /archives/netdev/2004-03/msg00736.html (10,914 bytes)
18. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Marc Zyngier <mzyngier@xxxxxxxxxxx>; Date: Mon, 08 Mar 2004 22:55:32 +0100; Ok, found it. It really looks like the new EISA probing code in hp100 never got tested, since a precious offset has disappeared during the rewriting process. Please note that you still need to enabl; /archives/netdev/2004-03/msg00789.html (11,244 bytes)
19. Re: 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Mon, 08 Mar 2004 21:26:01 -0500; applied; /archives/netdev/2004-03/msg00797.html (8,984 bytes)
20. 2.6.4-rc1 + hp100 EISA, not working (score: 1): Author: Pawe Sokoowski <falcon@xxxxxxxxxxxxxxx>; Date: Sun, 29 Feb 2004 22:06:16 +0100 (CET); Hi. I have HP 10/100VG AnyLan EISA card. My machine is a HP Netserver 4d/66LE. 486, EISA only. After latest changes in hp100 driver, it stopped working for me. It oopsed as module on 2.6.2 (and I exp; /archives/netdev/2004-02/msg01462.html (8,396 bytes)

Current List: 1 - 20
Page: [1]