Samsung XE303C12 / Ctrl-U not booting

This forum is for supported devices using an ARMv7 Samsung SoC.

Re: Samsung XE303C12 / Ctrl-U not booting

Postby cdrigby » Wed Aug 11, 2021 6:23 pm

$this->bbcode_second_pass_quote('', 'a')rmuseru wrote:
I use 3rd party kernel 5.13.6 from https://github.com/quarkscript/linux-ar ... 03c12-only with my xe303c12 and it boots ok from internal mmc.


Thanks for finding that armuseru. I will see if I can get it working on my own system.

CDR
cdrigby
 
Posts: 4
Joined: Mon Jul 05, 2021 10:27 am

Re: Samsung XE303C12 / Ctrl-U not booting

Postby murph » Sun Aug 22, 2021 2:52 pm

Does anyone have some detailed instruction on how to install this? I'm not familiar with how to.

thanks,
--murph
murph
 
Posts: 10
Joined: Thu Apr 30, 2020 11:35 pm

Re: Samsung XE303C12 / Ctrl-U not booting

Postby m3lang3 » Wed Aug 25, 2021 4:21 pm

Here's what I'm doing to install https://github.com/quarkscript/linux-ar ... 03c12-only right now:

1) Clear a bunch of space by using sudo pacman -Sc, and then clearing out large folders in my home dir using du -s -x -d 1. (in my case, I found 700 megs of browser caches) This resulted in about five and a half gigabytes free. (my first attempt failed due to running out of space)
2) Go to the link and click the green Code button in the top right-hand corner, then click Download ZIP.
3) Unzip it, cd linux-armv7-xe303c12-only-master/archlinuxarm/linux_xe303c12
4) makepkg -s
5) Press enter to choose N for the (NEW) features added
6) Exit the menu that comes up (after exiting, I saw a message about options being forced, which is good)
7) Watch it compile.

If all goes well, I will do a makepkg -i, and then go into the linux_xe303c12_firmware folder and do a makepkg -si as well.

EDIT: makepkg -i doesn't work on the running system as the new kernel and old kernel are conflicting packages - removing the currently-running kernel is likely not a good idea. I'll build the firmware, then find a USB key to boot off of.
m3lang3
 
Posts: 13
Joined: Mon Aug 31, 2020 4:35 pm

Re: Samsung XE303C12 / Ctrl-U not booting

Postby m3lang3 » Thu Aug 26, 2021 3:56 am

Success! Linux hostname 5.13.6-1 #1 SMP PREEMPT Wed Aug 25 12:08:46 EDT 2021 armv7l GNU/Linux

I booted off a USB stick with arch-chroot on it, then ran:

