Skip site navigation (1)Skip section navigation (2)
Date:      25 Jul 2003 12:20:50 -0400
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        "Greg 'groggy' Lehey" <grog@freebsd.org>
Cc:        FreeBSD mobile Mailing List <freebsd-mobile@freebsd.org>
Subject:   Re: Problems with X on Dell Inspiron 5100?
Message-ID:  <1059150050.300.18.camel@gyros>
In-Reply-To: <20030725083002.GB5448@wantadilla.lemis.com>
References:  <20030725083002.GB5448@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-uGNKI9kauafYmur6ODqw
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, 2003-07-25 at 04:30, Greg 'groggy' Lehey wrote:
> Is anybody using X and -CURRENT on a Dell Inspiron 5100?  I've spent
> the last couple of days trying to get the *(&*&* to work, and I'm
> still having a lot of trouble.  X dies with a SIGSEGV:
>=20
> (II) RADEON(0): initializing int10
> (=3D=3D) RADEON(0): Write-combining range (0xa0000,0x20000) was already c=
lear
> (=3D=3D) RADEON(0): Write-combining range (0xc0000,0x40000) was already c=
lear
> (WW) RADEON(0): Bad V_BIOS checksum
> (II) RADEON(0): Primary V_BIOS segment is: 0xc000
> (=3D=3D) RADEON(0): Write-combining range (0x0,0x1000) was already clear
> (--) RADEON(0): Chipset: "ATI Radeon Mobility M7 LW (AGP)" (ChipID =3D 0x=
4c57)
> (--) RADEON(0): Linear framebuffer at 0xf0000000
> (--) RADEON(0): MMIO registers at 0xe0100000
> (=3D=3D) RADEON(0): Write-combining range (0xe0100000,0x80000) was alread=
y clear
> (--) RADEON(0): VideoRAM: 16384 kByte (64-bit DDR SDRAM)
> (=3D=3D) RADEON(0): Write-combining range (0xe0100000,0x80000) was alread=
y clear
> (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect
> (II) RADEON(0): Primary Display =3D=3D Type 2
> (II) RADEON(0): Panel ID string: =FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=
=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF
> (II) RADEON(0): Panel Size from BIOS: 65535x65535
>=20
>    *** If unresolved symbols were reported above, they might not
>    *** be the reason for the server aborting.
>=20
> Fatal server error:
> Caught signal 11.  Server aborting
>=20
> This happened when I ran X -configure.  The same laptop works fine
> with Knoppix (CD-based Linux distro), so I took the Knoppix config
> file and tried that.  Modulo a couple of minor differences it happened
> again.  It also happens both with 4.2.1 and 4.3.0
>=20
> The corresponding Knoppix output at this point was:
>=20
> (II) RADEON(0): initializing int10
> (II) RADEON(0): Primary V_BIOS segment is: 0xc000
> (--) RADEON(0): Chipset: "ATI Radeon Mobility LW (AGP)" (ChipID =3D 0x4c5=
7)
> (--) RADEON(0): Linear framebuffer at 0xf0000000
> (--) RADEON(0): MMIO registers at 0xe0100000
> (--) RADEON(0): VideoRAM: 16384 kByte (64-bit DDR SDRAM)
> (II) RADEON(0): Primary Display =3D=3D Type 2
> (II) RADEON(0): Panel ID string: G08303141XD
> (II) RADEON(0): Panel Size from BIOS: 1024x768
>=20
> Somehow it looks as if FreeBSD isn't reading the Video BIOS parameters
> correctly.  Has anybody seen this and done something about it?  I'll
> continue playing around, but it would be nice to hear of some solution
> close at hand.

Can you send me your XF86Config?  I got X working no problem on my 5150
yesterday, but I think we have slightly different Radeon cards.

Joe

>=20
> Greg
> --
> See complete headers for address and phone numbers
--=20
PGP Key : http://www.marcuscom.com/pgp.asc



--=-uGNKI9kauafYmur6ODqw
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQA/IVjib2iPiv4Uz4cRAnajAJ0f5kcrMJQu+tKLBH5NxZXVo7D5fQCeK0K/
kDe4Ronh6cBGXaANbC3MypI=
=Poeu
-----END PGP SIGNATURE-----

--=-uGNKI9kauafYmur6ODqw--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1059150050.300.18.camel>