New install, No Dual boot With Windows Vista
by Mickey
Fedora 18 new install.
Fedora didn't setup Windows Vista in boot Menu.
How do I get windows in Boot Menu.
Windows is still on Hard Drive at sda1 .
Below is /boot/grub2/grub.cfg.
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'
c96f7e74-f54e-4399-8956-202ea476ecd9
else
search --no-floppy --fs-uuid --set=root
c96f7e74-f54e-4399-8956-202ea476ecd9
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'
c96f7e74-f54e-4399-8956-202ea476ecd9
else
search --no-floppy --fs-uuid --set=root
c96f7e74-f54e-4399-8956-202ea476ecd9
fi
insmod gfxmenu
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-10.pf2
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-12.pf2
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-Bold-14.pf2
loadfont ($root)/boot/grub2/fonts/unicode.pf2
insmod png
set theme=($root)/boot/grub2/themes/system/theme.txt
export theme
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.11.4-101.fc18.i686)' --class fedora --class
gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-simple-c96f7e74-f54e-4399-8956-202ea476ecd9' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'
c96f7e74-f54e-4399-8956-202ea476ecd9
else
search --no-floppy --fs-uuid --set=root
c96f7e74-f54e-4399-8956-202ea476ecd9
fi
echo 'Loading Fedora (3.11.4-101.fc18.i686)'
linux /boot/vmlinuz-3.11.4-101.fc18.i686
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0
rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-3.11.4-101.fc18.i686.img
}
menuentry 'Fedora' --class fedora --class gnu-linux --class gnu --class
os $menuentry_id_option
'gnulinux-simple-c96f7e74-f54e-4399-8956-202ea476ecd9' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'
c96f7e74-f54e-4399-8956-202ea476ecd9
else
search --no-floppy --fs-uuid --set=root
c96f7e74-f54e-4399-8956-202ea476ecd9
fi
echo 'Loading Linux 3.6.10-4.fc18.i686 ...'
linux /boot/vmlinuz-3.6.10-4.fc18.i686
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0
rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-3.6.10-4.fc18.i686.img
}
submenu 'Advanced options for Fedora' $menuentry_id_option
'gnulinux-advanced-c96f7e74-f54e-4399-8956-202ea476ecd9' {
menuentry 'Fedora, with Linux 3.6.10-4.fc18.i686' --class fedora
--class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.6.10-4.fc18.i686-advanced-c96f7e74-f54e-4399-8956-202ea476ecd9'
{
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2
--hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'
c96f7e74-f54e-4399-8956-202ea476ecd9
else
search --no-floppy --fs-uuid --set=root
c96f7e74-f54e-4399-8956-202ea476ecd9
fi
echo 'Loading Linux 3.6.10-4.fc18.i686 ...'
linux /boot/vmlinuz-3.6.10-4.fc18.i686
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0
rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-3.6.10-4.fc18.i686.img
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_ppc_terminfo ###
### END /etc/grub.d/20_ppc_terminfo ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Vista (loader) (on /dev/sda1)' --class windows
--class os $menuentry_id_option 'osprober-chain-198AEF5376275C18' {
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'
198AEF5376275C18
else
search --no-floppy --fs-uuid --set=root 198AEF5376275C18
fi
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply
type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
10 years, 8 months
FC19, 3.11.6-200, and ATI video
by mark
I've just updated a user's FC19 box to the latest. No X. Period. I can use
xinit to get a window, but no fonts at all. Startx from init 3 gives me a
black screen.
When I look at Xorg.0.log, no matter if I have the radeon driver
blacklisted or not, whatever driver it uses is not for this kernel. The
proprietary one fails to build - as a start, it's still using
create_proc_entry.
The box has a FirePro 2260.
What can I do to get my user up and running, other than, say, installing
CentOS...?
mark
--
grub2 MUST DIE!!!
10 years, 8 months
Re: F18: Bind-chroot & Dovecot mount errors, how to fix?
by J.Witvliet＠mindef.nl
Uiteraard!
----- Oorspronkelijk bericht -----
Van: Tom Horsley [mailto:horsley1953@gmail.com]
Verzonden: Wednesday, October 23, 2013 12:15 PM W. Europe Standard Time
Aan: users(a)lists.fedoraproject.org <users(a)lists.fedoraproject.org>
Onderwerp: Re: F18: Bind-chroot & Dovecot mount errors, how to fix?
On Wed, 23 Oct 2013 16:30:19 +1030
Tim wrote:
> Since Fedora likes to put removeable media into /var/run/username/media
> you might encounter that problem again, unless you put /var/run into its
> ignore database.
It is worse than that. It apparently doesn't store the
ignored info anywhere, because if a mountpoint appears
again then disappears again, it will warn you again
no matter what you might have told it previously.
This appears to be another case of butt-headed developers
since lots of users have asked for a way to eradicate
this "feature" but the requests are always rejected
as "user is wrong".
I think I put in a syslog rule to just filter out all the
messages since there is no practical way to make them
stop.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
10 years, 8 months
X-Server fails to start
by Klaus-Peter Schrage
Every once and a while, say in 5 out of 10 boot events, the boot process
stalls and ends up in a text console
(kernel 3.11.4-201.fc19.x86_64, KDE 4.11.2-1, NVIDIA graphics card with
nouveau driver):
[snip]
Starting The KDE login manager...
[ OK ] Started The KDE login manager.
Starting Command Scheduler...
[ OK ] Started Command Scheduler.
Starting Job spooling tools...
[ OK ] Started Job spooling tools.
Starting Wait for Plymouth Boot Screen to Quit...
[ OK ] Started Machine Check Exception Logging Daemon.
[ OK ] Started Install ABRT coredump hook.
[ OK ] Started LSB: VirtualBox Linux kernel module.
Starting LSB: VirtualBox web service API...
Starting LSB: VirtualBox autostart service...
Starting LSB: VirtualBox balloon control daemon...
[ OK ] Started LSB: VirtualBox web service API.
[ OK ] Started LSB: VirtualBox balloon control daemon.
[ OK ] Started LSB: VirtualBox autostart service.
[ OK ] Started IPv6 firewall with ip6tables.
[ OK ] Started IPv4 firewall with iptables.
[ OK ] Started Login Service.
[ OK ] Started Network Manager Script Dispatcher Service.
[ OK ] Started LSB: DKMS kernel modules installer service.
[FAILED] Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details.
Starting Manage, Install and Generate Color Profiles...
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[end of output]
Sometimes there are a few more lines of output after FAILED, but the
boot process always finishes around that line.
The last lines of Xorg.0.log are:
[snip]
[ 45.416] (II) NOUVEAU(0): NVLeaveVT is called.
[ 45.417] (II) NOUVEAU(0): Closed GPU channel 0
[ 45.447] (EE) Server terminated successfully (0). Closing log file.
[/snip]
I can get to another text console, but doing 'startx' only gives me a
very rudimentary graphical desktop, not KDE.
I have searched bugzilla for the term 'Failed to start Wait for Plymouth
Boot Screen to Quit' with no results, and even googling didn't produce
anything to help me further.
Any help of the wise people on this list would be greatly appreciated.
KP
10 years, 8 months
Got myself in a bind
by Paolo Galtieri
I'm running F19 with all the latest updates. I did something as a
normal user that has made my system unusable. I'm running the mate
desktop and here are the issues I'm having:
1) No applets in the notification area except the date/time applet.
2) Only one of 2 Ethernet interfaces comes up. Even after rebooting.
3) The only desktop I can use is Mate, there is no option for me to
choose something else.
4) Why is one network interface labeled em1 and the other enp4s4?
What I did that may have caused the problem is to change the name of the
network interface as shown in nm-applet. nm-applet showed the name as
enp4s4 while ifconfig showed it as p5p1. After I did this I could no
longer get that interface to start. I tried deleting the interface and
adding it back in and I still could not get the interface to come up.
In fact at some point in time after stopping and restarting Network
Manager the p5p1 interface no longer showed up in nm-applet. Finally I
killed nm-applet assuming it would restart, but nothing happened. I
tried to add the notification area back in, but this doesn't work. I
can click on add to panel and select the notification area and click on
add, but nothing happens. I even tried logging in as a different user
and there was no nm-applet in the notification area. Running ps showed
nm-applet to be running as the user id I was logged in as, but it didn't
show up in the notification area.
So how the F*** do I get the notification area restored? and how the
F*** do I get Network Manager to see and configure both network interfaces?
Of course I can re-install F19 and re-download all the updates, but I
hope there is a better way than that.
Paolo
10 years, 8 months
Bit of a problem
by Roger
I have a HD with 2 partitions. Ubuntu 13.04 on one, primary boot is
through ubuntu grub and Fedora 19 on partition 2 which I use all the time.
Ubuntu13.04 ran into a problem yesterday during software update, it lost
the internet connection and errors out with a dialog to say internet
connection is lost.
I tried it again this morning with same result after checking the
internet and ensuring connection with fedora and ubuntu on eth0.
I do not understand why ubuntu loses internet during update when it can
download files and emails ok.
Ubutnu 13.04 has problem for me, I have run all the cleanups and tests
and run only the minimum of apps and there are no errors reported, but
it takes >30 seconds to start a terminal and another 50 seconds before
the prompt appears.
Because Fedora 19 is booted from the ubuntu grub partition I am
reluctant to reinstall a fresh ubuntu because if it trashes Fedora I
have major hassles re installing Rails and Drupal which are day projects
on both linuxes.
Is there any way I can change the boot to Fedora?
I am seriously considering reverting ubuntu to 12LTS which my daughters
run without a problem.
Will it be safe as in not trashing Fedora to do a fresh U-LTS install,
are there any gotchas I need to be aware of?
Does anyone else experience difficulties with Ubuntu 13.04?
Help very much appreciated
thanks in advance
Roger
10 years, 8 months
fedora19 cups 1.6.4 released Oct 11 broke printer
by Nate Pearlstein
I print from Mac OS 10.8.x to a Fedora 19 print server using hplip and the latest cups upgrades broke printing.
The output is severely stretched and large and some pictures are black.
Reverting to cups 1.6.2 using:
yum downgrade cups cups-filesystem cups-lpd cups-libs cups-ipptool cups-devel
fixed the problem. I would have gone back to the previous release cups 1.6.3 but yum downgrade seems to have picked the base fedora 19 cups not a previous update.
I'm assuming the change here: https://bugzilla.redhat.com/show_bug.cgi?id=1010580 caused it. if I knew what info should be collected I'd file a bug.
--
Nate Pearlstein - npearl(a)sgi.com - Product Support Engineer
10 years, 8 months
