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: <200712152217.28865.alistair@devzero.co.uk>
Date:	Sat, 15 Dec 2007 22:17:28 +0000
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	Gene Heskett <gene.heskett@...il.com>
Cc:	Robert Hancock <hancockr@...w.ca>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: New question on that sata controller

On Saturday 15 December 2007 21:24:09 Gene Heskett wrote:
> On Saturday 15 December 2007, Robert Hancock wrote:
> >Gene Heskett wrote:
> >> Greetings;
> >>
> >> When I asked about a sata controller earlier this week, I gave a link to
> >> it. Unforch (maybe) when it actually arrived, the cards box showed a
> >> silicon image chip, and the card had a via.  So much for getting what I
> >> ordered...
> >>
> >> The required module then was sata_via, not sata_uli, and it seems to be
> >> working ok.  However, this one claims its a raid controller according to
> >> an lspci -v:
> >>
> >> 01:0a.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID
> >> Controller (rev 50)
> >>         Subsystem: VIA Technologies, Inc. VT6421 IDE RAID Controller
> >>         Flags: bus master, medium devsel, latency 32, IRQ 19
> >>         I/O ports at 9400 [size=16]
> >>         I/O ports at 9800 [size=16]
> >>         I/O ports at 9c00 [size=16]
> >>         I/O ports at a000 [size=16]
> >>         I/O ports at a400 [size=32]
> >>         I/O ports at a800 [size=256]
> >>         [virtual] Expansion ROM at e9000000 [disabled] [size=64K]
> >>         Capabilities: [e0] Power Management version 2
> >>
> >> I just noted that the Expansion ROM is disabled, but I didn't see any
> >> jumpers to enable it on the card prior to installing it.  Does anyone
> >> know how this is supposed to work?  I would like to make it directly
> >> bootable but I believe this has to be 'enabled' for that.
> >
> >It's usually normal for it to be disabled after boot, I believe. Are you
> >getting anything showing up on boot indicating its BIOS is active?
>
> No, not a thing.  Also invisible in the mainboards bios config AFAICT.

Normally this option is called "Enable Option ROM" or enable "INT 13/19h 
hook". See if you have such an option. It's surprising this isn't enabled by 
default.

However, the BIOS still might not support directly booting off the controller, 
I'm afraid.

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.
--
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