• Content Count

  • Joined

  • Last visited

About Superkoning

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @usual user Thank you for all your work and time and explanation! You have provided me with a working Armbian Ubuntu on my Cubox, so I'm happy. Thank you
  2. I swapped the two blocks in extlinux.conf, rebooted, did not press a key, after 10 seconds it boots through (10 seconds, not 100) and ... that booted to X / DE too. So both options seem to boot (assuming now the other boot options was choosen as default). Is that good news, or not? sander@cubox-i:~$ dmesg | grep Kernel [ 0.000000] Kernel command line: root=UUID=d0456b88-9549-4375-b5ce-5fdaa9d79e04 rootfstype=ext4 rootwait console=tty1 consoleblank=0 video=mxcfb0:dev=hdmi,1920x1080m60,if=RGB24,bpp=32 coherent_pool=2M cma=256M@2G rd.luks=0 rd.lvm=
  3. Results: On the first boot, I was too late pressing "2" (fetching my phone to make pictures), and the Cubox nicely booted through to X / DE. So there is a time-out and default option? On the second boot, I pressed 2 but nothing happened ... the keyboard is not working. Pressing Numlock does not light the LED on the keyboard. After the full boot, the keyboard is working again. So, is the USB port of the cubox not powered in the initial phase of booting ... ? (Only the keyboard is connected to USB, so no USB power problem I would say) Should I swa
  4. Yes, 15 minutes and a whole night, during the first tries. I also ping-ed to see if the cubox was network-reachable (to check if it was just a display problem) but no ping respons. Today a few minutes. Please note: your Ubuntu-plus-extlinux.conf was black for only 15 seconds or so. What do you advice to do? I don't see "boot.scr" in the extlinux.conf. (This is also proof that I really don't know the magic you've done ...) EDIT: we can also leave it this way as: - it works for me, - the few other Cubox i1 single-core Armbian users in
  5. Oh ... I now realize I post the dmesg as code (my usual method), not as an attachment (as you requested). Do you want me to change that for the existing posts?
  6. Summary: with your extlinux.conf added, I can boot Armbian Ubuntu deskop on my Cubox! Steps taken: Base / Recheck: Download the standard Armbian Ubuntu image Armbian_20.02.7_Cubox-i_bionic_current_5.4.28_desktop.7z, unpack, write to SD card, do NOT add the extlinux.conf, boot it... same behaviour: only the first splash screen, then nothing. So that confirms earlier behavior & my original post. SD card back into my (Ubuntu) laptop, and copy the file: sander@witte2004:~$ cd /media/sander/d0456b88-9549-4375-b5ce-5fdaa9d79e04 sander@witte2004:/med
  7. (Again: still on Fedora, which works) Hmmm, is this interesting? [ 3.494048] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [ 3.500678] [<c031127c>] (unwind_backtrace) from [<c030b744>] (show_stack+0x18/0x1c) [ 3.508524] [<c030b744>] (show_stack) from [<c0b85974>] (dump_stack+0xa8/0xc4) [ 3.515842] [<c0b85974>] (dump_stack) from [<c034d59c>] (__warn+0xdc/0xf8) [ 3.522807] [<c034d59c>] (__warn) from [<c034d94c>] (warn_slowpath_fmt+0x70/0x84) [ 3.530384] [<c034d94c>] (warn_slowpath_f
  8. I would prefer Ubuntu, so which links to $ ll Bionic_current_desktop -rw-rw-r-- 1 sander sander 661128023 Mär 28 18:21 Bionic_current_desktop $ file Bionic_current_desktop Bionic_current_desktop: 7-zip archive data, version 0.4 $ ll Bionic_current_desktop -rw-rw-r-- 1 sander sander 661128023 Mär 28 18:21 Bionic_current_desktop $ sha256sum Bionic_current_desktop 0b00ac659cda20516158180ba3d375850afe9b6c2b14bc83bcd9e174b2ca2e6
  9. dmesg from Fedora: [lxqt@trial ~]$ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.4.0-0.rc3.git0.1.fc31.armv7hl (root@micro-011) (gcc version 9.2.1 20190827 (Red Hat 9.2.1-1) (GCC)) #1 SMP Fri Oct 18 20:33:34 CEST 2019 [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: SolidRun Cubox-i Solo/DualLite [ 0.000000] Memory policy: Data cache writeback [ 0.000000] efi: Getting EFI parameters
  10. OK, unpacked, wrote to SD-card, boot from it ... bingo ... login-prompt ... root/trial, and I'm in. Typing is strange: no QWERTY but ... QWERTZ ... German? Anyway: your image works! So ... next step ... ? PS: non-related: when I login as kodi ... a nice KODI GUI starts up. Nice PS2: with a remote login a lxqt from my Ubuntu laptop, I have a normal QWERTY setup.
  11. Thanks for your offer. I indeed would prefer to have Armbian Ubuntu (instead of Solidrun Debian) running on the Cubox i1-300-D, and I can spend an hour or so on Fedora. Please note: trying all kinds of random parameters is not my thing.
  12. OK, then I'll stick to the Solidrun Debian on the Cubox i1. A pity, but at least Armbian Ubuntu is still running on my Nanopi NEO2. Thank you.
  13. Thank you for replying. So ... as the solidrun Debian images is running well, that is some kind of paradox, as Armbian (not booting through) uses Solidrun as a basis? Or is there still hope? Can I pick some setting from the running Solidrun Debian and copy it to Armbian Ubuntu? I'm just a Linux user, and I know nothing about DT / dtb. sander@cubox-debian:~$ ls -al /boot/ total 21840 drwxr-xr-x 3 root root 4096 Apr 3 11:06 . drwxr-xr-x 18 root root 4096 Feb 14 2019 .. -rw-r--r-- 1 root root 2881153 Sep 3 2019 -rw