public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raymond Lewis Rebbeck <dystopianray@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What about kernel 2.6.19 ?
Date: Sun, 18 Feb 2007 06:29:07 +1030	[thread overview]
Message-ID: <200702180629.07227.dystopianray@gmail.com> (raw)
In-Reply-To: <17879.23625.634747.202001@ccs.covici.com>

On Sunday, 18 February 2007 6:19, John covici wrote:
> on Sunday 02/18/2007 Raymond Lewis Rebbeck(dystopianray@gmail.com) wrote
>
>  > On Sunday, 18 February 2007 5:41, Dan Farrell wrote:
>  > > On Sun, 18 Feb 2007 05:31:21 +1030
>  > >
>  > > Raymond Lewis Rebbeck <dystopianray@gmail.com> wrote:
>  > > > On Sunday, 18 February 2007 5:25, alain.didierjean@free.fr wrote:
>  > > > > Just compiled kernel 2.6.19-r5, with same config as 2.6.18-r6.
>  > > > > When trying to boot it, I get a kernel panic, grub not finding
>  > > > > (hd0,0), when booting 2.6.18 doesn't cause any problem. What's new
>  > > > > in 2.6.19 that causes this? What's the solution ? Help welcome.
>  > > > >
>  > > > > --
>  > > > > ~adj~
>  > > >
>  > > > It's probably due to the SATA drivers being moved out of the SCSI
>  > > > section of menuconfig, which iirc, changed their CONFIG names.
>  > > >
>  > > > You should double check that all your required drivers have been
>  > > > configured.
>  > >
>  > > I tried kernel 2.19 and the new libata PATA drivers and all seemed to
>  > > work fine, execpt I too got the same kernel panic with not
>  > > finding /dev/hd[a-z][0-9]+.  I think the names of these device nodes
>  > > might have changed?  I'm not sure but my theory is that if i would
>  > > have used the older ATA drivers instead, things would have been fine.
>  > >
>  > > People _Are_ running the 2.6.19 kernels successfully.
>  >
>  > The new libata PATA drivers put your hdds under /dev/sd* and your cdroms
>  > under /dev/sr* rather than /dev/hd*. So you'll have to either
>  > reconfigure your kernel to use the regular IDE drivers or fix all
>  > mention of /dev/hd* to the correct /dev/sd* device.
>
> Well, if I do that will I have to have only 15 partitions on an ide
> drive -- currently I am running on a drive with 17 partitions?  Which
> configs are the old ide drivers and are they going to be maintained?

I've never heard of any 15 partition limit. The old ide drivers are the 
CONFIG_IDE drivers that you'd have been using previously. They are likely to 
be maintained for the forseeable future. The libata PATA drivers are 
considered experimental and do not yet implement all the functionality and 
device support of the existing ide drivers.

-- 
Raymond Lewis Rebbeck
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-02-17 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 18:55 [gentoo-user] What about kernel 2.6.19 ? alain.didierjean
2007-02-17 18:58 ` Peter Lewis
2007-02-19  9:25   ` [gentoo-user] What about kernel 2.6.19 ? (Solved) alain.didierjean
2007-02-17 19:01 ` [gentoo-user] What about kernel 2.6.19 ? Raymond Lewis Rebbeck
2007-02-17 19:11   ` Dan Farrell
2007-02-17 19:23     ` Raymond Lewis Rebbeck
2007-02-17 19:49       ` John covici
2007-02-17 19:59         ` Raymond Lewis Rebbeck [this message]
2007-02-17 20:04           ` Raymond Lewis Rebbeck

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=200702180629.07227.dystopianray@gmail.com \
    --to=dystopianray@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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