Bug 27922
Summary: | setting graphics mode for text console with video= instead of vga= does not work | ||
---|---|---|---|
Product: | Drivers | Reporter: | Elmar Stellnberger (estellnb) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | glisse, mrmazda |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.38-0.0.7 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Elmar Stellnberger
2011-01-31 22:35:16 UTC
With radeon rv380 and a P275 Trinitron CRT, video=1024x768 on cmdline instead of vga=0xwhatever or vga=7whatever works for me with default modesetting state and Kulow/openSUSE kernel-desktop-2.6.37.2-3 and GA kernel-default-2.6.37.1-1.2 to produce same result on tty[1-6] as vga=791/vga=0x305/vga=0x317/vga=0x318 did before KMS implementation. As far as I have tested it on my machine the radeon module needs to be loaded with KMS enabled (no radeon.modeset=0 parameter) to get the video kernel-cmdline option interpreted (/proc/cmdline). If you f.i. need to use uvesafb instead give the following option: uvesafb.mode_option=1600x1200-24@60 (1920x1200 is no Vesa mode). The same parameters can be given on modeprobe leaving the module name (radeon., uvesafb.) out (/usr/src/linux-ver/Documentation/fb). This is not a bug, video= command line is only interpreted with kernel modesetting enabled. We don't support anymore non kernel modesetting case for radeon. |