SA64

drmozes · 01-05-2023, 04:10 PM

Hello!

We're now on Linux 6.1! Everything looks good here on the RockPro64, Pinebook Pro and Raspberry Pi4.

For Raspberry Pi users, you *must* append 'irqpoll' to the Kernel cmdline before you reboot.

As root, load '/boot/extlinux/extlinux.conf' your favourite editor. At the bottom of the file you'll find an uncommented line beginning with the key word: 'APPEND'

Add 'irqpoll' in there, so it looks something like this:

Code:

APPEND awaitrootdev earlyprintk rootfstype=ext4 root=LABEL=SLKroot irqpoll

For new installations on the Rpi, this is now a default setting.

If there are any Kernel module requests let me know here and they can go in the Linux 6.1.4 release, when I'll also release the A-i-O Installers.

Cheers
s.

kermitdafrog8 · 01-06-2023, 07:18 PM

Is this for RPI4 only or do we need this on the 3 as well?

drmozes · 01-07-2023, 11:00 AM

Quote:

Originally Posted by kermitdafrog8

Is this for RPI4 only or do we need this on the 3 as well?

I don't know, I only have an Rpi4. If you boot it and the SD card drops off the bus and dmesg is full of errors, you should add it and report back.
On the Rpi4 without it, the MMC sub system is unstable but it worked-ish - certainly enough to edit the config file and reboot; but if it all went wrong you can just mount the SD card in another system to edit the config file.

Please report back what works.
Thanks

glorsplitz · 01-07-2023, 07:56 PM

Should we post any issues with 6.1 here or new thread?

I'm asking since upgrading pinebook pro, wireless isn't starting up the way I've been doing it.

I've been doing small script for years when doing wireless on slackware as in

Code:

#/bin/sh
/usr/sbin/wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -B
/sbin/ifconfig wlan0 up 192.168.0.18
/sbin/route add default gw 192.168.0.1

In rc.M right after "# Initialize the networking hardware." I put couple lines to run that script.

That wasn't working, so I put it at the end of rc.local. That didn't work.

After system is up, manually running the script as root works.

Do I need to sleep somewhere as maybe pinebook pro is being slow about initializing things?

I'm not interested in whatever else network tools like networkmanager, have no experience with it.

jloco · 01-09-2023, 09:17 AM

Upgrade to 6.1.3 was fine on my pbp outside of the created initrd. It always creates a broken initrd, and I just replace it with the one from the kernels/ dir which then works. I don't use the labels, and I'm running on emmc, so I'll call my install non-standard and live with it.

One thing that was the same on 5.19.16 and still on 6.1.3 is there's no sound. I start in telinit 3 generally, and run telinit 4 if I'm going to use a GNOME session. The control center always shows the Mic picking up all the sound around me but no speakers output sound.

The only way I've been able to get speaker sound on Slackware is to first telinit 1 before I go to 3 or 4. Though, if I must be honest, I'm glad the sound isn't working upon boot, because the speaker pop and clicking noise is terrible, and I'd rather have no sound than that sound. Still, it should be noted, as it's likely a bug in a module not initializing properly.

drmozes · 01-10-2023, 08:46 AM

Quote:

Originally Posted by jloco

Upgrade to 6.1.3 was fine on my pbp outside of the created initrd.

In what way is it broken?

jloco · 01-10-2023, 03:26 PM

Quote:

Originally Posted by drmozes

In what way is it broken?

The pbp doesn't boot. That little red light which is the source of much distress just stays red eternally after the initial boot process finishes. Putting the stock initrd in the created ones place fixes booting, so I assume it's stripping out modules the machine needs to boot. I'll create a new one next chance I get and look through it to compare what is missing.

drmozes · 01-13-2023, 04:51 AM

Quote:

Originally Posted by jloco

The pbp doesn't boot. That little red light which is the source of much distress just stays red eternally after the initial boot process finishes. Putting the stock initrd in the created ones place fixes booting, so I assume it's stripping out modules the machine needs to boot. I'll create a new one next chance I get and look through it to compare what is missing.

OK thanks, as it should work - it's independent from the storage and labels.

Re the sound - I know. It worked originally but the way we set it up is to copy a saved working copy of the sound config into place from within the Installer.
There has to be a better way to do it but when I experimented further, IIRC that the alsactl tool was pretty buggy.
If you find a way to make it work reliably let us know.

glorsplitz · 01-14-2023, 04:59 PM

hello all

applied last updates "Tue Jan 10 08:08:08 UTC 2023" now kde/plasma won't start properly, "We are sorry, Plasma closed unexpectedly".

kde/plasma worked before last updates. xfce and the others work.

no Xorg.0.log (EE) messages, after closing kde/plasma fail window, I captured what's in fail.txt.

kde/plasma works on the rockpro64

EDIT: out of curiosity, I closed the kde/plasma fail window but didn't ctrl-alt-backspace, alt-space brings up krunner, I can run apps, like gimp, firefox, kwrite, konqueror, dolphin.

glorsplitz · 01-21-2023, 10:04 PM

after "Thu Jan 19 08:08:08 UTC 2023" updates kde is working again on pbp