Archiv > General
Autofs
Holger:
--- Quote ---Es gibt nichts was auf ein DVD / CD Laufwerk hinweist. Kein sr*, sg*, cd, dvd.
--- End quote ---
kann ich bestätigen
obwohl auch hier das LW beim booten gefunden wird:
--- Quote ---hdc: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdc: UDMA/33 mode selected
cdrom: Uniform CD-ROM driver Revision: 3.20
e820: BIOS-provided physical RAM map:
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
pci 0000:00:0f.0: Boot video device
ide0: BM-DMA at 0x10c0-0x10c7
ide1: BM-DMA at 0x10c8-0x10cf
Probing IDE interface ide0...
Probing IDE interface ide1...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide-gd driver 1.18
ide-cd driver 5.00
ide-cd: hdc: ATAPI 48X DVD-ROM DVD-R/RAM CD-R/RW drive, 2048kB Cache
--- End quote ---
Gruß
Holger
wino:
Hallo,
Was sagt beispielsweise:
lspci -nn
lsmod | grep ata
dmesg | grep ata
udevadm info -a -p $(udevadm info -q path -n /dev/sr0) # /dev/hda oder wie Euer Laufwerk heißt.
Gruß
wino
obelix:
Hallo wino.
--- Code: ---MLD> lspci -nn
00:00.0 Class 0500: 10de:02f0
00:00.1 Class 0500: 10de:02fa
00:00.2 Class 0500: 10de:02fe
00:00.3 Class 0500: 10de:02f8
00:00.4 Class 0500: 10de:02f9
00:00.5 Class 0500: 10de:02ff
00:00.6 Class 0500: 10de:027f
00:00.7 Class 0500: 10de:027e
00:02.0 Class 0604: 10de:02fc
00:03.0 Class 0604: 10de:02fd
00:04.0 Class 0604: 10de:02fb
00:09.0 Class 0500: 10de:0270
00:10.0 Class 0604: 10de:026f
00:10.1 Class 0403: 10de:026c
00:14.0 Class 0680: 10de:0269
00:18.0 Class 0600: 1022:1100
00:18.1 Class 0600: 1022:1101
00:18.2 Class 0600: 1022:1102
00:18.3 Class 0600: 1022:1103
00:0a.0 Class 0601: 10de:0260
00:0a.1 Class 0c05: 10de:0264
00:0b.0 Class 0c03: 10de:026d
00:0b.1 Class 0c03: 10de:026e
00:0d.0 Class 0101: 10de:0265
00:0e.0 Class 0101: 10de:0266
00:0f.0 Class 0101: 10de:0267
03:00.0 Class 0300: 10de:06e4
04:05.0 Class 0c00: 1106:3044
--- End code ---
lsmod | grep ata findet nichts.
--- Code: ---MLD> dmesg | grep ata
BIOS-e820: [mem 0x000000007ffb0000-0x000000007ffbdfff] ACPI data
DMI: MAXDATA System Product Name/A8N-VM Maxdata-CSM, BIOS 0208 10/17/2006
Memory: 2067688k/2096832k available (3966k kernel code, 28692k reserved, 1775k data, 396k init, 1187528k highmem)
.data : 0xc13df85a - 0xc159b480 (1775 kB)
libata version 3.00 loaded.
sata_nv 0000:00:0e.0: version 3.5
sata_nv 0000:00:0e.0: Using SWNCQ mode
sata_nv 0000:00:0e.0: setting latency timer to 64
scsi0 : sata_nv
scsi1 : sata_nv
ata1: SATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe000 irq 21
ata2: SATA max UDMA/133 cmd 0xe400 ctl 0xe080 bmdma 0xe008 irq 21
sata_nv 0000:00:0f.0: Using SWNCQ mode
sata_nv 0000:00:0f.0: setting latency timer to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0xdc00 ctl 0xd880 bmdma 0xd400 irq 20
ata4: SATA max UDMA/133 cmd 0xd800 ctl 0xd480 bmdma 0xd408 irq 20
ata1: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
EXT4-fs (hda1): mounted filesystem with ordered data mode. Opts: (null)
--- End code ---
--- Code: ---MLD> udevadm info -a -p $(udevadm info -q path -n /dev/hdc)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:0d.0/ide1/1.0/block/hdc':
KERNEL=="hdc"
SUBSYSTEM=="block"
DRIVER==""
ATTR{ro}=="0"
ATTR{size}=="8388604"
ATTR{stat}==" 0 0 0 0 0 0 0 0 0 0 0"
ATTR{range}=="1"
ATTR{discard_alignment}=="0"
ATTR{events}==""
ATTR{ext_range}=="1"
ATTR{events_poll_msecs}=="2000"
ATTR{alignment_offset}=="0"
ATTR{inflight}==" 0 0"
ATTR{removable}=="1"
ATTR{capability}=="119"
ATTR{events_async}==""
looking at parent device '/devices/pci0000:00/0000:00:0d.0/ide1/1.0':
KERNELS=="1.0"
SUBSYSTEMS=="ide"
DRIVERS=="ide-cdrom"
ATTRS{media}=="cdrom"
ATTRS{model}=="TOSHIBA DVD-ROM SD-M1612"
ATTRS{drivename}=="hdc"
ATTRS{firmware}=="1004"
ATTRS{serial}==""
looking at parent device '/devices/pci0000:00/0000:00:0d.0/ide1':
KERNELS=="ide1"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:0d.0':
KERNELS=="0000:00:0d.0"
SUBSYSTEMS=="pci"
DRIVERS=="AMD_IDE"
ATTRS{irq}=="0"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x01018a"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="ff"
ATTRS{device}=="0x0265"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-7"
ATTRS{vendor}=="0x10de"
ATTRS{resource1}=="P"
ATTRS{resource3}=="P"
ATTRS{subsystem_device}=="0x81bc"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
--- End code ---
Gruß
Obelix
wino:
Hallo Obelix,
Bitte noch die Ausgabe von ls -l /dev/disk/by-path
Aus dieser Ausgabe und den vorherigen kann man eine Regel für udev ableiten. Danach sollte das Laufwerk als /dev/cdrom und /dev/dvd eingebunden werden können.
EDIT:// Kannst die Regeldatei als 20-custom.rules unter /etc/udev/rules.d abspeichern und testen.
--- Code: ---# custom rules
# cdrom
SUBSYSTEM=="block", KERNEL=="hd*", SUBSYSTEMS=="ide", ATTRS{media}=="cdrom", SYMLINK+="cdrom dvd cdrw/%k"
--- End code ---
MfG
wino
obelix:
Hi Wino.
Ohh man Danke für den Schubser., Da bin ich ganz wild auf udev und merke es nicht :rolleyes: :wand . Wieso übernimmt man nicht die Ubuntu Udev - Rules?
Gruß
Obelix
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version