Jump to content

Kernel update procedure has been changed


Igor

Recommended Posts

 

Igor,

 

first, many thanks for your work! I highly apprechiate your effort.

 

I tried to upgrade from 3.4.105 to 3.4.110 on a Cubietruck (boot from NAND, System on SSD) via update script. The script finished with no recognizable error and everything seems to be fine. But after the reboot kernel 3.4.105 is still active.

 

I am willing to learn. Any hint apprchiated.

 

Best regards,

 

Mark

 

After running the update for the third time, the correct kernel was installed. A good guess might be that this was some kind of dependency issue. The boot log still shows that there are modules missing:

 

FATAL: Module bt_gpio not found.

FATAL: Module wifi_gpio not found.

FATAL: Module bcmdhd not found.

 

I am not going to dig deeper into this at the moment. If anybody has a hint I will be happy to fix this.

 

Greetings

 

Mark

Link to comment
Share on other sites

That's correct. Those is a proper modules set for a current legacy Cubietruck kernel:

 

This part is not included into update. You need to edit /etc/modules and replace with this + what you might be using extra.

hci_uart
gpio_sunxi
rfcomm
hidp
sunxi-ir
bonding
spi_sun7i
ap6210
Link to comment
Share on other sites

Hi

I have tried to run the batch script on a armbian jessie running on Banana pi, image with kernel 4.4.1 gotten from this site.

The script run just fine, but after the reboot the kernel is still version 4.4.1. I see that the last image come with 4.4.3.

Is the repo outdated or?

Bye

Link to comment
Share on other sites

Why not add a feature that checks if indeed there is an updated kernel?

 

We do that in a way. For example:

 

When you login you are notified - if updates exists and if you don't have auto update enabled.

 

[ 3 updates to install: apt-get upgrade ]

 

After you do apt-get upgrade and if kernel was updated, you get another prompt at login:

 

[ Kernel was updated, please reboot! ]

Link to comment
Share on other sites

It looks like it's not present in the source. From which kernel did you made an upgrade?

 

It's possible that we haven't transfer all patches when we switch kernel source ... 

Link to comment
Share on other sites

It looks like it's not present in the source. From which kernel did you made an upgrade?

I looked at kernel source, and for some reason SUNXI_WDT is available only for sun4i and sun5i families. Since it should be compatible with sun7i too, it may be possible to patch kernel config to allow watchdog module compilation for sun7i.

Link to comment
Share on other sites

http://forum.lemaker.org/thread-1847-1-1.html

 

OK, I am adding patch to meet this.

--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -351,10 +351,10 @@ config IMX2_WDT
 
 config SUNXI_WDT
        tristate "Allwinner A10/A13 Watchdog"
-       depends on ARCH_SUN4I || ARCH_SUN5I
+       depends on ARCH_SUN4I || ARCH_SUN5I || ARCH_SUN7I
        help
          This is the driver for the hardware watchdog on the Allwinner
-         A10/A13 processors.
+         A10/A13/A20 processors.
 
          If you have one of these processors and wish to have
          watchdog support enabled, say Y, otherwise say N.
Link to comment
Share on other sites

Thanks ;)

can i download the ready compiled module somewhere to put it into /lib/modules/.... ?

 

We provide kernel update via repository and this functionality comes withing next update. Within days, a week or so.

 

For urgent cases / if you can't wait - you need to recompile on your own - we provide full working build tools.

Link to comment
Share on other sites

Hi,

 

I have Kernel 3.4.112 on my A20, after running an upgrade I get the following message: 

** Unrecognized file system type **

** File not found zImage **

Bad Linux ARM zImage magic!

 

How do I resolve this? :o

You need provide all possible data not just "3.4.112 and A20"

 

Probably only a link from zImage to vmlinuz-xxxxxx is missing in /boot 

Link to comment
Share on other sites

Hi

I tried to upgrade my 3.14 kernel to any Kernel above 3.18, because of this:

https://github.com/lintweaker/xmos-native-dsd

 

Using putty, I tried with this command:

wget -q -O - http://upgrade.armbian.com | bash

 

But after a while I received message "Hardware not supported"

 

My board is Cubox-i4 Pro. Can you help?

and the answer was well hidden. The procedure is here:

https://forum.armbian.com/index.php/topic/651-hummingboard-i2ex-mainline-kernel/?p=4704

Link to comment
Share on other sites

How to update to nightly versions/kernels with mainline?

 
I have the latest Armbian (5.25) installed with mainline kernel (4.9.4). uname says:
Linux orangepipc 4.9.4-sun8i #14 SMP Thu Feb 2 02:03:26 CET 2017 armv7l armv7l armv7l GNU/Linux
There are nightlys with 4.10 kernel. How do I upgrade to them? If I try to install the kernel manually, 
root@orangepipc:~# apt-get -s install linux-image-dev-sun8i
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-image-dev-sun8i is already the newest version (5.25).
0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.

it says I have the newest one.

 
With
 
