Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

1647 profile views
  1. When I run apt-get update && apt-get upgrade my Orange Pi One does not boot anymore. That's why I've posted this advice. Something's up with the bootloader that causes my Orange Pi One (and Orange Pi PC for that matter) to sit and do nothing forever after I power them on after I update the kernel.
  2. I've noticed that Armbian builds are taking a really long time to power up on Orange Pi PC and Orange Pi One. Is there some way I can see what's going on in the bootloader that's causing these long delays? Also, if I run apt-get dist-upgrade and take the latest kernel, it never boots after that point. I think something's wrong with the boot sector (or whatever it is) that is written/updated on the SDCard. The Orange Pi power LEDs don't light up until the bootloader successfully finds an OS on the SDCard. All of the builds over at orangepi.org work just fine but the Armbian ones aren't working right. I'm using a diverse collection of very high-quality SDCards from different manufacturers. Any thoughts? Thanks in advance.
  3. Running apt-get dist-upgrade tries to install the new Allwinner H3 kernel but it takes the Orange Pi PC a really, really long time to extract and install it. The heartbeat LED flashed really fast and after 30 minutes I elected to stop it. Has anyone succeeded doing apt-get dist-upgrade today to get the new kernel on the Orange Pi PC or Orange Pi One, and, if so, how long did it take? The packages are: linux-firmware-image-sun8i linux-headers-sun8i linux-image-sun8i linux-jessie-root-orangepih3 linux-u-boot-orangepih3-default Thanks in advance for any information or advice.
  4. [This is a repost of my own post at orangepi.org.] Hi, I'm very excited to use the Armbian on Orange Pi One. Without rebuilding a kernel or fex file, here is how to configure the Orange Pi One governor so the "[ 150.135554] [cpu_freq] ERR:set cpu frequency to 648MHz failed!" and "[ARISC ERROR] messages no longer appear in dmesg. We will set it to 912MHz on the low end and 1200MHz on the higher end which scale up and down properly on the Orange Pi One. This is until you update your fex file and/or kernel config to use different values for the CPU frequency scaling that are a little different on the Orange Pi One than they are on the Orange Pi PC. Put it in your /etc/rc.local just after the line "/usr/local/bin/sun8i-corekeeper.sh &". /usr/bin/cpufreq-set -d 912MHz -u 1200MHz -g ondemand You can change "ondemand" parameter to conservative, ondemand, userspace, powersave, interactive, or performance. Also, edit /etc/default/cpufrequtils to read: ENABLE=true MIN_SPEED=912000 MAX_SPEED=1200000 GOVERNOR=ondemand
  5. Are you using a HDMI to DVI converter or cable? If so, the console will not appear on your display and you'll have to log in and run the "h3disp -m 5 -d" command and reboot. It may be possible that the system switches from the serial port console to the video console at the "Uncompressing Linux..." message. Then it is up and running with a blank screen on the video display. See what IP address it got from your network's DHCP server and try logging into it remotely and tell us what you find.
  6. Thank you! This was vexing me for a long time. I knew they had to be changed but had no idea why because the values "look" fine. Great catch!
  7. Those commits are very interesting but, yeah, they shouldn't remove the old values. If I ever get a working toolchain to build the kernel I'll see what I can do.
  8. Well, your work is wonderful, and I really think you're doing a great job. I think there's similar attitude problems at Banana Pi communities. I want you to continue supporting Orange Pi H3 boards, for sure. They are the most powerful working implementation I have found so far.
  9. Thanks for the warning. I am very excited to get a 4.x kernel working on my Orange Pi boards. Thanks again for your hard work!
  10. I have a question about error messages with the Orange Pi One using Armbian_5.05_Orangepih3_Debian_jessie_3.4.110_desktop. On the Orange Pi One, I get these errors in the kernel log (dmesg): [ 993.251167] [cpu_freq] ERR:set cpu frequency to 648MHz failed! [ 1146.035749] [ARISC ERROR] :message process error [ 1146.035780] [ARISC ERROR] :message addr : f004b840 [ 1146.035794] [ARISC ERROR] :message state : 5 [ 1146.035807] [ARISC ERROR] :message attr : 2 [ 1146.035820] [ARISC ERROR] :message type : 30 [ 1146.035833] [ARISC ERROR] :message result : ff [ 1146.035845] [ARISC WARING] :callback not install [ 1146.035861] [cpu_freq] ERR:set cpu frequency to 720MHz failed! [ 1146.335676] [ARISC ERROR] :message process error [ 1146.335705] [ARISC ERROR] :message addr : f004b840 [ 1146.335721] [ARISC ERROR] :message state : 5 [ 1146.335735] [ARISC ERROR] :message attr : 2 [ 1146.335749] [ARISC ERROR] :message type : 30 [ 1146.335763] [ARISC ERROR] :message result : ff [ 1146.335776] [ARISC WARING] :callback not install [ 1146.335792] [cpu_freq] ERR:set cpu frequency to 648MHz failed! On the Orange Pi PC, these errors do not occur. I'm curious what I might need to do. I have used h3disp to enable my HDMI-to-DVI cable with "h3disp -m 720p60 -d" and my kernel version is 3.4.112-sun8i. Thanks!
  • Create New...