From: "Alex Villacís Lasso" <a_villacis@palosanto.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel command line parameter parsing is broken at drm_kms_helper.edid_firmware when compiling under Fedora 18
Date: Mon, 21 Jan 2013 10:08:39 -0500 [thread overview]
Message-ID: <50FD59F7.7000308@palosanto.com> (raw)
In-Reply-To: <50FB4697.1050907@palosanto.com>
El 19/01/13 20:21, Alex Villacís Lasso escribió:
> I am having this strange issue. My computer has a LCD display that does not send any EDID, and therefore I need the command parameter "drm_kms_helper.edid_firmware=edid/1280x1024.bin" In Fedora 16, the stock kernel does not have
> CONFIG_DRM_LOAD_EDID_FIRMWARE set. Therefore I compiled my own kernel from vanilla sources, and the parameter worked. I have just now upgraded to Fedora 18. The new stock kernel is supposed to have CONFIG_DRM_LOAD_EDID_FIRMWARE set, but when I boot with
> the drm_kms_helper parameter, I get a message "drm_kms_helper: Unknown parameter `bin'". I thought this was a kernel bug caused by some patch in the stock kernel, so I filed https://bugzilla.redhat.com/show_bug.cgi?id=901899 , and then proceeded to
> compile 3.8-rc4 from vanilla sources. However, I am surprised to find that the vanilla sources, when compiled under Fedora 18, exhibit the same bug. Has anyone seen a situation like this? Is this a possible compiler bug in Fedora 18? A grub2 bug?
> Apparently the kernel is misparsing the commandline parameter and thinks "bin" is the module parameter, not "edid_firmware".
BTW, I have CONFIG_DYNAMIC_DEBUG=y in my kernel config, and I tried adding dyndbg="file params.c +p" to the kernel command line, but I see no additional debug output that might point out what is happening.
prev parent reply other threads:[~2013-01-21 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 1:21 kernel command line parameter parsing is broken at drm_kms_helper.edid_firmware when compiling under Fedora 18 Alex Villacís Lasso
2013-01-21 15:08 ` Alex Villacís Lasso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FD59F7.7000308@palosanto.com \
--to=a_villacis@palosanto.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox