[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-xwin-discuss
Subject:    Re: [xwin-discuss] [osol-discuss] Wont boot up to GDM using Live CD
From:       Vikram Hegde <Vikram.Hegde () Sun ! COM>
Date:       2009-09-27 19:39:47
Message-ID: 4ABFBF83.6080102 () sun ! com
[Download RAW message or body]

Hi,

Any one of the entries in the compatible list (in prtconf output) can 
cause the driver to bind to the hardware.
I see pci1458,d000 in the compatible list which doesn't have 2e32. One 
way to find the alias being used is to
run prtconf -D. This will give you the driver bound to the chipset. Then 
search for that driver in /etc/driver_aliases.
Then compare all aliases for that driver in /etc/driver_aliases against 
the compatible list for the chipset in prtconf output.
That will give you the compatible name that cuases driver binding.

Vikram

rick ratta wrote:
> I've been trying to analyze my issues with video rendering on this PC with an intel G41 chipset.
>
> Forgive me if my questions or observations are idiotic, but I've been trying to understand how this
> chipset is matched to a driver. And I think the mapping is expressed in the
> /etc/driver_aliases file.
>
> When I look at prtconf -v I believe the chipset is identified as
>
>         display, instance #0
>             Driver properties:
> ... stuff deleted
>                 name='compatible' type=string items=7
>                     value='pci8086,2e32.1458.d000.3' + 'pci8086,2e32.1458.d000'
>  + 'pci1458,d000' + 'pci8086,2e32.3' + 'pci8086,2e32' + 'pciclass,030000' + 'pc
> iclass,0300'
> ...stuff deleted
>             Device Minor Nodes:
>                 dev=(99,0)
>                     dev_path=/pci@0,0/display@2:text-0
>                         spectype=chr type=minor
>                         dev_link=/dev/fbs/text-0
>                         dev_link=/dev/vt00
>                         dev_link=/dev/fb
>                     Minor properties:
>                         name='ddi-kernel-ioctl' type=boolean dev=(99,0)
>                 dev=(99,1)
>                     dev_path=/pci@0,0/display@2:agpmaster0
>                         spectype=chr type=minor
>                         dev_link=/dev/agp/agpmaster0
>
> But I cannot find any references to the "pci8086,2e32" anywhere.
> So how does this chipset map to any driver. I'm not sure I understand all the
> nomenclature in this output with respect the "1458" "subsystem".
>
> I've poked into the opensolaris source and I can see where the driver_aliases is 
> constructed and where most "GXX" chipsets are defined. And indeed in the 
>
> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/intel/io/drm/drm_pciids.h
>
> file there is
>
> 	{0x8086, 0x2E32, CHIP_I9XX|CHIP_I965, "Intel G41"}, \
>
> But there is no entry added to /etc/driver_aliases for "2e32" in the
>
> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/pkgdefs/SUNWdrmr/postinstall
>
> script which seems to reflect the /etc/drivers_aliases file on my system.
>
> Again if I am missing something significant in this analysis, I'd appreciate a kick in the
> head. Or if it appears that I haven't read enough documentation to understand the system
> files, I'll take a pointer to some doc.
>
> Thanks
>
> -rick
>   


-- 
==============================================================================
dodo: A bird that forgot how to fly. Going, going, going ...
==============================================================================

_______________________________________________
xwin-discuss mailing list
xwin-discuss@opensolaris.org
[prev in list] [next in list] [prev in thread] [next in thread]