All of lore.kernel.org
 help / color / mirror / Atom feed
From: mshiju@in.ibm.com
To: Jeremy Jackson <jerj@coplanar.net>
Cc: linux-kernel@vger.kernel.org, linux-mca@vger.kernel.org
Subject: Re: Linux installation problem
Date: Wed, 7 Mar 2001 15:44:07 +0530	[thread overview]
Message-ID: <CA256A08.0039498E.00@d73mta05.au.ibm.com> (raw)


 CDROM is detected. On booting it gives the following messages
######################

Detected scsi CD-ROM sr0 at scsi0, channel 0, id 12, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12

#############################

The kernel message from the  virtual consol is as follows:

########################
trying to mount device scd0
loopfd is -1
LOP_SET_FD failed : Bad file descriptor

####################

Where am I gone wrong?

Thanks & Regards
Shiju



mshiju@in.ibm.com wrote:

> Hi all,
>            I am trying to install Linux (redhat-7) on a ps/2 server-9595
> machine (mca ). I am booting from a floppy disk and using a custom build
> 2.4.1 kernel image since there are problems  booting  the machine using
the
> installation image on  redhat CD and also it is not CD bootable. The
> problem is that after booting it asks for redhat CDROM and when I insert
> the redhat CDROM it gives a message "I could not find a redhat linux
CDROM
> in any of your CDROM drives ". The CD drive is a SCSI device and I have
> enabled SCSI cdrom in kernel compilation . Can any one help me .
>
> Thanks & Regards
> Shiju

Hi,

I have a type 8560 PS/2... not the same as yours but I did install
slackware
on
it once.

I would suggest installing from a standard PC.  Boot disks are very
inflexible,
since you don't have any utilities to poke around and figure out what's
going
on.

Once you have a complete root filesystem, once you've got a kernel to
recognise your scsi adapter, (and disk), you're off to the races, and can
use all kinds of tools to look into the CDROM problem...BUT

it's probably not going to recognise the disk either...

check different virtual consoles with alt-f1, f2, etc: under
a normal redhat boot disk, the different vc's will have diagnostic
messages, ie kernel messages, list of modules being loaded, etc.

maybe the best way is to be sure to compile kernel with support
for scsi subsystem *in kernel* - not module, along with
scsi-disk, scsi-cdrom, and your scsi host adapter.  the last
one may be the tricky one.  you will have to figure out if it is supported.
(the one in my PS/2 is at least for 2.0 kernel)

if you can make the kernel on the boot disk use a smaller font,
you will be able to see more of the messages at once.

also, shift-PgUp should let you scroll back some of the messages.
look for the kernel messages from your scsi host adapter driver...
if you don't see any there's a problem!

take a look inside your box and see what kind of scsi adapter it has.
or use your reference disk to see what it is.  post that here
so someone (maybe me) can check for kernel support.

Cheers,

Jeremy





             reply	other threads:[~2001-03-07 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 10:14 mshiju [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-06  9:19 Linux installation problem mshiju
2001-03-06 16:14 ` Jeremy Jackson
2001-03-06 16:33   ` David Weinehall
2001-03-06 16:50     ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA256A08.0039498E.00@d73mta05.au.ibm.com \
    --to=mshiju@in.ibm.com \
    --cc=jerj@coplanar.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mca@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.