Question about boot message

[benjibasson]

Hi
When I boot porteus V5 with kernel 6.4.10-porteus in copy2ram I got some strenge messages during the boot process before the xfce desktop display

Code: Select all

finished copying to RAM - booting media can be removed safely
changing root directory noauto live system is ready now - starting Porteus
INIT: version 2.96 booting
Additional xzm modules have been found - updating system caches 
dbus [582]: Unknown username "avahi" in message bus configuration file
Triggering udeu events: /sbin/udevadm trigger --action=add 
grep: /mnt/sda3/porteus64bit_v50/porteus/porteus-v5.0-x86_64.cfg: No such file o r directory
grep: /mnt/sda3/porteus64bit_v50/porteus/porteus-v5.0-x86_64.cfg: No such file o r directory
INIT: Entering runlevel: 4
Welcome to Porteus
v5.0

what does it mean

Code: Select all

dbus [582]: Unknown username "avahi" in message bus configuration file?

why does it print

Code: Select all

grep: /mnt/sda3/porteus64bit_v50/porteus/porteus-v5.0-x86_64.cfg: No such file o r directory

althought it is here?

Code: Select all

root@porteus:/home/guest# ls /mnt/sda3/porteus64bit_v50/porteus/porteus-v5.0-x86_64.cfg
/mnt/sda3/porteus64bit_v50/porteus/porteus-v5.0-x86_64.cfg*

boot option in grub2

Code: Select all

menuentry "porteus  on sda3 xfce safe mode"{
set root=(hd0,3)
linux /porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 login=guest copy2ram noswap noauto
initrd /porteus64bit_v50/boot/syslinux/initrd.xz
}

Cheers

[ncmprhnsbl]

these messages are related to /etc/rc.d/rc.S.
the first one is dbus starting and finding a problem related to avahi.. we don't have avahi included, did you install it? if so, looks like you need to create a user(and group) "avahi" for it to work properly.
looking at https://download.salixos.org/x86_64/15. ... /doinst.sh

Code: Select all

# Create user and group
grep -q '^avahi:' /etc/group || groupadd -g 214 avahi
grep -q '^avahi:' /etc/passwd || useradd -u 214 -g 214 -c "Avahi User" -d /dev/null -s /bin/false avahi

and if you're not using changes, make a module containing the modified /etc/{group,passwd} files.

the second ones are bad scripting that will be fixed, that don't cause any harm, just make noise and only seem to appear with the combination of 'noauto' and 'copy2ram'
guessing that maybe at that stage of the booting, the boot device is unmounted.
thanks for the report

[Ed_P]

boot option in grub2

Code: Select all

menuentry "porteus  on sda3 xfce safe mode"{
set root=(hd0,3)
linux /porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 login=guest copy2ram noswap noauto
initrd /porteus64bit_v50/boot/syslinux/initrd.xz

}

A grub2 USB menu I use.

Code: Select all

menuentry " Porteus 5.0 USB - AF'" --class slackware   --class icon-porteus  {

     set porteus_parms="volume=33 reboot=cold extramod=/Modules"  
     set bootdrv=$root
     search -f /boot/syslinux/vmlinuz --set=root
     if [ $root != $bootdrv ]; then
        linux  /boot/syslinux/vmlinuz $porteus_parms
        initrd /boot/syslinux/initrd.xz
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     }

No from=, no login= (since guest is the default).

[benjibasson]

we don't have avahi included, did you install it?

I don't know

[Rava]

^
Can you post the output of these commands when your system is up and running (DE started, then open a terminal)

Code: Select all

cat /etc/porteus/*
ls -lo /mnt/live/memory/images
cat /proc/cmdline

[Ed_P]

Code: Select all

cat /etc/porteus/*
ls -lo /mnt/live/memory/images
cat /proc/cmdline

Excellent suggestion Rava. These 3 commands should be added to Porteus' 002-xtras.xzm module as a command named debug for users to use when asking for help. Maybe with a uname -a command also.

[Rava]

Excellent suggestion Rava. These 3 commands should be added to Porteus' 002-xtras.xzm module as a command named debug for users to use when asking for help. Maybe with a uname -a command also.

Good suggestion, though I recommend the additional info of using [ code ] and [ /code ] when posting on the forum. Since when the user has lots of modules activated the output could be quite extensive.
The [ code ] part is sure not needed when the user can figure out the issue by her/himself with the sole use of debug.sh

[Ed_P]

I recommend the additional info of using [ code ] and [ /code ] when posting on the forum.

I agree.

[Rava]

I recommend the additional info of using [ code ] and [ /code ] when posting on the forum.

I agree.

I think you have the skills needed to craft the script. Wanna give it a try? But please create a new thread since this is getting quite off topic, best in Community effort for now.