Hi all,
I’ve the same issue. How many lights do the Blade have. When I plug in the power cable I have a continiues light shining. Is there anything else?
Tom
I am facing the same error: booting casaOS, I see from my router DHCP worked, but I am unable to contact it in any way. Ping from router to zima and zima to router are failing with a mix of timeout and host unreachable.
I have then tried to install Proxmox and Debian 12 on a second SSD I have plugged, these 2 OS are not even able to complete the DHCP request properly. With Proxmox sometimes I was able to see an IP was offered, but never got an answer from the Zima, other times not even the offer.
I have tried also using 3 different ethernet cables, leading to the same results.
At this point I am quite disappointed, first the faulty RAM I have described in the other thread, then this.
What are you talking about, who said anything about Zima? I get the IP’s from my router.
I think 777-Spider refers using http://casaos.local.
Anyway I got updates. The support asked me via email to try to install Windows. I did and in fact I have internet access from the Zima and I am able to ping the router, but I am not able to ping the Zima from the router (I am not familiar with Windows, so maybe there are some extra settings to do).
I came back to casaOS and “sudo dmesg” returned me an error with the Realtek NIC firmware:
firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
I will try today to install the firmware package manually (Debian -- Package Download Selection -- firmware-realtek_20230210-5_all.deb).
Can you try connect a screen/TV to the Zima, a keyboard, and check for errors with sudo dmesg?
EDIT: I was able to access casaOS ui and install Proxmox on a secondary SSD. Apparently my router (Mikrotik HEXs) is having trouble with the r8168. I have plugged the ethernet into a switch and it worked. This is the first time I see this kind of error, even stranger thinking that with Windows is working fine without the need of a switch
Got my replacement board, same issues. Tried the RTC battery trick again, it got the red light on the board to turn on. Trying a different RAM today, still no luck connecting on findzima nor on casaos.local. I’m really not sure what to do with this thing.
Can you try to plug the ethernet to the router via a switch, instead of plugging it directly to the router?
And if you have time, just to test, can you try a live Linux, even better if not Debian based.
I have solved my problem, but I do not know what exactly fixed it, as I also updated twice my router in the process.
Now I have Proxmox installed on an external SSD drive, and since then I am also able to plug the Zima directly to the router. To install it I needed to plug into a switch, as I had no link after DHCP if I plugged directly to the router (both with native CasaOS, Proxmox 7.4 with kernel 5, 8.1 with kernel 6, and EndeavourOS).
Due to the fact that Windows was working fine, and Linux via the switch was working fine as well, I suppose there is some kind of bug at L2 frames between this specific NIC (rtl8168h) on Linux (maybe at kernel level?) and some routers’ internal switch chip (my router uses the MT7621). I have even tried to play with different MTU sizes, but at the end I came back to 1500.
EDIT: for info, my switch uses a RTL8370N chip.
Does the USB PSU specifically say on it that it outputs 12V/3A on the small print on it?
If USB C PD negotation fails then the PD spec says that PSU should drop to 5V.
I received my 3 blades today.
0) RAM purchased worked for me
- I found that the zima app does not detect it.
The board did not have zerotier running - so no surprise - One of the 3 did not boot. I am preparing a zima USB drive now
- All the boards have same serial number on their individual carton
- I was able to use the provided power supply and I was able to use the 140W PD port on ISDT Power X200
- I was not able to connect my ADLINK PocketAI. I feel this may be something odd with the zimablade as the PocketAI works with a 12v USBC PD connector on a low end laptop
Also, it appears that the casaos script that sets the App repo needs help. It was getting apps from China and not github.
I found correction at the github. So I corrected the error. I will reinstall casaos from git and this will be corrected.
Update…
I recommend installing debian from scratch.
Side-by-side with the stock install I find I saved a ton of storage, fewer services were running, i did not need to find all the ‘stuff’ left behind such as the casaos user, and spelunking out the odd things such as app repo being in China.
My idle power use seemed lower on the fresh install as well
Fmotta, any tips for installing Debian? I’m a linnoob so any help is appreciated, even websites with guidance
@tmoney
Having installed Windows many many times (and a time or two in past month), and Linux dozens more times than Windows, I find that installing Linux to be as simple as it can be. Whereas installing Windows is as difficult as it can be.
IMO… if you have installed Windows 8 or later, you will find Debian and Ubuntu to be easier than falling off a chair.
- Download the ISO file from the web
- Use blenaEcher to write it to a thumbdrive
- Install a USB hub with the thumbdrive and keyboard and mouse
- Plug in DP port to monitor and power
- Press esc (I think … maybe F1 or Del) to get into BIOS
- Choose the thumbdrive to boot
- Follow the prompts and likely accept defaults on install to the emmc
- Let it install and reboot
- Power off and unplug thumbdrive
- Power on and have an OS
As for installing CasaOS… the website makes it as easy as one command (after the system boots, has network access, and you have root privileges)
Amazing, I will give it a try thanks fmotta!