yes
no. Just change branch using option 1
yes
no. Just change branch using option 1
Now I got it. Nope, still the same, just without the ānot detectedā message: https://www.youtube.com/watch?v=452XuI9I--k
Hey,
first of all - thanks for your work on openhabian and your effort to bring us a working RPi5 release.
I installed the 64bit beta release (v1.9) openhabian image onto a RPi 5 8GB Model. Canāt upload my first-boot.log yet, as my account is too new. Maybe it will work after this first postā¦
//edit: Here it is:
first-boot.log (286.3 KB)
Had problems with installing influxdb due to the missing bookworm release - changed it to ādebian stable mainā in the bash file and everything works as expected now.
Not tested the wifi configuration with openhabian-config yet, as I already configured it inside the pi-imager.
//edit2: Deactivated the wifi via openhabian-config and reactivated it after a restart - unfortunately without success. The console showed me the following.
+ case "$choice2" in
+ configure_wifi setup
+ [[ -z 1 ]]
+ local disabledText
+ local enabledText
+ local questionText
+ local wifiConfig
+ local wifiCountry
+ local wifiNetworkList
+ local wifiPassword
+ local wifiSSID
+ disabledText='WiFi is currently disabled on your box.\n\nATTENTION:\nWould you like to enable WiFi and continue setup?'
+ enabledText='WiFi is currently enabled on your box.\n\nATTENTION:\nWould you like to disable WiFi and use Ethernet?'
+ questionText='We could not detect any WiFi hardware on your system.\nYou are not running any of supported systems (RPi4, RPi3, RPi0W) which have WiFi builtin. However, we cannot detect all possible WiFi hardware.\nDo you really want to continue and have openHABian try to setup WiFi?'
++ timestamp
++ printf '%(%F_%T_%Z)T\n' -1
+ echo -n '2023-11-16_08:17:42_CET [openHABian] Beginning WiFi configuration... '
2023-11-16_08:17:42_CET [openHABian] Beginning WiFi configuration... + is_pi_wlan
+ is_pifive
+ [[ '' == \p\i\5 ]]
+ grep -q '^Revision\s*:\s*[ 123][0-9a-fA-F][0-9a-fA-F][0-9a-fA-F]17[0-9a-fA-F]$' /proc/cpuinfo
+ return 0
+ return 0
+ echo OK
OK
+ [[ setup == \s\e\t\u\p ]]
+ grep -qsE '^[[:space:]]*dtoverlay=(pi3-)?disable-wifi' /boot/config.txt
+ whiptail --title 'WiFi is currently disabled' --yesno 'WiFi is currently disabled on your box.\n\nATTENTION:\nWould you like to enable WiFi and continue setup?' 10 80
+ cond_redirect enable_disable_wifi enable
+ [[ -n '' ]]
+ echo -e '\n\033[90;01m$ enable_disable_wifi enable \033[39;49;00m'
$ enable_disable_wifi enable
+ enable_disable_wifi enable
+ is_pi
+ is_pifive
+ [[ '' == \p\i\5 ]]
+ grep -q '^Revision\s*:\s*[ 123][0-9a-fA-F][0-9a-fA-F][0-9a-fA-F]17[0-9a-fA-F]$' /proc/cpuinfo
+ return 0
+ return 0
+ [[ enable == \e\n\a\b\l\e ]]
++ timestamp
++ printf '%(%F_%T_%Z)T\n' -1
+ echo -n '2023-11-16_08:17:45_CET [openHABian] Enabling WiFi... '
2023-11-16_08:17:45_CET [openHABian] Enabling WiFi... + grep -qsE '^[[:space:]]*dtoverlay=(pi3-)?disable-wifi' /boot/config.txt
+ sed -i -E '/^[[:space:]]*dtoverlay=(pi3-)?disable-wifi/d' /boot/config.txt
+ echo 'OK (reboot required)'
OK (reboot required)
+ return 0
+ is_pi_wlan
+ is_pifive
+ [[ '' == \p\i\5 ]]
+ grep -q '^Revision\s*:\s*[ 123][0-9a-fA-F][0-9a-fA-F][0-9a-fA-F]17[0-9a-fA-F]$' /proc/cpuinfo
+ return 0
+ return 0
+ dpkg -s firmware-brcm80211
+ dpkg -s wpasupplicant wireless-tools
++ timestamp
++ printf '%(%F_%T_%Z)T\n' -1
+ echo -n '2023-11-16_08:17:45_CET [openHABian] Checking if WiFi is working... '
2023-11-16_08:17:45_CET [openHABian] Checking if WiFi is working... + iwlist wlan0 scan
+ grep -qs 'Interface doesn'\''t support scanning'
+ rfkill unblock wifi
/opt/openhabian/functions/wifi.bash: Zeile 60: rfkill: Kommando nicht gefunden.
+ ip link set wlan0 up
Cannot find device "wlan0"
+ iwlist wlan0 scan
+ grep -qs 'Interface doesn'\''t support scanning'
+ echo FAILED
FAILED
+ echo -e '\nI was not able to turn on the WiFi\nHere is some more information:\n'
I was not able to turn on the WiFi
Here is some more information:
+ rfkill list all
/opt/openhabian/functions/wifi.bash: Zeile 65: rfkill: Kommando nicht gefunden.
+ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether d8:3a:dd:ae:c1:69 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.77/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
valid_lft 863820sec preferred_lft 863820sec
inet6 2001:4dd0:4add:0:78e0:ce01:b33e:a474/64 scope global dynamic noprefixroute
valid_lft 7021sec preferred_lft 3421sec
inet6 fe80::4c97:6dab:c721:2854/64 scope link noprefixroute
valid_lft forever preferred_lft forever
+ return 1
+ '[' 1 -ne 0 ']'
+ whiptail --msgbox 'There was an error or interruption during the execution of:\n "30 | System Settings"\n\nPlease try again. If the error persists, please read /opt/openhabian/docs/openhabian-DEBUG.md or https://github.com/openhab/openhabian/blob/main/docs/openhabian-DEBUG.md how to proceed.' 14 80
+ return 0
+ true
+ show_main_menu
+ local choice
+ local version
Iāll keep you up to date.
Iāve upgraded you to a basic user. You should be able to post it now.
@mstormi
Sure I can do. But your link does not longer provides the images I have found before.
If you can point me to the 64-bit image I will try.
I noticed that āKernelā and āPlatformā in the connection message says something strange - perhaps the system is being misidentified here?
###############################################################################
############### openhabian ##################################################
###############################################################################
## Ip = 192.168.1.77
## Release = Debian GNU/Linux 12 (bookworm)
## Kernel = Linux 6.1.0-rpi4-rpi-2712
## Platform = BCM43455 37.4MHz Raspberry Pi 3+-0190
## Uptime = 0 day(s). 0:1:5
## CPU Usage = 1.75% avg over 4 cpu(s) ( core(s) x - socket(s))
## CPU Load = 1m: 0.90, 5m: 0.32, 15m: 0.11
## Memory = Free: 6.58GB (84%), Used: 1.36GB (16%), Total: 7.86GB
## Swap = Free: 1.09GB (100%), Used: 0.00GB (0%), Total: 1.09GB
## Root = Free: 51.10GB (91%), Used: 4.77GB (9%), Total: 58.29GB
## Updates = 2 apt updates available.
## Sessions = 1 session(s)
## Processes = 159 running processes of 4194304 maximum processes
###############################################################################
For comparison, here is the message from my Pi4 (32bit) production system:
###############################################################################
############### openhabian ##################################################
###############################################################################
## Ip = 192.168.1.31
## Release = Raspbian GNU/Linux 11 (bullseye)
## Kernel = Linux 6.1.21-v8+
## Platform = Raspberry Pi 4 Model B Rev 1.1
## Uptime = 19 day(s). 12:19:43
## CPU Usage = 0.25% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
## CPU Load = 1m: 0.10, 5m: 0.04, 15m: 0.01
## Memory = Free: 1.19GB (32%), Used: 2.55GB (68%), Total: 3.75GB
## Swap = Free: 2.99GB (100%), Used: 0.00GB (0%), Total: 2.99GB
## Root = Free: 21.49GB (79%), Used: 5.38GB (21%), Total: 28.05GB
## Updates = 4 apt updates available.
## Sessions = 1 session(s)
## Processes = 131 running processes of 32768 maximum processes
###############################################################################
After disabling and trying to re-enable wifi with openhabian-config the wlan0 interface isnāt available any more. I checked the /boot/config.txt - but itās not just deactivated with dtoverlay=disable-wifi
.
Are there any driver installs happen, which could mess up the internal wifi-chip?
@mstormi
Installation of the 64-bit version didnāt work for me. I tried two times with the same result:
first-boot.log 0 bytes, date 12.08.2023, 14:14
RPI5 never became visible in my network
So it looks as if got stuck in a very early phase.
Currently I canāt check the screen output as I have to get a micro HDMI adapter first. Any other āpost-mortemā infos I can provide?
Iāll try again once I have the HDMI adapter, best case tomorrow.
@mstormi
Using this link version 1.8b is the latest release available, so I have accidently installed this (which has failed). I canāt find the 1.9 version on Github
try again
@mstormi
Worked. I could install the 64-bit image āopenhabian-pi-raspios64-202311152115-git5e2bdc7-crc8aeb7e78.img.xzā successfully on my RPI5 with Openhab up and running.
first-boot.log (291.5 KB)
Iāve created a beta release please try the bullseye and bookworm variants.
Please try wifi, Iād guess it will not do on bookworm because of changes to interface name and switch to Network Manager.
Iāve tested all three images on RPI5
The images
did not install on RPI5, but I think this is expected.
Screen message:
The installed operating system (OS) does not indicate support for Raspberry Pi 5
Update the OS or set os_check=0 in config.txt to skip this check
The image
This is how the /boot dir looked like:
12 4 drwxr-xr-x 3 root root 4096 Oct 10 03:57 .
2 4 drwxr-xr-x 18 root root 4096 Oct 10 03:57 ..
35 0 lrwxrwxrwx 1 root root 20 Oct 10 03:39 cmdline.txt -> firmware/cmdline.txt
494 228 -rw-r--r-- 1 root root 230365 Oct 5 11:33 config-6.1.0-rpi4-rpi-2712
551 228 -rw-r--r-- 1 root root 230343 Oct 5 11:33 config-6.1.0-rpi4-rpi-v8
36 0 lrwxrwxrwx 1 root root 19 Oct 10 03:39 config.txt -> firmware/config.txt
1 4 drwxr-xr-x 5 root root 4096 Jan 1 1970 firmware
743 10844 -rw-r--r-- 1 root root 11101826 Oct 10 03:57 initrd.img-6.1.0-rpi4-rpi-2712
1405 10844 -rw-r--r-- 1 root root 11102336 Oct 10 03:56 initrd.img-6.1.0-rpi4-rpi-v8
37 0 lrwxrwxrwx 1 root root 17 Oct 10 03:38 overlays -> firmware/overlays
484 4 -rw-r--r-- 1 root root 83 Oct 5 11:33 System.map-6.1.0-rpi4-rpi-2712
490 4 -rw-r--r-- 1 root root 83 Oct 5 11:33 System.map-6.1.0-rpi4-rpi-v8
744 8528 -rw-r--r-- 1 root root 8728960 Oct 5 11:33 vmlinuz-6.1.0-rpi4-rpi-2712
745 8524 -rw-r--r-- 1 root root 8726865 Oct 5 11:33 vmlinuz-6.1.0-rpi4-rpi-v8
and this is the dir /boot/firmware
1 4 drwxr-xr-x 5 root root 4096 Jan 1 1970 .
12 4 drwxr-xr-x 3 root root 4096 Oct 10 03:57 ..
678 32 -rwxr-xr-x 1 root root 31171 Oct 10 03:57 bcm2710-rpi-2-b.dtb
682 34 -rwxr-xr-x 1 root root 33367 Oct 10 03:57 bcm2710-rpi-3-b.dtb
681 34 -rwxr-xr-x 1 root root 33994 Oct 10 03:57 bcm2710-rpi-3-b-plus.dtb
683 32 -rwxr-xr-x 1 root root 31066 Oct 10 03:57 bcm2710-rpi-cm3.dtb
685 32 -rwxr-xr-x 1 root root 32559 Oct 10 03:57 bcm2710-rpi-zero-2.dtb
684 32 -rwxr-xr-x 1 root root 32559 Oct 10 03:57 bcm2710-rpi-zero-2-w.dtb
687 54 -rwxr-xr-x 1 root root 54575 Oct 10 03:57 bcm2711-rpi-400.dtb
686 54 -rwxr-xr-x 1 root root 54531 Oct 10 03:57 bcm2711-rpi-4-b.dtb
689 54 -rwxr-xr-x 1 root root 55140 Oct 10 03:57 bcm2711-rpi-cm4.dtb
688 38 -rwxr-xr-x 1 root root 38182 Oct 10 03:57 bcm2711-rpi-cm4-io.dtb
690 52 -rwxr-xr-x 1 root root 51982 Oct 10 03:57 bcm2711-rpi-cm4s.dtb
691 72 -rwxr-xr-x 1 root root 73712 Oct 10 03:57 bcm2712-rpi-5-b.dtb
692 52 -rwxr-xr-x 1 root root 52476 Oct 10 03:38 bootcode.bin
161 2 -rwxr-xr-x 1 root root 103 Jan 1 1980 cmdline.txt
113 2 -rwxr-xr-x 1 root root 1213 Oct 10 03:39 config.txt
159 2 drwxr-xr-x 3 root root 2048 Nov 19 20:52 firmware
713 12 -rwxr-xr-x 1 root root 11437 Nov 19 20:51 first-boot.bash
638 0 -rwxr-xr-x 1 root root 0 Nov 19 20:51 first-boot.log
695 4 -rwxr-xr-x 1 root root 3177 Oct 10 03:38 fixup4cd.dat
694 6 -rwxr-xr-x 1 root root 5403 Oct 10 03:38 fixup4.dat
696 10 -rwxr-xr-x 1 root root 8390 Oct 10 03:38 fixup4db.dat
697 10 -rwxr-xr-x 1 root root 8390 Oct 10 03:38 fixup4x.dat
698 4 -rwxr-xr-x 1 root root 3177 Oct 10 03:38 fixup_cd.dat
693 8 -rwxr-xr-x 1 root root 7268 Oct 10 03:38 fixup.dat
699 10 -rwxr-xr-x 1 root root 10235 Oct 10 03:38 fixup_db.dat
700 10 -rwxr-xr-x 1 root root 10235 Oct 10 03:38 fixup_x.dat
702 10842 -rwxr-xr-x 1 root root 11101826 Oct 10 03:57 initramfs_2712
701 10844 -rwxr-xr-x 1 root root 11102336 Oct 10 03:57 initramfs8
680 2 -rwxr-xr-x 1 root root 145 Oct 10 03:57 issue.txt
704 8526 -rwxr-xr-x 1 root root 8728960 Oct 10 03:57 kernel_2712.img
703 8524 -rwxr-xr-x 1 root root 8726865 Oct 10 03:57 kernel8.img
679 2 -rwxr-xr-x 1 root root 1594 Oct 10 03:38 LICENCE.broadcom
718 4 -rwxr-xr-x 1 root root 4096 Nov 20 2023 ._openhabian.conf
714 4 -rwxr-xr-x 1 root root 3872 Nov 20 2023 openhabian.conf
158 26 drwxr-xr-x 2 root root 26624 Oct 10 03:38 overlays
160 2 drwxr-xr-x 3 root root 2048 Nov 20 2023 .Spotlight-V100
707 790 -rwxr-xr-x 1 root root 807580 Oct 10 03:38 start4cd.elf
708 3664 -rwxr-xr-x 1 root root 3750600 Oct 10 03:38 start4db.elf
706 2202 -rwxr-xr-x 1 root root 2254208 Oct 10 03:38 start4.elf
709 2932 -rwxr-xr-x 1 root root 3001608 Oct 10 03:38 start4x.elf
710 790 -rwxr-xr-x 1 root root 807580 Oct 10 03:38 start_cd.elf
711 4710 -rwxr-xr-x 1 root root 4822504 Oct 10 03:38 start_db.elf
705 2910 -rwxr-xr-x 1 root root 2978368 Oct 10 03:38 start.elf
712 3638 -rwxr-xr-x 1 root root 3725288 Oct 10 03:38 start_x.elf
715 2 -rwxr-xr-x 1 root root 1372 Nov 19 20:51 webserver.bash
Anything I can do to help?
Check if openhabian-installer.service.since_bookworm
exists in /etc/systemd/system/
and eventually rename it to openhabian-installer.service
then systemctl daemon-reload
and reboot to see if installation starts.
Iām about to update the images in the links above check the bookworm one again when thatās done.
That was the reason.
Found in /etc/systemd/system/
-rw-r--r-- 1 root root 496 Nov 19 20:51 openhabian-installer.service.since_bookworm
Rename, reload, reboot. Now Openhab is properly installed.
Here you go:
No images there
@mstormi
Installed image openhabian-64-latest-202311211558.img.xz on RPI5
Openhab up and running, but WiFi was not configured (SSID and PW in openhabian.conf)
first-boot.log (291.9 KB)