RE: [Cooker] ide-scsi problems
> > > http://www-106.ibm.com/developerworks/linux/library/l- > fs6/?open&t=grl,l=252,p=lfs6 > ) they talk about the use of /dev-state. The use the new bind ability of > mount. It is not new actually. And its usage here is not necessary at all - we achieve the same result with devfsd.conf It has one advantage that permissions are preserved even for non-devfs case. It is unlikely be of significant advantage as we do not (expect to) boot without devfs except for real emergency They do later say it turned out to be useful, but I'd like to see the example of it. This is nice, elegant, eye-catching, but absolutely not needed. but they also make a cp ( from their init wrapper ) : > cp -ax /dev-state/compat/* /dev ... > So, if you happen to be using a non-devfs kernel module, you'll need to > create a device node in /dev manually. The problem with this approach is > that > this new device node will be ignored by devfsd, meaning that the next time > you reboot, it will disappear. Our solution to this problem is to have the > /dev-state/compat directory; if you have a non-devfs module, simply create > your old-style device nodes in /dev-state/compat and they will be manually > added to the devfs filesystem at boot time, thanks to the considerate > steps > of our handy init wrapper. > This contradicts with the code. It should be cp -ax /dev-state/compat /dev so that the whole /dev/compat tree is recreated. As it stands now, you have /dev/compat/some-device in non-devfs case and /dev/some-device in devfs case. But yes, having special separate directory for extra files is one possibility. Having it inside /dev gives you advantage of having it both with and without devfs. Unfortunately it does not solve the problem our rc.sysinit tries to solve. You can't simply do 'mknod /dev/foo ...' and expect it to exist after reboot. That is the major problem for end user. You have to modify every package to create files in /dev/compat (or somewhere else) and teach users to do the same. For that matter you can just as well add extra lines to devfsd.conf (good, creating file is simpler, but devfsd.conf provides additional possibilities). -andrej
RE: [Cooker] ide-scsi problems
[I have been cleaning folder]
> > - there is someting strange with ide-scsi CDs; instead of creating
link
> to
> > /dev/scsi/... plain block device is created:
> >
> > filr-xr-xr-x1 root root 33 ??? 1 1970 cdrom0 ->
> > ../ide/host0/bus1/target0/lun0/cd
> > brw-rw-rw-1 root root 11, 0 ??? 1 1970 cdrom1
> >
> > I do not know if it may have some side-effect; in any case,
permisions
> from
> > pam_console are not applied here so you get world-readable device.
It
> may be
> > considered a problem. OTOH canonical path has correct permissions:
> >
> > {pts/1}% ll /dev/scsi/host0/bus0/target0/lun0/cd
> > brw-rw1 bor cdwriter 11, 0 ??? 9 23:15
> > /dev/scsi/host0/bus0/target0/lun0/cd
> >
> > as tey should be. I have no idea who does it.
>
> booh :-(
It again the result of our "restoring of devfs state" in rc.sysinit.
Basically, when registering /dev/cdroms/* entry cdrom drivers check real
device name is registered. But it is *not* registered - it is tried, but
existing devfs entry for scsi/host0/bus0/target0/lun0/cd is found so
nothing gets registered. Contrary to the expectation (but
understandable), registering devfs entry from within a kernel is *not*
the same as doing mknod on devfs. So cdrom driver gives up and just
created file instead of link.
How many times have I said "restoring devfs state is evil Evil EVIL" :(
-andrej
Re: [Cooker] ide-scsi problems
Borsenkow Andrej <[EMAIL PROTECTED]> writes:
[...]
> Nope, it does not work for non-devfs case (tested). Kernel will probe
> scsi_hostadapter *only* if no hostadapters are registered. It means, if you
> have two (me as example :-) and one of them is loaded and other not - kernel
> will not try to modporbe host_adapter at all (which is awfull kludge anyway).
good point. Ok, so:
probeall scsi_hostadapter module1 module2
in /etc/modules.conf
scsi_hostadapter
in /etc/modules (need for non-devfsd)
scsi_hostadapter instead of scsi-hosts in /etc/modules.devfs
[...]
> - ide-scsi is unconditionally loaded in rc.sysinit:
>
> if grep -q "ide-scsi" /proc/cmdline ; then
> modprobe ide-cd >/dev/null 2>&1
> modprobe ide-scsi >/dev/null 2>&1
this is needed if you ide-cd module and don't want your cdrom to be seen as
scsi. It's not needed when ide-cd is not in module (which is our case). So i
propose:
if grep -q "ide-scsi" /proc/cmdline ; then
modprobe ide-cd >/dev/null 2>&1 && modprobe ide-scsi >/dev/null 2>&1
> It may be leftover, now ide-scsi is preloaded in /etc/modules; so this
> probably should be removed? In any case, it prevents autocleaning module.
as for scsi modules, we're going away from autocleaning. ethx modules should
not be autocleaned either. Good spot for autocleaning are the fs modules.
>
> - there is someting strange with ide-scsi CDs; instead of creating link to
> /dev/scsi/... plain block device is created:
>
> filr-xr-xr-x1 root root 33 ??? 1 1970 cdrom0 ->
> ../ide/host0/bus1/target0/lun0/cd
> brw-rw-rw-1 root root 11, 0 ??? 1 1970 cdrom1
>
> I do not know if it may have some side-effect; in any case, permisions from
> pam_console are not applied here so you get world-readable device. It may be
> considered a problem. OTOH canonical path has correct permissions:
>
> {pts/1}% ll /dev/scsi/host0/bus0/target0/lun0/cd
> brw-rw1 bor cdwriter 11, 0 ??? 9 23:15
> /dev/scsi/host0/bus0/target0/lun0/cd
>
> as tey should be. I have no idea who does it.
booh :-(
Re: [Cooker] ide-scsi problems
On Sun, 9 Sep 2001, Borsenkow Andrej wrote: > - ide-scsi is unconditionally loaded in rc.sysinit: > > if grep -q "ide-scsi" /proc/cmdline ; then > modprobe ide-cd >/dev/null 2>&1 > modprobe ide-scsi >/dev/null 2>&1 > > It may be leftover, now ide-scsi is preloaded in /etc/modules; so this > probably should be removed? In any case, it prevents autocleaning module. Where is it loaded? If it is not laoded very early then hdparm has a problem trying to optimize a disk that doesn't exist yet. I am speaking of the /etc/sysconfig/hardisks file which is also problematic because most hdparm options do not work on CD-ROM's anyway. -- Sincerely, David Walluck <[EMAIL PROTECTED]>
Re: [Cooker] ide-scsi problems
Pixel wrote:
> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>
>
>>Pixel wrote:
>>
>>>in fact, the best solution is to use
>>>probeall scsi_hostadapter scsi_hostadapter1 scsi_hostadapter2 ...
>>>and to perl -pi -e 's/scsi-hosts/scsi_hostadapter/g' /etc/modules.devfs
>>>that way, both devfs and non-devfs will work nicely.
>>>
>>How should it work with non-devfs? And I do not see any point in chaging the
>>name - scsi-hosts is already used in modules.devfs and is good mnemonic name.
>>
>
> because of:
>
> pixel@no:/home/chmou/rpm/BUILD/linux>grep -2 -r scsi_hostadapter .
> ./drivers/scsi/scsi.c-#ifdef CONFIG_KMOD
> ./drivers/scsi/scsi.c- if (scsi_hosts == NULL)
> ./drivers/scsi/scsi.c: request_module("scsi_hostadapter");
> ./drivers/scsi/scsi.c-#endif
> ./drivers/scsi/scsi.c- return scsi_register_device_module((struct
>Scsi_Device_Template *) ptr);
>
> The kernel explicitly modprobe's scsi_hostadapter. So unless we patch the
> kernel to make it modprobe scsi-hosts, we should patch devfsd to modprobe
> scsi_hostadapter instead of scsi-hosts.
>
> # If they asked for ide-scsi, load it
Nope, it does not work for non-devfs case (tested). Kernel will probe
scsi_hostadapter *only* if no hostadapters are registered. It means, if
you have two (me as example :-) and one of them is loaded and other not
- kernel will not try to modporbe host_adapter at all (which is awfull
kludge anyway). Some more random comments:
- loading such modules as ide-scsi and ppa results in nasty console
output. If they are going to be loaded on demand, something needs to be
done about it
- ide-scsi is unconditionally loaded in rc.sysinit:
if grep -q "ide-scsi" /proc/cmdline ; then
modprobe ide-cd >/dev/null 2>&1
modprobe ide-scsi >/dev/null 2>&1
It may be leftover, now ide-scsi is preloaded in /etc/modules; so this
probably should be removed? In any case, it prevents autocleaning module.
- there is someting strange with ide-scsi CDs; instead of creating link
to /dev/scsi/... plain block device is created:
filr-xr-xr-x1 root root 33 ??? 1 1970 cdrom0 ->
../ide/host0/bus1/target0/lun0/cd
brw-rw-rw-1 root root 11, 0 ??? 1 1970 cdrom1
I do not know if it may have some side-effect; in any case, permisions
from pam_console are not applied here so you get world-readable device.
It may be considered a problem. OTOH canonical path has correct permissions:
{pts/1}% ll /dev/scsi/host0/bus0/target0/lun0/cd
brw-rw1 bor cdwriter 11, 0 ??? 9 23:15
/dev/scsi/host0/bus0/target0/lun0/cd
as tey should be. I have no idea who does it.
-andrej
RE: [Cooker] ide-scsi problems
If you boot into Gnome, you can mount and unmount w/o any problems. Must be
a bug in KDE.
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Borsenkow Andrej
Sent: Saturday, September 08, 2001 1:00 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject:Re: [Cooker] ide-scsi problems
Vincent Meyer wrote:
> Hello,
>
> In todays latest cooker I have two problems with ide scsi drives.
>
> First - can't mount the drive.. KDE says "special device does not
> exist" for /dev/scd0. On doing a little digging, /dev/scd0 is now a
> link to /dev/host0/bus0/target0/lun0/cd, In that dirctory there is
> generic and disc, but no cd. Creating a link cd --> disc make it kinda
> work, but not completely.
>
I cannot reproduce it.
{pts/2}% ll /dev/scd0
lr-xr-xr-x1 root root 31 ??? 9 2001 /dev/scd0 ->
scsi/host1/bus0/target0/lun0/cd
> With the link in place, now i can try to mount and it says "no
> media" rather than the above message. Haven't tried it after rebooting
> yet.
>
Confirmed. Same here.
> Eject isn't happy. "eject /mnt/cdrom2" and "eject /dev/scd0" both
> bomb with a "last parameter is invalid" message.
>
eject scd0 works here.
But as long as I canot mount - it does not matter :-(
-andrej
Re: [Cooker] ide-scsi problems
Pixel wrote:
> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>
>
>>Pixel wrote:
>>
>>>in fact, the best solution is to use
>>>probeall scsi_hostadapter scsi_hostadapter1 scsi_hostadapter2 ...
>>>and to perl -pi -e 's/scsi-hosts/scsi_hostadapter/g' /etc/modules.devfs
>>>that way, both devfs and non-devfs will work nicely.
>>>
>>How should it work with non-devfs? And I do not see any point in chaging the
>>name - scsi-hosts is already used in modules.devfs and is good mnemonic name.
>>
>
> because of:
>
> pixel@no:/home/chmou/rpm/BUILD/linux>grep -2 -r scsi_hostadapter .
> ./drivers/scsi/scsi.c-#ifdef CONFIG_KMOD
> ./drivers/scsi/scsi.c- if (scsi_hosts == NULL)
> ./drivers/scsi/scsi.c: request_module("scsi_hostadapter");
> ./drivers/scsi/scsi.c-#endif
> ./drivers/scsi/scsi.c- return scsi_register_device_module((struct
>Scsi_Device_Template *) ptr);
>
> The kernel explicitly modprobe's scsi_hostadapter. So unless we patch the
> kernel to make it modprobe scsi-hosts, we should patch devfsd to modprobe
> scsi_hostadapter instead of scsi-hosts.
>
>
Ah, that's really cute. And we do not even need to patch devfsd but just
change modules.devfsd. Two times cute!
Do you know kernel sources by heart? :-)
-andrej
Re: [Cooker] ide-scsi problems
Borsenkow Andrej <[EMAIL PROTECTED]> writes:
> Pixel wrote:
> > in fact, the best solution is to use
> > probeall scsi_hostadapter scsi_hostadapter1 scsi_hostadapter2 ...
> > and to perl -pi -e 's/scsi-hosts/scsi_hostadapter/g' /etc/modules.devfs
> > that way, both devfs and non-devfs will work nicely.
>
> How should it work with non-devfs? And I do not see any point in chaging the
> name - scsi-hosts is already used in modules.devfs and is good mnemonic name.
because of:
pixel@no:/home/chmou/rpm/BUILD/linux>grep -2 -r scsi_hostadapter .
./drivers/scsi/scsi.c-#ifdef CONFIG_KMOD
./drivers/scsi/scsi.c- if (scsi_hosts == NULL)
./drivers/scsi/scsi.c: request_module("scsi_hostadapter");
./drivers/scsi/scsi.c-#endif
./drivers/scsi/scsi.c- return scsi_register_device_module((struct
Scsi_Device_Template *) ptr);
The kernel explicitly modprobe's scsi_hostadapter. So unless we patch the
kernel to make it modprobe scsi-hosts, we should patch devfsd to modprobe
scsi_hostadapter instead of scsi-hosts.
Re: [Cooker] ide-scsi problems
Pixel wrote: > in fact, the best solution is to use > > probeall scsi_hostadapter scsi_hostadapter1 scsi_hostadapter2 ... > > and to perl -pi -e 's/scsi-hosts/scsi_hostadapter/g' /etc/modules.devfs > > > that way, both devfs and non-devfs will work nicely. How should it work with non-devfs? And I do not see any point in chaging the name - scsi-hosts is already used in modules.devfs and is good mnemonic name. The pb used to be solve > by putting every scsi_hostadapter* in /etc/modules. But i didn't know probeall > at that time (maybe it didn't exist?). The probeall solution is much neater > and also ensures the scsi_hostadapters are insmoded in the same order. > I did not realised that it makes preloading redundant. Good.
Re: [Cooker] ide-scsi problems
Borsenkow Andrej <[EMAIL PROTECTED]> writes: > thread today (forgot subject and do not have it anymore). You have to add > > probeall svsi-hosts scsi_hostadapter scsi_hostapdapter1 ... in fact, the best solution is to use probeall scsi_hostadapter scsi_hostadapter1 scsi_hostadapter2 ... and to perl -pi -e 's/scsi-hosts/scsi_hostadapter/g' /etc/modules.devfs that way, both devfs and non-devfs will work nicely. The pb used to be solve by putting every scsi_hostadapter* in /etc/modules. But i didn't know probeall at that time (maybe it didn't exist?). The probeall solution is much neater and also ensures the scsi_hostadapters are insmoded in the same order.
Re: [Cooker] ide-scsi problems
PLease, please!
The problem of disappearing ide-scsi cdrom is totally diferent; see
another thread today (forgot subject and do not have it anymore). You
have to add
probeall svsi-hosts scsi_hostadapter scsi_hostapdapter1 ...
for all SCSU hostadapters to modules.conf. That will cause devfsd to
insmod SCSI modules on access to /dev/scd* and this will also create
/dev/scd* if it does not exist. See:
{pts/2}% sudo rmmod ide-scsi
{pts/2}% ll /dev/scd*
zsh: no matches found: /dev/scd*
{pts/2}% ll /dev/scd0
lr-xr-xr-x1 root root 31 ??? 9 00:44 /dev/scd0 ->
scsi/host1/bus0/target0/lun0/cd
{pts/2}% lsmod | grep ide-scsi
ide-scsi8096 0 (autoclean)
scsi_mod 91040 4 [sr_mod ide-scsi ppa sd_mod]
{pts/2}% grep hostadapter /etc/modules.conf
alias scsi_hostadapter ppa
alias scsi_hostadapter1 ide-scsi
probeall scsi-hosts scsi_hostadapter scsi_hostadapter1
What you have done is to commet out removing of device entry when module
is unloaded. While it is possible solution it has drawbacks.
-andrej
guran wrote:
> Hi
>
> I had the same 'not found device' so I went to /etc/devfsd.conf and hashed
> out the two last lines:
>
> # Enable full compatibility mode for old device names. You may comment these
> # out if you don't use the old device names. Make sure you know what you're
> # doing!
> REGISTER.* MKOLDCOMPAT
> UNREGISTER .* RMOLDCOMPAT
>
> # You may comment out the above and uncomment the following if you've
> # configured your system to use the original "new" devfs names or the really
> # new names
> #REGISTER vc/.* MKOLDCOMPAT
> #UNREGISTER vc/.* RMOLDCOMPAT
> #REGISTER pty/.* MKOLDCOMPAT
> #UNREGISTER pty/.* RMOLDCOMPAT
> #REGISTER miscMKOLDCOMPAT
> #UNREGISTER miscRMOLDCOMPAT
>
> # You may comment these out if you don't use the original "new" names
> REGISTER.* MKNEWCOMPAT
> UNREGISTER .* RMNEWCOMPAT
>
> And then all was back.
> guran
>
Re: [Cooker] ide-scsi problems
Hi I had the same 'not found device' so I went to /etc/devfsd.conf and hashed out the two last lines: # Enable full compatibility mode for old device names. You may comment these # out if you don't use the old device names. Make sure you know what you're # doing! REGISTER.* MKOLDCOMPAT UNREGISTER .* RMOLDCOMPAT # You may comment out the above and uncomment the following if you've # configured your system to use the original "new" devfs names or the really # new names #REGISTER vc/.* MKOLDCOMPAT #UNREGISTER vc/.* RMOLDCOMPAT #REGISTER pty/.* MKOLDCOMPAT #UNREGISTER pty/.* RMOLDCOMPAT #REGISTER miscMKOLDCOMPAT #UNREGISTER miscRMOLDCOMPAT # You may comment these out if you don't use the original "new" names REGISTER.* MKNEWCOMPAT UNREGISTER .* RMNEWCOMPAT And then all was back. guran -- Mandrake Linux 8.1 beta Cooker kernel-2.4.8.21 vers:1.569
Re: [Cooker] ide-scsi problems
Borsenkow Andrej wrote: > Vincent Meyer wrote: > >> With the link in place, now i can try to mount and it says "no >> media" rather than the above message. Haven't tried it after >> rebooting yet. >> > > Confirmed. Same here. > Eh ... I forgot to insert CD. You too? :-) So, everything works for me on new install. I may suspect problems on update from earlier versions, that's true. -andrej
Re: [Cooker] ide-scsi problems
Vincent Meyer wrote:
> Hello,
>
> In todays latest cooker I have two problems with ide scsi drives.
>
> First - can't mount the drive.. KDE says "special device does not
> exist" for /dev/scd0. On doing a little digging, /dev/scd0 is now a
> link to /dev/host0/bus0/target0/lun0/cd, In that dirctory there is
> generic and disc, but no cd. Creating a link cd --> disc make it kinda
> work, but not completely.
>
I cannot reproduce it.
{pts/2}% ll /dev/scd0
lr-xr-xr-x1 root root 31 ??? 9 2001 /dev/scd0 ->
scsi/host1/bus0/target0/lun0/cd
> With the link in place, now i can try to mount and it says "no
> media" rather than the above message. Haven't tried it after rebooting
> yet.
>
Confirmed. Same here.
> Eject isn't happy. "eject /mnt/cdrom2" and "eject /dev/scd0" both
> bomb with a "last parameter is invalid" message.
>
eject scd0 works here.
But as long as I canot mount - it does not matter :-(
-andrej
[Cooker] ide-scsi problems
Hello, In todays latest cooker I have two problems with ide scsi drives. First - can't mount the drive.. KDE says "special device does not exist" for /dev/scd0. On doing a little digging, /dev/scd0 is now a link to /dev/host0/bus0/target0/lun0/cd, In that dirctory there is generic and disc, but no cd. Creating a link cd --> disc make it kinda work, but not completely. With the link in place, now i can try to mount and it says "no media" rather than the above message. Haven't tried it after rebooting yet. Eject isn't happy. "eject /mnt/cdrom2" and "eject /dev/scd0" both bomb with a "last parameter is invalid" message. In order to get ide-scsi support on the pcmcia cards I still have to modprobe -r ide-scsi then modprobe ide-scsi back in again. Vinny
Re: [Cooker]IDE-SCSI problems...
On Sun, 15 Jul 2001 20:42:30 -0700 Slava Kharin <[EMAIL PROTECTED]> wrote: > I am having troubles to access my ide-atapi CD-RW drive. I have it > configured as 'hdd=ide-scsi" in the kernel. I tried 2.4.3-mdk and 2.4.6-3mdk > >from the cooker without any success. I had no problems under LM-7.2 with the > 2.2.x kernel. > I have a link /dev/cdrom -> /dev/scd0. > However when I try to mount the drive as 'mount /mnt/cdrom' I get > mount: /dev/cdrom: unknown device > > [root@littlebox /root]# lsmod > ide-scsi7568 0 > scsi_mod 85312 1 [ide-scsi] Afaik you need the sr_mod module for mounting scsi cdroms, and the sg module for burning or formatting scsi disks. Try to modprobe sr_mod. > mount /dev/hdc /mnt/cdrom gives the same thing, unknown device That's good, it's a scsi device now. -- Marcel Pol [EMAIL PROTECTED]
Re: [Cooker]IDE-SCSI problems...
First... I would take it out of supermount... it can be problematic. In linuxconf (file systems, access local drives) change it from a partition of /mnt/cdrom to a partition of /dev/cdrom and then change the Type from supermount to iso9660. Then tab to options... I set the options as read only (don't worry you will still be able to write to it), user mountable, and not mount at boot time. Also, you might want to set /usr/bin/cdrecord as executable to "other" or make sure you are part of the cdwriter group. --- Slava Kharin <[EMAIL PROTECTED]> wrote: > Hi, > > I am having troubles to access my ide-atapi CD-RW > drive. I have it > configured as 'hdd=ide-scsi" in the kernel. I tried > 2.4.3-mdk and 2.4.6-3mdk > from the cooker without any success. I had no > problems under LM-7.2 with the > 2.2.x kernel. > > I found a similar problem report in the archive (see > below) but no solution > was sugested. > The kernel seems to recognize the cdrom drive. Here > what dmesg says: > > hda: ST51270A, ATA DISK drive > hdc: WDC AC28400R, ATA DISK drive > hdd: LG CD-RW CED-8081B, ATAPI CD/DVD-ROM drive > > scsi0 : SCSI host adapter emulation for IDE ATAPI > devices > Vendor: LGModel: CD-RW CED-8081B Rev: > 1.00 > Type: CD-ROM ANSI > SCSI revision: 02 > > > I can see the cdrom drive both in /proc/ide/hdd and > in /proc/scsi. I have a > link /dev/cdrom -> /dev/scd0. The corresponding > line in fstab is > > /dev/cdrom /mnt/cdrom iso9660 > ro,nosuid,noauto,exec,user,nodev 0 0 > > The drive is recongized when I run cdrecord: > > cdrecord --scanbus > Cdrecord 1.10 (i586-mandrake-linux-gnu) Copyright > (C) 1995-2001 Jörg Schilling > Linux sg driver version: 3.1.19 > Using libscg version 'schily-0.5' > scsibus0: > 0,0,0 0) 'LG ' 'CD-RW CED-8081B ' > '1.00' Removable CD-ROM > 0,1,0 1) * > 0,2,0 2) * > 0,3,0 3) * > 0,4,0 4) * > 0,5,0 5) * > 0,6,0 6) * > 0,7,0 7) * > > However when I try to mount the drive as 'mount > /mnt/cdrom' I get > > mount: /dev/cdrom: unknown device > > > Help is appreciated. > > Thanks, > Slava > - > From: Ryan Little > Subject: [Cooker]IDE-SCSI problems > Date: Mon, 23 Apr 2001 18:51:12 -0700 > > ok, this is weird, I have a sony ide cdburner on > hdc, and ide-scsi is all > set up, I'm running a clean install of Mandrake 8, > but apparantly I've > boffed something up while trying to disable > automount on my cd drivesor > not, hadn't really tried mounting this drive before > either. > > [root@littlebox /root]# lsmod > > ide-scsi7568 0 > scsi_mod 85312 1 [ide-scsi] > [root@littlebox /root]# cat /proc/scsi/scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: SONY Model: CD-RW CRX145E Rev: 1.0b > Type: CD-ROM ANSI SCSI > revision: 02 > [root@littlebox /root]# mount /dev/scd0 /mnt/cdrom > mount: /dev/scd0: unknown device > [root@littlebox /root]# ls -l /dev/scd0 > brw-rw1 root cdwriter 11, 0 Apr 14 > 07:06 /dev/scd0 > > mount /dev/hdc /mnt/cdrom gives the same thing, > unknown device > I'm at a loss here. > > In case it makes a difference here's /etc/fstab, > although it shouldn't > matter when I try to mount it manually like above... > > [root@littlebox /root]# cat /etc/fstab > /dev/hdb5 / ext2 defaults 1 1 > none /dev/pts devpts mode=0620 0 0 > /dev/hdb7 /home ext2 defaults 1 2 > /dev/hdc /mnt/cdrom auto > user,noauto,nosuid,exec,nodev,ro 0 0 > /dev/cdrom2 /mnt/cdrom2 auto > user,noauto,nosuid,exec,nodev,ro 0 0 > /dev/hda6 /mnt/downloads ext2 defaults 1 2 > /mnt/floppy /mnt/floppy supermount > fs=vfat,dev=/dev/fd0 0 0 > /dev/hda1 /mnt/windows vfat > user,exec,umask=0,codepage=850,iocharset=iso8859-1 0 > 0 > none /proc proc defaults 0 0 > /dev/hda5 /usr ext2 defaults 1 2 > /dev/hdb6 swap swap defaults 0 0 > > also: > [root@littlebox /root]# mount -t iso9660 /dev/hdc > /mnt/cdrom > mount: wrong fs type, bad option, bad superblock on > /dev/hdc, >or too many mounted file systems >(could this be the IDE device where you in > fact use >ide-scsi so that sr0 or sda or so is needed?) > ide-scsi: hdc: unsupported command in request queue > (0) > isofs_read_super: bread failed, dev=16:00, > iso_blknum=16, block=32 > > Please if anyone can tell me whats wrong reply to me > @ > [EMAIL PROTECTED] or [EMAIL PROTECTED] > > > > > > > > = SI Reasoning [EMAIL PROTECTED] gnupg/pgp key id 035213BC __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: [Cooker]IDE-SCSI problems...
On Monday 16 July 2001 05:42, you wrote: > I am having troubles to access my ide-atapi CD-RW drive. Hi HP wrote in the installation text, to my CD-RW, that sometimes the IDE chip might have problems when a fast harddrive and a CD-RW was placed on the same cable. My problems disappeared when I put both my harddrives as a,b and had the CD-RW as c. regards guran
[Cooker]IDE-SCSI problems...
Hi, I am having troubles to access my ide-atapi CD-RW drive. I have it configured as 'hdd=ide-scsi" in the kernel. I tried 2.4.3-mdk and 2.4.6-3mdk from the cooker without any success. I had no problems under LM-7.2 with the 2.2.x kernel. I found a similar problem report in the archive (see below) but no solution was sugested. The kernel seems to recognize the cdrom drive. Here what dmesg says: hda: ST51270A, ATA DISK drive hdc: WDC AC28400R, ATA DISK drive hdd: LG CD-RW CED-8081B, ATAPI CD/DVD-ROM drive scsi0 : SCSI host adapter emulation for IDE ATAPI devices Vendor: LGModel: CD-RW CED-8081B Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 02 I can see the cdrom drive both in /proc/ide/hdd and in /proc/scsi. I have a link /dev/cdrom -> /dev/scd0. The corresponding line in fstab is /dev/cdrom /mnt/cdrom iso9660 ro,nosuid,noauto,exec,user,nodev 0 0 The drive is recongized when I run cdrecord: cdrecord --scanbus Cdrecord 1.10 (i586-mandrake-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling Linux sg driver version: 3.1.19 Using libscg version 'schily-0.5' scsibus0: 0,0,0 0) 'LG ' 'CD-RW CED-8081B ' '1.00' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * However when I try to mount the drive as 'mount /mnt/cdrom' I get mount: /dev/cdrom: unknown device Help is appreciated. Thanks, Slava --------- From: Ryan Little Subject: [Cooker]IDE-SCSI problems Date: Mon, 23 Apr 2001 18:51:12 -0700 ok, this is weird, I have a sony ide cdburner on hdc, and ide-scsi is all set up, I'm running a clean install of Mandrake 8, but apparantly I've boffed something up while trying to disable automount on my cd drivesor not, hadn't really tried mounting this drive before either. [root@littlebox /root]# lsmod ide-scsi7568 0 scsi_mod 85312 1 [ide-scsi] [root@littlebox /root]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX145E Rev: 1.0b Type: CD-ROM ANSI SCSI revision: 02 [root@littlebox /root]# mount /dev/scd0 /mnt/cdrom mount: /dev/scd0: unknown device [root@littlebox /root]# ls -l /dev/scd0 brw-rw1 root cdwriter 11, 0 Apr 14 07:06 /dev/scd0 mount /dev/hdc /mnt/cdrom gives the same thing, unknown device I'm at a loss here. In case it makes a difference here's /etc/fstab, although it shouldn't matter when I try to mount it manually like above... [root@littlebox /root]# cat /etc/fstab /dev/hdb5 / ext2 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /home ext2 defaults 1 2 /dev/hdc /mnt/cdrom auto user,noauto,nosuid,exec,nodev,ro 0 0 /dev/cdrom2 /mnt/cdrom2 auto user,noauto,nosuid,exec,nodev,ro 0 0 /dev/hda6 /mnt/downloads ext2 defaults 1 2 /mnt/floppy /mnt/floppy supermount fs=vfat,dev=/dev/fd0 0 0 /dev/hda1 /mnt/windows vfat user,exec,umask=0,codepage=850,iocharset=iso8859-1 0 0 none /proc proc defaults 0 0 /dev/hda5 /usr ext2 defaults 1 2 /dev/hdb6 swap swap defaults 0 0 also: [root@littlebox /root]# mount -t iso9660 /dev/hdc /mnt/cdrom mount: wrong fs type, bad option, bad superblock on /dev/hdc, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) ide-scsi: hdc: unsupported command in request queue (0) isofs_read_super: bread failed, dev=16:00, iso_blknum=16, block=32 Please if anyone can tell me whats wrong reply to me @ [EMAIL PROTECTED] or [EMAIL PROTECTED]
Re: [Cooker]IDE-SCSI problems....
On Monday 23 April 2001 21:59, you wrote: > On 23 Apr 2001 21:04:41 -0400, Ryan Little wrote: > > ok, this is weird, I have a sony ide cdburner on hdc, and ide-scsi is all > > set up, I'm running a clean install of Mandrake 8, but apparantly I've > > boffed something up while trying to disable automount on my cd > > drivesor not, hadn't really tried mounting this drive before either. > > Here's a quick stab in the dark. 2.4.x kernels use hdx="scsi" instead of > hdx="ide-scsi". Have in the parameters in grub "hdc=ide-scsi", with the latest cooker kernel, and works fine! Unfortunately, only works for my DVD player, can't get it to recognise my CD-RW yet, as the controller is a PCMCIA IDE card, and isn't present at boot time. (CD-RW is "hde") Does the kernel accept both "ide-scsi" and "scsi" ? Does it seem to make a difference which one is used? V.
Re: [Cooker]IDE-SCSI problems....
On 23 Apr 2001 21:04:41 -0400, Ryan Little wrote: > ok, this is weird, I have a sony ide cdburner on hdc, and ide-scsi is all > set up, I'm running a clean install of Mandrake 8, but apparantly I've > boffed something up while trying to disable automount on my cd drivesor > not, hadn't really tried mounting this drive before either. Here's a quick stab in the dark. 2.4.x kernels use hdx="scsi" instead of hdx="ide-scsi". -- Steve Fox http://k-lug.com
[Cooker]IDE-SCSI problems....
ok, this is weird, I have a sony ide cdburner on hdc, and ide-scsi is all set up, I'm running a clean install of Mandrake 8, but apparantly I've boffed something up while trying to disable automount on my cd drivesor not, hadn't really tried mounting this drive before either. [root@littlebox /root]# lsmod ide-scsi7568 0 scsi_mod 85312 1 [ide-scsi] [root@littlebox /root]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX145E Rev: 1.0b Type: CD-ROM ANSI SCSI revision: 02 [root@littlebox /root]# mount /dev/scd0 /mnt/cdrom mount: /dev/scd0: unknown device [root@littlebox /root]# ls -l /dev/scd0 brw-rw1 root cdwriter 11, 0 Apr 14 07:06 /dev/scd0 mount /dev/hdc /mnt/cdrom gives the same thing, unknown device I'm at a loss here. In case it makes a difference here's /etc/fstab, although it shouldn't matter when I try to mount it manually like above... [root@littlebox /root]# cat /etc/fstab /dev/hdb5 / ext2 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /home ext2 defaults 1 2 /dev/hdc /mnt/cdrom auto user,noauto,nosuid,exec,nodev,ro 0 0 /dev/cdrom2 /mnt/cdrom2 auto user,noauto,nosuid,exec,nodev,ro 0 0 /dev/hda6 /mnt/downloads ext2 defaults 1 2 /mnt/floppy /mnt/floppy supermount fs=vfat,dev=/dev/fd0 0 0 /dev/hda1 /mnt/windows vfat user,exec,umask=0,codepage=850,iocharset=iso8859-1 0 0 none /proc proc defaults 0 0 /dev/hda5 /usr ext2 defaults 1 2 /dev/hdb6 swap swap defaults 0 0 also: [root@littlebox /root]# mount -t iso9660 /dev/hdc /mnt/cdrom mount: wrong fs type, bad option, bad superblock on /dev/hdc, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) ide-scsi: hdc: unsupported command in request queue (0) isofs_read_super: bread failed, dev=16:00, iso_blknum=16, block=32 Please if anyone can tell me whats wrong reply to me @ [EMAIL PROTECTED] or [EMAIL PROTECTED]
