mga6 dev 1

[wintpe]

downloaded and installed mga6 dev 1

installing it on a PC ive had that is usualy a bit difficalt

hw is asrock nf3-vsta am2 + board phenon 1 9650 2.3 gig quad core

nvidia 6800GT

overall a typical mga install

on login in to plasma wayland, just black screen and had to hit cnt alt del to get out of that as the usual would not work.

logged in the standard plasma, and the mouse went into a slow step mode, the whole of plasma is doing something that makes it look like id installed
it on a 486 box with 4 meg of memory (of that was possible), totally unusable.

logged in using icewm , performance issue gone, and works perfectly as far as i could see.

went to do a software update, no network looked at the network settings with ifconfig, all looks normal
got ip address, default router dns etc all from dhcp no problem, but cant ping traceroute or establish any outbound connection.

went into mga control center network changed use network mangler automatic to no

and network now bounced into life, run update 820 aprox packages

after the update no improvement in plasmas performance, just not usable.

let me know if these are already known issues , and ill file bugs for those that are new

regards peter

[pete910]

I will give this a go on my AMD GPU, Would like to test their new driver, Having a quick glance at cauldron repos, They have mesa 11.2.1 already built

If am honest am not that keen on how plasma looks , may be change scares me due to age

[pete910]

Update:

Installed on a old 80gig hdd (GOWD THEIR SLOW)

Apart from been caught out with the boot loader saying mageia 5 seems to work fine.

Few minor bugs but nothing major. Actually plasma dont seem bad with the default setup that mageia has.

Defaulting to the radeon driver for me, Works fine, no issues like you've had winpe.

Need to recompile the kernel to use the amdgpu with mine though Not done that in while if am honest .

Quick Q winpe, On install did it give the normal boot config option? As in where to install the boot loader.

[wintpe]

thats interesting it could be the older nvidia driver

i prefer lxqt now, but i still use kde's kwin

so i added lxqt and logged in and it worked ok,

so i changed the window manager to kwin-x11

now lxqt has caught the slow as snail bug, and its so slow
i cant undo via the window system, so ill have to yank .config directory.

it must be a bug with this older (304) version of the nvidia driver, that goes with the 6800GT.

as its a quad core (i know its one of the oldest quad cores) but it was ok on centos 7

before i overwrote it with mga6 dev.

as i said in the begining of this thread i dont intend on using this pc

its just the first place i test all new os releases before i think about

my main desktop.

right now ill be thinking about that for quit some time.

mga5 is just so stable, i have no need to rush, but was interested in providing some feedback here for the
devs

regards peter

[ozky]

Are you peter use nvidia fglrx ? too bad if you use it it's not compatible with wayland yet you have to force and use only nouveau driver.

[DarkFoss]

Actually Nvidia released a new driver today 364.19 with Wayland support. They released a driver at the end of March with initial wayland support 364.12 as well.
http://www.phoronix.com/scan.php?page=n ... 9-Released
http://www.nvidia.com/download/driverRe ... 0577/en-us

[ozky]

Thanks i was hoping they will add wayland support.
This is good to those nvidia users,i don't own myself nvidia or amd graphics only intel.

[wintpe]

as i said above, its the 304 driver that goes with the 6800GT, which is now a 10 year old, but still a
fast card. It was the top of the range card when the 5200 era was current.

so the 36x driver simply does not support this card.

ill try using svga/vesa for now, but for others with older nvidia cards this slow issue with kwin could be a showstopper if it cant be fixed.

regards peter

[syschuck]

I just installed mga6 dev 1 on my older laptop. It's a Gateway AMD Turion x2 Model M-1625. While its old, it's been a very good laptop for linux. It was running Mageia 4 nicely, but I got a wild-hair to install Mageia 6. I'm posting this message from it, so I was successful but two things got me. First, I had Mageia4 installed on the boot disk with root / using an XFS file system. When Grub boot's it doesn't recognize the XFS filesystem as a valid filesystem and throws an Error 17. A couple of google searches lead me to ubuntu that had all kinds of wrong advise. What I found was If you have XFS as your root/boot in the install select grup2 in the boot loader and things will go smooth. Maybe Mageia 6 should select grub2 by default?

Editorial: I'm not a fan of cryptic error messages like Error 17 without the software providing an explanation of the error. In the old days of limited memory systems every byte counted, so something like: ERR17 was acceptable and kept the message to 5 bytes. Since limitations like that don't exist in modern systems, can we be a little more vocal about the issue; in this case Error 17 should say something like; "Error 17. This error occurs when grub version 1 does not have the proper library installed to read your / partition to continue with a stage 2 boot process. Too resolve this error, we recommend that you install and use grub2 as your boot loader on this type system"

