Mailinglist Archive: opensuse (3513 mails)
| < Previous | Next > |
Re: [SLE] Still having problems with SCSI CD's not being seen by SuSE Linux
- From: JR <jruhsam@xxxxxxxxxx>
- Date: Fri, 2 Mar 2001 17:13:47 -0700
- Message-id: <01030217134700.00987@linux>
Hello.
Sorry about that but I had a headache and was on the run for work and was not thinking very straight. Thank you for pointing that out to me. :-)
Here is the information that was passed on by SuSE to me that did work for me.
***************************************
It seems that the SCSI driver was not integrated correctly into the system.
The SCSI adapter in Your system uses the the driver
aic7xxx.o
You find the following article about that in our support
database http://sdb.suse.de/en/ with the keyword "scsi".
Title: How to integrate a SCSI adapter
http://support.suse.de/en/sdb/html/scsiadd.html
_______________________________________________________
Request:
You have got a running system that boots over IDE. You want
to add a SCSI controller to get access to a harddisk or a
scanner. Please find out first whether your controller is
supported. Therefore you may search in our SuSE Support
Data Base.
Procedure:
Find out the exact type of SCSI controller. Under
/usr/src/linux/drivers/scsi you'll find the documentation
(e.g. README.aic7xxx for Adaptec controllers) and the
sources for different drivers for SCSI controllers.
Then try to load the driver with the command modprobe.
Example (for Adaptec controller):
modprobe aic7xxx
If this was successful you can check with the command
dmesg
There should be a message which says that the driver was
successfully loaded. With
cat /proc/scsi
you can see all recognized devices attached to the
controller.
If this is succesful please put the command
modprobe aic7xxx
into the file /etc/init.d/boot.local
so that the driver will loaded at booting.
*****************************
On Friday 02 March 2001 16:51, Jerry Kreps wrote:
> Share your experience!!
> What was it that yoy had to do?
> (Remember, were were all newbies once, and fresh newbies may be lurking!)
> JLK
>
>
>
> On Friday 02 March 2001 07:50, JR wrote:
> > Hello.
> >
> > I had tried changing the kernal but that caused even more problems.
> > I just received a reply to my support ticket with SuSE and they
> > walked me through what needed to be done to check and get the
> > modprobe to work. I now have working SCSI. :-)
> >
> > Thank you for your reply,
> > James Ruhsam
> >
> > On Friday 02 March 2001 05:31, you wrote:
> > > Did you configure your kernel with the scsi in it or as a module?
> > > If as a module did you modprobe scsi to load it?
> > > JLK
> > >
> > > n Thursday 01 March 2001 18:17, JR wrote:
> > > > Hello.
> > > >
> > > > I have just tried the 2.2 kernal a couple of times with no
> > > > luck, I still have no SCSI CD-RW or DVD drive.
> > > >
> > > > /proc/scsi/scsi contains 'Attached devices: none' and nothing
> > > > else.
> > > >
> > > > I am still fairly new to Linux and am at a loss as to where to
> > > > look, or what to do next.
> > > >
> > > > Thank you,
> > > > James Ruhsam
> > > >
> > > > On Sunday 25 February 2001 20:47, you wrote:
> > > > > On Fri, Feb 23, JR wrote:
> > > > > > I sure hope that someone can help me with this problem. I
> > > > > > just installed SuSE 7.1 on my computer with my SCSI DVD
> > > > > > drive. Now every time I boot into Linux and look for my
> > > > > > SCSI CD's, one SCSI DVD and one SCSI CD-RW, I get this
> > > > > > mesage in the information area, 'Attached devices: none'.
> > > > > > I have a standard Adaptec SCSI PCI card and the drives
> > > > > > mentioned above. I can not locate anything in the manual
> > > > > > to assist me in corecting this problem. The SCSI is
> > > > > > terminated and the CD drives are different numbers. As I
> > > > > > said before, I used the SCSI DVD to install SuSE 7.1 with
> > > > > > just over 20 hours ago. The Kernal I am using is the 2.4.
> > > > > > I tried to rebuild the Kernal with the SCSI but the kernal
> > > > > > failed to boot each time I tried, no mater how I tried to
> > > > > > set it up.
> > > > >
> > > > > What does /proc/scsi/scsi contain? Did you try it with the
> > > > > 2.2 kernel as well?
> > > > >
> > > > > Bye,
> > > > > LenZ
> > >
> > > --
> > > To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
> > > For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> > > Also check the FAQ at http://www.suse.com/support/faq
>
>
Sorry about that but I had a headache and was on the run for work and was not thinking very straight. Thank you for pointing that out to me. :-)
Here is the information that was passed on by SuSE to me that did work for me.
***************************************
It seems that the SCSI driver was not integrated correctly into the system.
The SCSI adapter in Your system uses the the driver
aic7xxx.o
You find the following article about that in our support
database http://sdb.suse.de/en/ with the keyword "scsi".
Title: How to integrate a SCSI adapter
http://support.suse.de/en/sdb/html/scsiadd.html
_______________________________________________________
Request:
You have got a running system that boots over IDE. You want
to add a SCSI controller to get access to a harddisk or a
scanner. Please find out first whether your controller is
supported. Therefore you may search in our SuSE Support
Data Base.
Procedure:
Find out the exact type of SCSI controller. Under
/usr/src/linux/drivers/scsi you'll find the documentation
(e.g. README.aic7xxx for Adaptec controllers) and the
sources for different drivers for SCSI controllers.
Then try to load the driver with the command modprobe.
Example (for Adaptec controller):
modprobe aic7xxx
If this was successful you can check with the command
dmesg
There should be a message which says that the driver was
successfully loaded. With
cat /proc/scsi
you can see all recognized devices attached to the
controller.
If this is succesful please put the command
modprobe aic7xxx
into the file /etc/init.d/boot.local
so that the driver will loaded at booting.
*****************************
On Friday 02 March 2001 16:51, Jerry Kreps wrote:
> Share your experience!!
> What was it that yoy had to do?
> (Remember, were were all newbies once, and fresh newbies may be lurking!)
> JLK
>
>
>
> On Friday 02 March 2001 07:50, JR wrote:
> > Hello.
> >
> > I had tried changing the kernal but that caused even more problems.
> > I just received a reply to my support ticket with SuSE and they
> > walked me through what needed to be done to check and get the
> > modprobe to work. I now have working SCSI. :-)
> >
> > Thank you for your reply,
> > James Ruhsam
> >
> > On Friday 02 March 2001 05:31, you wrote:
> > > Did you configure your kernel with the scsi in it or as a module?
> > > If as a module did you modprobe scsi to load it?
> > > JLK
> > >
> > > n Thursday 01 March 2001 18:17, JR wrote:
> > > > Hello.
> > > >
> > > > I have just tried the 2.2 kernal a couple of times with no
> > > > luck, I still have no SCSI CD-RW or DVD drive.
> > > >
> > > > /proc/scsi/scsi contains 'Attached devices: none' and nothing
> > > > else.
> > > >
> > > > I am still fairly new to Linux and am at a loss as to where to
> > > > look, or what to do next.
> > > >
> > > > Thank you,
> > > > James Ruhsam
> > > >
> > > > On Sunday 25 February 2001 20:47, you wrote:
> > > > > On Fri, Feb 23, JR wrote:
> > > > > > I sure hope that someone can help me with this problem. I
> > > > > > just installed SuSE 7.1 on my computer with my SCSI DVD
> > > > > > drive. Now every time I boot into Linux and look for my
> > > > > > SCSI CD's, one SCSI DVD and one SCSI CD-RW, I get this
> > > > > > mesage in the information area, 'Attached devices: none'.
> > > > > > I have a standard Adaptec SCSI PCI card and the drives
> > > > > > mentioned above. I can not locate anything in the manual
> > > > > > to assist me in corecting this problem. The SCSI is
> > > > > > terminated and the CD drives are different numbers. As I
> > > > > > said before, I used the SCSI DVD to install SuSE 7.1 with
> > > > > > just over 20 hours ago. The Kernal I am using is the 2.4.
> > > > > > I tried to rebuild the Kernal with the SCSI but the kernal
> > > > > > failed to boot each time I tried, no mater how I tried to
> > > > > > set it up.
> > > > >
> > > > > What does /proc/scsi/scsi contain? Did you try it with the
> > > > > 2.2 kernel as well?
> > > > >
> > > > > Bye,
> > > > > LenZ
> > >
> > > --
> > > To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
> > > For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> > > Also check the FAQ at http://www.suse.com/support/faq
>
>
| < Previous | Next > |