satelliteuser083

Did just as you suggested and the first bit - auto-mounting hde and hde1 - worked. Many thanks . The 10.2 permission suggestion didn't; however I managed to get write access in 10.2 by changing it - as root - to 'myself'. Now, strangely, write access (but only to the 'myself' folder, thus not allowing me to create sub-folders) is refused in 10.1, where the owner and group are now set to '500'. Don't understand the significance of this '500'. Not very important but an interesting technical problem.

Sorry, forgot the filesystem, it's ext3. I've just tried your suggestion, but it didn't work. The first reboot after modifying fstat failed because I'd forgotten to insert the card (logical, I thought); this CAN happen, of course, but it shouldn't cause the system to hang with the message that "the filesysytem hde could not be found" (or something like that, I can't remember the exact wording). Anyway, I inserted the card and rebooted, with the same result. The filesystem definitely IS ext3 (it's an old hdd with 10.1 installed on it), although, when mounted using the script previously described, KDiskFree indicates the type as '?'. Looks to be a bit more complicated than at first sight. Fortunately I was able to remove the entry in fstat on 10.1 (which always caused a hang-up at boot) via 10.2, so 10.1 works again now.

contents of /etc/fstab (10.1): /dev/hda7 / ext3 noatime 1 1 /dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hda6 swap swap defaults 0 0 /dev/hde5 swap swap defaults 0 0 ;************** contents of /etc/fstab (10.2) WITH pcmcia-hdd: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/hda8 / ext3 noatime 1 1 /dev/hdc /mnt/cdrom iso9660 user,iocharset=iso8859-1,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hda6 swap swap defaults 0 0 ;************** contents of /etc/fstab (10.2) WITHOUT pcmcia-hdd: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/hda8 / ext3 noatime 1 1 /dev/hdc /mnt/cdrom iso9660 user,iocharset=iso8859-1,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hda6 swap swap defaults 0 0 ;********************************* Hope this helps

I have a PCMCIA HD-Drive (it's called "PCMCIA PnPIDE", and 10.1 recognises it as hde). It is normally not mounted following boot, so I have to do this manually, currently with the script su -c "mount /dev/hde1 /mnt/cardhde" , which means having to enter the root-password. I would like the system to do this automatically, if possible, but have no idea how to even begin such an exercise. Any help would be appreciated. Having mounted the device I have full read/write rights in 10.1. Doing EXACTLY the same in 10.2 (I copied the script into 10.2), however, I have no write access. The properties box says that the owner/group is "root" in 10.1 (but still allowing me to write) and "501" in 10.2. Can anyone tell me what this "501" means and how I can overcome this situation? Moved from 'Software' to 'Terminal Shell Commands, Kernel and Programming' - Artificial Intelligence

Am not having much luck with this mdkkdm-installation. When I entered the command which you suggested (following su -) I was given the message "no package named mdkkdm". Do I have to force urpmi to go to the DVD, because it didn't seem to want to go there (assuming that that's where mkdkdm is).

Did exactly as you suggested and IT WORKED. Thanks very much!! :lol:

The two entries are: KDM (KDE Display Manager) - which I assume you mean by 'mdkkdm', and XDM (X Display Manager) KDM was already selected. I've tried selecting each and restarting the manager (as required) but no difference. Strange, but as said, it's not important.

I used polemicz's method, which works. Thanks. The entry in lilo.conf (in 10.1) regarding 10.2 is: image=/mnt/le2005/boot/vmlinuz-2.6.11-6mdk label="linux-le2005" root=/dev/hda6 initrd=/boot/initrd.img read-only which, when selected, leads to 10.2 being booted. There's just something that I don't fully understand about this boot process. I was under the impression that, on selecting this entry, the boot loader on hda6 (i.e. 10.2) would be run, giving the usual selection of 'linux', 'linux-nonfb' and 'failsafe', but all that happens is that 'linux' is run immediately, with no menu being presented. If this is correct, what is the point of writing the lilo-bootloader to the boot-partition at installation-time?? Have I made a mistake with the "other-os" stanza (syntax, perhaps) in the 10.1 lilo.conf?

With the FOURTH DVD I have managed to get LE2005 up and running, in the usual Mandrake manner of super-easy installation. Much happiness!! Just a small point, which isn't at all important but would like to solve. In 10.1 at boot-time I am presented with two icons (for me and for root), from which I can choose how to boot and only have to supply the approp. password. In 10.2 I have been unable to get this facility: I am only given a double-box that I have to fill in with both user and password. Is the 10.1 arraangement also possible in 10.2, and, if so, how?

Following installation of LE 2005 I attempted to install kppp, only to be presented with the continual message to "Please insert the medium named "Installation DVD" on device [/dev/cdrom]". Each time I insert the DVD it is rejected (and ejected). Has anyone else had this problem? How does 10.2 recognise the DVD which has been inserted, and is there any way of overcoming this hitch?

I have 10.1 on hda5, 10.2 on hda6 and the swap (for both) on hda7. See below for the continuing saga ... Have managed to install LE 2005 (upgrade of existing installation) and it also boots correctly (no error-messages, anyway). At least, that's what I thought ... At 10.2 installation-time I specified that the lilo-bootloader be written to the MBR, which then booted correctly. I want a dual-boot with mdk 10.1, so I - as root - opened both lilo.conf files (the one on the 10.1 partition and the other on the 10.2 partition) and modified the 10.2 lilo.conf by pasting the 10.1 entries from the 10.1 lilo.conf into it. So far, so good. Ran lilo -v, rebooted and, lo and behold, the lilo list offered me both installations. I selected 10.2 and it again booted correctly. I then rebooted and selected 10.1 from the lilo-list, only to see the following message (from many) - Could not load /lib/modules/2.6.8.1-12mdk/modules.dep: No such file or directory [FAILED] This is lilo, using lilo.conf from 10.2, remember. When (three days ago) I modified lilo.conf in 10.1, and ran lilo -v from 10.1, I couldn't get 10.2 to boot properly. Then I had the error-message - Could not load /lib/modules/2.6.11-6mdk/modules.dep: No such file or directory This seems to be an irreconcilable conflict and I assume that I'm doing something wrong - but WHAT?

Managed to install mdk LE 2005 from a different medium, and the installation appeared to have been successful, no error-messages at least. However, on boot a number of error messages does appear, including (probably not unsurprisingly): - Init USB controller: FATAL: Could not load /lib/modules/2.6.8.1-12mdk/modules.dep: No such file or directory [FAILED] - Mount USB filesystem: mount point /proc/bus/usb does not exist [FAILED] - Bringing up loopback interface: arping .... Error, some other host already uses address 127.0.0.1 [FAILED] but, more seriously: - Mounting local filesystems: fs type supermount not supported by kernel. fs type vfat not supported by kernel [FAILED] Following boot I entered MCC/Install to install kppp, and was confronted with the message - Please insert the medium named "Installation DVD" on device [/dev/hdc] but was unable to proceed past this point because the system refused to recognise the DVD (which WAS used for the installation!!). I remember having had difficulties starting the installation, and had to go via <F1> and then 'install linux', but otherwise everything seemed to be OK.. When I try to simply read the DVD I get the error message: - Could not mount the device. fs type ISO9660 not supported by kernel. The DVD is OK because mdk 10.1 can read it without any problems. Perhaps there is some ident-file missing (or unaccessable). Any tips would be welcome

Sadly was unable to get into 10.1 because 'startx' didnt work and couldn't find a suitable editor to modify 'etc/lilo.conf' with. So I reinstalled 10.1 (it gets easier every time), setting the mount-point to '/', which enabled me to get into X with access to 'root' and an editor for the modification of lilo.conf. Now I have 10.1 AND 10.2 bootable ,but this is clearly no long-term solution to the problem of multiple oot-partitions. This all occurs on my spare HDD, by the way, I still have the problem of the mount-point for an installation of a second (or further) OS, however. I must admit that I thought I understand the significance of the mount-point, but it looks as though I don't. On re-installing 10.1, I (apparently) removed '/' from 10.2, so how come I can still boot into this from lilo? Can I use any mount-point other than '/' for a new installation? Until I solve this point I am reluctant to install 10.2 on my main HDD for fear of ruining 10.1 again. By the way, polemicz, where did you get your installation of mandriva from? Mine doesn't boot correctly, thought that perhaps the DVD was faulty and a different source might solve that.

I received my DVD of mdk 10.2 (le 2005) yesterday, installed it and, of course, it didn't work. On installation I had a serious number of 'unable to install ...PACKAGE-NAME' messages, don't know whether this had anything to do with my particular hardware config or faults on the DVD. Anyway, on reboot (only 10.1 in LILO, by the way) I selected 'linux' as usual and the system started to boot but failed to start X-Windows. On installation of 10.2 I had selected and formatted a new partition, and set the mount-point '/' to this new partition. Come to think of it, this was probably wrong and now inhibits the correct booting of 10.1. If it WAS incorrect, which mount-point SHOULD I have used? Any tips on this? Also, if the problem DOES lie with the mount-point (see above), how do I restore the '/' mount-point to 10.1? I don't know how to start X-Windows manually, so was unable to modify /etc/lilo.conf to include the new 10.2, as suggested. Couldn't even get vi to run!! Any help to any of these points would be appreciated. PS fortunately I did all this on a spare HDD, so I still have my original HDD with a working installation of 10.1. :P

I re-installed mkd 10.1 (official) and now the printer doesn't output anything. It works under Win 2000 Pro (dual boot), so its not a hardware problem, and the scanner section works under mkd. I've uninstalled cups, deleted the printer driver and added it again, but no luck. The 'add printer' procedure appears to run correctly, up to the point where I try to print the test page, then NOTHING. Looks like I've forgotten to install something else, but can't remember what. The printer did work prior to the re-installation. Any hints?

Thanks polemicz, just a couple of points to clarify some confusion on my part. Assume you mean "and placed its bootloader on the boot partition (of 2005)". Also "you'll have to have 2005 set up" means that 2005 must already have been installed before attempting to modify 2001 lilo.conf.

I read somewhere - can't remember where, sadly - about someone who had two different versions of mkd on a disk, one that was in normal use and a later version for experimentation. I seem to remember that this involved having one installation of lilo in the MBR linking to another installation (of lilo) in the partition with one or other of the two mkd versions. Sounds a bit confusing, when I think of it!! Anyway, I'd like to do the same with mkd 10.1 (my normal version) and 10.2LE for experimentation. How exactly does this have to be done and why is it not possible to manually modify lilo in the MBR to allow access to either of these two versions. I've modified lilo.config myself and it didn't seem particularly difficult. Any hints greatly appreciated.

THANKS all, I did as was suggested and it worked. It took a bit of fiddling, but I can now boot correctly, no re-installation reqd ! Once again, thanks.

scarecrow and adamw, thanks. Now the (for me) not-so-trivial bit. How do I edit /etc/fstab? I've already tried with vi (since, from the rescue-DVD, there's no xwindows editor available), but have not been able to address hda8. How do I specify this partition to the editor? In Windows I would say D:/etc/fstab or E:/etc/fstab, but don't know the linux-syntax. I would also prefer to NOT have to use vi, so another suggestion would do well !!

