Raspberry Pi Installation Help?

[gkusiak]

(1st Dec, 2021 02:36 AM)plugh Wrote:  Not trying to hijack thread, but forum won't let newbie start thread.

Software
XBian version: XBian_Buster_latest_rpi4.img.gz (dated 2021-08-17)
XBMC/Kodi version: ??
Overclock settings: none

Hardware
Device type and model (e.g. Raspberry Pi 3 Model B 1024 MB,
Power supply rating:2.5A
SD card size and make/type: sandisk 16gb "Ultra"
Network (Ethernet or wireless): wired
Connected devices (TV, USB, network storage, ...): 1080p TV, keyboard, mouse

I expanded the gz, wrote image to sd card, booted the Pi.
I get a splash screen, which eventually gets to 'starting kodi'
After a couple minutes, screen switches to a console login.

I can SSH in, looked around for some kind of log file (none?)
Latter part of DMESG output is:

Quote:[ 14.502071] smsc95xx 1-1.1:1.0 eth0: Link is Up - 100Mbps/Full - flow control off
[ 14.545465] init: failsafe main process (532) killed by TERM signal
[ 14.743540] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 14.791579] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 14.823119] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 14.823154] cfg80211: failed to load regulatory.db
[ 14.916795] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 14.934324] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 14.937064] usbcore: registered new interface driver brcmfmac
[ 15.013599] init: xbian-failaccess main process (437) killed by TERM signal
[ 15.147906] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[ 15.165812] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[ 15.171384] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 15.171431] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 15.176870] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[ 15.184679] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[ 15.184781] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[ 15.184968] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 15.185099] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 15.185162] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 15.185509] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[ 15.185539] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[ 15.185640] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[ 15.186340] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[ 15.187549] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[ 16.076500] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 17.393591] uart-pl011 3f201000.serial: no DMA platform data
[ 18.134781] Bluetooth: Core ver 2.22
[ 18.135390] NET: Registered protocol family 31
[ 18.135403] Bluetooth: HCI device and connection manager initialized
[ 18.135431] Bluetooth: HCI socket layer initialized
[ 18.135445] Bluetooth: L2CAP socket layer initialized
[ 18.135477] Bluetooth: SCO socket layer initialized
[ 18.157080] Bluetooth: HCI UART driver ver 2.3
[ 18.157100] Bluetooth: HCI UART protocol H4 registered
[ 18.157703] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 18.160112] Bluetooth: HCI UART protocol Broadcom registered
[ 18.563821] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.563835] Bluetooth: BNEP filters: protocol multicast
[ 18.563855] Bluetooth: BNEP socket layer initialized
[ 117.345533] init: wait-for-state (zram-swapxbmc-done) main process (1989) terminated with status 100
[ 117.378060] systemd-udevd[118]: Failed to touch /run/udev/queue: No such file or directory
[ 117.384004] systemd-udevd[118]: Failed to touch /run/udev/queue: No such file or directory
[ 117.386845] zram: Added device: zram0
[ 117.390799] zram: Added device: zram1
[ 117.391588] zram: Added device: zram2
[ 117.392473] zram: Added device: zram3
[ 117.441102] zram0: detected capacity change from 0 to 134217728
[ 117.502479] Adding 131068k swap on /dev/zram0. Priority:20 extents:1 across:131068k SSFS
[ 117.662455] Adding 250364k swap on /dev/mmcblk0p3. Priority:0 extents:1 across:250364k SSFS
[ 180.474962] init: wait-for-state (xbmcxbmc-loaded) main process (2797) terminated with status 100
[ 180.560855] init: xbmc-failed-start main process (534) killed by TERM signal
[ 180.656022] init: xbmc post-start process (2787) terminated with status 1
[ 181.166488] init: wait-for-state (kill-splashxbmc-exits) main process (3068) killed by TERM signal

Should I expect the Xbian 'latest buster image' to boot straight into Kodi on a virgin Pi3B?
Can someone point me to the location of a log file on the sdcard that might reveal more?

It's been several years since I last dabbled with any of this stuff. My multiple Pi1B's running OpenElec 5.0.8 / kernel 3.17.8 / Kodi 14.2 are still in service playing files via SMB (no streaming add-ons).

I recently bought a Pi Zero 2 W, which (based upon my research) probably needs a 5.10 kernel and new dtb file - hence my focus on a 'recent' Buster-based distribution. When Xbian's Kodi would not start on *it*, I pulled my old never used Pi3B off the shelf, rewrote the sdcard, and had the same problem on the Pi3B.

If you’re trying to use the same image on both Pi’s, I’m not entirely certain that’s possible. I’m also not anywhere near sure that there’s an xbian (or even official kodi) version for the new little one.
All sorts of things wrong with that post, so @Nachteule was probably just being nice in his response about junk equipment. The 3b is still a viable platform, but the new Zero? That’s just a fairly capable IoT device, not a HTPC/server.


Sent from my iPhone using Tapatalk