dude67

What's the app?

No, that's not what he said: I believe he said that he can use 100gb out of the 120gb (means the recovery system uses around 20gb) and he has already made use of 40gb with some data. So, he has left 60gb, if I understood correctly. I'd use it exactly how Ian says: 20gb for / 1gb for /swap rest for /home

The KDE4 theme is called 'Elegance'.

Here's my new 2009.1 with KDE4.

Nice one, Lex!

Thanks! I myself am quite happy with that wallpaper (the earth - I picked it up from InterfaceLIFT: http://interfacelift.com/wallpaper_beta/do...s/rating/hdtv/) The desktop theme for KDE4 is Elegance.

Here's mine.

An update: I did file a bug (on Jan 25th) , but no news as of today in bugzilla. It was assigned to a team (Feb 13), but nothing new since (it's still marked as NEW even though it's labeled high priority and critical by the receiver). But, I just tried today to boot with the latest updated kernel version (2.6.27.19-desktop-1mnb) and it worked! I don't know what's been updated, but it works. I did a reboot with 'Linux' as the default kernel (i.e. booting automatically to the latest installed kernel version) and it is working fine. I'll wait a few days before reporting this to bugzilla, but it's looking good!

Here's mine. I got a new screen (23" 1920x1080 widescreen) yesterday!

Here's the screenshot

For me it opens up a pop up window, but the player doesn't show anything. It just says "Getting playlist - stopped". But for me it doesn't complain about the plugin. This is from my FF about:plugins for the Windows mediaplayer plug-in: File name: mplayerplug-in-wmp.so mplayerplug-in 3.55

I do like the black look on your desktop Ian (not ref. your wallpaper). I wish I could get something like that on my KDE4...

Thanks Neddie, the game is hilarious! BTW: There is an rpm version of the game on that site.

Nice. Me likes. In addition to the very nicely written content, the text is easy to read (neutral colours) and most importantly the text is not too long!

Yes, I think I should file a bug, unless someone comes up with a solution. I'll look into it and see if the bugzilla already has that bug filed. I'll post back the results. Anyway, thanks again Ian for you help!

Yes, I got the same error as before. And if I didn't bring this up earlier, I cannot boot to any other option (in Mandriva) than the current kernel - i.e. I cannot boot to e.g. failsafe or linux-nonfb...

I believe the error was the same, but will double-check. I'm currently at work and will check that tonight when I get home.

OK... Yes I can see them. With 'ls -l': brw-rw---- 1 root disk 9, 0 2009-01-13 19:47 md0 brw-rw---- 1 root disk 9, 1 2009-01-13 19:47 md1 brw-rw---- 1 root disk 9, 2 2009-01-13 19:47 md2

You mean this? (Sorry for my ignorance - I do appreciate your help!) $ cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md2 : active raid1 sdc9[1] sda9[0] 506272256 blocks [2/2] [UU] md1 : active raid1 sdc8[1] sda8[0] 102398208 blocks [2/2] [UU] md0 : active raid1 sda6[0] sdc6[1] 20474688 blocks [2/2] [UU] unused devices: <none>

OK. I removed the old "initrd-2.6.27.7-desktop-1mnb.img" file that already now existed and generated a new one. Still no luck.

Forgot to mention that I did run mkinitrd (the same I did before) after this, but it just said that it already existed (and obviously didn't generate a new initrd file).

Still no help with that either. :unsure:

I see that the md0 is not specified in the /etc/mdadm.conf file. Should it be? OK, it's there in the example, but how has it worked for me with this one kernel? I'll add this to the config file and reboot (with a newer kernel): ARRAY /dev/md0 devices=/dev/sda6,/dev/sdc6

# mdadm configuration file # # mdadm will function properly without the use of a configuration file, # but this file is useful for keeping track of arrays and member disks. # In general, a mdadm.conf file is created, and updated, after arrays # are created. This is the opposite behavior of /etc/raidtab which is # created prior to array construction. # # # the config file takes two types of lines: # # DEVICE lines specify a list of devices of where to look for # potential member disks # # ARRAY lines specify information about how to identify arrays so # so that they can be activated # # You can have more than one device line and use wild cards. The first # example includes SCSI the first partition of SCSI disks /dev/sdb, # /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second # line looks for array slices on IDE disks. # #DEVICE /dev/sd[bcdjkl]1 #DEVICE /dev/hda1 /dev/hdb1 DEVICE /dev/sda* DEVICE /dev/sdc* # # If you mount devfs on /dev, then a suitable way to list all devices is: #DEVICE /dev/discs/*/* # # # # ARRAY lines specify an array to assemble and a method of identification. # Arrays can currently be identified by using a UUID, superblock minor number, # or a listing of devices. # # super-minor is usually the minor number of the metadevice # UUID is the Universally Unique Identifier for the array # Each can be obtained using # # mdadm -D <md> # #ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371 #ARRAY /dev/md1 super-minor=1 #ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1 ARRAY /dev/md1 devices=/dev/sda8,/dev/sdc8 ARRAY /dev/md2 devices=/dev/sda9,/dev/sdc9 # # ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor # will then move a spare between arrays in a spare-group if one array has a failed # drive but no spare #ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1 #ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1 # # When used in --follow (aka --monitor) mode, mdadm needs a # mail address and/or a program. This can be given with "mailaddr" # and "program" lines to that monitoring can be started using # mdadm --follow --scan & echo $! > /var/run/mdadm # If the lines are not found, mdadm will exit quietly MAILADDR root@localhost #MAILADDR root@mydomain.tld #PROGRAM /usr/sbin/handle-mdadm-events 62,1 Bot

OK, did that, but it didn't help. I mkinitrd'ed and booted to that kernel, but I got the same result: Booting has failed.