fedora_requires_release_note requested: [Bug 505846] After upgrading root partition to ext4, Fedora will not boot
by Red Hat Bugzilla
Product: Fedora
Version: 11
Component: mkinitrd
Alexandr Kara <sasakara(a)email.cz> has asked for fedora_requires_release_note:
Bug 505846: After upgrading root partition to ext4, Fedora will not boot
https://bugzilla.redhat.com/show_bug.cgi?id=505846
------- Additional Comments from Alexandr Kara <sasakara(a)email.cz>
* Description of problem:
After upgrading root filesystem to ext4, the system will not boot.
* How reproducible:
Possibly always (haven't tried multiple times)
* Steps to Reproduce:
change ext3 to ext4 in /etc/fstab for the root partition
# telinit 1
# mount -o remount,ro /
# tune2fs -O extents,uninit_bg,dir_index /dev/device
# fsck -pf /dev/device
# reboot
* Actual results:
Doesn't boot with a message like: "Cannot mount root filesystem, unsupported
options(40)".
* Expected results:
Normal boot
* Additional info:
To solve the problem, I modified the initrd image manually - I changed "-t
ext3" to "-t ext4" inside the "/init" file of the image.
I didn't run mkinitrd after filesystem upgrade, this might have helped.
I am adding this info in case somebody uses the same HOWTO and runs into
problems.
14 years, 10 months
[Bug 499585] clarify minimum hardware requirements
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.
https://bugzilla.redhat.com/show_bug.cgi?id=499585
A. Mani <a.mani.cms(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |a.mani.cms(a)gmail.com
--- Comment #3 from A. Mani <a.mani.cms(a)gmail.com> 2009-06-10 20:31:23 EDT ---
No problems on a
512MB RAM + ext4 + 2.0Ghz Single Core 64-bit Athlon (nvidia chipset)
(F11 x86-64 dvd install)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
14 years, 11 months
[Bug 504217] New: atl1e driver corrupts network data
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.
Summary: atl1e driver corrupts network data
https://bugzilla.redhat.com/show_bug.cgi?id=504217
Summary: atl1e driver corrupts network data
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: release-notes
AssignedTo: relnotes(a)fedoraproject.org
ReportedBy: bill-bugzilla.redhat.com(a)bfccomputing.com
QAContact: kwade(a)redhat.com
CC: wb8rcr(a)arrl.net
Classification: Fedora
There is an issue with network hardware driven by the atl1e driver under Fedora
11 that consistently causes network traffic corruption. Such hardware
includes, at least, some ASUS motherboards, newer eeePC models, and some
hardware from Acer. Where a different network card cannot be added, users who
depend on reliable network traffic would be advised to not upgrade from Fedora
10 to Fedora 11 at this time. This issue is being tracked in bz 503288.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
14 years, 11 months
[Bug 498757] New: mention lm_sensors changes
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.
Summary: mention lm_sensors changes
https://bugzilla.redhat.com/show_bug.cgi?id=498757
Summary: mention lm_sensors changes
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: release-notes
AssignedTo: relnotes(a)fedoraproject.org
ReportedBy: tom.horsley(a)att.net
QAContact: kwade(a)redhat.com
CC: wb8rcr(a)arrl.net
Classification: Fedora
Description of problem:
I was quite confused by the kernel changes that had the side effect
of disabling almost all the lm_sensors info. Bug 496355 shows my
confusion and the kernel changes which caused it as well as the
kernel boot parameter that can be used to get old behavior.
Seems like this would be good info to go in the release notes
somewhere (if it is already there, I couldn't find it).
The acpi_enforce_resources=lax boot parameter got back my sensor
data, and copying the /etc/sensors3.conf file from fedora 10 got
back my interpretation of that data.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
14 years, 11 months