Re: BuildRequires: sparse
by Roland McGrath
sparse-0.3-1.fc7 will be required by new kernel builds, so we think it
belongs in f7-final
16 years, 11 months
suggested one line patch to powernow-k8 for 65nm Athlon64
by Calvin Dodge
I'm the proud owner of a new "Lima" Athlon64, and was annoyed to see
that powernow-k8 didn't recognize it.
It turns out AMD bumped the revision number from 6 to 7, and
powernow-k8 doesn't like that.
At the suggestion of powernow-k8's maintainer (Mark Langsdorf) I
edited line 49 of powernow-k8.h and changed:
#define CPUID_XMOD_REV_G 0x00060000
to
#define CPUID_XMOD_REV_H 0x00070000
then changed CPUID_XMOD_REV_G in powernow-k8.c to CPUID_XMOD_REV_H
(actually, he just said "bump it to 7", but it seemed logical to
increment the revision letter, too)
This worked, and the cpuspeed daemon lowered the CPU frequency and
voltage when idling.
Anyway, Mark said he'd submitted a patch, but it hadn't made its way
to the main kernel source yet. Is there any chance the Fedora kernel
maintainers might add such a patch to the next kernel?
Calvin Dodge
16 years, 11 months
uswsusp with Fedora default kernel?
by Matej Cepl
Hello,
just a question, whether somebody made uswsusp working with
Fedora Core 6? Old kernel is unacceptably slow for me, and I need
ndiswrapper so kernel-suspend2 package is not an option, because
I would have to recompile the driver all the time. uwsusp being
in mainline kernel seems to be the only option, but apparently
uswsusp is not packaged for Fedora Core 6 -- of course, I could
package the program myself, but I am afraid of fiddling with
mkinitrd, which in Fedora seems to be extremely unflexible (or
may be I got it wrong).
Are there packages available somewhere where I haven't found them
yet, or could at least somebody point me please to some HOWTO on
changing mkinitrd (what should I do to make uswsusp work, and how
to made it into package)? And of course there are issues with
SELinux as well.
I have made experimental package available on
http://matej.ceplovi.cz/progs/rpms/suspend-0.50.20070328-6.3.1.src.rpm
(binary RPMs and .spec file are available in the same place), but
they don't work for me (because of SELinux, and because I haven't
modified mkinitrd).
Thanks for any hint,
Matěj Cepl
16 years, 12 months
Latest updates to the FC7 kernel
by Chuck Ebbert
Current version is 1.3132
* Thu May 03 2007 John W. Linville <linville(a)redhat.com>
- Add a locking fix to benefit rt2x00
* Thu May 03 2007 John W. Linville <linville(a)redhat.com>
- Update git-wireless-dev.patch (fix lockdep spew, zd1211rw-mac80211 fixes)
- Remove linux-2.6-zd1211rw-mac80211-queue-limit.patch (obsolete)
- Update git-iwlwifi.patch (signal level fixes, iwlwifi -> iwl3945 name change)
- Remove git-iwlwifi-fixes.patch (obsolete)
- Remove iwlwifi portions of linux-2.6-warnings-inline.patch (obsolete)
* Wed May 02 2007 Dave Jones <davej(a)redhat.com>
- Assorted dyntick/clock/timer fixes.
17 years
RHEL 3
by Majumder, Rajib
Hi,
I am wondering if RHEL 3 (based on 2.4.21 kernel but RH claims they backported lot of 2.6 kernel's feature into it) supports Multi-Core and Hyperthreaded CPUs.
Is the CPU-scheduler multi-core/hyperthreading aware? Is it aware ccNUMA multi-core CPU?
Any input is appreciated.
Thanks
Rajib
==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================
17 years
BuildRequires: sparse
by Roland McGrath
I've updated extras^H^H^H^H^H^HFedora devel sparse to 0.3 and built it in
Koji. I have no clue if magic is required to get it into the tag used for
new builds' dependencies. The following ought to be adequate to tweak the
kernel spec to use it rather than build it (assuming the old spec crap
wants to stick around conditionally for FC-6 copies).
Index: kernel-2.6.spec
===================================================================
RCS file: /cvs/pkgs/rpms/kernel/devel/kernel-2.6.spec,v
retrieving revision 1.3128
diff -u -b -p -r1.3128 kernel-2.6.spec
--- kernel-2.6.spec 3 May 2007 19:56:54 -0000 1.3128
+++ kernel-2.6.spec 3 May 2007 22:19:56 -0000
@@ -327,8 +355,15 @@ BuildConflicts: rhbuildsys(DiskFree) < 5
Source0: ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-%{kversion}.tar.bz2
#Source1: xen-%{xen_hv_cset}.tar.bz2
Source2: Config.mk
+
%define sparsever 0.3
+%if "%fedora" >= "7"
+%define buildsparse 0
+BuildRequires: sparse >= %{sparsever}
+%else
+%define buildsparse 1
Source3: sparse-%{sparsever}.tar.bz2
+%endif
Source10: COPYING.modules
Source11: genkey
@@ -1436,10 +1491,12 @@ find . \( -name "*.orig" -o -name "*~" \
cd ..
+%if %{buildsparse}
# unpack sparse.
if [ ! -d sparse-%{sparsever} ] ; then
%setup -D -T -q -a 3
fi
+%endif
# Unpack the Xen tarball.
%if %{includexen}
@@ -1462,12 +1519,15 @@ cd xen
%build
%if %{usesparse}
+%if %{buildsparse}
# Build sparse.
perl -p -i -e 's/-O /-O2 -finline-functions /' sparse-%{sparsever}/Makefile
make -C sparse-%{sparsever}
-
# Pass these options to kernel builds.
%define sparse_mflags C=1 CHECK=../sparse-%{sparsever}/sparse
+%else
+%define sparse_mflags C=1
+%endif
%endif
#
17 years
Fedora current Kernel
by Neshama Parhoti
Hello!
How can I tell what is the current kernel version of Fedora (5 and 6) ?
Of course without installing and running yum update kernel...
I want to know whether the newest kernel in those Fedora versions already
have KVM...
thank you
neshama
17 years
hardcoded mkinitrd dep?
by drago01
I was testing f7 kernels on fc6 recently to test iwlwifi and I noticed
that the kernel depends on a newer mkinitrd for (no?) reason...
I install the kernels with --nodeps and the boot up fine, the new initrd
also looks ok (has the pata modules etc.)
what was the reason for this?
a broken mkinitrd version between fc6 and the reuquired one that should
be avoided?
17 years
Pre-release kernel versioning
by Thorsten Leemhuis
Hi all!
I'd like to put a old but still valid discussion on the table again
where a solution never was found: Pre-release kernel versioning.
In short: Kernel like for example kernel-2.6.20-1.3066.fc7 are in
reality 2.6.21-rc6-git5. That's not only confusing to users, it also
breaks outside kernel modules sometimes; just yesterday I saw a patch in
3rd party repo applied that did this...
+-#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,21)
++#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,20)
...to make it compile against the kernel from FC4-test4 (no idea if it
helped, but I had to apply similar patches in the past nyself to make
somethign work), as the kernels in rawhide until they switched to
2.6.21-final announces itself as 2.6.20-1.3066.fc7 instead of
2.6.21-rc6-git5, as upstream would do.
I don't want to get further into the details if I don't have to, as this
stuff was discussed multiple times already on mailing lists. The last
time was here:
https://www.redhat.com/archives/fedora-devel-list/2007-March/msg00897.html
So, what will we do in the future? Can we (after F7 is out and rawhide
rolls again) please switch to something less confusing where version
somehow allows normal users to clearly see what kernel they got? And one
that doesn't confuse outside modules? Something like
kernel-2.6.22-1.3200.fc7.rc2.git15
maybe?
CU
thl
17 years
Keep the FC6 kernel at 2.6.20 or move it to 2.6.21?
by Chuck Ebbert
The number of bugs reported against the FC6 kernel is now dropping.
Should we move to kernel 2.6.21 and risk a whole new wave of bug reports,
or leave it on 2.6.20 and live with the fact that some things can't/won't
be fixed right, like support for PCI message signaled interrupts?
17 years
