http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ATI firmware cannot be |mkinitrd: ATI firmware |loaded by radeon module in |cannot be loaded by radeon |initrd |module due to udevd not | |running yet -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c2 --- Comment #2 from Robin Knapp 2010-04-14 10:38:48 CEST --- I'll try this tonight. But I'm not sure whether this might conflict with udev's automatic hw detection and might introduce new (timing) issues. Maybe this is no problem at all if the modules interpret "nomodeset" by themself For the automatic detection - I'm not sure what /lib/udev/rules.d/79-kms.rules does (prevent automatic loading?), but it's missing in initrd. Maybe related? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |robin.knapp@ts.fujitsu.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c5 --- Comment #5 from Robin Knapp 2010-04-14 21:15:59 CEST --- btw, is this really needed in the latest kernel? # grep i915 /lib/modules/$(uname -r)/modules.dep kernel/drivers/gpu/drm/i915/i915.ko: kernel/drivers/char/agp/intel-agp.ko ... Won't this force the correct order? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c7 --- Comment #7 from Robin Knapp 2010-04-14 22:40:25 CEST --- Okay, I couldn't test it as my X600 Mobility seems to work without the agp driver. Well, it's a PCI-Express card, so that makes sense. So adding the KMS udev script and adding udev to the kms-boot.sh %depend line should work on all systems. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c9 --- Comment #9 from Stefan Dirsch 2010-04-16 01:18:39 UTC --- Created an attachment (id=354863) --> (http://bugzilla.novell.com/attachment.cgi?id=354863) mkinitrd-kms-firmware.diff * loading firmware files for KMS modules needs udev; hence make sure that udev is started before loading KMS modules. But then we also need the KMS udev rule, so that the KMS is not accidently loaded before the appropriate agp module, which would be fatal. (bnc #596268) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c13 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #13 from Michal Marek 2010-04-16 12:17:01 UTC --- Fixed by http://gitorious.org/opensuse/mkinitrd/commit/88b392abf6f2d98dee1b349856fdda... and submitted to Base:System. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c15 --- Comment #15 from Michal Marek 2010-04-16 13:09:17 UTC --- https://build.opensuse.org/request/diff/38050 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c18 --- Comment #18 from Klaus Kämpf 2010-04-20 09:46:26 UTC --- Confirmed. radeon/RS780_pfp.bin gets loaded in openSUSE 11.3 M5 after upgrading to mkinitrd-2.5.10-68.2.x86_64 from Base:System However, boot.msg now shows <3>[ 3.033332] r600_cp: Failed to load firmware "radeon/R600_rlc.bin" <3>[ 3.033342] [drm:r600_startup] *ERROR* Failed to load firmware! (apparently without any ill effects ?!) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c20 --- Comment #20 from Stefan Dirsch 2010-04-20 10:07:34 UTC --- (In reply to comment #18)

Confirmed. radeon/RS780_pfp.bin gets loaded in openSUSE 11.3 M5 after upgrading to mkinitrd-2.5.10-68.2.x86_64 from Base:System

However, boot.msg now shows <3>[ 3.033332] r600_cp: Failed to load firmware "radeon/R600_rlc.bin" <3>[ 3.033342] [drm:r600_startup] *ERROR* Failed to load firmware!

(apparently without any ill effects ?!)

Probably unrelated to being loaded in initrd. But you can double check by adding 'nomodeset 3' to kernel boot command line. Then unload "radeon" kernel module and reload it again manually via modrobe. (In reply to comment #19)

A bit more concerning is the need for "selinux=0" during boot. But it might as well be related to running the M5 kernel. Lets see what M6 brings ;-)

What happens if you don't use that option? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c22 --- Comment #22 from Klaus Kämpf 2010-04-20 10:35:42 UTC --- (In reply to comment #20)

Probably unrelated to being loaded in initrd. But you can double check by adding 'nomodeset 3' to kernel boot command line. Then unload "radeon" kernel module and reload it again manually via modrobe.

The 'radeon' module is not loaded after boot. modprobing it results in Apr 20 12:31:43 linux-lkbf kernel: [ 52.536362] [drm] Initialized drm 1.10 20060810 Apr 20 12:31:43 linux-lkbf kernel: [ 52.592933] [drm] VGACON disable radeon kernel modesetting. Apr 20 12:31:43 linux-lkbf kernel: [ 52.597777] pci 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Apr 20 12:31:43 linux-lkbf kernel: [ 52.601959] pci 0000:01:05.0: setting latency timer to 64 Apr 20 12:31:43 linux-lkbf kernel: [ 52.602211] [drm] Initialized radeon 1.32.0 20080528 for 0000:01:05.0 on minor 0 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c24 --- Comment #24 from Robin Knapp 2010-04-20 12:41:42 CEST --- (In reply to comment #22)

