Dev1 Galaxy Forum / [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (Andre4freedom) — Fri, 21 Jul 2023 17:43:30 +0000

And one other note to add:
I've just tested the rc5 netinstall. The USB stick boots correctly, installation is flawless, the system works very well, on both, BIOS-architectures and EFI-architectures.
Good work, thanks to you.

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (Andre4freedom) — Tue, 11 Jul 2023 14:31:12 +0000

Just to conclude that matter,
the desktop-iso (rc4) works like a charm too.
I found no issues with all 3 isos tested. (rc4!)

I suggest to mark the topic resolved...
Thanks to you all

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (sgage) — Sat, 08 Jul 2023 12:00:03 +0000

Ralph,

I burned RC4 to USB using BalenaEtcher. Long story short: I'm coming to you from a shiny new Daedalus install :-)

I used the first installation option, and it proceeded nominally. I selected the MATE Desktop in tasksel, and it seems good.

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (Andre4freedom) — Sat, 08 Jul 2023 09:35:02 +0000

Hello all,
I'm happy to report the new rc4 isos boot correctly from the USB sticks. I have tested the netinstall and server iso.
The desktop iso comes next.
I will report if issues come up again.

So for now life is beautiful and the world is a wonderful place. THANK YOU, Ralph and all concerned.
Have a good day, André

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (Andre4freedom) — Sat, 08 Jul 2023 09:07:00 +0000

I see, the rc4 isos are already there, I will test immediately and report back.

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (ralph.ronnquist) — Sat, 08 Jul 2023 08:02:08 +0000

Thanks. yes that's good confirmation.

The USB problem case came up because the "installer pre-boot" (on those isos) is insufficiently stocked with kernel modules, so it fails to operate that device to find the "actual installer". The onwards iso building is revised to comprehensively include all (current) block device options.

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (Andre4freedom) — Sat, 08 Jul 2023 06:00:41 +0000

Result:
The netinstall iso (rc3) successfully boots into the installer when burned to a CDROM and booted from.
The same iso booted from a USB stick fails.
The test was performed on the very same machine..
And yes, on the CD it's syslinux booting.

I hope the information helps...

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (Andre4freedom) — Sat, 08 Jul 2023 05:36:24 +0000

@ralph.ronnquist,
Sorry for the delay, had a night's rest....
Here the required lspci -v on my Alma Linux installation:

[linuxadmin@coyote ~]$ lspci -v
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, fast devsel, latency 0
	Capabilities: 
	Kernel driver in use: ivb_uncore
	Kernel modules: ie31200_edac

00:02.0 VGA compatible controller: Intel Corporation IvyBridge GT2 [HD Graphics 4000] (rev 09) (prog-if 00 [VGA controller])
	DeviceName:  CPU
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: 
	Kernel driver in use: i915
	Kernel modules: i915

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI])
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, medium devsel, latency 0, IRQ 24
	Memory at f7e20000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: 
	Kernel driver in use: xhci_hcd

00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, fast devsel, latency 0, IRQ 31
	Memory at f7e3c000 (64-bit, non-prefetchable) [size=16]
	Capabilities: 
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) (prog-if 02 [16550])
	Subsystem: Intel Corporation Device 2035
	Flags: 66MHz, fast devsel, IRQ 19
	I/O ports at f0e0 [size=8]
	Memory at f7e3a000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: 
	Kernel driver in use: serial

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
	DeviceName:  L1U1
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, fast devsel, latency 0, IRQ 25
	Memory at f7e00000 (32-bit, non-prefetchable) [size=128K]
	Memory at f7e39000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at f080 [size=32]
	Capabilities: 
	Kernel driver in use: e1000e
	Kernel modules: e1000e

00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, medium devsel, latency 0, IRQ 16
	Memory at f7e38000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: 
	Kernel driver in use: ehci-pci

00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
	DeviceName:  AU1
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, fast devsel, latency 0, IRQ 32
	Memory at f7e30000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: 
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: [disabled]
	Prefetchable memory behind bridge: [disabled]
	Capabilities: 
	Kernel driver in use: pcieport

00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000e000-0000efff [size=4K]
	Memory behind bridge: f7d00000-f7dfffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Capabilities: 
	Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f7e37000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: 
	Kernel driver in use: ehci-pci

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
	I/O behind bridge: [disabled]
	Memory behind bridge: f7c00000-f7cfffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Capabilities: 

00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 04)
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, medium devsel, latency 0
	Capabilities: 
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich

00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 26
	I/O ports at f0d0 [size=8]
	I/O ports at f0c0 [size=4]
	I/O ports at f0b0 [size=8]
	I/O ports at f0a0 [size=4]
	I/O ports at f060 [size=32]
	Memory at f7e36000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: 
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
	Subsystem: Intel Corporation Device 2035
	Flags: medium devsel, IRQ 18
	Memory at f7e35000 (64-bit, non-prefetchable) [size=256]
	I/O ports at f040 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
	DeviceName:  L2U1
	Subsystem: Intel Corporation Device 2035
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at f7d00000 (32-bit, non-prefetchable) [size=128K]
	I/O ports at e000 [size=32]
	Memory at f7d20000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: 
	Kernel driver in use: e1000e
	Kernel modules: e1000e

03:03.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70) (prog-if 10 [OHCI])
	Subsystem: Intel Corporation Device 2035
	Flags: medium devsel, IRQ 10
	Memory at f7c00000 (32-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: 

[linuxadmin@coyote ~]$

I will burn the rc3 iso to a CD and test booting it on that same machine.
I will report back. Thank you all!

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (ralph.ronnquist) — Sat, 08 Jul 2023 04:26:44 +0000

Ok, yes that would be the isolinux (syslinux) menu. That boot case is supposedly the same for the daedalus iso although the actual boot menu is slightly different.

But it also depends on whether the legacy bios sees the USB as a cdrom at /dev/sdX or as a bootable partition at /dev/sdX1. There is then a slight difference between the chimaera and daedalus isos in that the type code for the first partition is 0x00 (Empty) for the chimaera iso and 0x11 (Hidden..) for the daedalus iso. Possibly that difference is what causes your bios to treat them differently.

The upcoming rc4 will be "corrected" to use 0x00 as type code, and in addition include further changes towards handling Andre's use case.

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (sgage) — Sat, 08 Jul 2023 01:53:28 +0000

ralph.ronnquist wrote:

@sgage thanks for those.
It's quite peculiar that the chimaera and daedalus isos have different legacy boot behaviour since they supposedly are the same for legacy boot.
They do differ in UEFI boot loading where chimaera iso has grub whereas daedalus iso has syslinux.
Or, does the working chimaera iso come up as a grub boot menu for you?

I just booted up the working chimaera iso, and it comes up as what I guess is a syslinux menu - at least it doesn't look quite like any grub menu I've ever seen. Now that I think about it, I'm pretty sure that I didn't actually install my current chimaera from an iso at all - I think it might actually be an upgrade from beowulf! And I'm pretty sure that that beowulf install was an upgrade from ascii! What a world!

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (ralph.ronnquist) — Sat, 08 Jul 2023 00:43:21 +0000

@sgage thanks for those.

It's quite peculiar that the chimaera and daedalus isos have different legacy boot behaviour since they supposedly are the same for legacy boot.

They do differ in UEFI boot loading where chimaera iso has grub whereas daedalus iso has syslinux.

Or, does the working chimaera iso come up as a grub boot menu for you?

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (sgage) — Fri, 07 Jul 2023 23:37:35 +0000

ralph.ronnquist wrote:

@Andre4freedom before we close of "missing module" as reason, would you mind posting output of lspci -v from your Alma-linux. (That should tell explicitly which modul(s) are in use).
EDIT: actually, now I realize the installer pre-boot doesn't have ehci-pci (nor ohci-pci) which I think means it doesn't support USB2 or USB1. That's not ideal. Looks like there is an rc4 coming up shortly for that...

Though I did make my USB stick on a USB3 capable stick, and booted from a USB3 port. But I will try rc4...

[edit: I have only been trying the netinstall throughout this conversation]

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (ralph.ronnquist) — Fri, 07 Jul 2023 23:13:12 +0000

@Andre4freedom before we close of "missing module" as reason, would you mind posting output of lspci -v from your Alma-linux. (That should tell explicitly which modul(s) are in use).

EDIT: actually, now I realize the installer pre-boot doesn't have ehci-pci (nor ohci-pci) which I think means it doesn't support USB2 or USB1. That's not ideal. Looks like there is an rc4 coming up shortly for that...

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (sgage) — Fri, 07 Jul 2023 23:09:39 +0000

ralph.ronnquist wrote:

Peculiar.
Would you mind booting up chimaera and show both ls -l /dev/ and lsmod from there?

https://pastebin.com/xHZ4EE21

https://pastebin.com/0bHafJvn

This is from my up to date chimaera install. I am also running a daedalus install for many months, upgraded from chimaera.

Re: [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_*

dummy@example.com (ralph.ronnquist) — Fri, 07 Jul 2023 22:31:01 +0000

Peculiar.
Would you mind booting up chimaera and show both ls -l /dev/ and lsmod from there?