Happy to all in 2021
Not before release of Slackware 15
Not before release of Slackware 15
To be even more confusing, check your /var/log/Xorg.0.log :
Code: Select all
guest@porteus:~$ grep "Slackware 15.0" /var/log/Xorg.0.log
[ 54.709] Build Operating System: Slackware 15.0 Slackware Linux Project
Code: Select all
guest@porteus:~$ cat /etc/slackware-version
Slackware 14.2+
confirmedRava wrote: ↑04 Jan 2021, 03:33System 5.0rc2 with 003-xfce-4.12-20201108.xzm
/opt/porteus-scripts/xpsinfo aka 'Porteus System Info' ends with this:Code: Select all
/bin/sh: -c: line 1: syntax error: unexpected end of file Traceback (most recent call last): File "/opt/porteus-scripts/xpsinfo", line 360, in <module> class XPSInfo(Gtk.Window): File "/opt/porteus-scripts/xpsinfo", line 361, in XPSInfo system_info = PSInfo() File "/opt/porteus-scripts/xpsinfo", line 20, in __init__ self.init_infos() File "/opt/porteus-scripts/xpsinfo", line 255, in init_infos fd.write( f.read() ) File "/usr/lib64/python3.8/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 6429: invalid start byte
hmm.. yeah ..whatever was going on there isn't now, for me... for the moment
Code: Select all
# file -b /var/log/*
Code: Select all
# file /var/log/*
/var/log/Xorg.0.log: JSON data
/var/log/btmp: empty
/var/log/cron: ASCII text
/var/log/debug: ASCII text
/var/log/dmesg: JSON data
/var/log/faillog: empty
/var/log/lastlog: empty
/var/log/maillog: empty
/var/log/messages: ASCII text
/var/log/nfsd: directory
/var/log/packages: symbolic link to ../lib/pkgtools/packages
/var/log/pkgtools: directory
/var/log/porteus-livedbg: ASCII text
/var/log/samba: directory
/var/log/scripts: symbolic link to ../lib/pkgtools/scripts
/var/log/secure: ASCII text
/var/log/setup: symbolic link to ../lib/pkgtools/setup
/var/log/slim.log: ASCII text
/var/log/syslog: ASCII text
/var/log/wtmp: data
although that's not the issue here, it's on my todo list (and for various other of the new scripts)
I think you meantncmprhnsbl wrote: ↑12 Jan 2021, 13:12@Rava (or anyone else who experiences this) . if xpsinfo fails with that error^
please do: (as root)Code: Select all
# file -b /var/log/*
Code: Select all
# file /var/log/*
Code: Select all
root@porteus:/# file /var/log/*
/var/log/Xorg.0.log: JSON data
/var/log/btmp: empty
/var/log/cron: ASCII text
/var/log/debug: ASCII text
/var/log/dmesg: JSON data
/var/log/faillog: empty
/var/log/lastlog: data
/var/log/maillog: empty
/var/log/messages: Non-ISO extended-ASCII text
/var/log/messages.1.gz: gzip compressed data, last modified: Mon Jan 11 18:29:34 2021, from Unix, original size modulo 2^32 773525
/var/log/nfsd: directory
/var/log/openbox-changelog: ASCII text
/var/log/packages: symbolic link to ../lib/pkgtools/packages
/var/log/pkgtools: directory
/var/log/porteus-livedbg: ASCII text
/var/log/samba: directory
/var/log/scripts: symbolic link to ../lib/pkgtools/scripts
/var/log/secure: ASCII text, with very long lines
/var/log/setup: symbolic link to ../lib/pkgtools/setup
/var/log/syslog: ASCII text, with very long lines
/var/log/wtmp: data
Code: Select all
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing Porteus Installer 100%
_.====.._
,:._ ~-_
'\ ~-_
\ \.
,/ ~-_
-..__..-'' PORTEUS ~~--..__
==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--
Installing Porteus to /dev/mmcblk0p1
WARNING: Make sure this is the right partition before proceeding.
Type 'ok' to continue or press Ctrl+c to exit.
ok
Flushing filesystem buffers...
Installation failed with error code '2'.
Please ask for help on the Porteus forum: www.porteus.org/forum
and provide the information from /mnt/mmcblk0p1/boot/debug.txt
Exiting now...
cat: /mnt/mmcblk0p1/boot/syslinux/lilo.menu: No such file or directory
Code: Select all
device: /dev/mmcblk0
partition: /dev/mmcblk0p1
partition number: p1
partition mount point: /mnt/mmcblk0p1
installation path: /mnt/mmcblk0p1/boot
subfolder:
filesystem: ext2
bootloader: lilo
error code: 2
system: porteus.example.net 5.4.30-porteus x86_64
mount details: /dev/mmcblk0p1 /mnt/mmcblk0p1 ext2 rw,noatime,nodiratime 0 0
[…]
Disk /dev/mmcblk0: 1.84 GiB, 1977614336 bytes, 3862528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 135 3858623 3858489 1.8G 83 Linux
The device is in a /mnt/ directory - /mnt/mmcblk0p1 .
Code: Select all
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing Porteus Installer 100%
_.====.._
,:._ ~-_
'\ ~-_
\ \.
,/ ~-_
-..__..-'' PORTEUS ~~--..__
==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--
Installing Porteus to /dev/sdd1
WARNING: Make sure this is the right partition before proceeding.
Type 'ok' to continue or press Ctrl+c to exit.
ok
Flushing filesystem buffers...
Using extlinux bootloader.
Installation finished successfully.
You may reboot your PC now and start using Porteus.
Please check the /boot/docs folder for additional information about
the installation process, Porteus requirements and booting parameters.
In case of making tweaks to the bootloader config,
please edit: /mnt/sdd1/boot/syslinux/porteus.cfg file.
Press Enter to exit.
Could be a slot for both, you definitely can insert and mount a secure digital card in it - as seen in what debug.txt above reports.
I thought my BIOS "choose device to boot from screen" showed me the card reader if one is inserted during boot…
Code: Select all
MMCBLK0P2 has unsupported feature: METADATA_CSUM
Get a new version of e2fsck !
Code: Select all
Init ID "x1" respawning too fast. Disabled for 5 minutes.