I am finally getting back to this. Sorry to take so long. On Fri, 15 May 2020 19:47:02 -0500 David Wright <[email protected]> wrote:
> On Fri 15 May 2020 at 16:03:12 (-0600), Charles Curley wrote: > > I have several fit-PC 1s. > > https://en.wikipedia.org/wiki/Fit-PC#fit-PC_1.0 I have done fresh > > installs of Buster on two, so it should work. But recently the net > > install ISO (debian-10.0.0-i386-netinst.iso) did not find the two > > Ethernet adapters. > > I don't know why—mine did. It's a Pentium III (with pae). The only > firmware it "requires" is for the Yamaha sound, but because my 386 > laptop needs a couple of bits, I always download the firmware version. > But the kernel package(s) contained within should be identical. My processor does not have pae. I don't know if that is significant. In any case, the installer has kernels for both, and apparently figures out which to use. I have three other identical machines; all three are running Buster as upgraded. > > > root@chaffee:~# lspci -vs 00:0d.0 > > 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > > RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10) Subsystem: > > Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast > > Ethernet Adapter Flags: bus master, medium devsel, latency 64, IRQ > > 10 I/O ports at f800 [size=256] Memory at e1014000 (32-bit, > > non-prefetchable) [size=256] Capabilities: [50] Power Management > > version 2 Kernel driver in use: 8139too > > Kernel modules: 8139cp, 8139too I did boot the installation CD again, and ran lspci there. It found the two Ethernet controllers. > > * The netinst installer has supported these in the past, including, > > I believe, 10.0. Or am I mistaken, these are no longer supported. > > These are the 10.0 kernels from > > 488636416 Jul 6 2019 firmware-10.0.0-i386-netinst.iso > > in iso9660://pool/main/l/linux-signed-i386/ > > 41860120 Jun 20 2019 > linux-image-4.19.0-5-686-pae_4.19.37-5_i386.deb 41548424 Jun 20 2019 > linux-image-4.19.0-5-686_4.19.37-5_i386.deb I have: root@hawk:/media/cdrom# ll pool/main/l/linux-signed-i386/linux-image-4.19.0-5-686* -r--r--r-- 1 root root 41548424 Jun 20 2019 pool/main/l/linux-signed-i386/linux-image-4.19.0-5-686_4.19.37-5_i386.deb -r--r--r-- 1 root root 41860120 Jun 20 2019 pool/main/l/linux-signed-i386/linux-image-4.19.0-5-686-pae_4.19.37-5_i386.deb root@hawk:/media/cdrom# so we are the same there. However, are these the kernel that is installed, or the one that runs for the installer? Or both? > > which contain > > CONTENTS/lib/modules/4.19.0-5-686-pae/kernel/drivers/net/ > > 11344 Jun 19 2019 mii.ko > > CONTENTS/lib/modules/4.19.0-5-686-pae/kernel/drivers/net/ethernet/realtek/ > > 39868 Jun 19 2019 8139cp.ko > 49180 Jun 19 2019 8139too.ko > > CONTENTS/lib/modules/4.19.0-5-686/kernel/drivers/net/ > > 11344 Jun 19 2019 mii.ko > > CONTENTS/lib/modules/4.19.0-5-686/kernel/drivers/net/ethernet/realtek/ > > 39476 Jun 19 2019 8139cp.ko > 49052 Jun 19 2019 8139too.ko I confirm those. root@hawk:/media/cdrom/pool/main/l/linux-signed-i386# dpkg -c linux-image-4.19.0-5-686_4.19.37-5_i386.deb | egrep \(8139\|mii\) -rw-r--r-- root/root 39476 2019-06-19 16:16 ./lib/modules/4.19.0-5-686/kernel/drivers/net/ethernet/realtek/8139cp.ko -rw-r--r-- root/root 49052 2019-06-19 16:16 ./lib/modules/4.19.0-5-686/kernel/drivers/net/ethernet/realtek/8139too.ko -rw-r--r-- root/root 11344 2019-06-19 16:16 ./lib/modules/4.19.0-5-686/kernel/drivers/net/mii.ko root@hawk:/media/cdrom/pool/main/l/linux-signed-i386# dpkg -c linux-image-4.19.0-5-686-pae_4.19.37-5_i386.deb | egrep \(8139\|mii\) -rw-r--r-- root/root 39868 2019-06-19 16:16 ./lib/modules/4.19.0-5-686-pae/kernel/drivers/net/ethernet/realtek/8139cp.ko -rw-r--r-- root/root 49180 2019-06-19 16:16 ./lib/modules/4.19.0-5-686-pae/kernel/drivers/net/ethernet/realtek/8139too.ko -rw-r--r-- root/root 11344 2019-06-19 16:16 ./lib/modules/4.19.0-5-686-pae/kernel/drivers/net/mii.ko root@hawk:/media/cdrom/pool/main/l/linux-signed-i386# > > > * I tried supplying the kernel modules from a working installation. > > The installer looked only at the device itself (/dev/sdb) and not > > at any partitions (/dev/sdb1, /dev/sdb2, etc). Even when I provided > > the drivers on a partitionless device (a USB floppy disk drive), it > > failed to find the modules. How do I set up the media so the > > installer can find the modules? I was not correct here. This time I saved the installation logs. The installer tried to mount each of \dev\sda*, which is the existing hard drive, and /dev/fd0, which is the non-existent floppy drive. It made no attempt to mount \dev\sdb (the USB floppy drive where the modules were located) or \dev\sdb*. Perhaps the installer should walk \dev\sd* in its attempt to find the modules? > > I didn't know the installer would find modules, only firmware. I have used the ability to load modules in the past. > I would try: > > modprobe [--dump-modversions] [filename] > > or > > insmod [filename] > > if modprobe can't load them from any old path (untested— > I've never had to do this). I did not try these. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
