On 9 Sep, Danilo Godec wrote:
> No, you don't. I always patch my kernels with ide, raid, usb and lately
> with i2c (in that particular order). I don't know about reiser, as it's
> still not ready for 64 bit architectures (Alpha) and also clashes with
> raid code (in some cases). I don't recall ever trying in any other
> order...
I might have been wrong about it being the raid code, but out of the
patches I applied to 2.2.16 (on x86), one of them would patch perfectly
clean if it was first, but barf many times if it wasn't.
> That "dangerous" package is not dangerous because of it's code, but
> because of it's features, that could be misused and lead to data loss.
Ah... trying to scare away the faint of heart, eh? :)
>> I also found that running lilo with my newly patched kernel resulted in
>> boots that hung at LI but booting with the CD and using the stock
>> kernel via a boot disk would install lilo just fine, and it boots the
>> new 2.2.16-RAID kernel without issues. Go figure.
>
> That's weird, but probably the two kernels disagree about the drive
> geometry. It would be nice if you could investigate just a bit more.
I am going to dig to try to find out more if I can.. and will, of
course, share what I find.
Considering I have to give lilo an append line of
"idebus=66 hda=5606,255,63 hdc=5606,255,63" to use more then 12Gig on
the large disks, you might be right about the geometry issue. When I
boot off the CD and run lilo, that kernel can't see the whole disks
(actually it can't see them at all since it can't see the controller
they're on, a Siig cmd649-based controller). The wierdest thing is, I
boot off of scsi disks, not the IDE ones.
--
Mike Marion - Unix SysAdmin/Engineer, Qualcomm Inc. - http://www.miguelito.org
The idea that Bill Gates has appeared like a knight in shining armour to
lead all customers out of a mire of technological chaos neatly ignores the
fact that it was he who, by peddling second-rate technology, led them into
it in the first place. - Douglas Adams in Guardian, 25-Aug-95
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
