Bug 1268

Summary: Graphical boot not working on Radeon 3200
Product: Mageia Reporter: Nikita Krupenko <krnekit>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: balcaen.john
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Logs for boot

Description Nikita Krupenko 2011-05-13 22:38:49 CEST
Description of problem:
When I boot my system, I don't see graphical boot, but only some error messages about memory. Logs are in the attachment.

Version-Release number of selected component (if applicable):
Mageia 1 Beta 2
Comment 1 Nikita Krupenko 2011-05-13 22:39:53 CEST
Created attachment 403 [details]
Logs for boot

Logs added
Comment 2 Ahmad Samir 2011-06-04 00:14:51 CEST
This looks similar to bug 1471, does the system boot if you add:
radeom.modset=0

to the kernel boot parameters (at the GRUB screen) ?
Comment 3 John Balcaen 2011-06-04 01:10:14 CEST
There's a little typo : it's radeon.modeset=0

CC: (none) => balcaen.john

Comment 4 Ahmad Samir 2011-06-04 02:38:08 CEST
Yes, of course; thanks for the correction.
Comment 5 Nikita Krupenko 2011-06-04 14:24:15 CEST
(In reply to comment #2)
> This looks similar to bug 1471, does the system boot if you add:
> radeom.modset=0
> 
> to the kernel boot parameters (at the GRUB screen) ?

I should note, that the system boots successfully, but only graphical bootsplash (i.e. plymouth) not working.
With added parameter radeon.modset=0 graphical boot working, but the system unusable - moving windows is very slow.
Comment 6 John Balcaen 2011-06-04 15:22:23 CEST
Once you're able to boot you should :
1) install the radeon-firmware package
urpmi radeon-firmware
2) regenerate the mkinitrd
 mkinitrd /boot/initrd-2.6.38.7-desktop-1.mga.img 2.6.38.7-desktop-1.mga -f

With that option the firmware should be now available in the initrd & you should be able to boot without the radeon.modeset=0 on grub command line

Regarding the graphical boot splash=silent should do the trick.
Comment 7 Nikita Krupenko 2011-06-04 18:09:11 CEST
Thank you, this helped!
One note: I've used this command to rebuild initrds:

$ sudo bootloader-config --action rebuild-initrds
Comment 8 Ahmad Samir 2011-06-27 21:41:05 CEST
A duplicate.

*** This bug has been marked as a duplicate of bug 1471 ***

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