ports/148652: x11-drivers/xf86-video-intel support for HM55

[Mars G Miro]

The following reply was made to PR ports/148652; it has been noted by GNATS.

From: Mars G Miro <spry at anarchy.in.the.ph>
To: Chip Camden <sterling at camdensoftware.com>, bug-followup at freebsd.org
Cc:  
Subject: Re: ports/148652: x11-drivers/xf86-video-intel support for HM55
Date: Wed, 11 Aug 2010 23:41:06 +0800

 On Wed, Aug 11, 2010 at 11:35 PM, Chip Camden
 <sterling at camdensoftware.com> wrote:
 > Quoth Chip Camden on Tuesday, 10 August 2010:
 >> Quoth Mars G Miro on Wednesday, 11 August 2010:
 >> > On Tue, Aug 10, 2010 at 11:47 PM, Chip Camden
 >> > <sterling at camdensoftware.com> wrote:
 >> > > Quoth Mars G Miro on Tuesday, 10 August 2010:
 >> > >> +1 for this.
 >> > >>
 >> > >> I have an Asus K52J series laptop w/ an HM55 Ironlake chipset.
 >> > >>
 >> > >> Is it supposedly the intel driver for this? Because I don't see it =
 at
 >> > >> http://intellinuxgraphics.org/user.html .
 >> > >>
 >> > >> Is the driver development w/ intel now? Because, aside from the
 >> > >> sticker that says Nvidia GeForce 310M, I can see that there is a
 >> > >> driver for it at
 >> > >> http://www.nvidia.com/object/freebsd-x64-256.44-driver.html . I'm
 >> > >> currently delving into the xorg configuration, no luck so far. I'm =
 on
 >> > >> 8.1-RELEASE/amd64.
 >> > >>
 >> > >>
 >> > >
 >> > > If yours has an NVIDIA sticker, then I'd give the nvidia driver a tr=
 y.
 >> > > What does 'pciconf -vl | grep vga' show?
 >> > >
 >> > > In my ASUS notebook, the graphics is Intel Integrated HD and the pci=
 conf
 >> > > -vl gives a PCIID for vgapci0 that matches the HM55 (0x00468086), so=
  I think the
 >> > > intel driver will need to support HM55 for this to work. =A0I'm stil=
 l
 >> > > patiently using vesa.
 >> > >
 >> >
 >> > hmmm, we might be using similar chipsets:
 >> >
 >> > vgapci0 at pci0:0:2:0: =A0 =A0 class=3D0x030000 card=3D0x1c221043 chip=3D=
 0x00468086
 >> > rev=3D0x12 hdr=3D0x00
 >> > =A0 =A0 vendor =A0 =A0 =3D 'Intel Corporation'
 >> > =A0 =A0 class =A0 =A0 =A0=3D display
 >> > =A0 =A0 subclass =A0 =3D VGA
 >> > =A0 =A0 cap 05[90] =3D MSI supports 1 message
 >> > =A0 =A0 cap 01[d0] =3D powerspec 2 =A0supports D0 D3 =A0current D0
 >> > =A0 =A0 cap 13[a4] =3D PCI Advanced Features: FLR TP
 >> >
 >> > dmesg says:
 >> >
 >> > agp0: <Intel Ironlake (M) SVGA controller> on vgapci0
 >> > agp0: detected 32764k stolen memory
 >> > agp0: aperture size is 256M
 >> >
 >> >
 >> >
 >> > > --
 >> > > Sterling (Chip) Camden =A0 =A0| sterling at camdensoftware.com | 2048D/=
 3A978E4F
 >> > > http://camdensoftware.com | http://chipstips.com =A0 =A0 =A0 =A0| ht=
 tp://chipsquips.com
 >> > >
 >> >
 >> >
 >> >
 >> > --
 >> > cheers
 >> > mars
 >> > -----
 >>
 >> yup -- exactly the same.
 >>
 >> --
 >> Sterling (Chip) Camden =A0 =A0| sterling at camdensoftware.com | 2048D/3A97=
 8E4F
 >> http://camdensoftware.com | http://chipstips.com =A0 =A0 =A0 =A0| http:/=
 /chipsquips.com
 >
 >
 > BTW, the only way I could get even 'vesa' to work with this was to
 > specify the refresh rates for the monitor in xorg.conf. =A0E.g.:
 >
 > Section "Monitor"
 > =A0 =A0 =A0 =A0Identifier =A0 "Monitor0"
 > =A0 =A0 =A0 =A0VendorName =A0 "Monitor Vendor"
 > =A0 =A0 =A0 =A0ModelName =A0 =A0"Monitor Model"
 > =A0 =A0 =A0 =A0HorizSync =A0 =A030-107
 > =A0 =A0 =A0 =A0VertRefresh =A048-120
 > =A0 =A0 =A0 =A0Option =A0 =A0 =A0 "DPMS"
 > =A0 =A0 =A0 =A0ModeLine =A0 =A0 "1600x900" 110.4 1600 1664 1706 2000 900 =
 903 906 920 -hsync -vsync
 > EndSection
 >
 >
 
 Yeah the vesa configuration wasn't that hard... but I want more ;-)
 
 I'm currently browsing thru the nvidia forums...
 
 
 > --
 > Sterling (Chip) Camden =A0 =A0| sterling at camdensoftware.com | 2048D/3A978=
 E4F
 > http://camdensoftware.com | http://chipstips.com =A0 =A0 =A0 =A0| http://=
 chipsquips.com
 >
 
 
 
 --=20
 cheers
 mars
 -----