The error
'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
appear
when executing
xmcd &
How to fix it?
How to fix it?
> How to fix it?
You must change XMCD's idea of what hardware adress
the CD-Drive has.
Dont know from the top of my head if this is Configurable
or requires a source code change.
--
Lars Tunkrans
> > The error
> > 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> > appear
> > when executing
> > xmcd &
> > How to fix it?
> The Motif CD Player makes a reasonable assumption that
> you CD drive is SCSI unit 6. This is the normal
> Adress for any Older SUN Workstation. And xmcd is an old
> program ( I used it in 1993 )
> You must change XMCD's idea of what hardware adress
> the CD-Drive has.
> Dont know from the top of my head if this is Configurable
> or requires a source code change.
> --
> Lars Tunkrans
Either stop vold (/etc/init.d/volmgt stop) or make xmcd use the vold
managed device in /vol/dev/aliases/
Thomas
How to fix it?
and
wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
[7] 4672
wcars27e-147> USCSICMD ioctl failed: I/O error
USCSICMD ioctl failed: I/O error
Both result in
Warning:
Device is not SCSI-II compliant.
My computer is Sun Ultra 10.
> > > The error
> > > 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> > > appear
> > > when executing
> > > xmcd &
> > > How to fix it?
> > The Motif CD Player makes a reasonable assumption that
> > you CD drive is SCSI unit 6. This is the normal
> > Adress for any Older SUN Workstation. And xmcd is an old
> > program ( I used it in 1993 )
> > You must change XMCD's idea of what hardware adress
> > the CD-Drive has.
> > Dont know from the top of my head if this is Configurable
> > or requires a source code change.
> > --
> > Lars Tunkrans
> The problem is more likely that vold is controlling the device.
> Either stop vold (/etc/init.d/volmgt stop) or make xmcd use the vold
> managed device in /vol/dev/aliases/
> Thomas
I dunno what xmcd is - you certainly need a higher version.Quote:> The error
> 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> appear
> when executing
> xmcd &
> How to fix it?
--
Michael Tosch / Master IS/IT Support
Ericsson Eurolab Deutschland GmbH
Tel: +49 2407 575 313
> and
> wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
> [7] 4672
> wcars27e-147> USCSICMD ioctl failed: I/O error
> USCSICMD ioctl failed: I/O error
> Both result in
> Warning:
> Device is not SCSI-II compliant.
> My computer is Sun Ultra 10.
I have no idea if xmcd handles non-SCSI CDROM:s, but from the error
message it doesn't seem that way.
Thomas
>> and
>> wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
>> [7] 4672
>> wcars27e-147> USCSICMD ioctl failed: I/O error
>> USCSICMD ioctl failed: I/O error
>> Both result in
>> Warning:
>> Device is not SCSI-II compliant.
>> My computer is Sun Ultra 10.
>An ultra 10 does not normally have a SCSI CDROM, it has an IDE CDROM
>normally at /dev/rdsk/c0t2d0s0.
>I have no idea if xmcd handles non-SCSI CDROM:s, but from the error
>message it doesn't seem that way.
--
**************************************************************************
* ftp://ftp.nndev.org/pub | #include <std.disclaimer> *
that sounds like the "security fix problem".Quote:>I try both
>wcars27e-145> xmcd -dev /vol/dev/aliases/cdrom0 &
>[7] 4591
>wcars27e-146> USCSICMD ioctl failed: I/O error
>USCSICMD ioctl failed: I/O error
>and
>wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
>[7] 4672
>wcars27e-147> USCSICMD ioctl failed: I/O error
>USCSICMD ioctl failed: I/O error
non-root users can no longer do USCSI ioctls.
You have to use a program that uses the ioctls specifically for CDROMs.
/usr/include/sys/cdio.h
--
http://www.blastwave.org/ for solaris pre-packaged binaries with pkg-get
Sign up to maintain a package for your own favourite software!
[Trim the no-bots from my address to reply to me by email!]
http://www.spamlaws.com/state/ca1.html
>>and
>>wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
>>[7] 4672
>>wcars27e-147> USCSICMD ioctl failed: I/O error
>>USCSICMD ioctl failed: I/O error
>that sounds like the "security fix problem".
>non-root users can no longer do USCSI ioctls.
Without more debugging the real reason is hart to tell.
--
URL: http://www.fokus.fhd.de/usr/schilling ftp://ftp.berlios.de/pub/schily
You probably should increase the verbosity of the "sd" driver to
diagnose the problem, with the command (you have to run this as
"root")
echo 'sd_error_level/W1' | adb -wk
> > I try both
> > wcars27e-145> xmcd -dev /vol/dev/aliases/cdrom0 &
> > [7] 4591
> > wcars27e-146> USCSICMD ioctl failed: I/O error
> > USCSICMD ioctl failed: I/O error
> Are there any error messages logged to /var/adm/messages when you try
> this?
> You probably should increase the verbosity of the "sd" driver to
> diagnose the problem, with the command (you have to run this as
> "root")
> echo 'sd_error_level/W1' | adb -wk
1. Cannot map sar output "ssdx" to cxtxdxsx...not in path_to_install or /dev/rdsk
2. Search cmd
3. Urgent: "lpc stat" and "lpc stat lj02" gives different result
5. how to kill "mt" or make "/dev/rmt/..." device NOT BUSY?
6. Driver For Realtek 8029 ethernet card
7. GETSERVBYNAME()????????????????????"""""""""""""
8. INN+Suck = Reply postings not threaded
9. open("/dev/rdsk/c0t0d0", O_RDWR);
10. echo "yes"|newfs /dev/rdsk/c3t0d0s1 ; Question
11. syslogd: "/" in "/dev//dev/tty"
12. Why "fdisk /dev/hdb1" works but not "fdisk /dev/hdb"!?
13. Help with /dev/console: no such device, and "cannot open tty"