List, good evening,
Our F24 installation in dual boot mode with Windows 7 has stopped W7
from booting from the Windows menu choice in Grub's screen. F24,
nevertheless, boots and operates fine.
Here are the installation details. We have a new laptop with Windows
7 pre-installed, which we'd configured for use, and backed up. The
BIOS is set for UEFI with legacy settings. Since W7 had occupied the
whole SSD we've upgraded the SSD (cloning the W7 SSD onto the new SSD
using dd) and then rechecked, and tested, W7 running on the lower
228GB of the new SSD; all was fine. We installed F24/Xfce/64 from its
'live' spin onto the the remaining (approx 250 GB) segment of the SSD,
allowing it to auto-partition. Installation proceeded without error;
gparted showed that F24 had created 2 more partitions above the W7
partitions. On reboot, Grub starts fine, the F24 selection boots
perfectly into F24, but selecting Windows just causes the machine to
'hang', showing a constant cursor in the top left corner of the screen.
Checks done so far:
1. Bios boot order now shows an additional item 'Fedora'. Switching
this 'Fedora' entry (in the Bios boot list) to below the HDD boot item
(in the Bios boot order) has no different effect.
2. Using the Grub CLI to set the root, the chainloader location, and
give a 'boot' command, has exactly the same effect as choosing the
Windows entry in the Grub menu - 'hang' with the constant cursor in
the top left corner. Grub CLI shows that the Windows boot partition,
and files, all seem to be in place (sda2,
3. Because some of our work activities require use of Windows, it was
essential to make sure we could get back to Windows, so we ran the W7
Windows System repair CD. This identified a problem in the UEFI
firmware and wanted to reset the 'fwbootmgr' item in the UEFI system
(NVRAM, apparently). We let it do this - aware that it might have
repercussions on the F24 installation that was working well but, since
it is relatively easy to re-install Fedora, we proceeded to let
Windows recover. But this had two effects:
(i) Windows rebooted quite happily, without a murmur. But it rebooted
only itself; Fedora's Grub menu never appeared.
(ii) Though the Fedora Grub menu had gone, checking the boot order in
the Bios we found that there was, now, a new entry: 'Windows Boot
Loader'. This was above another entry, 'Fedora' which was never
executing now because 'Windows Boot Loader' had higher priority order.
Switching the boot order in the Bios - to place 'Fedora' at the top,
and 'Windows Boot Loader' second - Fedora's Grub menu then appears on
booting up; F24 will boot and run perfectly, but selecting the Windows
choice in Grub's menus again 'hangs' (with a cursor in the the top
left corner). Setting the HDD to be at the top of the boot order gave
the same result as setting 'Fedora' at the top - F24 would load, but
Windows would not.
(i) UEFI seems to contain an 'order of booting'.
(ii) Fedora (presumably) makes a new entry in UEFI to point to its
Grub system on bootup - that aspect seems to succeed.
(iii) The chainloader sequence that Fedora employs executes a Windows
bootmgfw.efi (on this machine) which might be 'hanging'.
(iv) Might it be possible that the F24 installer has selected a file
other than that which Windows 7 itself *actually* uses when it boots?
Well, apologies for the length - I'd done quite a few checks and
thought it best to add those results to the post in case they help
narrow things down a bit. If anyone who managed this far has any
suggestions for some things to try or to check, I'd be very grateful.
In particular, I'd like to check which files W7 is using in its
initial boot - ie, that I could try to emulate with the Grub CLI. If
I could emulate a successful W7 boot, I could edit the F24 Grub
configuration and make the change permanent. Has anyone here tried
something similar themselves?
I update my Fedora Plasma desktop on a weekly basis. I have dnf tracer plugin installed.
On my weekly update I notice that I am almost always required to either restart the session or reboot the system. Both of these options are unacceptable because they require closing 10-15 apps and restarting them. That's unnecessary hassle and loss in productivity.
Fedora's all or none update system also doesn't make it easy. If I don't update system then I leave it vulnerable.
I am setting up a work machine and I have to decide if Fedora is appropriate for me or not.
Is the tracer plugin faulty or Fedora updates do require restarting session or system very frequently?
I have been using the "remind" calendar
program for a long time and I am now
having trouble reading the screen. It
provides a calendar page for the month
showing all 31 days on that page like a
conventional printed calendar.
Can anyone tell me how to make the font
bold and a little larger?
Better yet would be to also change it to
white text on black.
Any suggestions would be appreciated,
Bob Goodwin - Zuni, Virginia, USA
box10 FEDORA-25/64it LINUX XFCE Fastmail POP3
My trusty old IBM T30 laptop will no longer boot with the latest
It will still boot
The grub2 menu is displayed, and after selecting the 4.7.7-200 kernel
there's a 2-3 sec delay with blinking cursor, then I'm prompted for
the encryption passphrase for the /home filesystem. Then the
voluminous messages (from removing the rhgb boot option) scroll forth
and bootup proceeds normally.
However, If I choose any of the newer kernels, the blinking cursor
remains forever; no prompt for the encryption passphrase occurs; the
keyboard is totally non-responsive. Power cycling is required to
Things I've tried:
- dnf remove <the "bad" kernel>, and reinstall it.
- Rebuild initramfs-4.8.4-200.fc24.i686.img with dracut. The new file
is only one byte bigger, probably due to a different date, and still
- Added the secret 'dis_ucode_ldr' boot option, as revealed in
but this seemed aimed at newer IBM laptops, and indeed, had no
effect on my T30.
- Updated the BIOS. The T30 has two components: the BIOS and the EC
(Embedded Controller). My BIOS was up to date at version 2.10
but the EC was v. 1.03, while v. 1.07 was available.
Sadly, updating to EC v. 1.07 did not alleviate the problem.
Any thoughts, shared experience, commiserations, suggestions?
What can be so different about these newer kernels?
David A. De Graaf DATIX, Inc. Hendersonville, NC
I am trying to install F25 KDE 64 bit on an old HP Proliant with 2GB RAM
and a 2005 BIOS currently used in production (don't look at me, look at
the boss instead). The install is very very slow and took more than a
half hour to fsck the 2TB raid 1 disks. I only initially want to install
it on a free 20GB ext4 partition, no raid. Cannot unplug the 2TB disks.
Is there a way to avoid the useless half hour fsck?
I followed the instructions in the Fedora 25 Installation Guide and the DNF
system upgrade document, using `sudo dnf system-upgrade download --refresh
--releasever=25` and then the `sudo dnf system-upgrade reboot` command.
I then worked through an issue with the stock repositories and packages
causing my Nvidia graphics to lock up, and I eventually had a working
After a month of updates, I started seeing warnings about the size of the
var partition. Somehow /var/cache/PackageKit/24/metadata is still there and
very large. I tried `sudo pkcon refresh force -c -1` but I still have 3.3
gigs in PackageKit's Fedora 24 directory.
What would be a good course of action?
I'm reluctant to use root to just delete the files, assuming that they are
in some PackageKit database somewhere.
Is there another step that should be added to the DNF system upgrade
document to have this directory cleaned?
I have a program (c) calling a routine compiled by f95
In the c program I have a loop (calling the fortran routine) that
I wanted to paralleled by
#pragma omp parallel for
At the execution, I get:
Disk file read error number 5002
Type <enter> to exit program
All files have been compiled and linked with the option
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
I have to replace my graphic card and as the previous one was an nvidia
which has perfectly worked for 15 years, I want to remain with this brand.
Is the Gigabyte GeForce GT 740 ok to work under last version of fedora?
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
good day, Installed fedora25 - fully updated -installed xsane from repo - samsung scx4623f - works fine on various othet linux installed distros - multi boot setup.
No detection by xsane scanner - xsane from repo but no front or backends on system - unable to locate any installable software.
Kindly assist to get scanner working. Printer works fine. Thanks. Johan.