Re: Installing Buster on a Fit-PC: Can't find the network.
On Thu, 28 May 2020 22:49:58 -0500 David Wright wrote: > On Thu 28 May 2020 at 14:23:31 (-0600), Charles Curley wrote: > > On Fri, 15 May 2020 19:47:02 -0500 David Wright > > wrote: > > > On Fri 15 May 2020 at 16:03:12 (-0600), Charles Curley wrote: > [...] I went further with this, and concluded that the machine in question may have a hardware problem. Let us leave this as "unsolved" and "probably not worth the time to pursue". Thanks for your help. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Installing Buster on a Fit-PC: Can't find the network.
On Thu, 28 May 2020 22:49:58 -0500 David Wright wrote: > On Thu 28 May 2020 at 14:23:31 (-0600), Charles Curley wrote: > > On Fri, 15 May 2020 19:47:02 -0500 David Wright > > wrote: > > > On Fri 15 May 2020 at 16:03:12 (-0600), Charles Curley wrote: > > It shouldn't be. I only mentioned it because the installer mentions > it. I'm sure the d-i itself boots up a non-pae kernel. It does. > > In may depend on how you run the d-i. In expert mode, you get asked, > as you might want to use the installation with less well endowed > hardware. For stretch, the dialogue is Right, I've seen a shorter version of that as well. Probably no pae options. > > > > However, are these the kernel that is installed, or the one that > > runs for the installer? Or both? > > These are packages for installation according to the choice you make > as above (or is made for you). The installer's kernel is the vmlinuz > in installer.386 (one of the three). > Which is not the same as what you showed earlier. According to the hardware summary file (from yesterday's run of the installer): lspci -knn: 00:0d.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10) lspci -knn: Subsystem: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] syslog reports as follows: May 28 18:38:07 kernel: [0.412728] pci :00:0d.0: [10ec:8139] type 00 class 0x02 May 28 18:38:07 kernel: [0.412771] pci :00:0d.0: reg 0x10: [io 0xf800-0xf8ff] May 28 18:38:07 kernel: [0.412797] pci :00:0d.0: reg 0x14: [mem 0xe1014000-0xe10140ff] May 28 18:38:07 kernel: [0.412913] pci :00:0d.0: supports D1 D2 May 28 18:38:07 kernel: [0.412926] pci :00:0d.0: PME# supported from D1 D2 D3hot May 28 18:38:07 kernel: [0.413358] pci :00:0e.0: [10ec:8139] type 00 class 0x02 May 28 18:38:07 kernel: [0.413399] pci :00:0e.0: reg 0x10: [io 0xf400-0xf4ff] May 28 18:38:07 kernel: [0.413425] pci :00:0e.0: reg 0x14: [mem 0xe1014100-0xe10141ff] May 28 18:38:07 kernel: [0.413538] pci :00:0e.0: supports D1 D2 May 28 18:38:07 kernel: [0.413551] pci :00:0e.0: PME# supported from D1 D2 D3hot But I do not see any of the three drivers in the lsmod listing in the hardware summary file. So lspci is finding the hardware but the kernel is neglecting to load the driver. I looked at syslog for a running instance of buster. It has a lot more references to the 8139, including: May 28 15:00:32 chaffee kernel: [0.400872] pci :00:0d.0: [10ec:8139] type 00 class 0x02 May 28 15:00:32 chaffee kernel: [0.400914] pci :00:0d.0: reg 0x10: [io 0xf800-0xf8ff] May 28 15:00:32 chaffee kernel: [0.400939] pci :00:0d.0: reg 0x14: [mem 0xe1014000-0xe10140ff] May 28 15:00:32 chaffee kernel: [0.401049] pci :00:0d.0: supports D1 D2 May 28 15:00:32 chaffee kernel: [0.401063] pci :00:0d.0: PME# supported from D1 D2 D3hot May 28 15:00:32 chaffee kernel: [0.401489] pci :00:0e.0: [10ec:8139] type 00 class 0x02 May 28 15:00:32 chaffee kernel: [0.401529] pci :00:0e.0: reg 0x10: [io 0xf400-0xf4ff] May 28 15:00:32 chaffee kernel: [0.401555] pci :00:0e.0: reg 0x14: [mem 0xe1014100-0xe10141ff] May 28 15:00:32 chaffee kernel: [0.401664] pci :00:0e.0: supports D1 D2 May 28 15:00:32 chaffee kernel: [0.401677] pci :00:0e.0: PME# supported from D1 D2 D3hot Which, other than the host name, looks identical to the above (and should). Further down, there are several lines of output from the driver as it initializes itself and the hardware. Those are not present in the syslog from the installer. > > I checked out the /var/log/installer/syslog and here's the section > that involves the NIC. The first part shows where the modules > originate, the second shows their being used. You can see that the > pae modules are skipped as the installer kernel is non-pae. > (I've removed the timestamps after the first ones): > > Mar 22 20:05:27 anna[1939]: DEBUG: retrieving > mtd-core-modules-4.19.0-5-686-di 4.19.37-5 > anna[1939]: DEBUG: retrieving nic-modules-4.19.0-5-686-di 4.19.37-5 > anna[1939]: DEBUG: retrieving nic-pcmcia-modules-4.19.0-5-686-di 4.19.37-5 > anna[1939]: DEBUG: retrieving nic-shared-modules-4.19.0-5-686-di 4.19.37-5 > anna[1939]: DEBUG: retrieving nic-usb-modules-4.19.0-5-686-di 4.19.37-5 > anna[1939]: DEBUG: retrieving nic-wireless-modules-4.19.0-5-686-di 4.19.37-5 > anna[1939]: DEBUG: retrieving xfs-modules-4.19.0-5-686-di 4.19.37-5 Nope, not in my installer syslog. > [… …] > Mar 22 20:06:27 anna[1939]: DEBUG: retrieving xfsprogs-udeb 4.20.0-1 > main-menu[220]: INFO: Falling back to the package description for brltty-udeb > main-menu[220]: INFO: Falling back to the package description for brltty-udeb > main-menu[220]: INFO: Menu item 'ethdetect' selected > kernel: [ 301.076362] 8139cp: 8139cp: 10/100
Re: Installing Buster on a Fit-PC: Can't find the network.
On Thu 28 May 2020 at 14:23:31 (-0600), Charles Curley wrote: > On Fri, 15 May 2020 19:47:02 -0500 David Wright > 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. It shouldn't be. I only mentioned it because the installer mentions it. I'm sure the d-i itself boots up a non-pae kernel. > In > any case, the installer has kernels for both, and apparently figures out > which to use. In may depend on how you run the d-i. In expert mode, you get asked, as you might want to use the installation with less well endowed hardware. For stretch, the dialogue is │ The list shows the available kernels. Please choose one of them in order to │ │ make the system bootable from the hard drive. │ │ │ │ Kernel to install: │ ┌─│ │ │ │ linux-image-4.9.0-7-686 │ │ │ linux-image-4.9.0-7-686-pae │ │ │ linux-image-586 │ │ │ linux-image-686 │ │ │ linux-image-686-pae │ └─│ none │ > 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? These are packages for installation according to the choice you make as above (or is made for you). The installer's kernel is the vmlinuz in installer.386 (one of the three). > > 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 >
Re: Installing Buster on a Fit-PC: Can't find the network.
I am finally getting back to this. Sorry to take so long. On Fri, 15 May 2020 19:47:02 -0500 David Wright 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
Re: Installing Buster on a Fit-PC: Can't find the network.
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. > 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 > > root@chaffee:~# lsmod | grep 8139 > 8139too32768 0 > 8139cp 28672 0 > mii16384 2 8139cp,8139too > root@chaffee:~# > > These adapters do not require firmware. > > Two questions: > > * 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 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 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 didn't know the installer would find modules, only firmware. 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). Cheers, David.
Installing Buster on a Fit-PC: Can't find the network.
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. 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 root@chaffee:~# lsmod | grep 8139 8139too32768 0 8139cp 28672 0 mii16384 2 8139cp,8139too root@chaffee:~# These adapters do not require firmware. Two questions: * The netinst installer has supported these in the past, including, I believe, 10.0. Or am I mistaken, these are no longer supported. * 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? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
