[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.6: Where'd my HD go?
well. this is a problem of 2.6 pciide driver just partially, on the other
hand it's your hardware's problem. some one correct me if i'm wrong.
> pciide0: channel 0 ignored (other hardware responding at addresses)
this string should answer all the questions "why". it says, that there's
another ide controller responding on the historic addresses (0x1f0/16,
14 irq, or 0x160(??) irq15). i had similar problem with my home box (486),
it has on-board pciide (with no DMA, though, like yours) and io multi card
in ISA slot (because it has not floppy/serials/parallel on-borad). yeah,
weird box :-) so 2.5 worked with no probs, and 2.6 complained from the
begining with messages like yours one. i needed to switch the io card
prtoperly. so, you should find the offending device and switch it off.
btw, your box is pentium based an it would be wonder if it had io multi
card in it (or is it has two on-boad ide controllers?). although i'd say
it isn't the case, because 2.6 on mine box, when failed to initialize
pciide, found "wdc? on isa0", and everything worked fine. on your box
it doesn't find wd0/acd0. may be pciide probe killed the drives for
later probe by old wdc...
why i said it may be openbsd's pciide driver problem? because, i don't
know why pciide written to use so called "compatibility mode":
> pciide0 at pci0 dev 1 function 0 "PC Technology RZ1000" rev 0x01: no DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
according to docs, this means that pciide code programs pciide controller
to opearte at the same hardware adresses, as old controllers did.
pci ide controllers can operate in another mode, although i had no
time/wish to understand, what this mode is and how it works. may be
it would better to use that mode, so it would be possible to "forget"
about "something responding at addresses"...
> WARNING: NVRAM century is 20 but RTC year is 2000
:-) hehe, what this is supposed to say? sounds very weird. 2000 year
*is* in 20th century in both means (in human -- 21th century begins
in 2000th year's end; and in computer -- century = year / 100).
btw, avoid booting generic 2.5 on i386, because it makes horrible
things to CMOS settings (but openbsd still works after that!).
i use it successfully at home, patched with my own simple patch related
to the problem (http://isl.vtu.lt/~cyxob/works/openbsd/clock.c.diff).
i used to save generic kernel in case some mysterious shit happens, so
i needed to rebuild 2.5 generic as well. the patch (or smth. similar)
shoul be available from openbsd's errata page...
Denis A. Doroshenko
Omnitel Ltd., Sevcenkos 25, Vilnius 2600, Lithuania