On Fri, 22 Oct 2021, John Paul Adrian Glaubitz wrote: > > I've modprobe'd the AHA174x kernel module by hand, as it was not inserted > > automatically, but all I got was this line in the syslog: > > ... > > Oct 19 17:07:28 main-menu[245]: INFO: Menu item 'di-utils-shell' selected > > Oct 19 17:11:43 kernel: [ 535.043671] SCSI subsystem initialized > > ... > > Nothing more. According to the documentation the module needs no arguments > > and should auto-probe, but it did not detect any devices. > > I'm currently out of ideas what could be the reason for the device detection not > working, so I'll have to rely on your own debugging work. Either the driver is > missing the hardware IDs for your particular card (maybe it was patched out?!) > or there is an additional module that needs to enabled in the Debian kernel. Device IDs are supposed to be reported for any EISA devices present as the bus is probed, regardless of whether there is a driver available for the particular piece of hardware or not, so it should be possible to see if the expected device is recognised. For example with my EISA box (albeit an x86 one, but this part should be generic, and like the Jensen this is a pure-EISA system, no PCI) I get the following devices listed (and some, but not all claimed by Linux drivers) as the system boots: platform eisa.0: Probing EISA bus 0 eisa 00:00: EISA: Mainboard AEI0401 detected eisa 00:05: EISA: slot 5: DEC3002 detected defxx: v1.12 2021/03/10 Lawrence V. Stefani and others 00:05: DEFEA at I/O addr = 0x5000, IRQ = 10, Hardware addr = 00-00-f8-c8-b3-b6 00:05: registered as fddi0 eisa 00:06: EISA: slot 6: NPI0303 detected eisa 00:08: EISA: slot 8: TCM5094 detected eth0: 3c5x9 found at 0x8000, 10baseT port, address 00:a0:24:b6:8b:db, IRQ 12. platform eisa.0: EISA: Detected 3 cards I can see for AHA174x devices the following IDs have been defined: ADP0000, ADP0001, ADP0002, ADP0400, so check if any are listed in the kernel log. Maciej
