LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices



Reply
 
Search this Thread
Old 11-14-2004, 03:12 PM   #1
rabidundead
Member
 
Registered: Apr 2001
Location: Earth
Distribution: Trying to get GENTOO 2004.2 INSTALLED... Weeeee!!!!
Posts: 67

Rep: Reputation: 15
trident cyberblade 9397 w/ linux 2.6 -- framebuffer (solved)


Problem:

I am trying to get a framebuffer console working on an IBM ThinkPad 770 with a Trident CyberBlade 9397 display. I have had it work before many times at 1024x768 with kernel 2.4.21 and various distros. However, I cannot get any but the default console mode working with kernel 2.6.7.

Background info:

For kernel 2.4 the argument 'vga=791' worked great. I was using LILO then and I am aware that LILO interprets this parameter and sets the mode, not the kernel.

My display is capable of 1024x768 at 16bpp, though, I don't know the refresh rate of that mode.

According to < http://www.icewalkers.com/Linux/Howt...r-HOWTO-5.html >, the Trident CyberBlade is VESA 2.0-compliant, so I assume that the kernel 2.6 'vesafb' support should work.

I also know from various web resources that, although the 'tridentfb' driver mentions possible support for this display, it, in fact, does not work with my display.

Current situation:

I am upgrading to kernel 2.6.7. I included 'framebuffer support', 'vesafb', 'vga16fb' (basically all of the generic framebuffer support I could find) as built-ins to the kernel via menuconfig.

I did build the 'tridentfb' driver as a built-in also, though when I specify it as the driver to use via the kernel argument 'video=", I get nothing but a blank screenwhile the system boots.

Using 'video=mtrr.vesa:1024x768' drops to normal console mode.

Using 'video=vesafb' does the same, even if i add ':1024x768' or such to the line

Using 'vga=791' does the same, and AFAIK, is supposed to not work with this kernel anyway.. obsoleted in favor of the 'video=' syntax

One more piece of info:

As this may be a gotcha, I think it may be helpful to point out that I am not using LILO as the bootloader this time around, having opted to migrate to GRUB.

Anyway:

Anybody having any clue in this arena (including links to thorough documentation on the linux 2.6 'video=' syntax and all available options, etc. -- as I am not above RTFM-ing this problem) would be most appreciated.

Regards

Last edited by rabidundead; 11-14-2004 at 09:02 PM.
 
Old 11-14-2004, 06:45 PM   #2
rabidundead
Member
 
Registered: Apr 2001
Location: Earth
Distribution: Trying to get GENTOO 2004.2 INSTALLED... Weeeee!!!!
Posts: 67

Original Poster
Rep: Reputation: 15
Update:

New situation

I have recompiled and installed the kernel without 'tridentfb' at all

I am assuming that this driver is responsible for every test involving the 'vesafb' to result in a blank screen regardless of the boot-time "video=" kernel arguments i put in.

Results:

While it did alleviate the blank screen issue, i still only get standard console mode using either the "vga=" or "video=" syntax.

So, still not home, yet...
 
Old 11-14-2004, 08:38 PM   #3
rabidundead
Member
 
Registered: Apr 2001
Location: Earth
Distribution: Trying to get GENTOO 2004.2 INSTALLED... Weeeee!!!!
Posts: 67

Original Poster
Rep: Reputation: 15
Solved

The "tridentfb" was a problem, not a solution.. it caused one part of the problem. The other part was following the general advice to use the "video=" syntax.. as I have successfully got my console at 1024x768 with a nice Tux logo despite this.

Details:

I recompiled the kernel making these changes:
  1. removed the "tridentfb" driver completely -- as in: it's not a module or a built-in
  2. removed the "vga16fb" driver, as well
For GRUB, I used the "vga=791" boot argument instead of the "video=" argument.

Anyway:

Problem solved

Regards
 
  


Reply


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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
installation problem: screen freezes. Video card: trident cyberblade-i7 polaco Linux - Newbie 1 10-23-2005 02:35 PM
Newbie, installed Slack 10.1, X11 gives blank screen on Trident CyberBlade i1. UnnDunn Slackware 6 03-11-2005 11:57 AM
Trident Cyberblade - multiple X log entries. mcleodnine Linux - Hardware 1 04-17-2003 06:15 AM
Problems with X on Trident CyberBlade/i7 byoungwjy Linux - Software 0 10-21-2002 02:57 PM
Trident Cyberblade and Red Hat 7.2 won't work 2gethet linuxlah Linux - Hardware 3 09-01-2002 04:19 PM


All times are GMT -5. The time now is 02:44 PM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration