This is in regard to the issue that, when Linux is hibernated, upon
reboot the thaw starts immediately and the grub menu is not presented.
I am now absolutely convinced this is not a BIOS issue, it is a kernel
or boot loader issue.
I worked around it by adding a level of indirection to the boot process.
To do this requires that you have at least one Linux partition that is
not / or /boot.
The basic idea is that Linux is booted with a chainloader, same as
Windows. So the main grub menu gives you a choice of Linux or Windows,
and both are implemented with "chainloader +1" stanzas. It works, but I
don't recommend trying this unless you are fairly familiar with how the
boot loader works, and are comfortable reinstalling the boot loader from
a rescue CD/DVD if something goes wrong.
The high-level instructions go like this:
1) In your extra Linux partition, create "boot" and "boot/grub"
2) Copy the contents of /boot/grub to this new grub directory.
3) Edit the boot/grub/grub.conf file in this new directory so that
Windows and Linux are presented as "chainloader +1" stanzas.
4) Install grub in the master boot record, pointing to this partition
5) Install grub in the first sector of your root partition, with the
usual kernel choices.
When this is done, at boot time you get a choice of Linux or Windows. If
you select Linux, the second boot loader comes up with the usual choice
of kernels. If Linux is hibernated, you can then boot and run Windows
just fine (my Windows install doesn't have a hibernate option so I
wasn't able to test hibernating Windows in this scenario). If you boot
again and select Linux, instead of getting the choice of kernels, it
immediately resumes the hibernated image. This is how I *want* it to
work, so I have left it this way.
Suppose you have this:
/dev/sda2 Linux root
/dev/sda3 Linux /local
Then /boot/grub gets copied to /local/boot/grub, then
edit /local/boot/grub/grub.conf so that you have something like this:
grub> root (hd0,2)
grub> setup (hd0)
This loads the master boot record that points to /dev/sda2, the
Now edit /boot/grub/grub.conf and remove the Windows stanza (you don't
need it here any more). Then run:
grub> root (hd0,1)
grub> setup (hd0,1)
This loads grub into the first sector of the Linux root partition,
pointing at that partition and presenting the usual choice of kernels.
This has worked great for me. I can now hibernate Linux, boot into
Windows, and later resume from the hibernated Linux image.
I installed fedora 12 (English version) on a Dell R300 server, as well as
SVN and Trac, after I imported files into Linux, all files named in Chinese
became black squares or question marks when listing them, and there were
additional strings "invalid encoding" attached after each filename. In
addition, Chinese font in Firefox looks not pretty, some are big, and some
I installed cjkuni-fonts, cjkunifonts-uming fonts, and also setup locale to
zh_CN.UTF8, but it didn't get me any luck.
Could anyone help me with this? I appreciate any response.
I have a Hauppauge WinTv-HVR 1800 tuner with an analog Cable TV (NTSC -
Canada). In F12 I received a near perfect video picture from my cable
TV. In F13, the picture is black and white with various degrees of
interference lines depending on the tv channel.
I have played with (used) TVTime quite a bit in the last 3 or 4 years so
I am familiar with all the menu settings and the configuration file. No
matter what I try, I can't get the proper reception back.
I still have no analog sound for this tuner, but I see that as a
separate Alsa problem.
Any suggestions as to what I might be overlooking or might have
mis-configured with the video?
Fedora 13, Gnome 2.30.2
Evo.2.20.2, Emacs 23.2.1
With fedora 13, when I use Math:GSL, I get an error message:
Can't load '/usr/local/lib/perl5/auto/Math/GSL/Errno/Errno.so' for module
cannot restore segment prot after reloc: Permission denied at
/usr/lib/perl5/DynaLoader.pm line 200.
if I do not switch SELinux to permissive !!
IE I cannot use enforcing
Patrick DUPRÉ | |
Department of Chemistry | | Phone: (44)-(0)-1904-434384
The University of York | | Fax: (44)-(0)-1904-432516
Heslington | |
York YO10 5DD United Kingdom | | email: pd520(a)york.ac.uk
Latest F13 upgrades include two packages that "require" a restart:
evolution-data-server and GtkHTML.
... ?! Is it really necessary to *reboot* because two desktop
components have been upgraded? Shouldn't a logout/login be enough?
This sounds like overkill, specially if you're the only one using the
computer (i.e. there are no other users using those libraries/services
besides you -- *if* you're using them). I don't even use Evolution!
Isn't there any more clever way of determining if a reboot is really
necessary? Or maybe at least the message should be less "demanding", I
don't know... it really seems unneeded.
I used to be proud of Linux only needing a reboot when the kernel (or
some key component) was upgraded. This is sadly feeling like "those
good old times" :-(
In a sudden changing manner, now if I try to update the system, using
[fedorax@localhost ~]$ su -
[root@localhost ~]# yum update
It doesn't prompt me to type in 'y' or 'n' if some downloadable update
is there unlike earlier when I used to type in 'yes' to download a
particular package of some size and update the system. Not only in
this command but in some other commands also, I have the same thing
repeating when I am not being prompted for tying in 'y' or 'n' for the
confirmation of download. Why could this happen all of a sudden?
Quite often the fonts in a web page, or printing something from within
Firefox looks blurred. Here is a sample screenshot:
It's a random page I chose to exhibit the problem. Printing web pages
also looks like crap, but perhaps that's something to do with the
Is it possible this is instead the driver for my video card? I'm using
a dual-head HD5700:
[ 35.548] (--) PCI:*(0:6:0:0) 1002:68b8:174b:e147 ATI Technologies
Inc Juniper [Radeon HD 5700 Series] rev 0, Mem @ 0xd0000000/268435456,
0xfe9e0000/131072, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[112179.601] (II) RADEON(0): Modeline "1680x1050"x0.0 146.25 1680
1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
Are there other driver choices for this card with FC13, like perhaps
one that supports the 3D acceleration?
In any case, I recall seeing a doc that described how to install the
Windows TT fonts, but can't find it now. I believe it was also for an
A friend has a PC with
windows only on the main boot disk,
and another windows + F13 on the second disk.
Because he did not install grub on sda, he can only boot
windows on sda. Bios boot menu does not allow him to
select the second disk for booting. Only way he can
boot second disk is by disabling main disk (sda) in bios,
and then bios will boot from the second disk.
Since I do not have such a setup, nor such a PC, I needed
to find out the following:
if main disk is disabled in bios, and fedora is booted
from 2nd disk, is boot disk named /dev/sda as far as
Fedora is concerned? Or is it named /dev/sdb ??
So, now if he wants to use grub-install to iinstall the
boot loader onto the bios-disabled-drive,
a- is that drive visible to Fedora?
b- if it is visible, what will it's name be?
c- Assuming it is visible and Fedora names it /dev/sdb
and he runs: grub-install --recheck /dev/sdb
will grub-install attempt to put the grub image files in
the root directory of /dev/sdb??
(Note: as explained above, the main boot drive, disabled-in-bios, is all
a windows drive).
I am concerned that grub-install might damage windows.