Bug 3281

Summary: i915 freezes at boot time
Product: Mageia Reporter: Richard Giroux <nrgiroux>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: critical    
Priority: Normal CC: marja11
Version: 1Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Richard Giroux 2011-11-07 05:43:03 CET
Description of problem:
On an Acer TM6410 with i915 (driver) graphics card, the boot process stops on the second point of the graphical progress bar.  It seems to be just after udev 

On atl-F{1-6}, I see:

("Press I for interactive startup..)
udev ...

and

something (?) with i915
fb conflicting fb hw usage inteldrmfb




Version-Release number of selected component (if applicable):


How reproducible:
Every boot, be it a normal or failsafe boot.

Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2011-11-08 00:00:08 CET
Hi, maybe you search so idea here: https://bugs.mageia.org/buglist.cgi?quicksearch=i915

Component: Installer => RPM Packages

Comment 2 Marja Van Waes 2012-01-01 13:41:19 CET
(In reply to comment #1)
> Hi, maybe you search so idea here:
> https://bugs.mageia.org/buglist.cgi?quicksearch=i915

@ Richard

* Did you find anything useful in the bugs reports in that list?

If you found one that you think is the same as yours, please close this report as a duplicate of that one.

However, if you think your problem is different

* How did you install Mageia? From a DVD, live CD, different?
* Can you run the live CD (instead of installing it) without problems?

* Can you boot into runlevel 1 or 3? ( hit F3 in the grub boot menu and select DEFAULT and then add "1" or "3" to the kernel command line)

* If so, please get the output of 
lspcidrake -v
and attach it here 

and please attach /var/log/Xorg.0.log too

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-02-17 16:46:24 CET
@ Richard,

could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

Keywords: (none) => NEEDINFO

Comment 4 Marja Van Waes 2012-03-03 06:46:20 CET
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD