When I run wodim -scanbus or sudo wodim -scanbus, I'd expect to get a listing of the devices attached to the bus. But this does not happen. askwar@winnb000488 ~ $ wodim -scanbus wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. askwar@winnb000488 ~ $ sudo wodim -scanbus wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. askwar@winnb000488 ~ $ sudo wodim --devices wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. askwar@winnb000488 ~ $ wodim --devices wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. askwar@winnb000488 ~ $ wodim -version Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd Wodim 1.1.5.1 Copyright (C) 2006 Cdrkit suite contributors Based on works from Joerg Schilling, Copyright (C) 1995-2006, J. Schilling Burning works just fine though. Even without specifying a device with dev=$something. askwar@winnb000488 ~ $ grep -v \# /etc/wodim.conf | grep -v ^\$ CDR_DEVICE=cdrom CDR_FIFOSIZE=12m cdrom= -1 -1 -1 burnfree I'm using a SATA attached DVD+-RW writer. It's a Dell Latitude D620 notebook. In order to be able to burn with somewhat decent speed, I'm booting the kernel with the kernel parameters "lapic libata.atapi_enabled=1 combined_mode=libata". askwar@winnb000488 ~ $ emerge --info Portage 2.1.2.7 (default-linux/x86/2006.1/desktop, gcc-4.1.2, glibc-2.5-r2, 2.6.19-suspend2-r3.rtr.03-no-apggart i686) ================================================================= System uname: 2.6.19-suspend2-r3.rtr.03-no-apggart i686 Genuine Intel(R) CPU T2400 @ 1.83GHz Gentoo Base System release 1.12.10 Timestamp of tree: Mon, 07 May 2007 06:20:01 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.32 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/php/apache1-php5/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer" DISTDIR="/Gentoo/Portage/distfiles" EMERGE_DEFAULT_OPTS="--alphabetical" FEATURES="ccache collision-protect distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS=" http://ftp.heanet.ie/pub/gentoo/ http://gentoo.supp.name/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.gentoo.or.kr/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo/ http://distfiles.gentoo.org/ " LANG="de_CH.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="de" MAKEOPTS="-j3" PKGDIR="/Gentoo/Portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/Gentoo/Portage/build" PORTDIR="/Gentoo/Portage/tree" PORTDIR_OVERLAY="/Gentoo/Portage/local-tree/misc" SYNC="rsync://winds03:10873/gentoo-portage" USE="X acpi alsa berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dbus dmi dri dvd dvdr eds emboss encode fam firefox fortran gdbm gif gnome gpm gstreamer gtk hal iconv isdnlog jpeg kde kdeenablefinal kdehiddenvisibility ldap libg++ libnotify mad midi mikmod mmx mp3 mpeg ncurses nls nptl nptlonly ogg opengl pam pcmcia pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection samba sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts unicode vorbis wifi win32codecs x86 xine xinerama xml xorg xv zlib" ALSA_CARDS="dummy hda-intel intel8x0 intel8x0m usb-audio usb-usx3y" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse synaptics vmmouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="dummy none nv nvidia vga" Unset: CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Try either cdrkit-1.1.6 (better automatic detection of devices) or with wodim dev=ATA -scanbus.
I just upgraded - no success :( askwar@winnb000488 ~ $ wodim --version Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd Wodim 1.1.6 Copyright (C) 2006 Cdrkit suite contributors Based on works from Joerg Schilling, Copyright (C) 1995-2006, J. Schilling askwar@winnb000488 ~ $ sudo wodim -scanbus wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. askwar@winnb000488 ~ $ sudo wodim dev=ATA -scanbus WARNING: the ATA: method is considered deprecated on modern kernels! Use --devices to display the native names. wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. askwar@winnb000488 ~ $ sudo wodim dev=ATAPI -scanbus WARNING: the ATAPI: method is considered deprecated on modern kernels! Mapping device specification to ATA: method now. To force the old ATAPI: method, replace ATAPI: with OLDATAPI: wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation.
I also have the same problem, also with a SATA dvd+-rw, but I noticed that dev=ATAPI makes mention of trying dev=OLDATAPI. This seems to work. Additionally, README.ATAPI.setup mentions that the default device is /dev/cdrw. I have a dvd burner, so this device does not exist on my system. Instead "wodim dev=/dev/dvdrw1 -scanbus" lists the device. It looks like before using wodim, wodim.conf should be edited, though I have not yet been able to figure out the correct settings. CDR_DEVICE=dvdrw dvdrw= /dev/dvdrw1 -1 -1 burnfree does not work for me. I did try with and without space after dvdrw=, and with both spaces and tabs as separators. I don't know if this means it's a documentation issue, or a problem with SATA drives.
Any chance, this is related to libata? I'm using kernel 2.6.21.6 with libata and CONFIG_PATA_SIS=y (so obviously PATA devices) and I can't use -scanbus or --devices as well. dmesg tells this about the device: scsi 1:0:0:0: CD-ROM TOSHIBA DVD-ROM SD-R6012 1030 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 sr 1:0:0:0: Attached scsi generic sg1 type 5
I've downgraded to app-cdr/cdrkit-1.1.2 which doesn't have this issue.
i confirm the bug i'll ask upstream about this.
Ok from what i understand cdrkit now with -scanbus only get's scsi devices not IDE/ATA devices. If you pass the arguments wodim dev=/dev/cdrw it actually works can someone with a scsi burner confirm this ?
I can't confirm this. Wodim's -scanbus option works for me both on a machine with real scsi devices > wodim -scanbus scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) 'PLEXTOR ' 'CD-ROM PX-40TS ' '1.05' Removable CD-ROM 0,4,0 4) 'PLEXTOR ' 'CD-R PX-W124TS' '1.07' Removable CD-ROM 0,5,0 5) * 0,6,0 6) 'PIONEER ' 'DVD-ROM DVD-305 ' '1.03' Removable CD-ROM 0,7,0 7) * and on a machine with an IDE/ATAPI device driven by the old ATA framework (not libata), $ wodim -scanbus scsibus1000: 1000,0,0 100000) * 1000,1,0 100001) * 1000,2,0 100002) 'PLEXTOR ' 'DVDR PX-708A ' '1.11' Removable CD-ROM 1000,3,0 100003) * 1000,4,0 100004) * 1000,5,0 100005) * 1000,6,0 100006) * 1000,7,0 100007) * whereas my notebook's DVDRW device (as said in my prevous comment) cannot be found by -scanbus and this is the only machine where I use the new libata framework.
Please try, *cdrkit-1.1.8 (04 Jun 2008) 04 Jun 2008; Steve Dibb <beandog@gentoo.org> +cdrkit-1.1.8.ebuild: Version bump, bug 224337
app-cdr/cdrkit-1.1.9 still has it it only detects my device with cdrecord dev=OLDATAPI -scanbus scsibus0: 0,0,0 0) 'ASUS ' 'DRW-1814BLT ' '1.04' Removable CD-ROM which leads my mind to set this in my conf: CDR_DEVICE=asus asus=OLDATAPI:0,0,0 -1 -1 burnfree but it does not work, should it? another thing: For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from but there is no README.ATAPI.setup in the files installed by cdrkit it is here: http://ai.ms.mff.cuni.cz/cgi-bin/dwww/usr/share/doc/wodim/README.ATAPI.setup
*** Bug 346973 has been marked as a duplicate of this bug. ***
Looks like versions do not magically fix bugs.
I get now the same issue also with app-cdr/cdrkit-1.1.11. There are two of five computers, which suffer from this problem. I did not yet find a characteristical difference between two groups.
I think you should report this to upstream: http://lists.alioth.debian.org/mailman/listinfo/debburn-devel (or try to use cdrtools instead ;))
# Michał Górny <mgorny@gentoo.org> (05 Jun 2017) # (on behalf of Treecleaner project) # Abandoned upstream and downstream. Buggy to the point of producing # corrupted media. Use the original app-cdr/cdrtools or one of the many # other alternatives (app-cdr/dvd+rw-tools, dev-libs/libburn...). # Removal in 30 days. Bugs #254312, #591778. app-cdr/cdrkit
commit 05f5454a3108c4ffaeae8be59f4a32c74048293c Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Wed Jul 5 12:17:52 2017 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Wed Jul 5 12:35:12 2017 app-cdr/cdrkit: Remove last-rited pkg, #591778
