This time "Alexander Rayborn" <[EMAIL PROTECTED]> 
becomes daring and writes:

> Vox...
>
> I reported it as bug 1801 a few weeks ago.  Several attempts at fixes
> have been made, but as of RC2 it's still broke.  Badly.
>
> MDK 9.0 was really weird.  It would boot off the CD, then when it
> detected the IDE controllers, it would suddenly lose the CD-ROM drives
> completely and decide that they didn't exist.  I could no longer
> continue the install unless I did it over the network or whatever.
> That's still kinda useless though, since no CD-ROM drives would work in
> 9.0 even after you booted into it.
>
> 9.1 just plain doesn't see any hard drives and gives up in the install
> before I get anywhere.

  (Un)Fortunately, the box I'm using just got the HDs of my old
  desktop transfered to it (it's a cooker box, been on cooker
  since...7.2 I think :) and 2.4.19 booted nicely...but then I tried
  to use draksound to configure the soundcard integrated in this
  thing, and it wanted to use a module that doesn't exist in
  2.4.19-16mdk, so I got the current .21 and...it didn't want to boot
  :/ I really hope Pixel or somebody finds the fix for this, otherwise
  I won't be able to test any new kernels on cooker for a while :/

  On the other hand...I haven't lost my CD/burner (it's on one of the
  non-PCD controllers) with 2.4.19-16mdk, so...we need to raid the RH
  kernel to see how they fixed this problem.

  Vox

-- 
Think of the Linux community as a niche economy isolated by its beliefs.  Kind
of like the Amish, except that our religion requires us to use _higher_
technology than everyone else.       -- Donald B. Marti Jr.

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to