Sponsored Content
Special Forums Hardware Dell XPS M1330 doesn't detect optical drive Post 303041991 by hicksd8 on Tuesday 10th of December 2019 11:36:06 AM
Old 12-10-2019
I'm thinking...............

1. Perhaps the new mobo is faulty as far as this peripheral is concerned
2. Have you accidentally bent a pin on the mobo socket where this device plugs in?
3. Does the mobo have a jumper wrongly set to enable this device? (Compare to old mobo)
4. Is there a separate power connector for this device which you forgot to connect? (Probably not if it's whirring)

Can you connect this optical to another system temporarily just to check that it's working?

If the system BIOS can't see it then you have no hope until it does.

Last edited by hicksd8; 12-10-2019 at 01:04 PM..
This User Gave Thanks to hicksd8 For This Post:
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Magneto-Optical drive for SCO Openserver 5.0.5

Hi, I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160). During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Discussion started by: yurist
2 Replies

2. UNIX for Dummies Questions & Answers

trying to set up an optical drive

Trying to get my unix system to recognize an optical drive, it was delivered to us, so we assumed it worked, in the 2 years since no one ever has used it, we want to now. However, even running probe-scsi-all doesn't bring up that drive. It's a scsi address of 3, at the end of the chain, all... (1 Reply)
Discussion started by: kymberm
1 Replies

3. Shell Programming and Scripting

Why getopts doesn't detect correctly my switches?

Dear all, I have created a KornShell script containing swiches with getopts (command line switches). Normally, my script should work like this: $ ./myscript.ksh -a 12 -b 4 -c 78 The switch a was selected with the argument 12 The switch b was selected with the argument 4 The switch c was... (3 Replies)
Discussion started by: dariyoosh
3 Replies

4. Solaris

cannot detect NIC card on dell vostro 1500

i installed solaris 5.10 on dell vostro 1500...but it does not detect interface card....i need to pratice networking concepts ............please help me in this regard... (1 Reply)
Discussion started by: vivek_ng
1 Replies

5. Hardware

is rhel 6 compatible with dell xps 14

is rhel 6 compatible with dell xps 14.I tried to install it but could not install.Installation hanged at detecting hardware (1 Reply)
Discussion started by: shamapraveen
1 Replies

6. AIX

AIX doesn't detect TS3200 tape library

Hi all, I have a problem here root@host1 / # lsdev -Cc tape rmt0 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Defined 07-00-02 IBM 3573 Tape Medium Changer (FCP) root@host1 / # cfgmgr -l fcs2 Method error... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

7. Ubuntu

Ubuntu 16.04 doesn't detect my second monitor

I have Ubuntu 16.04 (dual boot with Windows 10) and a HP Spectre x360 laptop. I have recently bought a Dell Ultrasharp U2515H monitor, which I connect via a Dell docking station. When I plug the docking station to my laptop on Windows, both monitors are detected and everything works fine. ... (23 Replies)
Discussion started by: twelth_hour
23 Replies
DEVCTL(8)						    BSD System Manager's Manual 						 DEVCTL(8)

NAME
devctl -- device control utility SYNOPSIS
devctl attach device devctl detach [-f] device devctl disable [-f] device devctl enable device devctl suspend device devctl resume device devctl set driver [-f] device driver DESCRIPTION
The devctl utility adjusts the state of individual devices in the kernel's internal device hierarchy. Each invocation of devctl consists of a single command followed by command-specific arguments. Each command operates on a single device specified via the device argument. The device may be specified either as the name of an existing device or as a bus-specific address. More details on supported address formats can be found in devctl(3). The following commands are supported: attach device Force the kernel to re-probe the device. If a suitable driver is found, it is attached to the device. detach [-f] device Detach the device from its current device driver. If the -f flag is specified, the device driver will be detached even if the device is busy. disable [-f] device Disable a device. If the device is currently attached to a device driver, the device driver will be detached from the device, but the device will retain its current name. If the -f flag is specified, the device driver will be detached even if the device is busy. enable device Enable a device. The device will probe and attach if a suitable device driver is found. Note that this can re-enable a device dis- abled at boot time via a loader tunable. suspend device Suspend a device. This may include placing the device in a reduced power state. resume device Resume a suspended device to a fully working state. set driver [-f] device driver Force the device to use a device driver named driver. If the device is already attached to a device driver and the -f flag is speci- fied, the device will be detached from its current device driver before it is attached to the new device driver. If the device is already attached to a device driver and the -f flag is not specified, the device will not be changed. SEE ALSO
devctl(3), devinfo(8) HISTORY
The devctl utility first appeared in FreeBSD 11.0. BSD
February 5, 2015 BSD
All times are GMT -4. The time now is 12:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy