[Openchrome-users] OpenChrome and 775VM800 - Progress
Thomas Hellstrom
thomas
Fri Feb 10 21:40:42 PST 2006
> Hell[o]
>
> A small progress report from 775VM800 front. After a quite long session on
> #unichrome I was able to get normal display on my board. But there is
> still some issues.
>
> 1. To get any normal display two options need to be added to Device
> section
>
> Option "VBEModes" "on"
> Option "NoDDC" "on"
>
> Doing this makes possible to get 1024x768 at 75 with drivers patched a bit
> for VM800. Monitor can easyly reeach 85 but 75 is not so bad.
Morgoth, could you make sure you use latest openchrome SVN, add
Option "PrintVGARegs" to your Xorg.conf, post your compressed xorg.conf at
the wiki logFiles file gallery.
Then it would be helpful if you could also upload a couple of compressed
Xorg logs for startups with and without VBEModes, and for at least two
different resolutions. (at least 4 logs).
DRI works *almost* fine. glxgears works with quite good result around
> ~650fps. But lockups randomly with followng message in logs:
>
> [drm:via_hook_segment] *ERROR* Command regulator
> paused at count 8, address f9f80700, while current pause address is
> f9f81500.
> Please mail this message to <unichrome-devel at lists.sourceforge.net>
> [drm:via_hook_segment] *ERROR* Command regulator
> paused at count 4, address f9f0cd00, while current pause address is
> f9f0db00.
> Please mail this message to <unichrome-devel at lists.sourceforge.net>
> [drm:via_hook_segment] *ERROR* Command regulator
> paused at count 8, address f9e2ee00, while current pause address is
> f9e2fc00.
> Please mail this message to <unichrome-devel at lists.sourceforge.net>
>
These are common errors when using a fast processor, but they tend to go
away when the hardware is feeling well. AGP DMA is still a bit shaky but I
hope to get some hints from a guy familiar with the hardware. Until then,
don't use EnableAGPDMA.
> Tested with yesterday CVS snap.
>
> 3. Xv doesn't work at all, lockups the machine completly.
>
Strange. Xv should refuse to start with your chipset, or did you disable
the check?
> 4. It seems ID's for this board are still missing from sources (Both
> openchrome and DRI)
>
> via_id.c file from openchrome:
>
> + {"ASRock 775VM800", VIA_VM800, 0x1849,
> 0x3344, VIA_DEVICE_CRT},
>
> and drm_pciids.txt from DRM
>
> + 0x1106 0x3344 0 "VIA P4M800"
>
I'll have a look at the DRM.
Thanks.
/Thomas
> --------
> :: Morgoth/Dreamolers-CAPS && TBS ::
>
> ::: Homepage # http://binaryriot.com/dreamolers :::
> ::: Homepage # http://www.tbs-software.com/morgoth/ :::
> :: Email # morgoth6 at box43.pl ::
> ::: GG # 3681372 :::
>
> :: Pegasos User&Developer ::
>
>
>
> _______________________________________________
> openchrome-users mailing list
> openchrome-users at openchrome.org
> http://wiki.openchrome.org/mailman/listinfo/openchrome-users
>
>
More information about the Openchrome-users
mailing list