Tiny Core Base > piCore Test Releases
piCore14.0 Beta
aus9:
Hi at section (3) I do not get a desktop but thewaitforX failing
I too could not see any errors in that dmesg but my skills with Rpi are still low.
Maybe someone else with a desktop, happy to use the power switch to turn off and on to reboot could confirm their desktop fails too in loading
graphics-KERNEL?
2) Is it worthwhile in making beta2 images etc to mod /etc/inittab to allow one more getty?
that way if a member loads something that causes a crash ....black screen output....they can get a second getty and run startx?
cheers
Paul_123:
Images have ssh enabled by default. Use ssh to see what is going on..
I have a feeling this is a race condition in the audio not loading before the vc4 driver inits. During alpha, we needed to add the cma shared memory driver to the initrd to get this to work reliably, but beta 1 had newer firmware that seemed to work fine without.
If this is the case, when you run dmesg from ssh, it will show there is not a framebuffer created.
aus9:
Hi Paul_123
I removed graphics-KERNEL from my boot list and rebooted and used TC64 to load graphics-KERNEL
in TC64 its shows both alsa and graphics KERNEL TCEs loading but monitor on RPi goes black as prev reported.
2) I am not good as scp and have no plans to learn at this stage so I rebooted.....and for reasons I can not explain.....my persistent home dir was gone. PUFF so much for me thinking I knew what I doing ;D
I have just spotted that partition 1 needs a fsck. I get on to that later and my bootcode I got from Rich in another post....I will have to change that because
--- Quote ---[ 0.000000] Unknown kernel command line parameters "nortc noembed nozswap opt=mmcblk0p2 home=mmcblk0p2", will be passed to user space
[ 3.115230] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck..
--- End quote ---
3) anyhow here is link to dmesg created by ssh command on TC64
https://ln5.sync.com/dl/3b16fd620/r5hrb6fs-cfqi4cfz-ntdicqc3-c7rqk6ch
Altho others do not know.....I chose sync for its 5G free storage but it allows only 3 links to be active any point in time. So link will be deleted when I need a spare link......but you have the piCore64-14.x link which I am keeping.
If you do not mind, as I will be rebuilding my home dir here is dir link (as I lost that link and had to use sync to regain it)
https://ln5.sync.com/dl/1e5a26870/mijx95vj-pfbcqp6p-yevtqeqf-jd95g68b
3)
--- Code: ---cat dmesg-ssh.txt | grep framebuffer
[ 1.377773] simple-framebuffer 3e4e0000.framebuffer: framebuffer at 0x3e4e0000, 0x6e7000 bytes
[ 1.377795] simple-framebuffer 3e4e0000.framebuffer: format=a8r8g8b8, mode=1824x984x32, linelength=7296
[ 1.385816] simple-framebuffer 3e4e0000.framebuffer: fb0: simplefb registered!
--- End code ---
end of dmesg may be useful
--- Quote ---[ 13.792413] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 127.794271] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 127.811045] bcm2835_audio bcm2835_audio: card created with 8 channels
(gap by me)
[ 128.709351] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 128.710512] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 128.710533] [vc_sm_connected_init]: start
[ 128.750170] [vc_sm_connected_init]: installed successfully
[ 128.904083] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[ 128.913311] Console: switching to colour dummy device 80x25
[ 128.942189] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
[ 128.943842] Registered IR keymap rc-cec
[ 128.943970] rc rc0: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0
[ 128.944087] input: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0/input7
--- End quote ---
aus9:
I am now thinking the lost of home was because I could not recover within RPi from the blank screen so I used a power off power on to reboot.
I am now thinking I will save /etc/inittab once I resolve a better home bootcode
mortegai:
--- Quote from: Paul_123 on May 29, 2023, 10:03:20 PM ---...
I have a feeling this is a race condition in the audio not loading before the vc4 driver inits. During alpha, we needed to add the cma shared memory driver to the initrd to get this to work reliably, but beta 1 had newer firmware that seemed to work fine without.
--- End quote ---
Perhaps the cause may be the softdep between the vc4 and snd-soc-hdmi-codec modules, as indicated in http://forum.tinycorelinux.net/index.php/topic,26080.msg167351.html
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version