Porteus

Hello guys,

I'm trying to boot Porteus v3.1 on my new machine HP Spectre x360 but at the early boot process, after loading the .xzm modules I see a message of error:

https://www.imageupload.co.uk/image/cqwx

Is there someone who can help me please?
Thank you in advance,

kalo86

Hello people,

Is there someone who may share an update kernel module? I think the boot issue is due to an old kernel...
Thank you,

kalo86

Looks like it may be a hardware issue. Please try updating the kernel using Nekos kernel updater.

Hi brokenman, I'm going to try.
I hope it works with an updated kernel.
See you again here when I have news.

kalo

Hello,
I'm sad to say that with the new kernel (I tested both 4.2.6 and 4.3.0 versions) Porteus v3.1 does not want to boot on my HP laptop...
I don't want to boot Ubuntu (yes, it's the only one which is able to boot at the moment).
I do like only Porteus and/or similar Live OS because I use this one since old times (I was a Slax user, then Slax-Remix, now Porteus!).
What can I do?
I tried to boot also in text mode with no success (I tried also LxQt and KDE graphical desktops with no success).
Any help is much appreciated.
Regards,

kalo86

Hi Brokenman,

I have a great news for you: I successfully booted Nemesis (the latest beta version from your server).
This explains that the issue is due to the old packages of Porteus v3.1.
The new problem is based on me since this is the first time that I run an Arch-based distro and I really don't know how to start from zero.
I hope tp find a good how-to for Nemesis.
If you have any advice, I would appreciate that.
Thank you,

kalo86

The package manager in Arch is called pacman. Read up on that. The Arch documentation si excellent. In Porteus Nemesis the package manager to use is called 'pman' which you can use the same as pacman. The only difference is that it will create a porteus module for you at the end.

Hi,
I have an update: leaving only 000-kernel.xzm and 001-core.xzm in /base folder, I'm finally able to start Porteus v3.1 x86_64 in text mode.
Then I'm sure the problem is inside the last module: 002-xorg.xzm.

I'm thinking to compile one per one each module inside that module and then create a new 002-xorg-updated.xzm module.
Is there someone who can list the file name packages which are inside this xorg module?
Thank you all,

kalo86

hi if you want experimental way pman -S xorg and xorg-server with brokenman script you can merge all packages into one first you have to run the setup-pman that build the xzm packages so you can have the database of the repository index

Beny, at the moment I returned back to Porteus because I have other issues on Porteus-Nemesis...
If I solve the xorg issue on Porteus v3.1, I'm really ok with Porteus in general.
Do you have any advice regarding the xorg module?
Thanks,

kalo86

the brokenman's xorg is build for a portable use i so if you decide to build your xorg have a package more heavy but if you have the space can do it, the arch packages system allow you the downloads of a group of software so xorg,kde, xfce, gnome, the devel-base, plasma,the good thing is the merged option of the pman script,btw you can't use the arch way on the porteus classic.

So, there is no way to update xorg module in Porteus?

you can use the xorg of slackware current the last xorg unpack all the packages and repack in xzm,it is a huge work and the problems with the other base xzm. the nemesis system have the last version of all the base software new gcc gtk and xorg i think you have to focus on nemesis.

kalo86 wrote:Hi,
I have an update: leaving only 000-kernel.xzm and 001-core.xzm in /base folder, I'm finally able to start Porteus v3.1 x86_64 in text mode.
Then I'm sure the problem is inside the last module: 002-xorg.xzm.

I'm thinking to compile one per one each module inside that module and then create a new 002-xorg-updated.xzm module.
Is there someone who can list the file name packages which are inside this xorg module?
Thank you all,

kalo86

You can run lsxzm /path/to/file...it will list all files in the xzm.
Check /var/log/packages.

Thank you roadie, I will try soon.
It will be a long process but in my free time I'll try to do it manually (I have no choise).
Regards,

kalo86