arctic

mount -t /dev/hda /mnt It might be necessary that you specify the filesystem type, e.g. mount -t ext3 /dev/hda /mnt hda, hdb, hdc will be used if you have PATA harddisks, while sda, sdb, sdc will be used with SATA disks. If the partition is not mounted, you (logically) cannot chroot into it and thus cannot reinstall grub. ;) If you get stuck with commands, always try commandname --help (e.g. mount --help) first as it will explain the basics of any command (more information is available with "man commandname")

You can reinstall grub with the live-CD. It is a bit more complicated but should work. Boot the CD, mount the /root partition (mount -t /dev/hda1 /mnt) with root privileges from a terminal. Chroot into your system e.g. chroot /dev/hda1 You will be root user of your installed system from now on. Now run grub-install /dev/hda then exit and reboot. That should basically get you up and running again - unless you really borked your system.

When the computer is turned on, you will see the boot-menu Mandriva failsafe ... Right there, press e.g. the arrow down key and afterwards the arrow up key. This will bypass the usually active timeout mode (boot system X after X seconds automatically). At the bottom of the page , there should be an explanation for editing grub. Anyway, at this stage you should press "Esc" (sorry, I forgot to mention this before ), then "e". Yes, you can make permanent changes to grub from a Live-CD terminal. For this, you will have to mount the root partition in root mode, open the root partitions /boot/grub/menu.lst file and commit the changes. Do a bit of search on this board or in google. There are tons of pages that explain how to edit grub. If you need further help, let us know. :)

Try the following: At the boot-screen menu, hit "e" for editing the entry. You should get a display of the grub configuration. the important area is the "root" entry here, as it seems that it has a wrong pointer. Let's assume it lists root (hd0,0) and comes up with Error 17, then the hd0,0 entry is not configures correctly. Hit "e" again, edit the entry, so that it really points to the root partition you have, e.g. root (hd0,1) or root (hd1,0) This really depends on your setup. You can find out the partitions you have e.g. by booting the live-CD again, opening a terminal and launch the command as root: fdisk -l this will list all partitions of your system. In my case it shows: Platte /dev/hdc: 80.0 GByte, 80060424192 Byte 255 Köpfe, 63 Sektoren/Spuren, 9733 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Disk identifier: 0xe131e131 Gerät boot. Anfang Ende Blöcke Id System /dev/hdc1 * 1 1288 10345828+ 83 Linux /dev/hdc3 1289 1543 2048287+ 82 Linux Swap / Solaris /dev/hdc4 1544 9733 65786175 5 Erweiterte /dev/hdc5 1544 9733 65786143+ 83 Linux Platte /dev/hdd: 160.0 GByte, 160041885696 Byte 255 Köpfe, 63 Sektoren/Spuren, 19457 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Disk identifier: 0x000a37c6 Gerät boot. Anfang Ende Blöcke Id System /dev/hdd1 * 1 8926 71698063+ 83 Linux /dev/hdd2 8927 19457 84590257+ 5 Erweiterte /dev/hdd5 8927 19457 84590226 83 Linux the root partition has an ID83* entry (native linux), thus in my case, the entry could/should be: root (hd0,0) Once you have adjusted the setting, hit "Enter" and "b" for booting. Remember that these changes are temporary, thus if anything goes wrong it can be changed again and again. *= The IDs and their meaning: 0 Empty 9 AIX bootable 75 PC/IX b7 BSDI fs 1 DOS 12-bit FAT a OS/2 Boot Manag 80 Old MINIX b8 BSDI swap 2 XENIX root 40 Venix 80286 81 Linux/MINIX c7 Syrinx 3 XENIX usr 51 Novell? 82 Linux swap db CP/M 4 DOS 16-bit <32M 52 Microport 83 Linux native e1 DOS access 5 Extended 63 GNU HURD 93 Amoeba e3 DOS R/O 6 DOS 16-bit >=32 64 Novell Netware 94 Amoeba BBT f2 DOS secondary 7 OS/2 HPFS 65 Novell Netware a5 BSD/386 ff BBT 8 AIX

Hint: think back a few years and search for a famous speech performed by some ... errrm .... "guy" called Donald Rumsfeld. Cannot say more here, because it's off-topic and doesn't belong to this forum section. :D

Message repeat:

Nothing to add. Greg2 summed it up nicely.

Have you adjusted the power-saving settings in the kde-control center already?

Unplug all peripheral devices that you don't really need, too. Maybe a hardware problem...

Uh.. did you type all that when adjusting Grub? I always used copy&paste for that. :D ntldr looks way simpler and faster, that's for sure, but can you edit the boot entries at the boot-screen with ntldr? Grub allows you to change them instantly (nice feature in case things go wrong. JMHO).

Browsing problems with Firefox: https://mandrivausers.org/index.php?showtopic=30815 I don't know your level of computer literateness, but PHLAK is definitely not designed for newcomers but for very experienced users. If you want to start with Linux, better give Mandriva ONE or PCLinuxOS a try.

/me nods. A bug.

Check this. Might be the solution to your problem: https://mandrivausers.org/index.php?showtopic=30815

Well, as good as someone can feel after eating rotten fish by accident.

Why don't you set XP as the default OS in Grub then? It only requires you to change one number. ;) About the bugreports you listed (sorry, I didn't check bugzilla. Hehehe... when you are ill, the toilet has a higher priority), if the bug is known, then there is no workaround right now unless you do a network-install, which would/should install the fixed package (if there is one).

We fell asleep, I guess.. :lol:

Welcome aboard. :) First of all, you do not need the XP CD in order to restore the XP Bootloader. The Mandriva CDs/DVD do(es) have a rescue option which allows to restore the XP or Grub bootloader with two clicks. The summary screen and its Grub placement always worked for me. What you could do is to simply bypass the gGub-installation step when it is shown first and install Grub later, at the summary screen. If Grub gets installed in the MBR, then - of course - it is being accessed before any other Grub entry that you installed on any other partition. ;)

Welcome to the club.

I found that on the cooker mailing list. http://archives.mandrivalinux.com/cooker/2...05/msg03328.php Also check this, although it is rather old. Maybe it lists one thing that you missed when wheeling and dealing with both apps: http://dkukawka.blogspot.com/2006/03/kpowe...r-mandriva.html Hope it helps a bit.

Just a hint: If the old driver works well with Compiz, don't update it. "Never change a winning team."

Basically, in order to change the login photo in gdm, you have to adjust the user profile in Gnome. If you use KDE with gdm, then a change of the user-picture won't have any effect as gdm is the Gnome login manager. Same thing would happen if you use Gnome but use kdm for logging in. Changing the Gnome user-picture won't affect kdm. The only way to change it system-wide should be, as said already, through the MCC, system-section -> user settings.

I would check if it hangs again if you disable the 3D stuff. That might help to narrow down the problem.

Which kernel do you have installed (you should run the laptop-kernel)? Are there any pointers in /var/log/messages or ~/.xsession-errors?

Edit you /etc/urpmi/skip.list # Here you can specify the packages that won't be upgraded automatically # for example, to exclude all apache packages : # /^apache/

Uh... Dave Brubeck.