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: <45A42385.7090904@garzik.org>
Date:	Tue, 09 Jan 2007 18:21:41 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	"Jeff V. Merkey" <jmerkey@...fmountaingroup.com>
CC:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash
 IDE chip under 2.6.18

Jeff V. Merkey wrote:
> 
> I just finished pulling out a melted IDE flash drive out of a Shuttle 
> motherboard with the intel 945 chipset which claims to support
> SATA and IDE drives concurrently under Linux 2.6.18.
> 
> The chip worked for about 30 seconds before liquifying in the chassis.  
> I note that the 945 chipset in the shuttle PC had some serious
> issues recognizing 2 x SATA devices and a IDE device concurrently.   Are 
> there known problems with the Linux drivers
> with these newer chipsets.
> 
> One other disturbing issue was the IDE flash drive was configured (and 
> recognized) as /dev/hda during bootup, but when
> it got to the root mountint, even with root=/dev/hda set, it still kept 
> thinking the drive was at scsi (ATA) device (08,13)
> and kept crashing with VFS cannot find root FS errors.

We have two sets of ATA drivers now, and Intel motherboards support 
bazillion annoying IDE modes, so you will need to provide more info than 
this.

Is the motherboard in combined mode?  native mode?  AHCI or RAID mode?
What driver set did you pick?  is drivers/ide built in, modular, or 
disabled?  is drivers/ata built in, modular, or disabled?

The cannot-find-root-FS errors are definitely caused by driver and/or 
initrd misconfiguration.  The melted flash, I dunno, maybe you managed 
to get two drivers fighting over the same hardware.

	Jeff



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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