Hi, I have a Creative MuVo 64MB player. It worked fine with SuSE 9.0 but when I upgraded to 9.1 Pro, no luck. :-( Any ideas on how to get this to work with SuSE 9.1?? I really don't want to downgrade to 9.0 just to use the MuVo player.
Matthew Dunaway wrote:
Hi, I have a Creative MuVo 64MB player. It worked fine with SuSE 9.0 but when I upgraded to 9.1 Pro, no luck. :-( Any ideas on how to get this to work with SuSE 9.1?? I really don't want to downgrade to 9.0 just to use the MuVo player.
I found that I could get a 128Mb MuVo to work by creating a directory (as root)
# mkdir /media/muvo
and putting the line
/dev/sda1 /media/muvo subfs fs=floppyfss,user,procuid,nodev,nosuid,sync 0 0
(one line)
into /etc/fstab.
The problem seems to be submount, which is new in 9.1. After I've done this, the device appears mounted correctly 15-20 seconds after inserting the device.
Occasionally, the device mounts itself as something like /media/USB... instead.
The problem seems to be submount. You can disable submount altogether by editing the line HOTPLUG_USE_SUBFS=yes in /etc/sysconfig/hotplug to HOTPLUG_USE_SUBFS=no
Then everything ought to work as it did in earlier versions of SuSE.
I followed your suggestion to the letter and no luck. In fact, when I tried to transfer an mp3, KDE crashed. Not just once, but 3 times! On the 3rd crash, I had to hit ctrl-alt-backspace to get everything to close. Of course, I had to re-log in as a result.
Any ideas as to what went wrong?
John Lamb wrote:
Matthew Dunaway wrote:
Hi, I have a Creative MuVo 64MB player. It worked fine with SuSE 9.0 but when I upgraded to 9.1 Pro, no luck. :-( Any ideas on how to get this to work with SuSE 9.1?? I really don't want to downgrade to 9.0 just to use the MuVo player.
I found that I could get a 128Mb MuVo to work by creating a directory (as root)
# mkdir /media/muvo
and putting the line
/dev/sda1 /media/muvo subfs fs=floppyfss,user,procuid,nodev,nosuid,sync 0 0
(one line)
into /etc/fstab.
The problem seems to be submount, which is new in 9.1. After I've done this, the device appears mounted correctly 15-20 seconds after inserting the device.
Occasionally, the device mounts itself as something like /media/USB... instead.
The problem seems to be submount. You can disable submount altogether by editing the line HOTPLUG_USE_SUBFS=yes in /etc/sysconfig/hotplug to HOTPLUG_USE_SUBFS=no
Then everything ought to work as it did in earlier versions of SuSE.
Matthew Dunaway wrote:
I followed your suggestion to the letter and no luck. In fact, when I tried to transfer an mp3, KDE crashed. Not just once, but 3 times! On the 3rd crash, I had to hit ctrl-alt-backspace to get everything to close. Of course, I had to re-log in as a result.
Any ideas as to what went wrong?
I guess the MuVo 64Mb really is different in some way to the MuVo 128Mb.
Did you try disabling submount. You should can do this in the YaST->System->/etc/sysconfig Editor under Hardware->hotplug->HOTPLUG_USE_SUBFS setting it to no. Then you'll need a line in /etc/fstab /dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0 (comment out with a # the old line)
You ought then to can mount the MuVo in the older method: at worst start a konsole and do $ mount /media/muvo You can probably still get a desktop item to do this.
It's a pity SuSE didn't make submount a bit more optional in 9.1.
John Lamb wrote:
Matthew Dunaway wrote:
I followed your suggestion to the letter and no luck. In fact, when I tried to transfer an mp3, KDE crashed. Not just once, but 3 times! On the 3rd crash, I had to hit ctrl-alt-backspace to get everything to close. Of course, I had to re-log in as a result.
Any ideas as to what went wrong?
I guess the MuVo 64Mb really is different in some way to the MuVo 128Mb.
Did you try disabling submount. You should can do this in the YaST->System->/etc/sysconfig Editor under Hardware->hotplug->HOTPLUG_USE_SUBFS setting it to no. Then you'll need a line in /etc/fstab /dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0 (comment out with a # the old line)
You ought then to can mount the MuVo in the older method: at worst start a konsole and do $ mount /media/muvo You can probably still get a desktop item to do this.
It's a pity SuSE didn't make submount a bit more optional in 9.1.
Well, I went toYAST->System->/etc/sysconfig Editor under Hardware->hotplug, and there is no entry called HOTPLUG_USE_SUBFS.
Now what can I do?
You need to run YOU and update hotplug to the .22 version. That will add teh HOTPLUG_USE_SUBFS entry.
Having said that, that version broke a couple of devices for me so I went back to the DVD version. Use with care :-)
On Mon, 13 Sep 2004 16:20:23 -0800, Matthew Dunaway fert@eagle.ptialaska.net wrote:
John Lamb wrote:
Matthew Dunaway wrote:
I followed your suggestion to the letter and no luck. In fact, when I tried to transfer an mp3, KDE crashed. Not just once, but 3 times! On the 3rd crash, I had to hit ctrl-alt-backspace to get everything to close. Of course, I had to re-log in as a result.
Any ideas as to what went wrong?
I guess the MuVo 64Mb really is different in some way to the MuVo 128Mb.
Did you try disabling submount. You should can do this in the YaST->System->/etc/sysconfig Editor under Hardware->hotplug->HOTPLUG_USE_SUBFS setting it to no. Then you'll need a line in /etc/fstab /dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0 (comment out with a # the old line)
You ought then to can mount the MuVo in the older method: at worst start a konsole and do $ mount /media/muvo You can probably still get a desktop item to do this.
It's a pity SuSE didn't make submount a bit more optional in 9.1.
Well, I went toYAST->System->/etc/sysconfig Editor under Hardware->hotplug, and there is no entry called HOTPLUG_USE_SUBFS.
Now what can I do?
-- To unsubscribe send e-mail to suse-multimedia-e-unsubscribe@suse.com For additional commands send e-mail to suse-multimedia-e-help@suse.com
Paul Howie wrote:
You need to run YOU and update hotplug to the .22 version. That will add teh HOTPLUG_USE_SUBFS entry.
Having said that, that version broke a couple of devices for me so I went back to the DVD version. Use with care :-)
Well, I updated hotplug to version .22 and still no luck. I am starting to think that SuSE 9.1 just doesn't like this MuVo 64. I am just about ready to give up on this mp3 player and just go ahead and buy one that works with SuSE. It's either that or downgrade to 9.0 but me thinks that's stupid just for the sake of an mp3 player. But, on the other hand, it would be cheaper than a new mp3 player.
What do you guys think??
You could dual boot to a minimal install of suse 9.0 and use that for the MuVo. A bit extreme though.
Personally I can't understand why it isn't working. What happens when you plug it in? Nothing or something odd?
On Tue, 14 Sep 2004 02:17:11 -0800, Matthew Dunaway fert@eagle.ptialaska.net wrote:
Paul Howie wrote:
You need to run YOU and update hotplug to the .22 version. That will add teh HOTPLUG_USE_SUBFS entry.
Having said that, that version broke a couple of devices for me so I went back to the DVD version. Use with care :-)
Well, I updated hotplug to version .22 and still no luck. I am starting to think that SuSE 9.1 just doesn't like this MuVo 64. I am just about ready to give up on this mp3 player and just go ahead and buy one that works with SuSE. It's either that or downgrade to 9.0 but me thinks that's stupid just for the sake of an mp3 player. But, on the other hand, it would be cheaper than a new mp3 player.
What do you guys think??
-- To unsubscribe send e-mail to suse-multimedia-e-unsubscribe@suse.com For additional commands send e-mail to suse-multimedia-e-help@suse.com
Nothing happens. :-(
Paul Howie wrote:
You could dual boot to a minimal install of suse 9.0 and use that for the MuVo. A bit extreme though.
Personally I can't understand why it isn't working. What happens when you plug it in? Nothing or something odd?
On Tue, 14 Sep 2004 02:17:11 -0800, Matthew Dunaway fert@eagle.ptialaska.net wrote:
Paul Howie wrote:
You need to run YOU and update hotplug to the .22 version. That will add teh HOTPLUG_USE_SUBFS entry.
Having said that, that version broke a couple of devices for me so I went back to the DVD version. Use with care :-)
Well, I updated hotplug to version .22 and still no luck. I am starting to think that SuSE 9.1 just doesn't like this MuVo 64. I am just about ready to give up on this mp3 player and just go ahead and buy one that works with SuSE. It's either that or downgrade to 9.0 but me thinks that's stupid just for the sake of an mp3 player. But, on the other hand, it would be cheaper than a new mp3 player.
What do you guys think??
-- To unsubscribe send e-mail to suse-multimedia-e-unsubscribe@suse.com For additional commands send e-mail to suse-multimedia-e-help@suse.com
.
Matthew Dunaway wrote:
Nothing happens. :-(
Hmmm. Check with YaST software installation. The installed version of hotplug should be 0.44-32.22 and not 0.44-32. If you've got the wrong version, you can always try downloading from
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/noarch/hotplug-0.44-32.22.noarch.rpm
and install with # rpm -Uvh hotplug-0.44-32.22.noarch.rpm
I decided to test all of this, just to see. The awkward bit is getting /etc/fstab right. The relevant lines for me are these #/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 #/dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 #/dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 #/dev/sda1 /media/muvo subfs fs=floppyfss,user,procuid,nodev,nosuid,sync 0 0 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0 (that's 8 lines, the first four are just the commented out old ones).
I did all that, rebooted (just to make sure and because I'm too lazy to check everything I might need without rebooting).
I did four times on my KDE desktop the following - Right click=>Create New=>Device=>CD-ROM DEVICE - once each for the DVD, CD-Recorder, Floppy and Muvo.
There are some nice new icons in 9.1!
It all works very well, dare I say it, better than submount. I can mount DVDs and CDs instantly, play music CDs, play DVD films (still with 5.1 sound :-) ). I haven't checked the floppy or checked that the camera still works.
I hope that helps.
OK, we might be getting somewhere. On my desktop, I have an icon for the MuVo. It has a little green arrow on it and it says it is mounted. :-)) When Iclicked on it to open it, I got the following message:
could not enter folder /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1
any ideas???
John Lamb wrote:
Matthew Dunaway wrote:
Nothing happens. :-(
Hmmm. Check with YaST software installation. The installed version of hotplug should be 0.44-32.22 and not 0.44-32. If you've got the wrong version, you can always try downloading from
ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/noarch/hotplug-0.44-32.22.noarch.rpm
and install with # rpm -Uvh hotplug-0.44-32.22.noarch.rpm
I decided to test all of this, just to see. The awkward bit is getting /etc/fstab right. The relevant lines for me are these #/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 #/dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 #/dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 #/dev/sda1 /media/muvo subfs fs=floppyfss,user,procuid,nodev,nosuid,sync 0 0 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0 (that's 8 lines, the first four are just the commented out old ones).
I did all that, rebooted (just to make sure and because I'm too lazy to check everything I might need without rebooting).
I did four times on my KDE desktop the following - Right click=>Create New=>Device=>CD-ROM DEVICE
- once each for the DVD, CD-Recorder, Floppy and Muvo.
There are some nice new icons in 9.1!
It all works very well, dare I say it, better than submount. I can mount DVDs and CDs instantly, play music CDs, play DVD films (still with 5.1 sound :-) ). I haven't checked the floppy or checked that the camera still works.
I hope that helps.
Matthew Dunaway wrote:
OK, we might be getting somewhere. On my desktop, I have an icon for the MuVo. It has a little green arrow on it and it says it is mounted. :-)) When Iclicked on it to open it, I got the following message:
could not enter folder /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1
any ideas???
If the line in /etc/fstab identifying the muvo is something like:
/dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0
then right-click the muvo icon and select properties. Under the device tag, select /dev/sda1 and it should list the mount point correctly, in my case as /media/muvo.
This is the traditional approach to mounting devices in GNU/Linux. It has the advantage of being fairly robust. The disadvantage is that you couldn't plug in a device without first telling the OS what it was, hence 'hotplug' (correctly 'plug and play').
IIRC, under SuSE 8.2, if you plugged in a USB memory stick, the USB hotplug system would put an entry in /etc/fstab for you, something like /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1. This isn't happening to me now and doesn't matter to me. I don't have any other USB devices that could use /dev/sda* and I want to mount the device with the sync option.
I haven't used suseplugger (the 'hardware' icon) much; so I don't know what it should do. It doesn't list the MuVo for me. If you find a MuVo listed, it may be that hotplugging is trying to mount the device automatically. In that case, you could try commenting out the line for /dev/sda1 in /etc/fstab and see what happens. Probably you will find the device under the /media subdirectory. OTOH, leaving a line for /dev/sda1 in /etc/fstab should not be a problem.
I guess this is an issue that will get sorted out in the next year or so. IMHO it's not an easy issue because there's no one right way to solve it. I think some devices are automatically detected others not. Some devices can be hotplugged, others not; some devices should be automounted, others not; some devices should be mounted 'sync', others not. Trying to get one system that works for everything is tough.
How would I comment out a line inetc/fstab?
John Lamb wrote:
Matthew Dunaway wrote:
OK, we might be getting somewhere. On my desktop, I have an icon for the MuVo. It has a little green arrow on it and it says it is mounted. :-)) When Iclicked on it to open it, I got the following message:
could not enter folder /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1
any ideas???
If the line in /etc/fstab identifying the muvo is something like:
/dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0
then right-click the muvo icon and select properties. Under the device tag, select /dev/sda1 and it should list the mount point correctly, in my case as /media/muvo.
This is the traditional approach to mounting devices in GNU/Linux. It has the advantage of being fairly robust. The disadvantage is that you couldn't plug in a device without first telling the OS what it was, hence 'hotplug' (correctly 'plug and play').
IIRC, under SuSE 8.2, if you plugged in a USB memory stick, the USB hotplug system would put an entry in /etc/fstab for you, something like /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1. This isn't happening to me now and doesn't matter to me. I don't have any other USB devices that could use /dev/sda* and I want to mount the device with the sync option.
I haven't used suseplugger (the 'hardware' icon) much; so I don't know what it should do. It doesn't list the MuVo for me. If you find a MuVo listed, it may be that hotplugging is trying to mount the device automatically. In that case, you could try commenting out the line for /dev/sda1 in /etc/fstab and see what happens. Probably you will find the device under the /media subdirectory. OTOH, leaving a line for /dev/sda1 in /etc/fstab should not be a problem.
I guess this is an issue that will get sorted out in the next year or so. IMHO it's not an easy issue because there's no one right way to solve it. I think some devices are automatically detected others not. Some devices can be hotplugged, others not; some devices should be automounted, others not; some devices should be mounted 'sync', others not. Trying to get one system that works for everything is tough.
put a # symbol in front of the line
On Wed, 15 Sep 2004 00:46:07 -0800, Matthew Dunaway fert@eagle.ptialaska.net wrote:
How would I comment out a line inetc/fstab?
John Lamb wrote:
Matthew Dunaway wrote:
OK, we might be getting somewhere. On my desktop, I have an icon for the MuVo. It has a little green arrow on it and it says it is mounted. :-)) When Iclicked on it to open it, I got the following message:
could not enter folder /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1
any ideas???
If the line in /etc/fstab identifying the muvo is something like:
/dev/sda1 /media/muvo auto noauto,user,exec,sync 0 0
then right-click the muvo icon and select properties. Under the device tag, select /dev/sda1 and it should list the mount point correctly, in my case as /media/muvo.
This is the traditional approach to mounting devices in GNU/Linux. It has the advantage of being fairly robust. The disadvantage is that you couldn't plug in a device without first telling the OS what it was, hence 'hotplug' (correctly 'plug and play').
IIRC, under SuSE 8.2, if you plugged in a USB memory stick, the USB hotplug system would put an entry in /etc/fstab for you, something like /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1. This isn't happening to me now and doesn't matter to me. I don't have any other USB devices that could use /dev/sda* and I want to mount the device with the sync option.
I haven't used suseplugger (the 'hardware' icon) much; so I don't know what it should do. It doesn't list the MuVo for me. If you find a MuVo listed, it may be that hotplugging is trying to mount the device automatically. In that case, you could try commenting out the line for /dev/sda1 in /etc/fstab and see what happens. Probably you will find the device under the /media subdirectory. OTOH, leaving a line for /dev/sda1 in /etc/fstab should not be a problem.
I guess this is an issue that will get sorted out in the next year or so. IMHO it's not an easy issue because there's no one right way to solve it. I think some devices are automatically detected others not. Some devices can be hotplugged, others not; some devices should be automounted, others not; some devices should be mounted 'sync', others not. Trying to get one system that works for everything is tough.
-- To unsubscribe send e-mail to suse-multimedia-e-unsubscribe@suse.com For additional commands send e-mail to suse-multimedia-e-help@suse.com
Just so I know - your MuVo thingy is it a USB device? It is anything more (to Linux) than a mass storage device?
Does the software you use with it have a config file? The rest of this email is wrtten vwnting off as if the sotware does, so if it hasn't, there's no need to read any further...
I have posted about USB before:
when I upgraded from 8.2 -> 9.0 a USB printer that was working, stopped
when I upgraded from 9.0 -> 9.1 it started working again
however a USB scanner that was working in 9.0 stopped working in 9.1 (I await 9.2)
both the device drivers, have config files, of course. For the scanner I did receive considerable advice from one person on this list but to no avail.
I've made my 2 pence suggestion before, to some derision, but I'll suggest again, that I think that some clerical or similar errors are creeping in between upgrades (not surprising in one sense this is a big impressive distro)
For example plustek.conf suggests that "device" should look like dev/usbscanner but now scanners are organised into /dev/usb/scanner0 ([1], [2], etc)
the plustek file had a line
device auto
which couldn't pick up the scanner (even though it had been detected by sane-find-scanner and during boot)
naturally I punted with replacing device auto with usb/scanner0 etc but to no avail
USB printers are similarly organised (and in 9.0 the command line example is the SUSE helpfile on usb printers worked for dev/usbprinter but not for dev/usb/printer)
On Tuesday 14 September 2004 11:26, Matthew Dunaway wrote:
Nothing happens. :-(
Paul Howie wrote:
You could dual boot to a minimal install of suse 9.0 and use that for the MuVo. A bit extreme though.
Personally I can't understand why it isn't working. What happens when you plug it in? Nothing or something odd?
On Tue, 14 Sep 2004 02:17:11 -0800, Matthew Dunaway
fert@eagle.ptialaska.net wrote:
Paul Howie wrote:
You need to run YOU and update hotplug to the .22 version. That will add teh HOTPLUG_USE_SUBFS entry.
Having said that, that version broke a couple of devices for me so I went back to the DVD version. Use with care :-)
Well, I updated hotplug to version .22 and still no luck. I am starting to think that SuSE 9.1 just doesn't like this MuVo 64. I am just about ready to give up on this mp3 player and just go ahead and buy one that works with SuSE. It's either that or downgrade to 9.0 but me thinks that's stupid just for the sake of an mp3 player. But, on the other hand, it would be cheaper than a new mp3 player.
What do you guys think??
-- To unsubscribe send e-mail to suse-multimedia-e-unsubscribe@suse.com For additional commands send e-mail to suse-multimedia-e-help@suse.com
.
Gerry Gavigan wrote:
Just so I know - your MuVo thingy is it a USB device? It is anything more (to Linux) than a mass storage device?
Does the software you use with it have a config file? The rest of this email is wrtten vwnting off as if the sotware does, so if it hasn't, there's no need to read any further...
A MuVo is a USB memory stick with an M$ file system. The stick is usually used to store MP3s and the like because it comes with an MP3 player. But essentially, it's just a mass storage device.
-
Gerry Gavigan -
John Lamb -
Matthew Dunaway -
Paul Howie