[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#541630: ATI Rage 128 Pro Ultra TF doesn't start with linux-image-2.6.30-1-686



On Sun, 2009-08-16 at 04:03 +0200, advocatux wrote:
> 2009/8/16 Ben Hutchings <ben@decadent.org.uk>:
> [...]
> > I have put a new version of the module up in the same location.  Please
> > try again with this version.
> 
> Unfortunatley it doesn't work either (unless I'm doing something wrong).

It's not supposed to work - the point was to test that the modified
driver will not crash or hang if firmware is missing.

> At first attempt that's what kern.log says:
> 
> kernel: imklog 4.2.0, log source = /proc/kmsg started.
> kernel: [  373.834658] [drm] Module unloaded
> kernel: [  396.585897] [drm] Initialized r128 2.5.0 20030725 for
> 0000:01:00.0 on minor 0
> kernel: [  413.491987] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
> kernel: [  413.492092] agpgart-intel 0000:00:00.0: putting AGP V2
> device into 1x mode
> kernel: [  413.492125] pci 0000:01:00.0: putting AGP V2 device into 1x mode
> kernel: [  413.516303] platform r128_cce.0: firmware: requesting
> r128/r128_cce.bin
> kernel: [  413.532399] r128_cce: Failed to load firmware "r128/r128_cce.bin"
> kernel: [  413.532417] [drm:r128_do_init_cce] *ERROR* Failed to load firmware!
> kernel: [  413.532590] [drm:r128_cce_stop] *ERROR* called with no initialization
> kernel: [  840.604196] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
> kernel: [  840.604229] agpgart-intel 0000:00:00.0: putting AGP V2
> device into 1x mode
> kernel: [  840.604262] pci 0000:01:00.0: putting AGP V2 device into 1x mode
> kernel: [  840.715425] platform r128_cce.0: firmware: requesting
> r128/r128_cce.bin
> kernel: [  840.796697] r128_cce: Failed to load firmware "r128/r128_cce.bin"
> kernel: [  840.796714] [drm:r128_do_init_cce] *ERROR* Failed to load firmware!
> kernel: [  840.796887] [drm:r128_cce_stop] *ERROR* called with no initialization

This looks like the driver now behaves as intended.  Did the X server
restart successfully?

> Of course, module was loaded:
> 
> # lsmod | grep r128
> r128                   30824  0
> drm                   137920  1 r128
> 
> At second attempt, I rebooted the machine and tried again, but this
> time with the module loaded already and it fails once more:
> 
> kernel: [   30.211945] [drm] Initialized drm 1.1.0 20060810
> kernel: [   30.233255] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
> kernel: [   30.233264] PCI: setting IRQ 5 as level-triggered
> kernel: [   30.233276] pci 0000:01:00.0: PCI INT A -> Link[LNKA] ->
> GSI 5 (level, low) -> IRQ 5
> kernel: [   30.233637] [drm] Initialized r128 2.5.0 20030725 for
> 0000:01:00.0 on minor 0
> kernel: [   30.326581] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
> kernel: [   30.326612] agpgart-intel 0000:00:00.0: putting AGP V2
> device into 1x mode
> kernel: [   30.326644] pci 0000:01:00.0: putting AGP V2 device into 1x mode
> kernel: [   30.388709] platform r128_cce.0: firmware: requesting
> r128/r128_cce.bin
> kernel: [   30.444762] r128_cce: Failed to load firmware "r128/r128_cce.bin"
> kernel: [   30.444781] [drm:r128_do_init_cce] *ERROR* Failed to load firmware!
> kernel: [   30.444986] BUG: unable to handle kernel NULL pointer
> dereference at 00000094
[...]

This is expected - after a reboot you are loading the old unfixed
module.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: