linux-kernel - Re: ide boot failure 2.6.36/2.6.28

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101120074508.GA16854@liondog.tnic>
Date:	Sat, 20 Nov 2010 08:45:08 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"Andries E. Brouwer" <Andries.Brouwer@....nl>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: ide boot failure 2.6.36/2.6.28 - 2.6.27 works

On Sat, Nov 20, 2010 at 04:28:33AM +0100, Andries E. Brouwer wrote:
> Answering myself (and providing info that can be Googled):
> 
> > I wanted to boot a recent kernel on an old machine and failed.
> > The last kernel that worked was 2.6.27.
> > What goes wrong is that the disks are no longer detected on 2.6.28.
> 
> A typical error would be
> 
> 	Cannot open root device 342 or unknown block (3,66)
> 
> Reading the code shows that the default probing is no longer done.

Well, this got changed in 20df429dd6671804999493baf2952f82582869fa since
we had other problems when having ide-generic and a specific PCI IDE
controller driver enabled at the same time, AFAIR.

There are two fixes I can think of - you either enable the specific IDE
controller driver for your chipset or you enforce probing with

	ide_generic.probe_mask=0x3f

on the kernel command line.

HTH.

-- 
Regards/Gruss,
    Boris.
--
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/