Tiny Core Base > Raspberry Pi
[Solved] Upgrading piCore 13 to run on Raspberry Pi 5
Rich:
Hi Rabie
Please use Code Tags when posting commands and responses seen in a terminal. To use Code Tags click on the # icon
above the reply box and paste your text between the Code Tags as shown in this example:
--- Quote ---[code][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
--- End quote ---
It will appear like this in your post:
--- Code: ---[ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
--- End code ---
Code Tags serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.
Rich:
Hi Rabie
I don't run any Pi hardware myself, so this is just an observation.
Your log shows it detecting /dev/dri/card0 , which is what I would expect:
--- Code: --- ----- Snip -----
[ 2.452] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2.452] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[ 2.452] (II) no primary bus or device found
[ 2.452] falling back to /sys/devices/platform/axi/1002000000.v3d/drm/card0
----- Snip -----
--- End code ---
Yet for some reason it tries to use a non-existant /dev/fb0:
--- Code: --- ----- Snip -----
[ 2.466] (EE) open /dev/fb0: No such file or directory
----- Snip -----
--- End code ---
I suspect either something in config.txt or cmdline.txt needs to be adjusted.
Juanito:
Do you have this in config.txt:
--- Code: ---[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
--- End code ---
Juanito:
You should see:
--- Code: ---[ 2.886] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2.886] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[ 2.886] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 2.886] (II) Platform probe for /sys/devices/platform/axi/axi:gpu/drm/card1
[ 2.891] (**) OutputClass "vc4" setting /dev/dri/card1 as PrimaryGPU
--- End code ---
Rabie:
yes i have it in my config.txt
--- Code: ---cat /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-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img
[PI3]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img
[PI4]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img
[PI5]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8-16k.gz followkernel
kernel kernel61225v8-16k.img
[CM4]
otg_mode=1
[cm5]
dtoverlay=dwc2,dr_mode=host
[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
# 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
--- End code ---
But i improvised and created the following file:
--- Code: ---sudo nano /etc/X11/xorg.conf
Section "Device"
Identifier "Framebuffer"
Driver "fbdev"
Option "fbdev" "/dev/fb0"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Framebuffer"
EndSection
--- End code ---
After that, X started immediately on reboot! :)
Is it actually a bad idea to use the framebuffer fb0?
Because technically, the two HDMI outputs are called card0 and card1.
the next question is whether this setup will also work with the 32-bit version.
The reason I ask is that there are a few extensions available in the 32-bit version that are missing in the 64-bit one.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version