Search found 3349 matches

by MichaIng
Fri Oct 15, 2021 4:17 pm
Forum: Troubleshooting
Topic: Cannot start docker containers
Replies: 6
Views: 52

Re: Cannot start docker containers

That boot.img seems like a firmware, not a linux image, which should be called something with "linux" in its same. And most importantly it should be stored somewhere in the boot partition. In theory a bootloader can load it from everywhere, but there isn't some bootloader configuration or ...
by MichaIng
Fri Oct 15, 2021 4:10 pm
Forum: Troubleshooting
Topic: Cannot mount USB drive
Replies: 17
Views: 124

Re: Cannot mount USB drive

Good idea, probably a loop device does not suffer from such read-only flag. Whether it can then be mounted is another question, but probably it can be repaired (fsck) then.
by MichaIng
Fri Oct 15, 2021 4:06 pm
Forum: Troubleshooting
Topic: [rpi 4 8gb] Can't start Kodi
Replies: 28
Views: 489

Re: [rpi 4 8gb] Can't start Kodi

I'll have a look into the RPi build's scripts, I remember there was some workaround to switch to a different VT, probably it is exactly for that issue.
by MichaIng
Fri Oct 15, 2021 12:57 pm
Forum: Troubleshooting
Topic: [rpi 4 8gb] Can't start Kodi
Replies: 28
Views: 489

Re: [rpi 4 8gb] Can't start Kodi

Strange. But it must have something to do with the to ports, as on all other RPi models it works fine :?. Does it make a difference whether you use the --standalone flag or not? And another interesting test would be whether the Debian Kodi package works: apt purge kodi apt install kodi kodi --standa...
by MichaIng
Fri Oct 15, 2021 12:09 am
Forum: Troubleshooting
Topic: PI4 Multiple Displays
Replies: 3
Views: 66

Re: PI4 Multiple Displays

Okay great. The disable-wifi is correct if you don't use WiFi, but not related to this issue indeed. What I wanted to see is whether a KMS/DRM driver is enabled, and on your first output it was not, on your second output it is. You have two DRI devices card0 and card1, so they can be correctly used ...
by MichaIng
Thu Oct 14, 2021 8:04 pm
Forum: Troubleshooting
Topic: Cannot start docker containers
Replies: 6
Views: 52

Re: Cannot start docker containers

Strange thing, where is the kernel, actually? Can you show:

Code: Select all

ls -l /
And also to identify the model (as I cannot find a "NanoPC TV", only a NanoPC T4?):

Code: Select all

cat /proc/cpuinfo
cat /proc/device-tree/model
Where did you get the image from originally?
by MichaIng
Thu Oct 14, 2021 10:44 am
Forum: Requests
Topic: [Software Suggestion] Web-based file browser
Replies: 11
Views: 4226

Re: [Software Suggestion] Web-based file browser

Go to https://github.com/browsefile/backend/releases and download the latest "linux-armv6-bf.tar.gz" below "Assets". ARMv6 btw means RPi 1 and Zero models only, else it's ARMv7 at least ;).
by MichaIng
Wed Oct 13, 2021 3:32 pm
Forum: Troubleshooting
Topic: [rpi 4 8gb] Can't start Kodi
Replies: 28
Views: 489

Re: [rpi 4 8gb] Can't start Kodi

It works well on RPi Zero and RPi 2, so it is definitely an issue with the two HDMI ports on RPi 4, or another difference of the RPi 4 GPU. Btw, Kodi since Bullseye has native GBM support builtin on Debian as well, so it can be started without X server then as well. Would be interesting if this work...
by MichaIng
Wed Oct 13, 2021 2:52 pm
Forum: Troubleshooting
Topic: chromium kiosk autostart not working until i install a desktop
Replies: 8
Views: 99

Re: chromium kiosk autostart not working until i install a desktop

I think I found the missing dependency. Please try:

Code: Select all

apt install libgtk-3-0
To allow startup of Chromium without LXDE (which pulls this library as dependency).
by MichaIng
Wed Oct 13, 2021 1:42 pm
Forum: Troubleshooting
Topic: chromium kiosk autostart not working until i install a desktop
Replies: 8
Views: 99

Re: chromium kiosk autostart not working until i install a desktop

Interesting, on ARMv6 at least also installing a desktop does not solve it, but fails with "illegal instructions". You mean the autostart option started working just after you installed LXDE? EDIT: Ah dedicated known ARMv6 issue I already forgot again. Seems like it's not going to be fixed...