linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: danieljzhang <danieljzhang@hotmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: [2.6.18,19] SATA boot problems (ICH6/ICH6W)
Date: Tue, 23 Jan 2007 13:49:38 -0800 (PST)	[thread overview]
Message-ID: <8550219.post@talk.nabble.com> (raw)
In-Reply-To: <200612111003.39928.kovid@theory.caltech.edu>


Need help to rebuild new kernel:
I dont know if this is the same problem. Please do help. 

I am trying to build kernel
linux-2.6.20-rc2

with patch
gregkh-all-2.6.20-rc2.patch

But system hanged when boot.

The original working kernel is: 2.6.13-15.13-smp. The distribution is SUSE.

According to YaST2, Disk is ST380013AS, Device Name is /dev/sda Driver is
ata_piix.

I used the original .config but add sata as module, usb as kernel build-in.

In /etc/sysconfig/kernel, I add ahci module. Right now INITRD_MODULES="ahci
piix ata_piix reiserfs processor thremal fan"

When booting, there is no FATAL error for loading module. I built in the USB
module as kernel. I still can get keyboard (USB keyboard). 

Then it shows:
"Waiting for device /dev/sda2 to appear: ........ resume device /dev/sda2
not found (ignoring)
Loading reiserfs
Waiting for device /dev/sda3 to appear: ..........not found -- exiting to
/bin/sh

I got shell promt "$" anyway. But just pwd cd works.

But I can not find solution after googling and bothering linux guy around.
Please help!

I was told that there is a new SATA driver that I need to build and load.
Anyone can kindly send me a link?

Help, please!
-- 
View this message in context: http://www.nabble.com/-2.6.18%2C19--SATA-boot-problems-%28ICH6-ICH6W%29-tf2795723.html#a8550219
Sent from the linux-ide mailing list archive at Nabble.com.


      parent reply	other threads:[~2007-01-23 22:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 18:03 [2.6.18,19] SATA boot problems (ICH6/ICH6W) Kovid Goyal
2006-12-20  0:44 ` Tejun Heo
2006-12-20  2:00   ` Kovid Goyal
2006-12-20  2:13     ` Tejun Heo
2006-12-20  4:56       ` Kovid Goyal
2007-01-11 23:32       ` Kovid Goyal
2007-01-13  2:19         ` Tejun Heo
2006-12-20  3:29   ` Gary Hade
2006-12-20  3:53     ` Tejun Heo
2006-12-20  4:30       ` Tejun Heo
2006-12-21 17:10       ` Gary Hade
2007-01-30  1:55         ` Gary Hade
2007-01-30  7:32           ` Tejun Heo
2007-01-30 23:37             ` Gary Hade
2007-01-31  0:54               ` Jeff Garzik
2007-01-31 11:00                 ` Tejun Heo
2007-01-31 12:20                   ` Alan
2007-01-31 13:16                     ` Tejun Heo
2007-01-31 15:24                       ` Jeff Garzik
2007-01-31 15:30                         ` Mark Lord
2007-01-31 10:44               ` Tejun Heo
2007-01-31 10:47                 ` Jeff Garzik
2007-01-31 11:00                   ` Tejun Heo
2007-02-01  0:49                 ` Gary Hade
2007-02-17  0:34               ` Gary Hade
2007-02-21 12:40                 ` Tejun Heo
2007-02-22  0:41                   ` Gary Hade
2007-02-23  0:32                   ` Gary Hade
2007-01-23 21:49 ` danieljzhang [this message]

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=8550219.post@talk.nabble.com \
    --to=danieljzhang@hotmail.com \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).