Igor

Two things are important here: 1. You need to set edid=0 2. When you save u-boot environment, you need to issue reset to boot u-boot into new setting. Works for me.

Months ago, my primary testing tool become old 19" VGA Philips monitor with 1280x1024 and where I (must) use those converters. I have two different (possible the same?) and both working fine on everything I throw at them. So far I haven't found a glitch, while it's possible that exists at certain converters.

This way it works with 720p or whatever less than 1080p. There kernel logo doesn't want to show. Good on 1280x1024 or 720p Broken on 1080p: Relevant patch (without 320x200 bitmap.): I can't see what I did wrong.

https://github.com/igorpecovnik/lib/commit/0b7676e527350d8cd454eb638869179d80c23c4c Working at i2ex and v2 Thanks for the hint @zador.blood.stained Log: http://sprunge.us/BhLJ This is filling logs on HB2, have to solve once:

BT is USB, Wifi pci, ok. Can you provide full logs, preferable: armbianmonitor -u Thanks.

OMG. I think I'll just burn this board With actual fire.

That's connected VIA USB port. Just type lsusb ... Regarding MSI perhaps @rabeeh can explain more?

AFAIK HB does not support Message signaled Interrupts. I'll try to add this the rest to next update.

I just (again) wasted two hours to remember that any of those kernels needs a lot of code cleaning and fixing than "just" USB3. When this is done, than it would be possible to start debugging without wasting hours / days. About year ago I was approached by Allo, when they were trying to design their own board around S500 (Sparky). They were talking about mainlining (wishes) or bringing things at least to kernel 4.4, but I guess they abandon the idea due to whatever reason. There was lots of discussion going on and after my second reminder, that they need to hire and pay for my time, if they want me involved into their activities, I tuned myself out. They didn't listen what I was trying to tell them anyway.

If you were editing settings while transmission was running it's normal, than it doesn't work.

You said settings are not saved ... one thing is with transmission - you have to disable daemon when you edit config file otherwise changes are not saved. If low level things are working fine, than this is a general issue.

I have no idea what can be wrong. You can try to force video mode in u-boot, perhaps some other than detected one. That's about all what I can come up. It's a bit tricky but doable also without serial console: https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output

Did you enable this ttyS2 in board configuration? Which board do you use and which kernel do you use?

It happened to me few times but it worked after soft reboot.

It looks like one of the most common problems. Bad SD card. https://docs.armbian.com/User-Guide_Getting-Started/

Yes. Mainline kernel is still in development and come without end user support. Currently there are problems with screen detection / video driver. It used to work fine, but currently it's just broken ... dunno why exactly, but AFAIK @jernej is working on this. "tomorrow" this will be fixed and some other problem might jump out but we are getting close. For certain scenarios is o.k. for some time. Even with fixed video, there are other limitations on new kernel - no video or 3D acceleration.

yes, use our legacy xenial desktop build. https://forum.armbian.com/index.php?/topic/2218-cubietruck-multimedia-youtube/#comment-16773

On quick comparison there are few minor differences - LEDs are wired differently, eMMC section is useless but generally it should work with MiQi dtb. Have you try? If it works, we only need to create a patch to create this file. Put our tools into "create patches" and when prompted, create a rk3288-miniarm.dts file with adjusted LED gpio and removed eMMC. Than push resulted patch (when tested) to patches/kernel/rockchip-dev

https://forum.armbian.com/index.php?/search/&q=dkms

We can't reproduce since @sadegh forgot to provide on exact which image this happened. Is this result in hanging the board or just this message pops out to the console?

Not necessarily. Most of those bench marking methods are wrong / pointless in first place. This way is more realistic, and as you can see, there is something wrong with USB3 stack ...

Delete. It was not done properly. I just update two videos of compilation process. Take a look how it should look like.

Disabled.

This beta repository does not have archive. It's populated only with latest versions / rebuild every night and therefore you need to issue apt update right before upgrading. This will rebuild packages index and you will be able to issue upgrade.

If resolution remain unchanged, there is a possibility that your system is corrupted / read only due to failed SD card.