[Odroid-C2 - no USB]

The USB power has been a growing issue with my C2 for years now. To have the board use the SSD through a USB/SATA adapter, I now have to power the adapter (which has a Y cable) from a neighbour board. It used to work long time ago without the other board "help". So there is probably a weakening component on my C2. Right now the voltage drops between the +5V barrel alim centre, and USB connectors' 5V. I see no rationale in this.

 

My C2 is now decommissioned (I bought a OPi 3 LTS instead). So I will try to to solder a wire under the board to have the incoming 5V straight to the USB ports. It should not be worse than the Y USB cable bringing the 5V from the neighbour board.

[Odroid-C2 - no USB]

Odroid-C2 (there was no adequate tag)

 

After I upgraded my ssd install from 23.11.1 to 24.2.1, the board didn't boot.

 

When starting 24.2.1 from a fresh sd card, usb and disk leds are on, and the board boots. But they don't show in lsusb.

If I reconnect them after the board is booted, the leds stay off (and obviously they don't show in lsusb).

 

Of course, booting from external ssd stops at some point, because usb is lost during the boot (when connecting a display, the failures start to happen on armbian services).

 

Had to restore previous release 23.11.1 from backup on my ssd. Everything works again.

[Partition table on Orange Pi 5]

On 1/25/2024 at 10:16 PM, bedna said:

Not really important, because it boots, but why is the sector before the boot partition so freakishly large (16,8MB)?

Looped img of Armbian 23.11 Jammy-amazingfated GNOME for orangepi 5

 

Previous images had a smaller gap before partition 1.

My guess is that this space is now there to allow a future switch to UEFI boot, which as far as I understood, needs an EFI partition to be 1st on the disk, and it needs that much space. Someone here probably knows better than me.

 

I already tried this new layout, with EFI on partition 1, and "generic arm64" kernel on partition 2. No success yet. Will dig into this again some time soon.

[Video overscan]

Quote

Have you redirected the sound to hdmi in the settings? Default send to the jack.

Contrary to 5.1.160, the sound output menu is empty when booting with 6.7.0-rc4

 

On 12/28/2023 at 12:44 AM, royk said:

I had the same issue with an old Samsung TV/monitor and use a HDMI->VGA adapter as workaround.

I was considering a DVI adapter to stay "digital". But your solution is bolder!

 

On 12/22/2023 at 10:29 AM, nihilowy said:

i live with that on samsung old 26 led tv. It doesnt have image adjust  / auto  settings in tv menu, so its menu option. 

 in sway or gnome i dont see upper bar with time and volume settings , but i can click on edge and menu shows up. On sway also setting floating windows for apps is usefull. 

The overscan doesn't happen on another 1080p hdmi monitor.

I looked in the edid informations which appear in:

/sys/devices/platform/display-subsystem/drm/card0/*/edid

I found "wxedid" to decode and edit the edid (it's a tricky binary format).

The relevant "timing" informations are identical between the two monitors.

I tried editing the edid and writing it back: no change.

Nor does it seem to change anything when given as a boot parameter.

[Video overscan]

The issue seems solved in kernel 6.7.0-rc4.

But other issues appeared (among which no more sound).

For now I'm staying with 5.1.160.

[Experiences with OPi5 +]

Using armbian-install I achieved to have my board boot with no sd card inserted. Try the options which use the "mtd flash" (mtdblock0 below)

 

lsblk output:

NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
mtdblock0      31:0    0    16M  0 disk  
mmcblk0       179:0    0   233G  0 disk  
├─mmcblk0p1   179:1    0   512M  0 part  /boot
│                                        /media/mmcboot
└─mmcblk0p2   179:2    0 232.4G  0 part  /media/mmcroot
mmcblk0boot0  179:32   0     4M  1 disk  
mmcblk0boot1  179:64   0     4M  1 disk  
zram0         254:0    0   7.7G  0 disk  [SWAP]
zram1         254:1    0    50M  0 disk  /var/log
nvme0n1       259:0    0 931.5G  0 disk  
├─nvme0n1p1   259:1    0    64G  0 part  
│ └─cryptswap 253:0    0    64G  0 crypt [SWAP]
├─nvme0n1p2   259:2    0    64G  0 part  /var/log.hdd
│                                        /
└─nvme0n1p3   259:3    0 803.5G  0 part  
  └─home      253:1    0 803.5G  0 crypt /home

 

mtdblock0 is a small and slow rom which is on the board itself (not on the emmc module), contains the bootloader and is not mounted.

Maybe this is what's missing to have your board boot without sd card.

[Video overscan]

Armbianmonitor:

https://paste.armbian.com/soqixumoyu

When connected to some PC monitors, the image is larger than the physical screen: about 20 pixels at the top and bottom sides, and 50 pixels at the right and left sides are missing.

This happens as soon as the board boots (without logo), the start of lines are truncated, and this also happens on text ttys (Ctrl + Alt + F1..6).

I guess it's about a boot env variable, but I could not find it.

[Banana Pi M1+ Extra Configuration]

Thanks for the tip, that fixed the wifi on my BPI-M1+

On other boards (various H3 based OPIs) armbian supports the wifi straight away, so I'm wondering why you don't include this change in the image?

Anyway, congrats for your distribution, and for your support.

[Odroid C2 migrate from odrobian]

Thanks Igor,

 

I'll take the clean install path then, even if I had a slight hope for an easy migration trick.

And I'll use the opportunity to upgrade the server to an Odroid-HC1.

I read somewhere that you were running this forum on an Odroid-XU4.

Both sharing the same hardware, I believe you'll take special care of maintaining armbian for that platform :-)

I'll sure wait for the bugfixes, no emergency on my side…

 

Cheers !

[Odroid C2 migrate from odrobian]

Hi armbian team !

I've been running my Odroid C2 for almost 2 years with the only then available distro for my board : odrobian.

As that distro is now left without maintainer, I'm turning to other distros and am glad to see my board supported by armbian (which I currently use on various Orange Pi boards).

Is there a path to migrate my Odroid C2 installation from odrobian to armbian with minimum downtime ? (it's a server)

Or should I consider installing everything from scratch on another board and copy my configuration there ?

Thanks !