| Summary: | vga= values not accepted correctly by kernel/grub kernel line | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | George R. Goffe <grgoffe> | ||||
| Component: | grub | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | gansalmon, itamar, jfeeney, jonathan, kernel-maint, lkundrak, madhu.chinakonda, pjones | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-08-29 17:58:49 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
George R. Goffe
2011-02-27 18:33:24 UTC
Created attachment 481266 [details]
/boot/grub/grub.conf in current use.
Somehow this attachment process failed when I created this bug. Sigh...
A bug or UFU? :-)
George...
Your attachment is using vga=31a Chuck, This seems to fail as well. Do you need me to do something? Regards, George... Howdy, Is there any status for this bug? The problem still exists. Now, any specification of vga= in the kernel line causes the problem and I get a prompt for correct values even though correct values ARE specified. Just a few minutes ago, I rebooted my system. Here are the grub kernel lines. The code chokes on 318 and gives me a prompt to respecify. When I enter 318, that is accepted and booting continues. George... title Fedora (2.6.35.11-83.fc14.i686) root (hd0,0) kernel /vmlinuz-2.6.35.11-83.fc14.i686 ro root=/dev/sda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us init=/sbin/bootchartd vga=318 nomodeset drm.debug=0x04 initrd /initramfs-2.6.35.11-83.fc14.i686.img Looking closer at this, I don't think 318 is a valid mode unless maybe you meant 0x318, which would be decimal 794 (1280x1024, 16-bit color.) Chuck, When I boot, I get a complaint about 13f and then the prompt, press enter to get a list... 318 is there and I type in 318 which appears to be accepted and the boot continues. Other ranges of 31x produce ranges of 13x, all of which are rejected but when typed in, most are accepted and the boot continues. George... I think what is happening is that the kernel is assuming hexadecimal for vga modes typed at the prompt, and decimal when they're on the command line. Either "vga=0x318" or "vga=794" should work on the command line, and yield 1280x1024x16. "It's not a bug it's a feature." Chuck, Hmmmm... A feature? So, how does one deal with this feature? Is there doc for the feature? Is there a standard for data entered into the kernel? I have set some parameters with a 0x0040 for example (drm.debug=0x04). Shouldn't there be an error message if a person enters the data incorrectly? One that is meaningful? George... (confused in the woods). Chuck, Is there any status on this bug? The problem STILL exists. Is there doc to support this "feature"? Regards, George... This behaviour can't be changed as existing configuration depends upon it. If you want to pass a value in hex, use vga=0x318. If you want to pass it in decimal, use vga=794. 318 is only meaningful in hex, but looks like a decimal value, so the kernel assumes you've passed a decimal value. This is, as far as I can tell, how grub has always worked. It's also certainly not an issue with the kernel, which never even parses vga= itsel. Hi, Thanks for your response. I was fooled by the appearance of the values in the menu. There is no stipulation that values expected ARE hex. I'm a little confused by what you have written though. First you say the kernel assumes... then you say the kernel never even parses vga= values, I presume you mean values. My point, I think, is that the menu is misleading. Values chosen from the menu should also be acceptable in the kernel line OR some text making the distinction should be made. George... |