Ubuntu 15.10 / 16.04 for Odroid U3 ?

hugolp · Post by **hugolp** » Sun Sep 25, 2016 5:37 am

odroid wrote:Give us a couple of days. Sorry for the delay.

Update :
Has been released.
http://odroid.com/dokuwiki/doku.php?id= ... e_20160921

Odroid can you comment on the possibility of having the minimal version of Ubuntu 16.04 for the u2u3.

Post by **odroid** » Mon Sep 26, 2016 11:07 am

We have no plan to make a minimal image in near future due to many other to-do lists.
Sorry about that.

Post by **odroid** » Mon Sep 26, 2016 11:10 am

safeman wrote: I have the Hardkernel supplied WiFi dongle (Realtek RTL8188CUS) and sometimes when I plug it in it flashes, and I have seen a desktop notification showing it is being recognised. The MATE menu has no WiFi or Network Manager app that I can find or start from the command line.

We will check the 8188CUS driver/fw soon.

mories · Post by **mories** » Tue Sep 27, 2016 11:20 pm

Also in my case, the Hardkernel supplied WiFi Module 3 dongle (Realtek RTL8188CUS) (0bda:8176) does not work with this image.
What is the solution?

shezzski · Post by **shezzski** » Wed Sep 28, 2016 6:51 pm

I just want to thank Hardkernel for supporting this platform and providing Ubuntu 16.04.

thamjin · Post by **thamjin** » Thu Sep 29, 2016 4:49 pm

Hi odroid, Thanks for providing Ubuntu 16.04 for U3 platform !
Btw, is there an official Package Repository for U3 in place upgrade from 14.04LTS without flashing the emmc ?

Post by **odroid** » Thu Sep 29, 2016 5:34 pm

There has been no repository for U3.
We supported the updates via odroid-utility for long time.
But, there will be no(or rare) update due to our limited resources.

I think the upgrade from 14.04LTS will not work smoothly.

jargha · Post by **jargha** » Fri Sep 30, 2016 5:30 am

I'm not sure if I am doing something wrong but I have attempted to flash the Ubuntu 16.04 release to an eMMC and load on my U2 a couple of times without boot success.

I downloaded an verified the md5 of the image.
Flashed using 'dd' (on a system using Ubuntu 16.04) to emmc module.
Ran the 'sync' command a couple of times.
Booted U2 with emmc module installed.

Nothing appears on HDMI out during boot. I repeated the above process a couple of times without any success, and then flashed a 14.01 Ubuntu image for sanity purposes which worked fine on boot. The emmc module I have is 8GB capacity - is this sufficient for the Ubuntu 16.04 release?

Is there any other 'gotchas' which might be catching me out ? .... any advice greatly appreciated!

safeman · Post by **safeman** » Fri Sep 30, 2016 5:44 am

jargha wrote: ...
Flashed using 'dd' (on a system using Ubuntu 16.04) to emmc module.
...

Following the flashing instructions in the Wiki I did this for my U3 with a 64GB eMMC and all was fine. The Wiki shows you how to generate and compare the checksum from the eMMC so you could try that to confirm it was written ok.

jargha · Post by **jargha** » Fri Sep 30, 2016 6:20 am

Thx yes I saw that on the wiki and tried the commands listed (except I had to prefix 'sudo' to the second 'dd' command as I think it is missing on the wiki). The md5 values listed were the same for both times I ran the command, but different to md5sum of the image itself - it is unclear whether it should be the same as that provided on the image file.

hugolp · Post by **hugolp** » Fri Sep 30, 2016 6:43 am

jargha wrote:I'm not sure if I am doing something wrong but I have attempted to flash the Ubuntu 16.04 release to an eMMC and load on my U2 a couple of times without boot success.

I downloaded an verified the md5 of the image.
Flashed using 'dd' (on a system using Ubuntu 16.04) to emmc module.
Ran the 'sync' command a couple of times.
Booted U2 with emmc module installed.

