Bug 441444

Summary:	Using i915.modeset=1 causes an error message
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	rvokal
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:	2008-04-26 16:30:12 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 Bill Nottingham 2008-04-08 05:25:05 UTC

Description of problem:

Using i915.modeset=1 to enable the modesetting kernel driver causes the kernel
to print out a message on boot about this being an unknown boot parameter.

It's pretty obvious now that 'quiet' mode is back on.

Version-Release number of selected component (if applicable):

kernel-2.6.25-0.204.rc8.git4.fc9.x86_64

Comment 1 Chuck Ebbert 2008-04-11 16:49:11 UTC

It's not built in so you need to put that in modprobe.conf.

If this is happening on the live CD or install disk the parameter is working
because the code that loads the driver parses the kernel command line to pick
this up. There doesn't seem to be any good way of killing that warning though.

Comment 2 Bill Nottingham 2008-04-11 17:38:13 UTC

See /etc/modprobe.d/i915modeset - it's set up to be configued via /proc/cmdline

Comment 3 Chuck Ebbert 2008-04-11 22:27:48 UTC

So the kernel warning is bogus but there's no good way to kill it. Turning off
the warnings completely would make it hard to find real mistakes in the command
line.

Comment 4 Chuck Ebbert 2008-04-26 16:30:12 UTC

Upstream has been debating this problem but nobody has a good answer yet.