Debian/Ubuntu Netboot Installer

[odroidn2user]

Just for the quick update, I managed to install Ubuntu 20.04 from the development branch and could run Mali driver

That is good news!
Your development and insights on this is much, much appreciated!

[tobetter]

Thanks, maybe I would spend sometime soon to enable audio since I am able to see some patches from LibreElec and Batocera that enables it. I would gather the patches and put them together...

"Tapatalk wishes you to have fun with ODROID"

[odroidn2user]

enable audio since I am able to see some patches from LibreElec and Batocera that enables it. I would gather the patches and put them together...

It would be awesome if you could pull those patches in indeed, it seems to be a big issue currently with mainline and I don't see many kernels/images getting the audio working on mainline.
That would put your work-in-progress image quite a bit ahead of everyone else! (Obviously, you getting Wayland going on the G52 does as well!)

And also, that screenshot shows the demo running OpenGL ES 3.2! Nice!! That's pretty awesome indeed.
20.04 Focal Fossa (with the 19.10 Eoan Ermine wallpaper), all cores are going, the full 4 GB of memory is available, ethernet is clearly working, you got some (zram?) swap going! (I never understand why some images turn all swap off)...
And do I even see an OpenGL accelerated QT libs there as well? Cool! (That might be, perhaps, why SDDM isn't working right yet?)

Good work tobetter!

[odroidn2user]

So, at Manjaro.org they are also working at a hardware accelerated image for non-Bifrost devices, so using the Lima and Panfrost drivers, and also using OpenGL ES 2.0 with QT.
Perhaps it is of interest to read their status update on that here:
https://forum.manjaro.org/t/status-of-o ... ima/113591
and
https://forum.manjaro.org/t/how-to-enab ... ces/114885

They experience that a couple of apps refuse to work, among which (surprisingly so) is the Plasma desktop when using the Lima driver.
Just as a fyi to developers: I'd be more than happy to use an Odroid N2 accelerated image knowing some apps won't work!

[odroidn2user]

Updated to the latest 5.4.21 202002220108 kernel build.
No sound still, but also.... No visual glitches!
The update seems to have completely solved the visual flashes/glitches I had earlier!
So yet another step forward! Many thanks.

Oh, yeah, the missing window decoration around MPV in Wayland appears to be 'as designed', and this is accepted as-is ever since first diagnosed in 2016.
Apparently, the MPV app calls for some type of window decorations, which Wayland doesn't support.
So, neither gnome nor mpv feels obliged to solve that little issue. And wayland apparently is being wayland. So: No window decoration.
It appears that video players that fully support Wayland are few and far between.
More here: https://github.com/mpv-player/mpv/issues/3646

So, yeah.... nice...
People suggest using an XWayland backend/renderer in MPV, and setting a config file for using that as default.
Not yet gotten that to work though and not sure how that supports hardware acceleration if that is made to work.

[tobetter]

Updated to the latest 5.4.21 202002220108 kernel build.
No sound still, but also.... No visual glitches!
The update seems to have completely solved the visual flashes/glitches I had earlier!
So yet another step forward! Many thanks.

Oh, yeah, the missing window decoration around MPV in Wayland appears to be 'as designed', and this is accepted as-is ever since first diagnosed in 2016.
Apparently, the MPV app calls for some type of window decorations, which Wayland doesn't support.
So, neither gnome nor mpv feels obliged to solve that little issue. And wayland apparently is being wayland. So: No window decoration.
It appears that video players that fully support Wayland are few and far between.
More here: https://github.com/mpv-player/mpv/issues/3646

So, yeah.... nice...
People suggest using an XWayland backend/renderer in MPV, and setting a config file for using that as default.
Not yet gotten that to work though and not sure how that supports hardware acceleration if that is made to work.

A workmate of mine made a change on top of 5.4 kernel and many upstream patches and have tested the audio still not 100% stable but works.
Can you please do these commands in the terminal?

Code: Select all

sudo addgroup $USER audio
sudo addgroup $USER pulse
sudo -s
amixer sset 'FRDDR_A SINK 1 SEL' 'OUT 1'
amixer sset 'FRDDR_A SRC 1 EN' 'on'
amixer sset 'TDMOUT_B SRC SEL' 'IN 0'
amixer sset 'TOHDMITX I2S SRC' 'I2S B'
amixer sset 'TOHDMITX' 'on'

amixer sset 'FRDDR_B SINK 1 SEL' 'OUT 2'
amixer sset 'FRDDR_B SRC 1 EN' 'on'
amixer sset 'TDMOUT_C SRC SEL' 'IN 1'
amixer sset 'TOACODEC I2S SRC' 'I2S C'
amixer sset 'TOACODEC I2S OUT EN' 'on'
amixer sset 'TOACODEC Lane Select' '0'
amixer sset 'ACODEC' '255'

alsactl store
reboot

[istanbulls]

A workmate of mine made a change on top of 5.4 kernel and many upstream patches and have tested the audio still not 100% stable but works.
Can you please do these commands in the terminal?

Code: Select all

sudo addgroup $USER audio
sudo addgroup $USER pulse
sudo -s
amixer sset 'FRDDR_A SINK 1 SEL' 'OUT 1'
amixer sset 'FRDDR_A SRC 1 EN' 'on'
amixer sset 'TDMOUT_B SRC SEL' 'IN 0'
amixer sset 'TOHDMITX I2S SRC' 'I2S B'
amixer sset 'TOHDMITX' 'on'

amixer sset 'FRDDR_B SINK 1 SEL' 'OUT 2'
amixer sset 'FRDDR_B SRC 1 EN' 'on'
amixer sset 'TDMOUT_C SRC SEL' 'IN 1'
amixer sset 'TOACODEC I2S SRC' 'I2S C'
amixer sset 'TOACODEC I2S OUT EN' 'on'
amixer sset 'TOACODEC Lane Select' '0'
amixer sset 'ACODEC' '255'

alsactl store
reboot

I tried, the sound works for me

[odroidn2user]

A workmate of mine made a change on top of 5.4 kernel and many upstream patches and have tested the audio still not 100% stable but works.
Can you please do these commands in the terminal?

I'll be .... It works!!
The HDMI output, outputs actual audio.
I like it, I like it a lot. Perhaps I even like it a little too much.

Strange enough, I now get two options in Gnome:
- Multichannel Output - Built-in Audio
- Analog Output - Built-in Audio

Both of which direct audio to the connected HDMI.
Neither of which goes to the headphone jack.
And Multichannel Output about double the volume of Analog Output

Did I see the audio output is mono? Update: nope, is stereo.

Unrelated: The headphone jack gives quite a bit of static/buzzing.
Not sure what that is about. That as a side note.

Hmm... The visual glitches thing appears not completely solved.
Could that be a wonky HDMI cable? Update: I don't think it is.
Anyone else have those flashes / glitches?

Gnome Video actually works quite nice, for playing video.

[istanbulls]

I don't use headphones, N2 AVR is connected to the system.
Multi-channel output, mono

[istanbulls]

Petitboot versions: 20200224

It stays on the black screen with the uSD slot.
Worked smoothly with USB adapter. I made updates and adjustments, I made it 5-6 times close-open. It was working without any problems.
It does not open today
Everything is the same, I did not change. I slept and woke up, only the position of the sun changed. But it does not open today.

The same problem happened the day before and it did not open. Is it a coincidence that after making the sound patch?
I did a new installation all night and I have the same problem.
Also, I made more than one close-open after the patch of sound.


The screen looks like this when opening for the first time.

WhatsApp Image 2020-02-25 at 11.53.08.jpeg (211.35 KiB) Viewed 299 times

This is the next screenshot. This image remains stable for about 30 seconds.

WhatsApp Image 2020-02-25 at 11.53.08 (1).jpeg (122.75 KiB) Viewed 299 times

This last image continues to fail this way.

WhatsApp Image 2020-02-25 at 11.53.08 (2).jpeg (315.38 KiB) Viewed 299 times

[tobetter]

@istanbulls, I think I also encountered a similar issue when SD card is attached. Would you be able to test with SD card?

[istanbulls]

@istanbulls, I think I also encountered a similar issue when SD card is attached. Would you be able to test with SD card?

I did it with uSD Card.
The uSD slot has a black screen and never turns on.
It turns on with the USB adapter, but now it makes mistakes.

[tobetter]

@istanbulls, I think I also encountered a similar issue when SD card is attached. Would you be able to test with SD card?

I did it with uSD Card.
The uSD slot has a black screen and never turns on.
It turns on with the USB adapter, but now it makes mistakes.

Sorry, my mistake. Please test without SD card if blank screen or mmc -84 error happens.

[istanbulls]

I have one eMMC and I use it for android.
If it doesn't work with uSD, I don't think of trying it.

Thank you <3

[tobetter]

I have one eMMC and I use it for android.
If it doesn't work with uSD, I don't think of trying it.

Thank you <3

Oh...then maybe you can try attaching SD to USB card reader if the error comes from SD or a file system. If you do not have any issue with SD-USB card reader, I believe it's the kernel problem to fix.

"Tapatalk wishes you to have fun with ODROID"

[istanbulls]

I have one eMMC and I use it for android.
If it doesn't work with uSD, I don't think of trying it.

Thank you <3

Oh...then maybe you can try attaching SD to USB card reader if the error comes from SD or a file system. If you do not have any issue with SD-USB card reader, I believe it's the kernel problem to fix.

"Tapatalk wishes you to have fun with ODROID"

Worked smoothly with the uSD-USB card reader.
Last night, I restarted 6-7 times until morning, no problem.
I had these problems when I opened it again today.
How can I edit the core issues that need to be edited, do you have any ideas? Is there anything instructive?

[Sav]

Worked smoothly with the uSD-USB card reader.
Last night, I restarted 6-7 times until morning, no problem.
I had these problems when I opened it again today.
How can I edit the core issues that need to be edited, do you have any ideas? Is there anything instructive?

Maybe the last time you shutted down something went wrong and some files were corrupted.
If you have another pc with linux installed, you can check the file system running

Code: Select all

fsck /dev/sdb

assuming sdb is the uSD-USB card reader.

[istanbulls]

Worked smoothly with the uSD-USB card reader.
Last night, I restarted 6-7 times until morning, no problem.
I had these problems when I opened it again today.
How can I edit the core issues that need to be edited, do you have any ideas? Is there anything instructive?

Maybe the last time you shutted down something went wrong and some files were corrupted.
If you have another pc with linux installed, you can check the file system running

Code: Select all

fsck /dev/sdb

assuming sdb is the uSD-USB card reader.

Thanks for your help.
I made a new clean installation.

[odroidn2user]

Strange enough my install also doesn't want to boot anymore.
Probably just a weird coincidence, switching between the Ubuntu 19.04 with 5.4 on eMMC and Manjaro on SD.
And that is not something that the Odroid N2 does gladly. It somehow seems to only work if I have the N2 off the power for a while.

Last action was, I installed Dash to Panel on Ubuntu, somehow got a crash, and it didn't want to go again after.
I remember getting a comparable result earlier not long after installing dash to panel. Might be something to test?