Put nVidia-legacy-96.43.20-porteus-v1.1-x86_64-2beny into the base folder.
Starting lxde won't work, even when I started Porteus with the LXDE cheatcode from porteus.cfg
When I logged into the virtual terminal first as root, Porteus started X, seemingly as user root...
I thought prior the 1.0 finale it was a poll if X should be started as root or as non-root user and the majority voted for "non-root user"
(X was started with the generic /etc/X11/xorg.conf, while trying to start X as guest gave only an error and I needed to run nvidia-xconfig first)
So, I killed this X session. I also killed it, because I started 1.1 Porteus with the LXDE menu entry, still it started KDE.... And that, as LXDE or XFCe user is a no go.
Now, trying to start LXDE with startx from the guest account not works, it only starts KDE again.
Trying to start LXDE with startlxde does nothing from the console.
Again I need to go - just like I needed with 1.0 - to /etc/X11/xinit and do this as root:
Code: Select all
root@porteus:/etc/X11/xinit# rm xinitrc root@porteus:/etc/X11/xinit# ln -s xinitrc.lxde xinitrc
it made a nasty strange error, the desktop changed all the time between a light blue-grez background and the steel-grey Porteus background image.
At times the taskbar and startmenu in the lower area vanished, at times it was there like normal, and at rare moments I saw a window named lxde-greeter-gtk in the area where LXDE shows the running windows.
Maybe that program made the strange bug?
I got this error over and over again while that X session was running:
Code: Select all
lxpanel : X error: BadWindow (invalid Window parameter)
But at least now LXDE was started also as guest, and was not flickering or whatever you might call that error I described above, and was okay for use...
Here now again the two main issues with 1.1 and LXDE / startx for me:
1 ) That the looged in root user started X already, when I don't want root to start x, unless I tell root so manually, and on purpose.
2 ) The strange things with the "flickering desktop" the first time I started X as guest...
Now I try to start the 1.1 from other PCs with NVidia GPU and give you my heads up on how other machines react to the same Linux / Porteus system...
But one good thing already can be told: The PC I first started the 1.1 x86-64 with (see the above bugs) is the same as the 120 sec. after /sbin/udevadm trigger bug, and the 1.1 not creates that bug.