In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>* Magnus Hyllander <[EMAIL PROTECTED]> [2004-05-14 20:46]:
>> Booting with "linux ramdisk_size=8192" gets me past the previous
>> problem. Now I get other errors just a little later during initial boot:
>>
>> Freeing unused kernel memory: 132k freed
>> Setting up filesystem, please wait ...
>> echo[8]: Unimplemented SPARC system call 188
>> mount[9]: Unimplemented SPARC system call 188
>> uname[11]: Unimplemented SPARC system call 188
>> grep[12]: Unimplemented SPARC system call 188
>> init[10]: Unimplemented SPARC system call 188
>> [[13]: Unimplemented SPARC system call 188
>> Segmentation fault
>> BusyBox v1.00-pre10 (Debian 20040415-3) multi-call binary
>
>And idea?
This is one of the possible symtoms of the bterm/sparc framebuffer bug.
Try adding the "debian-installer/framebuffer=false" option to the silo
command line.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
