Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
im having trouble when i try to install solaris 10 on a piii machine,
when i get to the install, it asks what kind of install i want to use, (ive tried 1, 3 and 4, cos i dont have any idea what 2 is), then it gets to the bit about use being subject to license terms, where it hangs for about 2 to 10 minutes. then it says:
using RPC Bootparams for network configuration information.
then it repeats the previous set of errors again, it just goes round and round.
i think the problem may be with my bios, i googled a bit, and found one person with a similar problem on solaris 9, and that was because his bios had ultraDMA enabled on hard disks that didnt support it, so i checked mine, but it was disabled.
my system is a piii 450mhz
with 2 20gb hdd
an unmarked cd rw
an asus p2b motherboard
an ati rage ? graphics card
i tried several things, sometimes i got further than others, but in the end i gave up, took the system apart, and rebuilt it, noticing that the pii was not a 350mhz one like i thought, but was in fact 600mhz, so i built the system again, and changed the bios it seems to be working now, now i just have to find out what graphics card i put in it!
i have one box with a working solaris system, (which i would like to leave working), which has 3 hdd,
i have another box, which is not working, but i will hopefully have solaris on it soon, it has 2 hdd
i have had windows xp installed on the second system, and it was working fine, but when i try to install solaris, i keep getting this error, or a varient of,
i have come to think that this might be a problem with one of the hdd's in the system, since i rebuilt the system, and switched the drives around, therefore the one that was primary master became secondary master, and so on, the installer was then able to get to actually writing the partitions to disk before it produced the error. does this mean that the disk is suspect?
i would like to take out the 3rd disk in the other system, and replace the one of the disks on the second system, so i can see if it will work without the secondary hdd,
so basically what im asking is, if anyone has any info on the above error, then please let me know, and how do you remove a hdd from a system, without the system complaining about it.
what a pain in the butt to get registered here to try and help. I stumbled on your question via googling and I think I have your answer for you. Not 100% but worth a try. set the "pciide" boot environment variable in /boot/solaris/bootenv.rc to 'false'
Hi, do you have any URL that have step by step installation for solaris 10 ? Thanks
Regards
Daniel
Quote:
Originally posted by SolarCurve what a pain in the butt to get registered here to try and help. I stumbled on your question via googling and I think I have your answer for you. Not 100% but worth a try. set the "pciide" boot environment variable in /boot/solaris/bootenv.rc to 'false'
I'm getting the same problem on a dual P3. Installs fine, but fails to boot.
Safe mode boots, normal mode does not.
I tried removing /kernel/drv/ucode, because other folks have reported that removing "/platform/i86pc/ucode" works. (It seems ucode is in a different location in later builds).
I also tried the other suggestion that seems to work for some folks: that is, I pass the "-B $ZFS=BOOTFS,ata-dma-enabled=0" parameter to the kernel via GRUB, but that also fails.
Along the lines of this thread, I've also tried booting with the variables: "-B $ZFS=BOOTFS,ata-dma-enabled=0,pciide=0", and that did not work either.
I have tried both OpenSolaris 2008.05 rc2a and also Nexenta 1.0 rc5-b82 x86, and they both report the same problems as soon as the kernel tries to read the hard drive. It's interesting that the opensolaris live CD and the Nexenta install CD are both able to access the hard drive well enough to install everything. Yet the kernel on the hard drive fails.
I'm using the onboard IDE controller, and the board is a Supermicro Super P6DBE, spec'd to have "2 EIDE Bus Master interfaces support Ultra DMA/33 and Mode 4". (PDF manual => http://www.supermicro.com/manuals/mo...X/MNL-0612.pdf )
BTW, linux kernels work fine on this box.
[edit] I also tried installing a third party controller (Promise tx2-100 or something like that). Both opensolaris and nexenta failed to see the drive.
Problem solved in this thread. However, solving the hdd problem introduced a new problem - I can only use one CPU now.
The original problem turned out being that interrupts for hdd requests were going to the CPU that has interrupts disabled. How do I redirect interrupt requests to the correct CPU, so I can have both CPUs running?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.