The officially official Devuan Forum!

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

I'm sorry to report problems with the latest iso image files of daedalus rc2. (devuan_daedalus_5.0.0-rc2_amd64_netinstall.iso)
I have tested all rc2 isos, they all behave the same.
The problem occurs on some pure UEFI machines (GPT disk geometry) as well as on older machines (BIOS & MBR-geometry)
On some machines, the system would eventually boot into the installation, not at all on others.

I did try to boot the Debian 12 netinstall ISO and this one works perfectly well, as most other distro-isos do.

I'm not good enough to debug that, therefor I just report back to the community.

I hope this link to the screenshot works...
https://i.postimg.cc/4xjmyJRN/Screensho … -53-27.png

Have a great day - Andre

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

Ah, and of course, the machine is completely dead after this error message... Have to power it down.

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

Quite possibly we could turn this into a useful bug report; just describe in some detail which media you used and how did you prepare that? A memory stick or an actual CD? I assume you verified the sha256sum, but it's good if you confirm that.

EDIT: I seem to have ignored the title.. a USB would be a memory stick...

So how did you prepare it?

Could you run again and use the emergency shell to report the output from ls -l /dev

If you can install another USB stick, you could mount that and then copy /var/log/syslog to it, and put that into a code block of a post here.

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

Yes, right, these were the isos tested:
https://files.devuan.org/devuan_daedalu … nstall.iso
https://files.devuan.org/devuan_daedalu … server.iso
https://files.devuan.org/devuan_daedalu … esktop.iso

Procedure:
1. Downloaded the files
2. Verified the checksums (sha256sum)
3. copied the files onto different USB sticks
   (sudo dd if=devuan_daedalus_5.0.0-rc2_amd64_server.iso of=/dev/sdb bs=4M status=progress && sync)
4. Reset BIOS or EFI settings to default, disabled "secure-boot"
5. Inserted USB stick and tried to boot from it.

Important: After the attempt (as seen on screenshot) the computer, keyboard, everything was dead as in "dead". Had to power-cycle the computer to start again.

I tried on different machines. One of them (EFI-type machine) finally booted from the stick, the others did not (EFI and BIOS-types), they just locked up.

I have to say that an earlier daedalus-iso (early 2023)booted successfully on all machines.
If you need more info, please tell me and I will try to assist.
I'm really glad if you could bug-report it - I have rarely done so before... Thanks in advance!

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

Yes I'll deal with reporting.

Which hardware is this?

EDIT:  Also, in the emergency shell: run "fdisk -l" and capture that output (too).

oui

Member

Registered: 2017-09-02

Posts: 305  

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

try only this

with the browser:
https://files.devuan.org/devuan_daedalu … nstall.iso

and prepare your stick following those steps:

