Build current and edge releases on Odroid C1

[torz77]

I just got home to a successfully built image from the master branch

 

  ___      _           _     _    ____ _ 
 / _ \  __| |_ __ ___ (_) __| |  / ___/ |
| | | |/ _` | '__/ _ \| |/ _` | | |   | |
| |_| | (_| | | | (_) | | (_| | | |___| |
 \___/ \__,_|_|  \___/|_|\__,_|  \____|_|
                                         
Welcome to Armbian 23.02.0-trunk Jammy with Linux 5.15.95-meson

No end-user support: built from trunk

System load:   47%              Up time:       3 min
Memory usage:  8% of 990M       IP:            192.168.1.77
CPU temp:      46°C             Usage of /:    21% of 7.0G   
RX today:      31.4 KiB

Thanks again for your continued work on this.

[sgjava]

@torz77Any other stuff you find not working I'll add to issues. C1 was never meant to run 6.1 kernel, hahahaha

[torz77]

I will do.

 

At the moment, I've only hit one issue, and that is the need to power-cycle the board to reboot. Unfortunately I can't connect a serial console, so can only go off SSH. (I'll check the log next time I reboot). `sudo reboot now` throws me out of SSH as expected, but the network connection stays up (I can ping the board), although cannot reconnect on SSH until after power cycling, so it looks like it is getting stuck somewhere prior to shutting down networking.

 

This is a mild frustration, rather than the end of the world. The board is just running as an OpenLDAP server for my homelab, so shouldn't need power cycling too often. I was going to put an OpenVPN server on it too, but I may skip that if I can't reboot it remotely.

[sgjava]

@torz77That may be why all wifi adapters cause the ping response to go up into the seconds and heartbeat slows way down. It's probably in the device tree (dtb) or uboot, show knows. This is definitely a hack way to do it, but nothing else runs current kernels or distros. But yeah, manual power cycle for now.

[Kovács Gábor]

Hello Everyone,

Thanks for all your help. I've got the image compiled, however it doesn't work on the C0. Maybe next week I'll be able to debug via uart to see what is happening (blue LED is blinking as it should).  Additional thanks to torz77 for sharing me an image!

[sgjava]

@Kovács Gábor as I've stated above I've had no luck with USB wifi. I did test C1 with "Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter" The thing is network manager is not going to auto activate it. You'll need to go into the serial console and configure with nmtui. I do this with the NanoPi Duo since there's no wired Ethernet. The nice thing is the Duo uses the OTG port, so you can power and do serial off your PC. If you see a heartbeat then it's probably firing up.

 

One trick you could use is to configure a C1 with same USB Ethernet and just copy the configuration over from nmtui. For instance built in eth0 is under /etc/NetworkManager/system-connections/Wired\ connection\ 1.nmconnection. You'd need to figure out which network manager files to copy. I used to do this with wifi only devices. Configure on the hard way, then just make edits on SD card.

[samaritan]

Could someone upload the latest working image somewhere please? I have 2 old odroid-c1 board that I would like to use only with ssh, docker and external HD. Will that be possible with the current situation?

[samaritan]

I am so sorry!

Edited March 15, 2023 by samaritan

[SteeMan]

@samaritan  This is an Armbian forum, not a dietpi forum.  Please direct your posts elsewhere for dietpi issues.

[samaritan]

@SteeMan I am so sorry I didn't realized that the windows was the wrong one.

 

 

[samaritan]

Oups

Edited March 15, 2023 by samaritan

[samaritan]

The images are not worth running in production because at some point there's sd card corruption it is worth mentioning.

[sgjava]

I already mentioned that. If you stick with Ethernet then it's stable. nmtui adding wifi will hose your system.

 

[Kovács Gábor]

@sgjava Sorry for being away for such a long time, I had lots of things to do. I will be trying again with the odroid c0 next week using a serial console connection. There is one more thing I would like to ask you. Does this new kernel support USB at all? I understand that there is a problem with USB based Ethernet adapters, but in my case I would like to use a 4G USB Stick. In case you confirm that USB works, I will try to make this thing work. Otherwise - if USB is not supported at all - there would be no reason in experimenting. Thanks again.

[sgjava]

I tested a Realtek RTL8152B 10/100 adapter, so storage probably works as well. Wifi would corrupt the SD, so I never got that working.

[Kovács Gábor]

@sgjavaThanks, then I will give a try next week.

[going]

29.01.2023 в 21:20, sgjava сказал:

git clone --depth=1 --branch=master https://github.com/armbian/build

I'm sorry, @sgjava are you still doing this?

[sgjava]

@goingYes, as of last time I built, but you could try main or whatever new "master" branch is.

[going]

If you're interested, I'm just continuing to develop this master branch here.

 

[sgjava]

@goingIf you could just fix uboot and dtb we'd be all set, hahahaha

[going]

17 часов назад, sgjava сказал:

If you could just fix uboot and dtb we'd be all set

uboot I fixed in my branch.
Fixed it in the sense that if you assemble the image then it will load.
DTB for uboot or for kernel?
Does dtb work for kernel?
@sgjava I can probably make some changes to the dts, but I won't be able to check them.

I don't have this device and this fact makes it very difficult.

You can just check for EDGE to get the CLI image:

./compile.sh BUILD_ONLY="default" BUILD_MINIMAL=yes

 

Before starting the build system, please clear the "output/debs/*" folder.
In my branch, the directory structure for future package files will be slightly different.

[sgjava]

@goingSo you can get USB wifi to work? What about reboot? uboot used to not build, thus why I had to pull the debs.

[going]

2 минуты назад, sgjava сказал:

So you can get USB wifi to work?

Two things are needed for this to work.
The driver is in the kernel.
UDEV rules for switching usb modeswitch.

 

4 минуты назад, sgjava сказал:

What about reboot?

Reboot as a command on the command line or from a button?

 

14 минут назад, sgjava сказал:

uboot used to not build, thus why I had to pull the debs.

One inattentive developer made changes to the build system,

but did not check other development lines and this made the uboot package broken for the record.

This is fixed.

[torz77]

Reboot definitely doesn't work from cli. I don't have a button, so can't test.

 

Basically SSH session closes, but the network interface still pings until a power cycle.

[itsmaxdd]

Any feedback on a daily usable version?

[torz77]

I've been using this daily on a headless C1+ with no issues (outside of the reboot issue, which I can live with).

[itsmaxdd]

Are you building from source? Mind sharing the IMG? Have you tried docker as well?

[torz77]

Yes, I built from source. Unfortunately I don't think I still l have the img around. I have not tried Docker, no.

[torz77]

So, I have revisited my Odroid C1+ board, as I want to move away from Ubuntu. I'm pleased to say that the latest Armbian (Bookworm) builds just fine for the Odroid C1+, with the same caveats as before:

- Probably No HDMI (Not tested)

- Probably No WiFi (Not tested)

 

However, unlike before, rebooting seems to work fine without requiring a manual power cycle.

 

Whilst the instructions work for me, that does not mean that they will work for you. I just provide this here for any other Odroid C1+ users who may want to get a more up to date distro + kernel on their board. I have not done any extensive testing

 

I have built a Debian Bookworm image on a Debian Bookworm host system. I include the instructions that worked for me below. At the time of image build there is no need to download any external files from elsewhere. I have built a minimal image as that is what I require. I have not tested with any other flags. I built on host system without Docker, so cannot speak for the Docker build process.

 

With that said, current process is very simple. HEAD was at commit  `fc54623c4a6dd3b1a8fb5f0a325e5461f0ae6364`, in case you need to go back to a known working build.

 

sudo apt install git

git clone --depth=1 https://github.com/armbian/build.git

./compile.sh \
BOARD=odroidc1 \
BRANCH=current \
RELEASE=bookworm \
BUILD_MINIMAL=yes \
BUILD_DESKTOP=no \
CLEAN_LEVEL= \
PREFER_DOCKER=no \
KERNEL_CONFIGURE=no \
COMPRESS_OUTPUTIMAGE=sha,gpg,img

 

And that's it. Image is saved in:

./output/images

 

Final image running on the Odroid C1+:

  /_\  _ _ _ __ | |__(_)__ _ _ _ ___ _  _ _ _  ___ / _|/ _(_)__(_)__ _| |  
 / _ \| '_| '  \| '_ \ / _` | ' \___| || | ' \/ _ \  _|  _| / _| / _` | |  
/_/ \_\_| |_|_|_|_.__/_\__,_|_||_|   \_,_|_||_\___/_| |_| |_\__|_\__,_|_|  
                                                                            
v24.11 rolling for Odroid C1 running Armbian Linux 6.6.43-current-meson  
  
Packages:     Debian stable (bookworm)  
Support:      DIY (custom image)  
IP addresses: (LAN) IPv4: xxx.xxx.x.xxx IPv6: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (WAN) xx.xx.xx.xxx  
  
Performance:     
  
Load:         13%              Up time:       12 min  
Memory usage: 7% of 988M      
CPU temp:     49°C             Usage of /:    3% of 29G       
  
Commands:    
  
Configuration : armbian-config  
Monitoring    : htop

 

Edited 14 hours ago by torz77