Hello, On Sun, 23 Aug 2009, Basil Chupin wrote: [..]
This situation has never happened to me with any make of HD. Is there something in the latest HDs which cannot be handled by the BIOS which, in my case, is some 5 years old? Or is it that the latest kernels are not capable of handling older BIOSes?
Can't imagine that 2.6.x can't handle that. Considering how much old HW is still supported by them. Or at least by Alsa. If I'm not mistaken, the support for ancient SB or Adlib and other Cards, even my "exotic" Mozart/mad16 card with an OTI Chip is still there ;) (BTW: I love that about Linux! Running a recent kernel, possibly slimlined, on "ancient" hardware is fun!). I used # dmidecode [..] Handle 0x0000 DMI type 0, 19 bytes. BIOS Information Block Vendor: Award Software International, Inc. Version: 6.0 PG Release: 11/17/99 [..] with various kernels starting from the extra 'athlon' image SuSE then provided, a 2.2.10 (with the correct MTRR setting, not applying the bugfix that was then needed for Pentiums), up to the currently running 2.4.37.5. Haven't got round to testing a 2.6 yet, as I was missing a bunch of dependencies. But I think I have them now for different reasons, so I might try again with a 2.6 ;) I'm using disks over 128GB since early 2004, and if I interpret my old lilo.conf correctly, starting with a 2.4.16 kernel. Oh, and this is all on the same install (originally a SuSE 6.2): $ rpm -qa --last | tail -n 1 bc-1.04-74 Mon 16 Aug 1999 07:19:26 *scnr* -dnh -- Microsoft is a cross between The Borg and the Ferengi. Unfortunately they use Borg to do their marketing and Ferengi to do their programming. [Simon Slavin] -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org