May 2007 - relnotes-content - Fedora Mailing-Lists

[Fedora Project Wiki] Update of "Docs/Beats/PackageNotes" by KevinFenzi

by fedorawiki-noreply＠fedoraproject.org

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by KevinFenzi: http://fedoraproject.org/wiki/Docs/Beats/PackageNotes?action=diff&rev2=97... The comment on the change is: Add note about liferea on x86_64 not being very usable. ------------------------------------------------------------------------------ This release of Fedora includes Python 2.5, which does not support Zope. As a result, the `zope` and `plone` packages have been removed from this release. Work is underway to alleviate this problem for Zope 3, and possibly create a restricted Python 2.5 implementation of Zope 2. Refer to http://wiki.zope.org/zope3/Zope3UsingPython25 for additional information. Users who require the `zope` or `plone` packages are cautioned to plan appropriately, and use virtualized hosts or other methodologies to support their Zope and Plone needs. + === liferea on x86_64 bit platforms unstable === + + The liferea RSS/RDF feed reader has a known issue compiled for x86_64 platforms. This issue will cause it to start taking up 100% cpu time and become unresponsive. + As a workaround until the bug is found and fixed, you can remove the liferea.x86_64 package from your system and install the i386 version. Note that you will need the firefox.i386 package as well. + See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231073 for more information on the issue. +

17 years, 1 month

1
0
0 / 0

[Bug 234021] Sound module not loading upon boot/restart

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Sound module not loading upon boot/restart https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234021 ------- Additional Comments From a1tmblwd(a)netscape.net 2007-05-06 03:11 EST ------- This thread, https://www.redhat.com/archives/fedora-list/2007-May/msg00300.html , seems to have commonality with the problem I reported. If I'm not mistaken this guy's card has a PCI interface. Better check for a module loading problem. ISA interface may not have anything to do with the problem. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

17 years, 1 month

1
0
0 / 0

RE: MedHelp 92632

by relnotes＠fedoraproject.org

17 years, 1 month

1
0
0 / 0

[Fedora Project Wiki] Update of "Docs/Beats/Installer" by PaulFrields

by fedorawiki-noreply＠fedoraproject.org

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by PaulFrields: http://fedoraproject.org/wiki/Docs/Beats/Installer?action=diff&rev2=114&r... The comment on the change is: Include note about LVM ------------------------------------------------------------------------------ ==== Disk partitions must be labelled ==== - A change in the way that the linux kernel handles storage devices means that device names like `/dev/hdX` or `/dev/sdX` may differ from the values used in earlier releases. '''Anaconda''' solves this problem by relying on partition labels. If these labels are not present, then '''Anaconda''' presents a warning indicating that partitions need to be labelled and that the upgrade can not proceed. + A change in the way that the linux kernel handles storage devices means that device names like `/dev/hdX` or `/dev/sdX` may differ from the values used in earlier releases. '''Anaconda''' solves this problem by relying on partition labels. If these labels are not present, then '''Anaconda''' presents a warning indicating that partitions need to be labelled and that the upgrade can not proceed. Systems that use Logical Volume Management (LVM) and the device mapper usually do not require relabeling. ===== To check disk partition labels =====

17 years, 1 month

1
0
0 / 0

[Fedora Project Wiki] Update of "Docs/Beats/Installer" by PaulFrields

