Jump to content

Recommended Posts

Posted

Hello,

 

my OMV installation on Odroid HC1 is currently at kernel 4.14.111 which is a bit outdated now. Looking at the build config [1], the kernel is fetched from hardkernel [2] which is currently at 4.14.127. What needs to happen to bring the kernel up-to-date? I have been doing packaging for Fedora for quite a while now so I am happy to help if needed.

 

[1] https://github.com/armbian/build/blob/master/config/sources/odroidxu4.conf

[2] https://github.com/hardkernel/linux/tree/odroidxu4-4.14.y

Posted

IMO with Odroid HC1/XU4 you are safe to use kernels that are automatically build -> armbian-config -> system -> switch to nightly ... and you will have latest from https://github.com/hardkernel/linux/tree/odroidxu4-4.14.y

 

1 hour ago, belegdol said:

I have been doing packaging for Fedora for quite a while now so I am happy to help if needed.


We have many things already automated, while stable repository is updated by humans (by me).

Technically:

- you need too build a kernel package with our tools  (to have package scripts and packaging alright)

- send files (image, dtb, headers, sources) as a PR to https://github.com/armbian/upload (sources will not go due to Github file upload limits - you send them to me via PM, email, "dropbox", ...)

- I ran a script and repo apt.armbian.com is updated

 

If you like to help, you are more then welcome! In general, not just with this task.

Posted

Thanks for the info! It seems like I was able to create an Ubuntu VM and build a kernel. I will test it locally first and if no smoke comes out I'll make a PR. I have a few questions though:

  • where exactly in armbian/upload should the new debs go? To debs/stretch?
  • you only listed image, dtb, headers and sources. Am I correct to assume that u-boot does not change and is not required?
  • is there a way of making ./compile.sh use a ramdisk/tmpfs not to punish the SSD too much?

Thank you!

 

ETA: 4.14.127 is up and running.

Zrzut ekranu z 2019-06-25 12-19-30.png

Posted
1 hour ago, belegdol said:

where exactly in armbian/upload should the new debs go? To debs/stretch?


To all user space variants: Stretch, Buster, Bionic, Disco, ...

 

1 hour ago, belegdol said:

you only listed image, dtb, headers and sources. Am I correct to assume that u-boot does not change and is not required?

 

Yes, that is optional - its updated upon manual intervention only. Not needed.

 

2 hours ago, belegdol said:

is there a way of making ./compile.sh use a ramdisk/tmpfs not to punish the SSD too much?


Memory is used optimally by default if you have it enough ... FORCE_USE_RAMDISK="yes" switch might help.

Posted

Thanks again! I have created a PR:

https://github.com/armbian/upload/pull/3

 

The kernel sources can be downloaded from dropbox:

https://www.dropbox.com/s/znd7lnqxf937qtj/linux-source-default-odroidxu4_5.89_all.deb?dl=0

https://www.dropbox.com/s/7oh7idf6rvexjum/linux-source-next-odroidxu4_5.89_all.deb?dl=0

 

Let me know if this is how you expected to get the update. Also, if there are any other packages which would benefit from a simple version sync, please feel free to let me know.

Posted
2 hours ago, belegdol said:

Thanks again! I have created a PR:

https://github.com/armbian/upload/pull/3


I see now that I gave you wrong instructions, sorry. Uploads for packages that are common to all go to "debs" and script redistribute / link across all different variants. Only distribution specific packages goes into sub dirs ... tree is the same as in build script, which is also behind handling this. I also forgot to mention that it would be best to compile from "cosmetics" branch where a few bugs has been fixed. I'll fix this in next hour.


Any input here to help merging or closing is valuable:
https://github.com/armbian/build/pulls
https://github.com/armbian/build/issues

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

Important Information

Terms of Use - Privacy Policy - Guidelines