Re: 6.0-current panic: loading radeon module

From: Eric Anholt (eta_at_lclark.edu)
Date: 06/20/05

  • Next message: Suleiman Souhlal: "Re: ufs LOR"
    To: Steve Roome <steve@pepcross.com>
    Date: Mon, 20 Jun 2005 12:31:32 -0700
    
    

    On Mon, 2005-06-20 at 15:52 +0100, Steve Roome wrote:
    > On Fri, Jun 17, 2005 at 12:40:22PM -0500, Jonathan Noack wrote:
    > > On 6/17/2005 12:18 PM, Martin Cracauer wrote:
    > > >Steve Roome wrote on Fri, Jun 17, 2005 at 05:03:32PM +0100:
    > > >>If it's any iterest, I had a similar experience earlier this week.
    > > >>
    > > >>xorg-server-6.8.99.5 with a radeon 9600 X and -current as of Monday
    > > >>causes my entire machine to freeze up completely rather than just
    > > >>panic.
    > > >>
    > > >>It's fine if I take drm option out of the x config again - so it's
    > > >>only when I actually use DRM, and for me it's a black screen and hard
    > > >>lockup.
    > > >
    > > >This is odd. DRI (and hence DRM) only support radeons up to 9200
    > > >(really 9250 probably). Your 9600 series shouldn't have a need for
    > > >the drm module in first place.
    > >
    > > The r300 project (http://r300.sourceforge.net) is getting tantalizingly
    > > close to usable DRI for newer radeons. I saw glxgears running at 2600+
    > > fps for about 15 seconds before the 3D engine on my 9800 Pro locked up.
    > > I finally got tired of manually merging Mesa commits and translating
    > > linux drm changes to bsd so I'm no longer using it. If you're
    > > interested, here's the basic instructions:
    > > http://lists.freebsd.org/pipermail/freebsd-x11/2005-May/001903.html
    > >
    > > Note that it requires a decent amount of effort just to get it to
    > > compile, much less do anything useful. Abandon hope, all ye who enter
    > > here...
    >
    > I was under the impresion that newer DRM stuff had been stuffed in
    > back in april directly from the r300 project.

    No, the DRM drivers come from DRM CVS as always. There had been some
    r300 stuff done in DRM CVS, but not enough, and r300 has their own fork
    of the DRM.

    > drm0: <ATI Radeon AP 9600> port 0xc000-0xc0ff mem 0xc0000000-0xcfffffff,0xe1000000-0xe100ffff irq 7 at device 0.0 on pci2
    > info: [drm] AGP at 0xb0000000 256MB
    > info: [drm] Initialized radeon 1.16.0 20050311 on minor 0
    > drm0: <ATI Radeon AP 9600> port 0xc000-0xc0ff mem 0xc0000000-0xcfffffff,0xe1000000-0xe100ffff irq 7 at device 0.0 on pci2
    > info: [drm] AGP at 0xb0000000 256MB
    > info: [drm] Initialized radeon 1.16.0 20050311 on minor 0
    >
    > I'm also using xorg snap 6.8.99.5 which should have the newer
    > development (r300+ I thought) DRI drivers in it.

    No, xorg-server-snap is just the snapshot of X.Org that X.Org
    distributes, not r300.sf.net's driver (built from Mesa).

    -- 
    Eric Anholt                                     eta@lclark.edu
    http://people.freebsd.org/~anholt/              anholt@FreeBSD.org
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Suleiman Souhlal: "Re: ufs LOR"

    Relevant Pages

    • Re: 2.6.11-mm3 - DRM/i915 broken
      ... Initialized drm 1.0.0 20040925 ... # Firmware Drivers ... # Performance-monitoring counters support ... # Video For Linux ...
      (Linux-Kernel)
    • Re: [Dri-devel] Re: [Linux-fbdev-devel] DRM and pci_driver conversion
      ... > there some helper function I missed? ... >> I don't think DRM drivers are doing things correctly yet. ... >> code for marking PCI resources as being in use while DRM is using them. ...
      (Linux-Kernel)
    • Re: radeon-pre-2
      ... > The resource reservation conflicts are already solved in the current ... > DRM code. ... I _think_ Alan's argument is that this isn't about the resource ... And the drivers would never become non-stealth. ...
      (Linux-Kernel)
    • Re: OpenGL-based framebuffer concepts
      ... Merging DRM and fbdev is ... independent drivers are trying to control the same piece of hardware. ... The merging is blocked because of issues with DRM on BSD (merging ...
      (Linux-Kernel)
    • Re: __initcall macros and C token pasting
      ... To start off with, I didn't write the DRM macros, I'm just trying to ... The DRM macros are there because of the way DRM is built. ... the core and the chip drivers. ... make the core into one module and the chip drivers into others. ...
      (Linux-Kernel)