Anyway, its just an idea.

I had issues with the installer's graphics, but that was minor. Once I was up and running, I had troubles with the touch pad on the laptop. Double taps didn't work as a button press by default. It took a few minutes to find that in the KDE settings.

The good news is that everything seems to be pretty decent. Thank you developers a very nice preview.

[doktor5000]

What I found was If you have XFS as your root/boot in the install select grup2 in the boot loader and things will go smooth. Maybe Mageia 6 should select grub2 by default?

You should probably report that as an enhancement bug, same as what was did e.g. for btrfs where this works like you described.

Please report that as an enhancement request, after searching if it hasn't been reported yet already: https://wiki.mageia.org/en/How_to_report_a_bug_properly

[petedan10]

I tried a mate installation on my AMD GPU and after the installation got through I found a few quirks as well, like selecting something from Places menu results in Audacious trying to open it. Also didn't have the option to select open source AMD driver or not, though graphics worked fine for my limited testing.

[syschuck]

I thought I would report on the latest mageia 6 dev 1 install. I just bought a new 512GB SSD to be installed in my AMD A10-6800K APU with Radeon(tm) HD Graphics 4100 MHZ. I had mageia 5 installed on a 1TB HHD SATA1 (/dev/sda) and wanted the SSD to become the new boot drive. The BIOS is from MSI with some simple OC features. It boot mode was Legacy + UEFI. I had a very difficult time getting the BIOS to boot and it would always drop me into a confusing, useless, and annoying UEFI boot shell. That's not Mageia's fault, but this goofy implementation of the UEFI boot system. So with the 512SSD on SATA4 (dev/sdb) I booted and installed Mageia 6. I wanted to do a custom partition using XFS instead of ext4 (or is it using brtfs for the ext4 label?). I made sure it was using /dev/sdb and wrote the boot track but it looks like it simple update grub on /dev/sda. Anyway after installing the OS and reboot at the end, UEFI only showed SATA1 as being bootable. After a couple of false starts at trying to repair the boot sector, I decided to remove the HDD and only have the SSD installed (after a tweek the the UEFI bios again) I booted and began the install. I tried the custom partition again but it would not let me change anything, so I went with the ext4 (brtfs?) defaults with 4 partitions (That maybe a Mageia bug). The /dev/sda1 (/boot/EFI FAT32 partition), /dev/sda2 (ext4) /, /dev/sda3 (swap), and /dev/sda4 (ext4 /home). The installation was very fast for 7GB worth of software. SSDs are awesome. Once installed everything worked really nice. I really liked the modern look and background was kind of refreshing. I reinstalled the HDD and selected the SSD as the primary UEFI boot device.

After the reboot, I had trouble with the graphics this time. Plymouth kept dying. This machine was in AMD Dual graphics mode. In addition to the APU it had a Radeon 7670, so I disable the AMD APU graphics, and told the bios to use the external Radeon. That fixed the issue at the expense of loosing dual graphics mode (it's kind of like SLI on the Nvidia btw). After this little gotcha and 20 reboots later since I started, everything has finally working very nicely. Even the updates came in without problems and now I'm running a Kernel 4.6.2 with Virtualbox running my windows10 AD client I have to use at work. So it's looking very promising.

My take-away; UEFI reminds me of systemd, its just another way of taking something simple and making it as complex as possible. There may be a bug in the custom partitioning during installation which may be triggered by UEFI or the use of SSDs? Plymouth apparently does not like AMD Radeon dual graphics mode.

[benmc]

Places menu results in Audacious trying to open it

https://bugs.mageia.org/show_bug.cgi?id=18659

[RAIDENSUB]

This is the story of how i mess up my pc. I am not an expert with linux.
I few days ago i installed mageia 6 dev 1 in my pc using a usb with the x64 iso and uefi. My pc has a samsung 240gb ssd formatted in gpt for Windows 10 , and i have two partitions 15gb each for / and /home. I also have 1tb hard disk for my data. When i was in the partitioner i could see a 100+mb partition that i thought was the efi partition and i added the partition. The problem was that it was the msr partition and after the install windows wouldn't boot. In other distros the installer isn't showing the msr partition. Maybe mageia's installer should hide that partition. I know this was my fault, i was in a hurry and i didn't see that the installer had already mount the efi partition.

Sorry for my english