Jump to content


Global Moderator
  • Posts

  • Joined

  • Last visited

Everything posted by arctic

  1. When you install Mandriva, IceWM is automatically installed by default as a fallback-alternative. When you are at the login-manager, you can select - using the symbols on the lower right side - the desktop-session you want to use. There should be options like drak3D, KDE, IceWM, secured session etc.
  2. Off-topic: Until yesterday, this laptop ran with Mandriva 2009.1 and KDE4. I still found it horrible to work with it and encountered many plasma crashes and freezes when customizing things within the control center. It is still bug-ridden, but is admittedly not as horrible as it was 6 months ago.
  3. Okay, if you are installing Mandriva from scratch, then you always have a backup-desktop with IceWM. You can apply from there some patches to your system using the Mandriva Control Center (MCC, aka. "Configure your computer"). I guess that you ran into one of the bloody KDE4 bugs. I used KDE4 myself for some time and found it horrible and bug-ridden, so I went back to good old Gnome. Try to apply the updates to your system for now, then let's see if it is fixed or if we need to take a closer look at your system.
  4. Welcome aboard. :) Just a basic question: Are you installing from scratch or are you really trying to "upgrade" Suse with Mandriva? In the latter scenario, trouble IS expected, as the two linux-distributions are very, very different from each other and not really compatible (Suse is looseley based on Slackwares architecture and system-design, while Mandriva is rather based on Red Hats architecture and system-design).
  5. arctic

    Fedora 11

    I have it already up and running on my laptop and so far it works very well. Pleasant colours, good behaviour, good response time and the Live-installer got better, too. Being a long-long-time Red Hat/Fedora user, I must admit that this release is way better than the previous two releases, which I found rather irritating. Seems as if the developers got back on the right track after making some weird decisions in the past years.
  6. Geocities does still exist? I thought it had died already years ago... :unsure:
  7. A very old announcement, indeed. :D In order to avoid any further confusion, I'll close this topic. ;)
  8. arctic

    KDE 4.3

    That is quite probable. After all, KDE 4 is rather new, has a completely new code and thus new bugs which will need some time to get sorted out. The concept of KDE4 is very good IMO, but the implementation still needs some serious work before I will even consider a migration to KDE. But then... Gnome 3.0 is currently being developed. ;) Who knows, maybe it will be great, maybe it will be horrible. If both desktops begin to suck, I'll probably switch to Fluxbox, Windowmaker, Rox or IceWM. :D
  9. arctic

    KDE 4.3

    I guess you are talking about Gnome 2.24 and 2.26, right? Nobody uses 2.2.6 anymore. :P Well, as you might know, I usually run Gnome and honestly, KDE uses way more RAM and CPU power than Gnome on my computers. (I switched from KDE to Gnome because KDE was becoming a RAM-Monster already years ago.) An example: In Gnome, I can run Compiz and at the same time run 3D-accelarated games like BZflag without the system going crazy. If I run KDE and launch the same game, then the whole system starts to choke, to get hiccups because too much power is drawn towads the desktop-enhancing effects. And no, my systems are not that outdated: System A: 1,67 Ghz CPU, 1 GB RAM, 512 MB Nvidia card. System B :1 Ghz CPU, 512 MB RAM, 256 MB Nvidia, System 3: Dual Core 2,4 Ghz CPU, 4 GB RAM, 512 MB ATI. So... something is eating up the ressources in KDE :unsure: , way more than in Gnome - although Gnome also loves to eat RAM.
  10. arctic

    KDE 4.3

    I hope that they somehow manage to improve KDE so that it uses less resources instead of more with each new release. I found 4.1 and 4.2 to be rather resources-hungry.
  11. I found the artwork of all editions horrible.
  12. Currently I don't use Mandriva. I simply didn't like 2009.0, although it is hard to tell what I disliked except the graphics (bootloader, wallpapers,... looked like an amateurish early 90s OS to me...). Currently I run Ubuntu, but don't like it either. :lol: (rather slow and somehow doesn't feel right and... brown with orange... *shudder*) I want to install something else but haven't really decided which distro I'll install (Fedora? Debian? Arch? Other?) and .. I don't have the time needed for a reinstall right now...
  13. I know only one term in turkish: Güle güle. :)
  14. Welcome aboard and good luck with the forum. :) I'll move this to Portal News, where everyone will see the news. I hope that's okay with you.
  15. You should WORK, not play around! /me continues his work. ;)
  16. Before you even consider installing the Operating system, type startx and report the error you get. Also: please post the output of the command lspci especially the information about your video card. When you booted, there was once big "Failed" message visible in the video. Can you tell us exactly, which service it was that the system was unable to start? I couldn't decipher it on the video. Just a note: It's somehow weird that Fedora 7 ran on your system just fine (as it seems), while Mandriva 2009, which is newer and supports more hardware than Fedora 7 hangs up. :huh: In any case, it you are unable to get Mandriva running, there are many other distros available that you can test. (Distro-hopping can be quite some fun... from time to time :) )
  17. https://mandrivausers.org/index.php?showtopic=4638
  18. Welcome aboard. :) It could be several things that made the boot-process freeze. First of all, before you burn an iso image, you should verify that the md5sum is okay (=that the iso-image is in tiptop-condition). Secondly, it can be that some piece of your hardware is not fully compatible/not fully implemented yet into Mandriva. When the system boots, you can press "Esc". The bootup screen should then switch to a mode where you see what the system is doing, that is which services are initiated and which ones probably got stuck. Try that boot method and take care where the system says "Failed" instead of "OK". If you get a black monitor, it usually means that the graphical server didn't kick in. Could you tell us which graphics-card you have? That will probably make it easier for narrowing down the problem. The installation process is never started unless you tell the system do start the installation process. Once the instalaltion process starts, you will see several windows where you have to answer some simple questions/make decisions about your system setup. PS:: crtl+alt+del, if pressed twice will reboot the system. ctrl+alt+backspace will reboot the graphical server.
  19. arctic

    Mandriva won't boot

    Uh yes... Will edit it. :woops: Thnx, tyme. :)
  20. arctic

    Mandriva won't boot

    Please change the file so that it looks more like this as you did a reinstall with only two partitions (Check the UUID!!!! It could be different from my proposition): timeout 10 color black/cyan yellow/cyan gfxmenu (hd0,0)/boot/gfxmenu default 0 title linux kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=1e73fdac-def8-4859-afa2-99e6411c0cb0 noapic nolapic splash=silent vga=788 initrd (hd0,0)/boot/initrd.img If you have problems with the UUID, you can alternatively try /dev/sda and similar pointers. They should basically work. Hope this helps
  21. arctic

    Mandriva won't boot

    I guess we simply need to check if your grub (the bootloader) is configured properly. You do have two different UUIDs there (which is the first unusual thing that I see) and probably some paragraphs not placed correctly in your /boot/grub/menu.lst file (I had that once, too after a kernel update. Don't know why, but it happened). In order to fix that, we need to know a bit about your partition setup and harddisk-type. Please boot the live CD and run in a terminal the command "fdisk -l", which will list all partitions and harddisks of your system. Please post the result in here, as well as the contents of your /boot/grub/menu.lst file. (in order to do that you will have to mount the /root partition of your install. It can be done like this: root@linux:~# fdisk -l Disk /dev/sda: 80.0 GByte,blablablah Device boot. start end blocks Id System /dev/sda1 * 1 1216 9767488+ 83 Linux /dev/sda2 1217 9733 68412802+ 5 extended /dev/sda5 1217 1459 1951866 82 Linux Swap / Solaris /dev/sda6 1460 9733 66460873+ 83 Linux now run e.g.: root@linux:~# mount -t ext3 /dev/sda1 /mnt ... (that means: mount -t filesystemtype-of-linux-partition located at partition /dev/sda1 at mountpoint /mnt) Once, this is done, you can read the menu.lst file by navigating to the /mnt/boot/grub folder. If you need more help/info about mounting partitions, launch in a terminal mount --help or man mount
  22. Which Mandriva version are you using? BTW: I am using a cheap external card-reader for transferring my pictures (cost: 7 Euros). Way easier than dealing with the camera itself IMHO (especially if you have to transfer, as in my case, hundreds of pictures from several DSLRs to your desktop. :) )
  23. Just a tip: for mpeg4, I recommend (as already mentioned) to use the vlc multimedia-player. It just works with that file format, while others are quirky with mpeg4 from time to time.
  24. As Lex said, please give us some detail about the Mandriva-Version you are running, the Desktop Environment (KDE?) and such stuff. It is impossible to give you an answer if you only point us to "that window" which could be basically everything.
  • Create New...