Well i just bought myself a USB2.0 DVD burner for my computer. Well as usuall with winblows it was easy to set it up and all but then when i booted to slackware to get it set up in there i was having a bit of trouble. My friend said i should see if it was setup right away as some are in K3B so i did that but it doesn't find it. So as root i did a tail -f /var/log/messages and i found out that the usb drive was detected and set at /dev/uba but i wasn't able to mount a disc i put in there nor was i able to add the device manually in k3b. After searching the forums i didnt' really find anything that really was directed at this exact problem. So can you guys help a semi-n00b out here? Btw this is the output that i see for when i turn on the drive when in linux.

Look in your kernel config file and see if you see this:

# Block devices
#
CONFIG_BLK_DEV_UB=y

There'll be several other CONFIG_whatever's under #Block devices but according to what you've said so far I'd be willing to bet that CONFIG_BLK_DEV_UB is set to y or m. I'm not sure about the 2.6.12 kernel series but in the 2.6.11 series the help file for UB says that if you enable it you will cripple usb-storage. Having UB set to y or m is why your USB storage devices are being assigned ub* instead of sd*. You may want to look at the help file for UB and see if this problem still exists.

Here is the help file from my 2.6.11.5 kernel config:

I'm not sure if this is still a problem, but I know it is with the 2.6.11.xx series of kernels. One thing is UB was not designed for USB 2 storage devices, as it states it is for things like flash keys and memory cards (I think). If you will set the CONFIG_BLK_DEV_UB=n and recompile the kernel I *think* it might solve your problem, but I can't be 100% sure that it will.


Later,
MMYoung

Well thanks man, that worked and it's now recognized in k3b, now i seem to have another problem. When i goto mount a data-dvd i get this. Any clue what i have to do now?

DVD's usually have UDF filesystems, not ISO9660.

Try mounting it without the / after /mnt/cdrom2 and unless you have some special need, I never use any of the other stuff. So give this a try:

mount /dev/sr0 -t iso9660 /mnt/cdrom2

See if that'll mount. If so just add the following to your fstab:

/dev/sr0 /mnt/cdrom2 iso9660 noauto,users,ro 0 0

That way, it ain't mounted at boot and anybody can manually mount/umount it.

HTH,
MMYoung

True, but my DVD drives are all mounted with the iso9660 filesystem. Never had any problems with data or video DVD's.

Thinking out loud, if you specify udf will it mount a data CD (iso9660)? When you specify iso9660 it will mount both CD's and DVD's, so does it work the other way around?

Later,
MMYoung

Well after looking on google before checking back here i saw something about udf. so i tried that. nothing. still wont' work. I also noticed when i click on the drive the first time when i get a k3b error saying "malformed url" so i'm thinking that also has something to do with it. I tried mounting with no / after cdrom2 as with mount -t udf /dev/sr0 /mnt/cdrom2 -o umask=000 and i get the same error. So any more idea's?

Did you try it with iso9660 and without all that umask and such stuck on the end of the command?

Later,
MMYoung

Yea, tried with w/out the "-o umask=000" options. still the same thing, I also found out that i can't even burn a cd with it, so something is fishy. Oh another thing, i can play a dvd movie from the drive through xine. So something is definatly wrong, hopefully it's not something huge with my system thats screwing me up here.

well a friend of mine changed somethings for me and had me recompile my kernel. and now when i turn on the drive, it shows up as /dev/sda and /dev/sg0 but it's not showing up k3b anymore. This is the full thing that shows up when i turn it on.

Figured i'd post a reply to you guys that helped and those of you who would be interested to know if i got it working. I did get it working. I had a friend of mine look into my kernel config and he said there were some things that needed changing. mainly with usb and scsi emulation. he changed the config and i compiled and installed the kernel. Now the problem i had in the post above is sorta a bug persay imho with linux and how it handles usb optical drives. If i would turn on the drive with a disc in it that had data on it. it would read the drive as say a usb flash drive and would create /dev/sda and /dev/sg0. Now if i were to turn it on w/out a disc in it would create /dev/sr0 and dev/sg0 and thats what i want. I burned a cd at 32x just fine and i'm going to do a few more at 48x to see if the usb buss can handle it or not. And then tommorow i'll be going to buy some dvd-r's to test out burning dvd's in linux with to see how it handles. Thanks for all you guys that helped. It's the reason i like linux people mostly anymore as they are willing to help unlike people who are windows guru's who would just point and laugh at a n00b question.

Same problem. Since moving from Slackware 10.1 running 2.4.29 to Slackware 10.1 running 2.6.10, I cannot burn a DVD with my Sony USB 2.0 DVD/RW drive. I get a bunch of messages in the system log about device going offline. Then an lsmod shows usb_storage with a number approaching 4 gigs. I cannot modprobe -r usb_storage as it says device busy, even though the burner light is off and I've exited K3b. I have to reboot to use the drive.

The same drive on the same PC running the same version of K3B burns DVD's fine on the 2.4 kernel. Please fix this!