Search results

Ok thanks. I have this bug on Slackware, that's why I've asked :^)

I managed to boot 5.10.180.

5.10.180 boots !!! Thanks, I double-checked and noticed something messy, I think the dtb was overwritten at some point in the build. Worst part is that I md5summed everything on the SD cards because it drove me nuts, and the md5sums were correct. I was probably too sleepy and missed something...

FATAL: kernel too old 5.4.243-letux-lpae

Indeed most of the hardware I tested is working but https://projects.goldelico.com/p/gta04-kernel/ shows nothing about state so I guessed many work still had to be done. Also 5.4 and 5.10 don't work so why 6.4 would be in a good shape ? Well I always use omap5-letux-cortex15-v5.3+pyra-v5.3.dtb...

FATAL: kernel too old So recompiled official 5.6.19 kernel doesn't boot on Slackware.

FATAL: kernel too old So official 5.6.19 kernel doesn't boot on Slackware. Aside this one, I tried many kernels, nothing works properly, see this post: https://pyra-handheld.com/boards/threads/slackware-inside-pyra.99855/page-2#post-1714109

If the applet is activated, but with bt deactivated, does the plugin crash when bt is activated ?

Do starting a disabled-by-default bt from the applet crashes the applet ?

Lol, official kernel is not a uImage, it's a zImage: $ file vmlinuz-5.6.19-daveiii-pyradef-aufs vmlinuz-5.6.19-daveiii-pyradef-aufs: Linux kernel ARM boot executable zImage (little-endian) And when I try to boot a zImage, uboot says "wrong format" and I have to convert to uImage. Such a mess...

Looks like it's possible to get it from another uImage: $ file uImage uImage: u-boot legacy uImage, Linux-5.4.242-letux-lpae+, Linux/ARM, OS Kernel Image (Not compressed), 5380376 bytes, Thu Apr 27 10:55:17 2023, Load Address: 0X80008000, Entry Point: 0X80008000 1685000934 Not to mention that...

I have to convert the zImage to uImage format, unfortunately I don't know the <load-address> and <entry-point> parameters, do somebody know them ? Do I have to change the "-n" parameter ? mkimage -A arm -O linux -T kernel -C none -a <load-address> -e <entry-point> -n "Linux kernel" -d...

Well I've just spent 6 hours trying to boot another kernels. All of them fail. Letux 5.4.243 -> kernel panic ti_dt_clocks_register: failed to lookup clock node l4per_cm Letux 5.10.18 -> kernel panic ti_dt_clocks_register: failed to lookup clock node l4per_cm then it's stuck Official aTc 5.6.19...

From: http://www.slackware.com/changelog/stable.php?cpu=arm So that should work. I can check that at some point as I've kept my old builds. 1684912754 I updated PyraOS to bullseye then sid, the system was still bootable.

AFAIK this will give a "Kernel too old" with Slackware ARM and probably a lot of recent Linux distributions incl. Debian bullseye. 6.1 should work (tested on a devboard but can't remember exactly).

Yup. And I found out that AUFS isn't included in the Linux kernel. This is annoying.

Is dbp still maintained ? By who ?

Done with /etc/X11/xorg.conf.d/10-video-etnaviv.conf : Section "Screen" Identifier "DSI-1" # Use the one reported by xrandr Device "etnaviv" EndSection Section "Device" Identifier "etnaviv" Driver "modesetting" Option "kmsdev" "/dev/dri/card1" Option "AccelMethod"...

Boot: For some reason, I had to use an extlinux/extlinux.conf instead of uEnv.txt . Here's extlinux/extlinux.conf: TIMEOUT 30 DEFAULT primary MENU TITLE SL4P SD Card boot options LABEL primary MENU LABEL primary kernel LINUX /uImage FDT...

I was able to fix the blueman-applet crash: hciconfig -a gave: Name: '' Service Classes: Unspecified Device Class: Invalid Device Class I modified the /etc/rc.d/rc.bluetooth file. bluetoothd must be called with the --noplugin=hostname option: /usr/sbin/bluetoothd --noplugin=hostname & But I...