I saw the sticky for the new gentoo-sources-2.6.27 that will allow be to run my SunBlade 1000 with the fcal disks. Just started playing with this box I had collecting dust yesterday, and found this issue to be a little annoying.

But, how do I get it? If I use ACCEPT_KEYWORDS="~sparc" and emerge --search gentoo-sources, I only see as far as 2.6.26-r1. And I'm not seeing anything in /usr/portage/profiles that would block it.

I'd rather go with a more recent kernel than going back to 2.6.17.

I've been using gentoo for several years now (on several x86 boxes), but feeling a bit like a noob trying to figure this out...

Any help?

Thanks.

Last edited by JCampy on Wed Nov 26, 2008 10:22 pm; edited 1 time in total

There is no gentoo-sources-2.6.27. 2.6.27 is still in development. You can check kernel.org to see for yourself.

If you want a 2.6.27 kernel via portage, you can unmask git-sources or vanilla-sources. Both have 2.6.27 - but beware, if you have an Intel e1000e ethernet card, the latest kernel may fry it. Other than that, keep in mind it is still under development. I'm using vanilla-sources-2.6.27_rc7, and it works fine. I needed it for sound and wireless on my new laptop. So far so good, but I do have to use the nVidia beta drivers with it.

Vanilla-sources work? I haven't seen that stated anywhere (maybe I missed it?).

Regarding following the qla2xxx doc, I was figuring that running with the latest base kernel would be a more likely scenario for success. The doc seems a little too - um - hackish. Am I mistaken in that?

Vanilla-sources work? I haven't seen that stated anywhere (maybe I missed it?).

blu3bird wrote:

To set it up you need to install the kernel

Code:

>=sys-kernel/vanilla-sources-2.6.27_rc1
or
>=sys-kernel/gentoo-sources-2.6.27

Both are fine (or will be, once released)

JCampy wrote:

Regarding following the qla2xxx doc, I was figuring that running with the latest base kernel would be a more likely scenario for success. The doc seems a little too - um - hackish. Am I mistaken in that?

Using an initramfs to prepare mounting the root filesystem is quite common, lvm for instance or some raid configurations. Or did you mean something else?_________________Black Holes are created when God divides by zero!

JCampy wrote:
Regarding following the qla2xxx doc, I was figuring that running with the latest base kernel would be a more likely scenario for success. The doc seems a little too - um - hackish. Am I mistaken in that?

Using an initramfs to prepare mounting the root filesystem is quite common, lvm for instance or some raid configurations. Or did you mean something else?

No, that was it.

So, I got all that installed, got the settings set, etc.. I ran into an issue where the driver appeared to need to be built into the kernel, so I reset that. Now, I see the driver start to load, but then I'm getting an error on an "Inconsistent NVRAM: chksum = 0x0", so the driver doesn't load, it seems (sorry for lacking the full output - I don't see any easy way to capture it).

I saw an email thread between a couple of developers working on the driver who narrowed the issue down to ql2xextended_error_logging = 1. Setting this to 0 seems to make this issue go away. And I see that I can do that via /etc/modprobe.conf, but since I'm building the module into the kernel this doesn't seem to help. Any thoughts?

As long as the driver has optional parameters, one can pass the parameters to the driver whether or not it is a module. For an in-kernel driver, the optional parameter(s) need to be added to the kernel boot line in your boot loader. See /usr/src/linux/Documentation/kernel-parameters for the correct syntax.