A place to talk about anything and everything Omega related
4314
Topics
23541
Posts
hi @mauriziomeucci, sorry to hear about the frustration caused by not having the avahi daemon.
To quote @crispyoz:
The term "Beta" indicating that it is a test release inviting feedback, which would include which packages users may prefer to be included.
The 23.05 firmware is still in beta and not yet our stable firmware. We want to give users a chance to try it out before rolling it out as the default firmware in the factory.
If you have specific improvement suggestions (or bugs to report), you can create an Issue in the OnionIoT/OpenWRT-Packages GitHub Repo. There are issue templates you can use for Improvement Suggestions/Feature Requests and Bug Reports.
You can also try building your own version of the 23.05 firmware that includes the avahi daemon. This is now very easy and takes minutes instead of hours. See the How to Build Custom Firmware article in the new documentation for the procedure.
Let me know how it goes!
@luz what's a quick way to test if IPv6 and link local is enabled in the new fw? I'm not too familiar with IPv6 - I need to study
@luz hahaha, trying to become a full onioneer little by little.
It is the Omega2+. Here is a log of the boot process to see if I'm missing anything.
U-Boot 2024.04-gc2bfb2b8c6 (Jul 19 2024 - 15:18:23 -0400)
CPU: MediaTek MT7688A ver:1 eco:2
Boot: DDR2, SPI-NOR 3-Byte Addr, CPU clock from XTAL
Clock: CPU: 580MHz, Bus: 193MHz, XTAL: 40MHz
Model: Onion Omega2+
DRAM: 128 MiB
Core: 59 devices, 18 uclasses, devicetree: separate
Loading Environment from SPIFlash... SF: Detected mx25l25635e with page size 256 Bytes, erase size 64 KiB, total 32 MiB
OK
In: uartlite@c00
Out: uartlite@c00
Err: uartlite@c00
Initializing MT7688 GPIO system.
Net: eth0: eth@10110000
Hit any key to stop autoboot: 0
=>
I did see that address 80800000 is outside the zone range of the memory but the load address is defined as 0x80800000 and trying to load it via tftp and booting anywhere else fails to decompress the image. Maybe thats the issue and just assumed it should work. Thought the offset would take care of that but maybe I am misunderstanding what the offset does
CONFIG_SYS_LOAD_ADDR=0x80800000
While OpenWrt is a single user system, you can create additional users so you don't have to disclose the root user password. You can add the user by editing /etc/passwd and /etc/shadow or you can install the useradd package:
opkg install shadow-useradd
Now add a new user named "admin", but we don't want them to have shell access:
useradd admin -d /var -M -s /bin/false -p mytemporarypassword
The password is added in cleartext so you need to change it using the command:
passwd admin
Follow the prompts to set your password then you can confirm the new user has been added as required:
cat /etc/passwd
cat /etc/shadow
Since OnionOS uses ubus via rpc we need to add the user to the rpc user list. The configuration file is /etc/config/rcpd, but you can use uci commands to add the user:
uci add rpcd login
uci set rpcd.@login[-1].username='admin'
uci set rpcd.@login[-1].password='$p$admin'
uci add_list rpcd.@login[-1].read='*'
uci add_list rpcd.@login[-1].write='*'
uci commit rpcd
The username must match the username we just created and the structure of the password field causes the rpc daemon to use the system password we just created.
The "read" and "write" fields is set to an asterisk indicating that the user will have unrestricted access, the same as the root user.
You can confirm the new user had been added using a uci command:
uci show rpcd
rpcd.@login[0]=login
rpcd.@login[0].username='root'
rpcd.@login[0].password='$p$root'
rpcd.@login[0].read='*'
rpcd.@login[0].write='*'
rpcd.@login[1]=login
rpcd.@login[1].username='admin'
rpcd.@login[1].password='$p$admin'
rpcd.@login[1].read='*'
rpcd.@login[1].write='*'
Now restart the rpc daemon:
service rpcd restart
You can now login to OnionOS with the same functionality as the root user has, but the user has no console access.
@cyberai pls try running the checkCamera.py Example Python Program and posting the command line output and screenshots of the output.
This will give us a better idea of what's going on.
