Talk:Kernel mode setting

From ArchWiki
Jump to: navigation, search

xorg-server 1.16

Wrt [1], AFAIK you need root rights if you're not using KMS too. -- Karol (talk) 17:58, 2 August 2014 (UTC)

Early KMS start for GMA500 chip set

My computer is a Poulsbo. intel_agp and i915 didn't work for me. I finally solved the problem by MODULES="gma500_gfx". Shall we mention this on this page? Haochen (talk) 19:33, 26 February 2015 (UTC)

My fonts are too tiny

This is an issue for HiDPI laptops. The solution to changing TTY font is very vague, and the link "See Fonts#Changing the default font" is broken. Can someone clarify how to do this, the right way. Jadelord (talk) 10:34, 11 February 2016 (UTC)

I think the link should be to Fonts#Console fonts. So for instance you could install terminus-font and run setfont ter-c32n. That should make the fonts a lot larger. See Fonts#Console fonts for how to list all available fonts and how to make it permanent. Lonaowna (talk) 11:19, 11 February 2016 (UTC)
Thanks! I managed to change it permanently by adding a consolefont hook in mkinitcpio.conf. The setfont command was not working for me, since I was trying it on a terminal emulator instead on TTY!
Good you managed to change it! In a terminal emulator it should be really simple.. For instance in GNOME Terminal you can simply do Edit->Profile Preferences->Custom font. But of course this is different for each one. Lonaowna (talk) 12:58, 11 February 2016 (UTC)

Is the advise to always disable "video=..." really a good one?

The advise:

At first, note that for any method you use, you should always disable:
 Any vga= options in your bootloader as these will conflict with the native resolution enabled by KMS.
 Any video= lines that enable a framebuffer that conflicts with the driver.

got me into trouble when I recently installed Arch for the first time. My monitor (a 4k TV) simply displays "Invalid Format" if I do not use any "video=" statement to set a compatible mode, and I wondered whether "that enable a framebuffer that conflicts with the driver" was a statement that was valid for the amdgpu KMS driver that I use.

Is there any more detailed information available on what "video=..." parameters could cause conflicts? --Lvml (talk) 19:13, 18 March 2017 (UTC)

question

> At first, note that for any method you use, you should always disable:
>
>    Any vga= options in your bootloader as these will conflict with the native resolution enabled by KMS.
>    Any video= lines that enable a framebuffer that conflicts with the driver.
>    Any other framebuffer drivers (such as uvesafb).

Does "disable" here mean, disable in my kernel config, or just in the grub boot parameters? It's very common to have framebuffer drivers built in to the kernel. Does that conflict with KMS?

--Njn (talk) 00:56, 29 September 2017 (UTC)

It's just about removing the parameters from the bootloader configuration etc. -- Lahwaacz (talk) 06:32, 29 September 2017 (UTC)