rmarin2

I have the same problem. At bootup I get "fs type supermount not supported by kernel" when it trys to auto mount both my cdroms. I'm not sure if I missed a kernel option to enable supermount when I compiled the 2.6.7 kernel. If I find anything I'll be sure to post it!!

I'll be sure to check out those links. But like I mentioned earlier, the problem isnt getting k3b or any other software to work. I can burn cd's fine and even do a cd to cd copy without any problems. When I installed K3b I never let it change my fstab. I've manually controlled it. The problem is just being able to access data on my cdrom while I'm scsi emulation on it.

-Rich

why do you need k3b to recognize your regular cdrom drive?

When I copy a cd, I can do it on the fly (cd to cd), rather than creating an image first and then burning it.

did this probalem just occur after setting up k3b &/or xcdroast, or has it been from the get go? reason i ask, is that may be a key. after setting up those 2 programs, i started having problems with my drives/data not being recognized & had to start tweaking some things, so fill in that blank please. also, are you sure you have permissions set correctly for your burner? mind you, i'm new at this too, but after what i went through with cdrom/burner/ide/scsi/k3b/xcdroast i feel pretty confident about setting all of those devices & programs up. also, 2 other things to do............(this is kinda late into the game to mention this ) but, before editing fstab, lilo, or any configuration file, it's always wise to backup a good working copy of said file in case things get way beyond your comprehension to repair them. that way, you can just replace with the good file & you'd (at least) be back where you started. second, you can delete all lines in your fstab referencing your cdrom & cdrw, go to Mandrake Control Center->Mount Points, & use the wizard there to set up your drives. it's pretty easy to understand using the MCC. you can set types, permission, etc in there. again, i'd advise you to make back up copies before you start editing your heart out if you don't feel confident in doing so. sorry, but i'm at work, so i gotta get back to that now. if somebody else can't get you straightened out, i'll have time to get back here tonight from home.

Chris

Actually the problem has occurred from the initial install of mandrake 9.1. Actually this happend when i had 9.0 installed as well. I thought it would clear up if I did a fresh install of 9.1, but I guess not.

As for the backup, I've learned a long time ago to backup crucial files and data. So should something go horribly wrong while I'm trying to fix this problem, I can get back to my original starting point.

As for permissions, yes, that is ok.

I have no problems using MCC or command line. Command line is a little easier for me! :)

Thanks for your help Chris, and everyone else who has contributed their opinions!!

I will keep plugging away and researching. The answer must lie somewhere!! :)

-Rich

you do realize that hdd doesn't need to be set to ide-scsi, right?  you only have to set your burner to ide-scsi......

If I don't set hdd to ide-scsi, k3b doesn't recognize it.

i agree with Ixthusdan about supermount. i was having horrendous problems with my cdrom & burner (not) being recognized in K3b & weird ejecting problems. he finally convinced me about the evil supermount & i've been problem free since. get rid of the supermount lines in your fstab, then add icons for your rom & burner to your desktop (if you're using KDE) by right clicking desktop->new->cdrom/dvd device (or something close to that.....not at the Linux machine right now) then point the links to your mnt/cdrom (scd0) mnt/cdrom2 (scd1). you can also do the same if you want to disable supermount with your floppy drive, just right click & select new->floppy drive for the icon & point the link to the mnt/floppy. here's my fstab with the entries to make this all happen:

 

/dev/hdc7 / ext2 defaults 1 1<!--QuoteEBegin--><!--QuoteEBegin-->none /dev/pts devpts mode=0620 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/hdc10 /home ext2 defaults 1 2<!--QuoteEBegin--><!--QuoteEBegin-->/dev/scd0 /mnt/cdrom auto user,noauto,ro,exec 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/scd1 /mnt/cdrom2 auto user,noauto,ro,exec 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/fd0 /mnt/floppy auto user,noauto,ro,exec 0 0 dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/hdc1 /mnt/win_c vfat iocharset=iso8859-1,codepage=850,umask=0 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/hdc5 /mnt/win_d vfat iocharset=iso8859-1,codepage=850,umask=0 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/hdc6 /mnt/win_e vfat iocharset=iso8859-1,codepage=850,umask=0 0 0<!--QuoteEBegin--><!--QuoteEBegin-->none /proc proc defaults 0 0<!--QuoteEBegin--><!--QuoteEBegin-->/dev/hdc9 /usr ext3 defaults 1 2<!--QuoteEBegin--><!--QuoteEBegin-->/dev/hdc8 swap swap defaults 0 0

 

also note, again, if you're using KDE, you can right click on the desktop->configure->& select which device icons you want to appear or hide.

Chris

Well I moved the cd drives to different channels and is set up as follows:

hdb: cdrw --> mount point /mnt/cdrom - /dev/scd0

hdd: cdrom --> mount point /mnt/cdrom2 - /dev/scd1

