The F-12 branch is now for Fedora 12, and devel is now targeted for
Fedora 13. If you have updates that you don't expect to be upstream
soon, please update both branches.
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
On Sat, 29 Aug 2009 01:52:16 +0200
tom-ipp deve...@tom-ipp.info wrote:
Hello,
I assume it's the place to ask my question :
is there some known reason to not enable the module alsa snd-vxpocket,
for the digigram soundcard?
Otherwise, due to its audio quality, and despite of its long life, it
On Mon, 7 Sep 2009 14:27:24 -0700
Markus Kesaromous remotes...@live.com wrote:
Still not fixed:
arch/x86/kernel/pvclock.c:63:7: warning: __x86_64__ is not defined
It really is just a warning, arising because the kernel gets built with -Wundef.
On Wed, 22 Apr 2009 18:18:07 -0400
Chuck Anderson c...@wpi.edu wrote:
ERROR: Patch linux-2.6-build-nonintconfig.patch not listed as a
source patch in specfile
error: Bad exit status from /var/tmp/rpm-tmp.8pegaB (%prep)
this is due to the following code in ApplyPatch():
if ! egrep
On Tue, 28 Apr 2009 11:17:04 -0400
Chuck Anderson c...@wpi.edu wrote:
Great. I ended up having lots of other issues with vanilla build. At
some point during the build, the make oldconfig becomes interactive
during the %install phase. I answer all the questions with default
values
On Tue, 07 Apr 2009 21:44:19 +0100
Jeremy Sanders jer...@jeremysanders.net wrote:
Is there any reason the amd76x_edac module doesn't appear in the Fedora 10
kernel RPM? As far as I can see it should be being built from the
configuration.
We've got an AMD 790X based motherboard which
On Tue, 24 Mar 2009 16:17:24 -0400
Victor vicander...@gmail.com wrote:
Request for integrating this patch into the next kernel update for
Fedora 10. The patch fixes a bug in NFS where an error will not be
returned to the NFS client when an incomplete write happens at the
filesystem level on
On Tue, 3 Mar 2009 16:07:38 -0500
Jarod Wilson ja...@redhat.com wrote:
- Is there a long term goal to bring all the firmware from alsa-firmware
upstream into the kernel-firmware package?
No clue... Would have to talk to some alsa folks.
David Woodhouse is working on firmware
On Wed, 25 Feb 2009 14:15:37 +0100
Thorsten Leemhuis fed...@leemhuis.info wrote:
On 25.02.2009 13:27, Chris Lalancette wrote:
Gerd Hoffmann wrote:
We can also simply do this:
- Install PAE kernel if the CPU supports PAE.
i.e. make PAE the default kernel.
Yes, I really think we
On Tue, 24 Feb 2009 15:38:42 -0800 (PST)
Roland McGrath rol...@redhat.com wrote:
If we have NX (which anything made in the last few years will)
it's a performance win to use the hardware NX instead of the
segment limit hack we implemented in execshield.
It's more than performance. The
I thought we were going to enable these in rawhide since the e1000
EEPROM problem was fixed:
CONFIG_FUNCTION_TRACER (was CONFIG_FTRACE)
CONFIG_DYNAMIC_FTRACE
Also hda audio powersave is still off; we have:
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
___
2.6.28 has turned out to be a bit buggy. Also 2.6.27 has been chosen to be
a long-term supported kernel upstream. This means we can leave F9 and F10
on .27 and concentrate on getting .29 into shape for F10 and F11. With the
extra resources available from not trying to fix up .28 we can make .29
On Fri, 9 Jan 2009 16:45:11 -0500
Bill Nottingham nott...@redhat.com wrote:
Here's some proposed config changes.
-CONFIG_HAMRADIO=y
+# CONFIG_HAMRADIO is not set
hamradio was enabled because of user request.
___
Fedora-kernel-list mailing list
On Wed, 15 Oct 2008 12:39:55 -0400
Doug Chapman [EMAIL PROTECTED] wrote:
Sorry, meant to include the BZ in the original email. It has been
reported at least once. I have heard from several co-workers back in HP
that have been blocked by this.
On Fri, 3 Oct 2008 13:20:29 -0700 (PDT)
Roland McGrath [EMAIL PROTECTED] wrote:
What's this about?
Just reducing the time it takes to do 'make prep' when the next stable
update is released. The patches are so small it doesn't make sense to
untar the kernel and apply the stable update every
On Tue, 30 Sep 2008 11:10:35 +0200
Thorsten Leemhuis [EMAIL PROTECTED] wrote:
The alsa-project is a good example. Say you purchase a new motherboard
and it has a brand new audio codec that is not yet supported by the
in-kernel drivers. You report that to the alsa-project and they develop
Kyle McMartin wrote:
On Tue, Aug 05, 2008 at 11:01:17AM -0400, Jarod Wilson wrote:
On Tuesday 05 August 2008 09:24:10 Steve Dickson wrote:
Chuck Ebbert wrote:
Steve Dickson wrote:
Now that devel kernels rpms require the kernel-firmware rpm, it makes
sense to me that one should be able
Kyle McMartin wrote:
On Tue, Aug 05, 2008 at 04:19:07PM -0400, Chuck Ebbert wrote:
That's what it does. It includes all firmware, even for drivers that don't get
built. Look in firmware/Makefile and you'll see it builds lists
named fw-shipped-y, fw-shipped-m and fw-shipped- then just merges
Steve Dickson wrote:
Chuck Ebbert wrote:
Steve Dickson wrote:
Now that devel kernels rpms require the kernel-firmware rpm, it makes
sense to me that one should be able to build both of them at the same
time. So this patch adds the --with firmware build option
which will allow kernel-firmware
John W. Linville wrote:
I still think that for continuity's sake f8 and f9 should continue
to get wireless fixes from 2.6.27. Those should only be specific
bug fixes (although I suppose there is still time for a new driver),
so hopefully the nattering nabobs won't be opposed to continuing with
Ted Sume Nzuonkwelle wrote:
Hi,
My apologies if this is going to the wrong mailing list.
Is there an easy way to enable support for perfmon2 in the fedora 9
kernel(s)? Looks like the patch for perfmon2 available at
http://sourceforge.net/projects/perfmon2/
is only useful if patching a
Steve Dickson wrote:
Now that devel kernels rpms require the kernel-firmware rpm, it makes
sense to me that one should be able to build both of them at the
same time. So this patch adds the --with firmware build option
which will allow kernel-firmware rpms to built with kernel rpms.
This
On 03/28/2008 05:44 PM, Hans de Goede wrote:
Hi All,
I'm a Linux enthusiast / developer. Lately I'm mainly active doing
development for Fedora and writing kernel drivers (and as my day job I'm
a lecturer in Computer Science).
Fedora has a policy of not shipping a heavily patched kernel,
On 02/16/2008 06:53 AM, drago01 wrote:
Hi,
I tested the kernel-2.6.24.2-3.fc8 (downloaded the x86_64 build
directly) on my laptop.
Hal detects two batteries because it looks in sysfs and in procfs for
the battery info. I tryed to apply the patch from the hal-list which
causes hal to not look
Could this be yet another problem caused by the switch to GCC 4.3?
http://koji.fedoraproject.org/koji/getfile?taskID=389458name=build.log
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -p
'/.*/2.6.24-14.fc9(-ppc)?/.*|/.*2.6.24-14.fc9' -o debuginfo.list -p
On 02/01/2008 02:00 PM, Chuck Ebbert wrote:
Could this be yet another problem caused by the switch to GCC 4.3?
http://koji.fedoraproject.org/koji/getfile?taskID=389458name=build.log
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -p
'/.*/2.6.24-14.fc9(-ppc)?/.*|/.*2.6.24-14.fc9' -o
On 02/01/2008 04:22 PM, Roland McGrath wrote:
Oh wait, the copied not linked warning probaby explains the whole thing.
The /usr/lib/debug copy is not stripped, so it's not identical.
Yeah, ok. I wonder why this wasn't happening before.
Maybe the compiler is adding some new section type that
On 02/01/2008 05:17 PM, Jan Kratochvil wrote:
On Fri, 01 Feb 2008 22:06:29 +0100, Chuck Ebbert wrote:
...
And, after fixing that one we get (on ppc):
*** ERROR: same build ID in nonidentical files!
/usr/lib/debug/lib/modules/2.6.24-14.fc9/vmlinux
and /boot/vmlinuz-2.6.24-14.fc9
On 01/30/2008 03:54 PM, Jarod Wilson wrote:
On Wednesday 30 January 2008 03:47:26 pm Jarod Wilson wrote:
On Wednesday 30 January 2008 02:55:08 pm Jarod Wilson wrote:
On Wednesday 30 January 2008 02:17:17 pm Roland McGrath wrote:
Roland, I don't suppose any of the recent changes I seem to
On 01/22/2008 01:47 PM, Chuck Ebbert wrote:
awk '/^Patch.*:/ { print $1 %{_sourcedir}/$2 }' %{_specdir}/%{name}.spec |
while read num patch ; do
optfield=$( echo $num | cut -f 1 -d : | tr [:lower:] [:upper:] )_OPTS
opts=$( cat %{_specdir}/%{name}.spec | grep ^${optfield} | cut -f 2 -d
On 01/08/2008 09:30 AM, Mark wrote:
Hey,
I just downloaded and installed the latest kernel rpm from koji [1]
but found out that uvesafb isn't enabled in the fedora kernels. Could
a kernel maintainer put the following value in the config-generc:
CONFIG_FB_UVESA=y
so that uvesafb is
On 11/28/2007 03:29 AM, Pete Zaitcev wrote:
It's not important why stubs-32.h does not exist in glibc-headers.
stubs-32.h is in glibc-devel on Fedora 6 and was apparently removed
sometime after that.
___
Fedora-kernel-list mailing list
This might be useful for people building their own kernels:
--- kernel.spec 12 Nov 2007 22:05:50 - 1.237
+++ kernel.spec 13 Nov 2007 17:05:39 -
@@ -12,7 +12,16 @@
# that the kernel isn't the stock distribution kernel, for example,
# by setting the define to .local or .bz123456
#
On 10/23/2007 06:28 PM, Dave Jones wrote:
Are the addresses in System.map accurate? On the F7 2.6.23 kernel,
I had to subtract 0x40 and add 0x100 to the address in an
oops message to get an address to use with eu-addr2line.
Relocatable kernel is another thing that really screws
I got a 160MB kernel package and discovered that the kernel and
modules contained debug info. This seems to fix it, does anyone
see a problem with it?
make -s mrproper
cp configs/$Config .config
+%if !%{with_debuginfo}
+perl -p -i -e 's/^CONFIG_DEBUG_INFO=y$/#
On 10/17/2007 10:30 AM, Christopher Brown wrote:
Hi folks,
As per http://fedoraproject.org/wiki/Vacation I'm away for a little under a
month from tomorrow, pretty much out of contact. I have been through most of
the Fedora 7 kernel bugs and will resume these duties on my return. I hope I
We have a bug report requesting that we enable SECCOMP:
https://bugzilla.redhat.com/show_bug.cgi?id=295841
I suggest we enable it in Fedora 8 but leave it disabled in F7.
That way we're not changing a config item in a stable release,
and we don't have to carry patches to lower the feature's
We are still hitting problems with MSI (and probably mmconfig)
with kernel 2.6.22:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249469
Should we just go back to disabling these by default?
___
Fedora-kernel-list mailing list
On 08/02/2007 02:20 PM, dragoran wrote:
well but kqemu seems not to break that often I just recompile it after each
kernel release and it just works.
the code might be big but it does not depend on (fast) changing interfaces.
Maybe I missed the earlier discussions, but just what does kqemu
The arcmsr driver is in-kernel but you can't install to a
system using it for the main disk controller:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249647
Ditto for the uli526x network driver, network installs are
impossible on systems using that:
See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249587
Some users need mdadm to build an initrd.
Others might need a new release of cpuspeed (if they use it.)
We don't require those packages because not all users will need
them, AFAICT -- it depends on what features they use. Should we
On 07/11/2007 12:35 PM, Jarod Wilson wrote:
Cpuspeed afaics needs an adjustment if cpuidle stays:
$ LC_ALL=C sudo /etc/init.d/cpuspeed restart
Disabling ondemand cpu frequency scaling: /etc/init.d/cpuspeed: line 212:
/sys/devices/system/cpu/cpuidle/cpufreq/scaling_governor: No such
On 07/09/2007 06:29 PM, Feng Xian wrote:
Hi, I am working on a project about reducing page faults of multi-threaded
programs. I am using latest Fedora core (Linux 2.6) and pthread library. In
this project, each user-level thread (created by pthread_create()
function)
needs to pass a value to
On 06/24/2007 03:25 PM, David Woodhouse wrote:
On Fri, 2007-06-22 at 16:36 -0400, Chuck Ebbert wrote:
Why do we explicitly remove atomic.h from our kernel header package?
No reason any more. Once upon a time, before the cleanup of the upstream
kernel's exports was complete, we needed
On 06/20/2007 11:12 AM, Josh Boyer wrote:
And if it isn't good enough for upstream to ship and support, why in
$DEITY's name would we want to ship it, again?
*cough* squashfs *cough cough* wireless-dev *cough* CFS *cough hack* xen
*cough*
... exec-shield
[https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239507]
(In reply to comment #5)
We can do two things
1. Rebuild the RPM carefuly with CONFIG_USB_SUSPEND disabled, but without
changing anything else, see if that helps, and
I think we need this anyway. There are devices that require
On 06/07/2007 03:39 PM, Bill Nottingham wrote:
Xen.
This might get interesting to watch for F8 if XenU gets upstream
(Which akpm seems to suggest it might). Given we've decoupled
kernel/kernel-xen, we might want to just disable the upstream variant
until F9, and wait until we have
Chuck Ebbert wrote:
Dave Jones wrote:
Gets my vote too.
I've turned off CONFIG_PCI_MSI and turned it back on about 2-3 times
now for FC5/FC6, because each time it starts to look more promising,
it seems to find new ways to regress.
I might do a build next week in rawhide with it off again
Right now we package the debuginfo so it contains only the
DWARF debug information, but some utilities can't work with
that. If we put the full modules with debug info in the
package then everything should work, at the cost of making
the package about 14MB larger. Is there any reason not to
do
Josh Boyer wrote:
On Mon, 2007-04-02 at 14:05 -0400, Chuck Ebbert wrote:
Right now we package the debuginfo so it contains only the
DWARF debug information, but some utilities can't work with
that. If we put the full modules with debug info in the
package then everything should work
Jon Masters wrote:
Chuck Ebbert wrote:
At first glance it doesn't seem very hard to do something like this
on kernel install:
ln -s raid456.ko
/lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid4.ko
ln -s raid456.ko
/lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid5.ko
ln -s raid456
Jarod Wilson wrote:
Dave Jones wrote:
On Thu, Mar 29, 2007 at 02:06:58PM -0400, Jarod Wilson wrote:
Dave Jones wrote:
On Thu, Mar 29, 2007 at 01:41:45PM -0400, Chuck Ebbert wrote:
I was thinking about adding something like this to the .spec file
at the beginning
Apparently the qlogic drivers don't have any firmware included in FC7,
so nobody can actually use a qlogic adapter. Should we be patching the
kernel like in FC6 or do we need a separate package? Or maybe the
firmware goes in the kernel package?
Peter says the support for Anaconda / mkinitrd to
Clinton Lee Taylor wrote:
Greetings ...
I for one would like to vote for rpms of vanilla kernel build!
I have an Adaptec ASR-3410S, which is an i2o device, but since
2.6.18-1.2869.fc6, I can't use it and the i2o maintaner suggests I try a
vanilla kernel build to see if it's an FC kernel
54 matches
Mail list logo
