Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: Paul_123 on May 11, 2024, 12:53:19 PM
-
Team Tiny Core is happy to announce the first beta release of piCore-15.0. Both 32 and 64bit images are ready for download/testing.
rpi-kernel 6.6.47
gcc 13.2.0
binutils 2.42
glibc 2.39
busybox 1.36.1
micropython 1.19
openssl 3.2.0.
32bit - http://www.tinycorelinux.net/15.x/armhf/test_releases/RPi/piCore-15.0.0-beta3.zip (http://www.tinycorelinux.net/15.x/armhf/test_releases/RPi/piCore-15.0.0-beta3.zip) (This should run on all rpi boards)
64bit - http://www.tinycorelinux.net/15.x/aarch64/test_releases/RPi/piCore64-15.0.0-beta3.zip (http://www.tinycorelinux.net/15.x/aarch64/test_releases/RPi/piCore64-15.0.0-beta3.zip) (rpi zero2W, pi3, pi4, pi5)
A couple of notes:
- armv6/7/7l repos have been replaced by an armhf repo, which contains 32 bit extensions
- When using 32bit images, the pi4 and pi5 will use a 64bit kernel. please make sure to look at uname if manually downloading kernel module extensions.
-
Hello, I am getting Illegal instruction error executing openvpn binary, on RPi Model 1B.
I have also checked the md5 and it does match.
tc@box:~$ uname -a
Linux box 6.6.28-piCore #4 Thu Apr 18 22:44:37 EDT 2024 armv6l GNU/Linux
ldd /usr/local/sbin/openvpn
libnsl.so.1 => /lib/libnsl.so.1 (0xb6ef5000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb6ee7000)
liblzo2.so.2 => /usr/local/lib/liblzo2.so.2 (0xb6eb0000)
liblz4.so.1 => /usr/local/lib/liblz4.so.1 (0xb6e80000)
libssl.so.3 => /usr/local/lib/libssl.so.3 (0xb6dca000)
libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0xb6af4000)
libdl.so.2 => /lib/libdl.so.2 (0xb6ee4000)
libcap-ng.so.0 => /usr/local/lib/libcap-ng.so.0 (0xb6ad0000)
libc.so.6 => /lib/libc.so.6 (0xb697b000)
/lib/ld-linux-armhf.so.3 (0xb6fb8000)
libz.so.1 => /usr/lib/libz.so.1 (0xb6968000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb6ee1000)
tc@box:/mnt/mmcblk0p2/tce/optional$ md5sum openvpn.tcz
a91237244f981c189f83cd24ccc0070b openvpn.tcz
tc@box:/mnt/mmcblk0p2/tce/optional$ cat openvpn.tcz.md5.txt
a91237244f981c189f83cd24ccc0070b openvpn.tcz
-
I compiled openvpn 2.6.10 myself using your build file and it worked fine. I guess there is a cross compiling problem in your build environment?
tc@box:~$ /usr/local/sbin/openvpn --version
OpenVPN 2.6.10 armv6l-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
library versions: OpenSSL 3.2.1 30 Jan 2024, LZO 2.10
Originally developed by James Yonan
Copyright (C) 2002-2024 OpenVPN Inc <sales@openvpn.net>
Compile time defines: enable_async_push='no' enable_comp_stub='no' enable_crypto_ofb_cfb='yes' enable_dco='no' enable_debug='yes' enable_dlopen='unknown' enable_dlopen_self='unknown' enable_dlopen_self_static='unknown' enable_fast_install='yes' enable_fragment='yes' enable_iproute2='no' enable_libtool_lock='yes' enable_lz4='yes' enable_lzo='yes' enable_management='yes' enable_pam_dlopen='no' enable_pedantic='no' enable_pkcs11='no' enable_plugin_auth_pam='no' enable_plugin_down_root='yes' enable_plugins='yes' enable_port_share='yes' enable_selinux='no' enable_shared='yes' enable_shared_with_static_runtimes='no' enable_small='no' enable_static='yes' enable_strict='no' enable_strict_options='no' enable_systemd='no' enable_werror='no' enable_win32_dll='yes' enable_wolfssl_options_h='yes' enable_x509_alt_username='no' with_aix_soname='aix' with_crypto_library='openssl' with_gnu_ld='yes' with_mem_check='no' with_openssl_engine='auto' with_sysroot='no'
ldd /usr/local/sbin/openvpn
libresolv.so.2 => /lib/libresolv.so.2 (0xb6eab000)
liblzo2.so.2 => /usr/local/lib/liblzo2.so.2 (0xb6e70000)
liblz4.so.1 => /usr/local/lib/liblz4.so.1 (0xb6e40000)
libssl.so.3 => /usr/local/lib/libssl.so.3 (0xb6d8a000)
libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0xb6ab4000)
libcap-ng.so.0 => /usr/local/lib/libcap-ng.so.0 (0xb6a90000)
libc.so.6 => /lib/libc.so.6 (0xb693b000)
/lib/ld-linux-armhf.so.3 (0xb6f69000)
libz.so.1 => /usr/lib/libz.so.1 (0xb6928000)
libdl.so.2 => /lib/libdl.so.2 (0xb6ea8000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb6ea5000)
-
Hi ovacikar
Just an observation about the version you compiled:
libnsl.so.1 no longer shows up as a dependency.
-
I do have this library:
sudo find / -name libnsl*
/lib/libnsl.so.1
-
Hi ovacikar
Yes, but it no longer shows up when you run:
ldd /usr/local/sbin/openvpn
-
Yes the first ldd is the broken one downloaded from repository
Second ldd is the working one I compiled myself on native host.
-
Thanks for the report. I can confirm the problem, let me dig into whats going on.
-
Should be fixed, Building on a 64bit kernel takes a little more precaution. It was strip that was messing up the binary.
libnsl had nothing to do with the problem. is depreciated in glibc, but we still enable it for nfs support.
-
Have you recompiled all the tcz extensions for aarch64?
They are all different from version 14.x
-
No, they were resquashed with a 16k page size. The kernel for the pi5 uses a 16k page, and could not open the extensions with the old 4k page. 14.x did not use this kernel for the pi5.
-
Should be fixed, Building on a 64bit kernel takes a little more precaution. It was strip that was messing up the binary.
libnsl had nothing to do with the problem. is depreciated in glibc, but we still enable it for nfs support.
Thanks , reinstalled openvpn works fine now.
-
Hello, on previous piCore versions the disk activity led would blink rapidly during boot, so I could tell my headless Rpi is booting fine.
on 15.0 the led does not blink rapidly, it stays on during the boot process then turns off when disk activity ends.
I ended up adding this line to my bootlocal.sh to give me the same visual clue that boot process has completed:
echo heartbeat | sudo tee /sys/class/leds/ACT/trigger
-
Maybe you can change that in the device tree.
-
Reassigning the disk activity LED to heartbeat ended up being a better solution. This could be implemented in final picore release.
-
You can change the device tree parameters in config.txt
sudo mount /mnt/mmcblk0p1
sudo nano /mnt/mmcblk0p1/config.txt
dtparam=act_led_trigger=heartbeat
-
Finally got round to updating to piCore64-15.x beta.
Ref: http://forum.tinycorelinux.net/index.php/topic,26511.msg170886.html#msg170886
I don't see the kernel config, did we enable automatic bigger console fonts - without anything in cmdline.txt I still get 3840x2160?
-
It’s enabled, but not sure how the kernel picks the font. You can load the configs kernel module to see the config.
-
All I see for fonts is this:
CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
..wouldn't we need CONFIG_FONT_TER16x32=y?
-
Booting with fbcon=font:TER16x32 gets me 3840x2160 and a minuscule font.
Booting with video=HDMI-A-1:1920x1080M@60 gets me 1920x1080 and a readable font.
..so I'd say TER16x32 is not available to the kernel.
-
Which device/kernel are you using. With Raspi, configs are all managed with defconfigs. Perhaps I forgot to cherry pick a commit from 6.1.y to 6.6.y
-
RPi4 6.6.28-piCore-v8
-
Patch was applied, a dependency is missing for extra fonts. I'll have to rebuild kernels. Some pretty significant pi5 changes anyway.
-
Still trying to get sound via HDMI :(
tc@box:~/neofetch$ ./neofetch --off
tc@box
------
OS: TinyCoreLinux 15.0 aarch64
Host: Raspberry Pi 400 Rev 1.0
Kernel: 6.6.28-piCore-v8
Uptime: 5 mins
Packages: 461 (tce-status)
Shell: sh
Terminal: /dev/pts/0
CPU: (4) @ 1.800GHz
Memory: 350MiB / 3790MiB
Audacity fails to start
audacity: error while loading shared libraries: libportaudio.so.19.8: cannot open shared object file: No such file or directory
tc@box:~$
tce-load -wi vlc crashes the system !!
[tc@box:~$ df -h /dev/sda1
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.4G 65M 3.3G 2% /
tc@box:~$ df -h /dev/sda2
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 28G 864M 27G 4% /mnt/sda2
tc@box:~$]
-
Are you using alsa or pulseaudio?
What steps are you taking to get HDMI sound working?
-
Alsa
Read the Forum and tried
"
tc@box:~$ speaker-test -Ddefault:1 -c2 -t wav -l1
speaker-test 1.2.9
Playback device is default:1
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
ALSA lib conf.c:5671:(snd_config_expand) Unknown parameters 1
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM default:1
Playback open error: -22,Invalid argument
tc@box:~$
Tried to edit
# default
pcm.!default {
type plug
slave.pcm "hw:0,0"
}
etc.
USB Sound card is in use now ( as temporary solution ).
-
"Read the forum" doesn't tell us anything.
A pi400 has several different audio configurations, it all depends on what you put in your config.txt file. We also need to know what extensions you have loaded. Also check dmesg to see if there are any audio related errors.
-
I just tried with Xorg-3d:
speaker-test -D sysdefault:CARD=vc4hdmi0 -c2 -t wav -l1
aplay -D sysdefault:CARD=vc4hdmi0 /usr/local/share/sounds/alsa/Front_Center.wav
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
..works fine.
Following the above, running pavucontrol, which starts the dbus daemon and pulseaudio, xmms-pulse played music to the hdmi output without problems.
-
Audacity fails to start
That is correct - I'll take a look.
tce-load -wi vlc crashes the system !!
vlc works without problems for me.
-
I have to remind to check the config.txt file to modify the device tree:
https://www.raspberrypi.com/documentation/computers/config_txt.html#hdmi-audio
-
"Read the forum" doesn't tell us anything.
A pi400 has several different audio configurations, it all depends on what you put in your config.txt file. We also need to know what extensions you have loaded. Also check dmesg to see if there are any audio related errors.
Xlibs.tcz
Xorg-3d.tcz
Xorg-fonts.tcz
Xorg.tcz
Xprogs.tcz
abiword.tcz
adwaita-icon-theme.tcz
alsa-modules-6.6.28-piCore-v8-16k.tcz
alsa-modules-6.6.28-piCore-v8.tcz
alsa-plugins.tcz
alsa-utils.tcz
alsa.tcz
alsaequal.tcz
appstream-glib.tcz
apulse.tcz
aspell-dev.tcz
aspell-en.tcz
aspell.tcz
at-spi2-atk-dev.tcz
at-spi2-atk.tcz
at-spi2-core-dev.tcz
at-spi2-core-gir.tcz
at-spi2-core.tcz
aterm.tcz
atk-dev.tcz
atk-gir.tcz
atk.tcz
atkmm-dev.tcz
atkmm.tcz
audacity.tcz
avahi-dev.tcz
avahi.tcz
babl.tcz
bash.tcz
bc.tcz
binutils.tcz
bison.tcz
bluetooth-6.6.28-piCore-v8.tcz
bluez-alsa.tcz
bluez.tcz
boost-dev.tcz
boost.tcz
bubblewrap.tcz
bzip2-dev.tcz
bzip2-lib.tcz
bzip2.tcz
c-ares.tcz
ca-certificates.tcz
cairo-dev.tcz
cairo.tcz
cairomm-dev.tcz
cairomm.tcz
caps.tcz
clang.tcz
clutter-dev.tcz
clutter.tcz
cmake.tcz
cogl-dev.tcz
cogl.tcz
compiletc.tcz
coreutils.tcz
cups-dev.tcz
cups-filters.tcz
cups.tcz
curl-dev.tcz
curl.tcz
dbus-dev.tcz
dbus-glib-dev.tcz
dbus-glib.tcz
dbus-python3.8.tcz
dbus.tcz
dconf.tcz
desktop-file-utils.tcz
diffutils.tcz
double-conversion-dev.tcz
double-conversion.tcz
e2fsprogs_base-dev.tcz
enchant-dev.tcz
enchant.tcz
exiv2.tcz
expat2-dev.tcz
expat2.tcz
ffmpeg-dev.tcz
ffmpeg.tcz
file.tcz
findutils.tcz
firefox.tcz
firmware-rpi-bt.tcz
flac-dev.tcz
flac.tcz
flex.tcz
fltk-1.3.tcz
fontconfig-dev.tcz
fontconfig.tcz
freerdp.tcz
freetype-dev.tcz
freetype.tcz
fribidi-dev.tcz
fribidi.tcz
gamin-dev.tcz
gamin.tcz
gawk.tcz
gc-dev.tcz
gc.tcz
gcc.tcz
gcc_base-dev.tcz
gcc_libs-dev.tcz
gcc_libs.tcz
gcr-dev.tcz
gcr.tcz
gdbm-dev.tcz
gdbm.tcz
gdk-pixbuf-dev.tcz
gdk-pixbuf-gir.tcz
gdk-pixbuf.tcz
gdl-dev.tcz
gdl.tcz
gegl.tcz
geoclue-dev.tcz
geoclue.tcz
gettext.tcz
gexiv2.tcz
gfortran-lib.tcz
gfortran.tcz
giflib.tcz
gimp.tcz
git.tcz
glib-networking.tcz
glib1-dev.tcz
glib1.tcz
glib2-dev.tcz
glib2-python.tcz
glib2.tcz
glibc_add_lib.tcz
glibc_apps.tcz
glibc_base-dev.tcz
glibc_gconv.tcz
glibmm-dev.tcz
glibmm.tcz
glu-dev.tcz
glu.tcz
gmp-dev.tcz
gmp.tcz
gnome-autoar-dev.tcz
gnome-autoar-gir.tcz
gnome-autoar.tcz
gnome-common.tcz
gnome-desktop-gir.tcz
gnome-desktop.tcz
gnome-keyring.tcz
gnome-online-accounts-dev.tcz
gnome-online-accounts.tcz
gnumeric-dev.tcz
gnumeric.tcz
gnupg.tcz
gnutls-dev.tcz
gnutls.tcz
gobject-introspection-dev.tcz
gobject-introspection.tcz
goffice-dev.tcz
goffice.tcz
gom.tcz
graphene-dev.tcz
graphene.tcz
graphics-6.6.28-piCore-v8.tcz
graphite2-dev.tcz
graphite2.tcz
grep.tcz
grilo-plugins.tcz
grilo.tcz
gsettings-desktop-schemas-gir.tcz
gsettings-desktop-schemas.tcz
gsl-dev.tcz
gsl.tcz
gspell-dev.tcz
gspell.tcz
gst-plugins-bad.tcz
gst-plugins-base-dev.tcz
gst-plugins-base.tcz
gst-plugins-good.tcz
gst-plugins-ugly.tcz
gstreamer-dev.tcz
gstreamer.tcz
gtk1-dev.tcz
gtk1.tcz
gtk2.tcz
gtk3-dev.tcz
gtk3-gir.tcz
gtk3.tcz
gtkmm-dev.tcz
gtkmm.tcz
harfbuzz-dev.tcz
harfbuzz-gir.tcz
harfbuzz-icu-dev.tcz
harfbuzz-icu.tcz
harfbuzz.tcz
hicolor-icon-theme.tcz
hunspell-dev.tcz
hunspell-en_US.tcz
hunspell.tcz
icu.tcz
icu70-bin.tcz
icu70-dev.tcz
icu70.tcz
icu73.tcz
imlib2-bin.tcz
imlib2.tcz
info.lst
info.lst.gz
inkscape-dev.tcz
inkscape.tcz
intltool.tcz
inxi.tcz
isl.tcz
iso-codes.tcz
jasper-dev.tcz
jasper.tcz
json-c-dev.tcz
json-c.tcz
json-glib-dev.tcz
json-glib.tcz
jsoncpp.tcz
jwm.tcz
lame-dev.tcz
lame.tcz
lcms2-bin.tcz
lcms2-dev.tcz
libEGL-dev.tcz
libEGL.tcz
libGLES-dev.tcz
libGLES.tcz
libICE-dev.tcz
libICE.tcz
libSM-dev.tcz
libSM.tcz
libX11-dev.tcz
libX11.tcz
libXau-dev.tcz
libXau.tcz
libXcomposite-dev.tcz
libXcomposite.tcz
libXcursor-dev.tcz
libXcursor.tcz
libXdamage-dev.tcz
libXdamage.tcz
libXdmcp-dev.tcz
libXdmcp.tcz
libXext-dev.tcz
libXext.tcz
libXfixes-dev.tcz
libXfixes.tcz
libXfont2-dev.tcz
libXfont2.tcz
libXft-dev.tcz
libXft.tcz
libXi-dev.tcz
libXi.tcz
libXinerama-dev.tcz
libXinerama.tcz
libXmu.tcz
libXpm.tcz
libXrandr-dev.tcz
libXrandr.tcz
libXrender-dev.tcz
libXrender.tcz
libXt.tcz
libXtst-dev.tcz
libXtst.tcz
libXv-dev.tcz
libXv.tcz
libXxf86vm-dev.tcz
libXxf86vm.tcz
libacl.tcz
libarchive-dev.tcz
libarchive.tcz
libasound-dev.tcz
libasound.tcz
libass-dev.tcz
libass.tcz
libassuan-dev.tcz
libassuan.tcz
libatomic_ops-dev.tcz
libatomic_ops.tcz
libattr.tcz
libavahi.tcz
libavcodec.tcz
libavdevice.tcz
libavfilter.tcz
libavformat.tcz
libavutil.tcz
libbluetooth-dev.tcz
libbluetooth.tcz
libcanberra.tcz
libcap-dev.tcz
libcap.tcz
libcups.tcz
libdaemon-dev.tcz
libdaemon.tcz
libdmapsharing.tcz
libdrm-dev.tcz
libdrm.tcz
libelf-dev.tcz
libelf.tcz
libepoxy-dev.tcz
libepoxy.tcz
libevdev-dev.tcz
libevdev.tcz
libevent-dev.tcz
libevent.tcz
libexif.tcz
libfdk-aac.tcz
libffi7.tcz
libffi_base-dev.tcz
libfm.tcz
libfontenc-dev.tcz
libfontenc.tcz
libgcrypt-dev.tcz
libgcrypt.tcz
libgdata-dev.tcz
libgdata.tcz
libgpg-error-dev.tcz
libgpg-error.tcz
libgphoto2.tcz
libgsf-dev.tcz
libgsf.tcz
libical.tcz
libid3tag.tcz
libidn2-dev.tcz
libidn2.tcz
libinput-dev.tcz
libinput.tcz
libjpeg-turbo-bin.tcz
libjpeg-turbo-dev.tcz
libjpeg-turbo.tcz
libksba-dev.tcz
libksba.tcz
liblcms2.tcz
libldac.tcz
libltdl.tcz
liblz4-dev.tcz
liblz4.tcz
liblzma-dev.tcz
liblzma.tcz
libmad.tcz
libmediaart.tcz
libmypaint-dev.tcz
libmypaint.tcz
libnghttp2.tcz
libnotify-dev.tcz
libnotify.tcz
liboauth-dev.tcz
liboauth.tcz
libogg-dev.tcz
libogg.tcz
libopenaptx.tcz
libpci.tcz
libpciaccess-dev.tcz
libpciaccess.tcz
libpeas-gir.tcz
libpeas.tcz
libpng-dev.tcz
libpng.tcz
libpostproc.tcz
libpsl-dev.tcz
libpsl.tcz
libpulseaudio.tcz
libraw.tcz
librhash.tcz
librsvg-dev.tcz
librsvg.tcz
libsamplerate.tcz
libseccomp.tcz
libsecret-dev.tcz
libsecret.tcz
libsigc++-dev.tcz
libsigc++.tcz
libsndfile-dev.tcz
libsndfile.tcz
libsoup-dev.tcz
libsoup.tcz
libssh2.tcz
libswresample.tcz
libswscale.tcz
libtasn1-dev.tcz
libtasn1.tcz
libtheora-dev.tcz
libtheora.tcz
libtiff.tcz
libtool-dev.tcz
libtool.tcz
libunistring-dev.tcz
libunistring.tcz
libusb-dev.tcz
libusb.tcz
libuv.tcz
libv4l2-dev.tcz
libv4l2.tcz
libvorbis-dev.tcz
libvorbis.tcz
libvpx-bin.tcz
libvpx-dev.tcz
libvpx.tcz
libvulkan-dev.tcz
libvulkan.tcz
libwebp-dev.tcz
libwebp.tcz
libxcb-dev.tcz
libxcb.tcz
libxcrypt_base-dev.tcz
libxcvt-dev.tcz
libxcvt.tcz
libxkbcommon-dev.tcz
libxkbcommon.tcz
libxkbfile-dev.tcz
libxkbfile.tcz
libxml2-dev.tcz
libxml2.tcz
libxshmfence-dev.tcz
libxshmfence.tcz
libxslt-dev.tcz
libxslt.tcz
libyaml.tcz
libzstd.tcz
linux-6.6.y_api_headers.tcz
llvm-lib.tcz
llvm15-bin.tcz
llvm15-dev.tcz
llvm15-lib.tcz
lua-lib.tcz
m4.tcz
make.tcz
mc.tcz
menu-cache.tcz
mesa-dev.tcz
mesa.tcz
mirrors.tcz
mpc.tcz
mpfr.tcz
mpg123-dev.tcz
mpg123.tcz
mtdev-dev.tcz
mtdev.tcz
mtpaint.tcz
mypaint-brushes.tcz
nano.tcz
ncurses-dev.tcz
ncurses-terminfo.tcz
ncurses.tcz
nettle-dev.tcz
nettle.tcz
nghttp2.tcz
node.js.tcz
node.tcz
npth.tcz
nspr.tcz
nss-mdns.tcz
nss.tcz
openbox.tcz
openjpeg-dev.tcz
openjpeg.tcz
openssh.tcz
openssl-1.1.1.tcz
openssl-dev.tcz
openssl.tcz
opus-dev.tcz
opus.tcz
opusfile-dev.tcz
opusfile.tcz
p11-kit-dev.tcz
p11-kit.tcz
pango-dev.tcz
pango-gir.tcz
pango.tcz
pangomm-dev.tcz
pangomm.tcz
patch.tcz
pavucontrol.tcz
pciutils.tcz
pcmanfm.tcz
pcre.tcz
pcre2-dev.tcz
pcre2.tcz
perl5.tcz
perl_xml_parser.tcz
pixman-dev.tcz
pixman.tcz
pkg-config.tcz
poppler-dev.tcz
poppler.tcz
portaudio-dev.tcz
portaudio.tcz
portmidi.tcz
potrace-dev.tcz
potrace.tcz
pulseaudio-dev.tcz
pulseaudio.tcz
py3.8cairo.tcz
py3.8gobject.tcz
python3.11-dev.tcz
python3.11.tcz
python3.12.tcz
python3.8.tcz
qpdf.tcz
readline-dev.tcz
readline.tcz
rest-dev.tcz
rest.tcz
rhythmbox.tcz
ruby.tcz
rust.tcz
sbc-dev.tcz
sbc.tcz
sdl2-dev.tcz
sdl2-mixer-dev.tcz
sdl2-mixer.tcz
sdl2.tcz
sed.tcz
shared-mime-info.tcz
speex-dev.tcz
speex.tcz
speexdsp-dev.tcz
speexdsp.tcz
sqlite3-bin.tcz
sqlite3-dev.tcz
sqlite3.tcz
tdb.tcz
telepathy-glib-dev.tcz
telepathy-glib.tcz
tiff-bin.tcz
tiff-dev.tcz
totem-pl-parser.tcz
udev-extra.tcz
udev-lib-dev.tcz
udev-lib.tcz
unbound-dev.tcz
unbound.tcz
upgrade/
usbutils.tcz
util-linux_base-dev.tcz
util-macros.tcz
v4l-dvb-6.6.28-piCore-v8.tcz
vlc.tcz
wayland-dev.tcz
wayland-protocols.tcz
wayland.tcz
wbar.tcz
webkitgtk4-dev.tcz
webkitgtk4.tcz
wv.tcz
wxwidgets.tcz
x264-dev.tcz
x264.tcz
x265-dev.tcz
x265.tcz
xcb-proto.tcz
xf86-input-libinput.tcz
xf86-video-fbdev.tcz
xkbcomp.tcz
xkeyboard-config.tcz
xmms-dev.tcz
xmms-flac.tcz
xmms-pulse.tcz
xmms.tcz
xorg-proto.tcz
xorg-server-dev.tcz
xorg-server.tcz
xtrans.tcz
xwayland.tcz
yt-dlp.tcz
zlib_base-dev.tcz
zstd-dev.tcz
zstd.tcz
The list is from a 32GB USB Stick.
-
What are the contents of /mnt/mmcblk0p1/config.txt?
To check which extensions are loaded use “tce-status -i”.
What are the results of "aplay -l"?
-
That is correct - I'll take a look.
The latest version of audacity builds, but will not run - it gives a bunch of alsa errors for which google has no hits.
The existing version of audacity will not build on piCore64-15.x giving errors typical of using a more recent version of gcc.
I renamed libportaudio so the existing version of audacity starts, but it will not play to the hdmi output even though other apps have no problem.
Audacity seems full of bugs, I’m minded to remove the extension unless anyone thinks differently.
-
What are the contents of /mnt/mmcblk0p1/config.txt?
To check which extensions are loaded use “tce-status -i”.
What are the results of "aplay -l"?
tc@box:~$ aplay -l
aplay: device_list:277: no soundcards found...
tc@box:~$ inxi -A
Audio:
Device-1: bcm2711-hdmi0 driver: N/A
Device-2: bcm2711-hdmi1 driver: N/A
API: ALSA v: k6.6.28-piCore-v8 status: kernel-api
tc@box:~$
The Debian, Fedora , openSUSE etc on the same rPi400, without any audio issues, have all VC4 audio drivers present in the inxi -A . Wonder if that is the cause of the audio not getting into the HDMI cable...
-
Still need to know answers to what we have asked, so only one question at a time.
What are the contents of /mnt/mmcblk0p1/config.txt?
-
Still need to know answers to what we have asked, so only one question at a time.
What are the contents of /mnt/mmcblk0p1/config.txt?
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
# RPi PI0-1-2 are not supported on this image.
[PI02]
initramfs rootfs-piCore64-15.0.gz,modules-6.6.28-piCore-v8.gz followkernel
kernel kernel6628v8.img
[PI3]
initramfs rootfs-piCore64-15.0.gz,modules-6.6.28-piCore-v8.gz followkernel
kernel kernel6628v8.img
[PI4]
initramfs rootfs-piCore64-15.0.gz,modules-6.6.28-piCore-v8.gz followkernel
kernel kernel6628v8.img
[PI5]
initramfs rootfs-piCore64-15.0.gz,modules-6.6.28-piCore-v8-16k.gz followkernel
kernel kernel6628v8-16k.img
[CM4]
otg_mode=1
[ALL]
cmdline cmdline.txt
# Run in 64-bit mode
arm_64bit=1
# Run as fast as firmware / board allows
arm_boost=1
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
# Does not work with the vc4 driver.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
#camera_auto_detect=1
#display_auto_detect=1
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Additional overlays and parameters are documented /mnt/mmcblk0p1/overlays/README
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
[PI5]
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1
[all]
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2
There is no /mnt/mmcblk0p1/config.txt as a USB stick is used instead of uSD card.
/mnt/sda1/ is empty ( the config.txt is from the USB under Debian as /sdb1/ )
-
Booting from USB is fine, the boot disk is not mounted by default, so you need to mount it if you want to look at it. That config.txt looks fine. So the next is what extensions are loading
Run
tce-status -i
-
Booting from USB is fine, the boot disk is not mounted by default, so you need to mount it if you want to look at it. That config.txt looks fine. So the next is what extensions are loading
Run
tce-status -i
tc@box:~$ tce-status -i
Xlibs
Xorg
Xorg-fonts
Xprogs
abiword
adwaita-icon-theme
alsa
alsa-modules-6.6.28-piCore-v8
alsa-modules-6.6.28-piCore-v8-16k
alsa-plugins
alsa-utils
alsaequal
appstream-glib
apulse
aspell
aspell-dev
aspell-en
at-spi2-atk
at-spi2-atk-dev
at-spi2-core
at-spi2-core-dev
at-spi2-core-gir
aterm
atk
atk-dev
atk-gir
atkmm
audacity
avahi
avahi-dev
babl
bash
bc
bluetooth-6.6.28-piCore-v8
bluez
bluez-alsa
bubblewrap
bzip2
bzip2-dev
bzip2-lib
ca-certificates
cairo
cairo-dev
cairomm
caps
coreutils
cups
cups-dev
cups-filters
curl
curl-dev
dbus
dbus-dev
dbus-glib
dbus-glib-dev
dbus-python3.8
dconf
desktop-file-utils
enchant
enchant-dev
exiv2
expat2
expat2-dev
file
firefox
firmware-rpi-bt
flac
flac-dev
fltk-1.3
fontconfig
fontconfig-dev
freerdp
freetype
freetype-dev
fribidi
fribidi-dev
gamin
gamin-dev
gcc_libs
gcc_libs-dev
gcr
gcr-dev
gdbm
gdbm-dev
gdk-pixbuf
gdk-pixbuf-dev
gdk-pixbuf-gir
gegl
geoclue
geoclue-dev
gettext
gexiv2
giflib
gimp
git
glib-networking
glib1
glib1-dev
glib2
glib2-dev
glib2-python
glibc_add_lib
glibc_base-dev
glibc_gconv
glibmm
glu
gmp
gmp-dev
gnome-autoar
gnome-autoar-gir
gnome-desktop
gnome-desktop-gir
gnome-online-accounts
gnome-online-accounts-dev
gnumeric
gnumeric-dev
gnupg
gnutls
gnutls-dev
gobject-introspection
gobject-introspection-dev
goffice
goffice-dev
gom
graphene
graphene-dev
graphite2
graphite2-dev
grilo
grilo-plugins
gsettings-desktop-schemas
gsettings-desktop-schemas-gir
gst-plugins-bad
gst-plugins-base
gst-plugins-base-dev
gst-plugins-good
gst-plugins-ugly
gstreamer
gstreamer-dev
gtk1
gtk1-dev
gtk2
gtk3
gtk3-dev
gtk3-gir
gtkmm
harfbuzz
harfbuzz-dev
harfbuzz-gir
harfbuzz-icu
harfbuzz-icu-dev
hicolor-icon-theme
hunspell
hunspell-dev
hunspell-en_US
icu70
icu70-bin
icu70-dev
icu73
imlib2
imlib2-bin
intltool
inxi
iso-codes
jasper
json-c
json-c-dev
json-glib
json-glib-dev
jwm
lame
lcms2-bin
lcms2-dev
libEGL
libEGL-dev
libGLES
libGLES-dev
libICE
libSM
libSM-dev
libX11
libX11-dev
libXau
libXau-dev
libXcomposite
libXcomposite-dev
libXcursor
libXcursor-dev
libXdamage
libXdamage-dev
libXdmcp
libXdmcp-dev
libXext
libXext-dev
libXfixes
libXfixes-dev
libXfont2
libXft
libXft-dev
libXi
libXi-dev
libXinerama
libXinerama-dev
libXmu
libXpm
libXrandr
libXrandr-dev
libXrender
libXrender-dev
libXt
libXtst
libXtst-dev
libXv
libXxf86vm
libXxf86vm-dev
libacl
libarchive
libasound
libasound-dev
libassuan
libassuan-dev
libattr
libavahi
libavcodec
libavutil
libbluetooth
libbluetooth-dev
libcanberra
libcap
libcap-dev
libcups
libdaemon
libdaemon-dev
libdmapsharing
libdrm
libdrm-dev
libelf
libelf-dev
libepoxy
libepoxy-dev
libevdev
libevent
libevent-dev
libexif
libfdk-aac
libffi7
libffi_base-dev
libfm
libfontenc
libgcrypt
libgcrypt-dev
libgdata
libgdata-dev
libgpg-error
libgpg-error-dev
libgphoto2
libgsf
libgsf-dev
libical
libid3tag
libidn2
libidn2-dev
libinput
libjpeg-turbo
libjpeg-turbo-bin
libjpeg-turbo-dev
libksba
libksba-dev
liblcms2
libldac
libltdl
liblz4
liblz4-dev
liblzma
liblzma-dev
libmad
libmediaart
libmypaint
libmypaint-dev
libnotify
libnotify-dev
liboauth
liboauth-dev
libogg
libogg-dev
libopenaptx
libpci
libpciaccess
libpciaccess-dev
libpeas
libpeas-gir
libpng
libpng-dev
libpsl
libpsl-dev
libpulseaudio
libraw
librsvg
librsvg-dev
libsamplerate
libseccomp
libsecret
libsecret-dev
libsigc++
libsndfile
libsndfile-dev
libsoup
libsoup-dev
libssh2
libswresample
libswscale
libtasn1
libtasn1-dev
libtheora
libtheora-dev
libtiff
libtool
libtool-dev
libunistring
libunistring-dev
libusb
libusb-dev
libvorbis
libvorbis-dev
libvpx
libvulkan
libvulkan-dev
libwebp
libwebp-dev
libxcb
libxcb-dev
libxcvt
libxkbcommon
libxkbcommon-dev
libxkbfile
libxml2
libxml2-dev
libxshmfence
libxshmfence-dev
libxslt
libxslt-dev
libyaml
libzstd
llvm-lib
llvm15-bin
llvm15-dev
llvm15-lib
lua-lib
m4
make
mc
menu-cache
mesa
mesa-dev
mtdev
mtpaint
mypaint-brushes
nano
ncurses
ncurses-dev
ncurses-terminfo
nettle
nettle-dev
npth
nspr
nss
nss-mdns
openbox
openjpeg
openjpeg-dev
openssh
openssl
openssl-1.1.1
openssl-dev
opus
opus-dev
p11-kit
p11-kit-dev
pango
pango-dev
pango-gir
pangomm
pavucontrol
pciutils
pcmanfm
pcre
pcre2
pcre2-dev
perl5
perl_xml_parser
pixman
pixman-dev
poppler
portaudio
portaudio-dev
portmidi
pulseaudio
pulseaudio-dev
py3.8cairo
py3.8gobject
python3.11
python3.11-dev
python3.12
python3.8
qpdf
readline
readline-dev
rest
rest-dev
rhythmbox
ruby
rust
sbc
sbc-dev
sdl2
shared-mime-info
speex
speex-dev
speexdsp
speexdsp-dev
sqlite3
sqlite3-bin
sqlite3-dev
tar
tdb
telepathy-glib
telepathy-glib-dev
tiff-bin
tiff-dev
totem-pl-parser
udev-lib
udev-lib-dev
unbound
unbound-dev
util-linux
util-macros
wayland
wayland-dev
wayland-protocols
wbar
webkitgtk4
webkitgtk4-dev
wv
wxwidgets
x264
x265
xcb-proto
xf86-input-libinput
xf86-video-fbdev
xkbcomp
xkeyboard-config
xmms
xmms-dev
xmms-flac
xmms-pulse
xorg-proto
xorg-server
xtrans
xwayland
yt-dlp
zlib_base-dev
zstd
zstd-dev
tc@box:~$
-
You have managed to load half of the repository, but you are missing graphics-KERNEL.tcz
-
PS C:\Users\geev0> ssh tc@192.168.1.210
tc@192.168.1.210's password:
( '>')
/) TC (\ Core is distributed with ABSOLUTELY NO WARRANTY.
(/-_--_-\) www.tinycorelinux.net
tc@box:~$ tce-load -wi graphics-KERNEL.tcz
graphics-6.6.28-piCore-v8 is already downloaded.
graphics-6.6.28-piCore-v8.tcz: OK
tc@box:~$
"tc@box:/mnt/sda2/tce/ondemand$ ls
clutter-dev gfortran gnome-common inkscape-dev node sdl2-mixer-dev vlc
ffmpeg-dev gnome-autoar-dev gnome-keyring jasper-dev node.js udev-extra xorg-server-dev
tc@box:/mnt/sda2/tce/ondemand$"
"tc@box:/mnt/sda2/tce/optional$ ls graphics-*
graphics-6.6.28-piCore-v8.tcz graphics-6.6.28-piCore-v8.tcz.dep graphics-6.6.28-piCore-v8.tcz.md5.txt
tc@box:/mnt/sda2/tce/optional$"
tc@box:/mnt/sda2/tce/optional$ inxi -A
Audio:
Device-1: bcm2711-hdmi0 driver: vc4_hdmi
Device-2: bcm2711-hdmi1 driver: vc4_hdmi
API: ALSA v: k6.6.28-piCore-v8 status: kernel-api
tc@box:/mnt/sda2/tce/optional$
-
Can ssh to the system but the connected display has gone blank !
tc@box:~$ inxi -A
Audio:
Device-1: bcm2711-hdmi0 driver: vc4_hdmi
Device-2: bcm2711-hdmi1 driver: vc4_hdmi
API: ALSA v: k6.6.28-piCore-v8 status: kernel-api
tc@box:~$
:(
-
I'm guessing you loaded graphics-KERNEL in a gui, you should exit the gui before loading it.
To make testing easier, I suggest you remove all extensions from onboot (except openssh) and ondemand, reboot and then from the console: tce-load -i Xorg-3d flwm aterm wbar alsa alsa-utils
aplay -l
startx
..and then do your testing.
-
It is all working now and audio through HDMI is functional.
tc@box:/mnt/sda2/tce$ ls
firstrun mydata.tgz onboot.lst ondemand/ optional/ xwbar.lst
tc@box:/mnt/sda2/tce$
The solution came after a .db file that was in above list was deleted.
It has been a good learning experience and thanks for the guidance.
-
Thanks for this nice release of piCore!
It runs very smooth on my piZero2W and performs better than the last raspbian OS.
I do use solely the command line and do miss the gnu screen utility a lot (I have an unstable connection and want to pick up where I left after a disconnect, furthermore I like to run multiple tools in a split windows setup).
I tried using the old one from 14.x but that doesn't work.
I also tried compiling the gnu screen latest but a lot of dependencies were still missing.
So my question is, how can I get a gnu screen for 15.x, is one in the pipeline?
Kind Regards,
Pengo
-
Hi Pengo
... It runs very smooth on my piZero2W ...
That's the 32 bit version, right?
Is this what you are looking for:
http://tinycorelinux.net/15.x/armhf/tcz/screen.tcz.info
-
Hi Rich,
I am using the 64 bit version (which is ok for the piZero2W)
The repository of the 64 bit version does not have a screen.tcz (and the 32 bit version will not work)
-
Screen 4.9.1 has autotools/configure problems finding ncurses. But 4.9.0 works just fine.
I compiled and uploaded the extension for aarch64. Mostly untested, since I don't use screen.
-
Thanks for helping out Paul!
It looks like screen is working.
I recognize the ncurses compilation issue. More software has problems finding the ncurses header files and libraries.
It seems the include directory name has changed to ncursesw (from the top of my head)
-
I just pushed up Beta2 images, only changes are updating the kernel to 6.6.34 and fixing the compiled in fonts.
In my opinion, the TER16x32 font is too big, but the SUN12x22 font looks horrible. But I suppose, its just a console font.
-
Works fine for me :)
The kernel automatically selects TER16x32 for the monitor's native resolution of 3840x2160, it looks good and is just the right size to read easily.
In x or wayland I set the screen to 1920x1080 to be able to read it easily with the default fonts.
-
I just updated to piCore15.0 Beta armhf by copying over files to an sd card containing piCore-13.x running on an RPi3.
piCore-15.x booted and after copying over xorg-server (for the vc4 snippet) and graphics-KERNEL, the gui started.
I then updated all the extensions (due to the change in squashfs block size they are all marked for update) and now the gui will not start.
* I added the missing cairo dep to the harfbuzz dep file
* I created the missing llvm15-lib dep file containing gcc_libs, libzstd, ncurses and libxml2
* cairo-sphinx is missing a dep on pcre (this will probably disappear if compiled without pcre present).
There are no errors in Xorg.0.log, it looks like a normal startup - xorg does not start from boot due to the race condition loading modules, but starts with startx to a blank screen.
Strangely the screen comes up at 2048x1152, when I would have expected it to come up at 4khd or hd, but perhaps that's a limitation of the RPi3. If I add a snippet to set the screen to 1920x1080, it still comes up blank.
dmesg gives this: dmesg | grep vc4
[ 7.330096] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[ 7.338553] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0
[ 7.339287] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input0
[ 17.755263] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[ 17.757370] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0
[ 17.757667] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input1
[ 17.766294] input: vc4-hdmi HDMI Jack as /devices/platform/soc/3f902000.hdmi/sound/card1/input2
[ 17.767677] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[ 17.768153] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
[ 17.768499] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[ 17.768826] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[ 17.769153] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[ 17.769413] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
[ 17.775203] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
[ 17.778549] vc4-drm soc:gpu: [drm] Cannot find any crtc or sizes
Any ideas?
-
Can you check to make sure I added the vc4.conf file?
-
Yes, it’s there
-
After some more investigation, including burning the beta2 image to a new sd card, I found Xorg and wayland (weston) will start a gui, but not Xorg-3d.
The above would seem to indicate the problem is with graphics-KERNEL, but weston uses that too. What's puzzling me is that when I used mostly piCore-14.x extensions, but piCore-15.x graphics-KERNEL and xorg-server, Xorg-3d worked.
The above is using an RPi3 - Xorg-3d works on piCore64 using an RPi4.
Edit: Xorg.0.log attached
-
Hi Juanito
... xorg does not start from boot due to the race condition loading modules, but starts with startx to a blank screen. ...
I dealt with that by adding this to the beginning of .xsession:
# Wait for the video card to be detected so that
# Xorg can find it.
while [ $Timeout -lt 40 ]
do
[ -e /dev/dri/card0 ] && break
Timeout=$(($Timeout + 1))
sleep 0.25
done
-
Sure, but I’m loading Xorg-3d after booting and verifying that /dev/dri/card0 is present - you can see it is found in the xorg log attached to the previous post.
-
I dont think the pi4 and pi5 have issues with the race conditions, but the pi3 might. But in your log, you started X well after boot, and the gpu was found straight away. I think the first thing I would probably try is updating Mesa.
-
Hi Juanito
Sure, but I’m loading Xorg-3d after booting and verifying that /dev/dri/card0 is present - ...
I was not aware of that.
... you can see it is found in the xorg log attached to the previous post.
Yes, I saw that. That's what reminded me of what I did to get rid of the
"Failed in wait for X" error when booting.
-
I updated mesa, but the problem persists - 2d works, but 3d has a blank screen.
Information is being transmitted because if I change the screen resolution with an xorg snippet, the monitor reports the correct resolution is connected.
Still no errors in the xorg log :(
-
I just see notes about vc4/v3d compatibility issues with old videocore IV devices, but no real suggestions or solutions.
-
I tried updating xorg-server as this provides the modesetting driver, but no luck.
If I load graphics-KERNEL, but delete the modesetting driver, x starts using the llvmpipe software acceleration.
One thing I notice is that when graphics-KERNEL is loaded at the console prompt, the screen blanks and doesn't come back without turning it off/on - this doesn't happen with piCore64-15.x (v3d) and didn't happen with piCore-14.x (vc4).
So far no amount of googling turns up anything.
-
Hello, I have pi3b+ under hands that used to test gtk4 3d app, it works. For TC15 with v4 overlay `inxi -b` output there looks like
System:
Host: box Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
Desktop: FLWM v: N/A Distro: piCore 15.0
Machine:
Type: ARM System: Raspberry Pi 3 Model B Plus Rev 1.3 details: BCM2835
rev: a020d3 serial: xxx
CPU:
Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 600 min/max: 600/1400
Graphics:
Device-1: bcm2835-vc4 driver: vc4_drm v: N/A
Device-2: bcm2835-hdmi driver: N/A
Display: server: X.org driver: X: loaded: fbdev failed: modesetting
gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
resolution: 800x480
API: OpenGL v: 4.5 vendor: mesa v: 23.1.4 renderer: llvmpipe (LLVM 15.0.7
128 bits)
Network:
Device-1: bcm2835-mmc driver: mmc_bcm2835
Device-2: driver: lan78xx type: USB
Drives:
Local Storage: total: 14.84 GiB used: 3.67 GiB (24.8%)
Info:
Memory: total: N/A available: 920.9 MiB used: 184.3 MiB (20.0%)
Processes: 112 Uptime: 18m Shell: ash (busybox) inxi: 3.3.35
screen (LCD) doesn't blank and GTK apps with GL 4.5 CoreProfile work not so fast but acceptable taking into account hardware.
If there's need some info for comparing, let it know.
-
and with modesetting
System:
Host: box Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
Desktop: FLWM v: N/A Distro: piCore 15.0
Machine:
Type: ARM System: Raspberry Pi 3 Model B Plus Rev 1.3 details: BCM2835
rev: a020d3 serial: xxx
CPU:
Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 700 min/max: 600/1400
Graphics:
Device-1: bcm2835-vc4 driver: vc4_drm v: N/A
Device-2: bcm2835-hdmi driver: N/A
Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
dri: vc4
gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
resolution: 800x480~60Hz
API: OpenGL v: 2.1 vendor: broadcom mesa v: 23.1.4 renderer: VC4 V3D 2.1
Network:
Device-1: bcm2835-mmc driver: mmc_bcm2835
Device-2: driver: lan78xx type: USB
Drives:
Local Storage: total: 14.84 GiB used: 4.32 GiB (29.1%)
Info:
Memory: total: N/A available: 920.9 MiB used: 148.6 MiB (16.1%)
Processes: 117 Uptime: 3m Shell: ash (busybox) inxi: 3.3.35
-
I can get 3d acceleration with wayland:
inxi -b
System:
Host: boxrpi3c Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
Desktop: Weston v: 8.0.0 Distro: piCore 15.0
Machine:
Type: ARM System: Raspberry Pi 3 Model B Rev 1.2 details: BCM2835
rev: a02082 serial: 00000000c521e83a
CPU:
Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 600 min/max: 600/1200
Graphics:
Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A
Device-2: bcm2835-vc4 driver: vc4_drm v: N/A
Display: wayland server: X.org compositor: Weston v: 8.0.0 driver: X:
loaded: fbdev failed: modesetting gpu: vc4_hdmi,vc4_drm
resolution: 1920x1080
API: OpenGL Message: No GL data available.
Network:
Device-1: bcm2835-mmc driver: mmc_bcm2835
Device-2: driver: smsc95xx type: USB
Drives:
Local Storage: total: 59.48 GiB used: 407.4 MiB (0.7%)
Info:
Memory: total: N/A available: 920.9 MiB used: 227.6 MiB (24.7%)
Processes: 113 Uptime: 1h 24m Shell: ash (busybox) inxi: 3.3.35
..but not X (inxi via ssh): inxi -b
System:
Host: boxrpi3c Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
Console: pty pts/0 Distro: piCore 15.0
Machine:
Type: ARM System: Raspberry Pi 3 Model B Rev 1.2 details: BCM2835
rev: a02082 serial: 00000000c521e83a
CPU:
Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 600 min/max: 600/1200
Graphics:
Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A
Device-2: bcm2835-vc4 driver: vc4_drm v: N/A
Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
dri: vc4 gpu: vc4_hdmi,vc4_drm tty: 80x40
API: OpenGL Message: GL data unavailable in console. Try -G --display
Network:
Device-1: bcm2835-mmc driver: mmc_bcm2835
Device-2: driver: smsc95xx type: USB
Drives:
Local Storage: total: 59.48 GiB used: 407.7 MiB (0.7%)
Info:
Memory: total: N/A available: 920.9 MiB used: 220.5 MiB (23.9%)
Processes: 110 Uptime: 1h 52m Init: BusyBox Shell: ash (busybox)
inxi: 3.3.35
-
Perhaps look at the script mention in the RaspiOS package
https://forums.raspberrypi.com/viewtopic.php?p=2176793&hilit=Vc4+blank+screen+Xorg#p2176793
-
Thanks for the suggestion.
There are a couple of scripts, which produce: Section "OutputClass"
Identifier "vc4"
MatchDriver "vc4"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
..but the xorg log says "Option "PrimaryGPU" is not used"
and one that says "Glamor should not run on platforms prior to Pi 4": Section "Device"
Identifier "kms"
Driver "modesetting"
Option "AccelMethod" "msdri3"
Option "UseGammaLUT" "off"
EndSection
..but as per the xorg log, glamor is not disabled by it.
If I delete libglamoregl.so, it doesn't help :(
-
I can get 3d acceleration with wayland: inxi -b
...
Display: wayland server: X.org compositor: Weston v: 8.0.0 driver: X:
loaded: fbdev failed: modesetting gpu: vc4_hdmi,vc4_drm
resolution: 1920x1080
API: OpenGL Message: No GL data available.
with wayland it's strange that inxi (it uses glxinfo) cannot detect GL version
..but not X (inxi via ssh): [code]inxi -b
Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
dri: vc4 gpu: vc4_hdmi,vc4_drm tty: 80x40
not sure, can it be connected with `disable_fw_kms_setup`? In my case with v4+LCD+Xorg there's
display_auto_detect=1
dtoverlay=vc4-fkms-v3d
disable_fw_kms_setup=1
in config.txt and I've not touched Xorg.conf at all
-
dtoverlay=vc4-fkms-v3d is depreciated, what happens if you use dtoverlay=vc4-kms-v3d?
-
> dtoverlay=vc4-fkms-v3d is depreciated, what happens if you use dtoverlay=vc4-kms-v3d?
>
I've not known that, it has been always working there, so I've not thought to change it.
wiil test a bit further with vc4-kms-v3d and let it know...
p.s. meantime just for test checked it out with hdmi monitor, with hdmi it also works
Graphics:
Device-1: bcm2835-vc4 driver: vc4_drm v: N/A
Device-2: bcm2835-hdmi driver: N/A
Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
dri: vc4
gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
resolution: 1920x1200~60Hz
API: OpenGL v: 2.1 vendor: broadcom mesa v: 23.1.4 renderer: VC4 V3D 2.1
part of Xorg.log related to graphics
[ 19.828] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 19.828] (II) Platform probe for /sys/devices/platform/soc/soc:gpu/drm/card0
[ 19.833] (**) OutputClass "vc4" setting /dev/dri/card0 as PrimaryGPU
[ 19.833] (II) LoadModule: "glx"
[ 19.834] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 19.856] (II) Module glx: vendor="X.Org Foundation"
[ 19.856] compiled for 1.21.1.8, module version = 1.0.0
[ 19.856] ABI class: X.Org Server Extension, version 10.0
[ 19.857] (II) Applying OutputClass "vc4" to /dev/dri/card0
[ 19.857] loading driver: modesetting
[ 19.857] (==) Matched modesetting as autoconfigured driver 0
[ 19.857] (==) Matched fbdev as autoconfigured driver 1
[ 19.857] (==) Assigned the driver to the xf86ConfigLayout
[ 19.857] (II) LoadModule: "modesetting"
[ 19.857] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 19.866] (II) Module modesetting: vendor="X.Org Foundation"
[ 19.866] compiled for 1.21.1.8, module version = 1.21.1
[ 19.866] Module class: X.Org Video Driver
[ 19.866] ABI class: X.Org Video Driver, version 25.2
[ 19.866] (II) LoadModule: "fbdev"
[ 19.867] (II) Loading /usr/local/lib/xorg/modules/drivers/fbdev_drv.so
[ 19.869] (II) Module fbdev: vendor="X.Org Foundation"
[ 19.869] compiled for 1.21.1.8, module version = 0.5.0
[ 19.869] Module class: X.Org Video Driver
[ 19.869] ABI class: X.Org Video Driver, version 25.2
[ 19.869] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 19.869] (II) FBDEV: driver for framebuffer: fbdev
[ 19.869] (--) using VT number 2
[ 19.916] (II) modeset(0): using drv /dev/dri/card0
[ 19.916] (WW) Falling back to old probe method for fbdev
[ 19.916] (II) Loading sub module "fbdevhw"
[ 19.916] (II) LoadModule: "fbdevhw"
[ 19.917] (II) Loading /usr/local/lib/xorg/modules/libfbdevhw.so
[ 19.919] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 19.919] compiled for 1.21.1.8, module version = 0.0.2
[ 19.919] ABI class: X.Org Video Driver, version 25.2
[ 19.919] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 19.920] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 19.921] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[ 19.921] (II) Applying OutputClass "vc4" options to /dev/dri/card0
[ 19.921] (==) modeset(0): RGB weight 888
[ 19.921] (==) modeset(0): Default visual is TrueColor
[ 19.921] (II) Loading sub module "glamoregl"
[ 19.921] (II) LoadModule: "glamoregl"
[ 19.921] (II) Loading /usr/local/lib/xorg/modules/libglamoregl.so
[ 19.986] (II) Module glamoregl: vendor="X.Org Foundation"
[ 19.986] compiled for 1.21.1.8, module version = 1.0.1
[ 19.986] ABI class: X.Org ANSI C Emulation, version 0.4
[ 22.288] (II) modeset(0): glamor X acceleration enabled on VC4 V3D 2.1
[ 22.288] (II) modeset(0): glamor initialized
[ 22.288] (==) modeset(0): VariableRefresh: disabled
[ 22.288] (==) modeset(0): AsyncFlipSecondaries: disabled
[ 22.290] (II) modeset(0): Output HDMI-1 has no monitor section
[ 22.293] (II) modeset(0): EDID for output HDMI-1
....
[ 22.295] (II) modeset(0): Output HDMI-1 connected
[ 22.295] (II) modeset(0): Using exact sizes for initial modes
[ 22.295] (II) modeset(0): Output HDMI-1 using initial mode 1920x1200 +0+0
[ 22.295] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[ 22.295] (==) modeset(0): DPI set to (96, 96)
[ 22.295] (II) Loading sub module "fb"
[ 22.295] (II) LoadModule: "fb"
[ 22.295] (II) Module "fb" already built-in
[ 22.295] (II) UnloadModule: "fbdev"
[ 22.295] (II) Unloading fbdev
[ 22.296] (II) UnloadSubModule: "fbdevhw"
[ 22.296] (II) Unloading fbdevhw
[ 22.711] (==) modeset(0): Backing store enabled
[ 22.711] (==) modeset(0): Silken mouse enabled
[ 22.802] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[ 22.802] (==) modeset(0): DPMS enabled
[ 22.802] (WW) modeset(0): Option "PrimaryGPU" is not used
[ 22.803] (II) modeset(0): [DRI2] Setup complete
[ 22.803] (II) modeset(0): [DRI2] DRI driver: vc4
[ 22.803] (II) modeset(0): [DRI2] VDPAU driver: vc4
...
-
> dtoverlay=vc4-fkms-v3d is depreciated, what happens if you use dtoverlay=vc4-kms-v3d?
>
with vc4-kms-v3d it doesn't work in my case, looking at Xorg.log there's difference with fkms:
--- fkms
+++ kms
-(II) xfree86: Adding drm device (/dev/dri/card0)
-(II) Platform probe for /sys/devices/platform/soc/soc:gpu/drm/card0
-(**) OutputClass "vc4" setting /dev/dri/card0 as PrimaryGPU
+(II) no primary bus or device found
...
despite that I can see /dev/dri/card1 there, no idea why it comes in card1 slot with kms, maybe some kindof race condition (I've not digged into it)
-
I can get 3d acceleration with wayland: inxi -b
...
Display: wayland server: X.org compositor: Weston v: 8.0.0 driver: X:
loaded: fbdev failed: modesetting gpu: vc4_hdmi,vc4_drm
resolution: 1920x1080
API: OpenGL Message: No GL data available.
with wayland it's strange that inxi (it uses glxinfo) cannot detect GL version
It's the most interesting thing on rpi3, there's no xwayland there? If it's a pure wayland compositor, could you please share that binding API(OpenGL ES version and not llvm renderer) less than 3.0 or later?
-
Correct - that's weston running without xwayland - it seems faster than x/flwm too :)
glxinfo doesn't work on wayland/weston.
Here's all I can find from "XDG_RUNTIME_DIR=/run/user/1001 weston-launch -- --log=/home/tc/weston_log": weston 8.0.0
...
[09:02:07.602] Loading module '/usr/local/lib/libweston-8/drm-backend.so'
[09:02:07.606] initializing drm backend
[09:02:07.608] using /dev/dri/card0
[09:02:07.608] DRM: supports universal planes
[09:02:07.608] DRM: supports atomic modesetting
[09:02:07.608] DRM: supports picture aspect ratio
...
EGL version: 1.4
[09:02:07.722] EGL vendor: Mesa Project
[09:02:07.722] EGL client APIs: OpenGL OpenGL_ES
...
[09:02:07.726] GL version: OpenGL ES 2.0 Mesa 24.1.4
[09:02:07.726] GLSL version: OpenGL ES GLSL ES 1.0.16
[09:02:07.726] GL vendor: Broadcom
[09:02:07.726] GL renderer: VC4 V3D 2.1
...
[09:02:07.878] DRM: head 'HDMI-A-1' found, connector 32 is connected, EDID make 'DEL', model 'DELL U2720Q', serial 'JT61X13'
...
-
Correct - that's weston running without xwayland - it seems faster than x/flwm too :)
[09:02:07.722] EGL client APIs: OpenGL OpenGL_ES
[09:02:07.726] GL version: OpenGL ES 2.0 Mesa 24.1.4
[09:02:07.726] GL vendor: Broadcom
Wow, it works without glx and opengles<3.0 is attached to egl(wayland)
glxinfo doesn't work on wayland/weston.
I've looked into inxi-3.3.35 script, it calls all things that possible (glxinfo, eglinfo, clinfo,...) to collect and parse API info.
If there's mesa was built on the way, supposedly there's eglinfo there and can be used for inxi pretty print.
-
xorg-server patched and Xorg-3d adjusted so that RPi3 xorg-2d and xorg-3d work with vc4-kms-v3d
-
xorg-server patched and Xorg-3d adjusted so that RPi3 xorg-2d and xorg-3d work with vc4-kms-v3d
it looks like software rendering and visually slower comparing to v4-fkms
with v4-kms line in config
tc-kms% inxi -Ga
Graphics:
Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A bus-ID: N/A
chip-ID: brcm:3f902000 class-ID: hdmi
Device-2: bcm2835-vc4 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:soc
class-ID: gpu
Display: server: X.org driver: X: loaded: fbdev unloaded: modesetting
gpu: vc4_hdmi,vc4_drm display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
API: OpenGL v: 4.5 vendor: mesa v: 24.1.4 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: llvmpipe (LLVM 15.0.7 128 bits)
device-ID: ffffffff:ffffffff memory: 898.4 MiB unified: yes
with v4-fkms
tc-fkms% inxi -Ga
Graphics:
Device-1: bcm2835-vc4 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:soc
class-ID: gpu
Device-2: bcm2835-hdmi driver: N/A bus-ID: N/A chip-ID: brcm:soc
class-ID: hdmi
Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
dri: vc4
gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
Monitor-1: DSI-1 size-res: N/A modes: FIXED_MODE
API: OpenGL v: 2.1 vendor: broadcom mesa v: 24.1.4 glx-v: 1.4 es-v: 2.0
direct-render: yes renderer: VC4 V3D 2.1 device-ID: 14e4:ffffffff
memory: 898.4 MiB unified: yes
p.s. and gtk4 related:
it has started complain on vulkan after tcz updates
error while loading shared libraries: libvulkan.so.1: cannot open shared object file: No such file or directory
with loaded libvulkan (and v4-kms): it cannot use dri2 via egl->vulkan
% gtk4-widget-factory
libcups.so.2: cannot open shared object file: No such file or directory
Failed to load module: /usr/local/lib/gtk-4.0/4.0.0/printbackends/libprintbackend-cups.so
libgstplayer-1.0.so.0: cannot open shared object file: No such file or directory
Failed to load module: /usr/local/lib/gtk-4.0/4.0.0/media/libmedia-gstreamer.so
libEGL warning: DRI2: failed to authenticate
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
libEGL warning: egl: failed to create dri2 screen
-
% uname -a
Linux box 6.6.34-piCore-v7 #18 SMP Wed Jun 19 12:59:04 EDT 2024 armv7l GNU/Linux
running glxgears with v4-kms in config:
% top -n10 | head -10
Mem: 457868K used, 485156K free, 20660K shrd, 2344K buff, 263728K cached
CPU: 46.3% usr 2.4% sys 0.0% nic 51.2% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.64 2.87 2.55 6/136 9277
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
3430 2715 tc R 177m 19.1 1 44.0 glxgears
2727 2715 tc S 162m 17.5 0 2.3 lxterminal
2676 1 root S 100m 10.8 0 2.3 /usr/local/lib/xorg/Xorg -nolisten
2734 1 tc S 44732 4.7 2 0.0 {at-spi-bus-laun} /usr/local/lib/a
2757 1 tc S 36428 3.8 1 0.0 {at-spi2-registr} /usr/local/lib/a
2682 1 tc S 13272 1.4 0 0.0 flwm_topside
running glxgears with v4-fkms:
% top -n10 | head -10
Mem: 449144K used, 493888K free, 19084K shrd, 2344K buff, 237456K cached
CPU: 2.3% usr 2.3% sys 0.0% nic 95.2% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.48 0.27 0.11 2/134 8438
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
2665 1 root S 112m 12.1 1 3.1 /usr/local/lib/xorg/Xorg -nolisten
8432 4650 tc S 75084 7.9 3 1.5 glxgears
8396 4650 tc S 163m 17.6 2 0.0 lxterminal
8403 1 tc S 44768 4.7 2 0.0 {at-spi-bus-laun} /usr/local/lib/a
8426 1 tc S 36428 3.8 1 0.0 {at-spi2-registr} /usr/local/lib/a
2674 1 tc S 13340 1.4 2 0.0 flwm_topside
-
it looks like software rendering and visually slower comparing to v4-fkms
with v4-kms line in config
It looks like you’re missing something - the modesetting driver is not loaded, did you update both xorg-server and Xorg-3d?
-
it looks like software rendering and visually slower comparing to v4-fkms
with v4-kms line in config
It looks like you’re missing something - the modesetting driver is not loaded, did you update both xorg-server and Xorg-3d?
yep, firstly updated via "Apps", then after getting it not worked: Xorg removed and downloaded with 'tce-load -wl' to be sure
% ls -l /mnt/mmcblk0p2/tce/optional/Xorg*
-rw-rw-r-- 1 tc staff 4096 Aug 24 11:35 /mnt/mmcblk0p2/tce/optional/Xorg-3d.tcz
-rw-rw-r-- 1 tc staff 52 Aug 24 11:35 /mnt/mmcblk0p2/tce/optional/Xorg-3d.tcz.dep
-rw-rw-r-- 1 tc staff 46 Aug 24 11:35 /mnt/mmcblk0p2/tce/optional/Xorg-3d.tcz.md5.txt
-rw-rw-r-- 1 tc staff 1564672 Jun 28 20:40 /mnt/mmcblk0p2/tce/optional/Xorg-fonts.tcz
-rw-rw-r-- 1 tc staff 49 Jun 28 20:40 /mnt/mmcblk0p2/tce/optional/Xorg-fonts.tcz.md5.txt
-rw-rw-r-- 1 tc staff 4096 Aug 24 11:35 /mnt/mmcblk0p2/tce/optional/Xorg.tcz
-rw-rw-r-- 1 tc staff 120 Aug 24 11:35 /mnt/mmcblk0p2/tce/optional/Xorg.tcz.dep
-rw-rw-r-- 1 tc staff 43 Aug 24 11:35 /mnt/mmcblk0p2/tce/optional/Xorg.tcz.md5.txt
% ls -l /mnt/mmcblk0p2/tce/optional/xorg*
-rw-rw-r-- 1 tc staff 307200 Jul 3 23:34 /mnt/mmcblk0p2/tce/optional/xorg-proto.tcz
-rw-rw-r-- 1 tc staff 16 Jul 3 23:33 /mnt/mmcblk0p2/tce/optional/xorg-proto.tcz.dep
-rw-rw-r-- 1 tc staff 49 Jul 3 23:34 /mnt/mmcblk0p2/tce/optional/xorg-proto.tcz.md5.txt
-rw--w---- 1 tc staff 2674688 Aug 24 08:49 /mnt/mmcblk0p2/tce/optional/xorg-server.tcz
-rw-rw-r-- 1 tc staff 86 Aug 24 10:21 /mnt/mmcblk0p2/tce/optional/xorg-server.tcz.dep
-rw-rw-r-- 1 tc staff 50 Aug 24 10:21 /mnt/mmcblk0p2/tce/optional/xorg-server.tcz.md5.txt
-
Hi yvs
Try running an update like this:
tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update
exitcheck.sh reboot
-
Hi yvs
Try running an update like this:
tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update
exitcheck.sh reboot
% tce-audit builddb
Building Extension Database from /etc/sysconfig/tcedir/optional
....................................................................................
% tce-audit updatedeps
Updating .dep files from /etc/sysconfig/tcedir/optional
...
Building Extension Database from /etc/sysconfig/tcedir/optional
....................................................................................
% tce-audit fetchmissing
flac-dev is already downloaded.
libX11-dev is already downloaded.
libXau-dev is already downloaded.
libXdmcp-dev is already downloaded.
libXv-dev is already downloaded.
libXvmc is already downloaded.
Downloading: libacl-dev.tcz
Error on libacl-dev.tcz
libpsl-dev is already downloaded.
libsndfile is already downloaded.
libsoup is already downloaded.
libxcb-dev is already downloaded.
neon is already downloaded.
% tce-update
Checking for Easy Mode Operation... OK
Press Enter key to begin batch update of extensions in /mmcblk0p2/tce
or enter any char to exit now:
Checking Tiny Core Applications in /mnt/mmcblk0p2/tce/optional
Error Could not verify at-spi2-atk-dev.tcz
Error Could not verify at-spi2-atk.tcz
Error Could not verify atk-dev.tcz
Error Could not verify atk.tcz
Fetching required dependency: libX11-dev md5sum: can't open 'libX11-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libX11-dev': No such file or directory
Fetching required dependency: libxcb-dev md5sum: can't open 'libxcb-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libxcb-dev': No such file or directory
Fetching required dependency: libXau-dev md5sum: can't open 'libXau-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libXau-dev': No such file or directory
Fetching required dependency: libXdmcp-dev md5sum: can't open 'libXdmcp-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libXdmcp-dev': No such file or directory
Errors occurred during upgrade. Press Enter to see /tmp/upgrade_errors.lst
Your system is up-to-date.
Press Enter key.
% tce-load -wl libX11-dev libxcb-dev libXau-dev libXdmcp-dev
libX11-dev is already downloaded.
libxcb-dev is already downloaded.
libXau-dev is already downloaded.
libXdmcp-dev is already downloaded.
% tce-load -wl at-spi2-atk at-spi2-atk-dev atk atk-dev
at-spi2-atk is already downloaded.
at-spi2-atk-dev is already downloaded.
atk is already downloaded.
atk-dev is already downloaded.
% exitcheck.sh reboot
and
( '>')
/) TC (\ Core is distributed with ABSOLUTELY NO WARRANTY.
(/-_--_-\) www.tinycorelinux.net
failed in waitforX
tc@box:~$
in this time Xorg said neither fb0 nor dri/card0 are found
(EE) open /dev/fb0: No such file or directory
(EE) open /dev/dri/card0: No such file or directory
sometimes it's just "(EE) open /dev/dri/card0: No such file or directory" when xorg tries to work with it and that jumped to card1, but v4-kms usually works with framebuffer and there's x session via framebuffer.
p.s. with v4-fkms it works as that supposed to be on rpi3 in any configuration that I've had
-
Hi yvs
I'm not sure what's going on there.
In reply #75 you posted:
% uname -a
Linux box 6.6.34-piCore-v7 #18 SMP Wed Jun 19 12:59:04 EDT 2024 armv7l GNU/Linux
...
In reply #79 you show this:
... ----- Snip -----
% tce-update
Checking for Easy Mode Operation... OK
Press Enter key to begin batch update of extensions in /mmcblk0p2/tce
or enter any char to exit now:
Checking Tiny Core Applications in /mnt/mmcblk0p2/tce/optional
Error Could not verify at-spi2-atk-dev.tcz
Error Could not verify at-spi2-atk.tcz
Error Could not verify atk-dev.tcz
Error Could not verify atk.tcz
Fetching required dependency: libX11-dev md5sum: can't open 'libX11-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libX11-dev': No such file or directory
Fetching required dependency: libxcb-dev md5sum: can't open 'libxcb-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libxcb-dev': No such file or directory
Fetching required dependency: libXau-dev md5sum: can't open 'libXau-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libXau-dev': No such file or directory
Fetching required dependency: libXdmcp-dev md5sum: can't open 'libXdmcp-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libXdmcp-dev': No such file or directory
Errors occurred during upgrade. Press Enter to see /tmp/upgrade_errors.lst
----- Snip -----
...
The at-spi2-atk and atk extensions don't exist in the armhf (v7) repository.
They do exist in the aarch64 (v8) repository. Are you mixing extensions from
two different repositories?
I also don't understand where all those other extension (libX11-dev, libxcb-dev,
libXau-dev, and libXdmcp-dev) errors are coming from.
-
Here's what you should get with xorg 3d working using vc4-kms-v3d on an RPi3:
glxinfo
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Broadcom (0x14e4)
Device: VC4 V3D 2.1 (0xffffffff)
Version: 24.1.4
Accelerated: yes
Video memory: 920MB
...
inxi -Ga
Graphics:
Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A bus-ID: N/A
chip-ID: brcm:3f902000 class-ID: hdmi
Device-2: bcm2835-vc4 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:soc
class-ID: gpu
Display: server: X.org driver: X: loaded: modesetting
gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2048x1152 s-size: <missing: xdpyinfo>
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Dell U2720Q serial: JT61X13
built: 2020 res: 2048x1152 hz: 60 dpi: 87 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2048x1152 min: 720x400
API: OpenGL v: 2.1 vendor: broadcom mesa v: 24.1.4 glx-v: 1.4 es-v: 2.0
direct-render: yes renderer: VC4 V3D 2.1 device-ID: 14e4:ffffffff
memory: 898.4 MiB unified: yes
-
The at-spi2-atk and atk extensions don't exist in the armhf (v7) repository.
They do exist in the aarch64 (v8) repository. Are you mixing extensions from
two different repositories?
at-spi2-atk and atk were recently removed from the armhf repo as at-spi2-core now supplies at-spi2-atk and atk
-
Hi yvs
I'm not sure what's going on there.
In reply #75 you posted:
% uname -a
Linux box 6.6.34-piCore-v7 #18 SMP Wed Jun 19 12:59:04 EDT 2024 armv7l GNU/Linux
...
In reply #79 you show this:
... ----- Snip -----
% tce-update
Checking for Easy Mode Operation... OK
Press Enter key to begin batch update of extensions in /mmcblk0p2/tce
or enter any char to exit now:
Checking Tiny Core Applications in /mnt/mmcblk0p2/tce/optional
Error Could not verify at-spi2-atk-dev.tcz
Error Could not verify at-spi2-atk.tcz
Error Could not verify atk-dev.tcz
Error Could not verify atk.tcz
Fetching required dependency: libX11-dev md5sum: can't open 'libX11-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libX11-dev': No such file or directory
Fetching required dependency: libxcb-dev md5sum: can't open 'libxcb-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libxcb-dev': No such file or directory
Fetching required dependency: libXau-dev md5sum: can't open 'libXau-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libXau-dev': No such file or directory
Fetching required dependency: libXdmcp-dev md5sum: can't open 'libXdmcp-dev.tcz': No such file or directory
Failed
rm: can't remove '/tmp/libXdmcp-dev': No such file or directory
Errors occurred during upgrade. Press Enter to see /tmp/upgrade_errors.lst
----- Snip -----
...
The at-spi2-atk and atk extensions don't exist in the armhf (v7) repository.
They do exist in the aarch64 (v8) repository. Are you mixing extensions from
two different repositories?
I also don't understand where all those other extension (libX11-dev, libxcb-dev,
libXau-dev, and libXdmcp-dev) errors are coming from.
It's RPi3 with not so long ago (month two) installed TCL and a couple updates via Apps plus 'tce-load' if some packages were needed.
I'd suppose that 'tce-audit' script doesn't take into account periodical possible changes in TCL repository.
-
API: OpenGL v: 2.1 vendor: broadcom mesa v: 24.1.4 glx-v: 1.4 es-v: 2.0
So, API versions are the same as with v4-fkms. I think I will stay with v4-fkms until v4-kms is polished (fighting with v4-kms takes too much time).
-
Hi yvs
I'm not sure what's going on there.
In reply #75 you posted: ...
In reply #79 you show this: ...
The at-spi2-atk and atk extensions don't exist in the armhf (v7) repository.
They do exist in the aarch64 (v8) repository. Are you mixing extensions from
two different repositories?
I also don't understand where all those other extension (libX11-dev, libxcb-dev,
libXau-dev, and libXdmcp-dev) errors are coming from.
having time to look a bit more into details (besides atk related things clarified by @Juanito:
"at-spi2-atk and atk were recently removed from the armhf repo as at-spi2-core now supplies at-spi2-atk and atk")
Errors on libX11-dev, libxcb-dev, libXau-dev, and libXdmcp-dev:
it comes from libvulkan-1.3.283.tcz.dep, I'm not sure if that's from a local build or it came from repo some time ago too, like atk stuff
Error on libacl-dev:
- this artifact is still present in repo:
% wget -q -O - http://repo.tinycorelinux.net/15.x/armhf/tcz/gettext-dev.tcz.dep
gettext.tcz
libacl-dev.tcz
libxml2-dev.tcz
ncurses-dev.tcz
% wget http://repo.tinycorelinux.net/15.x/armhf/tcz/libacl-dev.tcz
--2024-08-28 22:58:16-- http://repo.tinycorelinux.net/15.x/armhf/tcz/libacl-dev.tcz
Resolving repo.tinycorelinux.net... 128.127.66.77
Connecting to repo.tinycorelinux.net|128.127.66.77|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-08-28 22:58:16 ERROR 404: Not Found.
I've not cleaned up optional/ to not download a lot of files again and suppose that removing all optional/ files and redownloading the needed can make tce-audit work with less complaints
-
Hi yvs
libacl-dev.tcz does not appear to be in the armhf or aarch64
repositories. Maybe paul-123 forgot to upload them ?
-
The package is acl-dev.tcz. I don't think there ever has been a libacl-dev. On arm, libacl is split out, but the dev package is still acl-dev.
I'm not sure how gettext-dev.tcz got libacl-dev referenced. Looks like the dep file for gettext-dev was just updated a couple of weeks ago....... I'll fix it.
-
I'm not sure how gettext-dev.tcz got libacl-dev referenced. Looks like the dep file for gettext-dev was just updated a couple of weeks ago.
Looks like my typo ☹️
-
Errors on libX11-dev, libxcb-dev, libXau-dev, and libXdmcp-dev:
it comes from libvulkan-1.3.283.tcz.dep
Which repo are you speaking of - libvulkan doesn’t have a dep file..
-
Errors on libX11-dev, libxcb-dev, libXau-dev, and libXdmcp-dev:
it comes from libvulkan-1.3.283.tcz.dep
Which repo are you speaking of - libvulkan doesn’t have a dep file..
most probably it was my experiments with vulkan builds at that time, so it needs to be skipped (and I already cleaned up my old locally built extensions)
-
OK - as an update to the piCore vulkan status, it works on an RPi4 running aarch64 although gtk4 windows are missing various decorations. I haven’t tested on an RPi4 running armhf yet.
-
OK - as an update to the piCore vulkan status, it works on an RPi4 running aarch64 although gtk4 windows are missing various decorations. I haven’t tested on an RPi4 running armhf yet.
I suppose it will work only in software mode (via llvm) as far gtk4 works with gl3+ only and underlying v4 driver is only gl2 compat
-
..but the 32bit RPi4 driver is v3d, no?
-
..but the 32bit RPi4 driver is v3d, no?
It's about rendering in general, and 2d and 3d.
I cannot say surely about RPi4 (not having one under hands to find out API provided by its VideoCore6 with common V4 driver).
Speaking of RPi3:
Here's what you should get with xorg 3d working using vc4-kms-v3d on an RPi3:
inxi -Ga
API: OpenGL v: 2.1 vendor: broadcom mesa v: 24.1.4 glx-v: 1.4 es-v: 2.0
direct-render: yes renderer: VC4 V3D 2.1 device-ID: 14e4:ffffffff
The same API versions I've seen with v4-fkms-v3d too.
And needless to say about much newer Vulkan and its support by V4.
-
I just pushed up beta3 images.
Changes:
Update to Kernel 6.6.47 (mainly to pickup a few critical pi5 changes.)
Update 32bit initrd to include udev rule changes.
-
As per:
sudo e2fsck /dev/sda8
Error: ext2fs library version out of date!
e2fsck 1.47.0 (5-Feb-2023)
Using EXT2FS Library version 1.46.5, 30-Dec-2021
Perhaps libext2fs.so.2 was updated from piCore-14.x, but not e2fsck?
-
Perhaps, I forgot to copy to initrd. I'll have to look. Thanks for reporting.
-
I just burned a fresh piCore15 beta3 image, e2fsck and libs all seem to checkout fine.
What may be special about your system?
-
Nothing that I can think of - I updated beta1 -> beta2 by mounting the image and copying the files over.
I'll update to beta3 soon..
-
somehow an old e2fsprogs extension laying around? Let me know, as I'll push out finals after this.
The only thing I'm planning to change, there was an issue with the udev rule 99-com.rules that was preventing the symlinks for serial0 and serial1 to be created for the serial ports. Our older version of udev did not handle the single quotes of a sed command in a PROGRAM= script. And then updating the startserialtty script.
-
I updated to beta3 using piCore 32/64 bit kernel on an RPi4 and aarch64 on another RPi4 - everything seems fine and the fsck error did not reappear.
Maybe it would be good to add the following to config.txt: [PI4]
initramfs rootfs-piCore-15.0.gz,modules-6.6.47-piCore-v8.gz followkernel
kernel kernel6647v8.img
arm_64bit=1
#initramfs rootfs-piCore-15.0.gz,modules-6.6.47-piCore-v7l.gz followkernel
#kernel kernel6647v7l.img
#arm_64bit=1
-
duplicate post
-
Picore 15 beta 3, the p1 partition somehow got increased to 128 MB. The content still takes 54.6 MB. How do I shrink it back and reasign to p2 with resize2fs ?
If shrinking and reallocating is not possible, can it be fixed in next release?
Linux box 6.6.47-piCore #9 Sat Aug 31 14:48:51 EDT 2024 armv6l GNU/Linux
Filesystem Size Used Available Use% Mounted on
/dev/mmcblk0p1 126.0M 54.6M 71.4M 43% /mnt/mmcblk0p1
Previous 15 Beta 1:
Filesystem Size Used Available Use% Mounted on
/dev/mmcblk0p1 78.8M 54.6M 24.1M 69% /mnt/mmcblk0p1
-
Shrinking and expanding a fat32 partition is not possible. From what I can see I changed the partition size before I released beta1, and the old size was only 64MB. Did you manually create a sdcard then copy the contents?
I don't want to release an image with only a 64MB partition, but what is the right number?
-
The 15 beta 1 comes with 80MB p1 partition. I have a second RPi with the output below.
What is wrong with the 80MB ? Increasing p1 unnecessarily leaves less space for the p2. Especially on a small card like 256 / 512 MB.
Linux picore 6.6.28-piCore #4 Thu Apr 18 22:44:37 EDT 2024 armv6l GNU/Linux
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 128,0,1 1023,3,16 8192 172031 163840 80.0M c Win95 FAT32 (LBA)
-
Hi Paul_123
... I don't want to release an image with only a 64MB partition, but what is the right number?
I guess that depends on how much stuff do you expect users
to be adding to the boot partition.
I have seen references to articles like this:
https://www.novaspirit.com/2018/01/09/tiny-core-raspberry-pi-zero-w-install/
where they recommend deleting an unneeded kernel architecture to make
room to download extensions needed for setting up wifi. They probably picked
that partition because its FAT32 so Windows can download the files if necessary.
In that article they download everything including .info, .tree, .list, and .zsync.
For TC9 ARMv6 that amounts to 5.8M.
So in my uninformed opinion, I would think 10M to 15M above the required
space for the boot files should be adequate.
-
The reason I went to 128MB is due to being able to run multiple kernel versions. As well as leaving space for firmware upgrades on the pi4's. For those of us who do in place upgrades. But I can put back to ~80MB
-
‘sounds interesting, how do you do the firmware update on a piCore RPi4?
-
You can also save some space by not start at sector 8192, I think you can start at 1.
Raspberry pi doesn't need and boot sector.
Something like this:
LANG=C parted --script -a none sdimage.img unit s mktable msdos mkpart primary fat32 1 80Mb mkpart primary ext4 80Mb 100%
-
Well for sure the easiest way to upgrade the firmware is to just download the firmware recovery image using rpi imager, put it on an empty sd card, boot it, then swap back. If you have never done it, you may need to update the USB controller too.
The repo with firmware is here: https://github.com/raspberrypi/rpi-eeprom
Its a little tricky due to dependencies, and where it expects to find the boot drive mounted. But environment variables can adjust that.
raspi-utils, pciutils and python3 are dependancies.
-
You can also save some space by not start at sector 8192, I think you can start at 1.
Raspberry pi doesn't need and boot sector.
This is done for compatibility of the card inserted into any number of operating systems. We have experimented in the past, and have had problems.
1) The official SDCard formatter tool puts the partition on sector 8192
2) RaspiOS puts the first partition on sector 8192