public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Márcio Oliveira" <moliveira@rhla.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Panic + Intel SATA
Date: Thu, 27 Oct 2005 15:56:16 -0200	[thread overview]
Message-ID: <436114C0.4000701@rhla.com> (raw)
In-Reply-To: <1130430478.17679.0.camel@localhost>

Alan Cox wrote:

>>>If you are using LVM2 or MD you just need to be sure you have the right
>>>config options enabled (the Red Hat src.rpm is a good guide).
>>>
>>>Alan
>>> 
>>>
>>>      
>>>
>>I'm not using lvm or raid in the /root or the /boot partition. All 
>>partitions was made directly in the disk and formated with ext3 file 
>>system. I think all needed options was compiled in the new kernel, since 
>>I copied the /boot/config-2.6.12-1.1456_FC4 (config file from the kernel 
>>that works fine) and compiled the kernel.src.rpm without any 
>>modifications in the config file, and it still not working.
>>    
>>
>
>You also created a new initrd with mkinitrd ?
>  
>
Yes, I created it. I also extracted the initrd image and compared it 
with a initrd that works fine (the initrd-2.6.12-1.1456_FC4.img initrd 
image provided by the kernel-2.6.12-1.1456_FC4.i386.rpm kernel package) 
and the images have the same files.

I got the mkinitrd-5.0.8-1 package and the 
kernel-devel-2.6.12-1.1456_FC4.i686.rpm package too. I compiled the 
mkinitrd package with the command:

# rpmbuild --rebuild mkinitrd-5.0.8-1.src.rpm
# rpm -ivh /usr/src/redhat/RPMS/i386/mkinitrd-5.0.8-1.i386.rpm

I also changed parameters in the kernel.spec file and recompiled it. The 
parameters was changed from:

%define buildsmp 1
...
%patch800 -p1

To:

%define buildsmp 0
...
# %patch800 -p1

(the nonint patch was generating error messages during the kernel rpm 
compilation)

# rpmbuild --target i686 -ba /usr/src/redhat/SPECS/kernel.spec
# rpm -ivh /usr/src/redhat/RPMS/i686/kernel-2.6.12.ext3-2.i686.rpm

After I finished the process, I booted the machine and got the same 
error message. I also rebuilt the initrd image and built a new 2.6.13 
fedora core src.rpm kernel, but it still not working... any more idea??

Thank you.

Márcio.

  reply	other threads:[~2005-10-27 17:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 18:18 Kernel Panic + Intel SATA Márcio Oliveira
2005-10-26 19:29 ` linux-os (Dick Johnson)
     [not found]   ` <4360261E.4010202@rhla.com>
2005-10-27  1:01     ` Marcio Oliveira
2005-10-27 12:49       ` linux-os (Dick Johnson)
2005-10-27 13:34         ` Alan Cox
2005-10-27 14:20           ` Márcio Oliveira
2005-10-27 16:27             ` Alan Cox
2005-10-27 17:56               ` Márcio Oliveira [this message]
2005-10-27 14:28         ` Márcio Oliveira
2005-10-27 15:21           ` linux-os (Dick Johnson)
2005-10-26 19:31 ` Jeff Garzik
2005-10-27  0:42   ` Marcio Oliveira
2005-10-27  0:59     ` Marcio Oliveira

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=436114C0.4000701@rhla.com \
    --to=moliveira@rhla.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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