Panic!!! I seem to have played a daft trick by creating an additional (Windows) partition immediately prior to the root partition of my Mandrake 10.1 (Official) installation (by splitting the larger Windows partition there). The effect is that what was previously hda7 is now hda8 and on boot I get unpleasant messages, such as 'cannot find ext3 filesystem on dev hda7', which finally end in a 'Kernel panic: no init found'. The boot-loader has been reinstalled, using the rescue option on the installation-DVD, so that the system now boots correctly from hda8 (and not hda7), but I assume that there is a configuration-file on hda8 (could it be /etc/fstab?), specifying that the required ext3 filesystem is on hda7, which, of course, is no longer correct. I've tried to merge the newly created partition back into the old one, but my version of Partition-Magic (V6) refuses to do it, so I'm stuck with this state. Is there any way of automatically updating whichever process/file is responsible for the configuration definition, or, if not, is it possible to do this manually? Failing all this, it looks as though another installation is looming. It strikes me, though, that there OUGHT to be a means of changing the configuration, otherwise this would preclude changing the partition structure of the disk, as IS possible in Windows. Some help would be greatly appreciated. [moved from Software by spinynorman]

Thanks to all who contributed, I've finally managed to get wvdial working in a konsole; that suits me :-) The deciding tip came from Jacques Goldberg at discuss@linmodems.org (see his paper -> http://linmodems.technion.ac.il/post-install.html), which considers modems in general wrt wvdial. Once again, thanks!! Marked the thread Solved - Artificial Intelligence

