Jump to content

Armbian images for R6S & R6C


Igor

Recommended Posts

@Igor This made my day.
I needed an SBC for my trip next week. Haven't received my KEdge2 case. Now I can use the R6C with NVMe and the software I like/need. 👍:thumbup:
Installed on R6C, NVMe works and both ethernet ports work. All I need to do is make my 5Ghz wifi antenna work. I do have a 5Ghz dongle that works, but not good enough for camping internet. 

Thank you! I'll see to make a video about it. 
Will it be accessible in the default download page?  

Link to comment
Share on other sites

38 minutes ago, NicoD said:

This made my day.

 

Thanks to @Efe Çetin

 

38 minutes ago, NicoD said:

Will it be accessible in the default download page?  

 

Lets keep it in WIP section for awhile until we don't do more testings. I found out armbian-install doesn't work well so this needs to be fixes, perhaps something else ...

Link to comment
Share on other sites

15 minutes ago, Efe Çetin said:

@NicoD i think you should make a video after we get stable images. Currently something is broken 

Ok. I'll wait till things are fixed.
I did just test install to NVMe and boot from sd and it indeed didn't work as it should. Couldn't boot into x anymore. Install to eMMC does work. 
I'm already very happy to have this. I can have the same setup on my trip as I've got on my main desktop at home with the Mekotronics mini.
With a 1TB NVMe for movies. That's great :)
I was really let down by the FE images for it. Seems there's degression. The old R6S image was better than the new R6C Ubuntu. Big thank you!

Link to comment
Share on other sites

That is so not helpful, if that worked, I wouldn't have bothered to ask.

 

I have done this for several sbc. It is only the r6s that when following those instructions, it doesn't boot.

If I use the friendly eflash images it works fine, but I cannot get any of the armbian r6s images to boot, they just sit there without any output, I have tried with and without the mask button.

 

Or was there something specific about those getting started instructions I have oviously overlooked?

 

Link to comment
Share on other sites

14 hours ago, Patrick Domack said:

How can I go about installing then onto an r6s. I have not figured out how to boot armbian on one of these devices.

 

13 minutes ago, Patrick Domack said:

That is so not helpful, if that worked, I wouldn't have bothered to ask.

Maybe if you provided more than a one sentence description on what your problem is and what you have tried, you would get a better answer.  u-boot logs are really useful in debugging booting issues for example.

Link to comment
Share on other sites

well, lets see, I burned all flavors of armbian to a 8gb microsd, plugged the microsd into the r6s, powered it on, with and without holding in the mask button and I get the same thing, no output

nothing on the filesystem changes.

Not sure where I am suppose to collect these u-boot logs from, as I said there is nothing on the screen and nothing changes on the filesystem (microsd card)

 

If I do not press the mask button, the sys light does it's double blink thing, saying it's attempting to eflash, so that is wrong I believe, and if I hold in the mask button, the sys led stays solid

 

Link to comment
Share on other sites

ok, I connected a usbttl and found it was booting (without the mask button), but it seems it setup the resolution on my monitor as 2560x1440 (that my monitor supports) but was doing it incorrectly, so the monitor was actually in 1920x1080 but the r6s thought it was in 2560x1440 so everything it was displaying was off the screen.

after using fbset to adjust it, everything was on the screen and it was usable.

Link to comment
Share on other sites

I have similar issue, the resolution of my monitor is 2560x1440. The system logs are as follows:

