Missing Kernel parameters compared to Ubuntu Kernel

This forum is for topics dealing with problems with software specifically in the ARMv7h repo.

Missing Kernel parameters compared to Ubuntu Kernel

Postby bmentink » Wed Dec 09, 2015 6:32 pm

Hi All,

It seems the Arch kernel does not support some kernel parameters that the Ubuntu kernel does.
For example in boot.ini :

setenv HPD "true" # hot plug detect
setenv governor "ondemand" # set default governor

.. and there are probably others.

I need at least support for the 1st one, as when I turn off my monitor it triggers the kodi black screen issue which locks up the box, forcing a reboot. (yes, I am aware the kodi issue is being worked on, but a good workaround in the meantime, is to turn off hot plug detect)

I am running, from memory, a 3.10.92 kernel at the moment ..
Is there a kernel that has this stuff in boot.ini?

By the way, my boot.ini and other files look way out of date:
$this->bbcode_second_pass_code('', 'ls -l /boot/
total 4096
-rw-r--r-- 1 root root 15616 Aug 30 2014 bl1.bin
-rw-r--r-- 1 root root 14592 Aug 30 2014 bl2.bin
-rw-r--r-- 1 root root 2019 Aug 30 2014 boot.ini
drwxr-xr-x 2 root root 4096 Dec 8 09:57 dtbs
-rwxr-xr-x 1 root root 1744 Aug 30 2014 sd_fusing.sh
-rw-r--r-- 1 root root 262144 Aug 30 2014 tzsw.bin
-rw-r--r-- 1 root root 331668 Aug 30 2014 u-boot.bin
-rwxr-xr-x 1 root root 3553896 Nov 24 14:37 zImage
')

.. and for completeness, here is my boot.ini
$this->bbcode_second_pass_code('', 'ODROIDXU-UBOOT-CONFIG

# U-Boot Parameters
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"

# Mac address configuration
setenv macaddr "00:1e:06:61:7a:39"

#------------------------------------------------------------------------------------------------------
# Basic Arch Linux ARM Setup. Don't touch unless you know what you are doing.
# --------------------------------
setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=/dev/mmcblk0p1 rootwait rw"

# boot commands
setenv bootcmd "ext4load mmc 0:1 0x40008000 /boot/zImage; ext4load mmc 0:1 0x44000000 /boot/dtbs/exynos5422-odroidxu3.dtb; bootz 0x40008000 - 0x44000000"

# --- Screen Configuration for HDMI --- #
# ---------------------------------------
# Uncomment only ONE line! Leave all commented for automatic selection.
# Uncomment only the setenv line!
# ---------------------------------------
# ODROID-VU forced resolution
# setenv videoconfig "video=HDMI-A-1:1280x800@60"
# -----------------------------------------------
# 1920x1080 (1080P) with monitor provided EDID information. (1080p-edid)
# setenv videoconfig "video=HDMI-A-1:1920x1080@60"
# -----------------------------------------------
# 1920x1080 (1080P) without monitor data using generic information (1080p-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080.bin"
# -----------------------------------------------
# 1280x720 (720P) with monitor provided EDID information. (720p-edid)
# setenv videoconfig "video=HDMI-A-1:1280x720@60"
# -----------------------------------------------
# 1280x720 (720P) without monitor data using generic information (720p-noedid)
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x720.bin"
# -----------------------------------------------
# 1024x768 without monitor data using generic information
# setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin"


# final boot args
setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr}"
# drm.debug=0xff
# Boot the board
boot')

EDIT: It seems uboot owns boot.ini, so why is uboot so old?
$this->bbcode_second_pass_code('', 'pacman -Qo /boot/boot.ini
/boot/boot.ini is owned by uboot-odroid-xu3 2012.07-3
')
Last edited by bmentink on Wed Dec 09, 2015 9:20 pm, edited 1 time in total.
bmentink
 
Posts: 81
Joined: Mon Sep 12, 2011 2:51 am

Re: Missing Kernel parameters compared to Ubuntu Kernel

Postby WarheadsSE » Wed Dec 09, 2015 8:54 pm

mdrjr is aware of this.

IIRC, the problem is that it the uboot package from HK currently doesn't want to build with gcc 5.2
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Missing Kernel parameters compared to Ubuntu Kernel

Postby bmentink » Thu Dec 10, 2015 3:30 am

I don't think it matters what the version of bootloader is on there, the issue is that the kernel needs to respond to the passed parameters ... that needs to be sorted by extra configuration of the kernel by whoever is maintaining that ....
bmentink
 
Posts: 81
Joined: Mon Sep 12, 2011 2:51 am

Re: Missing Kernel parameters compared to Ubuntu Kernel

Postby moonman » Thu Dec 10, 2015 10:05 am

Have you tried just putting these lines in boot.ini? boot.ini is the file read by U-Boot, not the kernel. U-Boot in turn will pass these arhuments to the kernel. If boot.ini is missing some lines (commented out lines) it does not mean it does not support using them.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Missing Kernel parameters compared to Ubuntu Kernel

Postby bmentink » Thu Dec 10, 2015 5:47 pm

Yes, I have tried putting at least the governor lines in the boot.ini file ... for example, set to ondemand, but after boot the governor is still set to performance.

Yes, I do know the boot.ini file is read by uboot and I do know that the bootargs line towards the bottom is what is passed to the kernel. @moonman, you are not reading this thread properly, otherwise you would see the boot.ini I posted which does NOT have any uncommented lines for those items I refer to ..... there is on the Ubuntu boot.ini, because they SUPPORT them in the kernel ;)

The problem is with kernel support for these things, no use passing them if the kernel ignores them. From comments in other threads, these kernel parameters are have just not been supported. Who is responsible for the ArchArm kernel?
-----
By the way the lines I am putting in boot.ini for the governor are:
$this->bbcode_second_pass_quote('', 's')etenv governor "ondemand"


and modify bootargs to read:
$this->bbcode_second_pass_quote('', 's')etenv bootargs "${bootrootfs} ${governor} ${videoconfig} smsc95xx.macaddr=${macaddr}"
bmentink
 
Posts: 81
Joined: Mon Sep 12, 2011 2:51 am


Return to ARMv7h

Who is online

Users browsing this forum: No registered users and 7 guests