Console framebuffer for ATI HD3200 and 16/9 screen
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Console framebuffer for ATI HD3200 and 16/9 screen
Hello folks,
Well, I'm quite n00b with Linux and decide to explore further more and thus I'd rather command line tips.
So I'm trying to configure the console framebuffer at boot. You know vesafb...
At this moment I'm able to make it run using the vesafb driver but I doubt that this is optimal configuration because it look a bit slow and don't support the formant and then the resolution of my screen. I found something about 16/9 screens for drivers using modedb like atyfb but I'm not safe with the boot options.
Here is my hardware configuration :
- Radeon HD 3200 with 256mb dedicated memory
- A LCD 16/10 screen capable of maximal resolution of 1280x800
About software :
- Slackware64 13.0 with kernel 2.6.29.6
- LILO as the boot loader
- ATI proprietary driver (fglrx) for 3d acceleration
I read several documents as much on Internet as in kernel docs but nothing seem to fit my needs.
Which one between radeonfb and atyfb, or anything else, do I have to use and how to configure the boot options?
P.S.: Since I'm not a native English speaker and still learning, some sentences may sound a bit odd. Then, don't be shy about asking what I exactly mean or even correcting me. I'm always glad to receive a useful comments.
This may not be helpfull, but I'd forget about the framebuffer and just hope it looks after itself. As you probably know the main reason a framebuffer would be trouble is if you got 'shearing' or 'tearing' of a video picture. This is due to the framebuffer and the monitor screen being out of sync: so that the screen is refreshed from the framebuffer before the framebuffer has got the full new picture, so you get the old picture and then a shear and then the new picture.
Well since you're using Lilo and I use Grub I don't know what configuration file to ask you for I'm just going to ask you to give us the contents of your Lilo boot configuration file. That should have something about vga resolution if you want framebuffer. Also run "fbset" in a console -- not x -- and give us the output of that.
Above all, thx for answering my thread. But, it's OK about that.
If I enable vesafg, for example, the listing of big directory is very slow. I'm close to read each file name. That's what I mean by "slow". But the refresh rate seems to be synchronized with the framebuffer since I've no 'shearing', 'tearing', 'flickering' or 'blinking'. I used fdiba, which contains fbgs, to read pdf documents and it's awesome.
I'm just annoyed about the slow listing or anything else that move and want understand more for learning purpose.
Even if you didn't answered my question, your answer wasn't helpless 'cause now I understand a bit more the mechanism.
thx a lot
Last edited by JonTn; 12-30-2009 at 05:19 PM.
Reason: ahm! correct a language mistake :redface:
Well since you're using Lilo and I use Grub I don't know what configuration file to ask you for I'm just going to ask you to give us the contents of your Lilo boot configuration file. That should have something about vga resolution if you want framebuffer. Also run "fbset" in a console -- not x -- and give us the output of that.
I think both (LILO and Grub) use the same way for kernel command.
Here is a sample :
Code:
grub.conf File That Supports Serial Console
#boot=/dev/hda
# Options added for serial console
serial --unit=0 --speed=9600 \
--word=8 --parity=no --stop=1
terminal --timeout=10 serial console
default=0
timeout=10
title Red Hat Linux (2.4.20-8)
root (hd0,1)
kernel /vmlinuz-2.4.20-8 ro \
root=LABEL=/ console=ttyS0,9600n8
initrd /initrd-2.4.20-8.img
Code:
lilo.conf with Serial Console Support
serial=0,9600n8
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=Linux
image=/boot/vmlinuz-2.4.20-8
label=2.4.20-8
read-only
initrd=/boot/initrd-2.4.20-8.img
append="root=LABEL=/ console=ttyS0,9600n8"
As you can see, it's quite similar. Grub take these arguments in kernel while lilo take them in append.
Since every documentation I've seen are "bootloader independant", I think the syntax is always the same.
I think both (LILO and Grub) use the same way for kernel command.
Here is a sample :
Code:
grub.conf File That Supports Serial Console
#boot=/dev/hda
# Options added for serial console
serial --unit=0 --speed=9600 \
--word=8 --parity=no --stop=1
terminal --timeout=10 serial console
default=0
timeout=10
title Red Hat Linux (2.4.20-8)
root (hd0,1)
kernel /vmlinuz-2.4.20-8 ro \
root=LABEL=/ console=ttyS0,9600n8
initrd /initrd-2.4.20-8.img
Code:
lilo.conf with Serial Console Support
serial=0,9600n8
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=Linux
image=/boot/vmlinuz-2.4.20-8
label=2.4.20-8
read-only
initrd=/boot/initrd-2.4.20-8.img
append="root=LABEL=/ console=ttyS0,9600n8"
As you can see, it's quite similar. Grub take these arguments in kernel while lilo take them in append.
Since every documentation I've seen are "bootloader independant", I think the syntax is always the same.
Gosh, you've completely lost me with all that. The only thing looks familiar to me there is your mention of "ttyS0", which I use /dev/ttyS0 as the serial port to which my dial-up modem is connected. The only reference I use in my grub.conf to implement the framebuffer is an addition to the end of the "kernel" line, that of "vga=0x315" to get an 800x600 resolution frambuffer I can use fbi image viewer, etc.
vesafb will not give you 1280x800 because it's not a vesa mode. Nor does radeonfb or atyfb support your GPU (radeonfb only supports up to the x850, iirc).
I followed the instructions to enable the kms driver but, unfortunately, I got a black screen during the boot time. Perhaps this experimental driver does not work with a Radeon HD 3200 for now. I will try again in a few time. Until that I will use the vesafb to have graphic in console mode.
Radeon KMS definitely supports the HD3200 in kernel 2.6.32. You would need/want to compile the framebuffer console into the kernel, but disable any other framebuffer drivers. Then compile radeon DRM as a module or also into the kernel.
Yep! I read a lot in Documentations/fb/* but nothing seems to work with my device (HD 3200) except vesafb.
Probably it's not supported. vesafb is a generic driver so .. too bad.. Maybe you can check the new kernel source?... Or maybe you need to use the real driver (non-framebuffer) for ATI? If it does exist, it's probably a third party driver like NVIDIA's. You can check it somewhere in the ATI website.
Quote:
This week, I'm moving for the university then I'll give some news about it the next week.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.