-----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-----
On Wednesday 07 May 2003 20:26, Curtis Rey wrote:
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? (snip) 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. ====================
Curtis, What we tell others to do, we forget to do ourselves, it seems. Check your manuals as I am sure there is mentiion of special things that might be needed with a Promise controller. Patrick -- --- KMail v1.5.1 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 06 May 2003 20:10, O'Smith wrote:
On Wednesday 07 May 2003 20:26, Curtis Rey wrote:
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?
(snip)
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.
====================
Curtis, What we tell others to do, we forget to do ourselves, it seems. Check your manuals as I am sure there is mentiion of special things that might be needed with a Promise controller.
Appernently, you have to tell the installation where it is because configs it differently than it would other wise inti from fstab, and is set to do this at the getgo, so reading fstab, e.g. /dev/hde1 means nothing to it now. boot option: ide=reverse ide2=0xe800,0xe802 ide3=0xe000,0xe002 hdeX=a,b+2 read form hwscan --storage_ctrl The upside to this install related to this issues is that the response so far appears to be much brisker. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+uNj87WVLiDrqeksRAo5LAJ97mlVlqN5w8O13zLI9/Qg3zrhJYACgkixS +7DMmtSoP15LJBDh6hJyTXQ= =PgYj -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 07 May 2003 06:24, David Krider wrote:
On Wed, 2003-05-07 at 04:59, Curtis Rey wrote:
boot option:
ide=reverse ide2=0xe800,0xe802 ide3=0xe000,0xe002
hdeX=a,b+2
read form hwscan --storage_ctrl
Holy cow. That's completely not obvious. Where did you find this answer?
Thanks, dk
It's in the sdb: "The Modules for Promise Controllers Cannot Be Loaded (07.06.2002)" Support knowledgebase (dstark_promise) Applies to SuSE Linux: Version 8.0 Symptom The modules for your Promise RAID controller cannot be loaded. Thus, the attached disks cannot be found. Cause The cause is still unknown. Solution Enter the necessary I/O addresses as boot parameters for ide2 and ide3. To calculate these addresses, start the rescue system and log in as 'root' user. Enter the command hwinfo --storage_ctrl The output section for the controller may be similar to: 27: PCI 20c.0: 0104 RAID bus controller [Created at pci.65] Unique ID: 6Ogo.XO4DClXBgC2 Hardware Class: storage Model: "Promise RAID bus controller" Vendor: 105a "Promise Technology, Inc." Device: 5275 "?" SubVendor: 105a "Promise Technology, Inc." SubDevice: 0275 "?" Revision: 0x01 I/O Ports: 0xa800-??? (rw) I/O Ports: 0xac00-??? (rw) I/O Ports: 0xb000-??? (rw) I/O Ports: 0xb400-??? (rw) I/O Ports: 0xb800-??? (rw) Memory Range: 0xee000000-??? (rw,non-prefetchable) IRQ: 10 (no events) Driver Info #0: Driver Status: ataraid,pdcraid are not active Driver Activation Cmd: "insmod ataraid; insmod pdcraid" Attached to: #15 (PCI bridge (Normal decode)) Write down the first 4 I/O ports (from now on known as A,B,C,D). Restart the installation and enter the following option at the boot prompt (remember you are working on a US keyboard layout now): ide2=A,B+2 ide3=C,D+2 A-D must be replaced with the values previously detected. According to our example, this option would read: ide2=0xa800,0xac02 ide3=0xb000,0xb402 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Now the trick is to adhere to this. My i/o's for the promise card are 0xe800-0xe8007 and 0xe000-0xe007, but entering these will a long sting of i/o errors when the disk is being initialized at boot - I know this from experience. So, following the formula "ide2=A,B+2 ide3=C,D+2". A word of note though. My I/O are not quite the same as this woud lead one to believe. Wherein the example sites A,B+2/C,D+2 that would mean (using the above example) 0xa800,0xac000+2 and 0xb000,0xb400+2. However if you look at the layout of my I/O's it's somewhat different. I/O ports at e800 [size=8] #translates to 0xe800 and A I/O ports at e400 [size=4] #translates to 0xe400 and B I/O ports at e000 [size=8] and C I/O ports at dc00 [size=4] and D I/O ports at d800 [size=16] and is most likely the ide mobo interface itself So I know the previous working i/o's "0xe800-0xe8007 and 0xe000-0xe007" and these represent ide2 and ide2 respectively (the others [e400, dc00] are might be slave ports - I'm guessing). So using the A,B+2 model would be 0xe800,0xe402 and 0xe000,0xdc02. I didn't do this but instead knew what the previous functioning i/o's were so I followed that (well, like is said - putting it in exactly didn't quite work with 0xe8007). Now the question is would 0xe800,0xe402 and 0xe000,0xdc02 have worked? I don't know. It may become evident if I try to add a device to the slave ports (e.g. 0xe402 and 0xdc02?), I don't know - my case doesn't have room to mount another hdd/disc read-writer-dvd, But I have another case that can and will be swaping this sys to that case and then attempt to add anothe device. :) If indeed 0xe402 and 0xdc02 do represent the slave ports then I'll post an update to this. HTH, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+uUy+7WVLiDrqeksRAtXLAJ0V4A891h1C0OI2wOkINY+tmhyL4ACeKyRN ettzK++JghSrccs3LKM0PL8= =3LNH -----END PGP SIGNATURE-----
participants (3)
-
Curtis Rey
-
David Krider
-
O'Smith