Mailinglist Archive: opensuse (4749 mails)

< Previous Next >
WHY?
  • From: Curtis Rey <crrey@xxxxxxxxxxx>
  • Date: Wed, 7 May 2003 19:26:37 -0500
  • Message-id: <200305071926.43955.crrey@xxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, get my new 8.2 from CompUSA. Put it in the cdrom and reboot.

Now the fun part!

Choosing boot paramters

acpi=off ide=reverse ide=nodma reiserfs

Boots fine, right upto the point where ide2/hde on the promise pcd20276
onboard controller isnt' recognized stating thay neither ide port is enable
(bios) for the promise onboard controller --- HUH?

Now, what happened between 8.2 and 8.1 wherein the boot protocal cant cue to
the promise onboard controller.. I had this problem with 8.0 and thought the
issue was closed with 8.1.

Now I'm back to square one! I have tried safe mode with the added
ide=reverse. I have tried with apci on/off/ apm on/off/ etc.... eveything I
can think of, but 8.2 keeps insisting that the ports for ide aren't enabled
in the bios - WRONG!

I tried doing the update by changing the source installation in telinti 3 and
it reads and will let me install everything but base (great) and then returns
a big rpm-error on all the packages. I tried to use "install/remove
software" and it would let me install base - with a great big rpm error (no
doubt the diff in compiliers/gcc versions).

So now what. Even when it fails and I go back and look at the modules loaded
it, depending on what I do, will have the ataraid drivers (the one I need -
don't have raid setup) and/or the pdcraid drivers. But regardless of
whatever, doesn't see/recognize/init the pdc20276 onboard promis ultra 133
controller so no hdeX = no /use no /home/X.

Any suggestions? Beuhler,.... Ferris Beuhler?

My on retort is this can't be solve is to print out the fstab, swap on of my
cd drives for the maxtor drive (making hdc-->hde and vice verse, and then in
the partiioner in the installer manually assign the partitions and file
systems without formatting). I would rather solve this and have everything
functioning as it is now.

TIA, Curtis.

P.S. After this is solved (and I hope in manner that doesn't need extremes) I
will file a big bug report. This shouldn't be happening.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+uaRA7WVLiDrqeksRAjVhAJ9fU/iTIanMxvFcE4JbyUS2tGCQ/QCfVaEH
dMGJBYjr06bW3k0h3vT6DBk=
=Wg3t
-----END PGP SIGNATURE-----


< Previous Next >
Follow Ups