On Mon, Sep 01, 2003 at 09:12:07PM +1000, Russell Shaw wrote:
> Kirk Strauser wrote:
> >I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic
> >SCSI CDROM. I've followed various instructions culled from mailing lists,
> >HOWTOs, etc.
At 2003-09-01T17:01:05Z, Greg Folkert <[EMAIL PROTECTED]> writes:
> Then you have put in your SCSI Controller's module in /etc/modules as well
> as sr_mod and any other modules needed.
I am a complete toolshed. I actually realized that I hadn't loaded my SCSI
adapter module about 2 minutes after
On Sun, 2003-08-31 at 13:09, Kirk Strauser wrote:
> I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic
> SCSI CDROM. I've followed various instructions culled from mailing lists,
> HOWTOs, etc., but I'm still having problems with getting the
Kirk Strauser wrote:
At 2003-09-01T11:12:07Z, Russell Shaw <[EMAIL PROTECTED]> writes:
The real scsi will appear under sdxx such as sda1.
Except that it doesn't. In fact, it's not even detected in dmesg.
What I've done so far:
1) Added this to my grub boot parameters:
hde=scsi ignore=hde
On Mon, 01 Sep 2003 10:45:55 -0500
Kirk Strauser <[EMAIL PROTECTED]> wrote:
> 1) Added this to my grub boot parameters:
>
> hde=scsi ignore=hde
Don't know if this is the problem, but this is my line from
/etc/lilo.conf
append="hdc=ide-scsi hdd=ide-scsi"
--
-johann koenig
Now Playing: Bow W
At 2003-09-01T11:12:07Z, Russell Shaw <[EMAIL PROTECTED]> writes:
> The real scsi will appear under sdxx such as sda1.
Except that it doesn't. In fact, it's not even detected in dmesg.
What I've done so far:
1) Added this to my grub boot parameters:
hde=scsi ignore=hde
2) Created an /etc
Kirk Strauser wrote:
I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic
SCSI CDROM. I've followed various instructions culled from mailing lists,
HOWTOs, etc., but I'm still having problems with getting the two to play
nicely together.
If I enable ide-
I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic
SCSI CDROM. I've followed various instructions culled from mailing lists,
HOWTOs, etc., but I'm still having problems with getting the two to play
nicely together.
If I enable ide-scsi for the CDRW, I
On Fri, 5 Apr 2002, Cheryl Homiak wrote:
> I found the answer!
> Sg0 sg1, etc. for generic scsi, which get used somehow but aren't actually
> linked to scd0 and scd1 or /cdrom etc., has permissions that don't allow you
> to
> access them as a user. since sg0 and sg1 etc. don't belong to the cdrom
I found the answer!
Sg0 sg1, etc. for generic scsi, which get used somehow but aren't actually
linked to scd0 and scd1 or /cdrom etc., has permissions that don't allow you to
access them as a user. since sg0 and sg1 etc. don't belong to the cdrom group
either, this doesn't help any. I changed my pe
On Sat, 30 Mar 2002, Cheryl Homiak wrote:
> I now have both a cdrom and a cdrw on my machine. They are both ide/atapi but
> i
> am using scsi emulation; the cdrw is scd0 and the cdrom is scd1. I have no
> problem accessing the cdrom or the cdrw as far as mounting or listening to
> audio
> cds. H
I now have both a cdrom and a cdrw on my machine. They are both ide/atapi but i
am using scsi emulation; the cdrw is scd0 and the cdrom is scd1. I have no
problem accessing the cdrom or the cdrw as far as mounting or listening to audio
cds. However, when I try to run abcde and/or cdparanoia I get e
Hey guys. I have a burner that I'm using in Linux via scsi emulation, and
a normal ATAPI CD-ROM. Under 2.2.18, by adding
append="hdc=ide-scsi"
to my lilo.conf file, I forced my burner to be handled by the scsi
emulation driver. My cdrom on /dev/hdd was left as an IDE device.
No
> ummm... does it say something like "no pci bios found" in the
> bootup messages? I had a compaq 486 that had scsi and net built
> in and never could get linux to run on it. Compaq had done something
> funny with the pci bios. It was located above normal accessable
> memory. There was a tool t
"Lewis, James M." wrote:
>
> > I've been fighting this Debian install for 3 weeks and am about tired of
> > it.
> > If I don't get an answer here, then I am taking the damn CD to the skeet
> > range. OK, here is what I got:
> >
> > Debian 2.1 bootable CD, official type that comes in the box, has t
> I've been fighting this Debian install for 3 weeks and am about tired of
> it.
> If I don't get an answer here, then I am taking the damn CD to the skeet
> range. OK, here is what I got:
>
> Debian 2.1 bootable CD, official type that comes in the box, has the
> Debian
> tm logo on it and the O
On Fri, 14 Apr 2000, [EMAIL PROTECTED] wrote:
> I've been fighting this Debian install for 3 weeks and am about tired of it.
> If I don't get an answer here, then I am taking the damn CD to the skeet
> range. OK, here is what I got:
>
> Debian 2.1 bootable CD, official type that comes in the box,
I've been fighting this Debian install for 3 weeks and am about tired of it.
If I don't get an answer here, then I am taking the damn CD to the skeet
range. OK, here is what I got:
Debian 2.1 bootable CD, official type that comes in the box, has the Debian
tm logo on it and the O'Rielly cow book i
A few days ago I made a fresh standard install of slink, after that I did an
upgrade pointing to frozen my apt-get, which came out very smoothly (only
procmail was not found). Any way, after having upgraded I decided to upgrade my
kernel also, so I did "apt-get -f install kernel-source-2.2.14",
On Sun, 10 Oct 1999, John Miskinis wrote:
> Hello (and Thanks for continued help),
>
> I have included the "xconsole" output, when I insert the card
> after the system is up. I also included what is output when I
> pulled out the card, as it notes that the SW INT is set and "Why?".
>
> I also m
Hello (and Thanks for continued help),
I have included the "xconsole" output, when I insert the card
after the system is up. I also included what is output when I
pulled out the card, as it notes that the SW INT is set and "Why?".
I also made the /dev/sr0 device from /dev with:
mkmod -m 777 sr0
On Sat, 9 Oct 1999, John Miskinis wrote:
> I am trying to get my JVC XR-W2040 CDROM drive to work under
> debian linux as my other CDROM is very flaky even when it is
> sometimes seen at bootup. I think I am EXTREMELY close, and
> would really appreciated any help. I have been studying the
> PCMC
Hello,
I am on my knees begging for help at this point :) -> :(
I am trying to get my JVC XR-W2040 CDROM drive to work under
debian linux as my other CDROM is very flaky even when it is
sometimes seen at bootup. I think I am EXTREMELY close, and
would really appreciated any help. I have been st
Strange, I thought the default block size for an ISO9660 filesystem was 2048.
I'm not
sure what this block size refers too. I'm not sure what exactly would happen if
you
changed it.
Pierfrancesco Caci wrote:
> I have a scsi cdrom (Plextor) and a scsi cdwriter (Yamaha). They
I have a scsi cdrom (Plextor) and a scsi cdwriter (Yamaha). They both
have a jumper to set the block size to 1024 bytes or to 512 bytes. The
manuals say that for Unix 512 is the good value.
Do you have any suggestions? What does this value mean, after all?
Pf
To: The Debian Gang - A howdy to all:
Since I posted my message yesterday on debian-user about having
problems mounting my Hitachi CDR-1750S cdrom I have found out
some additional information. As a review, the problems is that
when I give the following command
mount -t iso9660 /dev/scd0 /mnt
my
it is the only SCSI cdrom you have.
It could also be necessary to load the SCSI-cdrom driver before, so if the
sequence
# modprobe sr_mod
# mount /dev/scd0 /cdrom
does not work, I don't know what could be wrong. Are you using a custom
(i.e. not shipped wi
On Wed, 27 May 1998, Phlip wrote:
> Date: Wed, 27 May 1998 18:17:38 -0700
> From: Phlip <[EMAIL PROTECTED]>
> To: debian-user@lists.debian.org
> Subject: scsi cdrom
> Resent-Date: 28 May 1998 01:15:17 -
> Resent-From: debian-user@lists.debian.org
> Resent-c
> I hope I'm not in the dark about this due to mental deficiancy. I can't
> seem to mount my cdrom. I have a buslogic bt946c controlling a 1gig
> drive and a chinon 1X cdrom. It recognizes the cdrom at boot buty I
> cannot mount it. I either get "special device not found error" or "not a
> valid bl
Hello
I hope I'm not in the dark about this due to mental deficiancy. I can't
seem to mount my cdrom. I have a buslogic bt946c controlling a 1gig
drive and a chinon 1X cdrom. It recognizes the cdrom at boot buty I
cannot mount it. I either get "special device not found error" or "not a
valid block
Waller Martin MEJ wrote:
>
>Hi,
>
> I'm trying to install debian on a second computer here at work from
>cd-rom. I got the base system installed from floppy OK, and the cd rom was
>apparently detected, but i don't have a clue how to mount it. I was
>expecting a /dev/scd0 bloc
On Thu, Oct 30, 1997 at 04:51:02PM +, Waller Martin MEJ wrote:
> I'm trying to install debian on a second computer here at work from
> cd-rom. I got the base system installed from floppy OK, and the cd rom was
> apparently detected, but i don't have a clue how to mount it. I was
> exp
et 4 to asynchronous SCSI
Vendor: NEC Model: CD-ROM DRIVE:500 Rev: 2.5
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes.
The following message is a courtesy copy of an article
that has been posted as well.
I have a Toshiba 4X Internal CDROM. Upon booting my PC, the scan of
controller 0 reveals that the CDROM is indeed on SCSI controller 0.
However, when Debian Linux 1.3 boots up, it says
scsi: detected 0 hosts
a
Edit /etc/makedev.cfg to remove the "omit { }". It's a syntax error.
We'll make a point release after New Years with this fixed.
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED]
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
o run MAKEDEV in /dev, it conplains about some unexpected "}" in
makedec.cfg.
Can anybody please help?
By the way, the SCSI-cdrom is recognized at the booting time.
Xiaoming Ding
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
I think you haven't loaded the driver for your SCSI controller. The
message about the NCR53c406a seems to indicate you don't have one of
those. Try using the "modprobe" tool, or you can build a custom kernel
with the driver linked in.
Thanks
Bruce
--
Bruce Perens K6BP [EMAIL PRO
37 matches
Mail list logo
