Installation and dual boot preservation

This forum is dedicated to advanced help and support :

Ask here your questions about advanced usage of Mageia. For example you may post here all your questions about network and automated installs, complex server configurations, kernel tuning, creating your own Mageia mirrors, and all tasks likely to be touchy even for skilled users.

Installation and dual boot preservation

Postby TeraKnewKnothing » Jun 23rd, '16, 17:00

Hello,

I am migrating from Mandriva One 2011 to mga1 586.

I have a dual boot with windows 7 home edition and Mandriva - soon-to-be Mageia.

My question is:

Will this new installation affect the current dual boot and jeopardize booting into windows?
TeraKnewKnothing
 
Posts: 9
Joined: Jun 23rd, '16, 16:57

Re: Installation and dual boot preservation

Postby doktor5000 » Jun 23rd, '16, 18:30

That depends how you do the "migration". In general only the update from Mandriva 2010.x > Mageia 1 is supported, as newer Mandriva versions are based on rpm5 and we are still based on rpm.org which leads to some incompatibilities.
See also https://wiki.mageia.org/en/Archive:_Mag ... riva_Linux
You would have to provide some more context information how you want to migrate the mandriva installation in particular.

Also, what is being currently used as bootloader? The Mandriva one or the windows one?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18020
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Installation and dual boot preservation

Postby TeraKnewKnothing » Jun 24th, '16, 06:46

I believe the bootloader is the windows one. I don't know how to check it though.

Besides that here is the result of an overnight attempt to install using

These two successive commands from root:

Code: Select all
urpmi --replacefiles --auto-update --auto


Code: Select all
urpmi --auto-update


There were 584 packages in the installation.

I remember during the installation at least two packages that were not installable but I went ahead and tried to install anyway.

RPM and Python were the ones not installable.



Code: Select all

Preparing...                     ###################################################################################################################
  540/584: radeon-firmware       ###################################################################################################################
  541/584: dkms-broadcom-wl      ###################################################################################################################
+ /usr/sbin/dkms --rpm_safe_upgrade add -m broadcom-wl -v 5.100.82.112-2.mga1.nonfree

Creating symlink /var/lib/dkms/broadcom-wl/5.100.82.112-2.mga1.nonfree/source ->
                 /usr/src/broadcom-wl-5.100.82.112-2.mga1.nonfree

