Bug 524634

Summary: Error message displayed at start of boot
Product: [Fedora] Fedora Reporter: Quentin Armitage <quentin>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: airlied, ajax, bskeggs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-21 23:34:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Quentin Armitage 2009-09-21 15:00:10 UTC 
Description of problem:
The following error message is displayed at the start of the boot sequence:
nvidia-control: failed to evaluate _DSM: 5
nouveau 0000:01:00.0: No pointer to output script table
nouveau 0000:01:00.0: No pointer to output script table
nouveau 0000:01:00.0: No pointer to output script table
nouveau 0000:01:00.0: No pointer to output script table
fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver

Version-Release number of selected component (if applicable):
kernel-2.6.31-33.fc12.i686
xorg-x11-drv-nouveau-0.0.15-10.20090914git1b72020.fc12.i686
xorg-x11-server-Xorg-1.6.99.901-3.fc12.i686

How reproducible:
Always

Steps to Reproduce:
1. Boot the system
2.
3.
  
Actual results:
Error message above displayed

Expected results:
No error message

Additional info:
Comment 1 Ben Skeggs 2009-09-21 23:34:48 UTC 
The above aren't error messages really.  I can and will quieten the nvidia-control and "No pointer to output script table" messages however.  The message from fb is just informing you that vesafb is getting kicked off the hw to allow nouveau to take control, if you don't enable vesafb this message will also disappear.
Comment 2 Quentin Armitage 2009-09-22 07:27:39 UTC 
Many thanks for the response.

You mention "if you don't enable vesafb" ... . I am not aware of doing anything to enable vesafb; how do I disable it, and should I do so?
Comment 3 Ben Skeggs 2009-09-22 22:09:55 UTC 
Are you able to post your /var/log/messages?  vesafb will be enabled if there's any "vga=" line in your kernel boot options.
Comment 4 Quentin Armitage 2009-09-22 22:21:51 UTC 
I have vga=838 in my kernel boot options.

Are you still interested in /va/log/messages given the above?

Is there some way of doing the equivalent of vga=838 without vesafb being enabled?
Comment 5 Ben Skeggs 2009-09-22 23:26:42 UTC 
Ah, that's it then.  Nope, I don't need /var/log/messages in that case.

You don't need vga=838 with nouveau.  Once it loads, it should provide you with a framebuffer console in your display's native resolution.