To mount it, look for /dev/sda1 and so on. The usb devices I use reguarly are a external usb hard drive and a usb thumbdrive. They show up as /dev/sda1 and /dev/sda2 . The order depends on the order in which I plug them in and they are detected. Note that /dev/sda is the actual device and /dev/sda1 is the first (and only in my case) partition on the device. I am not exactly sure how it is with mp3 players, but I would think it is the same since they are usually just detected as "hard drives". Hope this helps, Preston On Thu, 23 Dec 2004 09:41:23 -0700, William Lugg wrote:

I've got a Rio Cali MP3 player that I hooked up to my SuSE 9.1 box running KDE. The first time I connected it, it noted that I had and displayed a Konqueror window showing its contents. Later, I attempted to copy some files to it and the X server hung. After a CTRL-ALT-Backspace and I logged in again, I plugged the Cali in again and nothing happens.

What might I have hosed up that would keep SuSE Plugger from seeing the device when it's plugged in? How can I manually mount the device? I know how to use the mount command, but how do I determine which block device in /dev it is? I guess I'm looking for a more general answer that I can apply to any future event like this one.

Thanks. Bill Lugg -- Bill Lugg Milstar Software Support Peterson AFB, CO

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

I think all your problems are because of a bug I found when I installed SuSE 9.1 on my new mainboard. If you have a board with USB 1.1 only, then all is fine. USB storage devices are recognized the first time and all times after that. If you have USB 2.0 USB Ports and USB 2.0 device with SuSE 9.1 (and I assume 9.2, too), then the first connect after system boot is fine, after that all connects fail. I wanted to look at it and compiled the kernel with usb mass storage debug on. Using that option, the log file fills up with messages but: It's working like a charm. So I think it's a general problem with USB 2.0 wich seem sto have a serious timing problem. Well, now I just recompile my SuSE kernels with USB mass storage debug mode and have lot's of log files to purge, but I have working USB 2.0 devices. I tried Hubert Mantels kernel of the day, too. Same problem. Debug mode on: No problem. It's not only my board. Got this error on a nvidia nforce2 board and on an intel d845 board. Greets, Daniel William Lugg schrieb am 23.12.2004 21:58:

That was just the ticket. Thanks. Though I'm currently having problems getting KDE to run, I was able to mount it from the command line and copy the files. Now my mp3 player is happy as a clam at high tide.

On another note, if I plug my card reader in and put a flash card in it, I assume that i just start trying to mount /dev/sda# until I find the one that mounts?

Are there any thoughts on what might be wrong with SuSE Plugger?

Thanks again for the help.

Hi, I'm using a Fujitsu-Siemens Amilo D series portable (P4, 30gyg HD & 512 MB RAM) with SUSE 9.2. At a given moment in a normal kde-linux session, after the kde-screensaver turned on, the only thing I got was a black screen. No keyboard combination worked, etc ... Restarted my pc (manually) and I was still having a black screen. Even the bios boot options where gone (you know, when turn on your pc usually the first thing you get is the manufactors logo and some bios options (F2, F8, F10). After several attempts (guess after 1 hour) I finally got the Siemens Logo and I was able to start up the bios. But it did not start my Linux OS. I got a black screen with "Insert system diskette and press Enter key to reboot". When inserting the Suse cd-rom, I was able to boot my OS. This sounded to me like an error in the /mbr. I've tried several times to repair/reinstall (different) bootloaders, but still the same problem. Finally I decided to format my whole HD (using Partition Magic) and to reinstall Suse. And guess what, I'm still having the same problem: "Insert system diskette and press Enter key to reboot" which I can solve through booting with the cd. I've tried different bios-settings for booting & several bootloaders. My question(s): 1. Does anybody recognizes this problem? 2. Is this a hardware/software/bios/mbr problem? 3. What else could I try? Thanks for your time, Rik rik at onckelinx dot be

Hallo! kappfinder findet nichts obwohl es neu installierte Programme gibt. Woran liegt das? SuSE 9.0, Kernel 2.4.21-266-athlon, KDE 3.3.2 Gruss

On Wed December 29 2004 9:54 am, rik wrote:

Hi Fred,

Thanks for your answer. I've managed to solve the problem:

- Changed the boot order in my bios to 1. HD 2. Floppy 3. CD-ROM

For some reason my pc does not boot when cd-rom comes first (only when I inserted the Suse CD).

Correct.......if there's not a bootable CD in the drive, then it's bypassed to the next drive. SOME systems will "barf" on this, and you'll have to remove the offending CD (non-bootable) then continue the boot process.

I do have a boot floppy, and that's OK. But then I've to set the floppy as the 1st to boot in the Bios (which is strange ;)

No.......that's "standard."

Anyway, I've installed the bios I found on the Fujitsu-Siemens website. But still the same. It's no longer a 'problem' since I boot my HD first.

Good deal!

But my question remains: how can kde/suse (?) ruin my bios/boot process in a normal session? Or was the reason probably a hardware crash that had nothing to do with my OS?

Correct.....nothing to do with the OS. Linux boots with a BIOS of it's own, once a proper drive has been found. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah