Jump to content

Patrick Domack

Members
  • Posts

    7
  • Joined

  • Last visited

  1. 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.
  2. Yes, that patch worked perfectly. Monitor is in 2560x1440 res, and it's really in that now on the display, instead of in 1080p
  3. I'll have to see if I can capture some logs to compare, as I have this issue on the r6s and r6c armbian builds, but I do not have this issue using the opi5 armbian build, all using debian bullseye version.
  4. 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.
  5. 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
  6. 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?
  7. How can I go about installing then onto an r6s. I have not figured out how to boot armbian on one of these devices.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines