<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - Dell Latitude 6430u failed to resume with nomodeset - no known kernel working" href="https://bugs.freedesktop.org/show_bug.cgi?id=82440#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - Dell Latitude 6430u failed to resume with nomodeset - no known kernel working" href="https://bugs.freedesktop.org/show_bug.cgi?id=82440">bug 82440</a> from <a class="email" href="mailto:lv.zheng@intel.com" title="Lv Zheng <lv.zheng@intel.com>"> Lv Zheng</a> <pre>(In reply to <a href="show_bug.cgi?id=82440#c14">comment #14</a>) > (In reply to <a href="show_bug.cgi?id=82440#c13">comment #13</a>) > > If our test machines don't want to be affected by wrong graphics changes, we > > need to be able to perform tests without graphics driver loaded. > > Ah, but you did have i915.ko loaded! nomodeset only disables kernel > modesetting as the name implies. You can try modprobe.blacklist=i915 to > prevent i915 from loading. (Although beware that some userspaces use insmod > or modprobe directly to override that.) I realized you were talking about this: without graphics driver loaded. :-) Sorry for my wording. Let me re-word. I wonder if I can still perform STR test with the graphics driver loaded but the specific functionalities bypassed. Kernel STR should still working for the kernel with kernel modesetting disabled, right? As we learned from 82439, by using nomodeset, we are able to bypass the affection of the bisected commit. But I just don't know why I cannot perform a successful STR by booting such a kernel.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>