Bug 679197

Summary:	kernel 2.6.37.1 message : [drm:drm_crtc_helper_set_config] ERROR failed to set mode on [CRTC:6]
Product:	[openSUSE] openSUSE 11.4	Reporter:	Gilles Sabourin <sabourin.gilles>
Component:	Basesystem	Assignee:	Egbert Eich <eich>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	jeffm
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	dmesg output

Description Gilles Sabourin 2011-03-13 19:29:08 UTC

User-Agent:       Opera/9.80 (Windows NT 5.1; U; fr) Presto/2.7.62 Version/11.01

I am running openSUSE 11.4 on ASUS A7N8X motherboard, in text mode only (this is a server - no X server installed). I got some error messages at boot :

[    4.103918] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6]
[    4.103923] fbcon_init: detected unhandled fb_set_par error, error code -22
[    4.103967] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6]
[    4.104753] Console: switching to colour frame buffer device 90x36
[    4.104775] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6]
[    4.105304] fb0: nouveaufb frame buffer device
[    4.105307] drm: registered panic notifier


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Gilles Sabourin 2011-03-13 19:30:12 UTC

Created attachment 419007 [details]
dmesg output

Comment 2 Gilles Sabourin 2011-03-13 19:43:18 UTC

I can only use a small portion of my monitor, maybe in a default 40x25 terminal located at the top left corner, instead of its full size.

Comment 3 Egbert Eich 2011-04-18 16:03:28 UTC

Please use the boot option 'nomodeset'. If you are running a server you don't need KMS.

Comment 4 Gilles Sabourin 2011-04-18 18:25:30 UTC

I can confirm to you that this workaround works. Thanks.

Comment 5 Egbert Eich 2014-09-07 21:04:34 UTC

openSUSE 11.4 is no longer supported. Thie issue reported may have long been
fixed upstream.Should you still encounter it feel free to create a new ticket.

Comment 6 Egbert Eich 2014-09-07 21:27:22 UTC

See last comment.