dude67

Nice one, Lex!

Wow, I'm really impressed with that. Nice use of KDE4. Well done.

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!

From above:

 

   Loading ahci module
  Waiting for driver initialization
  mdadm: /dev/md0 not identified in config file.
  mdadm: error opening /dev/md0: No such file or directory

 

do you still get the mdadm error when you restart now that it was added to the /etc/mdadm.conf file? Is the error the same? I want to see if we've partially solved something here or whether it still complains about it.

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

Can you tell me if the /dev/md0 node exists?

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.

I seem to have these initrd files (and a lot more files with initrd in the filenames, but I'm guessing these are relevant):

$ locate initrd
	 /initrd						 
	 /boot/initrd-2.6.27-desktop-0.rc8.2mnb.img
	 /boot/initrd-2.6.27.4-desktop-1mnb.img	
	 /boot/initrd-2.6.27.4-desktop-2mnb.img	
	 /boot/initrd-2.6.27.5-desktop-2mnb.img	
	 /boot/initrd-2.6.27.7-desktop-1mnb.img	
	 /boot/initrd-desktop.img				  
	 /boot/initrd.img						  
	 /etc/sysconfig/mkinitrd

So I should (?):

mkinitrd initrd-2.6.27.7-desktop-1mnb.img 2.6.27.7-desktop-1mnb

I have had this problem for quite some time now, and would appreciate if you'd be able to help out.

I have set up my system with SW RAID1 (earlier problem here: https://mandrivausers.org/index.php?showtopic=74504 ).

But ever since I've made that RAID set-up I've been unable to update my kernel. I currently boot to

2.6.27.4-desktop-2mnb

Here's my RAID1 set-up:

$ cat /proc/mdstat
 Personalities : [raid1] [raid6] [raid5] [raid4]
 md2 : active raid1 sdc9[1] sda9[0]
	   506272256 blocks [2/2] [UU]

 md1 : active raid1 sda8[0] sdc8[1]
	   102398208 blocks [2/2] [UU]

 md0 : active raid1 sda6[0] sdc6[1]
	   20474688 blocks [2/2] [UU]

 unused devices: <none>

I've seen a few kernel version updates for Mandriva, but have been unable to use them as I would get this error when booting to

any other kernel version as the one mentioned above.

		   ...
  Loading ahci module
  Waiting for driver initialization
  mdadm: /dev/md0 not identified in config file.
  mdadm: error opening /dev/md0: No such file or directory
  Creating root device.
  Mounting root filesystem.
  mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
  Setting up other filesystems.
  setuproot: moving /dev failed: No such file or directory
  setuproot: error mounting /proc: No such file or directory
  setuproot: error mounting /sys: No such file or directory
  Switching to new root and running init
  switchroot: /dev does not exist in new root
  Booting has failed.

This is my current /etc/lilo.conf file:

# File generated by DrakX/drakboot

# WARNING: do not forget to run lilo after modifying this file
default="desktop_2.6.27.4-2mnb"
boot=/dev/md0
map=/boot/map
install=menu
keytable=/boot/fi-latin1.klt
raid-extra-boot=mbr
menu-scheme=wb:bw:wb:bw
compact
prompt
nowarn
timeout=100
message=/boot/message
image=/boot/vmlinuz
label="linux"
root=/dev/md0
initrd=/boot/initrd.img
append="splash=verbose"
vga=788
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/md0
initrd=/boot/initrd.img
append="splash=verbose"
other=/dev/sda1
label="windows"
table=/dev/sda
other=/dev/sdb1
label="windows1"
table=/dev/sdb
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80
image=/boot/vmlinuz
label="failsafe"
root=/dev/md0
initrd=/boot/initrd.img
append="failsafe"
image=/boot/vmlinuz-2.6.27-desktop-0.rc8.2mnb
label="2.6.27-desktoprc8-2mnb"
root=/dev/md0
initrd=/boot/initrd-2.6.27-desktop-0.rc8.2mnb.img
append="splash=verbose"
vga=788
image=/boot/vmlinuz-2.6.27.4-desktop-1mnb
label="desktop_2.6.27.4-1mnb"
root=/dev/md0
initrd=/boot/initrd-2.6.27.4-desktop-1mnb.img
append="splash=verbose"
vga=788
image=/boot/vmlinuz-2.6.27.4-desktop-2mnb
label="desktop_2.6.27.4-2mnb"
root=/dev/md0
initrd=/boot/initrd-2.6.27.4-desktop-2mnb.img
append="splash=verbose"
vga=788
image=/boot/vmlinuz-2.6.27.5-desktop-2mnb
label="desktop_2.6.27.5-2mnb"
root=/dev/md0
initrd=/boot/initrd-2.6.27.5-desktop-2mnb.img
append="splash=verbose"
vga=788
image=/boot/vmlinuz-2.6.27.7-desktop-1mnb
label="desktop_2.6.27.7-1mnb"
root=/dev/md0
initrd=/boot/initrd-2.6.27.7-desktop-1mnb.img
append="splash=verbose"
vga=788
																																								   71,1-8		Bot

Is there something I should add to /etc/lilo.conf? What am I missing here?

Do you have the right-click add to desktop option in lancelot?

No. Only the "Add to favorites" choice.

I was using lancelot and that doesn't provide the option. Added the mandriva menu and I can just drag and drop so problem solved.

 

Cheers

I can do drag & drop directly from lancelot...

What I do is this. First I unlock the widgets (I keep them locked usually). Then I find the app from lancelot menu and simply do a drag & drop to the panel (where I want).

If I want to move the application icons around in the panel, I'll simply click on the "gnome-foot" looking icon on the right and the panel is in settings mode. The alternative is to right click on the panel and choose "Panel settings". Then I can move the icons around and change the lay-out of the panel.