ianw1974

Leave it installed, and manually copy the luna.svg to this location to fix it. Copy it from your Mageia 2 install, and place it in the correct location on Mageia 1. Or download fm the link I gave you previously.

OK, understand that it installed properly, but it seems that luna.svg is missing, hence why I asked if you can verify with the commands I put to make sure the file is exactly there. If you've done this, and it is, then I'm expecting it's searching in a place where it should be but it isn't. Which was why wanted to find out, if the luna.svg is in the place where I mentioned it should be.

Hi John,

Try here, some comments about where to put the luna.svg:

http://kde-look.org/content/show.php/luna.svg?content=93779

you can also download the luna.svg here. Alternatively, search to see if there is a luna package in Mandriva, if not, then download and unpack this to the correct location as per the comments in the link. It looks like it should be here:

/usr/share/apps/desktoptheme/default/widgets/luna.svg

You can always try to locate it:

updatedb
locate luna.svg

of course, su to root first so that you can update the locate database, and then search. A slower method without updating the locate database, would be something like this:

find / -iname luna.svg

Are you using an NVIDIA card? If so, right click the flash movie and click settings and then disable the hardware acceleration. It will then be OK.

As for the other error, please post exactly the error message, and will try to help.

I would say something hardware related, try running memtest and see what happens. I've had problems recently with an old laptop and the graphical display crashing on me, but from the console the laptop would work fine. Took the whole thing apart and cleaned it out, removing the CPU, memory and reseating all the components. I would try this and see what happens. Also go into your BIOS and choose the Load Optimised Defaults option to ensure no bad setting has been chosen in here. Incorrect memory config in the BIOS can cause hardware issues, I've had this as well.

The i915.modeset or nomodeset or other such boot options are only for when you start X, GDM, KDM etc and get a black screen and the system stops responding. This isn't going to help your X crashing problem. If you see X/GDM/KDM normally, then this is not going to help in this instance.

Having auto in fstab is a bad idea, because if you boot the machine without a disk in the drive it will attempt to mount something that is not there. If you have an fstab entry for it, it must be noauto.

If you don't have an fstab entry, you cannot just type:

mount /mnt/cdrom

because it doesn't know what device is attributed to /mnt/cdrom. Therefore you could then have to do something like:

mount /dev/cdrom /mnt/cdrom

or wherever you wanted to mount it. udev/dbus would need to be dealing with this that is why there should not be an fstab entry. I wouldn't expect the USB icon to be managing your CDROM since it's not a USB device. The CD/DVD should appear on your desktop and can then be accessible by double clicking it. And it's going to be read only unless you are using Brasero or K3B or similar which would be an application that uses the necessary tools so that you can write files to it. Otherwise CD/DVD that has something on it, will be readonly irrespective unless the session is re-opened in a CD/DVD burning application.

He's not saying it's a USB drive. He's saying, optical drives, like USB drives, don't need to be in your /etc/fstab. So for the /dev/sr0 line in your /etc/fstab file, place a # at the beginning of the line and save it.

If you have 2008.1 on your system, and the repos configured, you can easily find the version numbers of packages installed by using the gui application to search or:

urpmf --name package

replacing package with the text you want to search for, for example: firefox.

Hi John,

I can't tell you how to do it with drakwizard, or the MCC tools, but on one machine you'll need to make one directory accessible for sharing. For example /home. Then from the other machine, using MCC, you should be able to mount the partition somewhere else, so for example, you connect to machine1 and mount /home to for example /mnt/home (if this directory existed on machine2).

NFS is not browseable, this was why I suggested samba as it can be easily got at than compared to NFS.

Sorry I forget also about graphical partition tools such as gparted. I think mainly because I'm used to doing everything at the console.

Stand corrected :) MCC seems to do it then, so NFS better if no Windows systems about.

Yes NFS is good for Linux only hosts, although you have to mount from the command line or CLI, you cannot do it directly in konqueror or nautilus. With samba, you can, and so it's easily accessible without mounting it :)

I know John would prefer to mount in the gui, and not have problems for example if the other computer wasn't turned on when he attempted to access his files on the other machine. Although, this wouldn't necessarily need to be a major problem. With samba, you can access it on the fly without having to remember the sequence in ensuring one computer is on before the other as you would need to do with NFS.

I use NFS in the office with a NAS, but then it's always on and accessible :)

Hi John,

Console could be easiest in this instance, if the system is not recognising it. If you can't see it in konqueror or nautilus (depending on KDE or Gnome), then the easiest will be to open a console and then su and enter the root password. Once you are here, this is what you would need to do. First disconnect and reconnect the USB stick. Then do this:

