zamar19

Hi guys, I downloaded and burned to SDCard the last nightly image Armbian_5.58.180812_Orangepipc_Ubuntu_bionic_next_4.17.14 for OrangePI PC. Added desktop with apps, and it boots to desktop upon login. How to boot straight to desktop, without login and typing startx? I have 4K HDMI display, so must run development images, since stable don't support 4K as I was explained here earlier. The display has 2 main resolutions: 4K and 1080P. But in Armbian Display settings, choosing 4K gives full screen image, and choosing 1080P results in only a portion of display area used by the system. How I can activate in Armbian the 2nd main display resolution 1080P, so the desktop would occupy the entire screen with lower CPU & GPU load than 4K?

Can someone write a How-to on this?

Here's sudo armbianmonitor -u output. Link to it was present in the 1st post, but somehow auto deleted on its edit:

I'm not asking for out-of-the-box solution, but merely look for a workaround, and besides all smarty non-working drivers there're pretty straightforward "hard-coded" solutions, which can be suggested by more experienced users. Yet NONE is suggested so far. Btw, running LXQT desktop correctly identifies all available resolutions from 4K monitor EDID. So my guess is, uBoot driver tries to run 1st default 4K reso instead of set in extraargs 1080P, and fails to do it, especially without Mali support. Yet hard coding reso works on Ubuntu desktop with legacy kernel. I assume, uBoot graphics driver in Debian package is different from OS graphics driver? These commands fail, but seems forwarded to the kernel, as changing them alters boot results, so may be its syntax error? extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin,video=HDMI-A-1:1920x1080-24@60 extraargs="drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080-24@60" For now I hooked HDMI 2-port switch to the OPI PC. Once the device reads EDID from 1080P monitor, I flip the switch to the 4K monitor and it shows normal 1080P pic. Will see, may be editing default 1080P EDID file will bring more light, unless someone suggests something on-topic. I got both monitors EDIDs with get-edid and copied to the EDID folder, then references in armbianEnv.txt . They both have 256K size, while the Debian package EDIDs are 128K in size. May be shrinking the file size by deleting EDID extensions info would do the trick? What webUI admin tool is a good match for OPI on Debian? Webmin sounds a bit heavy, if still in the Debian repo.

I tried to follow advice from this post, but it didn't work: add line in /boot/armbianEnv.txt : extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080-24@60 I also tried to add similar line in boot.cmd and recompile, and it failed to boot: setenv extraargs "drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080-24@60" I assume the generic 1920x1080.bin from the distro can be used instead of my monitor edid.bin? The reason is I've a 4K monitor, so not sure if Linux driver will read or execute info from its EDID properly even if manually added to the EDID folder. Also the question: should a full path to the EDID folder be given in extraargs, or its known to the system? Do you guys ever answer questions, or its a monologues forums? I realize many have similar issues with monitor EDID - but no solution works for different monitors or OS release the same way, and the Wiki docs are grossly obsolete. I also suspect it may be a code syntax issue.

Tried to boot on another 1080P monitor - and the same OS booted OK. So it looks like uBoot can't read EDID from the 1st monitor. The question is: what are other ways to set monitor resolution apart from reading it from EDID? Can it be directly permanently set in uBoot? Is fw_setenv command supported in Debian Stretch in write mode? Tried fw_printenv, and got "Environment does not start on (erase) block boundary", which results in Read Only access to env from SSH console. Is that the latest uBoot? It seems that error was fixed in Aug 2016, not sure though if its the same uBoot line. Can we enable Netconsole in this uBoot, and how?

I've a problem with latest Armbian Debian Server stretch (ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi, Uboot loader 2017.11) on OrangePI One, and OrangePI PC. It boots seemingly OK, but without any output to 1080P HDMI monitor. So I've no video. But Ubuntu Desktop with Legacy kernel boots fine using the same SDCard (and same power supply ). I can SSH to the Debian after boot, here's the boot and diag log. Couldn't wait for senseless SDCard testing to finish, as it works perfect with Armbian Ubuntu Desktop version. Legacy version on 1st boot shown boot progress and defaulted to 720P resolution, which I changed later to 1080P. But Debian Server doesn't show ANY output on the same monitor during boot and after. I understand, there may be a problem with querying EDID - but how I can fix it? It can be a wrong color scheme too, like 1 instead of 0. Both OS versions are downloaded from *official* Armbian page links, tested upon burn to SDCard, and SHA256 matched to control files. I tried 2 different SDCards, and 2 Debian versions - OrangePI One and PC - the same thing: no HDMI output.

Can you make a similar tutorial for multiboot with making a separate partition for each distro on your sd card and use it to store the rootfs and other distro files? Also better explain, how to prepare multiboot sdcard for other ARM devices - what would be different as an example for Orange PI, and where to get these different files from?

Great effort! Can you try using BerryBoot ARM Bootloader instead to simplify multiboot for novices?

I was talking about this model, its unregulated, but I don't think it drops to 5V under OPI standalone load. Any simple way to find it out? I'm concerned about PC Monitor impact due to HDMI overvoltage. I assume your application requires passing up to 5A current through OPI. Would such current damage tiny power components of the device? I think, even powering an external 3.5' USB HDD is a bad idea due to high starting current. I found a few interesting power supply options for OPI allowing to use 12V CCTV or laptop adapters: 12V-to-5V 3A adjustable DC-DC Converter 12V-to-5V 3A Double USB Step Down Module On a relevant note, is it a good idea to use a USB powered hub with the device to connect multiple peripherals? I mean, if connecting a USB webcam, sound card, and Uno board to the same USB port on OPI One, they likely to limit each others signal bandwidth or otherwise interfere.

There're some cheap 5V 3A "LED Strip" power adapters sold on Aliexpress. They measure 6V at idle, but voltage may drop some at load. Can it damage OPI using such an adapter - what components? And if the power port is damaged, would it still be possible to power OPI through the PIN Header as you did? And if 6V is supplied directly via USB and HDMI power pins, can it also damage USB Thumbs and PC Monitor HDMI ports & main board?

Does Armbian currently have Microsoft Wireless Keyboard & Mouse support? If not, can you guys add it? Its not included in loboris's distro images I tried, unless you can point to one where its included.

My best guess is, Steven might have paid loboris ones to prepair a series of working images for OPI line. I do support your notion about paying dues to Armbian team as well, and possibly other distro authors, but success chance may jump a little if you address it directly to Steven Zhao, who seems to be "everything" man in this small company. He didn't seem to reference Armbian on their website.

Can you be more specific what "inherent potential" will be unleashed with 4.x? Also, I was under impression, vanilla 4.5 kernel thus far has minimal device driver support if any. Am I wrong?

@Igor Can you explain your "methodical approach"? What are its priorities?