Nothing appears on HDMI out during boot. I repeated the above process a couple of times without any success, and then flashed a 14.01 Ubuntu image for sanity purposes which worked fine on boot. The emmc module I have is 8GB capacity - is this sufficient for the Ubuntu 16.04 release?

Is there any other 'gotchas' which might be catching me out ? .... any advice greatly appreciated!

I plan to do the same next week, install the new image in a u2, please keep us informed.

safeman · Post by **safeman** » Fri Sep 30, 2016 6:57 am

jargha wrote:Thx yes I saw that on the wiki and tried the commands listed (except I had to prefix 'sudo' to the second 'dd' command as I think it is missing on the wiki). The md5 values listed were the same for both times I ran the command, but different to md5sum of the image itself - it is unclear whether it should be the same as that provided on the image file.

The wiki shows generating the checksum for both image file and, eMMC, and these should match (as well as match that given in the md5sum file). Looks like there is your problem if they don't.

jargha · Post by **jargha** » Fri Sep 30, 2016 10:19 pm

I may have performed a mistake during flashing, I will try flashing again tonight on the U2 and post here on whether I got a successful bootup.

jargha · Post by **jargha** » Sun Oct 02, 2016 7:00 am

jargha wrote:I may have performed a mistake during flashing, I will try flashing again tonight on the U2 and post here on whether I got a successful bootup.

I attempted to flash the Ubuntu 16.04 image again today for the 3rd time. This time I made sure to run the burn verification afterwards as described on the Flashing instructions Wiki page, and the matching md5sum was printed for both 'dd' command variants listed. However, when I installed the emmc in the U2, once again I got no visual output on HDMI when I powered up the system.

I'd be interested to hear if anyone has successfully flashed / booted up on a U2 or is this image possibly only working on U3 devices?

hugolp · Post by **hugolp** » Sun Oct 02, 2016 7:55 pm

jargha wrote:
jargha wrote:I may have performed a mistake during flashing, I will try flashing again tonight on the U2 and post here on whether I got a successful bootup.
I attempted to flash the Ubuntu 16.04 image again today for the 3rd time. This time I made sure to run the burn verification afterwards as described on the Flashing instructions Wiki page, and the matching md5sum was printed for both 'dd' command variants listed. However, when I installed the emmc in the U2, once again I got no visual output on HDMI when I powered up the system.

I'd be interested to hear if anyone has successfully flashed / booted up on a U2 or is this image possibly only working on U3 devices?

Have you tried accessing the device through ssh to verify if it is a problem of only the graphical side or the device not working in general?

Here are some instructions in case you are not familiar: http://odroid.com/dokuwiki/doku.php?id= ... up&s[]=ssh

bosscout · Post by **bosscout** » Mon Oct 03, 2016 4:57 pm

odroid wrote:Give us a couple of days. Sorry for the delay.

Update :
Has been released.
http://odroid.com/dokuwiki/doku.php?id= ... e_20160921

Overall it is a fine release. Everything works fine.
Only kodi in 1080P is indeed to much flashing (as mentioned). So I'm back to the previous 14.04.5 release. I will buy a new more powerful device later on this year.

jargha · Post by **jargha** » Mon Oct 03, 2016 11:52 pm

hugolp wrote:Have you tried accessing the device through ssh to verify if it is a problem of only the graphical side or the device not working in general?

Here are some instructions in case you are not familiar: http://odroid.com/dokuwiki/doku.php?id= ... up&s[]=ssh

Thx Hugo, I will try SSH this evening, in fact just looking at my Wifi Router adminstration page will tell me whether there is a live ethernet device running as a first check.

jargha · Post by **jargha** » Wed Oct 05, 2016 5:11 am

Just a small update:
* The device does not show up on the network with Ubuntu 16.04 flashed to 8GB emmc module
* I flashed to an 8GB Mini SD Card, in case there was an issue with the emmc adapter, and am having the same result (no boot up)

