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. -- Bill Lugg Milstar Software Support Peterson AFB, CO On Thu, 23 December 2004 10:12 am, Preston Hagar wrote:

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

On Thursday 23 December 2004 09:58, William Lugg wrote:

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?

Have you tried Kwikdisk? -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."

On Tue December 28 2004 7:24 pm, rik wrote: [snip]

inally 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?

I've encountered it with some ViA chipsets, yes. 'One reason I'm not fond of them. IF you can't resolve it, and if you have a floppy drive, trying making a boot floppy. 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

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