Re: 5.3-BETA1 for Alpha available

On Wed, 2004-08-25 at 01:14, Marcel Moolenaar wrote:
> On Wed, Aug 25, 2004 at 12:49:45AM +0200, Andreas Kohn wrote:
> 
> > With the miniinst I get a nice panic on boot:
> > 
> > >>>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
> > 
> > fatal kernel trap:
> > 
> >     trap entry     = 0x2 (memory management fault)
> >     cpuid          = 0
> >     faulting va    = 0x88100050
> 
> Is your SRM console serial or graphical?
>
> I have a similar looking problem when I switch the console to graphical.

>>> show
[...]
console                 graphics 
[...]

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:
> 
> 	set hint.sc.0.disable="1"
(disable or disabled? I tried both in the following cases)

console=serial, sc=disabled: same panic.
console=graphics, sc=disabled: same panic.

> 
> > This is a boot message from 5.2-CURRENT (May 2):
> 
> *snip*
> > pci0: <display> at device 13.0 (no driver attached)
> 
> 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. 
Or should I instead try to find the point in time where tga stopped
working?