Mageia forum

Hi,

I tested the 32-bit installation DVD. During installation, I can move the frame of the installer (the right part of the screen), from partitioning screen until the end of the installation screen. Otherwise, when I tried to install Grub2 (I installed the system on a usb key with a single root partition, and placing grub2 in the mbr) but the system refused (too little space to install grub2). So I installed Grub1 (graphical mode) in the MBR of the usb key, and that's ok. On some choices (during installation), I must click twice for activate the choice.
Otherwise, I have not encountered others problems that these ones during the installation.

Bye.

Hi,

I found others bugs (after installation).

- In the MCC (part to configure sources), I added local repositories. But I can't edit the lines referring to these local repositories. The edit button is grayed
- Rpmdrake crashed. But i see that a new update was available. I have the new version from repositories. I will check if rpmdrake will crash again.
- MCC doesn't work through desktop menu (I tried with Cinnamon and LXDE). I can't launch it. Therefore, I must launch MCC through the terminal.

hi all

I tested the 64 bit KDE dvd install.

The installer slideshow / details window was over the left of the screen and covered the Mageia logo and info pane.

Dupo wrote:On some choices (during installation), I must click twice for activate the choice.

This was for me as well. The first click looks as though it lists behind the pane, the second brings it to the front of the pane.
I chose Grub 1 as my bootloader choice.
Upon reboot everything worked as normal.
Just have to test the pesky canon printer.

next result.
updated 438 packages and rebooted for new kernel - cannot login with user mode gui or in safe mode- password not accepted. oh dear
I'll try and find which package is the problem
complete reinstall and update
ah-ha. checked the user password before rebooting and note that the password length has changed. reset password and rebooted to new kernel - ok

cheers

Benmc

I've never had to do that, but...

The network card names used to to be eth0/9, and now i see

enp2s0u1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx # edited
inet addr:10.0.0.15
;
;
;
enp5s0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx # edited
inet addr:10.0.0.16

What have I missed, how is this supposed to work?

Network Device Renaming has been implemented as proposed:

https://wiki.mageia.org/en/Feature:Netw ... NameChange
https://wiki.mageia.org/en/Mageia_4_beta2#Base_system

Everything is supposed to work now. If something isn't working for you, you should open a bug.

Jim

benmc wrote:cannot login with user mode gui or in safe mode- password not accepted. oh dear
I'll try and find which package is the problem

Probably the setup package. When setup is updated you need to check very carefully any changes that it proposes to make to config files. It's usually safest not to accept any changes (i.e. do not use the rpmnew files).

Jim

Testing problem: GUI corruption following today's rolling update(s)

Greetings to all from this nooB!

Installed M4B2-Kde-live. Worked just dandy (sans a few minor glitches, since solved) for 3 days, until today: todays' (late-afternoon Jan. 9) rolling updates demolished my system's thus-far superb GUI (Nvidia 6200 LE AGP Video Card driving a 1600x900 HD Acer Monitor).

Apparently, these daily update(s) corrupted the original install's Nvidia-driver (non-free Nvidia 304.117) possibly with a partial/incomplete overlay by the X11-Nuveau (sp) driver, as some of the messages that popped up after rebooting suggested ... Anyway, in trying to salvage my system, I tried to remove then re-install my video card's non-free driver. Alas, with no effect whatsoever. Yes, i did shutdown & reboot a few times.

Basically, the desktop (thus the entire system) is now utterly unusable -- I am stuck for now. Any suggestions before I trash this M4B2?

Hi

Be aware that beta software is not recommended for " daily use " as this can happen:

adiosxp3 wrote:Apparently, these daily update(s) corrupted the original install's Nvidia-driver

.
There is a Red Banner at the top of the download page let you know this.

Please dont let this hiccup diminish your Mageia experience.
As you installed with the live cd you can probably " upgrade " your current install back to the original install, or just reinstall completely.
Then when updating, choose not to update the Nvidia driver.

If you can login in "safe-mode " try also "urpmq --list-media active "
you should get something like:

Code: Select all

[root@localhost home]# urpmq --list-media active
Core Release2
Core Updates
Nonfree Release2
Nonfree Updates
Tainted Release
Tainted Updates
Core 32bit Updates
Nonfree 32bit Release
Nonfree 32bit Updates

hopefully you enabled " non-free " and "tainted " repositories,
and " urpmi --auto-update "

If you want to use Mageia for "normal everyday use " I would recommend using Mageia 3.

Thank you -- i am well aware of beta-caveats

Tried recovery -- no success. Therefore, i bricked the live-install, now did a full install from M4B2-core. Will refrain from updates for now. Installer destroyed my Grub/2 multi-boot (other OS-volumes still there), and the partition-table now appears to be empty. Pilot error, perhaps? So there must be a difference between the live-install's "use available free space" and the core-install's similar option. Any idea how i can re0instate my multi-boot menu?

adiosxp3 wrote:Any idea how i can re0instate my multi-boot menu?

Yeah, restore the config and reinstall grub2 into the boot sector.

As you don't provide any details, like what partitions you have, where your bootloader is located it's not possible to give better advice.
At least provide the output of

Code: Select all

lsblk

or

Code: Select all

fdisk -l

as root and mention what grub you have located where, what doesn't work anymore and what it should be able to boot.
But best use a separate thread for that ...

My apology for this late reply.

By way of using the live "Boot Repair Disc", i was able to restore my original Grub2 multi-boot menu (5 distros including Mageia) and regained boot-access to the other 4 distro. However, the drive's partition table was still non-existent; therefore, I used the "testdisk" facility (part of said boot repair disc) and the prior boot-repair's log file & sector-data to create a new parition table using the sector mappings discovered/logged earlier. And yes, this was just a TEST system.

My concern: at the time when i did a full install of M4B2, i had 15GB unallocated/free space on the drive's extended partition. The installer properly displayed all my extisting paritions and said free space. After I elected the installer's "use avalable free space" option, the install went clean to completion, but wiped out Grub's existing multi-boot options, and left me only with 2 boot options: normal or safe -- nothing else on Grub's list. Later, when i booted with the Gparted-live cd, I noticed that the other 4 distros' patritions still existed. However, since the partition table itself was zeroed out (possibly by M4B2's installer, or "pilot error"?), Gparted-live was useless for repair purposes, so i resorted to the above BRD-solution.

I've since flushed the M4B2 partitions, will wait for a while, then may take a fresh look at your final release once the dust settles ... In any event, thanks for your help!

If you don't change the default options, the installer will always default to write the bootloader to the MBR, that is expected.