Apr 21 15:46:49 r6c kernel: [    6.648224] rockchip-system-monitor rockchip-system-monitor: system monitor probe
Apr 21 15:46:49 r6c kernel: [    6.648940] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
Apr 21 15:46:49 r6c kernel: [    6.650007] random: fast init done
Apr 21 15:46:49 r6c kernel: [    6.650059] random: crng init done
Apr 21 15:46:49 r6c kernel: [    6.650950] rockchip-vop2 fdd90000.vop: Adding to iommu group 14
Apr 21 15:46:49 r6c kernel: [    6.656798] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x285, primary plane phy id: 2
Apr 21 15:46:49 r6c kernel: [    6.656807] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp1 assign plane mask: 0xa, primary plane phy id: 3
Apr 21 15:46:49 r6c kernel: [    6.656825] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x140, primary plane phy id: 8
Apr 21 15:46:49 r6c systemd[1]: Starting Create Volatile Files and Directories...
Apr 21 15:46:49 r6c kernel: [    6.656833] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp3 assign plane mask: 0x0, primary plane phy id: -1
Apr 21 15:46:49 r6c kernel: [    6.656838] rockchip-drm display-subsystem: failed to get hdmi0_phy_pll: -2
Apr 21 15:46:49 r6c kernel: [    6.656843] rockchip-drm display-subsystem: failed to get hdmi1_phy_pll: -2
Apr 21 15:46:49 r6c kernel: [    6.656916] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart3-win0 as cursor plane for vp0
Apr 21 15:46:49 r6c kernel: [    6.668177] rockchip-drm display-subsystem: bound fdd90000.vop (ops 0xffffffc0111bdc00)
Apr 21 15:46:49 r6c kernel: [    6.668855] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
Apr 21 15:46:49 r6c kernel: [    6.669007] rockchip-drm display-subsystem: bound fde80000.hdmi (ops 0xffffffc0111c6410)
Apr 21 15:46:49 r6c kernel: [    6.669357] rockchip-drm display-subsystem: failed to parse loader memory
Apr 21 15:46:49 r6c kernel: [    6.887021] dwhdmi-rockchip fde80000.hdmi: use tmds mode
Apr 21 15:46:49 r6c kernel: [    6.887072] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 1920x1080p60, type: 11(if:800) for vp0 dclk: 148500000
Apr 21 15:46:49 r6c kernel: [    6.887227] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
Apr 21 15:46:49 r6c kernel: [    6.887238] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 148500000, get 148500000
Apr 21 15:46:49 r6c kernel: [    6.887271] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:16a8c8 rate:1485000
Apr 21 15:46:49 r6c kernel: [    6.887549] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
Apr 21 15:46:49 r6c kernel: [    6.887552] dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 148500000
Apr 21 15:46:49 r6c kernel: [    6.887582] dwhdmi-rockchip fde80000.hdmi: don't use dsc mode
Apr 21 15:46:49 r6c kernel: [    6.887585] dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode
Apr 21 15:46:49 r6c systemd-tmpfiles[710]: Setting file flags is only supported on regular files and directories, cannot set on '/var/log/journal'.
Apr 21 15:46:49 r6c kernel: [    6.887592] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x16a8c8,bit_rate:1485000
Apr 21 15:46:49 r6c kernel: [    6.887785] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!
Apr 21 15:46:49 r6c kernel: [    6.954037] dwhdmi-rockchip fde80000.hdmi: use tmds mode
Apr 21 15:46:49 r6c kernel: [    6.970706] Console: switching to colour frame buffer device 240x67
Apr 21 15:46:49 r6c kernel: [    6.970810] dwhdmi-rockchip fde80000.hdmi: use tmds mode
Apr 21 15:46:49 r6c kernel: [    7.017772] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device

 

Link to comment
Share on other sites

I have noticed 2.4% packet loss on the 2.5g interfaces. If I disable gro on them, I no longer have packet loss

I have also tried adjusting the gro params, and that helps, and mostly changes the packet loss into high latency packets (loss down to 0.1% though)

The adjustments i used was to set gro_flush_timeout to 20000, and napi_defer_hard_irqs to 10

I'll probably just leave gro disabled, as it can greatly cause havoc with video work meetings.

I'm also planning on giving a newer version of the r8125 driver a shot and see what happens.

 

Link to comment
Share on other sites

Hello :D

 

I have somewhat moronic questions, so please bare with me. I see a lot of images for the NanoPi R6C. However I am mostly familiar to the Mate Desktop. I am under the assumption that I could install the minimal CLI Armbian image and work my way up from there.

 

Is this correct?

 

If not, what has to be done in order to achieve that desired outcome?

 

Thank you very much in advance,

 

Dantes

 

 

Link to comment
Share on other sites

On 4/27/2023 at 8:08 PM, Dantes said:

I am under the assumption that I could install the minimal CLI Armbian image and work my way up from there.

 

Is this correct?

 

Yes, that should work.

 

On 4/27/2023 at 8:08 PM, Dantes said:

 

If not, what has to be done in order to achieve that desired outcome?

 

Alternatively, you could build an Armbian image with Mate desktop, as I think that might be one of the supported ones available in build tool (not sure)?

Link to comment
Share on other sites

Just got my NanoPi R6S, and would love to install armbian. One thing I was wondering is whether the current image has GPU hardware acceleration video playback. In particular, it would be awesome to run kodi with hardware acceleration on it...

Link to comment
Share on other sites

@Efe Çetin Thank you very much for the hint! I will give this a spin!

 

[Edit:] I tried the instructions, but unfortunately, it seems like the pulling from the repo (which seems to be for Jammy?) for the Bullseye image offered on the Armbian webpage fails. Can I follow instructions to build those libraries for Bullseye? Or is there a Jammy image for the R6S I should follow?

Edited by Blind55
Link to comment
Share on other sites

There is another "crazy :D" device out: NanoPC-T6, almost same specs as r6s and r6c

 

https://www.friendlyelec.com/index.php?route=product/product&product_id=292

https://wiki.friendlyelec.com/wiki/index.php/NanoPC-T6

 

MEM: 4gb/8gb/16gb

EMMC: 32gb/64gb/256gb

NICS: 2x 2.5gbps nic

VIDEO: 3x hdmi (2x out,1x in)

IR: optional

 


 

 

T6_04-900x631.jpg

Edited by Dantes
Link to comment
Share on other sites

Yes, the new NanoPC-T6 is "wonderful", similar specs as r6s & r6c but with the rk3588 processor and not the "limited" rk3588s.

 

I have the new T6 working with an internal SSD NVMe and a wifi M.2 card and it's incredible... but I would like to use with Armbian as I'm using my BPI-W3

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines