Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Peter Horton <phorton@bitbox.co.uk>
To: Stéphane <stf@c-gix.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Best kernel for a Cobalt Qube 2
Date: Thu, 29 Jan 2004 12:49:24 +0000	[thread overview]
Message-ID: <40190154.10601@bitbox.co.uk> (raw)
In-Reply-To: <4018EA65.40407@c-gix.com>

Stéphane wrote:

> I'm using a Cobalt Qube 2 for a long time now, it's under a 2.4.14 
> kernel working 24/24 7/7 without any problem (no weird hang, no tulip 
> problems, both internal network cards used).
>
> It's appears that the new libc needs at least a 2.4.19 kernel, this is 
> breaking all my debian updates. So I'll have to switch.
>
> Do you have any advice about which kernel to use  ?
>
> According to what I read here, 2.4.23 seems not ready and it's not 
> clear to me if newest kernels still have problem whith the 
> network/serial bug...


2.4.23 is running solid here, but it needs a couple of patches (one 
fixes a cache aliasing bug triggered by IDE in PIO mode, another fixes 
up Galileo so the network driver works without stalling). I'll mail the 
patches when I get home.

The major problem with running the later 2.4 kernels is that  Cobalt 
boot loader kernel size restriction means you have to cut the kernel 
configuration down to the very minimum to get it to fit, and this is 
only going to get worse with 2.6. I've written a new boot loader which 
lifts this restriction (and some others), but it's a week or two away 
from completion (disk booting is complete, I'm just finisihing off 
network booting).

P.

  reply	other threads:[~2004-01-29 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 11:11 Best kernel for a Cobalt Qube 2 Stéphane
2004-01-29 12:49 ` Peter Horton [this message]
2004-03-30 10:09   ` Dominique Quatravaux
2004-03-30 10:15     ` Peter Horton
2004-03-30 10:21       ` Kevin D. Kissell
2004-03-30 10:21         ` Kevin D. Kissell
2004-01-29 13:39 ` Brian Stratman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40190154.10601@bitbox.co.uk \
    --to=phorton@bitbox.co.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=stf@c-gix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox