Sponsored Content
Full Discussion: CDROM Woes
Top Forums UNIX for Dummies Questions & Answers CDROM Woes Post 29370 by RTM on Friday 4th of October 2002 09:51:25 AM
Old 10-04-2002
According to the information I found on sunsolve, you should insure you installed the dvd per instructions that came with it (part of the answerbook according to the pdf file but I could not find it on docs.sun.com ). Since it shows in this documentation that it is a scsi device, you should see it in the output of probe-scsi-all. If you don't then the system doesn't see it so you need to install per the instructions.

Hardware info on Blade 1000


Componet list

Install and user guide
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Network Woes!! Please help! :confused:

Hello, We have an old Axil running SunOS Release 5.5.1. Recently, we updated our network, so the gateway and domain changed. Our network admin forgot (or didn't know) that we had this machine on the network, so it quietly lost its mind. Now we are trying to add it back to the network. He... (5 Replies)
Discussion started by: mrbig1492
5 Replies

2. Solaris

Remote CD woes

Good Day, I've remotely mounted a cdrom (no problems theere). The kicker is I can see the directories on the remote CD bout I can't see the files. What am I doing wrong? I'm logged in as root on both systems. All the permissions seem okay - what am I missing? Thanks (2 Replies)
Discussion started by: greg69
2 Replies

3. UNIX for Dummies Questions & Answers

Mksysb and Savevg woes

hi, i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work for about a month with no... (2 Replies)
Discussion started by: boredazfcuk
2 Replies

4. Solaris

pkgadd woes

Morning all, I am attempting to load a package from a Solaris 8 CDROM. This fails with the error : "pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap> No changes were made to the system" Any help would be appreciated Andy (6 Replies)
Discussion started by: AndyD
6 Replies

5. Solaris

SSH woes

version of solaris: SunOS 5.8 Generic-117350-39 sun4u sparc SUNW,Netra-240 version of SSH: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 Task: I need to have another Machine ssh into my machine, by either RSA authentication or username/pass authentication. History: In the begining my... (4 Replies)
Discussion started by: EWTGPAC
4 Replies

6. Shell Programming and Scripting

Regular expression woes

(Continuation of this thread: https://www.unix.com/shell-programming-scripting/136423-sed-regular-expression-problem.html) how would I replace a line that contains only a number, e.g. 6.00, with another number stored in variable $bulksize or $half ? I guess I don't understand all the parts... (1 Reply)
Discussion started by: bluesmodular
1 Replies

7. Solaris

Locale woes

Greetings Forumers! I've been fighting a locale problem on a v490 running Solaris 10 u4 (8/07). When I login to the system, I get several "locale" error messages: user1's password: Last login: Wed May 26 2010 09:14:13 -0400 from system1 You have mail. couldn't set locale correctly couldn't... (0 Replies)
Discussion started by: bluescreen
0 Replies

8. Web Development

mysql 4.0 -> 5.0 upgrade woes(?)

We recently upgraded mysql from 4.0 to 5.0 and the following code is throwing (via DB.php) a "Database Error: Unknown" error. I can say with certainty that my connection parameters are correct and functional. It's been so long since I've done any mysql, I'm hoping someone can look at the code and... (0 Replies)
Discussion started by: tiggyboo
0 Replies

9. Solaris

Jumpstart woes

Hey, I have been battling with jumpstart for the past few days. Interface nxge0 is set on a vlan: nxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 0.0.0.0 netmask ff000000 ether 0:21:28:3c:a0:6 nxge998000:... (0 Replies)
Discussion started by: stantonnet
0 Replies

10. AIX

Samba Woes

Hi all With the recent virus attacks we have been tasked with upgrading Samba to a "secure" version. Currently running 3.0.29a and looking to put the latest version down 4.6.5. Being a lazy bod I have only ever installed this, a long time ago, when you could get it in BFF filesets. Have... (6 Replies)
Discussion started by: splattty
6 Replies
CD(9)							   BSD Kernel Developer's Manual						     CD(9)

NAME
cd -- CDROM driver for the CAM SCSI subsystem DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com- mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags. QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver. The following is a list of quirks that the driver recognize. CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what size it is. This flag is currently unimplemented in the CAM cd driver. CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag. CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with multiple luns that are not a part of a changer. CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto- matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial read capacity command for LUN 0 of the changer through the changer scheduling code. CD_Q_10_BYTE_ONLY This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam- ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6 byte commands. FILES
/sys/cam/scsi/scsi_cd.c is the driver source file. SEE ALSO
cd(4), scsi(4) HISTORY
The cd manual page first appeared in FreeBSD 2.2. AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry <ken@FreeBSD.org>. BSD
September 2, 2003 BSD
All times are GMT -4. The time now is 01:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy