linux-kernel - Re: No IDE drivers loaded for Toshiba Satellite 320 CDS

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: <48017248.4030600@gmail.com>
Date:	Sun, 13 Apr 2008 11:39:04 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Frans Pop <elendil@...net.nl>
CC:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Subject: Re: No IDE drivers loaded for Toshiba Satellite 320 CDS

Frans Pop wrote:
> On Wednesday 02 April 2008, Lennart Sorensen wrote:
>>> Yes, that could be one way to implement it: load it and then check if
>>> that added any devices.
>> Well even if you see other disks doesn't mean you don't also have an old
>> IDE controller you want to use, so probably load it and see if it finds
>> any disks is the best bet after loading all the other probeable drivers
>> first.
> 
> I've decided (at least for now) to only do this f /sys/bus/isa is present.
> I added a check to see if there are additional devices in /sys/block after 
> loading ide-generic to decide whether or not to also include it in the 
> initrd for the installed system.
> 
> /sys/bus/isa is present for this machine so it works even if (as Ondrej 
> suggests) the controller is not actually on the ISA bus. We can always 
> extend the test if it turns out systems without ISA bus are also affected.
> 
> I'll also send out a call for testing specifically for this issue.
> 
> Thanks to you and Ondrej for the discussion.

Please be advised that some modern controllers are dual interfaced. 
Native one and legacy one.  The legacy one is SFF compliant and 
depending on configuration may appear at legacy IO addresses, so if you 
aren't careful, you can end up with two drivers driving the same 
hardware which usually doesn't end too well.  Loading generic drivers 
w/o knowing that it's needed is quite dangerous.  I would strongly 
advise against it.

-- 
tejun
--
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/