[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 <deblis@lionunicorn.co.uk> 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 ./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.

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
[… …]
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 PCI Ethernet driver v1.3 (Mar 22, 2004)
kernel: [  301.076383] 8139cp 0000:00:0e.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
kernel: [  301.177580] 8139too: 8139too Fast Ethernet driver 0.9.28
kernel: [  301.217875] PCI Interrupt Link [LNKB] enabled at IRQ 5
kernel: [  301.218014] PCI: setting IRQ 5 as level-triggered
kernel: [  301.234695] 8139too 0000:00:0e.0 eth0: RealTek RTL8139 at 0x35988a16, 54:e6:fc:82:3f:be, IRQ 5
net/hw-detect.hotplug: Detected hotpluggable network interface lo
kernel: [  301.811162] 8139too 0000:00:0e.0 enp0s14: renamed from eth0
net/hw-detect.hotplug: Detected hotpluggable network interface enp0s14
check-missing-firmware: looking at dmesg again, restarting from \[   71.504225\]
check-missing-firmware: timestamp found, truncating dmesg accordingly
check-missing-firmware: saving timestamp for a later use: [  301.811162]
check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
check-missing-firmware: no missing firmware in loaded kernel modules
check-missing-firmware: taking network interface enp0s14 up/down
kernel: [  304.676284] 8139too 0000:00:0e.0 enp0s14: link up, 100Mbps, full-duplex, lpa 0xC5E1
check-missing-firmware: looking at dmesg again, restarting from \[  301.811162\]
check-missing-firmware: timestamp found, truncating dmesg accordingly
check-missing-firmware: saving timestamp for a later use: [  304.676284]
check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
check-missing-firmware: no missing firmware in loaded kernel modules
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 'netcfg' selected
netcfg[3865]: INFO: Starting netcfg v.1.160
netcfg[3865]: WARNING **: Couldn't read Wpasupplicant pid file, not trying to kill.
netcfg[3865]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline
netcfg[3865]: INFO: Taking down interface enp0s14
netcfg[3865]: INFO: Taking down interface lo
netcfg[3865]: INFO: Activating interface enp0s14
netcfg[3865]: DEBUG: State is now 0
netcfg[3865]: DEBUG: Want link on enp0s14
kernel: [  379.008021] 8139too 0000:00:0e.0 enp0s14: link up, 100Mbps, full-duplex, lpa 0xC5E1
netcfg[3865]: INFO: Waiting time set to 3
netcfg[3865]: INFO: ethtool-lite: enp0s14: carrier up
netcfg[3865]: INFO: Found link on enp0s14
netcfg[3865]: DEBUG: Commencing network autoconfiguration on enp0s14
netcfg[3865]: DEBUG: rdnssd started; PID: 3875
netcfg[3865]: DEBUG: nc_v6_interface_configured(enp0s14, scope local)
netcfg[3865]: DEBUG: Running ip addr show enp0s14 to look for address
netcfg[3865]: DEBUG: ip line: 2: enp0s14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
netcfg[3865]: DEBUG: ip line:     link/ether 54:e6:fc:82:3f:be brd ff:ff:ff:ff:ff:ff
netcfg[3865]: DEBUG: ip line:     inet6 fe80::56e6:fcff:fe82:3fbe/64 scope link 
netcfg[3865]: DEBUG: Configured address found
netcfg[3865]: DEBUG: ip line:        valid_lft forever preferred_lft forever

Cheers,
David.


Reply to: