Red Hat Bugzilla – Bug 680132
QA:Testcase_intelvideo_restartx fails on Acer Aspire netbook
Last modified: 2011-11-22 10:40:53 EST
Description of problem:
Performing the restartx test during Fedora graphics test week (http://fedoraproject.org/wiki/QA:Testcase_intelvideo_restartx) I found that I was unable to successfully boot to init 3 while rhgb remained enabled.
Attempting to boot to init 3 with rhgb enabled resulted in a large white rectangle appearing over the top left of the screen, no further feedback was displayed. Re-attempting after removing the rhgb parameter did allow me to boot to init 3.
Version-Release number of selected component (if applicable):
F15 graphics test week image.
Steps to Reproduce:
1. Boot graphics test week image.
2. At grub prompt edit boot params adding '3' to set the init level.
3. Boot this configuration.
Machine booted at init level 3. Login prompt for displayed.
White rectangle artifact. No further feedback.
Attachments to follow.
Created attachment 480745 [details]
Created attachment 480746 [details]
Also noted white rectangle artefact during testing using test day live CD on a Samsung NC10 netbook (external USB DVD-RW):
I've attached a basic camera phone picture to help illustrate this, hopefully this is the same issue that is noted above. Apologies for the poor picture quality.
Created attachment 480969 [details]
Image of white rectangle
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require (from BOTH of you) that will be helpful in our diagnosis of this issue.
Please add drm.debug=0x04 to the kernel command line, restart computer, and attach
* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)
to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Apologies for the delay on this but when I add drm.debug=0x04 the netbook in question seems to take an inordinate amount of time to boot, to the point that I give up on it. Is it expected to extend boot time? How I can I check what if anything is happening?
It starts the graphical boot ok and then the progress indicator seems to complete but at that point nothing further happens. Am now working with the F15 alpha rather than the gfx test day image.
(In reply to comment #6)
> Apologies for the delay on this but when I add drm.debug=0x04 the netbook in
> question seems to take an inordinate amount of time to boot, to the point that
> I give up on it. Is it expected to extend boot time? How I can I check what if
> anything is happening?
Yes, but you shouldn't almost recognize the delay. Logs withouht that drm.debug are useful as well, so if you cannot help it, don't sweat it and provide them without drm.debug.
> It starts the graphical boot ok and then the progress indicator seems to
> complete but at that point nothing further happens. Am now working with the F15
> alpha rather than the gfx test day image.
Yes, that's correct. There are still many bugs being fixed as days go by.
Since installing the beta version of F15 released 19/04/2011, this issue
appears to be fixed for me.
Agree with the above poster, this works on my netbook now also. As the original reporter I am closing this bug.