Page 1 of 1

Successful Install: M3 64bit iso / USB stick / Acer Netbook

PostPosted: Jul 8th, '13, 19:00
by ca-on-adam
Hi,

I am posting my experience installing Mageia 3 using a USB Flash drive, which had some quirks but was otherwise a success.

I used Unetbootin v.585(Linux) to put the M3 64bit ISO onto an 8gb flash drive.

On boot, Unetbootins "Default" boot entry resulted in a Kernel Panic, some message about not syncing with block 2,0. The "text" menu entry worked. I noted that any menu item using the kernel and initrd under "alt0/" worked.

Mageia reported not finding a CDROM, and offered to the user a huge list of drivers to choose to activate a hypothetical CDROM drive. Instead, I chose 'cancel' and was presented with alternate install modes. Choosing 'hard disk' allowed me to select my USB stick and proceed to the graphical phase of the install.

I chose the following i18n options: English-Canada, Eastern time, US keyboard. Internet was not made available at the time of install.

Instead of selecting Gnome or KDE, I chose custom and selected all checkboxes, to see if any errors occured. During the install, I got a message "Installation Failed" and exactly 15 packages were listed. After that, it dropped back to the Desktop Choice screen, where I picked KDE to hopefully reduce the number of needed packages to pull the install through to success. I advanced past the installation phase rapidly, luckily the installer recognized packages already installed.

At the Graphics Summary screen, I got another Installation Failed message, this time two packages directly related to the Proprietary Radeon driver for the chipset on this netbook. On running 'test' the screen froze and I had to reboot forcefully.

On reboot, I ran 'upgrade' to preserve the installation rather then reformat, no error messages encountered.

Finallly, booting into the resultant system, I found two things. First, the radeon drivers DID successfully install, despite the warning messages. Secondly, running a software update in the GUI, it automatically installed the 15 packages that were failed in the install, plus some odds and ends.

Although I went back and chose KDE only during the install glitch, I found that all the packages, including server software, were fully installed and launching at startup. So it didn't matter which option I picked getting thrown back to the earlier screen, I still got what I wanted.

All in all, it was rocky terrain, but I think it was braindead enough that anyone could have succeeded with a USB install. It certainly went a lot better then Fedora, who's installer decided to crash because the USB stick didn't have the filesystem label it wanted.