DKMS: add Completed.
+ /usr/sbin/dkms --rpm_safe_upgrade build -m broadcom-wl -v 5.100.82.112-2.mga1.nonfree

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=2.6.39.4-5.1-desktop -C /lib/modules/2.6.39.4-5.1-desktop/build M=$(pwd)....(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.39.4-5.1-desktop (i586)
Consult the make.log in the build directory
/var/lib/dkms/broadcom-wl/5.100.82.112-2.mga1.nonfree/build/ for more information.
+ /usr/sbin/dkms --rpm_safe_upgrade install -m broadcom-wl -v 5.100.82.112-2.mga1.nonfree

Error! Could not locate wl.ko for module broadcom-wl in the DKMS tree.
You must run a dkms build for kernel 2.6.39.4-5.1-desktop (i586) first.
error: %post(dkms-broadcom-wl-5.100.82.112-2.mga1.nonfree.i586) scriptlet failed, exit status 4
+ /usr/sbin/dkms --rpm_safe_upgrade remove -m broadcom-wl -v 5.100.82.38-1 --all

-------- Uninstall Beginning --------
Module:  broadcom-wl
Version: 5.100.82.38-1
Kernel:  2.6.39.4-5.1-desktop (i586)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

wl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.39.4-5.1-desktop/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod....

DKMS: uninstall Completed.

-------- Uninstall Beginning --------
Module:  broadcom-wl
Version: 5.100.82.38-1
Kernel:  2.6.38.7-desktop-1mnb2 (i586)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

wl.ko.gz:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.38.7-desktop-1mnb2/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall Completed.

------------------------------
Deleting module version: 5.100.82.38-1
completely from the DKMS tree.
------------------------------
Done.
Installation failed:    file /usr/bin/multiarch-dispatch from install of multiarch-utils-1.0.13-1.mga1.noarch conflicts with file from package rpm-5.3.12-0.20110712.2.2.i586
        file /usr/share/info/cp-tools.info.xz from install of classpath-0.97.2-5.mga1.i586 conflicts with file from package libgcj12-4.6.1-3.3.i586
        gurpmi >= 5.7 is needed by (installed) drakxtools-13.58-1.mga1.i586
        python-rpm is needed by (installed) livecd-tools-031-48.noarch
        python-rpm is needed by (installed) smart-1.4-1.r951.1.i586
        urpmi >= 4.8.23 is needed by (installed) drakxtools-curses-13.58-1.mga1.i586
        multiarch-utils is needed by (installed) libncurses-devel-5.9-2.i586
        rpm is needed by (installed) locales-2.13-1.i586
        rpm is needed by (installed) locales-2.13-1.i586
        rpm >= 3.0.4-6mdk is needed by (installed) cups-common-1.4.8-2.2.i586
        rpm is needed by (installed) basesystem-minimal-1-3.mga1.i586
        error while checking dependencies
        gnome-python-gnomekeyring is needed by system-config-printer-1.3.1-4.1.mga1.i586
        error while checking dependencies
        file /usr/share/apps/ksplash/Themes/Default/1280x1024/background.png from install of mageia-kde4-config-common-1-12.1.mga1.noarch conflicts with file from package kdebase4-workspace-4.6.5-8.3.i586
        file /usr/share/apps/ksplash/Themes/Default/1920x1080/background.png from install of mageia-kde4-config-common-1-12.1.mga1.noarch conflicts with file from package kdebase4-workspace-4.6.5-8.3.i586
        file /usr/share/apps/ksplash/Themes/Default/1920x1200/background.png from install of mageia-kde4-config-common-1-12.1.mga1.noarch conflicts with file from package kdebase4-workspace-4.6.5-8.3.i586
        file /usr/share/apps/ksplash/Themes/Default/600x400/background.png from install of mageia-kde4-config-common-1-12.1.mga1.noarch conflicts with file from package kdebase4-workspace-4.6.5-8.3.i586
        file /usr/share/apps/ksplash/Themes/Default/Preview.png from install of mageia-kde4-config-common-1-12.1.mga1.noarch conflicts with file from package kdebase4-workspace-4.6.5-8.3.i586
        file /usr/share/apps/ksplash/Themes/Default/Theme.rc from install of mageia-kde4-config-common-1-12.1.mga1.noarch conflicts with file from package kdebase4-workspace-4.6.5-8.3.i586
        scim-client = 1.4.0 is needed by plasma-applet-kimpanel-backend-scim-4.6.5-1.2.mga1.i586
        error while checking dependencies




If there are any other commands I can run to better help with this please let me know.

Thanks.
Last edited by isadora on Jun 24th, '16, 14:21, edited 1 time in total.
Reason: Placed command-output in between [CODE]-tags for better readability ;)
TeraKnewKnothing
 
Posts: 9
Joined: Jun 23rd, '16, 16:57

Re: Installation and dual boot preservation

Postby TeraKnewKnothing » Jun 24th, '16, 07:07

I think it is the windows bootloader.

I should check first though. Can you suggest how to check ?

The installation of 541 of the 584 packages went ok.

I have the "set up boot system" in the Mageia Control Center.
But before I set it up I need to rule out if the windows boot loader is the one first.

If I boot out of Mageia now I can't be sure I can avail the original dual boot screen.

Thanks.
TeraKnewKnothing
 
Posts: 9
Joined: Jun 23rd, '16, 16:57

Re: Installation and dual boot preservation

Postby benmc » Jun 26th, '16, 11:29

Hello TeraKnewKnothing and welcome to Mageia.
TeraKnewKnothing wrote:I think it is the windows bootloader.

this is Mandriva 2011 bootloader (GRUB) menu from a virtual box, hence, no Windows entry.
Mandriva 2011.png
Mandriva 2011.png (8.46 KiB) Viewed 1345 times

If your boot menu looks like this, then you are using the Mandriva bootloader.
If it is text, it is likely to be the Windows bootloader

best regards

Benmc
benmc
 
Posts: 1205
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Installation and dual boot preservation

Postby TeraKnewKnothing » Jun 27th, '16, 04:42

Benmc et al.,

It is the windows bootloader I discovered. Thanks.

TKK
TeraKnewKnothing
 
Posts: 9
Joined: Jun 23rd, '16, 16:57


Return to Advanced support

Who is online

Users browsing this forum: No registered users and 1 guest

cron