The only thing in common with both is that they are both 8GB capacity, even though the image appears to flash successfully, I am starting to wonder if it is just that I need a higher capacity emmc / mini SD card (unfortunately I don't have any to hand to try this).

hugolp · Post by **hugolp** » Wed Oct 05, 2016 5:21 am

jargha wrote:Just a small update:
* The device does not show up on the network with Ubuntu 16.04 flashed to 8GB emmc module
* I flashed to an 8GB Mini SD Card, in case there was an issue with the emmc adapter, and am having the same result (no boot up)

The only thing in common with both is that they are both 8GB capacity, even though the image appears to flash successfully, I am starting to wonder if it is just that I need a higher capacity emmc / mini SD card (unfortunately I don't have any to hand to try this).

Unlikely. 8Gb should be more than enough. I guess it is my turn to test now and report back if I get a working U2 with the new image. Hopefully this week at some point Ill back up the data and services I have working on it and try.

Post by **odroid** » Wed Oct 05, 2016 3:21 pm

@jargha,

Did you "VERIFY" successfully?
http://odroid.com/dokuwiki/doku.php?id= ... diskimager

jargha · Post by **jargha** » Wed Oct 05, 2016 11:08 pm

odroid wrote:@jargha,

Did you "VERIFY" successfully?
http://odroid.com/dokuwiki/doku.php?id= ... diskimager

Hi odroid,

Yes the strange thing is that I verified successfuly - both MD5's printed during verification matched, and they also both matched the md5sum file provided alongside the image file which I downloaded.

Post by **odroid** » Thu Oct 06, 2016 10:37 am

Did you uncompress the xz file to img with 7-zip?

jargha · Post by **jargha** » Thu Oct 06, 2016 9:27 pm

Success at last

I had been flashing using a Ubuntu system, but also have Windows 10. I flashed the image onto Micro-SD card using the Win32 disk imager tool and now can successfully boot Ubuntu 16 image on the U2.

Interestingly, after flashing using the Win Disk Imager tool, I chose 'Verify' and was told that the verification was *not* successful - although Ubuntu is booting successfully on the device.

Sorry for all the noise, I'm still unsure what the root cause was, but it appears as though switching to the Windows tool for flashing resolved the issue for me.

hugolp · Post by **hugolp** » Fri Oct 07, 2016 11:23 pm

There is something funny with the image as I am having a similar experience with my U2, unfortunately without success.

I first tried tried to flash my 16G eMMC from Ubuntu 16.04. I downloaded the compressed image, checked the checksum, uncompressed and checked the checksum of the uncompressed image. Used dd with the parameters in the wiki to flash the image. Once done, used the bash script pointed by @Odroid to check the integrity of the data in the card. But when I used it in the U2 I do not get an IP address in the router list, it is not loading. I checked the checksum at every step and always was correct, and it will not load.

So following jargha experience, I tried to flash from windows. I installed a copy of windows 7 in a HD and used it to boot the computer. I then downloaded everything, uncompressed the image, loaded it in the flashing program and checked the checksum. It matched. Then flashed the card and, once done, verified. The verification was successful, but once again the u2 will not show up in the network. The only difference with jargha is I am using windows 7 instead of 10 (I do not have a w10 copy) and the verification was successful (unfortunately it seems as paradoxical as it sounds).

So I think it is pretty clear there is something funky going on with this image, since the only time that worked was when the verification failed. If I recall correctly, for the last Ubuntu image years ago there was also a problem for U2's because they needed something special in the image that was forgotten.

hugolp · Post by **hugolp** » Sat Oct 08, 2016 5:22 am

I have been all day trying to get this working. I have even installed windows 10 in the computer (apparently windows is free of charge now), but still no luck. Unfortunately(?) the verification of the flashing works sucessfully for me and then Ubuntu 16.04 in the U2 does not work.

1. Usually the red led is always on and the blue led blinks. When trying this image both red and blue are always on.

2. I have checked the logs in the card after booting and it seems to be repeating the same loop again and again, but I do not have the knowledge to understand what is happening.

Any idea what it can be or what I can try?

Post by **odroid** » Sat Oct 08, 2016 11:39 am

If the blue LED was solid on, something was wrong in the Kernel loading process.

Test your faulty SD cards with below FFT(Fake-Flash-Test) utility to check
https://sites.google.com/a/rmprepusb.co ... ory-drives
Try the Formatter 4.0 with the SD cards before flashing OS image.
https://www.sdcard.org/downloads/formatter_4/

Or your eMMC might have a broken boot loader or very old boot loader.
In that case, try this recovery.
http://forum.odroid.com/viewtopic.php?f=53&t=969

hugolp · Post by **hugolp** » Sat Oct 08, 2016 6:22 pm

Ok, so the problem was that the boot loader in the eMMC needed to be updated. Once I followed the procedure in the last link of your message, the flashing worked without a problem on the first try from Ubuntu using dd. No need for windows or anything.

hugolp · Post by **hugolp** » Sat Oct 08, 2016 6:48 pm

And apparently all of this was for nothing because in Ubuntu 16.04 docker version you need a kernel 3.10.x or older. Docker will not install in the default 3.8.X kernel shipped with this image. Is there a way to compile a 3.10.x or older kernel?

mories · Post by **mories** » Sat Oct 08, 2016 8:17 pm

Thank you for this update to U3.

odroid wrote: We will check the 8188CUS driver/fw soon.

Any news about the problem with the Hardkernel's wireless dongle WiFi module 3?.

According to my tests:
1) The dongle works in Ubuntu 16.04 Mate for RPi2.
2) The dongle works in your Ubuntu 14.04 image for U3, even using the kernel, modules and firmware of 16.04 image.

