pam_rundir Pragtical.

[meo]

Hello Juanito!

I've been trying to find som info that could lead me to make Pragtical work in piCore 16 and 17 because I can't make it work in piCore 17 beta2 either. Could the module pam_rundir solve this problem of mine or would it cause problems?

Kind Regards,
meo

[Juanito]

I just downloaded and loaded pragtical on a fresh install of piCore64 17beta2 on an RPi5 using Xorg-3d, flwm, aterm, and wbar and it starts from the icon in wbar without doing anything else.

linux-pam is not loaded.

I'm at a loss to understand why it doesn't work for you 

[meo]

Hi Juanito!

I have tried various things to make it work but in vane. I haven't the slightest clue what's causing it not to execute. It downloads using onboot in piCore64 17 beta2 but not if I choose ondemand. So I change that afterwards. Thanks for your sincere effort!

Greetings,
meeo

[Juanito]

Are you using Xorg-3d?

What kind of RPi are you using, RPi5?

[patrikg]

Hi @meo

Sorry for hijacking the thread.

Like always with Linux apps you could try to start the app from command line to see if you get any errors to get any clue whats going wrong.

[mocore]

ftr background of previous debugging @
https://forum.tinycorelinux.net/index.php?topic=28159.msg182869#msg182869

[meo]

Hello Juanito!

Sorry! I had a bad day yesterday. I am using Xorg in piCore64 17 beta 2. Tried to install Xorg-3d but I ran in to complications so this is a fresh install I am using now. The problem with Pragtical is consistent though. Usually everything runs smooth on my RPi 5. I have a little special setup though. I have a 512 GB SSD for RPi OS and sometimes I have another OS that I am trying out connected to a USB 3 port and then the original place for a micro SD card. I can start anyone tapping the space button when rebooting (or booting) then pressing 1 starts the OS connected to the internal micro SD slot. Pressing 4 starts first with the USB etc. and finally pressing 6 starts the OS on the SSD. Very useful trying out something new. But Pragtical is a hard nut to crack.

Kind regards,
meo

PS The piCore64 17 beta works pretty good now. Gimp works like a charm. DS

[Juanito]

You might want to try pragtical with Xorg-3d.

On an RPi5 running piCore64 17beta2 with an Xorg gui already loaded:

Code: [Select]

sudo cp /tmp/tcloop/xorg-server/usr/local/share/xorg-server/files/99-vc4.conf /usr/local/share/X11/xorg.conf.d
[exit to the console prompt]
tce-load -i Xorg-3d
startx
If the gui starts, verify 3d acceleration with:

Code: [Select]

tce-load -i glxinfo
glxinfo | grep Acc
    Accelerated: yes

[meo]

Hello again!

I have a cable connected to this Raspberry Pi. Does that make a difference?

Kind Regards,
meo

PS  And if the gui does not start? DS

[Juanito]

I don’t think a cable would cause a problem.

As long as you don’t have Xorg-3d onboot, you can reboot if the gui doesn’t start.

[meo]

Hi again Jusnito!

When something happened (a pile of files and OK) but the GUI didn't start. The error message from the test was: "Error: could't find RGB GLX visual or fbconfig".

Regards,
meo

[Juanito]

I just tested again.

The only extension I have onboot on this RPi5 running piCore64 17beta2 is openssl.

Boot, then:

Code: [Select]

tce-load -i Xorg-3d flwm aterm wbar
sudo cp /tmp/tcloop/xorg-server/usr/local/share/xorg-server/files/99-vc4.conf /usr/local/share/X11/xorg.conf.d
startx
..and the gui starts with 3d acceleration.

Note that very occasionally the gui doesn't start first time, but starts without problems when "startx" is issued a second time.

Edit: I'm using a monitor connected to the first hdmi port.

[meo]

Hello Juaniito!

I have tried several times today to get the Xorg-3d to load but almost always I get the answer Xorg-3d can't be found. If I then try to install the usual Xorg it's there and loads pretty fast. I don't know why this happens but it is in my mind and being processed.

Greetings,
meo

[Rich]

Hi meo
Please run this command:

Code: [Select]

ls -l /etc/sysconfig/tcedir/optional/*.tcz > Ext.lstAttach  Ext.lst  and  /etc/sysconfig/tcedir/onboot.lst  to your next post.