Samsung Arm Chromebook Install

[johnnydisco]

Hi All,

I've read through the instructions here and tried to do this 3 times (using mmcblk1 not sda) to no avail:

http://archlinuxarm.org/platforms/armv7 ... chromebook.

Pressing ctrl+u just causes the beep error on startup. I'm not sure what further information you need but has any else managed to get this working solely by following these instructions?

Many thanks,
John

PS please go easy, first post and I'm not sure what further information you'll need to hopefully assist..

[WarheadsSE]

It works. Copy & paste, right from the instructions.

[krovetz]

I'm having the same problem. Did you ever figure it out?

[raumzeit]

Same here with usb thumb stick... Hitting ctrl-u at startup turns the screen black for a second or two and then just causes a beep and switch back to the default screen. I also tried it three times now.
Any solutions for this available yet?

[WarheadsSE]

We know for a fact these work guys. Re-check.

[krovetz]

I've tried the installation instructions several times on two different usb ssd's. Neither works.

The same procedure worked on my usb stick.

For some reason, the procedure works with some hardware and not with others.

Same issue here, a low-tone beep when I hit crtl+u.

It looks like my partitions are ok:
$this->bbcode_second_pass_quote('', '
')# parted /dev/sda print
Model: Kingston DataTraveler SE9 (scsi)
Disk /dev/sda: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 21.0MB 16.8MB U-Boot
2 21.0MB 37.7MB 16.8MB ext2 Kernel
12 37.7MB 54.5MB 16.8MB fat16 Script
3 54.5MB 15.6GB 15.6GB ext4 Root

[shpedoikal]

... and I was using the usb 3.0 port.

Switched my usb stick to the usb 2.0 slot and it works just fine.

[raumzeit]

Sorry, but I exactly followed the instructions and tried two different USB sticks, still no success:

partition table looks good on both usb sticks:
1.
$this->bbcode_second_pass_code('', '
localhost / # cgpt show /dev/sda
start size part contents
0 1 PMBR (Boot GUID: 00000000-0000-0000-3850-020000000000)
1 1 Pri GPT header
2 32 Pri GPT table
8192 32768 1 Label: "U-Boot"
Type: ChromeOS kernel
UUID: BF53801A-0E87-AC41-BB82-D83B99A13272
Attr: priority=10 tries=5 successful=1
40960 32768 2 Label: "Kernel"
Type: Linux data
UUID: 551EFDBC-7FA0-9C44-80A0-2DCEA0DCF7D2
106496 31219679 3 Label: "Root"
Type: Linux data
UUID: 678FD148-F91A-3A4B-977C-62721EC78629
73728 32768 12 Label: "Script"
Type: Linux data
UUID: 87CCBC51-93B6-1F4B-98A9-48D2B26D1CAD
31326175 32 Sec GPT table
31326207 1 Sec GPT header
')
2.
$this->bbcode_second_pass_code('', '
localhost / # cgpt show /dev/sda
start size part contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
8192 32768 1 Label: "U-Boot"
Type: ChromeOS kernel
UUID: D8B949AC-58EA-384E-A0D8-5F859D8E89D9
Attr: priority=10 tries=5 successful=1
40960 32768 2 Label: "Kernel"
Type: Linux data
UUID: 59F74C23-1BEA-A240-899B-42243F76B2DB
106496 31160287 3 Label: "Root"
Type: Linux data
UUID: 90A0F0F8-B545-3844-970C-973D2B58AB5F
73728 32768 12 Label: "Script"
Type: Linux data
UUID: E2DEFC5D-BC04-474F-A61B-7792797AE397
31266783 32 Sec GPT table
31266815 1 Sec GPT header
')

and the md5sum check according to the post above gave me the exact same result...

I copy/pasted all the instructions and am very sure that I did not make anything different than stated in the installation instructions...

Also, the USB 3 port was never used by me...

what could be going wrong? The beep at startup just tells me that u-boot is not happy with the kernel it should load... Is there a possibility that my u-boot does not like chained boot? Or maybe the nv_uboot-snow.kpart provided by google has changed meanwhile?

[raumzeit]

Stupid me!

I only had the developer switch activated, but not switched to developer-mode BIOS...

http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/samsung-series-5-chromebook

After switching the BIOS everything works as expected, both usb sticks boot right into alarm!

However, developer-mode BIOS is not mentioned in the alarm install instructions.