In your 16.04 image for U3, the errors that occur can be seen:
systemctl status NetworkManager
systemctl status wpa_supplicant

meveric · Post by **meveric** » Sat Oct 08, 2016 9:07 pm

hugolp wrote:And apparently all of this was for nothing because in Ubuntu 16.04 docker version you need a kernel 3.10.x or older. Docker will not install in the default 3.8.X kernel shipped with this image. Is there a way to compile a 3.10.x or older kernel?

No, the Exynos 4 series of ODROIDs uses 3.8 Kernel for years already nothing changed on the Kernel, only the OS was updated.
And no, there is no 3.10 Kernel for the Exynos 4 series.
There are some 4.x Kernel builds, but you have to do everything manually, and don't expect much help in doing so: http://forum.odroid.com/viewtopic.php?f=55&t=3691

mories wrote:2) The dongle works in your Ubuntu 14.04 image for U3, even using the kernel, modules and firmware of 16.04 image.

The Kernel for 14.04 and 16.04 is the same, we use the same Kernel for all OS, so there is litereally NO DIFFERENCE in the Kernels between different OS.
Therefore it's most likely an OS configuration issue.

safeman · Post by **safeman** » Sat Oct 08, 2016 9:48 pm

meveric wrote: No, the Exynos 4 series of ODROIDs uses 3.8 Kernel for years already nothing changed on the Kernel, only the OS was updated.
And no, there is no 3.10 Kernel for the Exynos 4 series.
There are some 4.x Kernel builds, but you have to do everything manually, and don't expect much help in doing so: http://forum.odroid.com/viewtopic.php?f=55&t=3691
...
The Kernel for 14.04 and 16.04 is the same, we use the same Kernel for all OS, so there is litereally NO DIFFERENCE in the Kernels between different OS.
Therefore it's most likely an OS configuration issue.

Wish I'd known this. I've been waiting for 16.04 specifically because I need a 3.9 or later kernel.

What is the easiest way to get a 3.9 or later kernel for U3 - any distro, headless is fine?

meveric · Post by **meveric** » Sun Oct 09, 2016 3:39 am

safeman wrote:What is the easiest way to get a 3.9 or later kernel for U3 - any distro, headless is fine?

There is no easy way as I said before.

hugolp · Post by **hugolp** » Sun Oct 09, 2016 5:56 pm

meveric wrote:
hugolp wrote:And apparently all of this was for nothing because in Ubuntu 16.04 docker version you need a kernel 3.10.x or older. Docker will not install in the default 3.8.X kernel shipped with this image. Is there a way to compile a 3.10.x or older kernel?
No, the Exynos 4 series of ODROIDs uses 3.8 Kernel for years already nothing changed on the Kernel, only the OS was updated.
And no, there is no 3.10 Kernel for the Exynos 4 series.
There are some 4.x Kernel builds, but you have to do everything manually, and don't expect much help in doing so: http://forum.odroid.com/viewtopic.php?f=55&t=3691

If the only thing I need from the U2 is a working cpu, the eMMC, the 100Mbps network adapter and external storage usb, how doable is to use the 4.x kernel builds? I am using it headless so I do not need a working hdmi, mali or anything else.

meveric · Post by **meveric** » Sun Oct 09, 2016 6:34 pm

doesn't matter if you only want a few features, you still have to go through the entire process, there are not shortcuts: http://linux-exynos.org/wiki/Hardkernel_ODROID-X2

hugolp · Post by **hugolp** » Sun Oct 09, 2016 7:16 pm

meveric wrote:doesn't matter if you only want a few features, you still have to go through the entire process, there are not shortcuts: http://linux-exynos.org/wiki/Hardkernel_ODROID-X2

I understand, I already recompiled the kernel years ago to include some drivers that were needed at the time. My question was if there are any big issues with the present state of this kernel that would make it even try it not viable given my needs. But I see in the table of your link that everything except hardware video decoding/encoding seems to be working, so I think I will get a sd card to create a test system to see if I can get everything working with the new kernel.

LiquidAcid · Post by **LiquidAcid** » Sun Oct 09, 2016 11:04 pm

hugolp wrote:My question was if there are any big issues with the present state of this kernel that would make it even try it not viable given my needs.

Make sure to check any of these issues against vanilla-4.8.y and report them upstream.

safeman · Post by **safeman** » Mon Oct 10, 2016 12:24 am

meveric wrote:
safeman wrote:What is the easiest way to get a 3.9 or later kernel for U3 - any distro, headless is fine?
There is no easy way as I said before.

If you have actually said that somewhere, I missed it sorry. However...

I mentioned this as the reason for my wanting an updated distro many times. Both in this Ubuntu 16.04 topic, and elsewhere (including where someone suggested your Debian image). So I have mentioned this was my reason quite a few times, and I've been pointed to various solutions (including towards your Debian distro), but these latest posts are the first time I've seen anyone say that: a) the Ubuntu 16.04 is 3.8 and never going to be later, or that b) as you now say, there is **no distro** available with a > 3.8 kernel.

It would have been helpful to have known this back in April, and it is really surprising that - if anyone following this topic since then knew this to be the case - nobody has said it until this:

No, the Exynos 4 series of ODROIDs uses 3.8 Kernel for years already nothing changed on the Kernel, only the OS was updated.
And no, there is no 3.10 Kernel for the Exynos 4 series.

If that has appeared somewhere in this topic, by all means point it out to me, but I have followed it since I first posted and find it hard to believe that I missed it.

meveric · Post by **meveric** » Mon Oct 10, 2016 7:43 am

This topic is about a new OS version, not about a new Kernel version. New OS doesn't necessarily mean new Kernel version. At least not in the ARM world.
Most users that still use the ODROID U3 know about the limitations. No one discussed anything about the Kernel, since it's a known fact, that the Kernel is not developed anymore by HardKernel (for years already).

It's probably a miss-communication saying "I need a newer OS" when you actually mean "I need a newer Kernel".

safeman · Post by **safeman** » Mon Oct 10, 2016 6:58 pm

meveric wrote:This topic is about a new OS version, not about a new Kernel version. New OS doesn't necessarily mean new Kernel version. At least not in the ARM world.
Most users that still use the ODROID U3 know about the limitations. No one discussed anything about the Kernel, since it's a known fact, that the Kernel is not developed anymore by HardKernel (for years already).

It wasn't a known fact to me, and I see from this topic I'm not alone in that.

"Most users that still use the ODROID U3 know about the limitations."

I doubt this, but it really doesn't matter.

meveric wrote: It's probably a miss-communication saying "I need a newer OS" when you actually mean "I need a newer Kernel".

I agree it is a miscommunication, but no, I have said more than once that I wanted U16.04 OS because I was in need of a >3.8 kernel. I'd already posted months and months ago before this topic appeared about wanting a >3.8 kernel, but still nobody has picked up on the point.

I'm not saying anyone on this topic was deliberately unhelpful, but it seems unlikely "most" people are as knowledgeable about this as you think.

Anyway, it's ok. I now know the situation. It is just frustrating and has wasted my time to have been asking about a newer kernel for many months, and nobody pointing this out until last week.

meveric · Post by **meveric** » Mon Oct 10, 2016 8:34 pm

I've never actively seen you asking for a new Kernel, I checked some of your old posts and some of them are complains that ARCH still uses an old Kernel, but that's about it.
I found here you said something that you're waiting on "this kernel update", but no one actually ever said anything about a Kernel update, only a OS update.

It's better to ask questions like this in a separate thread, rather than adding to a discussion about another topic, since questions like this really seem to get missed that way.
Else someone probably could have told you months ago, that there won't be any Kernel updates.

crossover · Post by **crossover** » Tue Oct 11, 2016 9:11 am

Is this Kernel 4.8.1 working with U3?
http://forum.odroid.com/viewtopic.php?f ... 00#p162826

LiquidAcid · Post by **LiquidAcid** » Wed Oct 12, 2016 1:39 am

crossover wrote:Is this Kernel 4.8.1 working with U3?
http://forum.odroid.com/viewtopic.php?f ... 00#p162826

Occasionally. It works as long as I don't break stuff. Which I tend to do.... a lot.

mikewhatever · Post by **mikewhatever** » Sun Oct 23, 2016 12:59 am

meveric wrote: No, the Exynos 4 series of ODROIDs uses 3.8 Kernel for years already nothing changed on the Kernel, only the OS was updated.
And no, there is no 3.10 Kernel for the Exynos 4 series.
There are some 4.x Kernel builds, but you have to do everything manually, and don't expect much help in doing so: http://forum.odroid.com/viewtopic.php?f=55&t=3691

That is very unfortunate, not because newer kernels are better, but rather because the 3.8 we have had zero security patches, and over the years it accumulates. This month, October 2016, CVE-2016-5195 has been patched by mainline and distros, but ARM ecosystem is mostly left out, except Raspberry pi. Any way we can get at least the critical ones? If only we could have the 3.13, or the 4.4 kernel from Ubuntu LTSs, of any mainline LTS kernel to boot properly, and work as well as 3.8, ...but that's wishful thinking.
PS: I've been reading about a massive DDOS attack, and couldn't help thinking how many Odroids were in that botnet.

LiquidAcid · Post by **LiquidAcid** » Sun Oct 23, 2016 1:26 am

Vanilla 4.4.y (which is the most recent LTS) should boot fine on X2/U2/U3, but you still have to build the kernel yourself (and upstream u-boot).

safeman · Post by **safeman** » Sun Oct 23, 2016 2:00 am

mikewhatever wrote: [snip]
That is very unfortunate, not because newer kernels are better, but rather because the 3.8 we have had zero security patches, and over the years it accumulates. This month, October 2016, CVE-2016-5195 has been patched by mainline and distros, but ARM ecosystem is mostly left out, except Raspberry pi. Any way we can get at least the critical ones? If only we could have the 3.13, or the 4.4 kernel from Ubuntu LTSs, of any mainline LTS kernel to boot properly, and work as well as 3.8, ...but that's wishful thinking.
PS: I've been reading about a massive DDOS attack, and couldn't help thinking how many Odroids were in that botnet.

I bought Odroid-U3s for a specific purpose and now (a couple of years later) would be reluctant to have them deployed because they would need to be online.

I understand it costs hardkernel to continue support for older devices, but it makes me reluctant to buy from them again because I want devices that will be viable online for more than a couple of years.

mikewhatever · Post by **mikewhatever** » Sun Oct 23, 2016 2:44 am

LiquidAcid wrote:Vanilla 4.4.y (which is the most recent LTS) should boot fine on X2/U2/U3, but you still have to build the kernel yourself (and upstream u-boot).

Well, may be there is hope. I was able to compile a 4.2 kernel back in summer, but failed to figure out the uboot part. Perhaps next holidays I'll try again, if there aren't any pressing matters. The thing is, I was hoping to not have to reinvent the wheel.
I know, I know, Linux has to be hard, you should be able to type on keyboards with half the keys missing, ...guess I am just spoiled.

safeman wrote: I bought Odroid-U3s for a specific purpose and now (a couple of years later) would be reluctant to have them deployed because they would need to be online.

I understand it costs hardkernel to continue support for older devices, but it makes me reluctant to buy from them again because I want devices that will be viable online for more than a couple of years.

Same here. Swapped mine for an old Intel based netbook till I can get a patched kernel. No more ARM stuff for me.

LiquidAcid · Post by **LiquidAcid** » Sun Oct 23, 2016 2:50 am

mikewhatever wrote:I know, I know, Linux has to be hard, you should be able to type on keyboards with half the keys missing, ...guess I am just spoiled.

This just sounds like a developer board is not the right device for you.

meveric · Post by **meveric** » Sun Oct 23, 2016 4:30 am

mikewhatever wrote:That is very unfortunate, not because newer kernels are better, but rather because the 3.8 we have had zero security patches, and over the years it accumulates. This month, October 2016, CVE-2016-5195 has been patched by mainline and distros, but ARM ecosystem is mostly left out, except Raspberry pi.

http://forum.odroid.com/viewtopic.php?p=164672#p164672

hugolp · Post by **hugolp** » Tue Oct 25, 2016 3:12 pm

meveric wrote:
mikewhatever wrote:That is very unfortunate, not because newer kernels are better, but rather because the 3.8 we have had zero security patches, and over the years it accumulates. This month, October 2016, CVE-2016-5195 has been patched by mainline and distros, but ARM ecosystem is mostly left out, except Raspberry pi.
http://forum.odroid.com/viewtopic.php?p=164672#p164672

Hi, I did this to update the kernel from the vulnerability, and it seems to be working but I have a couple doubts probably others too so Ill post here.

1. The kernel that comes from the image is 3.8.13.30 so it is higher than version 3.8.13.28, yet I did not have to delete anything from /media/boot. Is this alright?
2. At the end of the install of the image I got a screen with different options and I selected the second one that was selected by default and said 'mast', was this the correct option?

meveric · Post by **meveric** » Tue Oct 25, 2016 3:24 pm

hugolp wrote:1. The kernel that comes from the image is 3.8.13.30 so it is higher than version 3.8.13.28, yet I did not have to delete anything from /media/boot. Is this alright?

Only if something is preinstalled in the same version you need to remove it manually first.

hugolp wrote:2. At the end of the install of the image I got a screen with different options and I selected the second one that was selected by default and said 'mast', was this the correct option?

Sadly I don't understand what you did. What image did you install? What options?