with gparted:
- new table (after that, ALL on the stick is erased!)
- new partition
- format fat16 , yes 16, not 32 (under 4 GB iso SIZE)
- set boot flag (don't forget that!)

with the konsole:
dd if=~/Downloads/devuan_daedalus_5.0.0-rc2_amd64_netinstall.iso of=/dev/... status=progress (change the ... into the target found by gparted BUT WITHOUT THE PARTITION No. (for ex. sdc and not sdc1!)

good luck!

note: you would spare energy using a derivate of Devuan offered with a "raisonable" installer! The Debian installer is shocking bad for users!

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

@Ralph: No problem,

I did a normal boot into the installed system to get the information:

Alma Linux 9.1

[linuxadmin@coyote ~]$ cat /etc/redhat-release 
AlmaLinux release 9.1 (Lime Lynx)
[linuxadmin@coyote ~]$

[linuxadmin@coyote ~]$ sudo fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD1000DHTZ-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 241CA6FA-A72E-437A-81A7-FDDE97E615BF

Device       Start        End    Sectors   Size Type
/dev/sda1     2048    1230847    1228800   600M EFI System
/dev/sda2  1230848    3327999    2097152     1G Linux filesystem
/dev/sda3  3328000 1953523711 1950195712 929.9G Linux LVM

Disk /dev/mapper/almalinux-root: 70 GiB, 75161927680 bytes, 146800640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/almalinux-swap: 7.78 GiB, 8355053568 bytes, 16318464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/almalinux-home: 852.14 GiB, 914979028992 bytes, 1787068416 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
[linuxadmin@coyote ~]$ 

Question: do you need the complete dmidecode output?
Here the essential information first:

[linuxadmin@coyote ~]$ sudo dmidecode -t bios
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: Intel Corp.
	Version: MKQ7710H.86A.8064.2013.1120.1214
	Release Date: 11/20/2013
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 12 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 4.6

Handle 0x005E, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 1
		en|US|iso8859-1
	Currently Installed Language: en|US|iso8859-1

[linuxadmin@coyote ~]$ sudo dmidecode -t system
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Netree AG
	Product Name: netPC
	Version:                                  
	Serial Number:                                  
	UUID: d5d9e0e1-8e94-e211-8fc5-2c27d725b21d
	Wake-up Type: Power Switch
	SKU Number: To be filled by O.E.M.
	Family: To be filled by O.E.M.

Handle 0x0021, DMI type 12, 5 bytes
System Configuration Options
	Option 1: To Be Filled By O.E.M.

Handle 0x0022, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

[linuxadmin@coyote ~]$ sudo dmidecode -t baseboard
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: Intel Corporation
	Product Name: DQ77MK
	Version: AAG39642-500
	Serial Number: BTMK312008X0
	Asset Tag: To be filled by O.E.M.
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: To be filled by O.E.M.
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x001F, DMI type 10, 12 bytes
On Board Device 1 Information
	Type: Video
	Status: Enabled
	Description: Intel(R) HD Graphics Device
On Board Device 2 Information
	Type: Ethernet
	Status: Enabled
	Description: Intel(R) 82579LM Gigabit Ethernet Device
On Board Device 3 Information
	Type: Sound
	Status: Enabled
	Description: Intel(R) High Definition Audio Device
On Board Device 4 Information
	Type: Ethernet
	Status: Enabled
	Description: Intel(R) 82574L Gigabit Ethernet Device

Handle 0x0038, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  CPU
	Type: Video
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:02.0

Handle 0x0039, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  L1U1
	Type: Ethernet
	Status: Enabled
	Type Instance: 2
	Bus Address: 0000:00:19.0

Handle 0x003A, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  AU1
	Type: Sound
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:1b.0

Handle 0x003B, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  L2U1
	Type: Ethernet
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:02:00.0

[linuxadmin@coyote ~]$ sudo dmidecode -t chassis
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer:                                  
	Type: Desktop
	Lock: Not Present
	Version:                                  
	Serial Number:                                  
	Asset Tag:                                  
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: To be filled by O.E.M.

[linuxadmin@coyote ~]$ sudo dmidecode -t processor
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0040, DMI type 4, 42 bytes
Processor Information
	Socket Designation: CPU 1
	Type: Central Processor
	Family: Core i7
	Manufacturer: Intel(R) Corporation
	ID: A9 06 03 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 58, Stepping 9
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
	Voltage: 11.1 V
	External Clock: 100 MHz
	Max Speed: 3800 MHz
	Current Speed: 3400 MHz
	Status: Populated, Enabled
	Upgrade: Socket BGA1155
	L1 Cache Handle: 0x003D
	L2 Cache Handle: 0x003C
	L3 Cache Handle: 0x003E
	Serial Number: Not Specified
	Asset Tag: Fill By OEM
	Part Number: Fill By OEM
	Core Count: 4
	Core Enabled: 4
	Thread Count: 8
	Characteristics:
		64-bit capable

[linuxadmin@coyote ~]$ sudo dmidecode -t memory
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x003F, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 32 GB
	Error Information Handle: Not Provided
	Number Of Devices: 4

Handle 0x0041, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x003F
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: DIMM3
	Bank Locator: CHANNEL A SLOT0
	Type: Unknown
	Type Detail: None

Handle 0x0042, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x003F
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8 GB
	Form Factor: DIMM
	Set: None
	Locator: DIMM1
	Bank Locator: CHANNEL A SLOT1
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1333 MT/s
	Manufacturer: Kingston
	Serial Number: 1518CBE5
	Asset Tag: 9876543210
	Part Number: 99U5458-036.A00LF 
	Rank: 2
	Configured Memory Speed: 1333 MT/s

Handle 0x0044, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x003F
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: DIMM4
	Bank Locator: CHANNEL B SLOT0
	Type: Unknown
	Type Detail: None

Handle 0x0045, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x003F
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8 GB
	Form Factor: DIMM
	Set: None
	Locator: DIMM2
	Bank Locator: CHANNEL B SLOT1
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1333 MT/s
	Manufacturer: Kingston
	Serial Number: 1B18C3E5
	Asset Tag: 9876543210
	Part Number: 99U5458-036.A00LF 
	Rank: 2
	Configured Memory Speed: 1333 MT/s

[linuxadmin@coyote ~]$ sudo dmidecode -t cache
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x003C, DMI type 7, 19 bytes
Cache Information
	Socket Designation: CPU Internal L2
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Through
	Location: Internal
	Installed Size: 1 MB
	Maximum Size: 1 MB
	Supported SRAM Types:
		Unknown
	Installed SRAM Type: Unknown
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 8-way Set-associative

Handle 0x003D, DMI type 7, 19 bytes
Cache Information
	Socket Designation: CPU Internal L1
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Through
	Location: Internal
	Installed Size: 256 kB
	Maximum Size: 256 kB
	Supported SRAM Types:
		Unknown
	Installed SRAM Type: Unknown
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x003E, DMI type 7, 19 bytes
Cache Information
	Socket Designation: CPU Internal L3
	Configuration: Enabled, Not Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 8 MB
	Maximum Size: 8 MB
	Supported SRAM Types:
		Unknown
	Installed SRAM Type: Unknown
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 16-way Set-associative

Please note that the install boot process fails before any disk-access. It boots from the USB stick. Boot from hard disk is no problem.
Just tell me if you need more... Glad to know you at my side. Thanks.

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

Thanks. Good information showing "normal" hardware, but I need more

In summary it seems that machine is able to load the pre-boot system if booted in UEFI mode, but not if booted in legacy mode. (is that correct? or does the installer start equivalently in legacy mode?)

One of possible reasons for such an outcome is if the USB stick requires a kernel module (device driver) that is missing from from the pre-boot system, and that is the information I am looking for.

For example, what does the Alma-linux system log say when the USB stick is inserted? Which kernel modules get loaded?.

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

WOW, you are pointing to a good direction....
here the required information:

The system has
- UEFI Boot enabled
- Legacy Boot enabled
- Secure Boot disabled

Booting the Devuan5 rc2 USB stick in UEFI mode: fails
Booting the Devuan5 rc2 USB stick in Legacy mode: fails

In both ways: the output shows:
= = 0 Devuan boot preamble = = =
And then fails miserably (locked completely up, dead, after messages complaining about unable to mount cdrom...)

The same test with Debian 12 goes well and boots successfully into the installer.

here is the extract from /var/log/messages in Alma Linux when inserting that Devuan 5 rc2 USB stick>:

Jul  7 09:11:34 coyote systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jul  7 09:11:34 coyote systemd[1]: systemd-localed.service: Deactivated successfully.
Jul  7 09:11:42 coyote chronyd[1016]: Selected source 83.150.25.25 (2.almalinux.pool.ntp.org)
Jul  7 09:11:43 coyote journal[1628]: Service not used for 60 seconds. Shutting down..
Jul  7 09:11:43 coyote systemd[1]: geoclue.service: Deactivated successfully.
Jul  7 09:11:45 coyote systemd[1]: realmd.service: Deactivated successfully.
Jul  7 09:12:07 coyote PackageKit[1632]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Jul  7 09:12:07 coyote PackageKit[1632]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Jul  7 09:12:08 coyote systemd[1]: Starting Fingerprint Authentication Daemon...
Jul  7 09:12:08 coyote systemd[1]: Started Fingerprint Authentication Daemon.
Jul  7 09:12:28 coyote kernel: usb 1-1.6: new high-speed USB device number 5 using ehci-pci
Jul  7 09:12:28 coyote kernel: usb 1-1.6: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
Jul  7 09:12:28 coyote kernel: usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul  7 09:12:28 coyote kernel: usb 1-1.6: Product: Ultra
Jul  7 09:12:28 coyote kernel: usb 1-1.6: Manufacturer: SanDisk
Jul  7 09:12:28 coyote kernel: usb 1-1.6: SerialNumber: 4C530001270914118551
Jul  7 09:12:28 coyote kernel: usb-storage 1-1.6:1.0: USB Mass Storage device detected
Jul  7 09:12:28 coyote kernel: scsi host7: usb-storage 1-1.6:1.0
Jul  7 09:12:28 coyote mtp-probe[2898]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
Jul  7 09:12:28 coyote mtp-probe[2898]: bus: 1, device: 5 was not an MTP device
Jul  7 09:12:28 coyote mtp-probe[2899]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
Jul  7 09:12:28 coyote mtp-probe[2899]: bus: 1, device: 5 was not an MTP device
Jul  7 09:12:29 coyote kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
Jul  7 09:12:29 coyote kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
Jul  7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] 30464000 512-byte logical blocks: (15.6 GB/14.5 GiB)
Jul  7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] Write Protect is off
Jul  7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul  7 09:12:29 coyote kernel: sdf: sdf1 sdf2
Jul  7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] Attached SCSI removable disk
Jul  7 09:12:30 coyote journal[952]: Mounted /dev/sdf1 at /run/media/linuxadmin/DEVUAN5 on behalf of uid 1000
Jul  7 09:12:36 coyote systemd[1]: virtqemud.service: Deactivated successfully.
Jul  7 09:12:39 coyote systemd[1]: fprintd.service: Deactivated successfully.
Jul  7 09:13:05 coyote systemd[1985]: Starting Mark boot as successful...
Jul  7 09:13:05 coyote systemd[1985]: Finished Mark boot as successful.
Jul  7 09:13:51 coyote chronyd[1016]: Selected source 195.186.1.100 (2.almalinux.pool.ntp.org)
Jul  7 09:14:30 coyote systemd-logind[950]: New session 4 of user linuxadmin.
Jul  7 09:14:30 coyote systemd[1]: Started Session 4 of User linuxadmin.
Jul  7 09:14:30 coyote systemd[1]: Starting Hostname Service...
Jul  7 09:14:30 coyote systemd[1]: Started Hostname Service.
Jul  7 09:15:00 coyote systemd[1]: systemd-hostnamed.service: Deactivated successfully.
(END)

