PorteuX 1.7 has been released
PorteuX 1.7 has been released
@Kulle, do you mind testing one of the kernels above?
Also, what exactly happens when you try to use the Linux installer?
Also, what exactly happens when you try to use the Linux installer?
PorteuX 1.7 has been released
sudo file -s /dev/sdb1
/dev/sdb1: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "SYSLINUX", sectors/cluster 64, reserved sectors 44, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 32, sectors 488570848 (volumes > 32 MB), FAT (32 bit), sectors/FAT 59626, reserved 0x1, serial number 0x86de5e1d, unlabeled
guest@porteux:/mnt/sdb1/boot$ ./porteux-installer-for-linux.run
Creating directory /tmp/porteux-installer
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing PorteuX Installer 100%
Please enter root password:
Passwort:
Only 'dos' or 'msdos' partition table is supported.
Format your storage media using partition table 'dos' or 'msdos' and try again
Which kernel should I test?
Where to download?
/dev/sdb1: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "SYSLINUX", sectors/cluster 64, reserved sectors 44, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 32, sectors 488570848 (volumes > 32 MB), FAT (32 bit), sectors/FAT 59626, reserved 0x1, serial number 0x86de5e1d, unlabeled
guest@porteux:/mnt/sdb1/boot$ ./porteux-installer-for-linux.run
Creating directory /tmp/porteux-installer
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing PorteuX Installer 100%
Please enter root password:
Passwort:
Only 'dos' or 'msdos' partition table is supported.
Format your storage media using partition table 'dos' or 'msdos' and try again
Which kernel should I test?
Where to download?
PorteuX 1.7 has been released
Hi,
000-kernel-6.10.6.xzm doesn't work
000-kernel-6.11.4.xzm doesn't work
and now ??
000-kernel-6.10.6.xzm doesn't work
000-kernel-6.11.4.xzm doesn't work
and now ??
PorteuX 1.7 has been released
@Kulle, the message is clear, no? That's not a bug in the installer. You need to have a partition table compatible with dos or msdos, otherwise it's not guaranteed PorteuX will work.
Regarding the kernels, try this:
1. Boot into Text Mode and call 'startx'. If it crashes, please show us /var/log/Xorg.0.log
2. Have you tried in Always Fresh mode?
3. Have you tried to add fsck cheatcode during boot to check/fix partitions?
4. Have you tried to copy vmlinuz and 000-kernel-6.10.6.xzm from PorteuX 1.6 and put them in PorteuX 1.7 to see if PC-b boots?
5. Are you using current or stable?
Regarding the kernels, try this:
1. Boot into Text Mode and call 'startx'. If it crashes, please show us /var/log/Xorg.0.log
2. Have you tried in Always Fresh mode?
3. Have you tried to add fsck cheatcode during boot to check/fix partitions?
4. Have you tried to copy vmlinuz and 000-kernel-6.10.6.xzm from PorteuX 1.6 and put them in PorteuX 1.7 to see if PC-b boots?
5. Are you using current or stable?
PorteuX 1.7 has been released
Hi porteux,
"You need to have a partition table compatible with dos or msdos, otherwise it's not guaranteed PorteuX will work."
Ok
But I use a brand new, unused, commercially available USB stick !
The installer must work, that's to be expected.
The porteus installer has always worked in such cases!
No problems.
I have never bothered with partitioning! I use the USB sticks as they are when I bought them, i.e. vfat
and not divided into partitions
"You need to have a partition table compatible with dos or msdos, otherwise it's not guaranteed PorteuX will work."
Ok
But I use a brand new, unused, commercially available USB stick !
The installer must work, that's to be expected.
The porteus installer has always worked in such cases!
No problems.
I have never bothered with partitioning! I use the USB sticks as they are when I bought them, i.e. vfat
and not divided into partitions
PorteuX 1.7 has been released
Hi porteux,
This kernel works: 000-kernel-6.11.4.xzm 163,7 MiB
But boots slowly !
And sometimes it freezes on "Loading /boot/syslinux/vmlinuz..."
I still use porteuX 0.4 Xfce 4.16
It boots reasonably fast on my 10 year old laptop.
And many modules of Porteus 5.0 work, including the language modules: de_DE-locales-files.xzm etc ...
But why does 1.7 boot slower than 0.4 ?
This kernel works: 000-kernel-6.11.4.xzm 163,7 MiB
But boots slowly !
And sometimes it freezes on "Loading /boot/syslinux/vmlinuz..."
I still use porteuX 0.4 Xfce 4.16
It boots reasonably fast on my 10 year old laptop.
And many modules of Porteus 5.0 work, including the language modules: de_DE-locales-files.xzm etc ...
But why does 1.7 boot slower than 0.4 ?
PorteuX 1.7 has been released
Hi porteux,
I have now tried porteux 1.6 stable Xfce.
doesn't work for me:
INIT: ID "x1" respawning too fast: disabled for 5 minutes
...
xinit : server error
Conclusion:
I continue to use porteux 0.4
because it works without any problems
I have now tried porteux 1.6 stable Xfce.
doesn't work for me:
INIT: ID "x1" respawning too fast: disabled for 5 minutes
...
xinit : server error
Conclusion:
I continue to use porteux 0.4
because it works without any problems
PorteuX 1.7 has been released
Hi porteux,
000-kernel-6.11.4.xzm 163,7 MiB works in 1.7 Xfce
sometimes it freezes on "Loading /boot/syslinux/vmlinuz..."
The freezing happens sporadically, but relatively rarely
The "paplay" command does not exist in 1.7, but it does exist in 0.4
Why?
The "xinput" I added in 0.4 doesn't work in 1.7 either, probably version?
etc. etc.
Various small adjustments are necessary.
It's annoying!
So you should not switch to newer versions too often
000-kernel-6.11.4.xzm 163,7 MiB works in 1.7 Xfce
sometimes it freezes on "Loading /boot/syslinux/vmlinuz..."
The freezing happens sporadically, but relatively rarely
The "paplay" command does not exist in 1.7, but it does exist in 0.4
Why?
The "xinput" I added in 0.4 doesn't work in 1.7 either, probably version?
etc. etc.
Various small adjustments are necessary.
It's annoying!
So you should not switch to newer versions too often
-
- Shogun
- Posts: 204
- Joined: 29 Dec 2010, 08:10
- Distribution: porteus v5.0-xfce K5.19.7
- Location: France
PorteuX 1.7 has been released
@porteux I confirm these modifs are OK for stable and current
Code: Select all
settings-stable
-rwxr-xr-x 1 root 171634688 oct. 23 18:59 000-kernel-6.11.4.xzm*
-rwxr-xr-x 1 root 25878528 oct. 23 18:59 06-crippled_sources-6.11.4.xzm*
-rwxr-xr-x 1 root 9704448 oct. 23 18:58 vmlinuz*
settings-current
-rwxr-xr-x 1 root 171061248 oct. 22 22:40 000-kernel-6.11.4.xzm*
-rwxr-xr-x 1 root 25903104 oct. 22 22:40 06-crippled_sources-6.11.4.xzm*
-rwxr-xr-x 1 root 9839616 oct. 22 22:39 vmlinuz*
PorteuX 1.7 has been released
@Kulle, paplay is part of PulseAudio, but PorteuX has moved to pipewire a long time ago, so most likely you should use pw-play, instead.
Don't know about xinput, since we don't ship it with PorteuX, so maybe you should download the package again (getpkg xinput) and convert it to xzm. I just tested and it works.
Now, regarding the kernel, I'm not sure why your machine is randomly freezing at the kernel loading. It could be your USB stick not working properly, your hardware, your BIOS settings. It's really hard to know since no one can replicate this issue. Also, you haven't properly answered my questions here.
What is your machine full specs?
Don't know about xinput, since we don't ship it with PorteuX, so maybe you should download the package again (getpkg xinput) and convert it to xzm. I just tested and it works.
Now, regarding the kernel, I'm not sure why your machine is randomly freezing at the kernel loading. It could be your USB stick not working properly, your hardware, your BIOS settings. It's really hard to know since no one can replicate this issue. Also, you haven't properly answered my questions here.
What is your machine full specs?
PorteuX 1.7 has been released
@bour59, are you saying that the kernel I posted here works for you 100%?
PorteuX 1.7 has been released
For all people having issues, please report pasting the output of:
And:
Code: Select all
ls /mnt/live/memory/images/
Code: Select all
uname -r
-
- Shogun
- Posts: 204
- Joined: 29 Dec 2010, 08:10
- Distribution: porteus v5.0-xfce K5.19.7
- Location: France
PorteuX 1.7 has been released
@porteux
total 4
drwxr-xr-x 3 root root 26 Oct 23 16:58 000-kernel-6.11.4.xzm/
drwxr-xr-x 21 root root 317 Oct 19 11:42 001-core-stable-20241019.xzm/
drwxr-xr-x 12 root root 178 Oct 19 11:45 002-gui-stable-20241019.xzm/
drwxr-xr-x 5 root root 60 Feb 3 2023 002-xtra-stable-20241019.xzm/
drwxr-xr-x 8 root root 95 Oct 19 11:54 003-xfce-4.18-stable-20241019.xzm/
drwxr-xr-x 2 root root 4096 Oct 25 08:01 changes/
6.11.4-porteux
can confirm boot successfull
startx ok
firefox ok
are you saying that the kernel I posted here works for you 100%?
sorry but I am limited to test exemple I dont use wifi
total 4
drwxr-xr-x 3 root root 26 Oct 23 16:58 000-kernel-6.11.4.xzm/
drwxr-xr-x 21 root root 317 Oct 19 11:42 001-core-stable-20241019.xzm/
drwxr-xr-x 12 root root 178 Oct 19 11:45 002-gui-stable-20241019.xzm/
drwxr-xr-x 5 root root 60 Feb 3 2023 002-xtra-stable-20241019.xzm/
drwxr-xr-x 8 root root 95 Oct 19 11:54 003-xfce-4.18-stable-20241019.xzm/
drwxr-xr-x 2 root root 4096 Oct 25 08:01 changes/
6.11.4-porteux
can confirm boot successfull
startx ok
firefox ok
are you saying that the kernel I posted here works for you 100%?
sorry but I am limited to test exemple I dont use wifi
PorteuX 1.7 has been released
Hi porteux,
There are some peculiarities in version 1.7:
1.) For /mnt/sdb1, the following is displayed:
Size: 232.9 GiB, Free space: 238.4 GB
This looks odd: size 232, free space 238
Two different units of measurement (GiB and GB) are used within a single display.
This is confusing. Who came up with this nonsense?!
Is there a way to configure the system to use only one unit of measurement consistently?
2.) When double-clicking a desktop file, the "untrusted application launcher" window always appears.
This is very annoying. I haven't found a way to disable this.
In version 0.4, these bothersome windows did not appear.
3.) It's unfortunate that there's no backward compatibility.
Version 1.7 lacks commands that were present in version 0.4, such as xclip.
There are some peculiarities in version 1.7:
1.) For /mnt/sdb1, the following is displayed:
Size: 232.9 GiB, Free space: 238.4 GB
This looks odd: size 232, free space 238
Two different units of measurement (GiB and GB) are used within a single display.
This is confusing. Who came up with this nonsense?!
Is there a way to configure the system to use only one unit of measurement consistently?
2.) When double-clicking a desktop file, the "untrusted application launcher" window always appears.
This is very annoying. I haven't found a way to disable this.
In version 0.4, these bothersome windows did not appear.
3.) It's unfortunate that there's no backward compatibility.
Version 1.7 lacks commands that were present in version 0.4, such as xclip.