That is good news!
Your development and insights on this is much, much appreciated!
That is good news!
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.
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.odroidn2user wrote: ↑Sat Feb 22, 2020 7:52 pmUpdated 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.
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 metobetter wrote: ↑Mon Feb 24, 2020 7:20 pm
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'll be .... It works!!
I did it with uSD Card.
Sorry, my mistake. Please test without SD card if blank screen or mmc -84 error happens.istanbulls wrote: ↑Tue Feb 25, 2020 7:45 pmI 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.
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.istanbulls wrote: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
Worked smoothly with the uSD-USB card reader.tobetter wrote: ↑Tue Feb 25, 2020 8:04 pmOh...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.istanbulls wrote: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
"Tapatalk wishes you to have fun with ODROID"
Maybe the last time you shutted down something went wrong and some files were corrupted.istanbulls wrote: ↑Tue Feb 25, 2020 8:42 pm
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?
Code: Select all
fsck /dev/sdb
Thanks for your help.Sav wrote: ↑Tue Feb 25, 2020 8:49 pmMaybe the last time you shutted down something went wrong and some files were corrupted.istanbulls wrote: ↑Tue Feb 25, 2020 8:42 pm
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?
If you have another pc with linux installed, you can check the file system runningassuming sdb is the uSD-USB card reader.Code: Select all
fsck /dev/sdb
I'm not completely sure about this but on the Manjaro site I think it states you must boot Manjaro on the N2 off the eMMc it is a known fault that it doesn't work with the uSD.odroidn2user wrote: ↑Wed Feb 26, 2020 4:31 pmStrange 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?
Yeah, the not-booting-from-SD issue is solved for Manjaro, it was a bad copy/paste basically, can now easily be fixed.
The repository is public but it won't work with the stock 18.04 image since the kernel package from my repository is not going to be installed into a FAT partition.
Are you meaning 19.04 or 20.04?I have other Intel machines running 18.10 awaiting 19.04 lts in April so was
wondering how stable non-Intel distributions are.
For the audio output, you need to activate it manually. Please visit the link for the instruction.I have been using N2 for browsing as it failed to do USB Audacity from vinyl test.
I have to rethink the single USB split on 4 USB 3.0 ports for DJ application.
There are two USB 2.0 Midi devices connected with hub as forth USB.
Other three are filled with 2.0 keyboard, wifi and BT.
I have untested USB 3.0-C external drive so watching for add on daughter card.
Am using audio jack now but Numark Party Mix has two additional stereo outs on Intel config.
One for DJ headphones and other for mains.
I use ssh -X to N2 display over eth0 to get a feel for target configuration (less Intel component).
I will experiment latency with N2 audio and slave Intel audio Mixxx app to Numark's 2 stereo outputs.
Here is Intel (not me) doing the deed...
[youtube] https://youtu.be/X9M4wI4t4PY [/youtube]
I was surprised that a N2 based media center can't do USB vinyl capture.
I tried netboot installer but without audio it was anti-climatic.
Code: Select all
;
; Ubuntu 19.04 (Disco Dingo) Installer
;
; Set as 'false' if you like to install manually from scratch.
di_auto=true
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; NOTE: the value below only affects when 'di_auto=true'. ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Uncomment one to use a installation profile
;
; 'minimal' -> Bare minimal Ubuntu server
; 'ubuntu-gnome-desktop' -> GNOME Desktop
;
;di_profile=minimal
di_profile=ubuntu-gnome-desktop
Code: Select all
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: G12AODROIDN2 [G12A-ODROIDN2], device 0: fe.dai-link-0 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: G12AODROIDN2 [G12A-ODROIDN2], device 1: fe.dai-link-1 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: G12AODROIDN2 [G12A-ODROIDN2], device 2: fe.dai-link-2 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
$
$ systemctl --user stop pulseaudio.socket && systemctl --user stop pulseaudio.service
$ pulseaudio -D
$ pacmd list-sinks
1 sink(s) available.
* index: 0
name: <auto_null>
driver: <module-null-sink.c>
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 1000
volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 344 KiB
max rewind: 344 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 2000.00 ms
module: 15
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"
$ pulseaudio -k
$ pacmd list-sinks
No PulseAudio daemon running, or not running as session daemon.
$ uname -a
Linux cooldroidn2 5.4.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.4.25-202003140746~disco (2020-03-13) aarch64 aarch64 aarch64 GNU/Linux
$
Well, on a fresh install, you should be able to execute the steps described by tobetter to configure the audio.
I am waiting for AUDIO to resolve on it's own in unmodified netboot installer.odroidn2user wrote: ↑Sun Mar 15, 2020 3:56 amWell, on a fresh install, you should be able to execute the steps described by tobetter to configure the audio.
Then reboot and audio should go. That is: audio over hdmi.
But then, I notice you are using a 202002 image, whereas previously I tested this on an 202001 image.
Perhaps tobetter changed something, perhaps the newer kernel/configuration works differently?
Tobetter probably could answer your questions, or perhaps you could download the 202001 image again.
I bought a usb audio card, which works on the Odroid N2... just not on the 202001 kernel from tobetter.CoolGames wrote: ↑Mon Mar 16, 2020 7:28 amI am waiting for AUDIO to resolve on it's own in unmodified netboot installer.
I am happy with 202002 without AUDIO more than stepping back to flashing 202001.
The objective is Desktop SBC which will run Ubuntu Studio for streaming real time music and video.
Yeah, it seems kde wayland not actually usuable, based on reports from others... Sadly.
Well, I wouldn't have expected me to say this, but I'm actually OK not having KDE Plasma. I found ubuntu gnome with some well tuned extensions works perfectly fine for me! Well, blimey! Who would've thunk, but the extensions really make things usable. You can create a normal layout, with taskbar at the bottom (dash to panel), start menu (arc menu), themes (arc), etc. Things look and feel a bit like how the Zorin OS is setup that way. I actually really like Gnome 3 setup like that. The 202001 image really works nicely set up like that, and also did a comparable configuration on a Raspberry Pi 4. Gnome 3 is surprisingly usable.tobetter wrote: ↑Sun Mar 15, 2020 9:35 pmSo what I decide is that I am switching to play with Ubuntu 20.04 which is coming in 1.5 months. I already have Ubuntu 20.04 version running on ODROID-N2, obviously, you guys can try at your own risk if you want. One major issue I found on ODROID-N2 is that the mouse cursor is invisible for Gnome desktop and the KDE screen is not properly working. I will look for a solution if this problem persists after March/19 when "User interface Freeze" according to the 20.04 release plan. Even if I am going to focus on Ubuntu 20.04, it won't stop supporting Linux 5.x kernel update for Debian 9/10 or Ubuntu 18.04/19.04, my build machine always keep building whenever change is made.
The glitch problem, I guess, kernel issue in my observation. I have not investigated it yet since I am looking at another chance Linux 4.9 which is not optimistic, unfortunately. For the audio issue, aren't you able to enable onboard HDMI audio put after applying a command in my previous post?odroidn2user wrote: ↑Mon Mar 30, 2020 8:49 pmTried the 19.04 202003 testing package, visual glitches still happening with all my hardware. Otherwise the Mali Wayland packages work right. The visual glitches thing happens with and without the Mali Wayland drivers. It seems to be a kernel issue. Perhaps some missing error handling or missing sync stuff or something like that. The 4.9 kernel series works right, but doesn't have the Mali Wayland packages. The onboard audio still not supported. Also, usb audio drivers still seem to be missing for externel audio devices, at least: mine wasn't supported.
What's the product of your audio device? I would be able to check if its driver is missing.odroidn2user wrote: ↑Tue Mar 31, 2020 12:42 amAs enthusiastic as I am over this device, its prospects and your working Mali Wayland image, it seem to just miss out in every use case I have in mind for it...Waiting patiently for things to improve. I'm thinking we got the Gnome and Wayland stuff mostly covered (??) but the kernel really needs to catch up on the visual glitching thing, the audio and the power management (and preferably the VPU).
For daily driver stuff the 4.9 kernel doesn't support my monitor (1400x1050) and the 5.4 does, but glitches and no audio jack. The HDMI audio is nice, but my monitor doesn't do audio, I need an audio jack connection there. And the 5.4 doesn't support my usb audio card. And even if that works, we still have the visual glitching thing.
For TV use, the the 4.9 has audio and video playing with Firefox and that is certainly good enough, but video files... not so much. And 5.x does Firefox AND video files (somewhat) AND HDMI audio, but then: visual glitches. CoreElec works, but can't surf with it. Need both.
So yeah... it narrowly and somewhat excruciatingly just manages to miss out on my use cases for the N2. But that's all a work in progress...
Still love the luxurious feeling of seeing the full, glorious Ubuntu Gnome on the Odroid N2. Only to change it all into something actually workable using theming and extensions, but still. The 2020 image really is wonderful.
Code: Select all
[ 6040.033317] usb 4-1: new full-speed USB device number 4 using ohci-platform
[ 6040.302477] usb 4-1: New USB device found, idVendor=1130, idProduct=1620, bcdDevice= 1.40
[ 6040.302509] usb 4-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 6040.302526] usb 4-1: Product: USB AUDIO
[ 6040.343469] usb 4-1: Warning! Unlikely big volume range (=17152), cval->res is probably wrong.
[ 6040.343494] usb 4-1: [2] FU [PCM Playback Volume] ch = 2, val = 0/17152/1
[ 6040.348542] input: USB AUDIO as /devices/platform/fe3e0000.usb/usb4/4-1/4-1:1.2/0003:1130:1620.000B/input/input17
[ 6040.424130] hid-generic 0003:1130:1620.000B: input,hidraw2: USB HID v1.10 Device [USB AUDIO ] on usb-fe3e0000.usb-1/input2
Code: Select all
[ 6125.559403] usb 4-1: USB disconnect, device number 4
[ 6140.663401] usb 4-1: new full-speed USB device number 5 using ohci-platform
[ 6140.937685] usb 4-1: New USB device found, idVendor=08bb, idProduct=2902, bcdDevice= 1.00
[ 6140.937718] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6140.937736] usb 4-1: Product: USB Audio CODEC
[ 6140.937752] usb 4-1: Manufacturer: Burr-Brown from TI
[ 6141.039936] input: Burr-Brown from TI USB Audio CODEC as /devices/platform/fe3e0000.usb/usb4/4-1/4-1:1.3/0003:08BB:2902.000C/input/input18
[ 6141.104108] hid-generic 0003:08BB:2902.000C: input,hidraw2: USB HID v1.00 Device [Burr-Brown from TI USB Audio CODEC ] on usb-fe3e0000.usb-1/input3
Code: Select all
[ 57.612223] usb 1-1.4: new full-speed USB device number 4 using xhci-hcd
[ 57.814724] input: Burr-Brown from TI USB Audio CODEC as /devices/platform/soc/ffe09000.usb/ff500000.usb/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.3/0003:08BB:2902.0004/input/input6
[ 57.873688] hid-generic 0003:08BB:2902.0004: input: USB HID v1.00 Device [Burr-Brown from TI USB Audio CODEC ] on usb-xhci-hcd.0.auto-1.4/input3
Code: Select all
[ 216.583751] usb 1-1.4: new full-speed USB device number 5 using xhci-hcd
[ 216.757715] input: USB AUDIO as /devices/platform/soc/ffe09000.usb/ff500000.usb/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.2/0003:1130:1620.0005/input/input7
[ 216.817221] hid-generic 0003:1130:1620.0005: input: USB HID v1.10 Device [USB AUDIO ] on usb-xhci-hcd.0.auto-1.4/input2
Code: Select all
$ uname -a
Linux ubuntu 5.4.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.4.28-202003312239~disco (2020-03-31) aarch64 aarch64 aarch64 GNU/Linux
Code: Select all
$ sudo addgroup tobetter audio
I was already in the audio groups because of the commands to get the audio over hdmi working.
Interesting...tobetter wrote: ↑Mon Mar 30, 2020 9:19 pmThe glitch problem, I guess, kernel issue in my observation. I have not investigated it yet since I am looking at another chance Linux 4.9 which is not optimistic, unfortunately. For the audio issue, aren't you able to enable onboard HDMI audio put after applying a command in my previous post?
In addition, I've found 5.6 kernel is out and I've just applied the bare minimal patches and it boots up. But still has to apply more patches from 5.4.
Yeah, but Manjaro does KDE Plasma on Xorg and tobetter has Ubuntu Gnome. Both have the glitching.
Yeah, that's my thinking as well, the kernel thing. But then Armbian didn't have the glitching... Which was surprising.tobetter wrote: ↑Fri Apr 03, 2020 5:03 amI am still suspecting that the glitch problem happens in the kernel and it happens more frequently when the bunch of a small part of the screen is updating. Still not found the best way to debugging. I've observed a similar glitch issue even from a minimal image. Still not figure out the best way to debug it. KDE on the Wayland is a bit worse, I guess it's not solely KDE problem. I've purchased HDMI screen grabbing device which is coming in a couple of days, I hope I can share more clearly what's what.
If it isn't too much of a hassle on your part, I'd love to have a play around with it. And it seems I have some time on my hands soon...
I just installed ubuntu-desktop on Armbian. I got 3.28.2 64bit.
I don't have a patch for Gnome desktop packages at all. I've not tested the Armbian image but curious if they use Wayland+DRM.odroidn2user wrote: ↑Fri Apr 03, 2020 6:45 amI just installed ubuntu-desktop on Armbian. I got 3.28.2 64bit.
Works, without glitching. So, I\m guessing it isn't the window manager.
Well, not outright.
Not sure what exactly was patched to get Gnome working with Wayland on tobetter's image, but normal gnome doesn't glitch on Armbian's 4.5 kernel.
And given that the glitching isn't Mali-Wayland-patched-Gnome specific, I'm thinking it isn't the window manager.
pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer/pxeboot/ODROID-N2/default
in the Petitboot shell.No wayland there. Not sure how to detect DRM, I'm guessing that is default. But yeah, no wayland with the drm.
So, I have an interesting morning.tobetter wrote: ↑Fri Apr 03, 2020 7:46 amIf you have the Petitboot 20200224, the Petitboot will load Ubuntu 20.04 Netboot Installer using PXE, but you have to manually run the commandpb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer/pxeboot/ODROID-N2/default
in the Petitboot shell.
viewtopic.php?f=182&t=33873#p282985
Hmmm....what was the Petitboot version worked for you?odroidn2user wrote: ↑Fri Apr 03, 2020 4:32 pmNo wayland there. Not sure how to detect DRM, I'm guessing that is default. But yeah, no wayland with the drm.
So, I have an interesting morning.tobetter wrote: ↑Fri Apr 03, 2020 7:46 amIf you have the Petitboot 20200224, the Petitboot will load Ubuntu 20.04 Netboot Installer using PXE, but you have to manually run the commandpb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer/pxeboot/ODROID-N2/default
in the Petitboot shell.
viewtopic.php?f=182&t=33873#p282985
The Odroid with Armbian on SD (a Lexar) boots, but refuses to log in. Just shows a mouse cursor. Either with the Ubuntu Gnome or with XFCE. Tried it a couple of times, no luck. Worked fine yesterday when I shut it down.
So, back to the RockPro64, with Manjaro ARM on a Samsung T5 SSD, which boots over USB3, has Panfrost. A nice setup.
Also doesn't boot, like completely not. Worked fine when yesterday when I shut it down.
Well, I still have the tobetter ubuntu image going on the Odroid. Plug back in the eMMC. It boots.
I update to the 20200224 petitboot as linked. Now the SPI refuses to boot.
The update when correct, it erased, flashed and verified. But then... nothing.
The new petitboot doesn't AT ALL support my HDTV-monitor.
I tried another monitor (a new Dell), it shows the logo, gives a couple of error messages then, black screen nothing.
I grab my camera, reboot petitboot for a little photo show. The camera gives a long pause and a big flash, the text on screen was by then long gone. Switch off the flash, try again.
Only shows the HK-logo, doesn't even bother with the error messages any more.
So, yeah. Not all that excited abou tthe 20200224 petitboot.
And pretty annoyed with the completely unpredictable and unreliable behaviour of theseARM devices.
HAve to go find a working computer now, to download the older petitboot and try to get the Odroid going again.
Then have to find out what is wrong the RockPro. Both are now useless for trying to download and install the petitboot again.
The Petitboot image 201911 what you mean by must be 20191127 that hits most downloaded so far.odroidn2user wrote: ↑Fri Apr 03, 2020 5:14 pmthe 201911 was working for me.
The link to the petitboot of 201911 is listed on the opening post, but links to a random post not anywhere near 201911.
It should be:
viewtopic.php?f=182&t=33873&start=500#p273785
I've tried loading it using the normal spitboot on SD card routine. That didn't take.
I managed (somehow, not sure) to boot the tobetter ubuntu image. Any way I could flash the spi from the console?
Ah, and thanks for making the tobetter ubuntu 2020 image bootable without spi/petitboot.
Yeah, I tried that, but strange enough the spiboot.img on the SD cardwas ignored. I now read that I should remove the eMMC. So, will give that a try later today.tobetter wrote: ↑Fri Apr 03, 2020 6:40 pmThe Petitboot image 201911 what you mean by must be 20191127 that hits most downloaded so far.
In order to overwrite the SPI flash memory, please flash the recovery image from the link and put the version you have as 'spiboot.img'. The boot select switch must be placed to 'MMC' when power on.
https://wiki.odroid.com/odroid-n2/os_im ... ev20190417
Since the Petitboot is not working, I would prepare an installer. Even you can try to upgrade your Disco to Focal after updating the file in /etc/apt/* but...well...I've failed a couple of times the packages are not reliable.
Users browsing this forum: No registered users and 2 guests