Porteus-v5.1 alpha 1 bug reports

[Ed_P]

maybe try passing "debug" in the bootparms

I tried debug and tried ls and cat commands but same problem. Any particular debug command/s I should try?
I also tried defragging the ISO, on an SSD drive.

[beny]

hi Ed_P, the porteus-v5.1 alpha cinnamon work on the usb key data, is found by the system, audio work too

Code: Select all

 guest@porteus:~$ inxi -Fxxxx
System:
  Host: porteus.example.net Kernel: 6.12.8-porteus arch: x86_64 bits: 64
    compiler: gcc v: 2.43.1-slack151 clocksource: tsc
  Desktop: Cinnamon v: 6.4.2 tk: GTK v: 3.24.43 wm: Muffin v: 6.4.1 vt: 7
    dm: LXDM Distro: Porteus-v5.1 base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: A320M-S2H v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: A320M-S2H-CF v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: F53
    date: 01/05/2021
CPU:
  Info: 6-core model: AMD Ryzen 5 3500X bits: 64 type: MCP smt: <unsupported>
    arch: Zen 2 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2196 min/max: 2200/4120 boost: enabled cores: 1: 2196
    2: 2196 3: 2196 4: 2196 5: 2196 6: 2196 bogomips: 43119
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: NVIDIA GK107 [GeForce GT 740] vendor: Micro-Star MSI
    driver: nouveau v: kernel arch: Kepler-2 pcie: speed: 2.5 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1 bus-ID: 07:00.0
    chip-ID: 10de:0fc8 class-ID: 0300 temp: 30.0 C
  Display: x11 server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4 driver:
    X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-size: <missing: xdpyinfo>
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HP 24f serial: 3CM9140L0S
    res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.3 vendor: mesa v: 24.2.8 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: NVE7 device-ID: 10de:0fc8
Audio:
  Device-1: NVIDIA GK107 HDMI Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 16
    bus-ID: 07:00.1 chip-ID: 10de:0e1b class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.12.8-porteus status: kernel-api
  Server-1: EsounD v: 0.2.41 status: off
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: b4:2e:99:cb:c7:18
  IF-ID-1: dummy0 state: down mac: a2:4e:18:9b:eb:56
Bluetooth:
  Device-1: CSR8510 A10 driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-6:3 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: not found
    rfk-block: hardware: no software: no address: 00:1A:7D:DA:71:0D