apt-get -s upgrade I get:
The following packages will be upgraded:
  base-files bind9-host console-setup console-setup-linux dnsutils keyboard-configuration klibc-utils libbind9-140 libdns-export162
  libdns162 libgssapi-krb5-2 libhogweed4 libisc-export160 libisc160 libisccc140 libisccfg140 libk5crypto3 libklibc libkrb5-3
  libkrb5support0 liblwres141 libnettle6 libssh2-1 linux-firmware linux-libc-dev sudo

Would be the new kernel in "linux-firmware"?

 
The script mentioned earlier
wget -q -O - http://upgrade.armbian.com | bash

has no option for orangepipc

 
Thanks in advance!
Link to comment
Share on other sites

[as my posts went /dev/null today during the sql issue I'm gonna just summarize ;)]

 

Please update your info at

as follows

 

re 3.4: change "linux-u-boot-DEVICE_NAME (cubieboard, lime-a10)" to "linux-u-boot-DEVICE_NAME-default (cubieboard, lime-a10)"

 

re mainline: change "linux-u-boot-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...)" to "linux-u-boot-DEVICE_NAME-next (cubieboard, cubietruck, lime, ...)"

 

PS: And I'm right that I can have both 3.4 and mainline packages installed in parallel, but only have to install / remove the corresponding u-boot package to switch between those?

Link to comment
Share on other sites

9 minutes ago, odoll said:

PS: And I'm right that I can have both 3.4 and mainline packages installed in parallel, but only have to install / remove the corresponding u-boot package to switch between those?

No, this will may break with the kernel upgrade since zImage and uInitrd will be linked to either legacy or mainline based on packages processing order, so basically randomly.

Link to comment
Share on other sites

OK, shouldn't the dependencies then not only remove the u-boot packages, but the others as well!?!

 

root@share:~# apt-get -s install linux-u-boot-cubietruck-next linux-image-next-sunxi  linux-headers-next-sunxi linux-firmware-image-next-sunxi linux-dtb-next-sunxi linux-$(lsb_release -cs)-root-next-cubietruck
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libuuid-perl linux-base
Recommended packages:
  initramfs-tools
The following packages will be REMOVED:
  linux-u-boot-cubietruck-default
The following NEW packages will be installed:
  libuuid-perl linux-base linux-dtb-next-sunxi linux-firmware-image-next-sunxi
  linux-headers-next-sunxi linux-image-next-sunxi
  linux-jessie-root-next-cubietruck linux-u-boot-cubietruck-next
0 upgraded, 8 newly installed, 1 to remove and 1 not upgraded.
Remv linux-u-boot-cubietruck-default [5.25]
Inst libuuid-perl (0.05-1+b1 Debian:8.7/stable [armhf])
Inst linux-base (3.5 Debian:8.7/stable [all])
Inst linux-dtb-next-sunxi (5.26 Armbian:jessie [armhf])
Inst linux-firmware-image-next-sunxi (5.26 Armbian:jessie [armhf])
Inst linux-headers-next-sunxi (5.26 Armbian:jessie [armhf])
Inst linux-image-next-sunxi (5.26 Armbian:jessie [armhf])
Inst linux-jessie-root-next-cubietruck (5.25 Armbian:jessie [armhf])
Inst linux-u-boot-cubietruck-next (5.25 Armbian:jessie [armhf])
Conf libuuid-perl (0.05-1+b1 Debian:8.7/stable [armhf])
Conf linux-base (3.5 Debian:8.7/stable [all])
Conf linux-dtb-next-sunxi (5.26 Armbian:jessie [armhf])
Conf linux-firmware-image-next-sunxi (5.26 Armbian:jessie [armhf])
Conf linux-headers-next-sunxi (5.26 Armbian:jessie [armhf])
Conf linux-image-next-sunxi (5.26 Armbian:jessie [armhf])
Conf linux-jessie-root-next-cubietruck (5.25 Armbian:jessie [armhf])
Conf linux-u-boot-cubietruck-next (5.25 Armbian:jessie [armhf])

 

Link to comment
Share on other sites

On 28.2.2017 at 5:12 PM, odoll said:

as follows

 

re 3.4: change "linux-u-boot-DEVICE_NAME (cubieboard, lime-a10)" to "linux-u-boot-DEVICE_NAME-default (cubieboard, lime-a10)"

 

re mainline: change "linux-u-boot-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...)" to "linux-u-boot-DEVICE_NAME-next (cubieboard, cubietruck, lime, ...)"

 

PS: And I'm right that I can have both 3.4 and mainline packages installed in parallel, but only have to install / remove the corresponding u-boot package to switch between those?

Bump - please don't forgot to correct the wrong file names in Igor's first post

Link to comment
Share on other sites

On 7. 3. 2017 at 0:33 PM, odoll said:

And I'm right that I can have both 3.4 and mainline packages installed in parallel, but only have to install / remove the corresponding u-boot package to switch between those?


+ one annoying problem. Upon updating you ended up booting random kernel ... you boot in last updated kernel.

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