From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HmWZs-0002Qq-3d for garchives@archives.gentoo.org; Fri, 11 May 2007 14:58:40 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4BEvNsh012738; Fri, 11 May 2007 14:57:23 GMT Received: from desiato.localdomain (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4BEqrK2007728 for ; Fri, 11 May 2007 14:52:53 GMT Received: from hactar.digimed.co.uk (hactar.digimed.co.uk [192.168.1.2]) by desiato.localdomain (Postfix) with ESMTP id 3A35C16EA for ; Fri, 11 May 2007 15:52:50 +0100 (BST) Date: Fri, 11 May 2007 15:52:46 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Panic at boot time after update kernel to 2.6.20-r8. Message-ID: <20070511155246.4a27f4d4@hactar.digimed.co.uk> In-Reply-To: <4644803D.6000005@ergolight-sw.com> References: <46444041.1040404@ergolight-sw.com> <200705111333.54395.alan@linuxholdings.co.za> <4644803D.6000005@ergolight-sw.com> Organization: Digital Media Production X-Mailer: Claws Mail 2.9.2cvs5 (GTK+ 2.10.12; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_Xq_FAYA5=ryii3NDTR8xPOx"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 46fe4b72-16ab-4b20-8f0f-14abb3fadb95 X-Archives-Hash: 8b8cb6ba20009aa95d8c8ea525ecfd59 --Sig_Xq_FAYA5=ryii3NDTR8xPOx Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 11 May 2007 17:39:57 +0300, David Harel wrote: > Upgrade is from 2.6.17-r8 >=20 > Attached the panic message: >=20 >=20 > VFS: cannot open root device sda1 or unknown block (0,0) >=20 > please append a correct "root=3D" boot option. >=20 > Kernel panic - not syncing: VFS: unable to mount root fs on unknown -=20 > block (0,0) You've been bitten by the same thing that hit most other SATA users. The SATA config options moved between 2.6.18 and 2.6.19 so your SATA chipset driver is no longer compiled in to the kernel. Do a make menuconfig, hit / and search for your SATA driver and enable it. --=20 Neil Bothwick If a parsley farmer is sued, can they garnish his wages? --Sig_Xq_FAYA5=ryii3NDTR8xPOx Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (GNU/Linux) iD8DBQFGRINCum4al0N1GQMRAgbCAKDNs+2WLPVkr8mX3NeDW1yRGp69ogCgoP8X 0Q4EOw8ZMIpcCWfNt/Nshcw= =BLtA -----END PGP SIGNATURE----- --Sig_Xq_FAYA5=ryii3NDTR8xPOx-- -- gentoo-user@gentoo.org mailing list