LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Closed Thread
  Search this Thread
Old 12-18-2004, 02:13 AM   #1
vaworx
Member
 
Registered: Nov 2003
Location: Honolulu/HI
Distribution: Slackware current, FreeBSD 4.10, 5.4, 6.2, Debian, RedHat, CentOS, Sun Cobalt OS
Posts: 66

Rep: Reputation: 15
Frame Buffer Problem !!!


I gave up on this one already. I was searching for a solutions but seems like i cannot find any so i decided to post this thread and ask for suggestions. I've checked every possible HOWTO but still nothing. Here is the situation.

Distro: Slackware-current Kernel: kernel-2.6.9 Video: Integrated i810

Everything worked just fine 15mins total kernel config+compile+tune up-=> voila everything's working just fine, BUT something is bothering me and i cannot fix it. The frame buffer resolution is working on "640x480-60" which is i suppose the lowest standard. It's kinda ugly to leave the resolution in console that low and i wanted to higher it a lil bit maybe up to 1024x768-70 but nope it didn't work. I've tried every single option in /etc/fb.mode but nothing. What i get after running fbset is:

<vladimir@localhost>$fbset 1024x768-70
ioctl FBIOPUT_VSCREENINFO: Invalid argument.
<vladimir@localhost>$fbset --all 1024x768-70
ioctl FBIOPUT_VSCREENINFO: Invalid argument.

Any ideas?

Last edited by vaworx; 12-18-2004 at 02:26 AM.
 
Old 12-18-2004, 06:52 PM   #2
slightcrazed
Member
 
Registered: May 2003
Location: Lisbon Falls, Maine
Distribution: RH 8.0, 9.0, FC2 - 4, Slack 9.0 - 10.2, Knoppix 3.4 - 4.0, LFS,
Posts: 789

Rep: Reputation: 30
I believe that this is best done in your lilo.conf. See below:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
You *should* have somethign that looks like the above in your lilo.conf. Just uncomment the line that matches the resolution that you want your frame buffer console to use, rerun lilo (i.e. type lilo as root) and restart.

:-)

slight
 
Old 12-18-2004, 06:59 PM   #3
vaworx
Member
 
Registered: Nov 2003
Location: Honolulu/HI
Distribution: Slackware current, FreeBSD 4.10, 5.4, 6.2, Debian, RedHat, CentOS, Sun Cobalt OS
Posts: 66

Original Poster
Rep: Reputation: 15
it should but it does not work -=> the only option that works is @ 640x480 for some reason. I was thinking maybe it's a hardware issue -=> i was told that i810 and the frame buffer don't work that well but i don't know, actually i was told that it doesn't work at all -=> still researching though so let's see
 
Old 12-18-2004, 09:45 PM   #4
slightcrazed
Member
 
Registered: May 2003
Location: Lisbon Falls, Maine
Distribution: RH 8.0, 9.0, FC2 - 4, Slack 9.0 - 10.2, Knoppix 3.4 - 4.0, LFS,
Posts: 789

Rep: Reputation: 30
It is very possible that maybe that particular video adapter does not support frame buffers..... I don't know much about the i810 but I do know some adapters, especially on board adapters, do not include frame buffer support.

slight
 
Old 12-20-2004, 03:00 AM   #5
XavierP
Moderator
 
Registered: Nov 2002
Location: Kent, England
Distribution: Debian Testing
Posts: 19,192
Blog Entries: 4

Rep: Reputation: 474Reputation: 474Reputation: 474Reputation: 474Reputation: 474
Please do not post the same thread in more than one forum. Picking the most relevant forum and posting it once there makes it easier for other members to help you and keeps the discussion all in one place.

http://www.linuxquestions.org/rules.php

See Here: http://www.linuxquestions.org/questi...96#post1356596
 
  


Closed Thread


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
trying to use losetup, ioctl tells me argument is invalid Ephracis Linux - Software 3 03-26-2005 10:11 AM
alsamixer invalid argument subaruwrx Linux - Software 1 03-12-2005 01:34 PM
What is the replacement for sizeof() in the third argument for IOCTL commands yogeshwar_s Linux - Software 0 12-30-2004 07:48 AM
ioctl FBIOPAN_DISPLAY: Invalid Argument Andry Linux - Hardware 2 12-27-2004 10:55 PM
xawtv - invalid argument liguorir Linux - Software 0 06-17-2003 08:55 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 06:48 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration