Raspberry Pi Installation Help?

[gkusiak]

(10th May, 2021 07:40 AM)Nachteule Wrote:  

(10th May, 2021 04:13 AM)gkusiak Wrote:  will RasPi 4 xbian boot from USB? how do I make that happen?

In the meantime, this works great. I have the following configuration here:

1) boot from sd-card (if available)
2) boot from USB disk (if available)
3) boot from network (PXE boot)

Works fine, rpi-eeprom package is your friend

Terminal

root@kmxbilr2 ~ # apt-cache policy rpi-eeprom
rpi-eeprom:
Installiert: (keine)
Installationskandidat: 12.1-1
Versionstabelle:
12.1-1 500
500 http://kmcubie devel/main armhf Packages
7.9-1 500
500 http://kmcubie stable/main armhf Packages
root@kmxbilr2 ~ #

sorry to re-hash this, but I'm failing to understand how to make this happen right at this moment, changing to boot from USB

Terminal

root@xbian:/home/xbian# apt-cache policy rpi-eeprom
rpi-eeprom:
Installed: (none)
Candidate: 12.14-1
Version table:
12.14-1 500
500 http://apt.xbian.org stable/main armhf Packages
7.9-1 500
500 http://apt.xbian.org stable/main armhf Packages

what do I tell it? apt-install? apt-get? apt boot-usb-please?

[Nachteule]

Unfortunately i can't help you much more. I'm glad that I managed to do this for myself. you just have to install the package and read the man-pages and the docs. a good start is here: https://github.com/raspberrypi/rpi-eeprom or better here: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-4-bootloader-configuration

Smartly the heroes have changed their whole documentation structure, I don't know my way around anymore and all the links you are looking for are empty. Great strategy from RPF I can only say.

Anyway, my configuration looks like this

Terminal

root@kmxbilr2 ~ # rpi-eeprom-config
[all]
BOOT_UART=0
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=15000
TFTP_IP=
BOOT_ORDER=0xf241
SD_BOOT_MAX_RETRIES=3
NET_BOOT_MAX_RETRIES=5
ENABLE_SELF_UPDATE=1
DISABLE_HDMI=0
[none]

The parameter BOOT_ORDER is the one that must be adjusted. I set it to boot first from SD, then from USB and last from network.

[gkusiak]

Ok I guess I have to figure out how to edit that config. And find it first.
Thank you


Sent from my iPhone using Tapatalk

[Nachteule]

(30th Nov, 2021 01:06 AM)gkusiak Wrote:  Ok I guess I have to figure out how to edit that config. And find it first.
Thank you


Sent from my iPhone using Tapatalk

Terminal

root@kmxbilr2 ~ # rpi-eeprom-config -e
Updating bootloader EEPROM
image: /lib/firmware/raspberrypi/bootloader/default/pieeprom-2021-04-29.bin
config_src: vcgencmd bootloader_config
config: /tmp/tmp5uusnhdw/boot.conf
################################################################################​
[all]
BOOT_UART=0
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=15000
TFTP_IP=
BOOT_ORDER=0xf241
SD_BOOT_MAX_RETRIES=3
NET_BOOT_MAX_RETRIES=5
ENABLE_SELF_UPDATE=1
DISABLE_HDMI=0
[none]
FREEZE_VERSION=0

################################################################################​
*** INSTALLING /tmp/tmp5uusnhdw/pieeprom.upd ***

CURRENT: Do 29. Apr 16:11:25 UTC 2021 (1619712685)
UPDATE: Do 29. Apr 16:11:25 UTC 2021 (1619712685)
BOOTFS: /boot

EEPROM updates pending. Please reboot to apply the update.
To cancel a pending update run "sudo rpi-eeprom-update -r".

If it complains that it can't find vcgencmd (for me it does when I use sudo), a sudo ln -s /opt/vc/bin/vcgencmd /usr/local/bin/vcgencmd helps

The whole rpi-eeprom package is still a mess, but somehow you get it right

[gkusiak]

(30th Nov, 2021 01:22 AM)Nachteule Wrote:  

Terminal

root@kmxbilr2 ~ # rpi-eeprom-config -e
Updating bootloader EEPROM
image: /lib/firmware/raspberrypi/bootloader/default/pieeprom-2021-04-29.bin
config_src: vcgencmd bootloader_config
config: /tmp/tmp5uusnhdw/boot.conf
################################################################################​
[all]
BOOT_UART=0
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=15000
TFTP_IP=
BOOT_ORDER=0xf241
SD_BOOT_MAX_RETRIES=3
NET_BOOT_MAX_RETRIES=5
ENABLE_SELF_UPDATE=1
DISABLE_HDMI=0
[none]
FREEZE_VERSION=0

################################################################################​
*** INSTALLING /tmp/tmp5uusnhdw/pieeprom.upd ***

CURRENT: Do 29. Apr 16:11:25 UTC 2021 (1619712685)
UPDATE: Do 29. Apr 16:11:25 UTC 2021 (1619712685)
BOOTFS: /boot

EEPROM updates pending. Please reboot to apply the update.
To cancel a pending update run "sudo rpi-eeprom-update -r".

If it complains that it can't find vcgencmd (for me it does when I use sudo), a sudo ln -s /opt/vc/bin/vcgencmd /usr/local/bin/vcgencmd helps

The whole rpi-eeprom package is still a mess, but somehow you get it right

my eeprom is current thankfully - that sudo ^ was a big help, but now
I think I'm having to update EACH of those parameters in the command just to get the boot order changed...which is definitely a mess

UPDATE - yes, it does: somehow I managed to make it work to my great surprise. (And a USB3 thumb drive is SIGNIFICANTLY faster than an SD card - maybe the Pi5 will do away with them)

[plugh]

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.

[Nachteule]

@plugh
I suspect that simply Kodi is not started, why? - no idea. Of course Kodi should start immediately on a freshly installed system
Try running sudo start xbmc or kodi start in a ssh connection to see if Kodi at least starts manually.
You can find the Kodi log in folder /home/xbian/.kodi/temp/

About the Pi Zero 2W: Why do you always buy such garbage just to save some money and get into a lot of trouble. With 512MB memory for example you really won't be happy with a current Kodi, so don't bother.

[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

[syaochan]

Hi to everyone, sorry if I post in this thread but as a new user I cannot open a new thread.
I'm attempting to have xbian boot from USB SSD on an Raspberry Pi 4, but failed until now.
What I tried:
- Flash xbian image directly to SSD: boot stops at "waiting for root..." and then I get recovery console. Tried with /dev/sda2 and root device UUID in cmdline.txt
- Flash xbian to sdcard and then use xbian copier to copy to SSD: same results as above after removing sdcard and modifying cmdline.txt with correct SSD data
What can I do?

[Nachteule]

(29th Dec, 2021 04:24 AM)syaochan Wrote:  Hi to everyone, sorry if I post in this thread but as a new user I cannot open a new thread.
I'm attempting to have xbian boot from USB SSD on an Raspberry Pi 4, but failed until now.
What I tried:
- Flash xbian image directly to SSD: boot stops at "waiting for root..." and then I get recovery console. Tried with /dev/sda2 and root device UUID in cmdline.txt
- Flash xbian to sdcard and then use xbian copier to copy to SSD: same results as above after removing sdcard and modifying cmdline.txt with correct SSD data
What can I do?

Check in recovery console whether the usb disk is recognized

[syaochan]

(29th Dec, 2021 04:39 AM)Nachteule Wrote:  Check in recovery console whether the usb disk is recognized

That seems to be the problem, uas module was not loaded. I loaded the module, mounted /dev/sda2 under /rootfs and exited recovery console. Boot completed and Kodi started. How can I set to load uas module at boot?

[Nachteule]

You could add uas to /etc/modules and make sure that initramfs ist set to always in XBian-Config GUI -> System

In the future the module will be compiled into the kernel, then this problem should not occur anymore

[gkusiak]

How far in the future?


Sent from my iPhone using Tapatalk

[Nachteule]

(29th Dec, 2021 08:32 AM)gkusiak Wrote:  How far in the future?


Sent from my iPhone using Tapatalk

Tomorrow (Kernel 5.10.88 has it in)

[gkusiak]

That’s incredibly responsive of you
Thank you


Sent from my iPhone using Tapatalk