Posted on 04/25/2006 8:11:52 PM PDT by N3WBI3
I have a fried CD-RW. I don't know how it got that way (died all of a sudden).
So, in the meantime, I'm borrowing an external Yamaha and have it hooked up--as I can't afford to replace the CD-drive.
Question 1: I'm running Suse 10.0 Eval, first updated KDE to 3.5.1 and then updated the kernel to 2.6.16-default. Since the kernel upgrade, I cannot get any USB devices to start. I've tried editing /etc/fstab as recommended, but the devices won't mount--and if they do, nothing shows up in Konqueror. I did however, and only once, did
Question 2: How can I add this device to PhoenixBIOS so I can boot from it--the device doesn't show up at all. I'm going to need to be able to boot from the external drive to do any upgrades or patches.
thanks much!!
stout
Typing in /media/yamaha in konq gets nothing to show up, though.
For those of us who dont run suse but do run KDE:
What version of KDE do you run..
I run KDE 3.5.1 level "a".
Upgraded from 3.4.2 via Novell's YaST repository--once the new versions come out, Novell keeps RPM's on hand for SuSE users to keep KDE to date.
The /media/yamaha shows up. However, it doesn't auto-detect--I have to use "mount /dev/sr0 /media/yamaha" as root to get the device to mount--basically, to work.
I've read that starting with SuSE 10, subfs is only on the kernels Novell/OpenSuse compiles and ships with the system--as in upgrading the kernel wipes out the support.
(Didn't learn this until after I upgraded the kernel.)
USB sticks also work with the same command, appropriate devices and mount points. ;)
Will keep an eye on it--when I log off tonight, I'll try it again tomorrow morning--if it works, then I believe I have something working for now
But just out of curiosity--K3b is a universal burning app (meaning it'd work with an external), correct?
That makes some sense. I wouldn't be suprised at all if konq monitored that file for filesystem hints. Autofs should automagically add entries to fstab when media is inserted, but I've noticed that it's not as reliable after an upgrade as it is on a fresh install.
But just out of curiosity--K3b is a universal burning app (meaning it'd work with an external), correct?
That's what I use. Will cut CDs and DVDs. Will let you cut disks on the fly without generating an intermediate ISO, and can erase a rewritable on the fly as it writes too.
I've used K3b before--just wasn't sure if it would work.
I can't burn with it though. I tried switching to TAO, 12x (though the thing is a 24x RW burner. It always returns an error 255.
Incorrect (I think) Autofs should add to mtab not fstab..
/dev/sda1 / reiserfs acl,user_xattr 1 1
/dev/sda8 /home reiserfs acl,user_xattr 1 2
/dev/sda7 /opt reiserfs acl,user_xattr 1 2
/dev/sda5 /usr reiserfs acl,user_xattr 1 2
/dev/sda6 /var reiserfs acl,user_xattr 1 2
/dev/sda3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0
none /subdomain subdomainfs noauto 0 0
/dev/md0 /local xfs defaults 1 2
/dev/cdrom /media/cdrom subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/md1 /BU1 reiserfs defaults 1 2
I bolded the section that contains info on the USB file system and the USB DVD recorder. The item labeled cdrom is actaully my USB DVD writer.
In YAST under hardware I have both the CD-RW DVD-RW listed. Again both are DVD writers but the one listed as DVD is my USB device. The one labeled DVD recorder is an internal IDE recorder that I disconnected.
Because Linux sees all USB devices as SCSI it shows my USB DVD RW as located at /dev/sr0.
IIRC, to get it to recognize it initially, I rebooted with a DVD or CD in the USB drive after I added the initial info to fstab, then it also appeared in hardware under YAST. It was a while ago that I added it but I believe I just copied the line from my DVD recorder and renamed the first part to cdrom so it would see it as a different device. You may have to play around with the entry under fstab a little, rebooting each time with a disk in the drive to get it to recognize it.
Under /var/log/ there are two log files you may want to look at to seee if it is being recognized at all. Messages and boot.msg. Scan through them and look for your device and use that info to get the fstab entry right.
I hope I am not all over the place on this, I have only been using Linux for about a year, but hopefully something here might help.
Sorry for any confusion. Also, if I insert a disk it is automatically recognized so SUSE 10 will recognize it without having to manually mount it. I don't beleive I had to do anything else to get the auto mount to work.
Things seem to be working--just not the auto detection and mounting.
I think the kernel upgrade to 2.6.16 had something to do with it--subfs isn't recognized. But when I upgraded the kernel, I didn't see anything about it in the menuconfig.
Rze,
Do you have noauto or auto for the device in mtab..
That may be distro specific, but on FC4, if I insert a usb device, I see an entry in /etc/fstab for it.
mounting my usb keyfob thingamabob, I see this in fstab.
/dev/sda1 /media/LEXAR_MEDIA vfat pamconsole,exec,noauto,utf8,managed 0 0
It might well be a KDE specific thing that is mounting it, rather than autofs, but that's what I get.
Are we talking about on boot or runtime, I am running FC4 at the office and when I am back there next week I plan on checking this. Screwing with fstab is an ugly way to do things, fstab is one of those files which can really hose a boot sequence..
I agree about mucking about with fstab. Had issues a few weeks ago when I installed another hard disk. (necessary as my MP3 collection had pushed /home to over 90% full) In the process of putting it in and moving things around, my boot sequence got hosed and I ended up booting knoppix to fix fstab so it would recognise everything correctly.
yea autofs is really a better file to use but is not a required file on a Linux system...
Rze,
Whats left on this problem?
I'm at school right now, and my NX server is shut down--so I can't access my computer for the moment.
The external reads in Linux, but K3B won't burn anything. It shows up, but every time I burn, the error 255 comes up. I didn't think there'd be problems with the burning once the device got recognized in Linux.
The BIOS issue still remains though. If I can't boot off the external, there's no way that I know of to perform a clean install/upgrade.
I'm not sure where I'd go or what to do to add the device to the BIOS--so I can select it as a boot option.
Can you try xcdroast? Lets find out if this is OS or application..
I have the Gnome CD creator and K3b under the CD-burning menu--I don't see xcdroast.
Also, I went back into K3b setup and noticed the following with the permissions:
The internal one:
Current: 600 (rzeznikj.disk
New: 666 (rzeznikj.disk)
The Yamaha is listed twice, both carry:
Current: 640 (root.disk)
New: 666 (root.disk)
The programs listed at the bottom also carry root after their permissions.
But if that were the case, wouldn't it prompt me for root's password?
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.