Comment # 13 on bug 842806 from Rom��rio Rios

(In reply to Egbert Eich from comment #11)
> (In reply to Rom��rio Rios from comment #10)
> > > 
> > > Romario, I really don't know what 'this problem' is supposed to be.
> > > The original report talks about a hang of the system before the plymouth
> > > boot splash starts. Is this what you observe as well?
> > 
> > Yes. Whenever I boot after updating, the boot hangs (and the splash screen
> > isn't shown). The workaround for this goes as follows:
> > 
> > 1. Boot the system with the nomodeset kernel option
> > 2. Reinstall xf86-video-amdgpu (zypper in -f)
> > 3. Reinstall everything else radeon-related (zypper in -f libdrm_radeon1
> > libdrm_radeon1-32bit libvdpau_radeonsi radeontop)
> > 
> > It's been working so far.
> 
> This sounds very much like a voodoo workaround.
> 
> When you do this next time, please capture the output (including stderr):
> 
> # zypper in -f ... &> /tmp/radeon.log
> 
> - Do you have to install xf86-video-amdgpu and 'everything else
> radeon-related' separately?

I don't know, I never tried doing otherwise. Next time, I'll only try to
reinstall the driver to see if the issue goes away.

> - Is there a chance that any of these recreate the initrd for whatever
> reason?

I really don't know -- I don't recall seeing anything indicating that.

> - Did you make several boot attempts when the hang occurred?

Yes. It never boots unless I set the nomodeset kernel option.

> <snip>
> 
> There is no PCI device ID - because you missed an option. 'lspci -nn' is
> what you need to do.

Thanks for the tip.

$ sudo lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]

According to
http://developer.amd.com/resources/ati-catalyst-pc-vendor-id-1002-li/, 68f9 is
ATI Radeon��� HD 5450's ID.

> <snip> 
> Same for xf86-video-amdgpu.

I'll reinstall the driver only to determine 100% if reinstalling the video
driver is really what's making hardware acceleration work again.

> 
> > > At least, please answer above question - what is your exact problem - and
> > > provide a log file from the Xserver starting.
> > 
> > My last boot failure related to this issue was two boots ago. How can I get
> > this info?
> 
> Please just provide a log file from a running system.

I attached a jorunalctl --system -b log. Will that be enough?