The officially official Devuan Forum!

danista

Member

Registered: 2017-10-18

Posts: 40  

Not detect NIC's from install hd-media

I try to install a devuan_beowulf_3.0.0_i386-netinstall.iso using a hd-media method, from https://pkgmaster.devuan.org/devuan/dis … nt/images/

I have two network cards:

# lspci -k |grep -A3 net
02:05.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
        Subsystem: ASUSTeK Computer Inc. A7V600/P4P800/K8V motherboard
        Kernel driver in use: skge
        Kernel modules: skge
--
02:0d.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
        Subsystem: Intel Corporation EtherExpress PRO/100+ Management Adapter
        Kernel driver in use: e100
        Kernel modules: e100

The installer cannot detect these cards.

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,269  

Re: Not detect NIC's from install hd-media

Would you mind explain what using a hd-media method means with respect to install a devuan_beowulf_3.0.0_i386-netinstall.iso ?

In my mind you either use devuan_beowulf_3.0.0_i386-netinstall.iso or that which you find under https://pkgmaster.devuan.org/devuan/dis … nt/images/. They are two different and separate approaches to use for achieving a situation where you have Devuan installed.

I can understand if one of them, or both, have problems dealing with some hardware (even though at a glance your hardware seems far from obscure) but I'm afraid I can't immediatly understand how to conflate the two installation approaches into one.

danista

Member

Registered: 2017-10-18

Posts: 40  

Re: Not detect NIC's from install hd-media

Thank you for the answer. I put initrd.gz,  vmlinuz from the above source  on the hard drive partition and added to the bootloader:

menuentry "Dev1 beowulf netinst " {
    set root='(hd0,gpt2)'
    linux /boot/linux priority=low vga=788 ---
    initrd /boot/initrd.gz
   }

The hd-media method allows you to install the system from your hard drive, without using a USB flash drive or compact disc drive.

HevyDevy

Member

Registered: 2019-09-06

Posts: 358  

Re: Not detect NIC's from install hd-media

Off topic. So is this like a dual boot method. So say sda1 is main partition and you boot hd-media from bare sda2 partition?

Or can you boot hd-media from a blank disk with only one partition?

Nevermind, i just found the needed documentation. Ive only ever installed via USB and did not know this was an option.

https://www.debian.org/releases/etch/i3 … 05.html.en

Last edited by HevyDevy (2020-06-11 15:01:09)

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,269  

Re: Not detect NIC's from install hd-media

@danista: thanks. Afaiui, that boot entry says (to grub booting)

"after using the kernel and initrd of the boot-up partition, use the file system at partition 2 as (post-pivot) root file system"

That's a different thing from boot-up using the ISO kernel and initrd on partition 2.

It might possibly work if you copy the kernel and initrd from the ISO, where they actually reside in its /boot/isolinux/ directory, to replace the ones you have under /boot on partition 1. You should do that after having otherwise set up partition 1 with a full grub boot including that menuentry to identify partition 2 as (post-pivot) root file system.

I suppose this still brings a period of confusion for the kernel upon pivoting to the root file system, as it results in shadowing the partition 1 /boot tree, but that shouldn't cause an issue unless you then try to install onto partition 1 (or partition 2, of course).

danista

Member

Registered: 2017-10-18

Posts: 40  

Re: Not detect NIC's from install hd-media

I found some links to an existing problem in the installation log

Jun 21 15:16:27 main-menu[244]: INFO: Menu item 'ethdetect' selected
Jun 21 15:16:28 kernel: [  183.236904] intel_rng: FWH not detected
Jun 21 15:16:28 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Jun 21 15:16:32 check-missing-firmware: looking at dmesg again, restarting from \[   28.328526\]
Jun 21 15:16:32 check-missing-firmware: timestamp found, truncating dmesg accordingly
Jun 21 15:16:32 check-missing-firmware: saving timestamp for a later use: [  183.236904]
Jun 21 15:16:32 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Jun 21 15:16:32 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
Jun 21 15:16:32 check-missing-firmware: no missing firmware in loaded kernel modules
Jun 21 15:16:40 check-missing-firmware: looking at dmesg again, restarting from \[  183.236904\]
Jun 21 15:16:40 check-missing-firmware: timestamp found, truncating dmesg accordingly
Jun 21 15:16:40 check-missing-firmware: saving timestamp for a later use:
Jun 21 15:16:40 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Jun 21 15:16:40 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
Jun 21 15:16:40 check-missing-firmware: no missing firmware in loaded kernel modules