Rebooting somehow stopped working

[John Klos]

Hi,

In the last month I switched from netbsd-5 to current on my Amiga 1200 so
that I could test the latest fixes to our tree. Somewhere along the line,
perhaps in current, I lost the ability to reboot my computer. With the
latest current (5.99.21 from yesterday), when I do a reboot, the machine
gets as far as showing me the rainbow flash screen (from the phase5
Blizzard 1260), but immediately after the rainbow flash, the video signal
disappears and the monitor turns itself off, and nothing.

Can anyone else test this out and see if this is happening elsewhere? My
A4000 is colocated and is running netbsd-5, and hasn't had any problems
rebooting on its own. I can't really try current on it at the moment.

Thanks,
John Klos

[Frank Wille]

On Thu, 5 Nov 2009 23:08:15 +0000 (UTC)
John Klos <john@...> wrote:

> In the last month I switched from netbsd-5 to current on my Amiga
> 1200 so that I could test the latest fixes to our tree. Somewhere
> along the line, perhaps in current, I lost the ability to reboot my
> computer.

*Sigh*, seems we are losing the A1200. No active NetBSD/amiga developer
owns one. The keyboard-problem is another point. :|


> With the latest current (5.99.21 from yesterday), when I do
> a reboot, the machine gets as far as showing me the rainbow flash
> screen (from the phase5 Blizzard 1260), but immediately after the
> rainbow flash, the video signal disappears and the monitor turns
> itself off, and nothing.

Option P5PPC68KBOARD was defined, for the correct reboot-routine?


> Can anyone else test this out and see if this is happening elsewhere?

Until 5.99.20 there was no problem, neither with my A3000 nor with my
A4000.


--
Frank Wille

[Mike-183]

I had problems with this on linux too, i had to change the kickstart
pointer address in the kernel as i am using the map rom, this worked
then, but it didnt work this time around for some reason.

-Mike
2009/11/6 Frank Wille <frank@...>:

> On Thu, 5 Nov 2009 23:08:15 +0000 (UTC)
> John Klos <john@...> wrote:
>
>> In the last month I switched from netbsd-5 to current on my Amiga
>> 1200 so that I could test the latest fixes to our tree. Somewhere
>> along the line, perhaps in current, I lost the ability to reboot my
>> computer.
>
> *Sigh*, seems we are losing the A1200. No active NetBSD/amiga developer
> owns one. The keyboard-problem is another point. :|
>
>
>> With the latest current (5.99.21 from yesterday), when I do
>> a reboot, the machine gets as far as showing me the rainbow flash
>> screen (from the phase5 Blizzard 1260), but immediately after the
>> rainbow flash, the video signal disappears and the monitor turns
>> itself off, and nothing.
>
> Option P5PPC68KBOARD was defined, for the correct reboot-routine?
>
>
>> Can anyone else test this out and see if this is happening elsewhere?
>
> Until 5.99.20 there was no problem, neither with my A3000 nor with my
> A4000.
>
>
> --
> Frank Wille
>

[Ignatios Souvatzis-4]

On Fri, Nov 06, 2009 at 03:52:16PM +0100, Frank Wille wrote:

> On Thu, 5 Nov 2009 23:08:15 +0000 (UTC)
> John Klos <john@...> wrote:
>
> > In the last month I switched from netbsd-5 to current on my Amiga
> > 1200 so that I could test the latest fixes to our tree. Somewhere
> > along the line, perhaps in current, I lost the ability to reboot my
> > computer.
>
> *Sigh*, seems we are losing the A1200. No active NetBSD/amiga developer
> owns one. The keyboard-problem is another point. :|

I have one in storage - need to revive it, apparently.

        -is

[John Klos]

Hi,

> *Sigh*, seems we are losing the A1200. No active NetBSD/amiga developer
> owns one. The keyboard-problem is another point. :|

Yeah, I suppose I'd consider myself mostly inactive - I barely have time
to report issues when I see them!

> Option P5PPC68KBOARD was defined, for the correct reboot-routine?

Yes, although I intend to try some GENERIC kernels and see if it's
something else. My kernels are usually custom because I need to have the
root device explicitely set since Blizzard 1260's SCSI can't boot from
bootblocks on SCSI drives, so I boot from a CompactFlash card connected to
the motherboard IDE.

>> Can anyone else test this out and see if this is happening elsewhere?
>
> Until 5.99.20 there was no problem, neither with my A3000 nor with my
> A4000.

I posted something here in case anyone changed anything that might've led
to this, but I suppose not. I'll see if I can narrow things down a bit.

Thanks,
John

[John Klos]

Hi,

Here's a followup: this happens when booting from the bootblock and going
into AGA mode. I can boot with exactly the same options (netbsd -ASn2) and
just remove the "A", and it'll reboot on its own just fine thereafter.

I checked all the other things which have changed recently - the PCMCIA
card, the devices on the SCSI chain, and none of them matter. I also
checked to see if this is true regardless of the version of NetBSD, and it
happens with netbsd-5 going back to August through current from a few days
ago. It also happens regardless of using wscons or not.

I used to have the kernel not use AGA modes by default because I have a
scandoubler and I thought that 15 kHz modes would allow text to scroll
faster, but I tested this while I had the machine local, and it's not, so
I decided to update the bootblock to allow AGA mode. This was after the
power supply blew up, and it hasn't been back to the datacenter since,
which is why I'm only noticing now.

I also tried updating the bootblocks to netbsd-5 from today, and I see the
same behaviour.

Any ideas?

John

[Jukka Andberg]

Hi,

On Thu, 5 Nov 2009 23:08:15 +0000 (UTC) John Klos <john@...> wrote:
> In the last month I switched from netbsd-5 to current on my Amiga 1200 so
> that I could test the latest fixes to our tree. Somewhere along the line,
> perhaps in current, I lost the ability to reboot my computer. With the

I did some quick tests with Blizzard 1230-IV and BlizzardPPC/040.

On current both worked fine.
On netbsd-5 the BlizzardPPC would hang on reboot maybe one time in five, but that card has always had some trouble booting for me. On cold boot it always hangs, requiring reset by keyboard to start.

Also no keyboard problems in any configuration.

-- jukka