by fedorawiki-noreply＠fedoraproject.org

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by PaulFrields: http://fedoraproject.org/wiki/Docs/Beats/Installer?action=diff&rev2=113&r... The comment on the change is: Editorial pass ------------------------------------------------------------------------------ ===== To check disk partition labels ===== - Partition labels can be viewed by booting into the existing Fedora installation, and entering the following at a terminal prompt: + To view partition labels, boot the existing Fedora installation, and enter the following at a terminal prompt: {{{$ /sbin/blkid }}} - In the list displayed, confirm that each volume line has a `LABEL=` value, eg: + Confirm that each volume line in the list has a `LABEL=` value, as shown below: {{{/dev/hdd1: LABEL="/boot" UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2" TYPE="ext3" }}} ===== To set disk partition labels ===== - For partitions that don't have a label, use: + For partitions wihtout a label, use the following command: {{{ su -c 'e2label /dev/example f7-slash' # ext2/3 }}} - For a vfat filesystem, use dosfslabel from package dosfstools, and for ntfs filesystem use ntfslabel from the ntfsprogs package. Do not reboot the machine without also updating the file system mount entries, and the grub kernel root entry. + For a VFAT filesystem use `dosfslabel` from the `dosfstools` package, and for NTFS filesystem use `ntfslabel` from the `ntfsprogs` package. Before rebooting the machine, also update the file system mount entries, and the GRUB kernel root entry. ===== Update the file system mount entries ===== - If any filesystem labels were added or modified, then the device entries in `/etc/fstab` must be adjusted to match + If any filesystem labels were added or modified, then the device entries in `/etc/fstab` must be adjusted to match: {{{ su -c 'cp /etc/fstab /etc/fstab.orig' su -c 'gedit /etc/fstab' }}} @@ -110, +110 @@ ===== Update the grub.conf kernel root entry ===== - If the label for the / (root) filesystem was modified, the kernel boot parameter in the grub configuration file also needs to be modified + If the label for the / (root) filesystem was modified, the kernel boot parameter in the grub configuration file must also be modified: {{{ su -c 'gedit /boot/grub/grub.conf' }}} A matching example kernel grub line is:

17 years, 1 month

1
0
0 / 0

[Fedora Project Wiki] Update of "Docs/Beats/Installer" by DavidTimms

by fedorawiki-noreply＠fedoraproject.org

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by DavidTimms: http://fedoraproject.org/wiki/Docs/Beats/Installer?action=diff&rev2=112&r... The comment on the change is: labels for upgrade: incorporate additions from Tom Horsley and Bob Styma ------------------------------------------------------------------------------ ==== Disk partitions must be labelled ==== - A change in the way that the linux kernel handles storage devices means that device names like `/dev/hdX` or `/dev/sdX` may differ from the values used in earlier releases. Anaconda solves this problem by relying on partition labels. If these labels are not present, then '''Anaconda''' presents a warning indicating that partitions need to be labelled and that the upgrade can not proceed. + A change in the way that the linux kernel handles storage devices means that device names like `/dev/hdX` or `/dev/sdX` may differ from the values used in earlier releases. '''Anaconda''' solves this problem by relying on partition labels. If these labels are not present, then '''Anaconda''' presents a warning indicating that partitions need to be labelled and that the upgrade can not proceed. ===== To check disk partition labels ===== @@ -96, +96 @@ For partitions that don't have a label, use: {{{ su -c 'e2label /dev/example f7-slash' # ext2/3 }}} - For a vfat filesystem, use dosfslabel from package dosfstools, and for ntfs filesystem use ntfslabel from the ntfsprogs package. Do not reboot the machine without also updating the file system mount entries. + For a vfat filesystem, use dosfslabel from package dosfstools, and for ntfs filesystem use ntfslabel from the ntfsprogs package. Do not reboot the machine without also updating the file system mount entries, and the grub kernel root entry. ===== Update the file system mount entries ===== @@ -105, +105 @@ su -c 'gedit /etc/fstab' }}} An example of a mount by label entry is: - {{{ LABEL=/f7-slash / ext3 defaults 1 1 + {{{ LABEL=f7-slash / ext3 defaults 1 1 + }}} + + ===== Update the grub.conf kernel root entry ===== + + If the label for the / (root) filesystem was modified, the kernel boot parameter in the grub configuration file also needs to be modified + {{{ su -c 'gedit /boot/grub/grub.conf' + }}} + A matching example kernel grub line is: + {{{ kernel /vmlinuz-2.6.20-1.2948.fc6 ro root=f7-slash rhgb quiet }}} ===== Test changes made to labels ===== - If partition labels were adjusted, or the `/etc/fstab` file modified, then boot the existing Fedora installation to confirm that all partitions still mount normally. When complete, reboot the installation media to begin the installer. + If partition labels were adjusted, or the `/etc/fstab` file modified, then boot the existing Fedora installation to confirm that all partitions still mount normally and login is successful. When complete, reboot with the installation media to start the installer and begin the upgrade. ==== Upgrades versus fresh installations ====

17 years, 1 month

1
0
0 / 0

[Bug 234021] Sound module not loading upon boot/restart

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Sound module not loading upon boot/restart https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234021 ------- Additional Comments From a1tmblwd(a)netscape.net 2007-05-05 02:33 EST ------- (In reply to comment #9) > I put a modified suggestion (to use /etc/modprobe.conf) in an appropriate > section of the release notes source: > > http://fedoraproject.org/wiki/Docs/Beats/Multimedia > > The release notes that appear on the ISO are already frozen for F7; this change > should appear in the Web-only notes that are updated and released with F7, as > well as in any updates to the fedora-release-notes package. > > Thanks for your release note. > Your suggestion does not work. I changed /etc/modprobe.conf as follows: [root@slowpoke log]# cat /etc/modprobe.conf alias eth0 8139too alias scsi_hostadapter aic7xxx install snd-sbawe rc.local is the default; i.e. [root@slowpoke log]# cat /etc/rc.local #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local Upon boot I got the multiple errors for modprobe.conf; i.e. May 4 23:09:00 slowpoke modprobe: WARNING: /etc/modprobe.conf line 3: ignoring bad line starting with 'install' Is "install" a new command for FC7? It does not work for FC6. Placing the modprobe command into /etc/rc.local definitely works. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

17 years, 1 month

1
0
0 / 0

[Bug 234021] Sound module not loading upon boot/restart

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Sound module not loading upon boot/restart https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234021 ------- Additional Comments From a1tmblwd(a)netscape.net 2007-05-05 01:57 EST ------- Reply to comment #11: Using the files below the sound module does not load on bootup: [root@slowpoke ~]# cat rc.local #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local [root@slowpoke ~]# cat /etc/modprobe.conf alias eth0 8139too alias scsi_hostadapter aic7xxx alias snd-card-0 snd-sbawe options snd-card-0 index=0 options snd-sbawe index=0 remove snd-sbawe { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-sbawe The output from lsmod is in the attached file lsmod.fail. The sound module loads on bootup using the patched rc.local: [root@slowpoke ~]# cat rc.local.new #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local modprobe -r snd-sbawe modprobe snd-sbawe The output from lsmod is in the attached file lsmod.working.txt. The sound module also loads on bootup if all references to snd-awe are removed from /etc/modprobe.conf and the modified rc.local is used; e.g. [root@slowpoke ~]# cat modprobe.conf.new alias eth0 8139too alias scsi_hostadapter aic7xxx dmesg outputs for the failed-to-load and the loading sound configurations are also attached. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

17 years, 1 month

1
0
0 / 0

[Bug 234021] Sound module not loading upon boot/restart

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Sound module not loading upon boot/restart https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234021 ------- Additional Comments From a1tmblwd(a)netscape.net 2007-05-05 01:54 EST ------- Created an attachment (id=154192) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=154192&action=view) dmesg from loading sound module configuration -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

17 years, 1 month

1
0
0 / 0

[Bug 234021] Sound module not loading upon boot/restart

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Sound module not loading upon boot/restart https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234021 ------- Additional Comments From a1tmblwd(a)netscape.net 2007-05-05 01:52 EST ------- Created an attachment (id=154191) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=154191&action=view) dmesg from failed-to-load configuration -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

17 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

relnotes-content May 2007