Jump to content

Nickb333

Members
  • Posts

    9
  • Joined

  • Last visited

  1. This board seems to work well for me with Armbian once I'd resolved the power supply issue. I'm running the ethernet link at 1G, sound is provided by an external CM108 device. I'm mainly using it for light desktop work, browsing using Chromium and also running the Arduino IDE. Compared to a Pi3 it does all these tasks faster. Welcome to ARMBIAN 5.36 user-built Ubuntu 16.04.3 LTS 4.13.16-rockchip System load: 0.00 0.00 0.00 Up time: 4 days Memory usage: 7 % of 2005MB IP: 10.xxx.yyy.zzz CPU temp: 58°C Usage of /: 23% of 15G [ General system configuration (beta): armbian-config ] Last login: Sun Jan 14 20:18:47 2018 from 10.xxx.yyy.zzz
  2. So I held back the following packages from 5.30 after running apt-get update then ran apt-get upgrade and re-booted. nick@orangepione:~$ apt-mark showhold armbian-firmware armbian-tools-xenial linux-headers-sun8i linux-image-sun8i linux-u-boot-orangepione-default linux-xenial-root-orangepione No pink screen so far. Edit: Add armbianmonitor -r http://sprunge.us/jEIF
  3. Hi, On upgrading to 5.35 Ubuntu Xenia default 3.4.113 I am unable to get DVI video working, I am presented with a pink screen. Monitor is a 1280x1024 dvi connected via HDMI-DVI converter cable. I am configuring this with h3disp -m 1280x1024 -d. I have rolled back to a 5.30 image and everything works as it should. Possibly a bug? How can I upgrade everything in the distro without breaking the video again? Thanks.
  4. I have the same problem with 3.4.113 on a pdDuino2 and this resolved it. Thanks for the work-around.
  5. I had a similar issue with my 3B which is a 3 with GBe. That needed the nano image. Did you try legacy on yours? I had issues with high cpu load which is why I switched to mainline.
  6. You have 3.4 kernel = LEGACY so you need to edit the FEX. See https://docs.armbian.com/Hardware_Allwinner/#updating-a-fex Once you have a fex file to edit after bin2fex you should refer to http://linux-sunxi.org/Fex_Guide HTH.
  7. Thanks for youre reply. Added. That breaks the GbE - armbianmonotor -u output.
  8. Added armbianmonitor -m for the pcDuino3B running pcDuino3-nano mainline.
  9. I've had success with Armbian runing on Orange Pi One and pcDuino2. I'm using the legacy kernels on these boards. Today I've got a pcDuino3B - similar to pcDuino3 except it has GB ethernet from the pcDuino3 nano. I tried legacy kernels for both the 3 and the 3 nano. I see high cpu load ~35% from one of the kworker processes. Then I tried the mainline kernels from the 3 and the 3 nano. No cpu load problems but the GbE does not appear to be configured in the 3 image. 3 nano works on both ethernet and wifi so I'm wondering whether to stick with this one and see if there are any other differences. I don't have a build environment set up and no experience with kernel debugging. I'd like to try and resolve the high cpu issue with the legacy kernel so what should I look for or is there any info I can post here that might help point me in the right direction? Thanks, Nick.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines