linux-kernel - Re: 2.6.19-rt1 - failed to boot on AMD64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 1 Dec 2006 09:19:36 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mark Knecht <markknecht@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rt1 - failed to boot on AMD64


* Mark Knecht <markknecht@...il.com> wrote:

>   OK, so 2.6.19-rt1 starts booting, gets to the point where it see the 
> keyboard and mouse, and then apparently starts looking for a remote 
> NFS server? I don't remember seeing this on earlier kernels.

if you have a Fedora 5/6-ish setup then you might be better off by 
trying my yum rpm kernels, via:

   cd /etc/yum.repos.d
   wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo

   yum install kernel-rt.x86_64

by the looks of it something changed in the .config that prevented your 
block device from being detected - and after that the kernel fell back 
to other methods of booting.

another thing, is your /etc/fstab using labels, or explicit devices? 
IIRC labels are needed i think by the new SATA/PATA code, a'ka:

  LABEL=/                 /                       ext3    noatime,nodiratime 1 1

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/