Re: [Cooker] supermount-ng
> I would like to know if you consider using supermount-ng in the > kernel of the next 9.2 ? Who are "you"? As a reminder, it is not official list representing Mandrake official position ... > obiwan (Danny Tholen) has built kernels available on Mandrakeclub > that use it, and it works well. A lot of bugs or strange behaviour > has been corrected, like the CDROM access for a couple of seconds > (even empty) each time I was using urpmq to look for a package. Pardon me, but this should have some other reasons, I assure you :) supermount-ng will access CD-ROM just the same as long as some applications does it. So most probably newer version of urpmi did fix this problem by not probing media now. You can "fix" it for "traditional" supermount as well by using sysctl -w dev.cdrom.autoclose=0 the CD-ROM access people are seeing is due to the fact that most IDE drives do not distinguish between no media and tray open and mostly return just tray open so driver tries to close tray and drive probes for media. you will have to close tray manually then of course -andrey
Re: [Cooker] supermount or alternate fs mounter ?
Does autofs work reliably with urpmi and removable media?
It didn't for me in 8.2. I did urpmi.removemedia for the 8.2 discs,
removed the cdrom mount point in fstab then urpmi.addmedia for each disc
(/misc/cd), but it would still configure for /mnt/cdrom. I could only
install packages by de-configuring autofs, reinstating the fstab entry and
manually mounting the cdrom. Eventually gave up using autofs for anything
but my camera. So I was very pleased to see that everything in 9.0 "just
works" (and so far has with no major problems).
--
Guy McArthur * email{[EMAIL PROTECTED]}
Re: [Cooker] supermount or alternate fs mounter ?
Alan Hughes wrote: The problem is that AFAIK other auto mounters are user-space applications that work by periodically checking to see if a mount point is no longer used, and if so then unmounting it. Typically this check occurs at 30 second intervals (although I understand that most allow you to configure this timeout). What this means in a practical sense is that your CD (as an example) would not be unmounted until 30 seconds after you finish using it. Supermount OTOH is a kernel utility that auomatically mounts the device when you access its mount point, and unmounts as soon as you've finished using it. It basically does this by hooking into various kernel routines responsible for managing the internal file descriptor tables. The problem with supermount is that these hooks are spread over a number of places and they often have very subtle impacts on the rest of the kernel (impacts that seem to change with each new kernel version) that tends to screw things up. A significant PITA. It would help if Linus integrated supermount into the kernel, however I understand that he is not happy with the necessary patches - given the problems which Mandrake has had I don't blame him. I'm not aware of anything else that does the same sort of job as supermount, but I think someone else posted something a couple of days ago. I'll need to have a look in the list archives to refresh my memory. Allright, I understand. Thanks for the explanation. Can we expect to have an update for 9.0 anyway ? Eric
Re: [Cooker] supermount or alternate fs mounter ?
The problem is that AFAIK other auto mounters are user-space applications that work by periodically checking to see if a mount point is no longer used, and if so then unmounting it. Typically this check occurs at 30 second intervals (although I understand that most allow you to configure this timeout). What this means in a practical sense is that your CD (as an example) would not be unmounted until 30 seconds after you finish using it. Supermount OTOH is a kernel utility that auomatically mounts the device when you access its mount point, and unmounts as soon as you've finished using it. It basically does this by hooking into various kernel routines responsible for managing the internal file descriptor tables. The problem with supermount is that these hooks are spread over a number of places and they often have very subtle impacts on the rest of the kernel (impacts that seem to change with each new kernel version) that tends to screw things up. A significant PITA. It would help if Linus integrated supermount into the kernel, however I understand that he is not happy with the necessary patches - given the problems which Mandrake has had I don't blame him. I'm not aware of anything else that does the same sort of job as supermount, but I think someone else posted something a couple of days ago. I'll need to have a look in the list archives to refresh my memory. - Original Message - From: "Eric Fernandez" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 29, 2002 11:28 AM Subject: Re: [Cooker] supermount or alternate fs mounter ? > Robert Denier wrote: > > >You may want to check this but I think > > > >supermount -i disable > > > >will magically change fstab to get rid of supermount options. (Remember if > >you mess up fstab your machine may not boot.) > > > >Clearly you now have to mount everything by hand, but considering I use a cd > >at most every few days, it really doesn't bother me, although thats just my > >case. > > > > > I know that you can disable supermount. But my point was for the future > updates/9.1. Mandrake distribution needs an auto-mounter, especially for > newbies and people who do not want to have to mount manually. Now the > question is : since there are alternatives to supermount, like autofs or > AMD (the BSD automounter), why not replace the problematic supermount by > another solution ? > > Eric > > >
Re: [Cooker] supermount or alternate fs mounter ?
Robert Denier wrote: You may want to check this but I think supermount -i disable will magically change fstab to get rid of supermount options. (Remember if you mess up fstab your machine may not boot.) Clearly you now have to mount everything by hand, but considering I use a cd at most every few days, it really doesn't bother me, although thats just my case. I know that you can disable supermount. But my point was for the future updates/9.1. Mandrake distribution needs an auto-mounter, especially for newbies and people who do not want to have to mount manually. Now the question is : since there are alternatives to supermount, like autofs or AMD (the BSD automounter), why not replace the problematic supermount by another solution ? Eric
RE: [Cooker] supermount or alternate fs mounter ?
You may want to check this but I think supermount -i disable will magically change fstab to get rid of supermount options. (Remember if you mess up fstab your machine may not boot.) Clearly you now have to mount everything by hand, but considering I use a cd at most every few days, it really doesn't bother me, although thats just my case. -Robert -Original Message- From: [EMAIL PROTECTED] [mailto:cooker-owner@;linux-mandrake.com]On Behalf Of Eric Fernandez Sent: Tuesday, October 29, 2002 12:42 AM To: [EMAIL PROTECTED] Subject: [Cooker] supermount or alternate fs mounter ? I don't know if it has been discussed here, but since there are so many problems with supermount, why to not use an alternative ? Like autofs ? Is there any technical reason to stick to supermount ? Eric
RE: Re: [Cooker] Supermount in MDK 9.0
I had the problem also with commercial cds, for example tuxracer or quake III. Francisco Alcaraz Murcia (Spain) - Mensaje Original - Remitente: James Sparenberg <[EMAIL PROTECTED]> Fecha: Jueves, Octubre 17, 2002 5:02 am Asunto: Re: [Cooker] Supermount in MDK 9.0 > On Tue, 2002-10-15 at 22:44, Joerg Skottke wrote: > > Palmer, Hilary wrote: > > > I loaded 9.0 on my system at home, but I noticed if I start > copying a lot of > > > data off of a CD, SuperMount seems to drop the CD. It will say > that it > > > doesn't have access to any of the files after the few that are > copied. Then > > > I need to eject and reinsert the CD to see anything on it again. > > > > > > If I do not use the SuperMount feature and mount the CD-ROM > manually it > > > works fine. > > > > > > Any ideas? > > > > Hi all, > > > > i can confirm this misbehavior on 3 different machines. This even > > happens when installing software from cd. Suddenly the files can > no > > longer be found and the installation fails (here: StarOffice 6.0) > > > > Joerg > > > > I'm only able to get this to happen on cd's that I've burned at a > higherspeed. Commercial CD's or ones I burn at 4x don't do this. > > James > > > >
Re: [Cooker] Supermount in MDK 9.0
On Tue, 2002-10-15 at 22:44, Joerg Skottke wrote: > Palmer, Hilary wrote: > > I loaded 9.0 on my system at home, but I noticed if I start copying a lot of > > data off of a CD, SuperMount seems to drop the CD. It will say that it > > doesn't have access to any of the files after the few that are copied. Then > > I need to eject and reinsert the CD to see anything on it again. > > > > If I do not use the SuperMount feature and mount the CD-ROM manually it > > works fine. > > > > Any ideas? > > Hi all, > > i can confirm this misbehavior on 3 different machines. This even > happens when installing software from cd. Suddenly the files can no > longer be found and the installation fails (here: StarOffice 6.0) > > Joerg > I'm only able to get this to happen on cd's that I've burned at a higher speed. Commercial CD's or ones I burn at 4x don't do this. James
Re: [Cooker] Supermount in MDK 9.0
Palmer, Hilary wrote: > I loaded 9.0 on my system at home, but I noticed if I start copying a lot of > data off of a CD, SuperMount seems to drop the CD. It will say that it > doesn't have access to any of the files after the few that are copied. Then > I need to eject and reinsert the CD to see anything on it again. > > If I do not use the SuperMount feature and mount the CD-ROM manually it > works fine. > > Any ideas? Hi all, i can confirm this misbehavior on 3 different machines. This even happens when installing software from cd. Suddenly the files can no longer be found and the installation fails (here: StarOffice 6.0) Joerg > > Thanks, > Hil > > > Confidentiality Notice > > This message is intended for the sole use of the individual and entity to > whom it is addressed, and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. Any > unauthorized review, use, disclosure or distribution of this email message, > including any attachment, is prohibited. If you are not the intended > recipient, please advise the sender by reply email and destroy all copies of > the original message. Thank you. > > > > -- *** Joerg Skottke Tel: +49 40 23646 - 631 Quality Assurance Engineer Fax: +49 40 23646 - 550 Star Office GmbH mailto:[EMAIL PROTECTED] Sachsenfeld 4 http://www.sun.com/staroffice D-20097 Hamburg
Re: [Cooker] Supermount in MDK 9.0
I am experiencing the disappearing drive problem. I perform an action on a file on the CDROM and suddenly that file just disappears. Supermount seems flakey all over again, but I haven't complained about it yet because I am experiencing problems higher on my agenda ... like 3D accelleration no longer works with ATI Rage Pro Mach 64. -George Mitchell aaron wrote: >I haven't seen the disappearing drive problem yet, but I have noticed >that supermounted CD's don't show up in "df" output anymore. Fine in 8.2. > > >
Re: [Cooker] Supermount in MDK 9.0
I haven't seen the disappearing drive problem yet, but I have noticed that supermounted CD's don't show up in "df" output anymore. Fine in 8.2. -- Aaron Peromsik <[EMAIL PROTECTED]> [For thinner oatmeal, add more water.]
Re: [Cooker] Supermount in MDK 9.0
Hello I saw that problem in my computer too. But i fix it with edit in /etc/fstab file. There isn't any /dev/sd0 file on /dev you must enter directly the /dev/hdx for it. like /dev/hdd for secondery slave cdrom.! >From: Götz Waschk <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Am Montag, 14. Oktober 2002, 08:33:36 Uhr MET, schrieb Palmer, Hilary: > > I loaded 9.0 on my system at home, but I noticed if I start copying a >lot of > > data off of a CD, SuperMount seems to drop the CD. It will say that it > > doesn't have access to any of the files after the few that are copied. >Then > > I need to eject and reinsert the CD to see anything on it again. > >This is a known problem. I wonder why it's not included in the 9.0 errata. > > > If I do not use the SuperMount feature and mount the CD-ROM manually it > > works fine. >That's what I also did and what I recommend to everone using Mandrake 9.0. >-- >Götz Waschk <> master of computer science <> University of Rostock > http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key > --> Logout Fascism! <-- __USTA__ [EMAIL PROTECTED] icq# 10254358 See You Later _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: [Cooker] Supermount in MDK 9.0
On Monday 14 October 2002 14:33, Palmer, Hilary wrote: > I loaded 9.0 on my system at home, but I noticed if I start copying a lot > of data off of a CD, SuperMount seems to drop the CD. It will say that it > doesn't have access to any of the files after the few that are copied. > Then I need to eject and reinsert the CD to see anything on it again. > > If I do not use the SuperMount feature and mount the CD-ROM manually it > works fine. > Yes, supermount is knackered (f*cked) in 9.0. Hopefully we will soon have a new kernel rpm with the offending patches removed/fixed. You can use autofs to cahieve a similar effect, but the default 60 second timeout is too long, also pressing the eject button does not work unless autofs has already unmounted the media. > Any ideas? > > Thanks, > Hil > > > Confidentiality Notice > > This message is intended for the sole use of the individual and entity to > whom it is addressed, and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. Any > unauthorized review, use, disclosure or distribution of this email message, > including any attachment, is prohibited. If you are not the intended > recipient, please advise the sender by reply email and destroy all copies > of the original message. Thank you. ** The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. This message and any attachments have been scanned for viruses. Orbiscom Ltd. will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. www.Orbiscom.com **
RE: [Cooker] Supermount in MDK 9.0
OK... Thanks -Original Message- From: Götz Waschk [mailto:[EMAIL PROTECTED]] Sent: Monday, October 14, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: [Cooker] Supermount in MDK 9.0 Am Montag, 14. Oktober 2002, 08:33:36 Uhr MET, schrieb Palmer, Hilary: > I loaded 9.0 on my system at home, but I noticed if I start copying a lot of > data off of a CD, SuperMount seems to drop the CD. It will say that it > doesn't have access to any of the files after the few that are copied. Then > I need to eject and reinsert the CD to see anything on it again. This is a known problem. I wonder why it's not included in the 9.0 errata. > If I do not use the SuperMount feature and mount the CD-ROM manually it > works fine. That's what I also did and what I recommend to everone using Mandrake 9.0. -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <-- Confidentiality Notice This message is intended for the sole use of the individual and entity to whom it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure or distribution of this email message, including any attachment, is prohibited. If you are not the intended recipient, please advise the sender by reply email and destroy all copies of the original message. Thank you.
Re: [Cooker] Supermount in MDK 9.0
Am Montag, 14. Oktober 2002, 08:33:36 Uhr MET, schrieb Palmer, Hilary: > I loaded 9.0 on my system at home, but I noticed if I start copying a lot of > data off of a CD, SuperMount seems to drop the CD. It will say that it > doesn't have access to any of the files after the few that are copied. Then > I need to eject and reinsert the CD to see anything on it again. This is a known problem. I wonder why it's not included in the 9.0 errata. > If I do not use the SuperMount feature and mount the CD-ROM manually it > works fine. That's what I also did and what I recommend to everone using Mandrake 9.0. -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
Re: [Cooker] supermount?
> "L" == Lonnie Borntreger <[EMAIL PROTECTED]> writes: L> On Wed, 2002-10-09 at 14:16, Mario Vazquez wrote: >> There is a fix for supermount on cooker mirrors? L> Yes. It's called autofs. Please explain: "Autofs can also be used to manage file systems on removable media, but Anvin considers this to be more "abuse than use," since autofs is not designed for that purpose. http://www.linuxworld.com/linuxworld/expo/lw-wednesday-autofs.html -- Gary Lawrence Murphy - [EMAIL PROTECTED] - TeleDynamics Communications - blog: http://www.auracom.com/~teledyn - biz: http://teledyn.com/ - "Computers are useless. They can only give you answers." (Picasso)
Re: [Cooker] supermount?
On Wed, 2002-10-09 at 14:16, Mario Vazquez wrote: > There is a fix for supermount on cooker mirrors? Yes. It's called autofs. TTFN, Lonnie Borntreger
Re: [Cooker] supermount?
Mario Vazquez wrote on Wed, Oct 09, 2002 at 03:16:02PM -0400 : > There is a fix for supermount on cooker mirrors? When you see a new version of the kernel come down, that's when you try it. Look through the changelog to see if anything is noted about it. Blue skies... Todd -- ...and I will strike down upon thee with great vengeance and furious anger, those who attempt to poison and destroy my binaries, and you will know my name is root, when I lay my vengeance upon thee. Cooker Version mandrake-release-9.1-0.1mdk Kernel 2.4.19-16mdk msg78630/pgp0.pgp Description: PGP signature
Re: [Cooker] Supermount Problem: Serious?
I have the same problem with "No such file or directory" errors when copying
or just reading from my DVD-ROM drive.
Reading or copying files from my CD writer, which is using the ide-scsi
kernel module, seems to work fine. However, I have not fully tested this
theory.
I also receive an error:
kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete
Error }
kernel: hdc: cdrom_decode_status: error=0x40
I assume "/dev/hdc" (my DVD-ROM drive) is using the ide-cd module.
I might try making /dev/hdc use the ide-scsi module.
Hope this helps,
Tim
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
Re: [Cooker] Supermount Problem: Serious?
James Sparenberg wrote on Tue, Oct 01, 2002 at 12:00:29AM -0700 : > > Cd /mnt/cdrom/some_directory as a user su to root do some work. > eject the cdrom put in a new one. Quite often the new one is > unreadable. ie Understandable. The problem is that the eject should fail with an unable to unmount, IMHO. If you want to see what I mean, open a terminal right now, su to root, and then type 'umount /home': [root@trip todd]# umount /home umount: /home: device is busy That's what supermount should report since the regular user you su'd from is still in that directory. > directory Mandrake not found. Yes, everything in memory at this point is fubar'd because the media got removed out from under it. > Obvious question is since I only did an ls why or rather how did it know > about a directory mandrake. Now i exit the su ... it immediately drops > back to by user. IN a directory on the previously removed CD.(even > though that tree no longer exists.) In fact sometimes if I do an ls it > has even given me the files in the directory of the removed CD. (Not > always repeatable) A similar scenario is if I do: [todd@trip todd]$ mkdir test1 [todd@trip todd]$ cd test1 [todd@trip test1]$ mkdir test2 [todd@trip test1]$ cd test2 [todd@trip test2]$ pwd /home/todd/test1/test2 [todd@trip test2]$ su Password: [root@trip test2]# cd ../.. [root@trip todd]# rm -rf test1 [root@trip todd]# exit exit [todd@trip test2]$ pwd /home/todd/test1/test2 [todd@trip test2]$ ls [todd@trip test2]$ cd .. cd: could not get current directory: getcwd: cannot access parent directories: No such file or directory cd: could not get current directory: getcwd: cannot access parent directories: No such file or directory [todd@trip .]$ pwd pwd: could not get current directory: getcwd: cannot access parent directories: No such file or directory [todd@trip .]$ cd .. chdir: could not get current directory: getcwd: cannot access parent directories: No such file or directory [todd@trip ..]$ cd .. [todd@trip ..]$ ls bin/ dev/ home/lib/ opt/ root/ tmp/ var/ boot/ etc/ initrd/ mnt/ proc/ sbin/ usr/ [todd@trip ..]$ ls bin/ dev/ home/lib/ opt/ root/ tmp/ var/ boot/ etc/ initrd/ mnt/ proc/ sbin/ usr/ [todd@trip ..]$ pwd ../.. [todd@trip ..]$ cd / [todd@trip /]$ ls So removing the media out from under the user is similar to removing directories out from under the user (but not identical). It's pretty much fatal. Luckily in the above example, I could always just "cd /" and it took care of the issues that bash was having. But it's not that simple with supermount. Keep in mind that I know very little about supermount. Saying that I'm studying it is a lot like saying I'm studying the Theory of Relativity to make enhancements. It sounds really impressive, but it doesn't mean that it will ever happen (by my hand at least :) Rather, I'm looking at the code, trying to understand what it does. Someone like Juan knows that code much better and is able to read into the errors. Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg77824/pgp0.pgp Description: PGP signature
Re: [Cooker] supermount and usb-uhci
I have got also problems downloading pictures from my usb camera (canon powershot a40). The camera is correctly set up and I can access the image directory with konqueror. But sometimes it hangs during the copy and I have to do it again. Eric Borzenkov Andrey wrote: >I am really sorry but from your description it appears not related >directly to supermount. I do not know anything about flashcards, sorry >:( > > > >>Could this supermount error be related to the problems I am having >>with supermount and the usb-uhci/sr_mod loaded Flash memory-card >>reader? >> >>When I try to use the Flash card with supermount >> >> none /mnt/flash supermount dev=/dev/sda1,fs=vfat,user,noauto 0 0 >> >>it reads a few files and then hangs. >>
RE: [Cooker] supermount and usb-uhci
I am really sorry but from your description it appears not related directly to supermount. I do not know anything about flashcards, sorry :( > > Could this supermount error be related to the problems I am having > with supermount and the usb-uhci/sr_mod loaded Flash memory-card > reader? > > When I try to use the Flash card with supermount > >none /mnt/flash supermount dev=/dev/sda1,fs=vfat,user,noauto 0 0 > > it reads a few files and then hangs. > > It may also be an issue with interrupts -- the drive will lock up if I > use non-supermount fstab user-mount statements -- to use the Flash > card with LM9.0, I must disable (rmmod) my CD-RW drive support and > vice-versa, to use my CDRW, I must rmmod the usb-uhci and sr_mod > (which kills the mouse until a reboot) ... the two devices will not > co-exist. There were no problems with either device under LM8.2 > > If it helps, here's what I get in my log. The interrupt status > messages continue until I pop the Flash card, resetting the device. > > > Sep 22 13:30:23 maya kernel: usb.c: USB device 5 (vend/prod 0x5dc/0x2) is > not claimed by any active driver. > Sep 22 13:30:28 maya /etc/hotplug/usb.agent: Setup usb-storage for USB > product 5dc/2/1 > Sep 22 13:30:28 maya kernel: usb.c: registered new driver usb-storage > Sep 22 13:30:30 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1753 > Sep 22 13:30:33 maya kernel: usb_control/bulk_msg: timeout > Sep 22 13:31:04 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1524 > Sep 22 13:31:10 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1436 > Sep 22 13:31:16 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1340 > ... > Sep 22 13:31:22 maya kernel: usb.c: USB disconnect on device 5 > Sep 22 13:31:22 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1221 > Sep 22 13:31:29 maya /etc/hotplug/usb.agent: Setup usb-storage for USB > product 5dc/2/1 > Sep 22 13:34:14 maya kernel: usb-uhci.c: interrupt, status 2, frame# 692 > Sep 22 13:34:20 maya kernel: usb-uhci.c: interrupt, status 2, frame# 596 > Sep 22 13:34:26 maya kernel: usb-uhci.c: interrupt, status 2, frame# 500 > ... > Sep 22 13:35:04 maya kernel: usb-uhci.c: $Revision: 1.275 $ time 07:51:45 > Aug 30 2002 > Sep 22 13:35:04 maya kernel: usb-uhci.c: High bandwidth mode enabled > Sep 22 13:35:04 maya kernel: usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 9 > Sep 22 13:35:04 maya kernel: usb-uhci.c: Detected 2 ports > Sep 22 13:35:04 maya kernel: usb.c: new USB bus registered, assigned bus > number 1 > Sep 22 13:35:04 maya kernel: usb-uhci.c: v1.275:USB Universal Host > Controller Interface driver > Sep 22 13:35:04 maya usb: Loading USB interface0 (usb-uhci usb-uhci) > succeeded > Sep 22 13:35:06 maya kernel: input0: USB HID v1.00 Mouse [Logitech USB- > PS/2 Trackball] on usb1:3.0 > Sep 22 13:35:06 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1756 > Sep 22 13:35:06 maya kernel: usb.c: USB device not accepting new address=4 > (error=-110) > Sep 22 13:35:10 maya /etc/hotplug/usb.agent: ... no modules for USB > product 0/0/0 > Sep 22 13:35:10 maya /etc/hotplug/usb.agent: ... no modules for USB > product 4cc/1122/110 > Sep 22 13:35:11 maya /etc/hotplug/usb.agent: Setup usbmouse hid for USB > product 46d/c402/210 > Sep 22 13:35:11 maya /etc/hotplug/usb.agent: Setup mousedev for USB > product 46d/c402/210 > Sep 22 13:35:12 maya /etc/hotplug/usb.agent: Setup se401 for USB product > 471/30b/2036 > Sep 22 13:35:12 maya /etc/hotplug/usb.agent: Setup usb-storage for USB > product 5dc/2/1 > Sep 22 13:35:43 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1818 > Sep 22 13:35:46 maya kernel: usb_control/bulk_msg: timeout > Sep 22 13:35:50 maya kernel: usb_control/bulk_msg: timeout > Sep 22 13:35:50 maya kernel: usb-uhci.c: interrupt, status 2, frame# 942 > Sep 22 13:35:53 maya kernel: usb_control/bulk_msg: timeout > Sep 22 13:38:41 maya kernel: usb.c: registered new driver usbdevfs > Sep 22 13:38:41 maya kernel: usb.c: registered new driver hub > > > -- > Gary Lawrence Murphy - [EMAIL PROTECTED] - TeleDynamics Communications > - blog: http://www.auracom.com/~teledyn - biz: http://teledyn.com/ - > "Computers are useless. They can only give you answers." (Picasso)
RE: Re: [Cooker] Supermount Problem: Serious?
Luis,
Could you be so kind as explains us in detail how do you have setuped
autofs?
Thanks so much in advance
Francisco Alcaraz
Murcia (Spain)
- Mensaje Original -
Remitente: "Luis M" <[EMAIL PROTECTED]>
Fecha: Martes, Octubre 1, 2002 2:59 am
Asunto: Re: [Cooker] Supermount Problem: Serious?
>
> Just in case, I disable supermount for both of my cdroms... instead
> I setup
> autofs in /misc . Thus now, ls /misc/cdrom brings my CDs just fine.
> I always
> wonder why the need for supermount if autofs does the same ...
>
> In any case, maybe it's because of supermount that I cannot restart
> my
> computer. Everytime I do it says something about mount2 trying to
> umount
> something else and then the init says something about no more
> processes left
> in this run level and it stays there forever...
> I saw this error before with 8.2, I just don't remember what I did
> to fix
> it. And this happens to me on two completely different boxes. My
> workstation
> at work and the one I use at home. I reported this before but,
> nobody ever
> said anything; thus I assume that either no body ever reboots their
> computers or this is an isolated case and it only happens to me...
> @#$@#%
> I'm sure supermount or autofs have something to do with it... let
> me start
> the rebooting tests now :-) ...
>
> >From: John Allen <[EMAIL PROTECTED]>
>
> >This is definitely a supermount problem. Manually mounting works
> perfect..
> >I have this problem on all my cooker, and 9.0 machines. Tried
> 2.4.19-12mdk
> >and it fails also.
> >
> >Luis M wrote:
> >
> >>
> >>
> >>That usually means a bad burn. Do this:
> >>
> >>make sure that your ISO's have the right md5sum:
> >>
> >>f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso
> >>05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso
> >>1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso
> >>
> >>To check the md5sum:
> >>$> md5sum FILE.iso
> >>
> >>After you do that, then mount the ISO's to a directory (as root
> do this
> >>for the CD's you are having problems with):
> >>
> >>#> mount -t iso9660 -o loop FILE.iso /mnt/test
> >>
> >>Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried
> before... if
> >>this works fine (it should if the md5sum matched and your loop
> devices
> >>and hard drive work fine...), then try burning your disk at a
> lower speed
> >>than your burner supports -- burning at 8x is better than at any
> other
> >>speed if you have the time to wait until it finishes and use
> cheap blank
> >>disks.
> >>
> >>I have seen that problem you mentioned before and I'm sure is
> just a bad
> >>burn because after burning the disks at two steps slower than my
> writer
> >>supports, the disks worked fine.
> >>
> >>Sample session here:
> >>
> >>$> du -s /mnt/iso2/Mandrake/RPMS2/
> >>698M/mnt/iso2/Mandrake/RPMS2
> >>$> mkdir /mnt/backup/test
> >>$> cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test
> >>$>
> >>
> >>You can see that the iso's are fine...
> >>
> >>
> >>
> >>>From the CarshTesters List:
> >>>
> >>>
> >>> Date
> >>> 29 Sep 2002 12:25
> >>>
> >>>
> >>> Subject
> >>> Re: [CrashTesters] 9.0 Supermount nightmare
> >>>
> >>>
> >>>
> >>>On 29 Sep 2002 12:09 CDT you wrote:
> >>>
> >>> > On 29 Sep 2002 06:24 CDT you wrote:
> >>> >
> >>> > > Dear friends,
> >>> > > I am having lot of problems with supermount in 9.0:
> >>> > >
> >>> > > 1- With supermount enabled, when I try to copy several
> files
> >>>sometimes,
> >>> > > after few minutes, some of the files in the cdrom are not
> recognized>>> > > ("the file Toshiba... is not valid).
> >>> > >
> >>> > > 2. I have dissabled supermount in my dvd-drive; now I can
> mount and
> >>> > > umount as a user, the problem of files dissapearing is
> solved, but
> >>>when
> >>> > > Mandrake start ther is an error message: Fault: mount
> device not
> >>>found.
> >>> > > To eli
Re: [Cooker] Supermount Problem: Serious?
On Sun, 2002-09-29 at 13:24, John Allen wrote: > [EMAIL PROTECTED] wrote: > > >On Sun, 29 Sep 2002, Steven Spears wrote: > > > > > Mandrake start ther is an error message: Fault: mount device not found. > > > >I think you need to remove 'auto' and set 'noauto' in the responsible > >fstab line. Otherwise system will try to mount the empty drive, which > >will fail ofcourse. It is not a real bad problem is it? > > > > > > > >>Ran the test and sure enough, I get the same error as well. I opened the > >> > >> > > > > > > > >>and hope this helps. As anyone mentioned this on the cooker list? > >> > >> > > > >I think I saw it before. But IMHO (and others) supermount is just > >hopeless. And it has more problems than only the above. > >Anyone with a bit C experience should throw himself on improving > >Alan Cox' volumagic, so that we can do automounting in userspace. > >Hopefully I will try during Xmas holidays. But I never did something more > >serious than some easy gui programs, so do not hold your breath:) > > > > > >Danny > > > > > > > > > I have a really serious problem with supermount. I have created a DVD of > 9.0, which I cannot copy to my hard disk if /mnt/cdrom is supermounted. > It manages to copy maybe 20% then cannot open (stat) any files on the > DVD, not even from the command line. If I disable supermount and > manually mount the DVD it all works OK. (The option to manually > mount/unmount is gone from the CD-ROM popup menu in KDE so had to use > the mount comamnd directly) > > PS: This does not just hapen on one machine. > Don't know if this will help but I found one thing Scenario Cd /mnt/cdrom/some_directory as a user su to root do some work. eject the cdrom put in a new one. Quite often the new one is unreadable. ie cd /mnt/cdrom ls directory Mandrake not found. Obvious question is since I only did an ls why or rather how did it know about a directory mandrake. Now i exit the su ... it immediately drops back to by user. IN a directory on the previously removed CD.(even though that tree no longer exists.) In fact sometimes if I do an ls it has even given me the files in the directory of the removed CD. (Not always repeatable) Don't know if any of this will help... hope it does. James > >
Re: [Cooker] Supermount Problem: Serious?
Just in case, I disable supermount for both of my cdroms... instead I setup
autofs in /misc . Thus now, ls /misc/cdrom brings my CDs just fine. I always
wonder why the need for supermount if autofs does the same ...
In any case, maybe it's because of supermount that I cannot restart my
computer. Everytime I do it says something about mount2 trying to umount
something else and then the init says something about no more processes left
in this run level and it stays there forever...
I saw this error before with 8.2, I just don't remember what I did to fix
it. And this happens to me on two completely different boxes. My workstation
at work and the one I use at home. I reported this before but, nobody ever
said anything; thus I assume that either no body ever reboots their
computers or this is an isolated case and it only happens to me... @#$@#%
I'm sure supermount or autofs have something to do with it... let me start
the rebooting tests now :-) ...
>From: John Allen <[EMAIL PROTECTED]>
>This is definitely a supermount problem. Manually mounting works perfect..
>I have this problem on all my cooker, and 9.0 machines. Tried 2.4.19-12mdk
>and it fails also.
>
>Luis M wrote:
>
>>
>>
>>That usually means a bad burn. Do this:
>>
>>make sure that your ISO's have the right md5sum:
>>
>>f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso
>>05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso
>>1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso
>>
>>To check the md5sum:
>>$> md5sum FILE.iso
>>
>>After you do that, then mount the ISO's to a directory (as root do this
>>for the CD's you are having problems with):
>>
>>#> mount -t iso9660 -o loop FILE.iso /mnt/test
>>
>>Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if
>>this works fine (it should if the md5sum matched and your loop devices
>>and hard drive work fine...), then try burning your disk at a lower speed
>>than your burner supports -- burning at 8x is better than at any other
>>speed if you have the time to wait until it finishes and use cheap blank
>>disks.
>>
>>I have seen that problem you mentioned before and I'm sure is just a bad
>>burn because after burning the disks at two steps slower than my writer
>>supports, the disks worked fine.
>>
>>Sample session here:
>>
>>$> du -s /mnt/iso2/Mandrake/RPMS2/
>>698M/mnt/iso2/Mandrake/RPMS2
>>$> mkdir /mnt/backup/test
>>$> cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test
>>$>
>>
>>You can see that the iso's are fine...
>>
>>
>>
>>>From the CarshTesters List:
>>>
>>>
>>> Date
>>> 29 Sep 2002 12:25
>>>
>>>
>>> Subject
>>> Re: [CrashTesters] 9.0 Supermount nightmare
>>>
>>>
>>>
>>>On 29 Sep 2002 12:09 CDT you wrote:
>>>
>>> > On 29 Sep 2002 06:24 CDT you wrote:
>>> >
>>> > > Dear friends,
>>> > > I am having lot of problems with supermount in 9.0:
>>> > >
>>> > > 1- With supermount enabled, when I try to copy several files
>>>sometimes,
>>> > > after few minutes, some of the files in the cdrom are not recognized
>>> > > ("the file Toshiba... is not valid).
>>> > >
>>> > > 2. I have dissabled supermount in my dvd-drive; now I can mount and
>>> > > umount as a user, the problem of files dissapearing is solved, but
>>>when
>>> > > Mandrake start ther is an error message: Fault: mount device not
>>>found.
>>> > > To eliminate the message is enought activating again supermount to
>>>that
>>> > > drive.
>>> > >
>>> > > There you have my fstab file; I have to harddisks (hda with two vfat
>>> > > partitions and two xfs partitions; and hdb with the main linux
>>>paritions
>>> > >
>>> > > /dev/hdb5 / ext3 defaults 1 1
>>> > > /dev/hdb1 /boot ext3 defaults 1 2
>>> > > none /dev/pts devpts mode=0620 0 0
>>> > > /dev/hdb7 /disk xfs defaults 1 2
>>> > > /dev/hdb8 /home xfs defaults 1 2
>>> > > /dev/hdd /mnt/cdrom2 auto
>>> > > user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0
>>> > > none /mnt/floppy supermount
>>> > >
>>>dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0 0
>>>0
>>> > > /dev/hda1 /mnt/win_c vfat iocharset=iso8859-15,codepage=850,umask=0
>>>0 0
>>> > > /dev/hda5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0
>>>0 0
>>> > > /dev/hdb13 /object xfs defaults 1 2
>>> > > /dev/hda7 /otros xfs defaults 1 2
>>> > > /dev/hda6 /pelis xfs defaults 1 2
>>> > > none /proc proc defaults 0 0
>>> > > /dev/hdb11 /tmp xfs defaults 1 2
>>> > > /dev/hdb6 /usr xfs defaults 1 2
>>> > > /dev/hdb9 /usr/share ext3 defaults 1 2
>>> > > /dev/hdb10 /var xfs defaults 1 2
>>> > > none mnt/cdrom supermount
>>> > >
>>>dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0
>>> > > /dev/hdb12 swap swap defaults 0 0
>>> > >
>>> > >
>>> > > Ah!; in my laptop the problem also appears.
>>> > >
>>> > > Any idea about where the problem arises and how can it bee solved?
>>> > >
>>> > > Thanks so much in advance
>>> > >
>>> > >
>>> > > Francisco Alcaraz
>>> > > Murcia (Spain)
>>> > >
>>> > >
>>> > >
Re: [Cooker] supermount and usb-uhci
Hi, Am Mon, 2002-09-30 um 18.06 schrieb Gary Lawrence Murphy: > > Could this supermount error be related to the problems I am having > with supermount and the usb-uhci/sr_mod loaded Flash memory-card > reader? > > When I try to use the Flash card with supermount > >none /mnt/flash supermount dev=/dev/sda1,fs=vfat,user,noauto 0 0 > > it reads a few files and then hangs. > > It may also be an issue with interrupts -- the drive will lock up if I > use non-supermount fstab user-mount statements -- to use the Flash > card with LM9.0, I must disable (rmmod) my CD-RW drive support and > vice-versa, to use my CDRW, I must rmmod the usb-uhci and sr_mod > (which kills the mouse until a reboot) ... the two devices will not I have had the same problem with my usb mouse. But there is an easier way to relife the mouse. You could # rmmod usb-uhci and then # modprobe usb-uhci After this small "hack" the mouse will work. Hope there will be someone who will solve the supermount problem. Bye, Michael
Re: [Cooker] Supermount Problem: Serious?
This is definitely a supermount problem. Manually mounting works
perfect.. I have this problem on all my cooker, and 9.0 machines. Tried
2.4.19-12mdk and it fails also.
Luis M wrote:
>
>
> That usually means a bad burn. Do this:
>
> make sure that your ISO's have the right md5sum:
>
> f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso
> 05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso
> 1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso
>
> To check the md5sum:
> $> md5sum FILE.iso
>
> After you do that, then mount the ISO's to a directory (as root do
> this for the CD's you are having problems with):
>
> #> mount -t iso9660 -o loop FILE.iso /mnt/test
>
> Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried
> before... if this works fine (it should if the md5sum matched and
> your loop devices and hard drive work fine...), then try burning your
> disk at a lower speed than your burner supports -- burning at 8x is
> better than at any other speed if you have the time to wait until it
> finishes and use cheap blank disks.
>
> I have seen that problem you mentioned before and I'm sure is just a
> bad burn because after burning the disks at two steps slower than my
> writer supports, the disks worked fine.
>
> Sample session here:
>
> $> du -s /mnt/iso2/Mandrake/RPMS2/
> 698M/mnt/iso2/Mandrake/RPMS2
> $> mkdir /mnt/backup/test
> $> cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test
> $>
>
> You can see that the iso's are fine...
>
>
>
>> From the CarshTesters List:
>>
>>
>> Date
>> 29 Sep 2002 12:25
>>
>>
>> Subject
>> Re: [CrashTesters] 9.0 Supermount nightmare
>>
>>
>>
>> On 29 Sep 2002 12:09 CDT you wrote:
>>
>> > On 29 Sep 2002 06:24 CDT you wrote:
>> >
>> > > Dear friends,
>> > > I am having lot of problems with supermount in 9.0:
>> > >
>> > > 1- With supermount enabled, when I try to copy several files
>> sometimes,
>> > > after few minutes, some of the files in the cdrom are not recognized
>> > > ("the file Toshiba... is not valid).
>> > >
>> > > 2. I have dissabled supermount in my dvd-drive; now I can mount and
>> > > umount as a user, the problem of files dissapearing is solved,
>> but when
>> > > Mandrake start ther is an error message: Fault: mount device not
>> found.
>> > > To eliminate the message is enought activating again supermount
>> to that
>> > > drive.
>> > >
>> > > There you have my fstab file; I have to harddisks (hda with two vfat
>> > > partitions and two xfs partitions; and hdb with the main linux
>> paritions
>> > >
>> > > /dev/hdb5 / ext3 defaults 1 1
>> > > /dev/hdb1 /boot ext3 defaults 1 2
>> > > none /dev/pts devpts mode=0620 0 0
>> > > /dev/hdb7 /disk xfs defaults 1 2
>> > > /dev/hdb8 /home xfs defaults 1 2
>> > > /dev/hdd /mnt/cdrom2 auto
>> > > user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0
>> > > none /mnt/floppy supermount
>> > >
>> dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0
>> 0 0
>> > > /dev/hda1 /mnt/win_c vfat
>> iocharset=iso8859-15,codepage=850,umask=0 0 0
>> > > /dev/hda5 /mnt/win_d vfat
>> iocharset=iso8859-15,codepage=850,umask=0 0 0
>> > > /dev/hdb13 /object xfs defaults 1 2
>> > > /dev/hda7 /otros xfs defaults 1 2
>> > > /dev/hda6 /pelis xfs defaults 1 2
>> > > none /proc proc defaults 0 0
>> > > /dev/hdb11 /tmp xfs defaults 1 2
>> > > /dev/hdb6 /usr xfs defaults 1 2
>> > > /dev/hdb9 /usr/share ext3 defaults 1 2
>> > > /dev/hdb10 /var xfs defaults 1 2
>> > > none mnt/cdrom supermount
>> > >
>> dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0
>> 0 0
>> > > /dev/hdb12 swap swap defaults 0 0
>> > >
>> > >
>> > > Ah!; in my laptop the problem also appears.
>> > >
>> > > Any idea about where the problem arises and how can it bee solved?
>> > >
>> > > Thanks so much in advance
>> > >
>> > >
>> > > Francisco Alcaraz
>> > > Murcia (Spain)
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > I will run a test on this now and see what my results are.
>> >
>> > Steve Spears
>>
>> Ran the test and sure enough, I get the same error as well. I opened the
>> CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then
>> I did a
>> mass select in the RPMS2 directory and drug them into the new test
>> directory.
>> The copy started off fine but then cam up with the error that certain
>> files
>> didn't exist. I clicked auto skip to see what would happened. It went
>> on for
>> a little bit and then just stopped.
>>
>> I looked in the test directory that I created and there were only a
>> few files
>> in there. When I went back into the CD-ROM/Mandrake/RPMS2 via
>> Konqueror it
>> was showing only one file. enlightenment.
>>
>> Being curious, I went to a konsole and did the followign:
>>
>> [wriker@riker wriker]$ cd /mnt/cdrom
>> [wriker@riker cdrom]$ ls
>> ls: Boot: No such file or directory
>> Mandrake/
>> [wriker@riker cdrom]$ cd Mandrake/
>> [wriker@riker Mandrake]$ ls
>> RPMS2/
>> [wriker@riker Mandrake]$ cd RPMS2/
>> [wriker@ri
Re: [Cooker] supermount
I would be much happier with a 2.4.19-13mdk that fixed supermount for CD-ROMs, and did not enable supermount for floppies. The vast majority of people I know hardly ever use a floppy. a number of people even have built machines without floppy drives. Supermounting the CD with this bug makes the machine totally useless; and explaining manual mounting to my converted friends will scare the hell out of them. [EMAIL PROTECTED] wrote: >Danny > >Really I haven't seen supermount runing perfectly under 2.4; so, as you >say, is a good idea take in account other possibilities (Volumagic?) for >the future. Anyway I am according to you in the need of change the >default in 9.0 enabling, or, if it is not possible in the final >distribution, adding the solution in "errata". > >Francisco Alcaraz >Murcia (Spain) > > > >- Mensaje Original - >Remitente: <[EMAIL PROTECTED]> >Fecha: Lunes, Septiembre 30, 2002 5:13 pm >Asunto: [Cooker] supermount > > > >>I feel a bit responsible for the current state of supermount, since >>I >>talked Juan into fixing floppy-write-PANIC issues, which seems to >>have >>utterly broken supermount for CDROMS in the released 9.0 kernel. >> >>A simple 'find' in /mnt/cdrom will probably reveal what I'm talking >>about >>(half the files cannot be stat-ed). In addition, there is the >>problem of >>non-freeing inodes on zips and floppies. >> >>Juan, Andrey and probably others, did a great job on patching up >>supermount for each release, but I do have to admit that I have not >>seem >>it working without problems in the 2.4.x series. >> >>So, the question is, since the default enabling of supermount is >>bound to >>get people into trouble (try to install a game or whatever from >>CD), >>shouldn't there be an update ASAP for 9.0 with a 1) a fix or 2) >>disabled >>default supermount. At least it should be added to the errate page. >> >> >>For cooker I really would like to hear (Juavolumagic: >>http://ftp.linux.org.uk/pub/linu >> >>it mounts disks in userspace, and works already for CDROM drives. >>Is there any reason not to move to this tool for 9.1? It needs some >>work, >>but on the long therm certainly looks like a better solution than >>supermount. >> >>One problem remains that can perhaps only be fixed in the kernel: >>floppiesneed to sync immediatly (==performance loss) when writing, >>because the >>possibility of a manual eject on pc-hardware (this is probably a >>design >>error, MAC does it better;) >> >>bye, >>Danny >> >> >> >> >> >> >> >> > > >
RE: [Cooker] supermount
Danny Really I haven't seen supermount runing perfectly under 2.4; so, as you say, is a good idea take in account other possibilities (Volumagic?) for the future. Anyway I am according to you in the need of change the default in 9.0 enabling, or, if it is not possible in the final distribution, adding the solution in "errata". Francisco Alcaraz Murcia (Spain) - Mensaje Original - Remitente: <[EMAIL PROTECTED]> Fecha: Lunes, Septiembre 30, 2002 5:13 pm Asunto: [Cooker] supermount > > I feel a bit responsible for the current state of supermount, since > I > talked Juan into fixing floppy-write-PANIC issues, which seems to > have > utterly broken supermount for CDROMS in the released 9.0 kernel. > > A simple 'find' in /mnt/cdrom will probably reveal what I'm talking > about > (half the files cannot be stat-ed). In addition, there is the > problem of > non-freeing inodes on zips and floppies. > > Juan, Andrey and probably others, did a great job on patching up > supermount for each release, but I do have to admit that I have not > seem > it working without problems in the 2.4.x series. > > So, the question is, since the default enabling of supermount is > bound to > get people into trouble (try to install a game or whatever from > CD), > shouldn't there be an update ASAP for 9.0 with a 1) a fix or 2) > disabled > default supermount. At least it should be added to the errate page. > > > For cooker I really would like to hear (Juavolumagic: > http://ftp.linux.org.uk/pub/linu > > it mounts disks in userspace, and works already for CDROM drives. > Is there any reason not to move to this tool for 9.1? It needs some > work, > but on the long therm certainly looks like a better solution than > supermount. > > One problem remains that can perhaps only be fixed in the kernel: > floppiesneed to sync immediatly (==performance loss) when writing, > because the > possibility of a manual eject on pc-hardware (this is probably a > design > error, MAC does it better;) > > bye, > Danny > > > > > >
Re: [Cooker] supermount and usb-uhci
Could this supermount error be related to the problems I am having with supermount and the usb-uhci/sr_mod loaded Flash memory-card reader? When I try to use the Flash card with supermount none /mnt/flash supermount dev=/dev/sda1,fs=vfat,user,noauto 0 0 it reads a few files and then hangs. It may also be an issue with interrupts -- the drive will lock up if I use non-supermount fstab user-mount statements -- to use the Flash card with LM9.0, I must disable (rmmod) my CD-RW drive support and vice-versa, to use my CDRW, I must rmmod the usb-uhci and sr_mod (which kills the mouse until a reboot) ... the two devices will not co-exist. There were no problems with either device under LM8.2 If it helps, here's what I get in my log. The interrupt status messages continue until I pop the Flash card, resetting the device. Sep 22 13:30:23 maya kernel: usb.c: USB device 5 (vend/prod 0x5dc/0x2) is not claimed by any active driver. Sep 22 13:30:28 maya /etc/hotplug/usb.agent: Setup usb-storage for USB product 5dc/2/1 Sep 22 13:30:28 maya kernel: usb.c: registered new driver usb-storage Sep 22 13:30:30 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1753 Sep 22 13:30:33 maya kernel: usb_control/bulk_msg: timeout Sep 22 13:31:04 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1524 Sep 22 13:31:10 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1436 Sep 22 13:31:16 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1340 ... Sep 22 13:31:22 maya kernel: usb.c: USB disconnect on device 5 Sep 22 13:31:22 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1221 Sep 22 13:31:29 maya /etc/hotplug/usb.agent: Setup usb-storage for USB product 5dc/2/1 Sep 22 13:34:14 maya kernel: usb-uhci.c: interrupt, status 2, frame# 692 Sep 22 13:34:20 maya kernel: usb-uhci.c: interrupt, status 2, frame# 596 Sep 22 13:34:26 maya kernel: usb-uhci.c: interrupt, status 2, frame# 500 ... Sep 22 13:35:04 maya kernel: usb-uhci.c: $Revision: 1.275 $ time 07:51:45 Aug 30 2002 Sep 22 13:35:04 maya kernel: usb-uhci.c: High bandwidth mode enabled Sep 22 13:35:04 maya kernel: usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 9 Sep 22 13:35:04 maya kernel: usb-uhci.c: Detected 2 ports Sep 22 13:35:04 maya kernel: usb.c: new USB bus registered, assigned bus number 1 Sep 22 13:35:04 maya kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Sep 22 13:35:04 maya usb: Loading USB interface0 (usb-uhci usb-uhci) succeeded Sep 22 13:35:06 maya kernel: input0: USB HID v1.00 Mouse [Logitech USB-PS/2 Trackball] on usb1:3.0 Sep 22 13:35:06 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1756 Sep 22 13:35:06 maya kernel: usb.c: USB device not accepting new address=4 (error=-110) Sep 22 13:35:10 maya /etc/hotplug/usb.agent: ... no modules for USB product 0/0/0 Sep 22 13:35:10 maya /etc/hotplug/usb.agent: ... no modules for USB product 4cc/1122/110 Sep 22 13:35:11 maya /etc/hotplug/usb.agent: Setup usbmouse hid for USB product 46d/c402/210 Sep 22 13:35:11 maya /etc/hotplug/usb.agent: Setup mousedev for USB product 46d/c402/210 Sep 22 13:35:12 maya /etc/hotplug/usb.agent: Setup se401 for USB product 471/30b/2036 Sep 22 13:35:12 maya /etc/hotplug/usb.agent: Setup usb-storage for USB product 5dc/2/1 Sep 22 13:35:43 maya kernel: usb-uhci.c: interrupt, status 2, frame# 1818 Sep 22 13:35:46 maya kernel: usb_control/bulk_msg: timeout Sep 22 13:35:50 maya kernel: usb_control/bulk_msg: timeout Sep 22 13:35:50 maya kernel: usb-uhci.c: interrupt, status 2, frame# 942 Sep 22 13:35:53 maya kernel: usb_control/bulk_msg: timeout Sep 22 13:38:41 maya kernel: usb.c: registered new driver usbdevfs Sep 22 13:38:41 maya kernel: usb.c: registered new driver hub -- Gary Lawrence Murphy - [EMAIL PROTECTED] - TeleDynamics Communications - blog: http://www.auracom.com/~teledyn - biz: http://teledyn.com/ - "Computers are useless. They can only give you answers." (Picasso)
Re: [Cooker] Supermount Problem: Serious?
All md5sums check out perfect and it doesn't just happen with burnt CDs. It
happens with any, and my installs with these CDs were flawless over four+
computers so far. Don't think it's the CDs.
Steve
On Sunday 29 September 2002 3:51 pm, Luis M wrote:
> That usually means a bad burn. Do this:
>
> make sure that your ISO's have the right md5sum:
>
> f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso
> 05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso
> 1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso
>
> To check the md5sum:
> $> md5sum FILE.iso
>
> After you do that, then mount the ISO's to a directory (as root do this for
> the CD's you are having problems with):
>
> #> mount -t iso9660 -o loop FILE.iso /mnt/test
>
> Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if
> this works fine (it should if the md5sum matched and your loop devices and
> hard drive work fine...), then try burning your disk at a lower speed than
> your burner supports -- burning at 8x is better than at any other speed if
> you have the time to wait until it finishes and use cheap blank disks.
>
> I have seen that problem you mentioned before and I'm sure is just a bad
> burn because after burning the disks at two steps slower than my writer
> supports, the disks worked fine.
>
> Sample session here:
>
> $> du -s /mnt/iso2/Mandrake/RPMS2/
> 698M /mnt/iso2/Mandrake/RPMS2
> $> mkdir /mnt/backup/test
> $> cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test
> $>
>
> You can see that the iso's are fine...
>
> From the CarshTesters List:
> > Date
> > 29 Sep 2002 12:25
> >
> >
> > Subject
> > Re: [CrashTesters] 9.0 Supermount nightmare
> >
> >On 29 Sep 2002 12:09 CDT you wrote:
> > > On 29 Sep 2002 06:24 CDT you wrote:
> > > > Dear friends,
> > > > I am having lot of problems with supermount in 9.0:
> > > >
> > > > 1- With supermount enabled, when I try to copy several files
> >
> >sometimes,
> >
> > > > after few minutes, some of the files in the cdrom are not recognized
> > > > ("the file Toshiba... is not valid).
> > > >
> > > > 2. I have dissabled supermount in my dvd-drive; now I can mount and
> > > > umount as a user, the problem of files dissapearing is solved, but
> >
> >when
> >
> > > > Mandrake start ther is an error message: Fault: mount device not
> >
> >found.
> >
> > > > To eliminate the message is enought activating again supermount to
> >
> >that
> >
> > > > drive.
> > > >
> > > > There you have my fstab file; I have to harddisks (hda with two vfat
> > > > partitions and two xfs partitions; and hdb with the main linux
> >
> >paritions
> >
> > > > /dev/hdb5 / ext3 defaults 1 1
> > > > /dev/hdb1 /boot ext3 defaults 1 2
> > > > none /dev/pts devpts mode=0620 0 0
> > > > /dev/hdb7 /disk xfs defaults 1 2
> > > > /dev/hdb8 /home xfs defaults 1 2
> > > > /dev/hdd /mnt/cdrom2 auto
> > > > user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0
> > > > none /mnt/floppy supermount
> > > > dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=
> > > >0
> >
> >0 0
> >
> > > > /dev/hda1 /mnt/win_c vfat iocharset=iso8859-15,codepage=850,umask=0 0
> >
> >0
> >
> > > > /dev/hda5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0 0
> >
> >0
> >
> > > > /dev/hdb13 /object xfs defaults 1 2
> > > > /dev/hda7 /otros xfs defaults 1 2
> > > > /dev/hda6 /pelis xfs defaults 1 2
> > > > none /proc proc defaults 0 0
> > > > /dev/hdb11 /tmp xfs defaults 1 2
> > > > /dev/hdb6 /usr xfs defaults 1 2
> > > > /dev/hdb9 /usr/share ext3 defaults 1 2
> > > > /dev/hdb10 /var xfs defaults 1 2
> > > > none mnt/cdrom supermount
> > > > dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0
> >
> >0 0
> >
> > > > /dev/hdb12 swap swap defaults 0 0
> > > >
> > > >
> > > > Ah!; in my laptop the problem also appears.
> > > >
> > > > Any idea about where the problem arises and how can it bee solved?
> > > >
> > > > Thanks so much in advance
> > > >
> > > >
> > > > Francisco Alcaraz
> > > > Murcia (Spain)
> > >
> > > I will run a test on this now and see what my results are.
> > >
> > > Steve Spears
> >
> >Ran the test and sure enough, I get the same error as well. I opened the
> >CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I
> > did a
> >mass select in the RPMS2 directory and drug them into the new test
> >directory.
> >The copy started off fine but then cam up with the error that certain
> > files didn't exist. I clicked auto skip to see what would happened. It
> > went on for
> >a little bit and then just stopped.
> >
> >I looked in the test directory that I created and there were only a few
> >files
> >in there. When I went back into the CD-ROM/Mandrake/RPMS2 via Konqueror it
> >was showing only one file. enlightenment.
> >
> >Being curious, I went to a konsole and did the followign:
> >
> >[wriker@riker wriker]$ cd /mnt/cdrom
> >[wriker@riker cdrom]$ ls
> >ls: Boot: No such file or directory
> >Mandrake/
> >[wriker@riker cdrom]$ c
Re: [Cooker] Supermount Problem: Serious?
I understand. My point is that either we get SOMETHING that works or IMHO take out Supermount (or other like programs) altogether and setup Kwikdisk to start automatically so newbies can mount/unmount CD's easily. This is getting tedious. I have been running ML (all major releases and cooker) for a long time and Supermount is just a beast, it is so flakey!! I have good luck on my Cooker home box but elsewhere it just seems to fall over way too often. Newbies would quickly become frustrated with something that should work so simply (and has worked in Winblows for as long as I can remember). I have read that the code for supermount is pretty horrid but I couldn't say as I don't code. I test and submit bug reports though!! =) The OSS community is S talented, I am very surprised this has not been properly dealt with long before now.sigh. Cheers, Jason [EMAIL PROTECTED] wrote: On Mon, 30 Sep 2002, Jason wrote: important to have working. I think adding in Alan Cox's fix would be a good idea. It is not a real fix, it is a different program. It already works for CDs, but no floppies AFAIK. I might try to build an rpm and put it into contrib. But it is still very alpha. Danny
Re: [Cooker] Supermount Problem: Serious?
On Mon, 30 Sep 2002, Jason wrote: > important to have working. I think adding in Alan Cox's fix would be a > good idea. It is not a real fix, it is a different program. It already works for CDs, but no floppies AFAIK. I might try to build an rpm and put it into contrib. But it is still very alpha. Danny
Re: [Cooker] Supermount Problem: Serious?
On Sun, 29 Sep 2002, Luis M wrote: > > > That usually means a bad burn. Do this: How is this a bad burn, we are talking about things working with manual mount, but not with supermount. To be even more specific, sometimes I see half of the dirs, somethimes the other half. Even on commercial CDs. It is just utterly broken. But not on all machines it seems (because I never noticed it on my cooker box, but I could have been lucky.) Read the mails again, it has nothing to do with bad burns. Danny
Re: [Cooker] Supermount Problem: Serious?
I have the same problem on my Laptops (seems to work ok on my desktop systems so far). I have to disable supermount to be able to properly mount/unmount/use CD's. Plus, once disabled, I have to shut down and restart the system for the change to take effect, rebooting isn't enough. Supermount seems to bite the big one and for newbies it is very important to have working. I think adding in Alan Cox's fix would be a good idea. Cheers, Jason P.S. I am running a bone stock 9.0 install. John Allen wrote: > [EMAIL PROTECTED] wrote: > >> On Sun, 29 Sep 2002, Steven Spears wrote: >> >> > Mandrake start ther is an error message: Fault: mount device not > found. >> I think you need to remove 'auto' and set 'noauto' in the responsible >> fstab line. Otherwise system will try to mount the empty drive, which >> will fail ofcourse. It is not a real bad problem is it? >> >> >> >>> Ran the test and sure enough, I get the same error as well. I opened >>> the >> >> >> >> >>> and hope this helps. As anyone mentioned this on the cooker list? >> >> >> I think I saw it before. But IMHO (and others) supermount is just >> hopeless. And it has more problems than only the above. >> Anyone with a bit C experience should throw himself on improving Alan >> Cox' volumagic, so that we can do automounting in userspace. >> Hopefully I will try during Xmas holidays. But I never did something >> more serious than some easy gui programs, so do not hold your breath:) >> >> >> Danny >> >> >> >> > I have a really serious problem with supermount. I have created a DVD > of 9.0, which I cannot copy to my hard disk if /mnt/cdrom is > supermounted. It manages to copy maybe 20% then cannot open (stat) any > files on the DVD, not even from the command line. If I disable > supermount and manually mount the DVD it all works OK. (The option to > manually mount/unmount is gone from the CD-ROM popup menu in KDE so > had to use the mount comamnd directly) > > PS: This does not just hapen on one machine. > > >
Re: [Cooker] Supermount Problem: Serious?
That usually means a bad burn. Do this:
make sure that your ISO's have the right md5sum:
f7a093af34b8cbe1abc165213fea9deb Mandrake90-cd1-inst.i586.iso
05a3ccafaacc37d6d1e2f260fc274549 Mandrake90-cd2-ext.i586.iso
1a2fd731fb6e30d39b0b99f504b231b3 Mandrake90-cd3-i18n.i586.iso
To check the md5sum:
$> md5sum FILE.iso
After you do that, then mount the ISO's to a directory (as root do this for
the CD's you are having problems with):
#> mount -t iso9660 -o loop FILE.iso /mnt/test
Then go to /mnt/test/Mandrake/RPMS2 and do the same you tried before... if
this works fine (it should if the md5sum matched and your loop devices and
hard drive work fine...), then try burning your disk at a lower speed than
your burner supports -- burning at 8x is better than at any other speed if
you have the time to wait until it finishes and use cheap blank disks.
I have seen that problem you mentioned before and I'm sure is just a bad
burn because after burning the disks at two steps slower than my writer
supports, the disks worked fine.
Sample session here:
$> du -s /mnt/iso2/Mandrake/RPMS2/
698M/mnt/iso2/Mandrake/RPMS2
$> mkdir /mnt/backup/test
$> cp -a /mnt/iso2/Mandrake/RPMS2/*.rpm /mnt/backup/test
$>
You can see that the iso's are fine...
>From the CarshTesters List:
>
>
> Date
> 29 Sep 2002 12:25
>
>
> Subject
> Re: [CrashTesters] 9.0 Supermount nightmare
>
>
>
>On 29 Sep 2002 12:09 CDT you wrote:
>
> > On 29 Sep 2002 06:24 CDT you wrote:
> >
> > > Dear friends,
> > > I am having lot of problems with supermount in 9.0:
> > >
> > > 1- With supermount enabled, when I try to copy several files
>sometimes,
> > > after few minutes, some of the files in the cdrom are not recognized
> > > ("the file Toshiba... is not valid).
> > >
> > > 2. I have dissabled supermount in my dvd-drive; now I can mount and
> > > umount as a user, the problem of files dissapearing is solved, but
>when
> > > Mandrake start ther is an error message: Fault: mount device not
>found.
> > > To eliminate the message is enought activating again supermount to
>that
> > > drive.
> > >
> > > There you have my fstab file; I have to harddisks (hda with two vfat
> > > partitions and two xfs partitions; and hdb with the main linux
>paritions
> > >
> > > /dev/hdb5 / ext3 defaults 1 1
> > > /dev/hdb1 /boot ext3 defaults 1 2
> > > none /dev/pts devpts mode=0620 0 0
> > > /dev/hdb7 /disk xfs defaults 1 2
> > > /dev/hdb8 /home xfs defaults 1 2
> > > /dev/hdd /mnt/cdrom2 auto
> > > user,iocharset=iso8859-15,codepage=850,ro,umask=0 0 0
> > > none /mnt/floppy supermount
> > > dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0
>0 0
> > > /dev/hda1 /mnt/win_c vfat iocharset=iso8859-15,codepage=850,umask=0 0
>0
> > > /dev/hda5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0 0
>0
> > > /dev/hdb13 /object xfs defaults 1 2
> > > /dev/hda7 /otros xfs defaults 1 2
> > > /dev/hda6 /pelis xfs defaults 1 2
> > > none /proc proc defaults 0 0
> > > /dev/hdb11 /tmp xfs defaults 1 2
> > > /dev/hdb6 /usr xfs defaults 1 2
> > > /dev/hdb9 /usr/share ext3 defaults 1 2
> > > /dev/hdb10 /var xfs defaults 1 2
> > > none mnt/cdrom supermount
> > > dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0
>0 0
> > > /dev/hdb12 swap swap defaults 0 0
> > >
> > >
> > > Ah!; in my laptop the problem also appears.
> > >
> > > Any idea about where the problem arises and how can it bee solved?
> > >
> > > Thanks so much in advance
> > >
> > >
> > > Francisco Alcaraz
> > > Murcia (Spain)
> > >
> > >
> > >
> > >
> > >
> > >
> > I will run a test on this now and see what my results are.
> >
> > Steve Spears
>
>Ran the test and sure enough, I get the same error as well. I opened the
>CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I did
>a
>mass select in the RPMS2 directory and drug them into the new test
>directory.
>The copy started off fine but then cam up with the error that certain files
>didn't exist. I clicked auto skip to see what would happened. It went on
>for
>a little bit and then just stopped.
>
>I looked in the test directory that I created and there were only a few
>files
>in there. When I went back into the CD-ROM/Mandrake/RPMS2 via Konqueror it
>was showing only one file. enlightenment.
>
>Being curious, I went to a konsole and did the followign:
>
>[wriker@riker wriker]$ cd /mnt/cdrom
>[wriker@riker cdrom]$ ls
>ls: Boot: No such file or directory
>Mandrake/
>[wriker@riker cdrom]$ cd Mandrake/
>[wriker@riker Mandrake]$ ls
>RPMS2/
>[wriker@riker Mandrake]$ cd RPMS2/
>[wriker@riker RPMS2]$ ls
>ls: a2ps-devel-4.13-14mdk.i586.rpm: No such file or directory
>ls: adjtimex-1.12-6mdk.i586.rpm: No such file or directory
>ls: am-utils-6.0.7-2mdk.i586.rpm: No such file or directory
>ls: apache-manual-1.3.26-6mdk.i586.rpm: No such file or directory
>ls: apache-suexec-1.3.26-2mdk.i586.rpm: No such file or directory
>ls: fonts-type1-baltic-1.0-6mdk.noarch.rpm: No such file or directory
>ls: freeci
Re: [Cooker] Supermount Problem: Serious?
[EMAIL PROTECTED] wrote: >On Sun, 29 Sep 2002, Steven Spears wrote: > > Mandrake start ther is an error message: Fault: mount device not found. >I think you need to remove 'auto' and set 'noauto' in the responsible >fstab line. Otherwise system will try to mount the empty drive, which >will fail ofcourse. It is not a real bad problem is it? > > > >>Ran the test and sure enough, I get the same error as well. I opened the >> >> > > > >>and hope this helps. As anyone mentioned this on the cooker list? >> >> > >I think I saw it before. But IMHO (and others) supermount is just >hopeless. And it has more problems than only the above. >Anyone with a bit C experience should throw himself on improving >Alan Cox' volumagic, so that we can do automounting in userspace. >Hopefully I will try during Xmas holidays. But I never did something more >serious than some easy gui programs, so do not hold your breath:) > > >Danny > > > > I have a really serious problem with supermount. I have created a DVD of 9.0, which I cannot copy to my hard disk if /mnt/cdrom is supermounted. It manages to copy maybe 20% then cannot open (stat) any files on the DVD, not even from the command line. If I disable supermount and manually mount the DVD it all works OK. (The option to manually mount/unmount is gone from the CD-ROM popup menu in KDE so had to use the mount comamnd directly) PS: This does not just hapen on one machine.
Re: [Cooker] Supermount Problem: Serious?
On Sun, 29 Sep 2002, Steven Spears wrote: > > > Mandrake start ther is an error message: Fault: mount device not found. I think you need to remove 'auto' and set 'noauto' in the responsible fstab line. Otherwise system will try to mount the empty drive, which will fail ofcourse. It is not a real bad problem is it? > Ran the test and sure enough, I get the same error as well. I opened the > and hope this helps. As anyone mentioned this on the cooker list? I think I saw it before. But IMHO (and others) supermount is just hopeless. And it has more problems than only the above. Anyone with a bit C experience should throw himself on improving Alan Cox' volumagic, so that we can do automounting in userspace. Hopefully I will try during Xmas holidays. But I never did something more serious than some easy gui programs, so do not hold your breath:) Danny
Re: [Cooker] Supermount Problem: Serious?
Steven Spears wrote: > Ran the test and sure enough, I get the same error as well. I opened the > CD-ROM with 9.0 CD-ROM #2 and created a directory and opened it. Then I did a > mass select in the RPMS2 directory and drug them into the new test directory. > The copy started off fine but then cam up with the error that certain files > didn't exist. I clicked auto skip to see what would happened. It went on for > a little bit and then just stopped. > > I looked in the test directory that I created and there were only a few files > in there. When I went back into the CD-ROM/Mandrake/RPMS2 via Konqueror it > was showing only one file. enlightenment. > > Being curious, I went to a konsole and did the followign: > > [wriker@riker wriker]$ cd /mnt/cdrom > [wriker@riker cdrom]$ ls > ls: Boot: No such file or directory > Mandrake/ > [wriker@riker cdrom]$ cd Mandrake/ > [wriker@riker Mandrake]$ ls > RPMS2/ > [wriker@riker Mandrake]$ cd RPMS2/ > [wriker@riker RPMS2]$ ls > ls: a2ps-devel-4.13-14mdk.i586.rpm: No such file or directory > ls: adjtimex-1.12-6mdk.i586.rpm: No such file or directory > ls: am-utils-6.0.7-2mdk.i586.rpm: No such file or directory > ls: apache-manual-1.3.26-6mdk.i586.rpm: No such file or directory > ls: apache-suexec-1.3.26-2mdk.i586.rpm: No such file or directory > ls: fonts-type1-baltic-1.0-6mdk.noarch.rpm: No such file or directory > ls: freeciv-1.13.0-6mdk.i586.rpm: No such file or directory > ls: freetype-devel-1.3.1-17mdk.i586.rpm: No such file or directory > ls: fribidi-0.10.1-3mdk.i586.rpm: No such file or directory > ls: frozen-bubble-0.9.3-6mdk.i586.rpm: No such file or directory > ls: fwlogwatch-0.6-3mdk.i586.rpm: No such file or directory > ls: gabber-0.8.7-7mdk.i586.rpm: No such file or directory > ls: gaddr-1.1.4-2mdk.i586.rpm: No such file or directory > ls: gaim-0.59.1-2mdk.i586.rpm: No such file or directory > ls: gated-3.6-2mdk.i586.rpm: No such file or directory > ls: gatos-0.0.6-0.20010216.11mdk.i586.rpm: No such file or directory > ls: gawk-doc-3.1.1-3mdk.i586.rpm: No such file or directory > ls: gcc-c -3.2-1mdk.i586.rpm: No such file or directory > ls: gcc-g77-3.2-1mdk.i586.rpm: No such file or directory > ls: gcc-java-3.2-1mdk.i586.rpm: No such file or directory > ls: gcc-objc-3.2-1mdk.i586.rpm: No such file or directory > ls: gcj-tools-3.2-1mdk.i586.rpm: No such file or directory > ls: gcombust-0.1.52-1mdk.i586.rpm: No such file or directory > ls: gconf-editor-0.3-1mdk.i586.rpm: No such file or directory > ls: gd-utils-1.8.4-6mdk.i586.rpm: No such file or directory > ls: gedit-2.0.2-1mdk.i586.rpm: No such file or directory > ls: gettext-devel-0.11.2-8mdk.i586.rpm: No such file or directory > ls: gettext-0.11.2-8mdk.i586.rpm: No such file or directory > ls: xfce-3.8.16-2mdk.i586.rpm: No such file or directory > ls: xfig-3.2.3d-6mdk.i586.rpm: No such file or directory > ls: xfishtank-2.1tp-6mdk.i586.rpm: No such file or directory > ls: XFree86-static-libs-4.2.1-3mdk.i586.rpm: No such file or directory > ls: XFree86-Xnest-4.2.1-3mdk.i586.rpm: No such file or directory > ls: XFree86-Xvfb-4.2.1-3mdk.i586.rpm: No such file or directory > ls: XFree86-cyrillic-fonts-4.2.1-3mdk.i586.rpm: No such file or directory > ls: xine-aa-0.9.13-3mdk.i586.rpm: No such file or directory > ls: xine-oss-0.9.13-3mdk.i586.rpm: No such file or directory > ls: xine-plugins-0.9.13-3mdk.i586.rpm: No such file or directory > ls: xine-ui-0.9.13-2mdk.i586.rpm: No such file or directory > ls: xinput-1.2-5mdk.i586.rpm: No such file or directory > ls: xli-1.17.0-4mdk.i586.rpm: No such file or directory > ls: xlockmore-5.04-4mdk.i586.rpm: No such file or directory > ls: xmailbox-2.5-15mdk.i586.rpm: No such file or directory > ls: xmms-arts-0.4-8mdk.i586.rpm: No such file or directory > ls: xmms-esd-1.2.7-13mdk.i586.rpm: No such file or directory > ls: xmms-kjofol-skins-1.2.0-5mdk.i586.rpm: No such file or directory > ls: xmms-mesa-1.2.7-13mdk.i586.rpm: No such file or directory > ls: xmms-mikmod-1.2.7-13mdk.i586.rpm: No such file or directory > ls: xmms-more-vis-plugins-1.6.0-2mdk.i586.rpm: No such file or directory > ls: xmms-skins-1.0.0-13mdk.noarch.rpm: No such file or directory > ls: xmms-smpeg-0.3.4-7mdk.i586.rpm: No such file or directory > ls: xmovie-1.9-12mdk.i586.rpm: No such file or directory > ls: xpat2-1.07-12mdk.i586.rpm: No such file or directory > ls: xpcd-2.08-17mdk.i586.rpm: No such file or directory > ls: xpcd-gimp-2.08-17mdk.i586.rpm: No such file or directory > ls: xsysinfo-1.7-12mdk.i586.rpm: No such file or directory > ls: Xtart-1.0-7mdk.noarch.rpm: No such file or directory > ls: xterm-166-1mdk.i586.rpm: No such file or directory > ls: xtoolwait-1.3-5mdk.i586.rpm: No such file or directory > ls: xtraceroute-0.9.0-9mdk.i586.rpm: No such file or directory > ls: xwpick-2.20-10mdk.i586.rpm: No such file or directory > ls: xxgdb-1.12-19mdk.i586.rpm: No such file or directory > ls: ypserv-2.4-1mdk.i586.rpm:
Re: [Cooker] Supermount and CDs
> "warly" == Warly <[EMAIL PROTECTED]> writes: warly> Mattias Dahlberg <[EMAIL PROTECTED]> writes: >> Hi, >> >> Just wondering if it looks like the problem with supermount and symbolic >> links on CDs will be fixed in time for 8.2. If not, maybe there should be >> some kind of instruction somewhere to turn supermount off and re-install >> your Loki game if it doesn't work. Because it's not so easy to connect >> the game's problems to supermount, since the installation *appears* to >> have been successful. warly> Juan said that it will be ok for rc1 It is fixed in rc1 (i.e. if you have 2.4.18-5mdk. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] supermount & cdrecord: Risky?
»Leon Brooks« sagte am 2002-03-06 um 09:11:02 +0800 : > For *some* IDE CD-RW drives, if the drive is not accessed by supermount via > the _SCSI_ device name instead of the _IDE_ device name, yes, sometimes the > drive gets a little confused about what mode it's in. Otherwise, I've not had > a problem. Thanks. Because I only have SCSI drives, there shouldn't be a problem. That's all I wanted to know. Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.iso-top.de | Jabber: [EMAIL PROTECTED] iso-top.de - Die günstige Art an Linux Distributionen zu kommen Uptime: 4 days 5 hours 51 minutes
Re: [Cooker] supermount & cdrecord: Risky?
On Wednesday 06 March 2002 03:16, Alexander Skwar wrote: > Is it risky to leave the cdwriter supermounted when burning CDs? For *some* IDE CD-RW drives, if the drive is not accessed by supermount via the _SCSI_ device name instead of the _IDE_ device name, yes, sometimes the drive gets a little confused about what mode it's in. Otherwise, I've not had a problem. Cheers; Leon
Re: [Cooker] Supermount and CDs
On Wednesday 06 March 2002 05:33, Warly wrote: > Mattias Dahlberg <[EMAIL PROTECTED]> writes: > > Just wondering if it looks like the problem with supermount and symbolic > > links on CDs will be fixed in time for 8.2. > Juan said that it will be ok for rc1 It's nice to see more of these explicit ACKs to the list. Thanks, Warly! Cheers; Leon
Re: [Cooker] Supermount and CDs
Mattias Dahlberg <[EMAIL PROTECTED]> writes: > Hi, > > Just wondering if it looks like the problem with supermount and symbolic > links on CDs will be fixed in time for 8.2. If not, maybe there should be > some kind of instruction somewhere to turn supermount off and re-install > your Loki game if it doesn't work. Because it's not so easy to connect > the game's problems to supermount, since the installation *appears* to > have been successful. Juan said that it will be ok for rc1 -- Warly
Re: [Cooker] supermount & cdrecord: Risky?
Alexander Skwar wrote: > > Hi! > > Is it risky to leave the cdwriter supermounted when burning CDs? > > Alexander Skwar > -- > How to quote: http://learn.to/quote (german) http://quote.6x.to (english) > Homepage: http://www.iso-top.de | Jabber: [EMAIL PROTECTED] >iso-top.de - Die günstige Art an Linux Distributionen zu kommen >Uptime: 3 days 10 hours 26 minutes No problems here. Irek Stroinski
Re: [Cooker] supermount cannot handle symlinks on iso9660
> "goetz" == Goetz Waschk <[EMAIL PROTECTED]> writes: goetz> Hi, goetz> there's a problem with CDs mounted with supermount. All symlinks seem goetz> to be broken. For instance on the CD Commercial applications CD 1 from goetz> Mdk 8.1 the symlinks in Mandrake/RPMS4 are broken. They are OK if the goetz> CD is mounted without supermount. goetz> I've tested the kernels 2.4.13-12mdk, 2.4.17-14mdk and 2.4.17-16mdk Will be fixed in 2.4.18-2mdk. I haven't heard of this problem until this week :((( Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] Supermount killed my DVD/CDRW combo drive (suggestion for MDK)
I remember that when supermount was first incorporated into Mandrake, there was an easy to find option during the installation that allowed the user to turn it off before it was installed. Anyway of getting that re-incorporated into 8.2? On Thursday 07 February 2002 09:58 am, Jason Straight wrote: > I agree, my opinion is that supermount sucks, until the kernel handles hot > swapping better or something. As soon as I try to access something under > the mnt dir or whatever when the wrong device is in all hell breaks loose. > I wish for us laptop users with modular accessories mdk would put in a > choice to use supermount or regular old manual mount - it's not that hard > to mount and unmount devices manually. I think it's one of those instances > where the product is dumified for customers who can't understand and made > annoying for those who can. > > On Wednesday 06 February 2002 10:28, J. Patrick Smith wrote: > > Hello. > > > > The subject line is misleading. I did for several days assume that my > > drive had been somehow damaged, but in the preparation of this message, I > > tried to burn a CD again, and it actually worked. > > > > I recently downloaded 8.2beta1 for testing. > > > > Following installation, my system froze during the boot process when > > supermount began accessing my drives. > > > > I am using a Toshiba Satellite 3005/S303 which has a modular bay in which > > I can have either the DVD/CDRW combo drive installed or the Floppy drive. > > Naturally, I booted with the DVD/CDRW installed. > > > > There needs to either be a workaround to prevent supermount from locking > > up if the floppy drive is not actually present or an errata to indicate > > that supermount needs to boot with the floppy drive installed. > > > > Has anyone else met the same situation? or similar?
Re: [Cooker] Supermount killed my DVD/CDRW combo drive (suggestion for MDK)
I agree, my opinion is that supermount sucks, until the kernel handles hot swapping better or something. As soon as I try to access something under the mnt dir or whatever when the wrong device is in all hell breaks loose. I wish for us laptop users with modular accessories mdk would put in a choice to use supermount or regular old manual mount - it's not that hard to mount and unmount devices manually. I think it's one of those instances where the product is dumified for customers who can't understand and made annoying for those who can. On Wednesday 06 February 2002 10:28, J. Patrick Smith wrote: > Hello. > > The subject line is misleading. I did for several days assume that my drive > had been somehow damaged, but in the preparation of this message, I tried > to burn a CD again, and it actually worked. > > I recently downloaded 8.2beta1 for testing. > > Following installation, my system froze during the boot process when > supermount began accessing my drives. > > I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I > can have either the DVD/CDRW combo drive installed or the Floppy drive. > Naturally, I booted with the DVD/CDRW installed. > > There needs to either be a workaround to prevent supermount from locking up > if the floppy drive is not actually present or an errata to indicate that > supermount needs to boot with the floppy drive installed. > > Has anyone else met the same situation? or similar? -- ^^^ Jason Straight -- President BlazeConnect Internet Services -- Cheboygan Michigan ISP: www.blazeconnect.net Products: www.blazeconnect.com Phone: 231-597-0376 -- Fax: 231-597-0393
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
> "j" == J Patrick Smith <[EMAIL PROTECTED]> writes: j> Hello. j> The subject line is misleading. I did for several days assume that my drive j> had been somehow damaged, but in the preparation of this message, I tried to j> burn a CD again, and it actually worked. j> I recently downloaded 8.2beta1 for testing. j> Following installation, my system froze during the boot process when j> supermount began accessing my drives. j> I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I j> can have either the DVD/CDRW combo drive installed or the Floppy drive. j> Naturally, I booted with the DVD/CDRW installed. j> There needs to either be a workaround to prevent supermount from locking up j> if the floppy drive is not actually present or an errata to indicate that j> supermount needs to boot with the floppy drive installed. j> Has anyone else met the same situation? or similar? Wait for kernel-2.4.17-16mdk (to appear later today or tommorow), has a new supermount patch. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
Borsenkow Andrej <[EMAIL PROTECTED]> writes: > Does it hang after "Turning on user and group quotas for local > filesystems:" messages? In this case (if you can reliably reproduce this > problem) could you try the included patch for /etc/rc.d/rc.sysinit and > tell if it fixes the problem? The patch look fine for me btw:. -- http://www.chmouel.org/
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
yup, It does not seem to have a problem with a 2nd cdrom/cdrw/dvd because the system automatically recognizes the addition of another hd*, hoever the floppy is assumed and not checked so when it is removedlock up. --- "J. Patrick Smith" <[EMAIL PROTECTED]> wrote: > Hello. > > The subject line is misleading. I did for several > days assume that my drive > had been somehow damaged, but in the preparation of > this message, I tried to > burn a CD again, and it actually worked. > > I recently downloaded 8.2beta1 for testing. > > Following installation, my system froze during the > boot process when > supermount began accessing my drives. > > I am using a Toshiba Satellite 3005/S303 which has a > modular bay in which I > can have either the DVD/CDRW combo drive installed > or the Floppy drive. > Naturally, I booted with the DVD/CDRW installed. > > There needs to either be a workaround to prevent > supermount from locking up > if the floppy drive is not actually present or an > errata to indicate that > supermount needs to boot with the floppy drive > installed. > > Has anyone else met the same situation? or similar? > __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com
RE: [Cooker] Supermount killed my DVD/CDRW combo drive
> The subject line is misleading.
The more misleading subject is the more likely messages gets ignored.
I did for several days assume that my drive
> had been somehow damaged, but in the preparation of this message, I
tried to
> burn a CD again, and it actually worked.
>
> I recently downloaded 8.2beta1 for testing.
>
> Following installation, my system froze during the boot process when
> supermount began accessing my drives.
>
Does it hang after "Turning on user and group quotas for local
filesystems:" messages? In this case (if you can reliably reproduce this
problem) could you try the included patch for /etc/rc.d/rc.sysinit and
tell if it fixes the problem?
Please, if you report bug, report it with details. Else it is likely
that it simply will be ignored.
> I am using a Toshiba Satellite 3005/S303 which has a modular bay in
which I
> can have either the DVD/CDRW combo drive installed or the Floppy
drive.
> Naturally, I booted with the DVD/CDRW installed.
>
> There needs to either be a workaround to prevent supermount from
locking up
> if the floppy drive is not actually present or an errata to indicate
that
> supermount needs to boot with the floppy drive installed.
>
As you may guess if it happened on everyone's system it had been fixed
long ago. It happens only on some systems. It means that you should take
some steps to debug it. Or at least make a proper report stating when
exactly your system hangs and why do you think it is related to
supermount at all :-)
-andrej
--- /etc/rc.d/rc.sysinit.orig Wed Jan 30 21:51:30 2002
+++ /etc/rc.d/rc.sysinitWed Feb 6 19:14:55 2002
@@ -807,6 +807,9 @@
# Mount loopback
action "Mounting loopback filesystems: " mount -a -O loop
+# Reset pam_console permissions
+rm -rf /var/lock/console.lock /var/lock/console/*
+
# Restart devfsd actions now that the filesystems are ready
if [ -c /dev/.devfsd ]; then
if [ -x /sbin/devfsd ]; then
@@ -936,9 +939,8 @@
done
rm -f /var/lib/rpm/__db*
-# Reset pam_console permissions
-rm -rf /var/lock/console.lock /var/lock/console/*
-[ -x /sbin/pam_console_apply ] && /sbin/pam_console_apply -r
+[ -x /sbin/pam_console_apply -a ! -c /dev/.devfsd ] && \
+/sbin/pam_console_apply -r
{
# Clean up utmp/wtmp
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
i have a smiliar problems too. I have both a 3.5" and a 5.1/4" floppy drive and i know both works but for some reason if i have floppy2 (5.1/4") specified in /etc/fstab it hangs during the kde startup. /MattB On Wed, 2002-02-06 at 09:28, J. Patrick Smith wrote: > Hello. > > The subject line is misleading. I did for several days assume that my drive > had been somehow damaged, but in the preparation of this message, I tried to > burn a CD again, and it actually worked. > > I recently downloaded 8.2beta1 for testing. > > Following installation, my system froze during the boot process when > supermount began accessing my drives. > > I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I > can have either the DVD/CDRW combo drive installed or the Floppy drive. > Naturally, I booted with the DVD/CDRW installed. > > There needs to either be a workaround to prevent supermount from locking up > if the floppy drive is not actually present or an errata to indicate that > supermount needs to boot with the floppy drive installed. > > Has anyone else met the same situation? or similar? >
Re: [Cooker] supermount at fstab and successfull CD writing
SI Reasoning wrote: > > I have burned cd's without issue while it was > supermounted. > > --- Stefan <[EMAIL PROTECTED]> wrote: > > Fresh Xmas install with no /etc/fstab adaptions by > > hand... > > > > (the first) > > > > ... there where only seconds to finish writing a CD > > ... I opened the > > MidnightCommander to easy navigate the fs, taped the > > /mnt directory (mc > > reads ahead !?) ... and cdrecord stops writing the > > cd with an I/O error. > > Because the CDRW was 'supermounted'! > > > > Is it possible to switch off supermount for > > CD-Writers by default? The > > default user (if he/she belongs to the cdwriter > > group) would enjoy it. > > > > Stefan. > > > > > > > > > > __ > Do You Yahoo!? > Great stuff seeking new owners in Yahoo! Auctions! > http://auctions.yahoo.com same here, it works ok also, but I'm wondering...I have an Aopen CDRW2440, and it has something called "justlink", which I thought was similar to "burnproof", but if I check burnproof in gtoaster, it errors, so wonder if the "justlink" idea can be enabled?
RE: [Cooker] supermount at fstab and successfull CD writing
--- Borsenkow Andrej <[EMAIL PROTECTED]> wrote: > It is good practice to leave system alone while > burning your CD. > > -andrej > I had one external usb cd writer that was so flaky, that the only way I could consistently get it to burn properly was to run it from blackbox. If I tried to run it from win98 (the only version that this drive was supported in) or kde/gnome, etc then it would consistently flake and die, leaving me a very dangerous frisbee. __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
RE: [Cooker] supermount at fstab and successfull CD writing
> > I have burned cd's without issue while it was > supermounted. > Of course if you start burn and go away for a while it works. > > > > ... there where only seconds to finish writing a CD > > ... I opened the > > MidnightCommander to easy navigate the fs, taped the > > /mnt directory (mc > > reads ahead !?) ... and cdrecord stops writing the > > cd with an I/O error. > > Because the CDRW was 'supermounted'! > > This is basically the same issue on Winddows. If you try to access your driver while burning you (with high probability) end up with unusable disc. > > Is it possible to switch off supermount for > > CD-Writers by default? The > > default user (if he/she belongs to the cdwriter > > group) would enjoy it. > > It is not as easy. Nowadays often CD-RW is the single drive used both for reading and writing. It is good practice to leave system alone while burning your CD. -andrej
Re: [Cooker] supermount at fstab and successfull CD writing
I have burned cd's without issue while it was supermounted. --- Stefan <[EMAIL PROTECTED]> wrote: > Fresh Xmas install with no /etc/fstab adaptions by > hand... > > (the first) > > ... there where only seconds to finish writing a CD > ... I opened the > MidnightCommander to easy navigate the fs, taped the > /mnt directory (mc > reads ahead !?) ... and cdrecord stops writing the > cd with an I/O error. > Because the CDRW was 'supermounted'! > > Is it possible to switch off supermount for > CD-Writers by default? The > default user (if he/she belongs to the cdwriter > group) would enjoy it. > > Stefan. > > > > __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Re: [Cooker] supermount and laptops with removable modules
--- SI Reasoning <[EMAIL PROTECTED]> wrote: > Date: Fri, 1 Feb 2002 09:41:57 -0800 (PST) > From: SI Reasoning <[EMAIL PROTECTED]> > Subject: Re: [Cooker] supermount and laptops with > removable modules > To: [EMAIL PROTECTED] > > If I remove the floppy and replace it with a battery > or cdrw, the system freezes during bootup, right at > the mounting section. This is with supermount, it > will > work fine without it. > > --- Guillaume Cottenceau <[EMAIL PROTECTED]> > wrote: > > SI Reasoning <[EMAIL PROTECTED]> writes: > > > > > Maybe supermount should be an option instead of > > the > > > default. Laptops with removeable modules, in > > > particular, removable floppy , can lock up > during > > boot > > > when the floppy is not installed (if it has > > already > > > been setup in supermount). I have not run into > > > problems with 2nd cdroms (like cdrw) because the > > > system checks for the different drives. > Evidently > > > there is no checking for the floppy though (at > > least > > > on my laptop) which leads to the situation where > > > supermount tries to mount an unavaiable floppy > and > > the > > > system freezes at that point. > > > > Well the kernel should not freeze. Is it the same > > without > > supermount, when you try to mount the floppy > > "traditionally" ? > > > > > > -- > > Guillaume Cottenceau - > > http://people.mandrakesoft.com/~gc/ > > > > > __ > Do You Yahoo!? > Great stuff seeking new owners in Yahoo! Auctions! > http://auctions.yahoo.com > __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Fwd: Re: [Cooker] supermount and laptops with removable modules
Manual mounting is a foreign concept to newbies so I know there is danger in it, however, I still think it may be wise to give a choice with an explanation. Maybe have a laptop option during install, which will set the system up safest for laptops and auto load a faq with details so that the newbie would have a 1-2-3 process of enabling/testing features to see if it works. With some time the faq could be laptop brand specific and then eventually model specific. However for this release, it could be more generalized. This option could also load a standardized laptop kernel. This would help resolve such issues such as APIC. With time there could be .config files pre-created and tested for many different laptops and a 1-click button that would compile and install this kernel for the newbie. Maybe even an option that would remember the choices and auto-compile/install whenever the kernel-source is upgraded. I know there is an existing program called ik (install kernel) that has already automated most of this, it may be mdk modified for the distro. > --- Robert Fox <[EMAIL PROTECTED]> wrote: > > I reported this several time before - on my > notebook > > there is a serious > > delay after a new install mounting filesystems. > And > > KDE acts real slow > > because it's constantly trying to access the > > ls-120/CD combo drive, > > > > The solution is to "supermount -i disable" and > > reboot - all is then OK > > but of course, manual mounting is required from > that > > point on! > > > > Cheers, > > R.Fox > > > > > > > > On Fri, 2002-02-01 at 12:51, Guillaume Cottenceau > > wrote: > > > SI Reasoning <[EMAIL PROTECTED]> writes: > > > > > > > Maybe supermount should be an option instead > of > > the > > > > default. Laptops with removeable modules, in > > > > particular, removable floppy , can lock up > > during boot > > > > when the floppy is not installed (if it has > > already > > > > been setup in supermount). I have not run into > > > > problems with 2nd cdroms (like cdrw) because > the > > > > system checks for the different drives. > > Evidently > > > > there is no checking for the floppy though (at > > least > > > > on my laptop) which leads to the situation > where > > > > supermount tries to mount an unavaiable floppy > > and the > > > > system freezes at that point. > > > > > > Well the kernel should not freeze. Is it the > same > > without > > > supermount, when you try to mount the floppy > > "traditionally" ? > > > > > > > > > -- > > > Guillaume Cottenceau - > > http://people.mandrakesoft.com/~gc/ > > > > > > > > > > > > __ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com > __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Re: [Cooker] supermount and laptops with removable modules
Manual mounting is a foreign concept to newbies so I know there is danger in it, however, I still think it may be wise to give a choice with an explanation. Maybe have a laptop option during install, which will set the system up safest for laptops and auto load a faq with details so that the newbie would have a 1-2-3 process of enabling/testing features to see if it works. With some time the faq could be laptop brand specific and then eventually model specific. However for this release, it could be more generalized. This option could also load a standardized laptop kernel. This would help resolve such issues such as APIC. With time there could be .config files pre-created and tested for many different laptops and a 1-click button that would compile and install this kernel for the newbie. Maybe even an option that would remember the choices and auto-compile/install whenever the kernel-source is upgraded. I know there is an existing program called ik (install kernel) that has already automated most of this, it may be mdk modified for the distro. --- Robert Fox <[EMAIL PROTECTED]> wrote: > I reported this several time before - on my notebook > there is a serious > delay after a new install mounting filesystems. And > KDE acts real slow > because it's constantly trying to access the > ls-120/CD combo drive, > > The solution is to "supermount -i disable" and > reboot - all is then OK > but of course, manual mounting is required from that > point on! > > Cheers, > R.Fox > > > > On Fri, 2002-02-01 at 12:51, Guillaume Cottenceau > wrote: > > SI Reasoning <[EMAIL PROTECTED]> writes: > > > > > Maybe supermount should be an option instead of > the > > > default. Laptops with removeable modules, in > > > particular, removable floppy , can lock up > during boot > > > when the floppy is not installed (if it has > already > > > been setup in supermount). I have not run into > > > problems with 2nd cdroms (like cdrw) because the > > > system checks for the different drives. > Evidently > > > there is no checking for the floppy though (at > least > > > on my laptop) which leads to the situation where > > > supermount tries to mount an unavaiable floppy > and the > > > system freezes at that point. > > > > Well the kernel should not freeze. Is it the same > without > > supermount, when you try to mount the floppy > "traditionally" ? > > > > > > -- > > Guillaume Cottenceau - > http://people.mandrakesoft.com/~gc/ > > > > > __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com
Re: [Cooker] supermount and laptops with removable modules
If I remove the floppy and replace it with a battery or cdrw, the system freezes during bootup, right at the mounting section. This is with supermount, it will work fine without it. --- Guillaume Cottenceau <[EMAIL PROTECTED]> wrote: > SI Reasoning <[EMAIL PROTECTED]> writes: > > > Maybe supermount should be an option instead of > the > > default. Laptops with removeable modules, in > > particular, removable floppy , can lock up during > boot > > when the floppy is not installed (if it has > already > > been setup in supermount). I have not run into > > problems with 2nd cdroms (like cdrw) because the > > system checks for the different drives. Evidently > > there is no checking for the floppy though (at > least > > on my laptop) which leads to the situation where > > supermount tries to mount an unavaiable floppy and > the > > system freezes at that point. > > Well the kernel should not freeze. Is it the same > without > supermount, when you try to mount the floppy > "traditionally" ? > > > -- > Guillaume Cottenceau - > http://people.mandrakesoft.com/~gc/ > __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Re: [Cooker] supermount and laptops with removable modules
I reported this several time before - on my notebook there is a serious delay after a new install mounting filesystems. And KDE acts real slow because it's constantly trying to access the ls-120/CD combo drive, The solution is to "supermount -i disable" and reboot - all is then OK but of course, manual mounting is required from that point on! Cheers, R.Fox On Fri, 2002-02-01 at 12:51, Guillaume Cottenceau wrote: > SI Reasoning <[EMAIL PROTECTED]> writes: > > > Maybe supermount should be an option instead of the > > default. Laptops with removeable modules, in > > particular, removable floppy , can lock up during boot > > when the floppy is not installed (if it has already > > been setup in supermount). I have not run into > > problems with 2nd cdroms (like cdrw) because the > > system checks for the different drives. Evidently > > there is no checking for the floppy though (at least > > on my laptop) which leads to the situation where > > supermount tries to mount an unavaiable floppy and the > > system freezes at that point. > > Well the kernel should not freeze. Is it the same without > supermount, when you try to mount the floppy "traditionally" ? > > > -- > Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/ >
Re: [Cooker] supermount and laptops with removable modules
SI Reasoning <[EMAIL PROTECTED]> writes: > Maybe supermount should be an option instead of the > default. Laptops with removeable modules, in > particular, removable floppy , can lock up during boot > when the floppy is not installed (if it has already > been setup in supermount). I have not run into > problems with 2nd cdroms (like cdrw) because the > system checks for the different drives. Evidently > there is no checking for the floppy though (at least > on my laptop) which leads to the situation where > supermount tries to mount an unavaiable floppy and the > system freezes at that point. Well the kernel should not freeze. Is it the same without supermount, when you try to mount the floppy "traditionally" ? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Supermount and bootdisk
On Wed, 30 Jan 2002 09:05:02 +0300 Borsenkow Andrej <[EMAIL PROTECTED]> wrote: > > > As an addendum the same applies in rpmdrake if installating software > from a > > cd source be it the installation cds or an added cd. > > > > What exactly happens? There was a problem in urpmi that it could not > eject supermounted medium (since we switched to "none" for device). It > should be fixed in the latest urpmi. Or do you mean some other problem? > With supermount and urpmi-3.2-5 Using rpmdrake several pkgs selected for install. It is requested that I insert Installation CD1. I insert the CD and click OK. The following error is returned: 'eject: unable to find or open device for: "1" ' Charles
RE: [Cooker] Supermount and bootdisk
> As an addendum the same applies in rpmdrake if installating software from a > cd source be it the installation cds or an added cd. > What exactly happens? There was a problem in urpmi that it could not eject supermounted medium (since we switched to "none" for device). It should be fixed in the latest urpmi. Or do you mean some other problem? -andrej
Re: [Cooker] Supermount and bootdisk
On 29 Jan 2002 23:04:12 +0100 Yves Duret <[EMAIL PROTECTED]> wrote: > Charles A Edwards <[EMAIL PROTECTED]> writes: > > > This was touched on in a previous post but I thought that I would confirm it. > > > > In order to create a bootdisk, using mcc, supermount Must be Disabled. > > i will inspect that asap > thanx to report it. > As an addendum the same applies in rpmdrake if installating software from a cd source be it the installation cds or an added cd. Charles
Re: [Cooker] Supermount and bootdisk
Charles A Edwards <[EMAIL PROTECTED]> writes: > This was touched on in a previous post but I thought that I would confirm it. > > In order to create a bootdisk, using mcc, supermount Must be Disabled. i will inspect that asap thanx to report it. -- Yves Duret [EMAIL PROTECTED] piouk toujours et meme apres !
Re: [Cooker] supermount causes progblem for xmms
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Isn't it just a matter of defining your audio directory in XMMS to something else than /mnt/cdrom (for instance: /mnt/audio). Seems to work for me? Danny On Thursday 24 January 2002 00:56, you wrote: > actually there is a plugin on Contrib that lets you play > audio cd's even though supermount is installed but it > access the audiotracks another way. > > /MattB > > On Wed, 2002-01-23 at 17:23, Guillaume Cottenceau wrote: > > Tech At Mathco Dot Com <[EMAIL PROTECTED]> writes: > > > Would that be considered a bug in xmms or in supermount > > > > Probably a misfeature (rather than a bug) in xmms, which is not > > aware of supermount. > > > > For example for gtktalog I had to ask the author to write special > > code in order to work ok with supermount. > > > > > > -- > > Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/ - -- "He stood up straight and looked the world squarely in the fields and hills. To add weight to his words he stuck the rabbit bone in his hair. He spread his arms out wide. `I will go mad!' he announced." - - Arthur discovering a way of coping with life on Prehistoric Earth. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8UY00aeiN+EU2vEIRAjS/AJ95T4jXuq+s+Cz0BeykWPkaSZ5A+gCggZ73 mwSJLW8+X/bELR5n1KptCDE= =7UaT -END PGP SIGNATURE-
Re: [Cooker] supermount causes progblem for xmms
actually there is a plugin on Contrib that lets you play audio cd's even though supermount is installed but it access the audiotracks another way. /MattB On Wed, 2002-01-23 at 17:23, Guillaume Cottenceau wrote: > Tech At Mathco Dot Com <[EMAIL PROTECTED]> writes: > > > Would that be considered a bug in xmms or in supermount > > Probably a misfeature (rather than a bug) in xmms, which is not > aware of supermount. > > For example for gtktalog I had to ask the author to write special > code in order to work ok with supermount. > > > -- > Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/ >
Re: [Cooker] supermount causes progblem for xmms
Tech At Mathco Dot Com <[EMAIL PROTECTED]> writes: > Would that be considered a bug in xmms or in supermount Probably a misfeature (rather than a bug) in xmms, which is not aware of supermount. For example for gtktalog I had to ask the author to write special code in order to work ok with supermount. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] supermount causes progblem for xmms
Would that be considered a bug in xmms or in supermount /MattB On Wed, 2002-01-23 at 16:55, Guillaume Cottenceau wrote: > Tech At Mathco Dot Com <[EMAIL PROTECTED]> writes: > > > It appears whenever xmms is attempting to access the audiotracks from > > /mnt/cdrom it refuses to enter the directory. Konqueror has a lock > > Yes, the audio read from XMMS has never worked with supermount. > You need to umount the cdrom or disable supermount. > > > -- > Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/ >
Re: [Cooker] supermount causes progblem for xmms
Tech At Mathco Dot Com <[EMAIL PROTECTED]> writes: > It appears whenever xmms is attempting to access the audiotracks from > /mnt/cdrom it refuses to enter the directory. Konqueror has a lock Yes, the audio read from XMMS has never worked with supermount. You need to umount the cdrom or disable supermount. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] supermount - constant attepmts to mount empty drives
On Sunday 20 January 2002 04:02, you wrote: -> On þÔ×, 2002-01-17 at 21:27, Borsenkow Andrej wrote: -> > On þÔ×, 2002-01-17 at 17:09, Borsenkow Andrej wrote: -> > > Many people including me are annoyed by supermount attempting to mount -> > > empty drives. It is causing delays in GUI filemanagers; it also makes -> > > zsh completion really slow (just try to complete insode /mnt). -> > > -> > > Currently there is no check for drive change in subfs_go_online. We -> > > check for subfs_needs_mount which is something different. -> > > -> > > Do we get media change from device when we insert new media? In this -> > > case we could _try_ to insert check for media change into -> > > subfs_go_online and simply fall out if no media has been inserted. -> > > -> > > I am going to try it @home anyway, but - comments? -> > > -> > -> > Does not work (that easy). We do not have device to check until subfs -> > has been mounted. Oops. -> > -> -> Hmm ... looks like query_disk_change always returns 1 if there is no -> media inserted (at least for my two IDE drives and floppy). Anybody -> knows if it possible to reliably query for media presence? Except to try -> to access it as happens currently :( -> -> -andrej -> -> -> -> Nop... but found out that if you keep any disk in the drive, stops doing it.
Re: [Cooker] supermount - constant attepmts to mount empty drives
On þÔ×, 2002-01-17 at 21:27, Borsenkow Andrej wrote: > On þÔ×, 2002-01-17 at 17:09, Borsenkow Andrej wrote: > > Many people including me are annoyed by supermount attempting to mount > > empty drives. It is causing delays in GUI filemanagers; it also makes > > zsh completion really slow (just try to complete insode /mnt). > > > > Currently there is no check for drive change in subfs_go_online. We > > check for subfs_needs_mount which is something different. > > > > Do we get media change from device when we insert new media? In this > > case we could _try_ to insert check for media change into > > subfs_go_online and simply fall out if no media has been inserted. > > > > I am going to try it @home anyway, but - comments? > > > > Does not work (that easy). We do not have device to check until subfs > has been mounted. Oops. > Hmm ... looks like query_disk_change always returns 1 if there is no media inserted (at least for my two IDE drives and floppy). Anybody knows if it possible to reliably query for media presence? Except to try to access it as happens currently :( -andrej
Re: [Cooker] supermount - constant attepmts to mount empty drives
On Fri, 18 Jan 2002, SI Reasoning wrote: > If we are forced to receive these spurious messages, > the least that can be done is to spin them off into > their own logfile, at least it is not clogging > /var/log/messages then. It's not so much /var/log/messages filling up that irritates me. It's all our 8.1 users annoyed with the floppy disk and cdrom making noise every 30mins :-P -- Bryan Whitehead SysAdmin - JPL - Interferometry Systems and Technology Phone: 818 354 2903 [EMAIL PROTECTED]
Re: [Cooker] supermount - constant attepmts to mount empty drives
If we are forced to receive these spurious messages, the least that can be done is to spin them off into their own logfile, at least it is not clogging /var/log/messages then. --- Bryan B Whitehead <[EMAIL PROTECTED]> wrote: > No, it's definatly in 8.1 as well. > > /var/log/messages is filled up with tons of: > > Jan 13 14:00:02 mulan kernel: cdrom: open failed. > Jan 13 14:00:02 mulan last message repeated 3 times > Jan 13 14:00:02 mulan kernel: end_request: I/O > error, dev 02:00 (floppy), > sector 0 > Jan 13 14:00:02 mulan last message repeated 3 times > Jan 13 14:00:02 mulan kernel: cdrom: open failed. > Jan 13 14:00:02 mulan last message repeated 3 times > Jan 13 14:00:02 mulan kernel: end_request: I/O > error, dev 02:00 (floppy), > sector 0 > Jan 13 14:00:02 mulan last message repeated 3 times > > all the errors are at the top and half of the hour. > I think maybe amd is > stating all mounted FS :( > > On Thu, 17 Jan 2002, Chmouel Boudjnah wrote: > > > Borsenkow Andrej <[EMAIL PROTECTED]> > writes: > > > > > Many people including me are annoyed by > supermount attempting to mount > > > empty drives. It is causing delays in GUI > filemanagers; it also makes > > > zsh completion really slow (just try to complete > insode /mnt). > > > > > > Currently there is no check for drive change in > subfs_go_online. We > > > check for subfs_needs_mount which is something > different. > > > > > > Do we get media change from device when we > insert new media? In this > > > case we could _try_ to insert check for media > change into > > > subfs_go_online and simply fall out if no media > has been inserted. > > > > > > I am going to try it @home anyway, but - > comments? > > > > I think that behavior show up only recently ? > > > > -- > > http://www.linux-mandrake.com/en/club/ > > > > -- > Bryan Whitehead > SysAdmin - JPL - Interferometry Systems and > Technology > Phone: 818 354 2903 > [EMAIL PROTECTED] > > = SI Reasoning [EMAIL PROTECTED] "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
Re: [Cooker] supermount - constant attepmts to mount empty drives
No, it's definatly in 8.1 as well. /var/log/messages is filled up with tons of: Jan 13 14:00:02 mulan kernel: cdrom: open failed. Jan 13 14:00:02 mulan last message repeated 3 times Jan 13 14:00:02 mulan kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 Jan 13 14:00:02 mulan last message repeated 3 times Jan 13 14:00:02 mulan kernel: cdrom: open failed. Jan 13 14:00:02 mulan last message repeated 3 times Jan 13 14:00:02 mulan kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 Jan 13 14:00:02 mulan last message repeated 3 times all the errors are at the top and half of the hour. I think maybe amd is stating all mounted FS :( On Thu, 17 Jan 2002, Chmouel Boudjnah wrote: > Borsenkow Andrej <[EMAIL PROTECTED]> writes: > > > Many people including me are annoyed by supermount attempting to mount > > empty drives. It is causing delays in GUI filemanagers; it also makes > > zsh completion really slow (just try to complete insode /mnt). > > > > Currently there is no check for drive change in subfs_go_online. We > > check for subfs_needs_mount which is something different. > > > > Do we get media change from device when we insert new media? In this > > case we could _try_ to insert check for media change into > > subfs_go_online and simply fall out if no media has been inserted. > > > > I am going to try it @home anyway, but - comments? > > I think that behavior show up only recently ? > > -- > http://www.linux-mandrake.com/en/club/ > -- Bryan Whitehead SysAdmin - JPL - Interferometry Systems and Technology Phone: 818 354 2903 [EMAIL PROTECTED]
Re: [Cooker] supermount - constant attepmts to mount empty drives
On þÔ×, 2002-01-17 at 17:09, Borsenkow Andrej wrote: > Many people including me are annoyed by supermount attempting to mount > empty drives. It is causing delays in GUI filemanagers; it also makes > zsh completion really slow (just try to complete insode /mnt). > > Currently there is no check for drive change in subfs_go_online. We > check for subfs_needs_mount which is something different. > > Do we get media change from device when we insert new media? In this > case we could _try_ to insert check for media change into > subfs_go_online and simply fall out if no media has been inserted. > > I am going to try it @home anyway, but - comments? > Does not work (that easy). We do not have device to check until subfs has been mounted. Oops.
RE: [Cooker] supermount - constant attepmts to mount empty drives
> > Borsenkow Andrej <[EMAIL PROTECTED]> writes: > > > Many people including me are annoyed by supermount attempting to mount > > empty drives. It is causing delays in GUI filemanagers; it also makes > > zsh completion really slow (just try to complete insode /mnt). > > > > Currently there is no check for drive change in subfs_go_online. We > > check for subfs_needs_mount which is something different. > > > > Do we get media change from device when we insert new media? In this > > case we could _try_ to insert check for media change into > > subfs_go_online and simply fall out if no media has been inserted. > > > > I am going to try it @home anyway, but - comments? > > I think that behavior show up only recently ? > This is there since 2.4.8-XXmdk (when supermount was put back for the first time?) I do not really recall how it was before because somehow I was happy without supermount. -andrej
Re: [Cooker] supermount - constant attepmts to mount empty drives
Borsenkow Andrej <[EMAIL PROTECTED]> writes: > Many people including me are annoyed by supermount attempting to mount > empty drives. It is causing delays in GUI filemanagers; it also makes > zsh completion really slow (just try to complete insode /mnt). > > Currently there is no check for drive change in subfs_go_online. We > check for subfs_needs_mount which is something different. > > Do we get media change from device when we insert new media? In this > case we could _try_ to insert check for media change into > subfs_go_online and simply fall out if no media has been inserted. > > I am going to try it @home anyway, but - comments? I think that behavior show up only recently ? -- http://www.linux-mandrake.com/en/club/
Re: [Cooker] Supermount hangs up system (with LS-120)
Same problem here - Gateway Solo 9100 with DVD / LS120 combo. Same messages. V. Robert Fox wrote: > > Once again- latest Cooker (12.18.01) - fresh install using PCMCIA.IMG on > a Gateway Solo 9150XL notebook (my normal test machine) with a DVD and > LS-120 combo drive.
RE: [Cooker] Supermount hangs up system (with LS-120)
> Once again- latest Cooker (12.18.01) - fresh install using PCMCIA.IMG on > a Gateway Solo 9150XL notebook (my normal test machine) with a DVD and > LS-120 combo drive. > > Up until recently the system worked fine with previous Cookers - but > since the Supermount has been "fixed" - I get horribly slow response > under KDE and it seems that the system is constantly trying to read the > ls-120 drive (with or w/out media doesn't seem to make the difference) > > When I finally get booted into the system and disable supermount > (supermount -i disable) - the system is just fine. > > Attached is a copy from the dmesg output on a freshly installed and > first bootup system. > Is it supermount in general or just LS-120? What happens when you disable supermount only for LS-120? I suspect that it just takes too much time on LS-120. You may be interested in some patches that disable attempt to access media when drive reports "no media" but still make it work with devfs. I currently have thread on this matter that contains both ide-floppy patch and devfs-related patches to partition code. I am not sure which one is needed; I could forward you the whole thread and you contact folks for more info. If commenting out just LS-120 does not help - we must think something different :-) -andrej
Re: [Cooker] Supermount
> "grinder" == grinder <[EMAIL PROTECTED]> writes: grinder> Hi! grinder> Would you be so kind to send me a clean diff from the supermount grinder> patch for kernel version 2.4.x? (if you could, please send patch for grinder> 2.4.7) Could you check if the patch in ftp://ftp.mandrakesoft.com/pub/quintela/ applies to 2.4.7? It should, you need to apply them in the order: mediactl new_stat supermount I will still do a lot of changes this week, stay tuned reading that dir. BTW, when there are several patches with the same name, the one with higher letter is the last one, you only need to use the last one. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
RE: [Cooker] supermount -i enable problem
> > > Yes. I have very old patch (I sent it half a year ago but nobody > > expressed any interest) for supermount that corrects it. > > to who ? supermount patch or supermount script ? > It was to both but kernel part is not need anymore. > > Well, I always was surprised. IIRC my patch corrected this as well (i.e. > > it introduced a list of "good" fs types or like). > > I still have patch here, if anybody (in Mandrake) is still interested > > i'll be more than happy to look at it. Here is patch for /usr/sbin/supermount. It does add `--' when doing enable and removes it when doing disable. It does *not* prevent disk partition being supermounted - the problem is, /usr/bin/supermount does it for "known" fs types and one of them is vfat. We could - check for mount point names but it looks kinda silly - check if drive is removable. That needs some amount of non-trivial code that I am not willing to write. Instead it adds -m= parameter so you can do supermount -m=/mnt/cdrom enable which is probably enough (after all, you do know which drives are removable?) -andrej supermount.diff
RE: [Cooker] supermount -i enable problem
> > 1/ it doesn't put the -- > Are they still needed ? > Yes. I have very old patch (I sent it half a year ago but nobody expressed any interest) for supermount that corrects it. > 2/ it seems not to respect the user flag. Is it implied ? > Yes it is correct. You do not use mount command with supermount, you do not need user flag. > 3/ My windows partitions are supermounted ! > Well, I always was surprised. IIRC my patch corrected this as well (i.e. it introduced a list of "good" fs types or like). I still have patch here, if anybody (in Mandrake) is still interested ... -andrej
Re: [Cooker] supermount/rpm problem with -23mdk
> "borsenkow" == Borsenkow Andrej <[EMAIL PROTECTED]> writes:
borsenkow> With kernel 23 and supermounted CD rpm segfaults:
borsenkow> strace rpm -Uvh /cooker/i586/Mandrake/RPMS/libtool-1.4-6mdk.
borsenkow> i586.rpm
borsenkow> ...
borsenkow> open("/etc/mtab", O_RDONLY) = 8
borsenkow> fstat64(8, {st_mode=S_IFREG|0644, st_size=295, ...}) = 0
borsenkow> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
borsenkow> -1, 0) = 0x40407000
borsenkow> read(8, "/dev/hda5 / reiserfs rw,notail 0"..., 4096) = 295
borsenkow> stat64("/", {st_mode=S_IFDIR|0755, st_size=504, ...}) = 0
borsenkow> stat64("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
borsenkow> stat64("/dev", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
borsenkow> stat64("/dev/pts", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
borsenkow> stat64("/dev/shm", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=0, ...}) = 0
borsenkow> stat64("/mnt/hd", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
borsenkow> stat64("/mnt/cdrom",
borsenkow> +++ killed by SIGSEGV +++
It is fixed in -26mdk, it was a one line fix, but it took ages to find
that line :((( for details, it was a missing drop_super() :(((
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
Re: [Cooker] supermount
Submitted 18-Sep-01 by Matthew D. Pitts: > Anton, > What sort of problems have you experienced with supermount? I have used it > since 7.0 and never had a problem with it. I had several kernel panics caused by incorrect addressing. Essentially, if you use two different size floppies and inadvertantly attempt to access the mount point for /dev/fd0h1440 and you really wanted to mount /dev/fd0h1743 (a higher capacity disc in the same physical drive), supermount pukes and causes a kernel panic. Autofs simply refuses to mount the erroneous volume. Admittedly, the panic is caused by a user error, but the fact that a user *can* cause a panic because of this module makes it too dangerous, IMHO. Further problems related to the use of writeable removeable media included incomplete writes as the buffers weren't always flushed. With a system like supermount, you cannot afford to cache writes as the user expects to be able to remove the media when the drive light goes out. Supermount has also caused several conflicts with IDE CD-R(/W) drives. Specifically, attempting to mount the volumes while a write was either in progress (which of course fails), or beginning (cdrecord's countdown was in progress) which results in a coaster. These accesses are frequently unexpected such as a remote user logging into an X server and having an icon for the burner (as a cd-rom drive) on his desktop. -- Anton GrahamGPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request "I got everybody to pay up front...then I blew up their planet." "Now why didn't I think of that?" -- Post Bros. Comics
Re: [Cooker] supermount
Anton, What sort of problems have you experienced with supermount? I have used it since 7.0 and never had a problem with it. Matthew. - Original Message - From: "Anton Graham" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 18, 2001 8:11 AM Subject: Re: [Cooker] supermount > Submitted 18-Sep-01 by Borsenkow Andrej: > > > I suggest fixing it. It is probably too late to create and (more > > importantly) test any replacement. > > > autofs seems more stable and is already in the distro. I've been using > it since first experiencing supermount problems in 7.1. > > -- > Anton GrahamGPG ID: 0x18F78541 > <[EMAIL PROTECTED]> RSA key available upon request > > Asking a working writer what he thinks about critics is like asking a > lamp-post how it feels about dogs. > -- Christopher Hampton > >
Re: [Cooker] supermount
Submitted 18-Sep-01 by Borsenkow Andrej: > I suggest fixing it. It is probably too late to create and (more > importantly) test any replacement. autofs seems more stable and is already in the distro. I've been using it since first experiencing supermount problems in 7.1. -- Anton GrahamGPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request Asking a working writer what he thinks about critics is like asking a lamp-post how it feels about dogs. -- Christopher Hampton
Re: [Cooker] supermount integration
let juan work out the kinks in rw first :P
Re: [Cooker] supermount
David Durham wrote: > > Well... I tried editing my fstab line to just have dev= and fs= > but that didn't seem to help... then I rmmod-ed and modprobe-ed > supermount again and it still didn't work... > Oh well... > > On 04 Sep 2001 11:23:21 -0500, Tom Brinkman wrote: > > On Tuesday 04 September 2001 09:46 am, David Durham escribió: > > > Hi... I installed the newest kernel to day, 2.4.8-18, because I > > > wanted to try supermount. > > > Well, it installed fine and I did a `supermount -i enable` (as root) > > > and rebooted. > > > I stuck a data cd in and typed `ls /mnt/cdrom` (as root) and didn't > > > see anything... Then I did a `modprobe supermount` because it wasn't > > > listed in `lsmod` (what, again, do I need to do to make it always > > > load supermount?). Still nothing. > > > Is the format for /etc/fstab still to same? > > > My line for /mnt/cdrom: > > > /mnt/cdrom /mnt/cdrom supermount > > > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0 > > > I can manually mount the cdrom, `mount /mnt/cdrom` and it works fine > > > Any ideas? I'm just hoping I didn't miss a thread about it... > > > >I did just the same as you, but with the addition of trimming my > > fstab line from fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 > > 0, to just fs=iso9660,dev=/dev/cdrom 0 0 That appeared to get > > supermount working, but when I tried to access a CD in Konqueror, the > > system locked up jelly tight. Had to reboot to get it back. Same thing > > happened trying again in a terminal. > > > >Evidently Texstar's had a little better luck > > http://pclinuxonline.com/article.php?sid=434&mode=thread&order=0&thold=0 > > > > -- > > Tom Brinkman Galveston Bay > > > > I got the message "supermount not supported by kernel" during install, and the module was removed and fstab rewritten at that stage. Before 8.1 beta, it was so bad that I edited supermount out of my fstab. -- Anna
Re: [Cooker] supermount
On Tuesday 04 September 2001 11:44 am, David Durham escribió: > I've seen that problem when using a CDRW (and I think the session > wasn't closed) > > The problem was that the system NEEDED to mount it ro and should have > detected that... Perhaps specifying 'ro' on the fstab line would work > for ya... Thanks, I should'a thought of that myself. Yes, adding 'ro' did make supermount functional, but only in a console. Accessing from Konqueror still locks me up jelly tight. Strangely enough, I only added 'ro' to my cdrom, my (Plextor) burner works with supermount (console only) without 'ro'. Also, I checked, and mtab does match fstab. /mnt/cdrom /mnt/cdrom supermount fs=iso9660,ro,dev=/dev/cdrom 0 0 /mnt/cdrom2 /mnt/cdrom2 supermount fs=iso9660,dev=/dev/cdrom2 0 0 It might be a KDE issue, particularly in my case as I'm using Texstar's objprelink'd i686 KDE 2.2 rpm's. I'd rather do without supermount than those ;) They make KDE2.2 wicked quick ;>> -- Tom Brinkman Galveston Bay > > On 04 Sep 2001 11:23:21 -0500, Tom Brinkman wrote: > > On Tuesday 04 September 2001 09:46 am, David Durham escribió: > > > Hi... I installed the newest kernel to day, 2.4.8-18, because I > > > wanted to try supermount. > > > Well, it installed fine and I did a `supermount -i enable` (as > > > root) and rebooted. > > > I stuck a data cd in and typed `ls /mnt/cdrom` (as root) and > > > didn't see anything... Then I did a `modprobe supermount` > > > because it wasn't listed in `lsmod` (what, again, do I need to do > > > to make it always load supermount?). Still nothing. > > > Is the format for /etc/fstab still to same? > > > My line for /mnt/cdrom: > > > /mnt/cdrom /mnt/cdrom supermount > > > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0 > > > I can manually mount the cdrom, `mount /mnt/cdrom` and it works > > > fine Any ideas? I'm just hoping I didn't miss a thread about > > > it... > > > >I did just the same as you, but with the addition of trimming my > > fstab line from > > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0, to just > > fs=iso9660,dev=/dev/cdrom 0 0 That appeared to get supermount > > working, but when I tried to access a CD in Konqueror, the system > > locked up jelly tight. Had to reboot to get it back. Same thing > > happened trying again in a terminal. > > > >Evidently Texstar's had a little better luck > > http://pclinuxonline.com/article.php?sid=434&mode=thread&order=0&th > >old=0 > > > > -- > > Tom Brinkman Galveston Bay
Re: [Cooker] supermount
Well... I tried editing my fstab line to just have dev= and fs= but that didn't seem to help... then I rmmod-ed and modprobe-ed supermount again and it still didn't work... Oh well... On 04 Sep 2001 11:23:21 -0500, Tom Brinkman wrote: > On Tuesday 04 September 2001 09:46 am, David Durham escribió: > > Hi... I installed the newest kernel to day, 2.4.8-18, because I > > wanted to try supermount. > > Well, it installed fine and I did a `supermount -i enable` (as root) > > and rebooted. > > I stuck a data cd in and typed `ls /mnt/cdrom` (as root) and didn't > > see anything... Then I did a `modprobe supermount` because it wasn't > > listed in `lsmod` (what, again, do I need to do to make it always > > load supermount?). Still nothing. > > Is the format for /etc/fstab still to same? > > My line for /mnt/cdrom: > > /mnt/cdrom /mnt/cdrom supermount > > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0 > > I can manually mount the cdrom, `mount /mnt/cdrom` and it works fine > > Any ideas? I'm just hoping I didn't miss a thread about it... > >I did just the same as you, but with the addition of trimming my > fstab line from fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 > 0, to just fs=iso9660,dev=/dev/cdrom 0 0 That appeared to get > supermount working, but when I tried to access a CD in Konqueror, the > system locked up jelly tight. Had to reboot to get it back. Same thing > happened trying again in a terminal. > >Evidently Texstar's had a little better luck > http://pclinuxonline.com/article.php?sid=434&mode=thread&order=0&thold=0 > > -- > Tom Brinkman Galveston Bay > >
Re: [Cooker] supermount
I've seen that problem when using a CDRW (and I think the session wasn't closed) The problem was that the system NEEDED to mount it ro and should have detected that... Perhaps specifying 'ro' on the fstab line would work for ya... On 04 Sep 2001 11:23:21 -0500, Tom Brinkman wrote: > On Tuesday 04 September 2001 09:46 am, David Durham escribió: > > Hi... I installed the newest kernel to day, 2.4.8-18, because I > > wanted to try supermount. > > Well, it installed fine and I did a `supermount -i enable` (as root) > > and rebooted. > > I stuck a data cd in and typed `ls /mnt/cdrom` (as root) and didn't > > see anything... Then I did a `modprobe supermount` because it wasn't > > listed in `lsmod` (what, again, do I need to do to make it always > > load supermount?). Still nothing. > > Is the format for /etc/fstab still to same? > > My line for /mnt/cdrom: > > /mnt/cdrom /mnt/cdrom supermount > > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0 > > I can manually mount the cdrom, `mount /mnt/cdrom` and it works fine > > Any ideas? I'm just hoping I didn't miss a thread about it... > >I did just the same as you, but with the addition of trimming my > fstab line from fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 > 0, to just fs=iso9660,dev=/dev/cdrom 0 0 That appeared to get > supermount working, but when I tried to access a CD in Konqueror, the > system locked up jelly tight. Had to reboot to get it back. Same thing > happened trying again in a terminal. > >Evidently Texstar's had a little better luck > http://pclinuxonline.com/article.php?sid=434&mode=thread&order=0&thold=0 > > -- > Tom Brinkman Galveston Bay > >
Re: [Cooker] supermount
On Tuesday 04 September 2001 09:46 am, David Durham escribió: > Hi... I installed the newest kernel to day, 2.4.8-18, because I > wanted to try supermount. > Well, it installed fine and I did a `supermount -i enable` (as root) > and rebooted. > I stuck a data cd in and typed `ls /mnt/cdrom` (as root) and didn't > see anything... Then I did a `modprobe supermount` because it wasn't > listed in `lsmod` (what, again, do I need to do to make it always > load supermount?). Still nothing. > Is the format for /etc/fstab still to same? > My line for /mnt/cdrom: > /mnt/cdrom /mnt/cdrom supermount > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0 > I can manually mount the cdrom, `mount /mnt/cdrom` and it works fine > Any ideas? I'm just hoping I didn't miss a thread about it... I did just the same as you, but with the addition of trimming my fstab line from fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0, to just fs=iso9660,dev=/dev/cdrom 0 0 That appeared to get supermount working, but when I tried to access a CD in Konqueror, the system locked up jelly tight. Had to reboot to get it back. Same thing happened trying again in a terminal. Evidently Texstar's had a little better luck http://pclinuxonline.com/article.php?sid=434&mode=thread&order=0&thold=0 -- Tom Brinkman Galveston Bay
Re: [Cooker] supermount - quoting NG
"Andrej Borsenkow" <[EMAIL PROTECTED]> writes: [...] > > FYI, Juan has finished rewriting supermount in RO, and still has to > fix a > > couple of bugs in RW. It will be finished in time for 8.1. > > > > Good! Any chance to test it? (There was one bug specific to using > Russian locale :-) * Fri Aug 31 2001 Juan Quintela <[EMAIL PROTECTED]> 2.4.8-13mdk - kernel-source don't require egcs anymore :) - added kdb dir to the source rpm. - fix pcilynx compilation (P165). - remove parpot fix(P4020) merged upstream. - rediff jfs-shared patch (P4005). - removed kdb patch merdeg upstream (P3009). - removed massstorage id75 (P522), merged upstream. - supermount is back (and this time works ro, wait for more news). - rediff multipath (P40). - rediff speedtouch (P519). - sony-clie merged upstream (P420). - kdb patch to make it compile (P3016). - updated kdb. - 2.4.8-ac12. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] supermount - quoting NG
"Andrej Borsenkow" <[EMAIL PROTECTED]> writes: > > "Andrej Borsenkow" <[EMAIL PROTECTED]> writes: > > > > > Message-ID: > > > > > > If Mandrake doesn't get Supermount going in time for 8.1, > > > then they could pre-configure autofs to do that job for CDs > > > & floppies. That's what I'm using since I'm running a 2.4.6 > > > kernel, and it works well for me. > > > > > > Cheers... > > > > Quoting who ?? > > > > News Group. alt.os.linux.mandrake But who says that ? > > > > FYI, Juan has finished rewriting supermount in RO, and still has to > fix a > > couple of bugs in RW. It will be finished in time for 8.1. > > > > Good! Any chance to test it? (There was one bug specific to using > Russian locale :-) > > -andrej > -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
RE: [Cooker] supermount - quoting NG
> "Andrej Borsenkow" <[EMAIL PROTECTED]> writes: > > > Message-ID: > > > > If Mandrake doesn't get Supermount going in time for 8.1, > > then they could pre-configure autofs to do that job for CDs > > & floppies. That's what I'm using since I'm running a 2.4.6 > > kernel, and it works well for me. > > > > Cheers... > > Quoting who ?? > News Group. alt.os.linux.mandrake > > FYI, Juan has finished rewriting supermount in RO, and still has to fix a > couple of bugs in RW. It will be finished in time for 8.1. > Good! Any chance to test it? (There was one bug specific to using Russian locale :-) -andrej
Re: [Cooker] supermount - quoting NG
"Andrej Borsenkow" <[EMAIL PROTECTED]> writes: > Message-ID: > > If Mandrake doesn't get Supermount going in time for 8.1, > then they could pre-configure autofs to do that job for CDs > & floppies. That's what I'm using since I'm running a 2.4.6 > kernel, and it works well for me. > > Cheers... Quoting who ?? FYI, Juan has finished rewriting supermount in RO, and still has to fix a couple of bugs in RW. It will be finished in time for 8.1. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] supermount vs autofs
On 18 Aug 2001 01:02:53 -0400, David Walluck wrote: > On Fri, 17 Aug 2001, Alexander Skwar wrote: > > > But overall, I *completely* agree with you. I also fail to see the > > benefit of supermount - I suppose because of "ignorance", just like you > > are :) > > Well, show me how to use it maybe? :) I know my automount tries to contact > and LDAP server and then dies, so that's no good :) In /etc/auto.master I have: /misc /etc/auto.misc --timeout=3 /net/etc/auto.net --timeout=60 In /etc/auto.misc: cdrom -fstype=auto,ro,nosuid,exec,user,nodev :/dev/cdrom cdrom2 -fstype=auto,ro,nosuid,exec,user,nodev :/dev/cdrom2 I removed the /mnt/cdrom and /mnt/cdrom2 directories, and made them a symlink to /misc/cdrom and /misc/cdrom2. /etc/init.d/autofs start to start it. I also commented the lines in /etc/init.d/mandrake_everytime which check the existence of /mnt/cdrom to avoid an error message because it was not able to create these directories. If you don't access anything on cdrom/cdrom2 for 3 seconds, it will be unmounted automatically, so there's in fact no problem in having to wait before you can eject. Only drawback I discovered is that it lasts a rather long time to view the contents of /mnt/ when either or both of the cdroms are empty; it seems he tries to mount the cdroms, and so you have to wait for some sort of time-out when there's no cd in it. Frederik Himpe