I also disabled supermount but still cannot access data off the cdrom. This time, everytime I try to mount the drive I get an error saying FileSystem Type must be specified. When I change fstab to reflect the ISO9660 file type for that drive, the next error message I get is 'wrong fs type, bad option, bad superblock on scd1, or too many filesystems mounted'.

I am fresh out of ideas! :)

-Rich

Hmm.. so your saying that supermount doesn't play well with scsi emulation?

As for having the 2 drives on the same channel, I've tried moving them to separate channels but still ran into the same problem. But I will try again in conjuction with disabling supermount.

Thanks for the info!

-Rich

Ok, I've searched all over but haven't found an answer to my specific problem. So any help would be appreciated!

I am able to do scsi emulation on my cd drives and use burning software successfully, i.e. use k3b or x-cd-roast. The problem lies when I try to access data off the cdrom. I cannot read a cd from my cdrom but am able to read it from the cdrw. When I 'cd /mnt/cdrom2' I get an input/output error

Here is the kicker. When I take off scsi-emulation for my cdrom, I can access the drive fine, but obviously k3b doesn't see it.

I have 2 drives:

hdc: Plextor CDRW ----> mount point is /mnt/cdrom

hdd: Samsung 40x cdrom ---> mount point is /mnt/cdrom2

lilo.conf:

append="quiet devfs=mount hdc=ide-scsi hdd=ide-scsi"

fstab:

none /mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/cdrom2 supermount dev=/dev/scd1,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/scd0 and /dev/scd1 are sym links to the correct device

Thank you

-Rich

Sorry for digressing, but here is what I've tried to do this far, and still have no clue what is going on.

Installing vmware using the source code or the rpm package is successfull. I configure it for a WIN XP guest OS and that goes well. The problem occurs during the installation of the Guest OS. It loads the initial setup files and prompts to create the partition. If I select either an NTFS or FAT32 partition the same thing happens, vmware just aborts and I can't get back in unless I completely uninstall and start over!

Any ideas would be appreciated!

Thanks!

-Rich

I'm sorry but I'm not obliged to provide you any advice, and that is not a reason why you should lose your cool. Believe me, worse things happen :)

 

If you managed to install the software previously, try to determine the the factors that have changed, e.g. different kernel, hardware...

 

Also, did you submit a support request to VMWare?

I'm not sure if you know where you are posting, but that is why this forum was created, so that people can share ideas and help each other. Last time I checked it wasn't created to just post what you've managed to accomplish and not lend a helping hand if possible. So unless your willing to shed some light on this situation, post your accomplishments elsewhere!

I don't understand why so many people have problems with installing VMWare on Mandrake 9. You only have to follow the instructions of vmware-config.pl or read the manual first, usual stuff.

 

In the past month I have installed 5 Mandrake desktops with VMWare 3.2 evaluation and licenced versions.

Maybe so many people are having problems with vmware because each linux install is not the same. Therefore there may be something installed or not installed that is causing vmware to behave erratically. I too have installed vmware on MDK9 on several times without any problems, but this time something is causing it to not work!

How about offering some useful advice rather than assuming that since you can do it so should everyone else!!!!

Primary OS is mandrake 9.  Although it not listed as being officially supported it has worked flawlessly for me in the past, on several different installs.

 

Mandrake 9 has only been out for a month, how many OSs have you installed using vmware in that time period??

 

If you look around the board you should find a few other posts about MK9 and vmware. According to those, people have not been able to get it to work, I believe.

 

Good Luck.

I have seen some of those posts, however I have rebuilt my machine a few times with mandrake 9 and have gotten vmware to work. The only difference between the those installs and this one is that I am actually working as a user, not as root!

First things first, what is the primary OS and is it supported by vmware? Second, if NTFS fails then why not try XP using FAT32?

Primary OS is mandrake 9. Although it not listed as being officially supported it has worked flawlessly for me in the past, on several different installs.

I am actually going to try and use FAT32 right now. I will update you on the results!

I install vmware fine but when I try to install the gues OS (winXP), vmware just aborts. It always fails when it starts to format the NTFS partition it is going to install XP to. I have tried it as root and as a user but it still fails. I know it works because I've done it before, several times actually, using mdk9, winxp pro, and the latest version of vmware.

Any help please!! Thanks!

-Rich

I can't empty my trash bin in Evolution upon exiting. I have the option enabled in the config menu. I'm running MDK9 and evolution under kde. Any ideas?

Thanks!!

I'm still new to this but I have installed wine and I know it works because I also installed the crossover plugin and that works fine. When I try to install a program under wine i get this error:

fixme:win32:PE_CreateModule Security directory ignored

wine: Unhandled exception, starting debugger...

Warning: /usr/bin/winedbg.exe not accessible from a configured DOS drive

wine: Unhandled exception, starting debugger...

Any ideas how to fix this. It's driving me crazy!

Thanks in advance!!

P.S. Running MDK9 and the wine packaged that comes with it; version 20020804

-Rich