And here the output of lsmod after plugging the stick in:

[linuxadmin@coyote ~]$ lsmod > modules.text
[linuxadmin@coyote ~]$ cat modules.text 
Module                  Size  Used by
nls_utf8               16384  1
isofs                  49152  1
uinput                 20480  0
snd_seq_dummy          16384  0
snd_hrtimer            16384  1
nft_fib_inet           16384  1
nft_fib_ipv4           16384  1 nft_fib_inet
nft_fib_ipv6           16384  1 nft_fib_inet
nft_fib                16384  3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet
nft_reject_inet        16384  6
nf_reject_ipv4         16384  1 nft_reject_inet
nf_reject_ipv6         20480  1 nft_reject_inet
nft_reject             16384  1 nft_reject_inet
nft_ct                 24576  21
nft_chain_nat          16384  3
nf_nat                 57344  1 nft_chain_nat
nf_conntrack          176128  2 nf_nat,nft_ct
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
bridge                315392  0
stp                    16384  1 bridge
llc                    16384  2 bridge,stp
ip_set                 61440  0
rfkill                 36864  3
nf_tables             270336  276 nft_ct,nft_reject_inet,nft_fib_ipv6,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet
nfnetlink              20480  3 nf_tables,ip_set
qrtr                   49152  4
sunrpc                667648  1
vfat                   20480  1
fat                    86016  1 vfat
intel_rapl_msr         20480  0
intel_rapl_common      28672  1 intel_rapl_msr
x86_pkg_temp_thermal    20480  0
intel_powerclamp       20480  0
snd_hda_codec_hdmi     81920  1
coretemp               20480  0
snd_hda_codec_realtek   167936  1
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
ledtrig_audio          16384  1 snd_hda_codec_generic
snd_hda_intel          57344  2
kvm_intel             385024  0
snd_intel_dspcfg       32768  1 snd_hda_intel
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
kvm                  1105920  1 kvm_intel
snd_hda_codec         176128  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core          110592  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep              16384  1 snd_hda_codec
snd_seq                94208  7 snd_seq_dummy
snd_seq_device         16384  1 snd_seq
irqbypass              16384  1 kvm
iTCO_wdt               16384  0
rapl                   24576  0
iTCO_vendor_support    16384  1 iTCO_wdt
snd_pcm               151552  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
mei_wdt                16384  0
snd_timer              49152  3 snd_seq,snd_hrtimer,snd_pcm
snd                   118784  16 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
mei_me                 49152  1
intel_cstate           24576  0
mei                   155648  3 mei_wdt,mei_me
i2c_i801               32768  0
soundcore              16384  1 snd
intel_uncore          225280  0
lpc_ich                28672  0
pcspkr                 16384  0
i2c_smbus              20480  1 i2c_i801
xfs                  2002944  3
libcrc32c              16384  4 nf_conntrack,nf_nat,nf_tables,xfs
sr_mod                 28672  0
cdrom                  81920  2 isofs,sr_mod
sd_mod                 65536  6
t10_pi                 16384  1 sd_mod
sg                     40960  0
i915                 3321856  4
i2c_algo_bit           16384  1 i915
intel_gtt              24576  1 i915
drm_buddy              20480  1 i915
drm_dp_helper         159744  1 i915
drm_kms_helper        200704  2 drm_dp_helper,i915
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
cec                    53248  2 drm_dp_helper,i915
ttm                    86016  1 i915
ahci                   49152  3
libahci                49152  1 ahci
crct10dif_pclmul       16384  1
crc32_pclmul           16384  0
drm                   622592  7 drm_dp_helper,drm_kms_helper,drm_buddy,i915,ttm
libata                389120  2 libahci,ahci
crc32c_intel           24576  1
e1000e                323584  0
ghash_clmulni_intel    16384  0
video                  57344  1 i915
uas                    32768  0
usb_storage            81920  2 uas
dm_mirror              28672  0
dm_region_hash         24576  1 dm_mirror
dm_log                 20480  2 dm_region_hash,dm_mirror
dm_mod                184320  12 dm_log,dm_mirror
fuse                  176128  3
[linuxadmin@coyote ~]$

