Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Aug 2004 01:34:45 +0200
From:      Andreas Kohn <andreas.kohn@gmx.net>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        current@freebsd.org
Subject:   Re: 5.3-BETA1 for Alpha available
Message-ID:  <1093390484.3554.45.camel@klamath.ankon.de.eu.org>
In-Reply-To: <20040824231428.GB4049@dhcp53.pn.xcllnt.net>
References:  <20040824183019.GA82339@freebie.xs4all.nl> <1093387784.3554.28.camel@klamath.ankon.de.eu.org> <20040824231428.GB4049@dhcp53.pn.xcllnt.net>

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

--=-LivBiapChe5P4i5wUo4c
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2004-08-25 at 01:14, Marcel Moolenaar wrote:
> On Wed, Aug 25, 2004 at 12:49:45AM +0200, Andreas Kohn wrote:
>=20
> > With the miniinst I get a nice panic on boot:
> >=20
> > >>>boot dka100 -flags h
> > (boot dka100.1.0.6.0 -flags h)
> *snip*
> > tga0: <DEC TGA (21030) 2D Graphics Accelerator> mem
> > 0x88000000-0x8fffffff irq 9 at device 13.0 on pci0
> >=20
> > fatal kernel trap:
> >=20
> >     trap entry     =3D 0x2 (memory management fault)
> >     cpuid          =3D 0
> >     faulting va    =3D 0x88100050
>=20
> Is your SRM console serial or graphical?
>
> I have a similar looking problem when I switch the console to graphical.

>>> show
[...]
console                 graphics=20
[...]

Same panic happens if
>>> set console serial
>>> boot dka100 -flags h

(same means same, addresses, position, etc)

> BTW: what happens if you disable syscons with:
>=20
> 	set hint.sc.0.disable=3D"1"
(disable or disabled? I tried both in the following cases)

console=3Dserial, sc=3Ddisabled: same panic.
console=3Dgraphics, sc=3Ddisabled: same panic.

>=20
> > This is a boot message from 5.2-CURRENT (May 2):
>=20
> *snip*
> > pci0: <display> at device 13.0 (no driver attached)
>=20
> There's no TGA driver there...
Yes, I saw that too few minutes after sending the mail. The machine has
said TGA adapter in it, but I don't have a compatible monitor, so I'm
only operating it over serial console. (And ssh)
Guess I removed the driver when cleaning the config. (Long time
ago...somewhen in March IIRC).
I'm currently cross-building a 6-CURRENT world, and will try that as
well.=20
Or should I instead try to find the point in time where tga stopped
working?

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

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

iD8DBQBBK9CTYucd7Ow1ygwRAh8qAJ0Z2juFH/S9Y2GjQChQk/kwr3g1xACdHQ2q
1MN2rgatcxB6Ki4RU1awEJs=
=V4CF
-----END PGP SIGNATURE-----

--=-LivBiapChe5P4i5wUo4c--



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