Skip to main content

Bad, bad preupgrade!!

Writing from Rawhide about my frustration on preupgrade when it comes for triple boot. I have Microsoft Windows XP (used for Flash development and games) on first HDD, Fedora 10 on second HDD on which Grub reside in MBR and the now upgraded Rawhide on third HDD where its grub is set at the beginning of its partition and preupgrade occured.

Somehow, preupgrade also overwrite the first Grub it should not touch; it should only update the last grub from the third HDD. boot folder from the second HDD containing Fedora 10 is empty. How should I restore the boot folder from Fedora 10 now that kernel from Fedora 10 is good and practically linked with rawhide? See the image below



I submitted a bug report and let hope that problem will be resolved as soon as possible.
Labels:

Comments

Martin said…
er... you don't have /boot on separate partition as is default in fedora? If you have it's probably only a problem of the partition not being mounted into the [awful-and-totaly-not-rememberable-hash]/boot.

I am not sure about your case, but I usually dual boot Rawhide and Fn and have everything in one /boot. I just have to be careful not to format /boot during installation in order to not lost the kernel images... Of course grub.conf gets overwriten, but the old one is usually backed up in grub.conf.rpmnew or something. But I'm always doing fresh install so it might be different in your case.
Tue Apr 21, 02:02:00 pm GMT-7
Luya Tshimbalanga said…
Yes I have separate boot on each dedicated Hard Disk drive. It turned out to be a bug from preupgrade installed on second HDD that will write boot on the first Fedora partition it encounters and there were no way to specifically assign installation.

Fedora 10 has version 1.0.x and version 1.1.x that contains fixed issue just landed on test-updated.

In case of triple booting, I assign second distribution (Fedora in this example) on first partition of third HDD where it will be installed and change the main grub.conf with (root and chainloader).
Tue Apr 21, 03:22:00 pm GMT-7
Post a Comment

Popular posts from this blog

Summary of echo-icon-theme report on Virtual FUDCon

It was my first even conference on Virtual FUDCon which greatly saved time and money. In summary, echo-icon-theme will not be ready for Fedora 8 given the time constrains. Its guideline needs a rewrite started by Martin Sourada. The icons are now residing on echo-icon-theme repository which facilitates the access for contributors looking to add/update the icons. It also means the wiki page for EchoDevelopment will no longer upload icons and will serve as reference. The mouse cursors are not in the repository yet but will be available shortly. Mairin, Fedora Artwork team leader, suggested to use Tango guideline for icons smaller or equal than 24x24 while keeping the isometric view for 32x32 and above. Demitri Glezos thanked the team for the use of icons on his Transifex project . The set of icons is roughly 40 percent complete and users of other desktop environment like KDE are encouraged to test them and provide ticket to track issues. Be in mind the echo-icon-theme division tea...
4 comments
Read more

Using AMD RX Vega driver OpenCL on Fedora 29

The Raven Ridge APU is very capable processor to handle OpenCL inside some applications like Blender, Darktable and Gimp. Unfortunately, the current implementation from Mesa, clover, stuck to 1.3, is not supported. AMD released their driver 18.40 with OpenCL2.0+ targeting only Red Hat Enterprise Linux/Cent OS 6.10 and 7.5 in addition of Ubuntu LTS. The good new is the former rpm format can be used on Fedora. The graphical part of Raven Ridge is Vega 8, basically a cut-down of Vega56 or Vega64 meaning choosing either driver for RX Vega . The instruction is provided for extracting the rpm files but here is  some requirements for OpenCL: kernel-devel (provided by Fedora repository) amdgpu-dkms dkms libopencl-amdgpu-pro opencl-amdgpu-pro-icd Once done, applications needing OpenCL will automatically detect the driver located on /opt/amdgpu/lib64 . Blender will list as unknown AMD GPU and Darktable will enable it. OpenCL from official AMD driver enabled on Darktable ...
Post a Comment
Read more

Detailing the installation of AMD OpenCL rpm for Fedora

Revisiting the previous blog and freshly reinstalling Fedora Design Suite due to a busted boot, I look at the official guideline from AMD Driver for Red Hat Enterprise Linux 7.2 and write a way to improve the process of installing on Fedora 29 in this example. Extracting the tarball contains the following: amdgpu-install amdgpu-pro-install symlink to amdgpu doc folder repodata folder RPMS folder containing rpm package Executing the command ./amdgpu-install -opencl=pal --headless sadly failed on Fedora on that line: ./amdgpu-install -y --opencl=pal --headless Last metadata expiration check: 0:30:51 ago on Mon 19 Nov 2018 07:13:43 PM PST. No match for argument: amdgpu Upon closer look, the script failed to created a temporary repository on /var/opt/amdgpu-pro-local probably explaining why amdgpu metapackage name failed to display. Someone should investigate and provide a fix. At least, we find out Fedora support is available but unofficial. Due to its design, Gnome ...
Post a Comment
Read more