archetech

Members
  • Content Count

    6
  • Joined

  • Last visited

About archetech

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Hey suber. I just installed LXDE 10 on mine and it's a blast....no big issues really surprised at how it runs cool and smooth. Uses about half of my 1 GB ram and some swap space with Ffox hexchat lxterm open. I'll try KDE Plasma soon. Thing about rock64 boards is there's 3 versions and I had to try a few distros until I came back to ayufan after he finally caught up on his images. He must know this board well I assume. Board sat for a month here. I was too frustrated with it. So try arch manjaro armbian too. IMO the various devs focus on different uboot / kernel / userspace versions and that introduces issues. It's an arm thing due to building for chip families vs individual boards/versions. Try not to give up too fast on it. It's not a great or popular board for obvious reasons (cheap) but once it works it's a relief. I would use an sdcard first then if thats ok, an emmc.
  2. Update: kernel 5.6.0 boots on my V2. I just installed latest ayufan ubu focal unstable image and its been ok for a day now. Time will tell if this becomes my main image vs arch/manjaro/armbian. I'll try armbian again when a stable release is out with this kernel.
  3. I'm using a sandisk Ultra 16GB sd card. Never used emmc yet. Originally flashed and used spi usb boot w/o any probs. I flashed it back to empty in the testing im doing last 4-5 days. I'll leave spi alone and empty for now. Martin: I tried a jumper on emmc pins by the lights. Didn't help. May be that my timing isnt right ...boot with jumper stop the boot with a keystroke, remove jumper, hit a key and continue booting. Since lanefu's new v2 booted and tonys then the sdcards are more robust than this sandisk ultra? It's a brand name top card so that baffles me but could be the problem. Thats surely not the solution though. What kernel? the kernel in the current image dated 1-26-2020 plus I tried a build from lanefu that has 5.4.20 with latest patches. I read in a thread that the boot order is spi>emmc>sd. It used to be spi>sd>emmc and that change has caused lots of probs for pine products. Sounds to me like its about that order and the voltages being used and how that ruins the sdcard's chance of booting due to corruption. Plus using really old configs from ayufan from 2 yrs ago (no matter how updated) when the board was released is imo not right. I've enjoyed the hunt for this problem but i'm getting tired since the fix isnt some simple file edit or switch to a different image a plain user can do. I've done and reported what I resonably can.
  4. [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 8.748477] [drm] No driver support for vblank timestamp query. [ 8.751175] [drm] Cannot find any crtc or sizes [ 8.752049] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 1 [ 9.596617] Adding 502880k swap on /dev/zram1. Priority:5 extents:1 across:502880k SSFS [ 9.760746] [drm] Cannot find any crtc or sizes [ 9.763672] zram0: detected capacity change from 0 to 52428800 [ 11.920458] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [ 11.921159] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff) [ 14.451738] random: crng init done [ 14.452073] random: 7 urandom warning(s) missed due to ratelimiting [ 14.810329] ------------[ cut here ]------------ [ 14.810765] kernel BUG at fs/inode.c:588! [ 14.811128] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [ 14.811614] Modules linked in: zstd dw_hdmi_i2s_audio rockchipdrm lima snd_soc_rk3328 analogix_dp gpu_sched dw_mipi_dsi dw_hdmi zram ip_tables ipv6 crc_ccitt dwmac_rk stmmac_platform stmmac phylink phy_rockchip_inno_usb3 phy_rockchip_inno_hdmi [ 14.813531] CPU: 2 PID: 1 Comm: systemd Not tainted 5.4.14-rockchip64 #rc1 [ 14.814139] Hardware name: Pine64 Rock64 (DT) [ 14.814530] pstate: a0000005 (NzCv daif -PAN -UAO) [ 14.814967] pc : evict+0x164/0x168 [ 14.815276] lr : evict+0xe8/0x168 [ 14.815572] sp : ffff80001002b930 [ 14.815869] x29: ffff80001002b930 x28: ffff00003e1646c0 [ 14.816343] x27: ffff800011126d88 x26: ffff00003c6be500 [ 14.816815] x25: ffff00003c6be500 x24: ffff80001136b508 [ 14.817286] x23: ffff80001027e988 x22: ffff00003a210298 [ 14.817757] x21: ffff800010dca880 x20: ffff00003bcc4b10 [ 14.818231] x19: ffff00003bcc4b20 x18: 0000000000000000 [ 14.818703] x17: 0000000000000000 x16: 0000000000000000 [ 14.819176] x15: ffffffffffffffff x14: ffff80001136b508 [ 14.819649] x13: ffff80001002bb58 x12: ffff80001002bb4d [ 14.820121] x11: 00000000046b9e80 x10: ffff80001002bac0 [ 14.820594] x9 : 00000000ffffffd8 x8 : 0000000000000000 [ 14.821065] x7 : 0000000000000001 x6 : 0000000000000000 [ 14.821537] x5 : 0000000000000001 x4 : 61c8864680b583eb [ 14.822009] x3 : ffff800011366180 x2 : ffff8000113666f8 [ 14.822492] x1 : 0000000000000000 x0 : ffff00003bcc4bb0 [ 14.822972] Call trace: [ 14.823200] evict+0x164/0x168 [ 14.823474] iput+0xd8/0x190 [ 14.823732] dentry_unlink_inode+0x114/0x160 [ 14.824114] __dentry_kill+0xc0/0x1c0 [ 14.824442] shrink_dentry_list+0x7c/0xd8 [ 14.824799] shrink_dcache_parent+0xd8/0x130 [ 14.825180] d_invalidate+0x60/0xe0 [ 14.825494] proc_flush_task+0xa8/0x198 [ 14.825841] release_task.part.27+0x78/0x448 [ 14.826220] wait_consider_task+0x7a4/0x820 [ 14.826591] do_wait+0x130/0x1d8 [ 14.826880] kernel_waitid+0x110/0x1e0 [ 14.827212] __do_sys_waitid+0x3b4/0x428 [ 14.827561] __arm64_sys_waitid+0x24/0x30 [ 14.827921] el0_svc_common.constprop.1+0x88/0x178 [ 14.828346] el0_svc_handler+0x20/0x80 [ 14.828681] el0_svc+0x8/0xc [ 14.828944] Code: 17ffffd2 f90013f5 d4210000 d4210000 (d4210000) [ 14.829490] ---[ end trace b3d7224f99874ee8 ]--- [ 14.829902] note: systemd[1] exited with preempt_count 2 [ 14.830373] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 14.831048] SMP: stopping secondary CPUs [ 14.831400] Kernel Offset: disabled [ 14.831712] CPU features: 0x0002,20002000 [ 14.832067] Memory Limit: none [ 14.832342] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- verb=7 output same error not syncing on bionic and buster minimal current release img's.
  5. Applying kernel provided DT fixup script (rockchip-fixup.scr): Finally got a serial board so theres the output. Hope this helps to fix my V2 rock64 on new images. This is for latest standard buster server RC image. Not syncing is usually it cant find the right partition to complete the boot.
  6. I'm new to armbian so hi to all. I recently bought a sealed Rock64 v2 off ebay with psu and sdcard for low cost. It works ok but has lots of same issues like others have. I'm just adding my 2 cents in here so another user is heard in the thread. Armbian Bionic w/4.4 minimal works well. Anything else newer does not boot. I dont have serial cable so that's all I can report for now. Compiles well too. Arch and Manjaro stock images work well (5.5.1) but they segfault when compiling anything. Still looking for an image for v2 that compiles and is 5.2 or newer.