[Openchrome-users] Mesh notebook ... success & failure

[Peter Lord]

Peter Lord wrote, On 03/25/2006 12:44 PM:

<<snip>>

> However, glx doesn't appear to be happy :-(  I see :-
>
>    $ glxinfo
>    name of display: :0.0
>    libGL: XF86DRIGetClientDriverName: 5.0.0 unichrome (screen 0)
>    libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/unichrome_dri.so
>    drmOpenByBusid: Searching for BusID PCI:1:0:0
>    drmOpenDevice: node name is /dev/dri/card0
>    drmOpenDevice: open result is 4, (OK)
>    drmOpenByBusid: drmOpenMinor returns 4
>    drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
>    __driCreateNewScreen_20050727 - succeeded
>    libGL warning: 3D driver claims to not support visual 0x22
>    libGL warning: 3D driver claims to not support visual 0x23
>    libGL warning: 3D driver claims to not support visual 0x24
>    libGL warning: 3D driver claims to not support visual 0x25
>    libGL warning: 3D driver claims to not support visual 0x26
>    libGL warning: 3D driver claims to not support visual 0x27
>    libGL warning: 3D driver claims to not support visual 0x28
>    libGL warning: 3D driver claims to not support visual 0x29
>    libGL warning: 3D driver claims to not support visual 0x2a
>    libGL warning: 3D driver claims to not support visual 0x2b
>    libGL warning: 3D driver claims to not support visual 0x2c
>    libGL warning: 3D driver claims to not support visual 0x2d
>    Error: couldn't find RGB GLX visual
>
>
> /usr/lib64/xorg/modules/dri/unichrome_dri.so listed above is the one I 
> just built from source.
>
> glxgears doesn't work at all.
>
> I'm using gentto, BTW, and also have mesa 6.4.2 installed.
>
> Anything I can do to debug further ?

Ah, I see in the kernel messages :-

[drm] Initialized drm 1.0.1 20051102
PCI: Unable to reserve mem region #1:4000000 at f0000000 for device 
0000:01:00.0
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 169
[drm] Initialized via 2.9.1 20060111 on minor 0:
[drm] Used old pci detect: framebuffer loaded
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
irq 169: nobody cared (try booting with the "irqpoll" option)

Call Trace: <IRQ> <ffffffff8014dc54>{__report_bad_irq+48} 
<ffffffff8014decf>{note_interrupt+558}
       <ffffffff8014d732>{__do_IRQ+196} <ffffffff80110adc>{do_IRQ+43}
       <ffffffff8028ae4e>{acpi_processor_idle+0} 
<ffffffff8010ecdc>{ret_from_intr+0}
        <EOI> <ffffffff8028ae3c>{acpi_safe_halt+38} 
<ffffffff8028afdb>{acpi_processor_idle+397}
       <ffffffff8028ae4e>{acpi_processor_idle+0} 
<ffffffff8028ae4e>{acpi_processor_idle+0}
       <ffffffff8010cc8e>{cpu_idle+68} <ffffffff80598742>{start_kernel+393}
       <ffffffff8059824c>{_sinittext+588}
handlers:
[<ffffffff88142000>] (via_driver_irq_handler+0x0/0x183 [via])
Disabling IRQ #169


The IRQ's don't look too good :-(