Hello I have a sun blade 100 at work that I basically just use as a file server and was wanting to install the latest gentoo on it.
The live cd works great on it and I am able to compile and install a kernel on the box.
When it goes to boot the kernel image in silo the cursor just spins slow and eventually if I let it go long enough it will error out with the mmu fast error message.
the kernel is 4.0.5 and I just want to get a basic install of linux on it so I can just use it as a jump server and file server so I can ssh to other boxes that I administer.
I have tried numerous items but I have a feeling I am not configure silo correctly and the initrd. I have gotten gentoo installed on x86 boxes so I know I can do it but this box has just gotten the best of me.
I am just looking for suggestions or tips I could try to get this box to boot. It is a basic sun blade with 2 gig of memory and two 20 gig disks. I installed debian on it so I know Linux can work on it but I really want to switch to gentoo.
Sun Blade 100 and Kernel 4.0.5
Message
- Keruskerfuerst
- Advocate
- Posts: 2289
- Joined: Wed Feb 01, 2006 3:37 pm
- Location: near Augsburg, Germany
- Roman_Gruber
- Advocate
- Posts: 3858
- Joined: Tue Oct 03, 2006 8:43 am
- Location: Austro Bavaria
well.
just chroot from debian. and try to reuse the kernel settings form debian / there must be some sort of offical kernel config file => check if config.gz or what it is called exists in /proc in your running debian...
If you need diskspace, e.g. gparted livecd / liveusb can squeeze down your partition assuming you used something which is supported.
and, try to figure out whihc kernel modules are in use . it seems build in kernel modules are not shown as loaded and thats kinda tricky than.
building a kernel is rather tricky but there were pages out there where you could enter lspci output and get a list of suggested kernel settings, do not ask me where it is, i used that page 3 years ago.
Personally I would changeroot from a running distribution. i usually install a noobish distro like linux mint and chroot from that, when mint does not work than i use suse, arch linux or wahtever just suits my taste.
and remember 64 bit distro => chroot => 64 bit
but i doubt you can chroot from 32bit distro into 64 bit ... just in case ...
You may consider using lvm and adding that debian partition after installing to the phyisical extents of lvm and change your partition layout ...
just chroot from debian. and try to reuse the kernel settings form debian / there must be some sort of offical kernel config file => check if config.gz or what it is called exists in /proc in your running debian...
If you need diskspace, e.g. gparted livecd / liveusb can squeeze down your partition assuming you used something which is supported.
and, try to figure out whihc kernel modules are in use . it seems build in kernel modules are not shown as loaded and thats kinda tricky than.
building a kernel is rather tricky but there were pages out there where you could enter lspci output and get a list of suggested kernel settings, do not ask me where it is, i used that page 3 years ago.
Personally I would changeroot from a running distribution. i usually install a noobish distro like linux mint and chroot from that, when mint does not work than i use suse, arch linux or wahtever just suits my taste.
and remember 64 bit distro => chroot => 64 bit
but i doubt you can chroot from 32bit distro into 64 bit ... just in case ...
You may consider using lvm and adding that debian partition after installing to the phyisical extents of lvm and change your partition layout ...
- NeddySeagoon
- Administrator
- Posts: 56264
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
First a question, when booting your system, do you see the initial silo message of type
It must come first. If not, silo is misconfigured.
If you have a misconfigured kernel I would propose to do the following steps:
* If the kernel of the livecd works fine, just build this kernel. The .config file is availiable under /proc/config.gz on the livecd. Emerge the proper kernel sources. The livecd of 20141201 uses a 3.14.14 kernel
* Try to add both the gz-kernel image and in a separate section the uncompressed kernel image to silo.conf . Try both. For me recently the uncompressed kernel image did not work.
* If you can reproduce the kernel from the livecd you can step by step remove unused drivers from the kernel configuration to get a smaller kernel.
* Then - if you really want a 4.X kernel - you can do a kernel upgrade (e.g. use `make oldconfig')
Then this kernel should boot fine.
Code: Select all
SILO Version X.Y.ZIf you have a misconfigured kernel I would propose to do the following steps:
* If the kernel of the livecd works fine, just build this kernel. The .config file is availiable under /proc/config.gz on the livecd. Emerge the proper kernel sources. The livecd of 20141201 uses a 3.14.14 kernel
* Try to add both the gz-kernel image and in a separate section the uncompressed kernel image to silo.conf . Try both. For me recently the uncompressed kernel image did not work.
* If you can reproduce the kernel from the livecd you can step by step remove unused drivers from the kernel configuration to get a smaller kernel.
* Then - if you really want a 4.X kernel - you can do a kernel upgrade (e.g. use `make oldconfig')
Then this kernel should boot fine.