LinuxQuestions.org - [SOLVED] bananapi pro,display on monitor is 1" too far left

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - bananapi pro,display on monitor is 1" too far left (https://www.linuxquestions.org/questions/slackware-arm-108/bananapi-pro-display-on-monitor-is-1-too-far-left-4175648578/)

Quote:

Originally Posted by SCerovec (Post 5966181)

(a double HDMI KVM sort of switch - something)?

I'll pass on that.

I have what I need display wise, quirky workarounds are ok, thanks for the help.

Not sure if should be starting new thread but may be related to my disp.screen0_output_mode questions.

Quote:

/PROC/CMDLINE
This file shows the parameters passed to the kernel at the time it is started.

Is /proc/cmdline supposed to indicate the generic boot configurations as in "setenv bootcmd_generic..."? Or is /proc/cmdline not the same in arm as in x86_64?

I entered in the following order

Code:

setenv bootcmd_generic 'debug earlyprintk sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 disp.screen0_output_mode=EDID:1366x768p60 hdmi.audio=EDID:1'

Code:

printenv bootcmd_generic

Quote:

bootcmd_generic=debug earlyprintk sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 disp.screen0_output_mode=EDID:1366x768p60 hdmi.audio=EDID:1

Code:

saveenv

Quote:

Saving Environment to MMC...
Writing to MMC(0)... done

After reset and booting,

Code:

cat /proc/cmdline

Quote:

debug earlyprintk sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 disp.screen0_output_mode=EDID:1280x720p50 hdmi.audio=EDID:0 root=/dev/sda2 waitforroot=3 rootfstype=ext4

This is not what was saveenv in bootcmd_generic:

Quote:

disp.screen0_output_mode=EDID:1280x720p50 hdmi.audio=EDID:0

Maybe I'm not understanding something somewhere? Thank you

Quote:

Originally Posted by glorsplitz (Post 5966909)

Is /proc/cmdline supposed to indicate the generic boot configurations as in "setenv bootcmd_generic..."? Or is /proc/cmdline not the same in arm as in x86_64?

Ah, I scratched my head over this one a while back as well. I've added this to -current's installation document:

Code:

    IMPORTANT NOTE - Changing Linux Kernel boot parameters

    ||||||||||||||||||||||||||||||||||||||||||||||||||||||

    If you'd like to change the console output in the future (or any Linux Kernel

    command line value), you'd need to update the variable you're interested in

    (e.g. the 'slkconsole' U-Boot variable), _and_ re-enter the

    ''setenv bootargs "${slkconsole}....'' commands (see later post installation

      section further down this document), followed by 'saveenv'.

    This is due to the way U-Boot evaluates the variables.

Try re-entering your bootargs, and it ought to work.
I had assumed that U-Boot would process the variables dynamically, but it doesn't - you set the variables, and it evaluates them and stores the result.

That was it drmozes, thank you!

Code:

setenv bootcmd_generic 'debug earlyprintk sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 disp.screen0_output_mode=EDID:1366x768p60 hdmi.audio=EDID:1'

setenv bootargs "${slkconsole} ${bootcmd_generic} root=/dev/sda2 waitforroot=3 rootfstype=ext4"

saveenv

reset

Code:

cat /proc/cmdline 

console=tty1 debug earlyprintk sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 disp.screen0_output_mode=EDID:1366x768p60 hdmi.audio=EDID:1 root=/dev/sda2 waitforroot=3 rootfstype=ext4