It shows that the module "usb_storage            81920  2 uas" is present.
I hope that helps.... I'm ready to give more information if required. Thank you so much!
André

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

Thanks!
Evidently the installer pre-boot is missing the scsi block device support.
There will be an rc3 drop shortly without that problem.

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

You are a hero Ralph, thank you!
I will test it when it appears and report back.
Have a good day.

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

Unfortunately, the problem is still present in the rc3 files.
I have tested the netinstall-iso and the server-iso.
Does it help if I try to burn CDs with these rc3 files and test again?

sgage

Member

Registered: 2016-12-01

Posts: 341  

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

Ralph and Andre,

For what it's worth, I, too, was unable to boot RC2 or RC3. I tried several different methods of making a USB stick. Just a featureless black screen, not even a blinking cursor - had to cycle power to get out.

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

I assume you still see the bootloader menu?
If so, try by pushing TAB, then remove "nomodeset" and then push ENTER... does that start up the installer?

If you don't seen the bootloader menu then the problem is at the ISO format level. That's a bit harder to debug.
Does chimaera netinstall work for you?

Note: the dd command of post#4 above is typically good, though I think there might be bogus variants of dd on some (non-linux) platforms.

sgage

Member

Registered: 2016-12-01

Posts: 341  

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

I assume you still see the bootloader menu?
If so, try by pushing TAB, then remove "nomodeset" and then push ENTER... does that start up the installer?

If you don't seen the bootloader menu then the problem is at the ISO format level. That's a bit harder to debug.
Does chimaera netinstall work for you?

Note: the dd command of post#4 above is typically good, though I think there might be bogus variants of dd on some (non-linux) platforms.

I do not even get to the bootloader menu. I boot from the USB stick, and get... a black screen. Like I said, nothing, not a cursor, not anything.

Chimaera netinstall worked fine for me. I have tried dd, Rufus, BalenaEtcher, Ventoy. No joy.

- Steve

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

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

sgage

Member

Registered: 2016-12-01

Posts: 341  

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

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.

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

@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...

sgage

Member

Registered: 2016-12-01

Posts: 341  

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

@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]

Last edited by sgage (2023-07-07 23:47:35)

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

@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?

sgage

Member

Registered: 2016-12-01

Posts: 341  

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

@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!

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

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.

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

@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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>

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: <access denied>
	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: <access denied>
	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: <access denied>
	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: <access denied>

[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!

Andre4freedom

Member

Registered: 2017-11-15

Posts: 174  

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

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...

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,253  

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

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.