mageia 5 beta 1 testing

[wintpe]

So today ive been testing an install of mageia 5 beta 1

and i thought it worth sharing my expirience here, and overall its damm good.

first the hardware im testing with, as a refrence point, your expirience could be completly different with
different hardware.
CPU:phenom 1100T, memory 16 gig DDR3, motherboard amd SB990 based asus Crosshair V Formula bios 1703
harddisk Corsair Force 3 SSD 120 gig (blue)
GPU NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (GTX560 branded)
nic, dual bonded Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
monitor samsung 950 3D 120hts frame 137khts line
sound Creative Labs SB Audigy (rev 04)

install was pretty much the usual magia3/4 look, nothing suprising there, but the choice of desktop was not as id hoped.
there was the usual kde or gnome, or lxde, but no lxqt which i had hoped was going to replace the lxde selection.

i chose another , hoping it would get bundled in there, but all i got was icewm.

updates within the installer worked , fully, "no anoying bomb out like mga3/4 after just 3-5 packages, restart, udisk error"

logged in through icewm, and stared mcc, ran update , it found more updates, mainly kernel related.

then i added lxqt minimal, logged out and logged in with lxqt.

background was unselectable through the qt session settings i first had to run chbg to change from solid background to streached image before i could then use qt sessions to select the background.

I wanted to use kwin, rather than the default openbox, and had heard on the ubuntu grapevine that kwin was now seperate, and could be installed .

the kwin_x11 i installed definitly did not work, so that obviously does not apply to mag5.

the only option was to install kde4 minimal, (thats a joke, amorak is not needed for minimal kde, but still gets pulled in with kde-minimal, along with many other suplus packages)

anyway once kde minimal was installed, i could select kwin as the window manager in qt session settings logged out and logged back in, looking good
just like the mag3 rasorqt, although the fonts are all a bit bigger.

sorted out the graphics card settings using nvidia settings (vblank off if you want > 70 hts frame by the way)

saved the xorg.conf localy then wrote it back to /etc/X11

installed bino, that now works nice, without locking up the display like it did in mga3.

could not get palemoon to work, kept crashing, but thats not mageias fault, its precompiled by the palemoon people, so something incompatible there, that ill follow up, stuck with firefox for now.

my old thunderbird 2 still works fine, on mga5, but i need to add a libgnomeui 2 package otherwise it complained during install.

ardino works fine as long as you install the oracle 8 JRE, wont work with openjdk (thats the 1.5.8 beta by the way, needed for newer boards).

ninja-ide rpm installs fine, but will only start from a terminal, not the launcher, but that was also the case under mga3.

sound blaster audigy 6.1 works fine, as a sound card, not tested its high end midi features yet.

nics bond up fine, although not the change from ifcfg-ethx to ifcfg-enp6s0f0 and 1

the only issue i have had has been a repeat of a redhat known issue with autofs, described in a sperate post, which wont
affect most home users.

Otherwise a very good beta release (taking in consideration the updates ontop to 1st jan).

regards peter

[doktor5000]

install was pretty much the usual magia3/4 look, nothing suprising there, but the choice of desktop was not as id hoped.
there was the usual kde or gnome, or lxde, but no lxqt which i had hoped was going to replace the lxde selection.

Actually I added that in there, now it's gone again ... just saw that when I tried beta 2 installation two days ago
See http://svnweb.mageia.org/packages?view= ... ion=656028
Will have to check why it doesn't show up in installer.

[doktor5000]

Will have to check why it doesn't show up in installer.

The only lxqt packages on the DVD are lxqt-notificationd and lxqt-policykit ... have to check if there's enough space to add at least lxqt-minimal set of packages for the DVD.

[wintpe]

OK I had to rebuild my mageia WS above, due to a problem i caused.

I thought it worth sharing, in case anyone else had similar ideas, and would also be worth discovering a better solution to the problem.

I had two SSD disks, one the new neutrino disk, 256 and one the older sandforce disk 128.

I had mga3 on the 256, but realized it was not as quick as the sandforce, so when it came to building mga5, i wanted it moved back to
the sandforce.

however i left the mga3 system, on the 256 just in case mga5 beta turned out nasty.

anyhow, i was pleasantly surprised how mature the mga5 was, so i reset the 256 gig disk, (wiped it).

next time i rebooted, system was stuffed.

basically initrd in /boot on the mga5 system was referencing something on the 256 gig disk, and refused to start
without it.

i spend hours trying to reinstall boot loader in the mga5 beta DVD 's rescue more, and going into rescue mode trying to understand what had gone wrong.

I had also lost my mga3 system now.

so i booted into rescue mode, copied all the important configs off the mga5 system , and rebuilt it.

this time, i rebuilt with kde as the default windows system.

then did update within the installer, this time, update did the first 5 packages, restarted and then bombed out with udisk issue, as in mga4 and 3.

this must be a kde related issue, as this only happens with kde builds.

anyhow, rebooted, updated some more.

then installed lxqt minimal, added all the other packages i usually add, the background issue did not occur this time with lxqt.

i feel i got a better system second time round.

What I would like to know is how to rebuild an initrd, and get rid of the wring uuid reference that it had picked up, due to the way i did the first build.

and is there a way to fix the udisk error that the in install updates does with kde builds.

regards peter

[doktor5000]

What I would like to know is how to rebuild an initrd, and get rid of the wring uuid reference that it had picked up, due to the way i did the first build.

There were some recent threads on this topic. Please see viewtopic.php?f=7&t=7093 or viewtopic.php?f=7&t=8111
Best explanation was recently on one of our mailing lists, but currently can't find the mail again. This is what it said (with LVM):

Code: Select all

mkdir /mnt
mount /dev/vg-mga--root /mnt   *1)
mount /dev/sda1 /mnt/boot
 home? *2)
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /sys /mnt/sys
mount --bind /run /mnt/run
chroot /mnt
export DRACUT_SKIP_FORCED_NON_HOSTONLY=1
dracut -f

and is there a way to fix the udisk error that the in install updates does with kde builds.

Depends what that error exactly is?