[cAos-devel] Upgrading cAos kernel?
Tim Leger
tleger at cs.wright.edu
Mon Jan 15 19:14:37 GMT 2007
Hi Greg,
Well I tried the newer kernels (2.6.18 & 2.6.19) Michael pointed me
too, but still no luck. On a plus side though, it does see the built-in
ethernet port now. However, when I try to boot from the onboard SATA
controller ports it gives me an error about not being able to open
/dev/suspend2/ and then another error about opening /dev/console:2,
followed quickly after that by a kernel panic - not syncing. I'll keep
an eye out for the beta3 release of cAos3 and try it out this
motherboard as soon as I can.
Regards, Tim Leger
> Michael seems to already have the kernel update in testing for caos2,
> and I am building caos3 kernel and iso update now. Should be ready in
> a day or so. I will send a notice to the primary caos list when I get
> the caos server 3 beta3 posted for initial testing.
>
> BTW: Stateless is cool, give it a whirl. ;)
>
> Thanks and good luck!
>
> Greg
>
> On Jan 14, 2007, at 8:23 PM, Tim Leger wrote:
>
>
>> Hi Greg,
>>
>> Thanks for the quick reply. To be honest, it doesn't really
>> matter
>> which version of cAos I use, just as long as I can get the motherboard
>> SATA controller and Ethernet port to work. While the hardware is
>> all 64
>> bit and I plan on using the 64 bit version of cAos, I do remember
>> installing some 32 bit libraries (libstda++.so.5 if I recall) to
>> satisfy
>> the Intel compilers we use. The troublesome motherboards are for a
>> small (16 node) Beowulf cluster that I was asked to setup similar
>> to the
>> 96 node cluster I'm in charge of at the university. On our 96 node
>> cluster, I used cAos 2.2.2b and setup system imager with pxe boot to
>> handle cloning the 92 compute nodes as they were turned on along with
>> Torque to manage job submission and queuing. I didn't chose to use
>> warewulf since each compute node has a hard drive for local scartch
>> space and using a small amount for the system made sense. For the few
>> months our 96 node cluster has been up, it's been running great. This
>> is probably the reason I was asked to setup this other 16 node
>> cluster,
>> just wish now I had been involved in choosing the hardware, lol.
>> As I said earlier, I did manage to get cAos installed by using a
>> borrowed SATA controller card. Is there a way to just replace the
>> forcedeth and sata_nv modules with newer ones so they would support
>> the
>> motherboard chipset or would it be better to upgrade the kernel
>> instead? I'd like to get this fixed as soon as possible, but I
>> realize
>> you probably have a lot of other things you're working on regarding
>> the
>> new release. I really appreciate your help and keep up the good work.
>>
>> Thanks, Tim Leger
>>
>>> Hiya, I have it on my todo list to upgrade Caos server 3 and that
>>> version of Cinch to the 2.6.18 kernel, but just havent had much of a
>>> chance yet. What is your priority level on this?
>>>
>>> Will Caos server 3 meet your application and library requirements for
>>> this system/cluster, or will you be sticking to Caos-2?
>>>
>>> Thanks,
>>> Greg
>>>
>>> On Jan 14, 2007, at 7:13 PM, Tim Leger wrote:
>>>
>>>
>>>
>>>> Hello,
>>>>
>>>> I've been using cAos 2.2.2b for about 6 month now on a 96 node
>>>> cluster. Great distribution, I've really come to like the
>>>> simplicity of
>>>> the cAos distribution over the Mandrake distros I used to use. I'm
>>>> now
>>>> trying to install cAos on a new set of machines which have ASUS
>>>> M2N-MX
>>>> motherboards. I've tried installing both the cAos 2.2.2b and newer
>>>> cAos
>>>> 3 beta 2 with no success because neither one can see the built-in
>>>> SATA
>>>> controller, which is an nVidia nForce430 chipset (more specifically
>>>> the
>>>> mcp61). When cinch comes up, it reports that it can't find any
>>>> drives. To get around this, I've temporarily borrowed a SATA
>>>> controller
>>>> card from another machine and was able to get cAos 3 beta 2
>>>> installed.
>>>> However, the SATA controller on the motherboard still doesn't work
>>>> after
>>>> installing cAos and I can't keep the borrowed controller card in
>>>> this
>>>> machine for long. When I plug the drive back into the onboard
>>>> controller port after installing cAos, it fails to boot completely
>>>> with
>>>> a kernel panic and the message that the SATA port link is down.
>>>> I've done some digging around on the web and supposedly this is a
>>>> know problem which was fixed in the 2.6.18 and above kernels. Is
>>>> there
>>>> a way to upgrade the current 2.6.17 cAos kernel to a 2.6.18+
>>>> kernel? I
>>>> also thought about just installing the latest nVidia drivers, but
>>>> nVidia's website states that the latest nForce motherboard
>>>> drivers are
>>>> distributed with the linux kernels. I'd appreciate any help you
>>>> could
>>>> give me on how to fix this problem.
>>>>
>>>> Regards, Tim Leger
>>>>
>>>> _______________________________________________
>>>> cAos-devel mailing list
>>>> cAos-devel at caoslinux.org
>>>> http://lists.caosity.org/mailman/listinfo/caos-devel
>>>>
>>>>
>>> --
>>> Greg Kurtzer
>>> email: gmkurtzer at gmail.com
>>> aim: gmkurtzer
>>> skype: gmkurtzer
>>> irc: gmk at irc.freenode.net
>>>
>>> I believe the world would be a better place if people didn't
>>> their believe their beliefs. -- gmk
>>>
>>>
>>> _______________________________________________
>>> cAos-devel mailing list
>>> cAos-devel at caoslinux.org
>>> http://lists.caosity.org/mailman/listinfo/caos-devel
>>>
>>>
>>>
>> _______________________________________________
>> cAos-devel mailing list
>> cAos-devel at caoslinux.org
>> http://lists.caosity.org/mailman/listinfo/caos-devel
>>
>
> --
> Greg Kurtzer
> email: gmkurtzer at gmail.com
> aim: gmkurtzer
> skype: gmkurtzer
> irc: gmk at irc.freenode.net
>
> I believe the world would be a better place if people didn't
> their believe their beliefs. -- gmk
>
>
> _______________________________________________
> cAos-devel mailing list
> cAos-devel at caoslinux.org
> http://lists.caosity.org/mailman/listinfo/caos-devel
>
>
More information about the cAos-devel
mailing list