Bug 597566

Summary: kernel 2.6.34-rc3-3 will only boot if nomodeset is specified
Product: [openSUSE] openSUSE 11.3 Reporter: Forgotten User Si7ddX0wxG <forgotten_Si7ddX0wxG>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: jeffm
Version: Milestone 5   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: bootchart - system without nomodeset - longer boot time
bootchart - system with nomodeset - shorter boot time
hardware info
output of 'dmesg' after the long boot
bootchart after newer rpm applied

Description Forgotten User Si7ddX0wxG 2010-04-17 08:14:46 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/2.0.4-1.6 SeaMonkey/2.0.4

kernel will only boot if  nomodeset is specified

This boots:

title Desktop -- openSUSE 11.3 - 2.6.34-rc3-3
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.34-rc3-3-desktop root=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part1 resume=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part3 splash=silent quiet showopts nomodeset 
    initrd /boot/initrd-2.6.34-rc3-3-desktop

This Does NOT boot - no nomodeset specified 
-------------------------------------------
title Desktop -- openSUSE 11.3 - 2.6.34-rc3-3
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.34-rc3-3-desktop root=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part1 resume=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part3 splash=silent quiet showopts 
    initrd /boot/initrd-2.6.34-rc3-3-desktop

Reproducible: Always

Steps to Reproduce:
1. kernel 2.6.34-rc3-3 will only boot with  nomodeset  specified
Comment 1 Forgotten User Si7ddX0wxG 2010-04-17 08:48:49 UTC
onscreen the last two lines read:
ata1: softreset failed (device not ready)
ata4: softreset failed (device not ready)
Comment 2 Forgotten User Si7ddX0wxG 2010-04-19 22:51:56 UTC
I waited a longer time and it did eventually boot without the nomodeset specified
Boot time is faster with nomodeset specified 
Adding bootchart info.
Comment 3 Forgotten User Si7ddX0wxG 2010-04-19 22:54:59 UTC
Created attachment 355446 [details]
bootchart - system without  nomodeset - longer boot time
Comment 4 Forgotten User Si7ddX0wxG 2010-04-19 23:05:03 UTC
Created attachment 355448 [details]
bootchart - system with nomodeset - shorter boot time
Comment 5 Forgotten User Si7ddX0wxG 2010-04-19 23:11:43 UTC
shorter boot time - 34 seconds
longer  boot time - 1min 35 seconds

Disk is a SSD CRUCIAL_CT64M225
Comment 6 Forgotten User Si7ddX0wxG 2010-04-19 23:13:50 UTC
Created attachment 355449 [details]
hardware info
Comment 7 Jeff Mahoney 2010-04-20 18:15:12 UTC
Can you attach the output of 'dmesg' after the long boot?
Comment 8 Forgotten User Si7ddX0wxG 2010-04-21 04:14:02 UTC
Created attachment 355815 [details]
output of 'dmesg' after the long boot
Comment 9 Jeff Mahoney 2010-04-21 04:17:32 UTC
[    2.880555] [drm] Loading RS780 Microcode
[    2.880560] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin
[   62.880180] r600_cp: Failed to load firmware "radeon/RS780_pfp.bin"
[   62.880262] [drm:r600_startup] *ERROR* Failed to load firmware!
[   62.880307] radeon 0000:01:05.0: disabling GPU acceleration
[   62.880377] radeon 0000:01:05.0: ffff88013c43ba00 unpin not necessary
[   62.880380] radeon 0000:01:05.0: ffff88013c43ba00 unpin not necessary


That's easy enough. You need to install kernel-firmware.
Comment 10 Jeff Mahoney 2010-04-21 04:21:53 UTC
Or, if it is installed, then mkinitrd needs to account for it.
Comment 11 Forgotten User Si7ddX0wxG 2010-04-21 06:23:35 UTC
I got the file from:
http://svn.debian.org/viewsvn/kernel/dists/trunk/firmware-nonfree/linux-nonfree/radeon/RS780_pfp.bin
Question: which directory does RS780_pfp.bin go into ?
Comment 12 Jeff Mahoney 2010-04-21 14:38:11 UTC
Looks like it is actually a mkinitrd issue. bnc#596268 is the first report for the issue. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 596268 ***
Comment 13 Forgotten User Si7ddX0wxG 2010-04-26 07:00:45 UTC
I updated to these items and that fixed the problem
- kernel-firmware-20100227-17.1.noarch.rpm
- mkinitrd-2.5.10-19.1.x86_64.rpm
- kernel-desktop-2.6.34-6.1.x86_64.rpm
Comment 14 Forgotten User Si7ddX0wxG 2010-04-26 13:38:43 UTC
Created attachment 356808 [details]
bootchart after newer rpm applied
Comment 15 Jeff Mahoney 2010-04-26 13:42:15 UTC
Ok, thanks for the feedback. This is the expected behavior.