Sponsored Content
Special Forums Hardware Dell XPS M1330 doesn't detect optical drive Post 303043497 by milhan on Wednesday 29th of January 2020 07:03:38 PM
Old 01-29-2020
Hi,

Looks like the problem was the mobo. Got a new motherboard off of eBay and now the new mobo detects the optical drive fine.

Thanks for the help.
 

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
UDISKS-GLUE.CONF(5)						udisks-glue Manual					       UDISKS-GLUE.CONF(5)

NAME
udisks-glue.conf - udisks-glue configuration file format SYNOPSIS
~/.udisks-glue.conf $XDG_CONFIG_HOME/udisks-glue/config /etc/udisks-glue.conf $XDG_CONFIG_DIRS/udisks-glue/config DESCRIPTION
udisks-glue is configured by a series of match directives referencing filter directives. Filter directives define parameters that filter the UDisks events. Match directives specify actions to be taken by udisks-glue in case the corresponded filter matches. Filter and match directives can be specified in any order. You should use unique names for filter directives. The rules are evaluated in the order the match directives are specified. A default directive is a special directive used as a fallback in case no other directives match. It does not reference a filter directive. You may choose not to specify a default directive. Due to the way the rules are evaluated, it's recommended that more specific match directives are defined before less specific ones. If a match directive does not specify one of the available actions, another directive may be chosen. The currently available match directives are: automount If set, try to automatically mount the device (unset by default) automount_filesystem Filesystem type to use when automounting the device automount_options List of options to use when automounting the device post_insertion_command Command to run after a device is inserted or after its media has been made available post_mount_command Command to run after a device has been mounted post_unmount_command Command to run after a device has been unmounted post_removal_command Command to run after a device or its media has been removed udisks-glue will substitute some tokens with information about the device in each of the commands listed above: %device_file Path to the device file %mount_point Last known mount point for the device (only replaced in post_mount_command and post_unmount_command) The currently supported filter parameters are: label (string) User-visible label of the detected file system optical (boolean) Set if the device uses optical disc as its media optical_disc_closed (boolean) Set if the optical disc is closed optical_disc_has_audio_tracks (boolean) Set if the optical disc has audio tracks optical_disc_has_audio_tracks_only (boolean) Set if all tracks in the optical disc are audio tracks partition (boolean) Set if the device is a partition of another device partition_table (boolean) Set if the device has a partition table readonly (boolean) Set if the device is a ready-only device removable (boolean) Set if the device is a removable device type (string) Extended information about the device, generally set to the name of the detected file system if the usage property is set to filesystem usage (string) The result of probing for signatures on the block device, generally set to filesystem if a mountable file system was detected uuid (string) UUID of the detected file system Note that the rules are evaluated only at the time the device or its media is inserted. Internal drives are always ignored. EXAMPLE
The following configuration example shows how you can automount USB pendrives and similar devices. Notifications are provided by a custom script that could display on-screen information or provide notifications in some other way: filter disks { optical = false partition_table = false usage = filesystem } match disks { automount = true automount_options = sync post_mount_command = "mount-notify mounted %device_file %mount_point" post_unmount_command = "mount-notify unmounted %device_file %mount_point" } A more complex example shows how the filters can be used to mount optical and non-optical media (USB pendrives and the like) using differ- ent mount options and how a specific program can be launched on non-closed optical discs. # # Filters # filter disks { optical = false partition_table = false usage = filesystem } filter burnable { optical = true optical_disc_closed = false } filter optical { optical = true } # # The default entry (only used if no filters match) # default { post_insertion_command = "insertion-notify %device_file" } # # Additional entries # match disks { automount = true automount_options = { sync, noatime } post_mount_command = "mount-notify mounted %device_file %mount_point" post_unmount_command = "mount-notify unmounted %device_file %mount_point" } match burnable { post_insertion_command = "k3b %device_file" post_mount_command = "mount-notify mounted %device_file %mount_point" post_insertion_command = "udisks --mount %device_file --mount-options ro" } match optical { automount = true automount_options = ro post_mount_command = "mount-notify mounted %device_file %mount_point" post_insertion_command = "udisks --mount %device_file --mount-options ro" } SEE ALSO
udisks(1), udisks-glue(1) udisks(7), udisks-daemon(8) udisks-glue 2011-04-20 UDISKS-GLUE.CONF(5)
All times are GMT -4. The time now is 02:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy