Hardware is:
Pentium 3, 1.13 GHz
256 MB Ram
SCSI Adapter Adaptec 2940U2W
SCSI Adapter Adaptec 2910
SCSI Disk 18GB
SCSI Disk 4GB
SCSI CD-ROM
Network card: realtek 8139 (not supported, I'll install a driver after boot)
Video card: SiS 630
Here's a summary of what I did:
Boot from floppy with parameter "link=blad325" for 2940U2W or "link=blad"
for 2910
Start install from SCSI CD-ROM
Install system
Build new kernel
reboot
And then I get some strange error messages, like "PANIC", and about the
system being unable to dump on hd(41)...
I've just restarted installation, I'll post something more as soon as I get
the thing to boot.
If I boot from floppy, using root=hd(42), i can get the system to boot in
single user mode, but I get more strange errors like "can't open /dev/log"
or "itimer: not configured". If I press ^D for a normal boot, I get more
messages, the last one of them about getty being unable to open any
/dev/tty*...
Do you think I can solve these problems with a "normal" Adaptec 2940? Or the
controller doesn't matter, as long as I have the right drivers?
I noticed this is your second post on this with no response. So I'll add one.
Why 5.0.0? I'm sure someone will correct me if I'm wrong on this but I
think 5.0.0 came out about 5 years ago.
I would fully expect problems with 5.0.0 on any type of new hardware. At
least go with 5.0.5 or 5.0.6.
--------------------------------------------------------------
Ken Wolff
--------------------------------------------------------------
> I noticed this is your second post on this with no response. So I'll add
one.
>
> Why 5.0.0? I'm sure someone will correct me if I'm wrong on this but I
> think 5.0.0 came out about 5 years ago.
Because I only have 5.0.0 installation disks, and I need to setup a server
with that.
> I would fully expect problems with 5.0.0 on any type of new hardware. At
> least go with 5.0.5 or 5.0.6.
And how do I upgrade? How much does it cost? I think it would be out of our
budget.
Thank you.
Tried again with a "new" Adaptec 2940W, which should be supported.
Installation went OK, but here is the message I see at boot time:
PANIC: srmountfun - Error 22 mounting rootdev hd (1/42)
Trying to dump 49055 pages to dumpdev hd (1/41) at block 0, 614 pages per
'.'
0 pages dumped
** Safe to power off **
-or-
** Press any key to reboot **
So I think the controller is good. Should I try with an older PC? maybe
Pentium 3, or SDRAM, or whatever else is the real problem?
ron
"Gabriele Boccone" <gabr...@boccone.tk> wrote in message
news:b1u5p9$586$1...@newsreader.mailgate.org...
Thank you... It didnt help much, but I feel like I'm getting closer to the
real solution...
I could be wrong, but I don't think you can install 5.0.0 on a Pentium
3, Pentium 2 or less.
Abid
While you have the case open, remove the 2910 and run the cd on the
2940. Even if it would work and I doubt it would on 5.0.0, a 2910 has
no business in a server. At the same time, just about every one here
will tell you to take out the Realtek network card and mash it into tiny
bits, then buy a supported card.
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
> While you have the case open, remove the 2910 and run the cd on the
> 2940. Even if it would work and I doubt it would on 5.0.0, a 2910 has
> no business in a server. At the same time, just about every one here
> will tell you to take out the Realtek network card and mash it into tiny
> bits, then buy a supported card.
Ok, thank you. I think I should post more details...
I know that putting old software on new hardware is a Bad Thing (TM), but I
really need to do so. Our customer only has 5.0.0, and wants a new server
doing the same job as the older one. The first step is getting the thing to
boot, then we'll have some fun installing other programs.
About the case: yes, it's still open, if it has to be an "Open Server" :-)
:-) (Sorry, I couldn't resist)
About the 2910: I tried it only because the 2940U2W didn't work. They are
BOTH supported, with the drivers from Adaptec. I know a 2910 is a poor
controller (I think it doesn't even boot), but we are trying *everything*...
About the network card: I read the compatibility list and I thought it would
be very hard to find one of these cards nowadays. Better: I have some cards
which are supported, but my PC doesn't have any ISA slots to put them, only
PCI... :-( You think that this card can prevent the PC to boot?
> I could be wrong, but I don't think you can install 5.0.0 on a Pentium
> 3, Pentium 2 or less.
It seems you are right... but why? (In the meantime I'm trying with a
Pentium...)
Anyway here is a little update about the situation:
Install Ok, but pc doesn't boot from hd, then I start from the installation
floppy disk, and use the following boot string:
fd(64)unix root=hd(42) swap=hd(41)
The system boots, then says:
CONFIG: itimer (some error)
Unable to open /dev/log
And I get a single-user shell. If I press ^D, then boot process goes on, and
it stops when getty says "unable to open /dev/tty*".
if 2+2=4, the problem is in the kernel that is built after install... Here
is my guess (may be wrong...):
The kernel in the boot floppy doesn't have a driver for /dev/log, timer, and
/dev/tty*, to keep it small. It does, however, have a driver for the
controller and the hard disk, and some other things which are *very
important* for booting the machine. The kernel built on the hard disk after
install, instead, doesn't have some important driver, and can't boot.
And now... *tada.wav* the question:
how do I build a new kernel while I'm in single user mode?
Thank you very much...
> Anyway here is a little update about the situation:
>
> Install Ok, but pc doesn't boot from hd, then I start from the installation
Exactly what happens when you try to boot from the hard disk?
> floppy disk, and use the following boot string:
>
> fd(64)unix root=hd(42) swap=hd(41)
>
> The system boots, then says:
>
> CONFIG: itimer (some error)
> Unable to open /dev/log
>
> And I get a single-user shell. If I press ^D, then boot process goes on, and
> it stops when getty says "unable to open /dev/tty*".
>
> if 2+2=4, the problem is in the kernel that is built after install... Here
> is my guess (may be wrong...):
>
> The kernel in the boot floppy doesn't have a driver for /dev/log, timer, and
> /dev/tty*, to keep it small. It does, however, have a driver for the
> controller and the hard disk, and some other things which are *very
> important* for booting the machine. The kernel built on the hard disk after
> install, instead, doesn't have some important driver, and can't boot.
You seem to understand the situation very well.
> And now... *tada.wav* the question:
>
> how do I build a new kernel while I'm in single user mode?
Just to build a new kernel,
cd /etc/conf/cf.d
./link_unix
But... that won't help, because whatever's missing will still be
missing.
What's missing is _probably_ your host adapter driver. I don't know
which adapter you're using now -- you've mentioned 2910 and 2940U2W.
Those use different drivers (alad for 2910, blad for 2940U2W). I forget
whether alad was built into OSR500; I'm sure blad wasn't. So let me
guess that you need blad.
So, boot to single-user mode (your floppy technique will do). Put your
blad floppy in the drive. Mount it:
mount -r /dev/fd0 /mnt
Then run:
btldinstall /mnt
It will prompt you for which package to install; tell it "blad325" or
whatever the name is.
This _should_ have happened automatically as part of the install, but
maybe OSR500 didn't get that right.
_Then_ build a new kernel...
>Bela<
Well, the mashing part is optional, though satisfying.
--
Tony Lawrence
Free SCO, Mac OS X and Linux Skills Tests:
http://aplawrence.com/skillstest.html
> Exactly what happens when you try to boot from the hard disk?
Already posted in previous messages:
PANIC: srmountfun - Error 22 mounting rootdev hd (1/42)
another strange thing I've noticed 2 minutes ago:
%disk 0x01F0-0x01F7 14 - type=W0 unit=0 cyls=1024 hds=65535 secs=63
(looks like BIOS translation doesn't work)
then
%Sdsk - - - cyls=292 hds=255 secs=63 fts=sdb
> > And now... *tada.wav* the question:
> >
> > how do I build a new kernel while I'm in single user mode?
>
> Just to build a new kernel,
>
> cd /etc/conf/cf.d
> ./link_unix
already tried, *obviously enough* it didn't help
> What's missing is _probably_ your host adapter driver. I don't know
> which adapter you're using now -- you've mentioned 2910 and 2940U2W.
> Those use different drivers (alad for 2910, blad for 2940U2W). I forget
> whether alad was built into OSR500; I'm sure blad wasn't. So let me
> guess that you need blad.
2910 has been dumped, and 2940U2W followed. Now I'm going with a 2940W,
which is supported, and I see at boot time:
%adapter 0xDE00-0xDE00 11 - type=alad ha=0 id=7 fts=st
So the host adapter driver is there... already tried with terminators, and
without them, same thing.
> So, boot to single-user mode (your floppy technique will do). Put your
> blad floppy in the drive. Mount it:
>
> mount -r /dev/fd0 /mnt
>
> Then run:
>
> btldinstall /mnt
I was missing this part, I'm going to try this.
Thank you very much...
> > Exactly what happens when you try to boot from the hard disk?
>
> Already posted in previous messages:
>
> PANIC: srmountfun - Error 22 mounting rootdev hd (1/42)
>
> another strange thing I've noticed 2 minutes ago:
>
> %disk 0x01F0-0x01F7 14 - type=W0 unit=0 cyls=1024 hds=65535 secs=63
> (looks like BIOS translation doesn't work)
>
> then
> %Sdsk - - - cyls=292 hds=255 secs=63 fts=sdb
These messages show an IDE disk (of insane size, about 2 terabytes) and
a reasonable (~2GB) SCSI disk.
Do you have an IDE hard disk at all? If not, this is probably a big
part of the problem.
If you do have an IDE disk, is that what you're installing onto?
> > > And now... *tada.wav* the question:
> > >
> > > how do I build a new kernel while I'm in single user mode?
> >
> > Just to build a new kernel,
> >
> > cd /etc/conf/cf.d
> > ./link_unix
>
> already tried, *obviously enough* it didn't help
>
> > What's missing is _probably_ your host adapter driver. I don't know
> > which adapter you're using now -- you've mentioned 2910 and 2940U2W.
> > Those use different drivers (alad for 2910, blad for 2940U2W). I forget
> > whether alad was built into OSR500; I'm sure blad wasn't. So let me
> > guess that you need blad.
>
> 2910 has been dumped, and 2940U2W followed. Now I'm going with a 2940W,
> which is supported, and I see at boot time:
>
> %adapter 0xDE00-0xDE00 11 - type=alad ha=0 id=7 fts=st
>
> So the host adapter driver is there... already tried with terminators, and
> without them, same thing.
>
> > So, boot to single-user mode (your floppy technique will do). Put your
> > blad floppy in the drive. Mount it:
> >
> > mount -r /dev/fd0 /mnt
> >
> > Then run:
> >
> > btldinstall /mnt
>
> I was missing this part, I'm going to try this.
> Thank you very much...
Ok, but ... if the problem is due to seeing a ghost IDE drive, this
won't help. If you're using the 2940 (or 2910), you don't need a BTLD
since alad is built into OSR500; if you were still using the 2940U2W you
would need a BTLD, but I'm guessing it _did_ btldinstall itself
correctly during install. The resulting system wouldn't boot because of
this IDE problem, whatever it is.
You've been doing a bunch of installs, right? Start over with either
the 2940W or 2940U2W, whichever you would rather end up with. During
the very first boot to start installing, watch the hardware laundry list
carefully. If you see that "%disk 0x01F0-0x01F7 14 - type=W0 unit=0
cyls=1024 hds=65535 secs=63", stop immediately. Figure out how to get
past that before continuing.
Don't get hung up on BIOS translation, OpenServer won't necessarily use
the same geometry written on the disk or displayed in BIOS. What's most
important is that the value (cyls * hds * secs * 512) is approximately
equal to the real size of the disk.
Even before that, what's important is: do you actually have an IDE disk
in there? Do you intend to use it? Points to consider: it is very
difficult to convince OpenServer to boot from or install to a SCSI disk
when an IDE disk is present (it can be done, but it's tricky and the
exact nature of the tricks has changed from one release to the next).
Performance in a single-disk system will depend more on the fundamental
speed of the disk than the technology used to access it. Add a second
disk and SCSI will almost always win.
If you have an IDE disk and intend to use it: get the appropriate SLS
from ftp.sco.com (I forget which). OSR500's original IDE driver has
very small limits (I forget).
If you have an IDE disk and don't intend to use it: remove it, or at
least disable it in BIOS. You could also try booting the ISL media with
"defbootstr hd=Sdsk" (and maybe add "disable=wd"). I can't guess
whether that will work correctly with OSR500.
If you don't have an IDE disk, see if BIOS setup offers any hints as to
why OSR5 would see one. Or try "defbootstr disable=wd".
It is even possible that just by booting the OS that's already
installed, with "defbootstr disable=wd", you'll be able to boot.
> Already posted in previous messages:
Yes, but the only person who has all the information in their head is
you. And google. You can't expect people who are going out of their
way to help you to go even further out of their way to integrate all the
different messages every time they respond to a new one.
>Bela<
> These messages show an IDE disk (of insane size, about 2 terabytes) and
> a reasonable (~2GB) SCSI disk.
Ok. The SCSI disk is 4GB, but I think there is a size limit, and I'm going
to live with it.
The IDE disk is there, but I never thought OSR5 had IDE drivers and I always
ignored that... How stupid!
Yes, of course, you say IRQ 14 is the primary IDE channel, I should have
noticed before...
> If you do have an IDE disk, is that what you're installing onto?
Of course not, I didn't even know I could use it...
> You've been doing a bunch of installs, right? Start over with either
> the 2940W or 2940U2W, whichever you would rather end up with. During
> the very first boot to start installing, watch the hardware laundry list
> carefully. If you see that "%disk 0x01F0-0x01F7 14 - type=W0 unit=0
> cyls=1024 hds=65535 secs=63", stop immediately. Figure out how to get
> past that before continuing.
Ok, I'll disable IDE controller from the BIOS setup, and it should be
enough. I'll post some update on this subject.
> Yes, but the only person who has all the information in their head is
> you. And google. You can't expect people who are going out of their
> way to help you to go even further out of their way to integrate all the
> different messages every time they respond to a new one.
You are right, and everyone here has been very kind and helpful. :-)
I didn't expect so much help in this NG, I've had some bad experience
seeking for help in other NG's about other subjects...
Thank you, I'm a real beginner with OpenServer (I use Linux most of the
time, Solaris 8 and Unixware 7 sometimes...), I thought it was the same
thing as the other Unicses I knew... There's always a lot to learn...
>
> Thank you, I'm a real beginner with OpenServer (I use Linux most of the
> time, Solaris 8 and Unixware 7 sometimes...), I thought it was the same
> thing as the other Unicses I knew...
Nothing's the same. Every Unix is different, and some are more
different than others.
http://aplawrence.com/newtosco.html and
http://aplawrence.com/Linux/scolindiff.html might be of interest.
> "Bela Lubkin" <be...@caldera.com> ha scritto nel messaggio
> news:2003020702...@mammoth.ca.caldera.com...
>
> > These messages show an IDE disk (of insane size, about 2 terabytes) and
> > a reasonable (~2GB) SCSI disk.
>
> Ok. The SCSI disk is 4GB, but I think there is a size limit, and I'm going
> to live with it.
I'm not sure what the SCSI disk size limit was in OSR500, but definitely
larger than 4GB. I don't know why it only sees 2GB (maybe I
miscalculated?)
> The IDE disk is there, but I never thought OSR5 had IDE drivers and I always
> ignored that... How stupid!
> Yes, of course, you say IRQ 14 is the primary IDE channel, I should have
> noticed before...
>
> > If you do have an IDE disk, is that what you're installing onto?
>
> Of course not, I didn't even know I could use it...
But the install chooses which disk to use automatically -- you might
have been installing to the IDE disk without even knowing it.
> > You've been doing a bunch of installs, right? Start over with either
> > the 2940W or 2940U2W, whichever you would rather end up with. During
> > the very first boot to start installing, watch the hardware laundry list
> > carefully. If you see that "%disk 0x01F0-0x01F7 14 - type=W0 unit=0
> > cyls=1024 hds=65535 secs=63", stop immediately. Figure out how to get
> > past that before continuing.
>
> Ok, I'll disable IDE controller from the BIOS setup, and it should be
> enough. I'll post some update on this subject.
Try that, but keep a careful watch -- that doesn't always convince OSR5
that the drive isn't there. BIOSes vary widely in the technique used to
hide an IDE subsystem. If you still see any mention of "wd" or "IDE" in
the laundry list, go ahead and remove the drive. (Uncabling its power
connector should be enough.)
>Bela<
> I'm not sure what the SCSI disk size limit was in OSR500, but definitely
> larger than 4GB. I don't know why it only sees 2GB (maybe I
> miscalculated?)
The size limit IS 2GB, I don't know why, I've just upgraded to 5.0.4 (we
found a CD-ROM of this version, that one of our customers doesn't use
anymore), hope it helps... I'll post some news...
> But the install chooses which disk to use automatically -- you might
> have been installing to the IDE disk without even knowing it.
No, I'm sure about that. The IDE disk is for Linux and Windoze, and the
partition table is untouched.
> Try that, but keep a careful watch -- that doesn't always convince OSR5
> that the drive isn't there. BIOSes vary widely in the technique used to
> hide an IDE subsystem. If you still see any mention of "wd" or "IDE" in
> the laundry list, go ahead and remove the drive. (Uncabling its power
> connector should be enough.)
Thank you for the hints, luckily it DID work. I need that disk, because I'm
going to use linux on that PC too...
Then I can enable the controller again, if I put disable=wd in the
DEFBOOTSTR, right?
> > Try that, but keep a careful watch -- that doesn't always convince OSR5
> > that the drive isn't there. BIOSes vary widely in the technique used to
> > hide an IDE subsystem. If you still see any mention of "wd" or "IDE" in
> > the laundry list, go ahead and remove the drive. (Uncabling its power
> > connector should be enough.)
>
> Thank you for the hints, luckily it DID work. I need that disk, because I'm
> going to use linux on that PC too...
>
> Then I can enable the controller again, if I put disable=wd in the
> DEFBOOTSTR, right?
Hmmm. If you mean post-install, just make sure the "wd" driver isn't
linked into the kernel. But be aware that this will prevent you from
using ATAPI devices (your CD-ROM?). "disable=wd" would also prevent use
of ATAPI devices.
I _think_ you should be able to have an IDE controller enabled, and use
ATAPI devices, but still root off a SCSI hard drive: put "hd=Sdsk" in
DEFBOOTSTR.
>Bela<