Thanks, I'm just in the process of getting it to work from within a konsole; painfully slow process, though. Will return to your suggestion when this works.

hello bvc, did as suggested and downloaded 'libwvstreams3.74-3.74.0-4mdk.i586.rpm,' and 'wvdial-1.54.0-3mdk.i586.rpm'. clicked first on ibwvstreams and installed (got bad signature warning, which I ignored), then clicked wvdial, with same warning, also ignored. So I assume that wvdial is now available for use, but, WHERE is it? Can't find it in any of the menus :-( Perhaps ignoring the warnings was a bad move? Need further help !! Thanks, anyway.

I feel as though I'm going nuts, or something I tried your tip with urpmi, but with no apparent success. So, I went to RPM Search, searched on 'wvdial' and 'wvstreams' and then downloaded 'wvdial-1.54.0-3mdk.src.rpm' and 'wvstreams-3.74.0-4mdk.src.rpm' from ftp.uni-bayreuth.de. I then went to MCC -> Software Management -> Media Manager, where I tried to Add a new Medium (the folder where I'd saved the downloaded RPMs). This appeared to work - difficult to say because there's no feedback - but when I then returned to Software Management -> Install, did an Update media on this 'new' medium and then searched on 'wvdial' the result was a huge ---> NOTHING. Grrrrrrrrrrrrrrrr!! Is it me, or IS there a problem with MCC here? The logic evades me. Need help!!

I would like to use wvdial, cannot find it in my installation of 10.1 so assume it needs to be downloaded and installed that way :-( Anyway, found the .tar files for wvdial and its library but have no idea where the library needs to reside in order to be able to 'make' wvdial. Have tried to 'make' the library but keep getting mysterious error messages; am clearly trying to put it in the wrong place. A tip would be appreciated