Subject: Re: -current kernel problems (new sbic.c related?)
To: Jeff Thieleke <firstname.lastname@example.org>
From: Michael L. Hitch <email@example.com>
Date: 08/23/1995 22:42:57
On Aug 23, 10:19pm, Jeff Thieleke wrote:
> I have not been able to use any of the recent kernels on my system. The
> last working version I have is from August 16. The symptoms are that upon
> reboot, the screen either stays black or slightly red and the monitor
> squeals like it is being oversynced.
> (Incidently, these are the indentical symptoms as I experienced when I
> tried to use the LEV6_DEFER on older kernels, which also doesn't work!)
> I have been looking over the source-changes archive, and it looks like
> the only major changes have been the SCSI disconnects, siop, and sbic
> changes. Could one of these had an adverse effect on my A530's SCSI
> controller? Also, could anything be done to get the LEV6_DEFER to work?
I'll bet you are trying to use /dev/reload to start the new kernel.
That will NOT WORK if the kernel_reload() procedure in locore.s is not
at the same address in the new kernel as it is in the running kernel.
Changing LEV6_DEFER changes the code in locore.s, and kernel_reload()
will change position. The latest big changes in -current for the Amiga
had a change in locore.s that will also change the location of
kernel_reload(). You HAVE to boot the new kernel from AmigaDOS in this
case. [Once the new kernel has been booted from AmigaDOS, you can use
the /dev/reload - until the kernel_reload() procedure changes location
Michael L. Hitch INTERNET: firstname.lastname@example.org
Office of Systems and Computing Services
Montana State University Bozeman, MT USA