[SOLVED][Odroid-U3] How-to modify kernel parameters

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

[SOLVED][Odroid-U3] How-to modify kernel parameters

Postby AlexisTM » Mon Apr 07, 2014 2:07 pm

Dear sirs,

$this->bbcode_second_pass_quote('', 'E')DIT: for a perfectly clean boot with NO messages, use loglevel=-1
Working but I don't know if it is good to do


I would like to make a powerfull Kiosk with my Odroid-U3 on Archlinux, I would like to add the following parameters.
$this->bbcode_second_pass_code('', 'quiet loglevel=0 ')
I tried by creating a cmdline.txt file in /boot/cmdline.txt (like in Debian images) but it didn't worked.

Current (default) configuration
$this->bbcode_second_pass_code('', '[root@alarm ~]# cat /proc/cmdline
console=tty1 console=ttySAC1,115200 mem=2047M fbcon=map:1111111111111111111111111111 console=tty1 console=ttySAC1,115200n8 hdtv_type=dvi hdtv_format=1080p60hz root=/dev/mmcblk0p2 rootwait rw mem=')

Current (default) kernel
$this->bbcode_second_pass_code('', '[root@alarm ~]# uname -a
Linux alarm 3.8.13.19-2-ARCH #3 SMP PREEMPT Mon Mar 31 17:26:34 MDT 2014 armv7l GNU/Linux')

SOLUTION :

1). Modify the existing boot.txt file by adding your parameters in "bootargs" section or create a new with the following.
NOTE: this is for DVI, 1080p@60hz settings.
boot.txt
$this->bbcode_second_pass_code('', 'setenv fdt_high "0xffffffff"
setenv hdtv_type "dvi"
setenv hdtv_format "1080p60hz"
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; bootm 0x40008000"
setenv bootargs "console=tty1 console=ttySAC1,115200n8 hdtv_type=${hdtv_type} hdtv_format=${hdtv_format} root=/dev/mmcblk0p2 rootwait rw mem=2047M quiet loglevel=0"
boot')

2). Install mkimage
$this->bbcode_second_pass_code('', '# pacman -S uboot-mkimage')

3). Make the boot.scr via mkimage
$this->bbcode_second_pass_code('', 'mkimage -A arm -C none -T script -n 'Boot script for quiet ODROID-U3' -d /boot/boot.txt /boot/boot.scr')

Greetings,
Alexis
Last edited by AlexisTM on Thu Apr 10, 2014 8:17 am, edited 4 times in total.
AlexisTM
 
Posts: 12
Joined: Thu Apr 03, 2014 9:21 am

Re: [Odroid-U3] How-to modify kernel parameters

Postby mikmakmuk » Mon Apr 07, 2014 9:32 pm

Create a boot.txt in /boot with the following content
$this->bbcode_second_pass_code('', '
setenv fdt_high "0xffffffff"
setenv drm_video_mode "HDMI-A-1:1920x1080M@60"
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; bootm 0x40008000"
setenv bootargs "video=${drm_video_mode} console=tty1 console=ttySAC1,115200 mem=2047M fbcon=map:1111111111111111111111111111 root=/dev/mmcblk0p2 rootwait rw quiet loglevel=0"
boot
')

Then create a boot.scr with
$this->bbcode_second_pass_code('', '
mkimage -A arm -C none -T script -n 'Boot script for quiet ODROID-U3' -d boot.txt boot.scr
')

That *should* work, is however untested.
mikmakmuk
 
Posts: 6
Joined: Fri Apr 04, 2014 9:58 pm

Re: [Odroid-U3] How-to modify kernel parameters

Postby AlexisTM » Tue Apr 08, 2014 9:39 am

Thanks a lot, it is working!
(For next users who have same questions)

boot.txt
$this->bbcode_second_pass_code('', 'setenv fdt_high "0xffffffff"
setenv hdtv_type "dvi"
setenv hdtv_format "1080p60hz"
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; bootm 0x40008000"
setenv bootargs "console=tty1 console=ttySAC1,115200n8 hdtv_type=${hdtv_type} hdtv_format=${hdtv_format} root=/dev/mmcblk0p2 rootwait rw mem=2047M quiet loglevel=0"
boot')

$this->bbcode_second_pass_code('', 'mkimage -A arm -C none -T script -n 'Archie quiet OdroidU3' -d boot.txt boot.scr')

Now, I have still a problem to hide the [ OK ] messages. I tried to use Plymouth (like one the RasPi) but it didn't worked.
Nothing happens even when I do
$this->bbcode_second_pass_code('', 'plymouthd; plymouth --show-splash; sleep 10; plymouth --quit')
But It will be another subject! :D

Thanks again mikmakmuk!
AlexisTM
 
Posts: 12
Joined: Thu Apr 03, 2014 9:21 am

Re: [SOLVED][Odroid-U3] How-to modify kernel parameters

Postby pepedog » Tue Apr 08, 2014 10:56 am

[OK] comes from console=tty1 (which I personally like)
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: [SOLVED][Odroid-U3] How-to modify kernel parameters

Postby AlexisTM » Tue Apr 08, 2014 11:50 am

I also like it! For personal usage...

But on a KIOSK, this frighten the client...
AlexisTM
 
Posts: 12
Joined: Thu Apr 03, 2014 9:21 am

Re: [SOLVED][Odroid-U3] How-to modify kernel parameters

Postby WarheadsSE » Tue Apr 08, 2014 8:55 pm

OMG it said OK!

(just remove the 'console=tty1' bit)
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [SOLVED][Odroid-U3] How-to modify kernel parameters

Postby AlexisTM » Wed Apr 09, 2014 8:12 am

Dear,

I tried without the console=tty1 in boot.scr and by adding initrd=initrd.img but [ OK ] messages are still showed and Plymouth is not showing even if we can read " [ OK ]Started Show Plymouth Boot Screen."
I will create a new subject, it is a bit far of the initial title! :o

$this->bbcode_second_pass_code('', 'setenv fdt_high "0xffffffff"
setenv hdtv_type "dvi"
setenv hdtv_format "1080p60hz"
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; bootm 0x40008000"
setenv bootargs "console=ttySAC1,115200n8 hdtv_type=${hdtv_type} hdtv_format=${hdtv_format} initrd=initrd.img root=/dev/mmcblk0p2 rootwait rw mem=2047M splash quiet loglevel=0"
boot')

$this->bbcode_second_pass_code('', ' Starting Load/Save Random Seed...
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Load/Save Random Seed.
Starting udev Kernel Device Manager...
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Started udev Kernel Device Manager.
[ OK ] Found device /dev/ttySAC1.
[ OK ] Reached target Sound Card.
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Paths.
[ OK ] Found device 9730.
[ OK ] Found device /dev/mmcblk0p1.
Mounting /boot...
[ OK ] Mounted /boot.
[ OK ] Reached target Local File Systems.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Create Volatile Files and Directories...
Starting Trigger Flushing of Journal to Persistent Storage...
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Timers.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting OpenSSH Daemon...
[ OK ] Started OpenSSH Daemon.
Starting Automatic wired network connection using netctl profiles...
[ OK ] Started Automatic wired network connection using netctl profiles.
Starting reachable /dev/ump and /dev/mali...
Starting Apply cpupower configuration...
Starting Entropy Harvesting Daemon...
Starting Permit User Sessions...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
Starting Login Service...
[ OK ] Started Apply cpupower configuration.
[ OK ] Started Entropy Harvesting Daemon.
[ OK ] Started Permit User Sessions.
[ OK ] Started reachable /dev/ump and /dev/mali.
Starting Wait for Plymouth Boot Screen to Quit...
Starting Terminate Plymouth Boot Screen...
[ OK ] Started Login Service.')
AlexisTM
 
Posts: 12
Joined: Thu Apr 03, 2014 9:21 am


Return to Samsung

Who is online

Users browsing this forum: No registered users and 9 guests