Re: SuperSavage/IXC 64, no direct rendering

"Alex Deucher" <[email protected]>
Newsgroups gmane.comp.video.dri.user
Message-ID <[email protected]>
On 9/23/06, Robert Peter <[email protected]> wrote:
> > > Section "Device"
> > >     Identifier  "savage"
> > >         Driver                  "savage"
> > >         Option "AGPSize"        "16"
> > >         Option "AGPMode"        "4"
> > >         Option "DmaType"        "AGP"
> > >         Option "DmaMode"        "None"
> > >         Option "BusType"        "PCI"
> >
> > BusType PCI and DmaType AGP contradict each other. Try removing one or
> > both. The log file indicates that you have an AGP card. Are you forcing
> > BusType PCI for a specific reason?
>
> No, actually I got those lines from the web from someone pretending he has a
> working DRM with that chipset. I tried removing one/both, but it did not help
>
> > Everything looks more or less ok until here. There should be more
> > information about the cause of the failure in the kernel log. What does
> > dmesg say?
>
> dmesg after starting xorg:
> mtrr: MTRR 2 not used
> mtrr: 0xe8000000,0x4000000 overlaps existing 0xe8000000,0x1000000
> mtrr: base(0xe4000000) is not aligned on a size(0x5000000) boundary
> mtrr: 0xe8000000,0x4000000 overlaps existing 0xe8000000,0x1000000
> mtrr: base(0xe4000000) is not aligned on a size(0x5000000) boundary
> mtrr: 0xe8000000,0x4000000 overlaps existing 0xe8000000,0x1000000
> mtrr: base(0xe4000000) is not aligned on a size(0x5000000) boundary
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
> [drm:savage_bci_init] *ERROR* savage_bci_init called without lock held,
> held  -2147483648 owner d6da8e60 d4f5cf20
>
> Other drm related messages in kernel log:
> [drm] Initialized drm 1.0.1 20051102
> [drm] Initialized savage 2.4.1 20050313 on minor 0:
> [drm] Used old pci detect: framebuffer loaded
>
>
>
> Maybe someone understands that message (I have no idea actually).


you might try the savage driver from git head.  There were some
locking problems with 7.1 that I recently fixed.

Alex

>
> Thank you,
>
> Robert

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.