(In reply to comment #20)

...

Probably unrelated to being loaded in initrd. But you can double check by adding 'nomodeset 3' to kernel boot command line. Then unload "radeon" kernel module and reload it again manually via modrobe.

The 'radeon' module is not loaded after boot.

modprobing it results in

Apr 20 12:31:43 linux-lkbf kernel: [ 52.536362] [drm] Initialized drm 1.1.0 20060810 Apr 20 12:31:43 linux-lkbf kernel: [ 52.592933] [drm] VGACON disable radeon kernel modesetting.

I found that when booting with "nomodeset", loading the radeon module does not enable modesetting. Or maybe it's caused by the udev rules. Try this: modprobe --ignore-install radeon modeset=1 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c26 --- Comment #26 from Klaus Kämpf 2010-04-20 10:49:42 UTC --- (In reply to comment #25)

So no issues with loading ATI firmware? Sure that KMS is active? Verify with

cat /sys/module/radeon/parameters/modeset

0 means disabled, 1 enabled, -1 default (i.e. KMS enabled).

Its 0.

If it is 0 try with 'modprobe radeon modeset=1'. Do you now see any issues with loading the firmware?

Nothing different from comment #18 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c28 --- Comment #28 from Stefan Dirsch 2010-04-20 10:51:14 UTC --- (In reply to comment #23)

(In reply to comment #20)

...

What happens if you don't use that option?

This is shown on the console

boot/93-boot.sh: line 28: [: =: unary operator expected boot/93-boot.sh: line 34: [: =: unary operator expected Machine in enforcing mode and cannot execute load_policy To disable selinux, add selinux=0 to the kernel command line. Not continuing

I believe that's a differeent issue. Could you open a seperate bugreport for that? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c29 --- Comment #29 from Stefan Dirsch 2010-04-20 10:53:36 UTC --- (In reply to comment #26)

...

If it is 0 try with 'modprobe radeon modeset=1'. Do you now see any issues withloading the firmware?

Nothing different from comment #18

Ok. So it's unrelated to initrd. :-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c31 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@novell.com --- Comment #31 from Michal Marek 2010-04-20 14:04:40 UTC --- *** Bug 598126 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=598126 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c33 --- Comment #33 from Klaus Kämpf 2010-04-20 14:34:55 UTC --- iirc, no. But I have to check @home to be sure. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c35 --- Comment #35 from Klaus Kämpf 2010-04-20 19:01:31 UTC --- (In reply to comment #34)

(In reply to comment #33)

...

iirc, no. But I have to check @home to be sure.

You don't? This would explain a lot. :-)

Indeed, kernel-firmware was _not_ installed. How does this package get installed ? Which dependencies trigger its installation ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c37 --- Comment #37 from Klaus Kämpf 2010-04-20 19:41:20 UTC --- kernel-desktop already includes /lib/firmware/2.6.34-rc3-3-desktop/radeon/*, so kernel-firmware is apparently not needed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c39 --- Comment #39 from Stefan Dirsch 2010-04-20 22:09:30 UTC --- Indeed there are firmware files in /lib/firmware/2.6.34-rc4-4-desktop/radeon/ and /lib/firmware/radeon/, but apparenly two files are missing in /lib/firmware/2.6.34-rc4-4-desktop/radeon/. Apart from that the directories are identical. Only in /lib/firmware/radeon/: R600_rlc.bin Only in /lib/firmware/radeon/: R700_rlc.bin R600_rlc.bin is exactly the file you were missing. You need to run mkinitrd after installing the kernel-firmware package to add it to initrd. Otherwise it cannot be loaded from initrd. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c41 --- Comment #41 from Stefan Dirsch 2010-04-21 08:03:00 UTC --- (In reply to comment #40)

(In reply to comment #39)

...

Indeed there are firmware files in /lib/firmware/2.6.34-rc4-4-desktop/radeon/ and /lib/firmware/radeon/, but apparenly two files are missing in /lib/firmware/2.6.34-rc4-4-desktop/radeon/. Apart from that the directories are identical.

Ah, so this would qualify as a kernel packaging bug ?!

Maybe. Please report the issue and let me know about the results (or add me to Cc). I even don't understand why we have (about) the same firmware files at two different locations ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c43 --- Comment #43 from Klaus Kämpf 2010-04-21 19:09:29 UTC --- (In reply to comment #40)

Yeah, sorry to overlook the obvious. Will recreate initrd and test again when I'm back home.

Working fine now. All firmware files load properly and the console/bootsplash -> X11 switch is smooth. However, this display went dark after ~30 secs and the kernel oopsed (dead numlock). Fill file a separate bug for this :-/ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=596268 http://bugzilla.novell.com/show_bug.cgi?id=596268#c45 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johann-nikolaus.andreae@nac | |s.de --- Comment #45 from Jeff Mahoney 2010-04-22 13:38:29 UTC --- *** Bug 598869 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=598869 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.