Hi Octave,
> These are the exact problems that I've been running into with trying to
> make a generic kernel for slack. I have not had any luck with it as of
> yet. I hope we don't have to make box specific kernels for the install.
> That would suck.. but seeing how there are issues.. who knows.
I still believe it is possible to create generic kernels for these boxes,
since the Debian kernel I'm booting is a generic one... I'm looking high
and low for the .config file that created that one.
>I have
> emailed the aboot people about the problems with the newer compressed
> kernels. Question...
Ok, I thought about doing that myself. But lets wait and see what kind of
responce you get before drowning them in email ;-)
>when you get a Kernel Oops.. is it right when an
> IDE device is detected... like a CDROM?
No. I have no IDE devices in this box. Everything is SCSI (CD-ROM
included).
/Jesper
Octave J. Orgeron <octave@sun.com> wrote:
>Hi Jesper,
>
>These are the exact problems that I've been running into with trying to
>make a generic kernel for slack. I have not had any luck with it as of
>yet. I hope we don't have to make box specific kernels for the install.
>That would suck.. but seeing how there are issues.. who knows. I have
>emailed the aboot people about the problems with the newer compressed
>kernels. Question... when you get a Kernel Oops.. is it right when an
>IDE device is detected... like a CDROM?
>
>-Octave
>
>Jesper Juhl wrote:
>>
>> Hi Chris,
>>
>> I'm having strange problems with booting new kernels on my AS400 4/233.
>>
>> I can boot a prebuild Debian kernel and a SuSE kernel, but the generic
>> kernel provided with Slack does not work (as you know).
>>
>> I've tried building the exact configuration that you use for the generic
>> kernel, a generic kernel where the only change was to make it machine
>> specific and a very minimal machine specific kernel.
>>
>> The kernels all build fine and all seems well, but when I install them I
>> get SRM related errors when aboot tries to boot the kernel(s). The
errors
>> I'm getting are:
>>
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> ext2_blkno: error on iblk read
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> ext2_blkno: error on iblk read
>> failed to send Read to dka0.0.0.6.0
>> failed to send Read to dka0.0.0.6.0
>> [... goes on like that for a minute or two ...]
>> [... then finaly stops with the following ...]
>> aboot: segment 0, 3126632 bytes at 0xfffffc0000310000
>>
>> unzip: attempted to read past eof
>> aboot: loading uncompressed jjukernel1.gz...
>> aboot>
>>
>> I can then boot either my debian os suse kernel normally (sometimes it
>> does not stop at the prompt, and the errors just go on forever).
>>
>> I then tried reinstalling aboot, as I thought that might be where the
>> problem was hidden - but that didn't change a thing.
>> Then I tried installing a noncompressed kernel image, as I found out
that
>> aboot (0.7 and 0.7a) aparently has some issues with compressed kernels
>> where kernel version >= 2.2.16 .
>>
>> Booting the noncompressed kernel was possible (at least partially), it
>> starts to load just fine but then panics - which means we are back to
the
>> original problem of kernel of a kernel Oops on this box :-(
>>
>> I will continue to try and build a kernel that will boot on this machine
>> so we can fix this issue properly.
>> At least we now know that compressed kernels can be a problem. Any clues
>> about how to fix the ?failed to send Read? problem???
>>
>> I'll keep looking for answers and solutions, but if you have any
>> input/ideas then please let me know :-)
>>
>> /Jesper Juhl
>
>--
>******************************************************
>* Octave J. Orgeron * Specializing in : *
>* Unix Systems Administrator * Solaris/Tru64/Linux *
>* Sun Microsystems, Inc. * Certified Solaris *
>* octave@sun.com * Systems Administrator *
>******************************************************
>
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT