Jump to content

Orange pi zero: switching kernel


asp

Recommended Posts

Hello.

 

Yesterday i tried to switch kernel in debian jessie 5.24 from 3.4.113 to 4.x using this article:

 

To make sure you won’t run into conflicts within newly installed packages, remove them all before upgrade:

 

1
2
aptitude remove ~nlinux-dtb ~nlinux-u-boot ~nlinux-image ~nlinux-headers
aptitude remove ~nlinux-firmware ~narmbian-firmware ~nlinux-$(lsb_release -cs)-root

Proceed with install:

1
2
3
4
apt-get install linux-image-dev-sun8i linux-dtb-dev-sun8i linux-headers-dev-sun8i
apt-get install linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero
apt-get install armbian-firmware sunxi-tools swconfig a10disp
reboot

https://www.armbian.com/orange-pi-zero/

 

But there is no linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero packages in default repository.
I used apt-cache search to find this packages, so I found this dev. packages for other Orange pi models, but not dev. packages for orange pi zero.
How to switch kernel on Orange pi zero?
Link to comment
Share on other sites

Repository was updated today at around 4 a.m. at CET.

apt-get update

 should do the trick. And beware that you are switching to development kernel which might work or not.

Link to comment
Share on other sites

Repository was updated today at around 4 a.m. at CET.

apt-get update

 should do the trick. And beware that you are switching to development kernel which might work or not.

 
Ok, thank you. I'd like to ask you here about this kernels and wifi, although I created another topic about wifi on orange pi zero before.
As I wrote on this topic ( https://forum.armbian.com/index.php/topic/3355-orange-pi-zero-wifi-apmanaged/) wifi as AP+Client (two virtual interfaces) works good on kernel 4.9.4.. Why so? Is it possible to configure wifi in such way on 3.4.113 ?
Link to comment
Share on other sites

Why so? Is it possible to configure wifi in such way on 3.4.113 ?

 

No idea. 

 

Why bother if you got it working on modern kernel in first place? Well, you will need to check kernel source, configuration, driver, ...  as you can see, there are 100+ https://github.com/igorpecovnik/lib/tree/master/patch/kernel/sun8i-default patches over this kernel. It's a mess and there is no other way than digging into, if you really want to solve it / understand.

Link to comment
Share on other sites

No idea. 

 

Why bother if you got it working on modern kernel in first place? Well, you will need to check kernel source, configuration, driver, ...  as you can see, there are 100+ https://github.com/igorpecovnik/lib/tree/master/patch/kernel/sun8i-default patches over this kernel. It's a mess and there is no other way than digging into, if you really want to solve it / understand.

Thank you Igor for adding packages to repository, I already updated my debian jessie from 3.4.114 (5.24) to dev branch 4.9.4 (5.25).

Before I tested 4.9.4 kernel on ubuntu, but debian is more friendly for me.

 
BOARD=orangepizero
BOARD_NAME="Orange Pi Zero"
VERSION=5.25
LINUXFAMILY=sun8i
BRANCH=dev
ARCH=arm
IMAGE_TYPE=stable
 
But I note that I can use only 1 core and maximum frequency is 1.01 GHz.. why so?
 
 cat /proc/cpuinfo
processor       : 0
model name      : ARMv7 Processor rev 5 (v7l)
BogoMIPS        : 100.80
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc07
CPU revision    : 5
 
Hardware        : Allwinner sun8i Family
Revision        : 0000
Serial          : 02c00042d2041574
 

 

 

root@orangepizero:~# cpufreq-info
cpufrequtils 008: cpufreq-info © Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 4.24 ms.
  hardware limits: 120 MHz - 1.01 GHz
  available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 240 MHz and 1.01 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.01 GHz (asserted by call to hardware).
  cpufreq stats: 120 MHz:0.00%, 240 MHz:6.52%, 312 MHz:1.39%, 480 MHz:0.78%, 624 MHz:0.47%, 816 MHz:0.28%, 1.01 GHz:90.56%  (368)
root@orangepizero:~#
Link to comment
Share on other sites

Update boot loader.

 

Didn't help :(

 

apt-cache search linux-u-boot-orangepizero-dev
linux-u-boot-orangepizero-dev - Uboot loader 2017.01
 
 apt-cache  search  linux-$(lsb_release -cs)-root-dev-orangepizero
linux-jessie-root-dev-orangepizero - Armbian tweaks for jessie on orangepizero (dev branch)

 

 

apt-get update

 

 

apt-get install linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-jessie-root-dev-orangepizero is already the newest version.
linux-u-boot-orangepizero-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Link to comment
Share on other sites

Well, if this doesn't help, than I don't know. Mainline H3 kernel is in development phase and can work nice one day and can be completely broken the other day. 

Link to comment
Share on other sites

if this doesn't help, than I don't know.

 

Mainline and legacy kernel need different 'secure mode' by u-boot. So it's also changing one line in boot.scr when exchanging kernels on H2+/H3 boards. But I don't think we should enhance documentation but instead stop wasting time with end user support for dev kernels at all (it's still zero useful feedback)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines