Project

General

Profile

Bug #2161

[linux-libre-chromebook]trying to flash kernel image to root partition

Added by Time4Tea 16 days ago. Updated 15 days ago.

Status:
info needed
Priority:
bug
Assignee:
% Done:

0%


Description

I recently installed linux-libre-chromebook (arm Chromebook C201). During the installation, it was by default going to 'dd' the kernel image to my root partition (/dev/mmcblk0p4), as opposed to the correct kernel partition (/dev/mmcblk0p3). This seems like quite a serious issue, as potentially people just have to type 'y' to overwrite their root system.

History

#1 Updated by bill-auger 16 days ago

  • Assignee set to Megver83

#2 Updated by Megver83 16 days ago

The post_intall script linux-libre-chromebook uses is the same as of ALARM. Idk really how could I check it if I do not own a C201, sorry

#3 Updated by bill-auger 16 days ago

  • Assignee changed from Megver83 to oaken-source
  • Status changed from open to info needed
  • Project changed from Documentation to Packages

i think oaken-source has one - i dont know how much time he has these days to devote to parabola; but i will assign this issue to him - maybe someday he can try installing this kernel and confirm this as a bug

#4 Updated by Megver83 16 days ago

bill-auger wrote:

i think oaken-source has one - i dont know how much time he has these days to devote to parabola; but i will assign this issue to him - maybe someday he can try installing this kernel and confirm this as a bug

and hopefully he (or we) can solve it

#5 Updated by Time4Tea 15 days ago

I just re-installed the linux-armv7-chromebook package on ALARM and it seems to be flashing the kernel to the correct partition. So, looks like maybe they have already fixed it upstream?

#6 Updated by Time4Tea 15 days ago

Actually no, I just installed and ran linux-armv7-chromebook in Parabola and it did the same thing as linux-libre-chromebook. I think it's to do with the way I have my SD partitioned. I have ALARM on partitions 1 (kernel) & 2 (root) and Parabola on partitions 3 (kernel) & 4 (root). When I run it in ALARM, it tries to flash to p1, which is correct; however, in Parabola it tries to flash to p4, which is not.

Perhaps I should report this one upstream to ALARM?

Also available in: Atom PDF