[Bug 625832] Re: [Maverick] plymouth falls to text mode even if graphic mode worked before

[Claudio Moretti]

@Steve, I'm following a guide which says I need to replace vesafb with uvesafb in order to make framebuffer work.
One of the commands it says I have to launch is
$ sudo hwinfo --framebuffer

Here's the output I got (before installing v86d):
root at Jarvis:~# hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.464]
  Unique ID: rdCR.zrHRJLheAS6
  Hardware Class: framebuffer
  Model: "NVIDIA G84 Board - p410h1b "
  Vendor: "NVIDIA Corporation"
  Device: "G84 Board - p410h1b "
  SubVendor: "NVIDIA"
  SubDevice: 
  Revision: "Chip Rev"
  Memory Size: 14 MB
  Memory Range: 0xfb000000-0xfbdfffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  Mode 0x033e: 640x400 (+2560), 24 bits
  Mode 0x0345: 1600x1200 (+1600), 8 bits
  Mode 0x0346: 1600x1200 (+3200), 16 bits
  Mode 0x0347: 1400x1050 (+1400), 8 bits
  Mode 0x0348: 1400x1050 (+2800), 16 bits
  Mode 0x0349: 1400x1050 (+5600), 24 bits
  Mode 0x034a: 1600x1200 (+6400), 24 bits
  Mode 0x0352: 2048x1536 (+8192), 24 bits
  Mode 0x0360: 1280x800 (+1280), 8 bits
  Mode 0x0361: 1280x800 (+5120), 24 bits
  Mode 0x0362: 768x480 (+768), 8 bits
  Mode 0x0364: 1440x900 (+1440), 8 bits
  Mode 0x0365: 1440x900 (+5760), 24 bits
  Mode 0x0368: 1680x1050 (+1680), 8 bits
  Mode 0x0369: 1680x1050 (+6720), 24 bits
  Mode 0x037c: 1920x1200 (+1920), 8 bits
  Mode 0x037d: 1920x1200 (+7680), 24 bits
  Config Status: cfg=new, avail=yes, need=no, active=unknown

I'm looking at the last line: even if I don't know what it means with
cfg=new (even if I know that cfg stands for config), I see that, in my
opinion, framebuffer is available, not needed (understandable, as X.Org
does his job), but it's impossible to determine whether it's active or
not, which is my point: why does that happen?

I'm just trying to guess, I hope you'll understand this better than me.

Here's the guide I'm following (although I have not followed it
completely yet, so I DO NOT RECOMMEND trying it. For what that matters
:D)

https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-
resolution-plymouth-virtual-terminal-for-atinvidia-cards-with-
proprietaryrestricted-driver/

-- 
[Maverick] plymouth falls to text mode even if graphic mode worked before
https://bugs.launchpad.net/bugs/625832
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.