Talking to one of the guys from the silo mailling list, I've found out that it isn't a silo problem. Instead it is a kernel problem. I'm getting ready to recompile and look for options to change. Anyone have an idea what might cause the kernel to return the "No serial devices found" message?

Well the first thing that comes to mind is lack of serial support all together. I'd confirm you have support in your config. If it is in your config, I'd double check that the serial device doesn't need a special kernel module.

The lspci command from the pciutils package may be helpful to find what kind of serial device is in the Blade 1000.

I want to say that it is the siemens serial support under 'misc linux/sparc drivers'. I compiled it in as a module the first time round when I got the error. I'm not 100% sure, but pretty close. I've got another sunblade 1000 I'm installing gentoo on today with the Sept05 Sparc64 cd. I'll find out if that wasn't the one when I get the error haha.

I'd recommend gentoo-sources to begin with.
Also 2.6 is considered experimental for sparc yet, even though it works mostly fine for blade 1000/2000 (except for bbc_i2c which controls the thermals).
So you'd need to switch to the 2.6 profile (2006.0 instead of 2006.0/2.4) and package.keywords gentoo-sources (or vanilla-sources if you prefer so).
Remember to emerge udev too and unmerge devfsd.
For the latest toys, upgrade linux-headers and then re-emerge glibc.
That should be it._________________Gustavo Zacarias
Gentoo/SPARC monkey

1) What are my step exactly to switch to the 2.6 profile? (I've installed the system from the latest official LiveCD for Sparc) , and actually I'm now (compiling kernel) at chrooted environment of the LiveCD.

So where could I find 2.6 profile that supports 2.6 kernel and put it in /usr/portage/profiles/default-linux/sparc/sparc64/2006.0/2.6 directory, or should I replace the whole /usr/portage/profiles/default-linux/sparc/sparc64/2006.0/ directory?

2) How to upgrade linux-headers?
3) Any other tips, may be conserning silo configuration and module installation?
4) What modules you would advice to enter to /etc/modules.autoload.d/kernel-2.6?
What about:

2006.0 IS the 2.6 profile, don't go package.unmasking stuff around if you've got the wrong profile - you'll only have trouble and miss the good stuff. If you check /etc/make.profile you'll see it's pointing at 2006.0/2.4.
You'll just need to package.keywords a kernel once you're in the right profile - nothing more.
Also don't use the latest & greatest vanilla-sources - it may not be so great, check the hardware compatibility list or stick with the latest ~sparc gentoo-sources.
After switching to the 2.6 profile emerge linux-headers glibc to "upgrade".
The silo configuration is the same._________________Gustavo Zacarias
Gentoo/SPARC monkey