I just installed ATI/Radeon driver according this wiki: https://wiki.gentoo.org/wiki/Fglrx
and everything working nice, however during booting stage there is low resolution.
I tried to follow grub wiki: https://wiki.gentoo.org/wiki/GRUB2#Using framebuffer display features display but no any change.
Please advise how to work it out and why in some drivers it is automatically setting and in others not?_________________“You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...”

The first question to ask is are you booting in Bios or EFI mode? Because the framebuffer drivers available are not the same in each mode. I haven't use Fglrx since long but, to have something else than Vga resolution, you need to use vesafb or uvesafb as primary framebuffer for Bios mode. In Efi mode, you have efifb. simple framebuffer may be available too.

You have to make a search about which frambuffer drivers works in Bios and Efi mode with Fglrx. You may not have the native resolution of the screen. I depend on the features of the framebuffer driver in use. There will be a time steep between Linux video framebuffer driver and Xorg fglrx driver when you switch from Xorg terminal to virtual terminal and reverse.

If I am right, only Linux frambuffers who support KMS like nouveau, radeon and i915 give synchronisation between Linux and Xorg nouveau, radeon and intel video drivers.

According with the first link you give, Uvesafb seem's good with Fglrx. There's a link to._________________Paul

Thanks for your nice explanation!
I am booting with Bios and followed the link in Fglrx's wiki that you mentioned: https://wiki.gentoo.org/wiki/Uvesafb
I have a problem with 'Initramfs inclusion' chapter: I guess that I have to have initramfs, in order to get right resolution - Right?
However if configure the kernel like this I get panic error during booting (BTW: the resolution is nice in this case):

So I guess need to: 'Use dracut, genkernel, or another initramfs generator of choice to rebuild the initramfs.'
Please advise what tool to choose in order to rebuild initramfs? Just note that I am not using genkernel to build my kernel.
I added GRUB_CMDLINE_LINUX_DEFAULT="linux video=uvesafb:1240x1024-32,mtrr:3,ywrap" in /etc/default/grub according the wiki.

Quote:

If I am right, only Linux frambuffers who support KMS like nouveau, radeon and i915 give synchronisation between Linux and Xorg nouveau, radeon and intel video drivers.

When I used opensource radeon driver, I did not have resolution problem.
It just happened when I switched to propriety Fglrx... I thought it would be easier to work it out _________________“You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...”

If you added things that you want to work before root is mounted, you need to update the initrd.
If you don't mind waiting until root mounts to switch to framebuffer, your initrd may be OK._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

AFAIK after reading this wiki: https://wiki.gentoo.org/wiki/Initramfs/Guide I do not need initrd or initramfs.
So in order to have right resolution during boot stage I followed https://wiki.gentoo.org/wiki/Uvesafb and all steps were done except initramfs rebuild.
However still there is low resolution in booting. I faced this issue since switched from Radeon opensource driver to Fglrx propriety driver.
Please advise how to debug in order to find out the exact missing factor?_________________“You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...”

Try vesafb in the kernel. The binary blob video drivers in general, do not play nicely with framebuffer consoles.
The nVidia driver emits dire warnings in dmesg. Its been a while since I used fglrx.
The problem is the same in both cases. The binary blobs assume that they have exclusive control of the Graphics chip.
When a framebuffer driver grabs it, or changes settings, things start to not work.

You need to choose a framebuffer driver that does not attempt to configure any hardware.
That doesn't leave many.

Post your grub.cfg, possibly on a pastebin. It may be that the resolution settings are not being passed to the kernel._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

To be sure that it is Uvesafb who is the active framebuffer, disable any other framebuffer in the Linux kernel configuration including vga. Your kernel configuration can be helpfull.

After booting check the kernel boot parameters. Show us

Code:

cat /proc/cmdline

to be sure that the uvesafb parameters have been pass correctly to the kernel. Check if /dev/fb0 exist. In dmesg look for vga, vesa and uvesafb messages to know which driver in fact control the Linux display.

You can try Vesafb instead of Uvesafb. In Bios mode it work out of the box but can only give 4/3 resolutions. I ever use Uvesafb and I have been able to make it work with Fglrx I think._________________Paul

Last edited by Logicien on Sun Aug 21, 2016 9:18 am; edited 2 times in total

Thanks for your support! Your advise looks the right way to find out what is wrong..
Here my kernel configuration - Hope this is the right file (what name and where this file is located?) - I took it from /usr/src/linux > kwrite .config:
http://pastebin.com/Bdw9Hsd6
I disabled any other framebuffer in the Linux kernel configuration - still low resolution...

If you do not use an initramfs, remove the line "initrd /path/to/the/initramfs" otherwise, give the full path to the initramfs. Update the Grub2 configuration file with grub2-mkconfig and use this entry to boot next time.

Just a question: is the package sys-apps/v86d have been emerged and does the file /usr/share/v86d/initramfs exist?_________________Paul

If you have an initramfs in your Grub entry it may conflict with /usr/share/v86d/initramfs in the kernel image. An alternative is to give /usr/share/v86d/initramfs as an initramfs in a Grub entry. Otherwise you can try Vesafb.

About the entry I suggest to you, the line set root=(hd0,4) may have to be ajust to the good partition where is /vmlinuz-4.4.6-gentoo .