$this->bbcode_second_pass_code('', 'sudo mount /dev/mmcblk0p2 /mnt
arch-chroot /mnt
cd to the directory with the kernel
sudo pacman -R linux-armv7 linux-armv7-chromebook
makepkg -i
flashed to /dev/mmcblk0p1 (not sda1, which is the USB stick)
cd to the directory with firmware
makepkg -i
exit
umount /mnt
shutdown -r now
')

Hope this helps someone.
m3lang3
 
Posts: 13
Joined: Mon Aug 31, 2020 4:35 pm

Re: Samsung XE303C12 / Ctrl-U not booting

Postby armuseru » Sun Aug 29, 2021 7:57 pm

$this->bbcode_second_pass_quote('cdrigby', 'T')hanks for finding that armuseru. I will see if I can get it working on my own system.
Glad if it helped

$this->bbcode_second_pass_quote('m3lang3', 'r')emoving the currently-running kernel is likely not a good idea.

I guess this can do a non-conflict kernel
$this->bbcode_second_pass_code('', 'sed 's/vmlinux.kpart/another_kernel/g' -i PKGBUILD
sed 's/conflicts/# conflicts/g' -i PKGBUILD
sed 's/replaces/# replaces/g' -i PKGBUILD
makepkg')
armuseru
 
Posts: 34
Joined: Sat Jan 09, 2021 9:36 am
Top

Re: Samsung XE503C32 / Ctrl-U not booting

Postby mind5t0rm » Tue Aug 31, 2021 2:18 pm

Any luck with the latest kernel?

Did anyone try? Or do we have any info about when the kernel will be updated?

Thank you very much
mind5t0rm
 
Posts: 12
Joined: Mon Mar 22, 2021 2:39 pm

Re: Samsung XE303C12 / Ctrl-U not booting

Postby paddydetox » Tue Sep 28, 2021 12:34 am

I'm currently stuck on this step but with the XE503C12. I don't have a recovery USB as it is a first attempt on this device. I have removed the write-protect screw, unless there is TWO write-protect screws on this device, w hich there could be since there's two locations it could be. Pressing ESC+reload+Power tells me there is no chromeOS on USB device. clicking ctrl+U when powering on to normal attempts to boot from the USB, as the light starts flickering, but it kicks back to the dev page starter. Would love to get this up and running as I've not tried Arch yet in general and am excited!
paddydetox
 
Posts: 9
Joined: Mon Sep 27, 2021 7:13 pm

Re: Samsung XE303C12 / Ctrl-U not booting

Postby armuseru » Thu Sep 30, 2021 3:37 pm

$this->bbcode_second_pass_quote('paddydetox', ' ')but it kicks back to the dev page starter.

Probably it did not recognize kernel partition at usb-stick or usb-boot is still disabled. On xe303 boot from usb possible only from usb2 connector or sd-card, but not from usb3 (blue).

If I am not mistaken "screw work" needed only for uboot reflashing, to run linux it not required
https://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook-2#installation
armuseru
 
Posts: 34
Joined: Sat Jan 09, 2021 9:36 am
Top

Re: Samsung XE303C12 / Ctrl-U not booting

Postby paddydetox » Fri Oct 08, 2021 3:17 pm

I tried again with more success using the microSD method, but still could not get to boot. I didn't try a different USB port I was using the one on the left that is marked SS (not blue) but there is another normal speed one on the other side. I have disabled boot several times, I usually follow all instructions starting from the top. Just recently I did a full powerwash thinking that the previous chroot may be affecting things. I formatted the SD card I was using to do the attempts, and formatted the USB drive I was also using. I will try once more, starting from a fresh powerwash then using a USB in the standard port.
paddydetox
 
Posts: 9
Joined: Mon Sep 27, 2021 7:13 pm

Re: Samsung XE303C12 / Ctrl-U not booting

Postby armuseru » Sat Oct 09, 2021 10:59 am

After enabling developer mode no need to reset. If it still not boot from external storage try to reboot to chrome os and check is usb-boot enabled, for this execute from console as root crossystem (or crossystem | less or crossystem | more and so on). Result must be like this
$this->bbcode_second_pass_code('', '...
dev_boot_legacy = 0 # [RW/int] Enable developer mode boot Legacy OSes
dev_boot_signed_only = 0 # [RW/int] Enable developer mode boot only from official kernels
dev_boot_usb = 1 # [RW/int] Enable developer mode boot from USB/SD
...')
if not, execute crossystem dev_boot_usb=1 dev_boot_signed_only=0

Then inspect external disk like cgpt show /dev/mmcblk1 (or /dev/sda for pendrive)
$this->bbcode_second_pass_code('', ' start size part contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
8192 32768 1 Label: "Kernel"
Type: ChromeOS kernel
UUID: 200076F3-0E02-024A-9475-45D228E7146A
Attr: priority=10 tries=5 successful=1
40960 3813343 2 Label: "Root"
Type: ChromeOS rootfs
UUID: C4BCDA61-D9C5-1847-9E4A-46BCAF41E281
3854303 32 Sec GPT table
3854335 1 Sec GPT header')
There are must be 4Mb free space (8192*512/(1024*1024)) then chrome os kernel partition (16Mb=32768*512/(1024*1024)) then chrome os root partition (start at 8192+32768=40960). Boot attributes must be present too.

If after all this it won't boot, there might be something wrong with the external media or with the kernel. In the case of a kernel, you can reboot into Chrome OS, chroot into the Linux partition and install another kernel. Something like this
$this->bbcode_second_pass_code('', 'mount /dev/sda2 /mnt
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
chroot /mnt
pacman -S linux-peach
dd if=/boot/vmlinux.kpart of=/dev/sda1')
or try linux-armv7-rc-chromebook or linux-armv7-chromebook

upd2: I just notice that kernel flash file of linux-armv7-rc-chromebook or linux-armv7-chromebook are more than 8M and because of this uboot may fail to run it. When I experimenting with recompiling kernel uboot failed to recognize large kernels, in my case it run succesfull only with kernels less than 8M.
armuseru
 
Posts: 34
Joined: Sat Jan 09, 2021 9:36 am

PreviousNext

Return to Samsung

Who is online

Users browsing this forum: No registered users and 4 guests

cron