dmesg

it should then tell you what USB device it found at the end of the dmesg, and which disk it assigned, for example, /dev/sdb. Once you know this, you can do this:

fdisk -l /dev/sdb

that's a lowercase L. It will list your disks in the system, and should also list the USB stick that you plugged in and from where it matched in dmesg. I would expect that only one partition is listed on the disk. If that is the case, you can then do:

fdisk /dev/sdb
t
b
w

t = toggle partition type

b = set to W95 FAT 32

w = save changes

it will then return to the command prompt. Once this has been done, you can do this:

mkfs.vfat /dev/sdb1

and it will create a FAT32 filesystem on the USB stick. You can then remove it and reconnect again to see if the system recognises it normally. Please be careful, substitute /dev/sdb in my example with the one that matches your dmesg output. Also from the fdisk -l listing, you can check that size of the USB stick to verify you have the right disk, if it's 16GB like you posted here.

Hi John,

If you wish to do it via MCC, then the easiest will be to install the drakwizard application which will add a ton of stuff to the MCC panel. Then you will be able to click and install samba to run on one machine, and then connect to it from the other one. You only need to configure the samba server on one of your machines. The other will just be a client which will access the server and allow you to copy files from it to that machine.

CloneZilla will be able to do it no problems in terms of data copy etc and should even sort out grub booting etc. If it doesn't boot, then the easiest option later would be to do this.

1. Install the new disk as the first disk in the system.

2. Attach the old disk as the second disk in the system.

3. Boot and install new system on the first disk.

4. Create a new home directory on the new disk.

5. Copy data later once rebooted from old disk to new disk - only data for your username in /home.

I think this minority share holder is a bit silly. I would have expected shareholders would accept funding to improve their financial position, rather than vetoing it, and possibly ending up with erm, nothing? :huh:

Try:

systemctl disable dm

Mandriva has systemd scripts and SysV also, so it could explain why it looks disabled, when in fact it's being controlled elsewhere.

Also check what else is in /etc/init.d and post back if it doesn't work:

ls /etc/init.d/

Please provide the output of:

chkconfig --list

and also add here the /etc/inittab:

cat /etc/inittab

Maybe there is a service loading. Check:

chkconfig --list | grep -i dm

to see if any services are here relating to display manager. Could be kdm, gdm, xdm, or something similar. I forget how Mandriva might have it, as I'm not using it right now.

Should work as it uses the Realtek 8069 module from what I know, this card has been about for a few years now. A post here recently mentioned this card.

iptables. Can also install webmin to configure it much easier than from the console.

From a bit of reading it should be detected, as it should use the Realtek 8169 module as it seems to be based on that, unless something has changed. An lspci can verify this I would expect.

Doesn't make sense on why some lowly previous main investor is blocking it, unless he's hoping to pick Mandriva up for nothing, or has some ulterior motive. Shady.

Removing the disk and booting the machine, should leave you with the disk missing. Adding a partition with fdisk, or whichever you normally use :) and changing the type to Linux raid autodetect. You won't add the 1TB to the array, since it won't be the same size. You'll create a separate array with the 1TB disk, but with the second disk missing. Then, when you've copied the data from the old array to the new array, you can then remove the 750GB disk and add a second 1TB disk and then add this to the array.

With /etc/mdadm.conf - if you have disks /dev/sdb and /dev/sdc as part of the array, and /dev/sdc is faulty, then you edit /etc/mdadm.conf and remove the info that corresponds with /dev/sdc and replace it with "missing". Look at my article I wrote ages ago:

http://www.linuxsolutions.org/index.php?option=com_content&task=view&id=25&Itemid=26

in particular:

Creating Arrays

Since /dev/sda is in use, we cannot add this to the array yet, so we will build the array with /dev/sda offline, and only /dev/sdb active.  This is how:

   mdadm --create /dev/md0 --level=1 --raid-devices=2 missing /dev/sdb1
   mdadm --create /dev/md1 --level=1 --raid-devices=2 missing /dev/sdb2
   mdadm --create /dev/md2 --level=1 --raid-devices=2 missing /dev/sdb3
   mdadm --create /dev/md3 --level=1 --raid-devices=2 missing /dev/sdb5
   mdadm --create /dev/md4 --level=1 --raid-devices=2 missing /dev/sdb6

here you can see, the part where I have /dev/sda missing but the array configured on /dev/sdb. When I then remove and replace /dev/sda with the new disk (eg 1TB), I would then add it later to the array. It's all in the link, it will tell you how to add the disk later, and then in /etc/mdadm.conf you replace missing with /dev/sda.