2.414 on old kernel boots, still crashes when doing a library update.
2.417 on new kernel just does not boot. The solid run boot sequence comes up, flashes text like it would boot, then just goes blank.
works fine here on a cuboxi2ex, what are you using?
Are you able to connect a serial console to a PC and send me the output of the boot process?
cubox-i4
sure. pm me
Same here. Old Kernel works fine, the new one doesnāt boot. Cuboy i4pro.
Gladfully I never had any crashes while scanning my library.
Andreas
Booting OK on my Cubox-i 2ultra.
yes, it has been confirmed from a log, that uboot does not identify the hardware model correctly.
The kernel is OK, Iām working on it but it may take a while as this is the part Iām not very familiar with.
Could someone try the following bypass?
What needs to be done is renaming 2 dtb files, this can be done on a PC.
The files are in the boot partition, the visible part of the SD on a PC.
- rename āimx6q-cubox-i.dtbā to āimx6q-cubox-i.dtb.orgā
- rename āimx6dl-cubox-i.dtbā to āimx6q-cubox-i.dtbā
Then make sure you eject the SD from the PC before removing it.
Reboot and report back please.
tried this,
also renamed the files in the dtb folder you had me create as well, still same results, I emailed you the new log. right now I am flashing my sd card with a known working image and going to serial console boot that and compare results.
Ok, the kernel for i2 and i4 should be the same, which makes me believe there is an issue with u-boot.
Cubox i2 and Cubox i4 are using the same dtb, perhaps u-boot is not initializing the boards properly.
As we must be close (i2 works really well), I will take some time for this.
But there is only so much I can do, so please do not expect too much.
I donāt have the hardware to test, so a lot of it is guess workā¦
I donāt wanna jump the gun here, but I think gkkpch has nailed it! He made me a custom image that finally booted on the newer 4.14 kernel on my cubox-I 4 pro. I added 2 smaller portions of my library that have always worked, they seemed to load faster than previous builds, even the UI seems to respond MUCH smoother and faster, and as I am typing this I am adding the HUGE portion of my library to it and it has surpassed all previous builds already, I am about 10,000 tracks in, it has NEVER made it that far before!
and the update to my previous post is IT FINISHED, 22,289 tracks, 1,474 artists and 3,257 albums! It has NEVER EVER EVER made it even remotely close to finishing my library before! gkkpch!!! You nailed it!
@thederk123: Thanks for taking the effort to test my images.
Thanks also to the Armbian Team, whoās kernel and u-boot sources I used to build @thederk123ās test image.
I will try to pack things up (and document my work) this weekend and build an official image with Armbianās kernel.
So gladā¦
I tested it all night, let it play for hours, no problems, ran like a charm! I had one crash when i was switching from DSD Direct to DSD over PCM but that only happened once! I am extremely happy, as i believe everyone who has a cubox-i 4 will be with this build. Now you should have a stable platform to build from in the future @gkkpch!
[spoiler]ok, so there is a problem, I was testing last night at low volumes as it was late. Tested when I got home today after work at regular and louder volumes and there is what sounds like over amplification, my center speaker is popping.[/spoiler]
EDIT: DISREGARD, it was a particular set of FLAC files, tested with other players, SAME results.
ok, this needs to be looked at as a separate issue.
Over amplification is not much I can do with thoughā¦
Will try this as my test environment.
cubox i2ex SPDIF -> SMSL DAC -> RCA output -> amplifier
it was actually fixed when I played it in Roon, I had to enable the track volume leveling from album. I donāt remember having that problem with volumio before, there is an option for that isnāt there? for it to adjust with replaygain info from album/track?
Is anyone testing using a low latency (125uS) USB sound card to see if there are any glitches/dropouts ?
I havenāt had a chance to test yet but Iām downloading the latest test image now.
I never had the problems others were reporting with freezes with large libraries - about the only issue I had with the previous versions was that after a high uptime the web UI would sometimes get quite sluggish and require a reboot.
Edit: just noticed a problem with the old version with the older kernel that I have been using for a while.
It will not boot past u-boot with a TV connected to the HDMI port! It always hangs. However if I leave the TV disconnected until after u-boot is finished and the kernel starts booting I get a picture and it boots normally. As I normally run it headless I had not noticed this beforeā¦
Successfully installed the latest build with the 4.15.18 kernel.
Iāve only tested it for about 15 minutes before I lost control of the living room 
but so far first impressions are good. 
USB audio playback on my Behringer UMC204HD seems clean - I tested with a 20Hz sinewave sent via airplay listening for any ācrackleā caused by sample dropouts - I didnāt hear any over a 2 minute period. Playback on music sounds normal over airplay, mpd from library files and spotifyconnect2.
Library scan completed without any problems - although I only have 2883 songs in my library, probably small compared to some people.
Web UI seems snappy at the moment, but Iāll see how it is after it has a few days uptime on it as it only used to slow down after a while before.
The issue with difficulty booting with HDMI connected in 3.x is still there - I always see the solidrun u-boot loader screen but often the screen goes black and fails to boot after that - but only when HDMI is connected. With HDMI disconnected it boots every time.
I have a vague recollection that we had the same problem with OSMC kernels and had to patch a bug in the hdmitx code in the kernel to fix it, and those fixes are not up-streamed.
Since volumio is designed to be headless the workaround is simple - donāt connect an HDMI device unless you are debugging! (Connecting it part way through boot up seems to work ok)
Will hopefully get more time to test tomorrow.
Sorry, the latest version is not based on 4.15.x anymore, it needed to be be reversed to kernel 4.14.y LTS. then this works.
I have not been able to get any feedback on a dev version yet, but this would be identical to http://updates.volumio.org/cuboxi/volumio/2.425/volumio-2.425-2018-07-20-cuboxi.img.zip
Ah OK. I used the latest link on the original post assuming that was the latest build to test.
I will download this version and try it. I donāt quite follow what you are saying - are you saying that 4.14 fixes the issue with it sometimes failing to boot with HDMI connected ?