Drives:
  Local Storage: total: 1.85 TiB used: 968.76 GiB (51.2%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB
    speed: 6.0 Gb/s tech: SSD serial: 50026B7782FD7D43 fw-rev: K1B3 scheme: MBR
  ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB
    speed: 6.0 Gb/s tech: SSD serial: 50026B7783E605F8 fw-rev: 62B3 scheme: MBR
  ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
    speed: 6.0 Gb/s tech: SSD serial: S2R6NX1J939251A fw-rev: 2B6Q scheme: GPT
  ID-4: /dev/sdd vendor: Western Digital model: WD10EZRZ-00HTKB0
    size: 931.51 GiB speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: WD-WCC4J3SAA88K
    fw-rev: 1A01 scheme: MBR
  ID-5: /dev/sdf vendor: SanDisk model: Cruzer Blade size: 58.23 GiB
    type: USB rev: 2.0 spd: 480 Mb/s lanes: 1 tech: N/A
    serial: 4C530001120308105554 fw-rev: 1.27 scheme: MBR
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 42.1 C mobo: N/A gpu: nouveau temp: 29.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.72 GiB used: 1.25 GiB (16.2%)
  Processes: 295 Power: uptime: 18m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: SysVinit v: N/A runlevel: 4 default: 4
  Packages: pm: pkgtool pkgs: 608 Compilers: N/A Shell: Bash v: 5.2.37
    running-in: gnome-terminal inxi: 3.3.36
guest@porteus:~$ 

                                                                                                                               

[Ed_P]

An interesting update of a new alpha download.



Added in 18 minutes 4 seconds:
And same results!!



inxi doesn't work in debug mode.

[beny]

hi, inxi you have to use slapt-mod: Raw CD image (application/vnd.efi.iso)
515.9 MB (515899392 bytes)
and i don't have the banner porteus lightning fast,portable, ah maybe i have to boot at init3 to see it
Ed_P your environment maybe is polluted my system don't have the banner also in init3 but i can go wrong on this.

[Ed_P]

Same name, two different sizes, many different dates.





So, 5.1 alpha 1 a daily update? Maybe the ISOs should be named alpha1, alpha2, .... What dates do you have Beny?

[ncmprhnsbl]

So, 5.1 alpha 1 a daily update?

the isos haven't been updated since the announcement.
if you downloaded before that or from a mirror that hadn't synced, that would explain the discrepancy.

[Ed_P]

the isos haven't been updated since the announcement.
if you downloaded before that or from a mirror that hadn't synced, that would explain the discrepancy.

Ok. Any way of noting which mirrors have been updated when announcing the updates?

Can you recommend useful debug commands to try when booting the ISO?

Added in 11 hours 11 minutes 55 seconds:

the build process for the isos is essentially the same as 5.0* ..

While I have booted larger ISOs, for example the 858MB APorteus-XFCE_fr-v24.05.17-x86_64.iso, this 5.1 alpha is the largest Porteus ISO. Maybe the standard build process needs to be reviewed?

[beny]

i have downloaded the iso from http://ftp.nluug.nl/os/Linux/distr/porteus/ and the date of the packages are 1 and 2 january,and why change the iso build work great.i suppose that your system is ok, why you don't try to burn the iso and start from a cd rom player, so you can check if you have trouble with your iso player software.if the cd start and boot

[tome]

Ed_P we know your bootparms but what are your porteus_parms values

[Ed_P]

what are your porteus_parms values

Whatever values are in the ISO file, since that's what I boot. Where would I find said values in the ISO file?

bootparms I have tried are:
set bootparms="volume=33 reboot=cold from=$iso"
set bootparms="volume=33 reboot=cold from=$iso debug"
set bootparms="from=$iso debug"
set bootparms="from=$iso"

Added in 16 minutes 50 seconds:
The new /boot/syslinux/vmlinuz 1/2/25 have porteus_parms?

Added in 14 minutes 13 seconds:

what are your porteus_parms values

An excellent catch tome.

Added in 1 hour 43 minutes 28 seconds:
My porteus_parms values:

set porteus_parms="volume=33 reboot=cold extramod=/Modules"

from my Porteus 5.0 USB menu.

The disadvantage of cut & paste when creating new menus.

My Porteus 5.1_alpha ISO now boots.

I repeat:

An excellent catch tome.

Added in 6 hours 1 minute 32 seconds:
In that the folder /Modules doesn't exist shouldn't the booting error have been "Can't find any extramods" rather than "Can't find the Porteus v5.1 cfg file"?

Added in 1 minute 46 seconds:
And porteus_parms no longer exists in any of my Porteus menus.

Added in 1 hour 49 minutes 36 seconds:
OK, New scenario.

With Porteus 5.01 I have these boot parms:

Code: Select all

set linux_folder=/porteus5.0
set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-241211.iso"
set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules \
       noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;menu2"
search -f $iso --set=root
linux (loop)/boot/syslinux/vmlinuz   from=$iso $bootparms

With Porteus 5.1 alpha I have these boot parms:

Code: Select all

 set linux_folder=/porteu5.0
set iso="/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha-x86_64.iso"
set bootparms="from=$iso volume=33 reboot=cold extramod=$linux_folder/Modules noload=-test;my;My"  
search -f $iso --set=root
linux  (loop)/boot/syslinux/vmlinuz $bootparms # debug

Booting Porteus 5.1 yields:
"^ searching for additional modules in /porteus5.0/Modules
^ couldn't find /porteus5.0/Modules. Correct your from= cheatcode
Documentation in /usr/doc/porteus. Press enter to continue booting."

The point here is; /porteus5.0/Modules exists, is on the same drive as the /ISOs, is found with Porteus 5.01 and black screens with Porteus 5.1.



Added in 33 minutes 32 seconds:
BTW Without the "extramod=$linux_folder/Modules noload=-test;my;My" parms the 5.1alpha ISO boots.

[donald]

About the Audio issue
This is what I have:

Code: Select all

guest@porteus:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC888 Analog [ALC888 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 1: ALC888 Digital [ALC888 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
guest@porteus:~$

This is what I get using pipewire/wireplumber:

Code: Select all

guest@porteus:~$ wpctl status
....................
Audio
 ├─ Devices:
 │      49. Built-in Audio                      [alsa]
 │  
 ├─ Sinks:
 │  *   50. Built-in Audio Digital Stereo (IEC958) [vol: 0.40]
 │  
 ├─ Sources:
 │  *   51. Built-in Audio Digital Stereo (IEC958) [vol: 1.00]
 │  
 ├─ Filters:
 │  
 └─ Streams:

No analog/speakers Audio.

Now the hack:
I can have Audio if I create a sink in /etc/pipewire.conf.
I add to context.objects:

Code: Select all

{ factory = adapter
        args = {
            factory.name           = api.alsa.pcm.sink
            node.name              = "blabla"
            node.description       = "blabla-blub"
            media.class            = "Audio/Sink"
            api.alsa.path          = "hw:0"
            alsa.card              = "0"
            alsa.device            = "0"
            audio.channels         = 2
        }
    }

Now I have:

Code: Select all

guest@porteus:~$ wpctl status
...........................
Audio
 ├─ Devices:
 │      49. Built-in Audio                      [alsa]
 │  
 ├─ Sinks:
 │  *   31. blabla-blub                         [vol: 0.65]
 │      50. Built-in Audio Digital Stereo (IEC958) [vol: 0.35]
 │  
 ├─ Sources:
 │  *   51. Built-in Audio Digital Stereo (IEC958) [vol: 1.00 MUTED]
 │  

and set it as default:

Code: Select all

wpctl set-default 31

...all this should not be necessary!!....PW/WP...another nerdy usability regression.

[Ed_P]

The point here is; /porteus5.0/Modules exists, is on the same drive as the /ISOs, is found with Porteus 5.01 and black screens with Porteus 5.1.

I misspoke! Porteus 5.1 doesn't black screen permanently, it black screens for 24 seconds!! Porteus 5.01's boot screen is only black for about 4 seconds when booting. Not finding the /porteus5.0/Modules folder is still a problem and why Porteus 5.1alpha takes 24 seconds to boot is a new one..

[Blaze]

Ed_P, try this hack Porteus-XFCE-v5.1-alpha-x86_64 (Пост Blaze #101534) and test your boot up of Porteus.

[Ed_P]

Thank you Blaze. An interesting hack but I boot my Cinnamon system as an ISO so I will need to make it into a module.

I think the extramod= cheatcode problem is 5.1-alpha isn't using the $root value when looking for folders with iso boots like 5.01.

Code: Select all

BOOT=`grep -A1 "Porteus data found in:" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`
DRV=${BOOT:5:4}
if [ "$DRV" == "isol" ]; then
   ISOBOOT=`grep -A1 "//porteus" /var/log/porteus-livedbg|tail -n2|sed 's^//^/^g'`
   DRV=${ISOBOOT:5:4}
fi
if [ "$DRV" == "nvme" ]; then
   DRV=${ISOBOOT:5:9}
fi  

An old problem: Wishlist for porteus 3.1

Added in 57 minutes 38 seconds:

I tried adding $root to my bootparms but it didn't help.

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha-x86_64.iso volume=33 reboot=cold extramod=(hd0,gpt7)/porteus5.0/Modules noload=-test;my;My;dat.xzm
guest@porteus:~$
guest@porteus:~$ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/nvme0n1p1: LABEL="ESP" UUID="887E-BEC9" TYPE="vfat"
/dev/nvme0n1p3: LABEL="OS" UUID="44FAA150FAA13F54" TYPE="ntfs"
/dev/nvme0n1p4: UUID="DCD67942D6791E48" TYPE="ntfs"
/dev/nvme0n1p5: LABEL="Image" UUID="9A88A2BF88A29971" TYPE="ntfs"
/dev/nvme0n1p6: LABEL="DELLSUPPORT" UUID="14FCA329FCA30458" TYPE="ntfs"
/dev/nvme0n1p7: LABEL="Data" UUID="FEA6A472A6A42CD9" TYPE="ntfs"
/dev/nvme0n1p8: LABEL="Backups" UUID="A462A67562A64C3C" TYPE="ntfs"

# Booting device:
/mnt/isoloop

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/002-xtra.xzm
/mnt/isoloop/porteus/base/003-cinnamon.xzm

# Base module versions:
001-core.xzm:20250101
002-xorg.xzm:20250101
002-xtra.xzm:20250101
003-cinnamon.xzm:20241222
initrd.xz:20240731

ISO=/mnt/nvme0n1p7//ISOs/Porteus/Porteus-CINNAMON-v5.1-alpha-x86_64.iso
guest@porteus:~$

Added in 20 minutes 47 seconds:
From Porteus 5.01.

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-241211.iso volume=33 reboot=cold extramod=/porteus5.0/Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;menu2
guest@porteus:~$ 
guest@porteus:~$ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/nvme0n1p1: LABEL="ESP" UUID="887E-BEC9" TYPE="vfat"
/dev/nvme0n1p3: LABEL="OS" UUID="44FAA150FAA13F54" TYPE="ntfs"
/dev/nvme0n1p4: UUID="DCD67942D6791E48" TYPE="ntfs"
/dev/nvme0n1p5: LABEL="Image" UUID="9A88A2BF88A29971" TYPE="ntfs"
/dev/nvme0n1p6: LABEL="DELLSUPPORT" UUID="14FCA329FCA30458" TYPE="ntfs"
/dev/nvme0n1p7: LABEL="Data" UUID="FEA6A472A6A42CD9" TYPE="ntfs"
/dev/nvme0n1p8: LABEL="Backups" UUID="A462A67562A64C3C" TYPE="ntfs"

# Booting device:
/mnt/isoloop

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/002-xtra.xzm
/mnt/isoloop/porteus/base/003-cinnamon.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/07-printing-x86_64-2025-01-02.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/Dell6.4.10-wifi.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/Dellautonet.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/Dellsound.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/brother-mfcj4335dwpdrv-3.5.0-1.i386.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/firefox-132.0-x86_64-en-US.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/mychanges.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/wmctrl-1.07-x86_64-2salix15.0.xzm
/mnt/nvme0n1p7//porteus5.0/Modules/xtrmods.xzm

# Base module versions:
001-core.xzm:20241212
002-xorg.xzm:20241212
002-xtra.xzm:20240924
003-cinnamon.xzm:20240924
initrd.xz:20230923

ISO=/mnt/nvme0n1p7//ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-241211.iso
guest@porteus:~$ 

[ncmprhnsbl]

I think the extramod= cheatcode problem is 5.1-alpha isn't using the $root value when looking for folders with iso boots like 5.01.

the thing is, extramod= is handled in initrd and it's is virtually identical between 5.1 and 5.01, apart from the one line in linuxrc to set CFG=porteus-v5.1-$ARCH.cfg.
and only a small difference in finit locate function regarding UUID/LABEL searching, adding a -w (whole word) to grep ..

I tried adding $root to my bootparms but it didn't help.

extramod=(hd0,gpt7)/porteus5.0/Modules

passing grub internal syntax to porteus isn't going to work, i would try a /dev/ or /mnt/ path , if not LABEL or UUID
presumably, eg.:
extramod=/dev/nvme0n1p7/porteus5.0/Modules
or
extramod=LABEL:Data/porteus5.0/Modules