From eparis at redhat.com Mon Aug 3 15:35:53 2009 From: eparis at redhat.com (Eric Paris) Date: Mon, 03 Aug 2009 11:35:53 -0400 Subject: enable CONFIG_IMA Message-ID: <1249313753.2447.22.camel@dhcp231-106.rdu.redhat.com> Just noticed that the F12 kernel have CONFIG_IMA turned off: # CONFIG_IMA is not set I'd like to see: CONFIG_IMA=y CONFIG_IMA_MEASURE_PCR_IDX=10 CONFIG_IMA_AUDIT=y CONFIG_IMA_LSM_RULES=y This should ONLY be enabled for 2.6.31 kernels as before my patches in 2.6.31 there were a couple of normal user trigger-able security issues with IMA. Without configuration on the boot line or configuration after boot of the ima infrastructure there is no impact to building this piece of code outside of the fact that it builds CONFIG_TCG_TPM and CONFIG_TCG_TIS in and will not allow them to be built as modules. This may cause some consternation on users of the latest lenovo thinkpads who have to patch those modules to get them to work (TPM on latest lenovo notebooks only supports ACPI not PNP for device discovery), but seeing as how noone really uses the tpm anyway and hopefully it'll be fixed upstream this week I don't see that as a large problem.... -Eric From remotestar at live.com Mon Aug 10 18:45:51 2009 From: remotestar at live.com (Markus Kesaromous) Date: Mon, 10 Aug 2009 11:45:51 -0700 Subject: =?windows-1256?q?kernel_2=2E6=2E29=2E6-217=2E2=2E3=2Efc11_compil?= =?windows-1256?q?ed_from_source_will_not_boot=FE=FE?= Message-ID: Dear list, There is something seriously wrong with this kernel release. It compiles - but will not boot all the way. It hangs somewhere. I even tried to boot into single user mode. I never get to the shell prompt when booting in single user mode, nor to the gnome login banner when letting it boot in multiuser mode. After some 30-45 minutes I Ctrl-Alt_Del and the kernel pops the message Stopping all md devices .. and the pc reboots. I did not have this problem with these kernels 2.6.29.6-213.fc11 2.6.29.5-191.fc11 Are there others who have tried to build 2.6.29.6-217.2.3.fc11 from source rpm and configured the kernel in any way before building? Did you see any errors when running make modules_install as I did? Did the resulting kernel boot up all the way? If you need more info, please let me know. Cheers, Markus K. _________________________________________________________________ Windows Live?: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 From snecklifter at gmail.com Mon Aug 10 23:41:52 2009 From: snecklifter at gmail.com (Christopher Brown) Date: Tue, 11 Aug 2009 00:41:52 +0100 Subject: =?utf-8?q?Re=3A_kernel_2=2E6=2E29=2E6-217=2E2=2E3=2Efc11_compile?= =?utf-8?b?ZCBmcm9tIHNvdXJjZSB3aWxsIG5vdCBib2904oCP4oCP?= In-Reply-To: References: Message-ID: <364d303b0908101641p559bf733y1eed2a00a2fdcc3d@mail.gmail.com> 2009/8/10 Markus Kesaromous : > > Dear list, > There is something seriously wrong with this kernel release. > It compiles - but will not boot all the way. It hangs somewhere. > I even tried to boot into single user mode. I never get to the shell > prompt when booting in single user mode, nor to the > gnome login banner when letting it boot in multiuser mode. > After some 30-45 minutes I ?Ctrl-Alt_Del and the kernel > pops the message > > Stopping all md devices > .. > and the pc reboots. > > I did not have this problem with these kernels > 2.6.29.6-213.fc11 > 2.6.29.5-191.fc11 > > Are there others who have tried to build ?2.6.29.6-217.2.3.fc11 > from source rpm and configured the kernel in any way before > building? > Did you see any errors when running make modules_install > as I did? Did the resulting kernel boot up all the way? > > If you need more info, please let me know. The main piece of information you appear to have missed off is the modifications you have made in your build. I would suggest the following for further reading: http://fedoraproject.org/wiki/Docs/CustomKernel http://fedoraproject.org/wiki/KernelCommonProblems Regards -- Christopher Brown From remotestar at live.com Tue Aug 11 04:54:48 2009 From: remotestar at live.com (Markus Kesaromous) Date: Mon, 10 Aug 2009 21:54:48 -0700 Subject: =?windows-1256?b?UkU6IGtlcm5lbCAyLjYuMjkuNi0yMTcuMi4zLmZjMTEg?= =?windows-1256?q?compiled_from_source_will_not_boot=FE=FE?= In-Reply-To: <364d303b0908101641p559bf733y1eed2a00a2fdcc3d@mail.gmail.com> References: <364d303b0908101641p559bf733y1eed2a00a2fdcc3d@mail.gmail.com> Message-ID: On Tue, 11 Aug 2009 00:41:52AM, Christopher Brown wrote: > Date: Tue, 11 Aug 2009 00:41:52 +0100 > From: snecklifter at gmail.com > To: remotestar at live.com > CC: fedora-kernel-list at redhat.com > Subject: Re: kernel 2.6.29.6-217.2.3.fc11 compiled from source will not boot?? > > 2009/8/10 Markus Kesaromous : >> >> Dear list, >> There is something seriously wrong with this kernel release. >> It compiles - but will not boot all the way. It hangs somewhere. >> I even tried to boot into single user mode. I never get to the shell >> prompt when booting in single user mode, nor to the >> gnome login banner when letting it boot in multiuser mode. >> After some 30-45 minutes I Ctrl-Alt_Del and the kernel >> pops the message >> >> Stopping all md devices >> .. >> and the pc reboots. >> >> I did not have this problem with these kernels >> 2.6.29.6-213.fc11 >> 2.6.29.5-191.fc11 >> >> Are there others who have tried to build 2.6.29.6-217.2.3.fc11 >> from source rpm and configured the kernel in any way before >> building? >> Did you see any errors when running make modules_install >> as I did? Did the resulting kernel boot up all the way? >> >> If you need more info, please let me know. > > The main piece of information you appear to have missed off is the > modifications you have made in your build. I would suggest the > following for further reading: > > http://fedoraproject.org/wiki/Docs/CustomKernel > http://fedoraproject.org/wiki/KernelCommonProblems > > Regards > > -- > Christopher Brown > Thank you Christopher. The steps to build the kernel at URL http://fedoraproject.org/wiki/Docs/CustomKernel were exactly what I needed. I was not aware of this document before. The only thing "extra" I had to do was to untar linux-2.6.29.tar.bz2 and fix drivers/staging/rt2860/config.mk, and then re-tar. Guess I should have created a patch, and should have added that patch to the spec file. But, since this is only one-off, I did not see the need for it. I am sure there will be yet another kernel update for whic I will have to repeat this whole process. What a pain in the neck! If I had known that the Atheros 9K series of mini-pci cards were supported natively, I would not have bought the Ralink 2860 card. Thanx again for your help. Cheers, Markus _________________________________________________________________ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCB&publ=WLHMTAG&crea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 From remotestar at live.com Wed Aug 12 20:44:45 2009 From: remotestar at live.com (Markus Kesaromous) Date: Wed, 12 Aug 2009 13:44:45 -0700 Subject: (no subject) Message-ID: Dear List, I searched the ath9k source directory /usr/src/redhat/BUILD/kernel-2.6.29/linux-2.6.29.i586/drivers/net/wireless/ath9k for any strings that would hint/suggest support for the Atheros 9220/9223 chipset. I saw no such strings. So, I emailed Atheros.com sales dept. and asked if they intend to provide an open source driver for the AR9000 series chipsets, esp. the AR9220/AR9223. They replied that they already DO support the AR92xx chipset in the ath9k driver. Before I go out and purchase the mini-pci card, is it true that the ath9k driver has ineed been tested to fully support AR9220/AR9223 chipsets?? Thank you, Markus _________________________________________________________________ Express your personality in color! Preview and select themes for Hotmail?. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_express:082009 From remotestar at live.com Thu Aug 13 00:04:34 2009 From: remotestar at live.com (Markus Kesaromous) Date: Wed, 12 Aug 2009 17:04:34 -0700 Subject: (no subject) In-Reply-To: <364d303b0908121601v4e763cf2q9ab22deab6354f43@mail.gmail.com> References: <364d303b0908121601v4e763cf2q9ab22deab6354f43@mail.gmail.com> Message-ID: ---------------------------------------- > Date: Thu, 13 Aug 2009 00:01:25 +0100 > Subject: Re: (no subject) > From: snecklifter at gmail.com > To: remotestar at live.com > > Hi Markus, > > 2009/8/12 Markus Kesaromous : >> >> Dear List, >> I searched the ath9k source directory >> /usr/src/redhat/BUILD/kernel-2.6.29/linux-2.6.29.i586/drivers/net/wireless/ath9k >> for any strings that would hint/suggest support for the Atheros 9220/9223 >> chipset. I saw no such strings. > > What strings were you looking for? I stated:>> for any strings that would hint/suggest support for the Atheros 9220/9223 (meaning 9220 or 9223 ala grep '922[0-9]' * (within the ath9k directory). > >> So, I emailed Atheros.com sales dept. and asked if they intend to provide an open >> source driver for the AR9000 series chipsets, esp. the AR9220/AR9223. They replied that they already DO support the AR92xx chipset in the ath9k driver. >> >> Before I go out and purchase the mini-pci card, is it true that the ath9k driver >> has ineed been tested to fully support AR9220/AR9223 chipsets?? > > Your thought process intrigues me. If you have communication from the > manufacturer advising it is supported then you have your answer (and a > waterproof returns policy if they are wrong). I have learned never to trust sales people. When it comes to dealing with online merchants, what the sales contact at the manufacturer says will not be sufficient reason for return for a full refund, of a device which turns out to be unsupported. My question to you is - why do you have to resort to assuming such a pompous attitude via questions like "Your thought process intrigues me." There is a fitting description for such attitude, but I will not spam this mailing list with such a vivid description. > Some basic investigation > on the web will tell you what you need to know: > > http://wiki.debian.org/ath9k#supported > > Generally I just plug shit in and it works. > > Christopher Brown _________________________________________________________________ Get your vacation photos on your phone! http://windowsliveformobile.com/en-us/photos/default.aspx?&OCID=0809TL-HM From snecklifter at gmail.com Thu Aug 13 06:02:01 2009 From: snecklifter at gmail.com (Christopher Brown) Date: Thu, 13 Aug 2009 07:02:01 +0100 Subject: (no subject) In-Reply-To: References: <364d303b0908121601v4e763cf2q9ab22deab6354f43@mail.gmail.com> Message-ID: <364d303b0908122302i42126a1s4e0e85b5942c8608@mail.gmail.com> 2009/8/13 Markus Kesaromous : > > ---------------------------------------- >> Date: Thu, 13 Aug 2009 00:01:25 +0100 >> Subject: Re: (no subject) >> From: snecklifter at gmail.com >> To: remotestar at live.com >> >> Hi Markus, >> >> 2009/8/12 Markus Kesaromous : >>> >>> Dear List, >>> I searched the ath9k source directory >>> /usr/src/redhat/BUILD/kernel-2.6.29/linux-2.6.29.i586/drivers/net/wireless/ath9k >>> for any strings that would hint/suggest support for the Atheros 9220/9223 >>> chipset. I saw no such strings. >> >> What strings were you looking for? > > I stated:>> for any strings that would hint/suggest support for the Atheros 9220/9223 (meaning ?9220 or 9223 ala ? grep '922[0-9]' ?* ?(within the ath9k directory). > >> >>> So, I emailed Atheros.com sales dept. and asked if they intend to provide an open >>> source driver for the AR9000 series chipsets, esp. the AR9220/AR9223. They replied that they already DO support the AR92xx chipset in the ath9k driver. >>> >>> Before I go out and purchase the mini-pci card, is it true that the ath9k driver >>> has ineed been tested to fully support AR9220/AR9223 chipsets?? >> >> Your thought process intrigues me. If you have communication from the >> manufacturer advising it is supported then you have your answer (and a >> waterproof returns policy if they are wrong). > > I have learned never to trust sales people. When it comes to dealing with online > > merchants, what the sales contact at the manufacturer ?says will not be sufficient > reason for return for a full refund, ?of a device which turns out to ?be unsupported. Then why contact them? > My question to you is - why do you have to resort to assuming such a pompous attitude via questions like "Your thought process intrigues me." I'm afraid this is your interpretation. > There is a fitting description for such attitude, but I will not spam this mailing list with such a vivid description. Then please reply off-list, as I did. >> Some basic investigation >> on the web will tell you what you need to know: >> >> http://wiki.debian.org/ath9k#supported No really, that's my pleasure. -- Christopher Brown From jcm at redhat.com Thu Aug 13 06:22:41 2009 From: jcm at redhat.com (Jon Masters) Date: Thu, 13 Aug 2009 02:22:41 -0400 Subject: Annoying kmemleak scans In-Reply-To: <1250002434.2367.1.camel@localhost.localdomain> References: <1250002434.2367.1.camel@localhost.localdomain> Message-ID: <1250144561.4754.11.camel@perihelion.bos.jonmasters.org> On Tue, 2009-08-11 at 16:53 +0200, Fabian Deutsch wrote: > Starting with F11 kmemleak is part of the kernel. It is quite annoying > when every couple of minutes kmemleak starts to scan for memeleak within > the kernel. I do not see any point in doing this on desktop machines, so > is there a chance of disabling it by default? > It eats quite much of battery when running F11 on a laptop. Having kmemleak turned on at least in rawhide is a good thing. As for a released kernel, I'd agree that the kthread Catalin uses probably affects battery life. Of course you could disable it, but I suppose you mentioned this because of the default - hence, copying fedora-kernel so that someone can actually answer your question. Jon. From sgruszka at redhat.com Fri Aug 14 14:35:03 2009 From: sgruszka at redhat.com (Stanislaw Gruszka) Date: Fri, 14 Aug 2009 16:35:03 +0200 Subject: [PATCH 0/3] iwl3945 driver fixes for Fedora 11 (2.6.29) In-Reply-To: <1248359742-15865-1-git-send-email-sgruszka@redhat.com> References: <1248359742-15865-1-git-send-email-sgruszka@redhat.com> Message-ID: <20090814143502.GA3832@dhcp-lab-161.englab.brq.redhat.com> On Thu, Jul 23, 2009 at 04:35:39PM +0200, Stanislaw Gruszka wrote: > Due to backport of patch > > linux-2.6-iwl3945-report-killswitch-changes-even-if-the-interface-is-down.patch > > we have bunch of iwl3945 bugs (race conditions) that are not reproducible > on vanilla 2.6.29. These patches address them (at least some of them). I see in cvs that F10 is moving to 2.6.29, so these patches should go F-10 too. Cheers Stanislaw From linville at tuxdriver.com Fri Aug 14 14:44:25 2009 From: linville at tuxdriver.com (John W. Linville) Date: Fri, 14 Aug 2009 10:44:25 -0400 Subject: [PATCH 0/3] iwl3945 driver fixes for Fedora 11 (2.6.29) In-Reply-To: <20090814143502.GA3832@dhcp-lab-161.englab.brq.redhat.com> References: <1248359742-15865-1-git-send-email-sgruszka@redhat.com> <20090814143502.GA3832@dhcp-lab-161.englab.brq.redhat.com> Message-ID: <20090814144425.GM2650@tuxdriver.com> On Fri, Aug 14, 2009 at 04:35:03PM +0200, Stanislaw Gruszka wrote: > On Thu, Jul 23, 2009 at 04:35:39PM +0200, Stanislaw Gruszka wrote: > > Due to backport of patch > > > > linux-2.6-iwl3945-report-killswitch-changes-even-if-the-interface-is-down.patch > > > > we have bunch of iwl3945 bugs (race conditions) that are not reproducible > > on vanilla 2.6.29. These patches address them (at least some of them). > > I see in cvs that F10 is moving to 2.6.29, so these patches should go F-10 too. I'm heading out for the weekend. Would someone else care to shepherd this? John -- John W. Linville Someday the world will need a hero, and you linville at tuxdriver.com might be all we have. Be ready. From pgrinberg at nyc.saic.com Fri Aug 14 18:35:22 2009 From: pgrinberg at nyc.saic.com (Paul Grinberg) Date: Fri, 14 Aug 2009 14:35:22 -0400 Subject: Recompile kernel without SMP Message-ID: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> Hi there, I am trying to recompile kernel without SMP. So far I've been unsuccessful. Meaning I am able to compile, but it was still SMP.. Can someone tell me what I am doing wrong? And why I don't get "kernel-headers" build? It is probably related to spec parameters.... So far this is what I've done: cd ~/ rpmdev-setuptree # as regular user cd rmpbuild yumdownloader --source kernel # as regular user cd ~/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.i686/ cp configs/kernel-2.6.29.6-i586.config .config make menuconfig # console setup Select option: Processor type and features. Disable "Symmetric multi-processing support" (SMP) cp .config ~/rpmbuild/SOURCES/config-i686-generic cp .config ~/rpmbuild/SOURCES/config-i686 cd ~/rpmbuild/SPECS nano kernel.spec Add line: % define buildid .NONSMP Replace: # Allow kernel-firmware building #%define with_firmware %{?_with_firmware: 1} %{?!_with_firmware: 0} %define with_firmware %{?_with_firmware: 0} %{?!_with_firmware: 1} #%define with_firmware %{?_without_firmware: 0} %{?!_without_firmware: 1} %define with_firmware %{?_without_firmware: 1} %{?!_without_firmware: 0} # Allow kernel-headers building # Allow kernel-devel building # Create RPM package rpmbuild -bb --with firmware --target=i686 kernel.spec # To actually install kernel su rpm -ivh kernel-firmware-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm kernel-PAE-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm kernel-PAE-devel-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm Just in case: $ cat config-i686-PAE | egrep -i "smp" | more CONFIG_BROKEN_ON_SMP=y # CONFIG_SMP is not set CONFIG_X86_FIND_SMP_CONFIG=y # CONFIG_X86_VSMP is not set CONFIG_SCSI_SAS_HOST_SMP=y CONFIG_VIDEO_VP27SMPX=m Best, Paul From remotestar at live.com Fri Aug 14 20:51:44 2009 From: remotestar at live.com (Markus Kesaromous) Date: Fri, 14 Aug 2009 13:51:44 -0700 Subject: Recompile kernel without SMP In-Reply-To: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> Message-ID: > Date: Fri, 14 Aug 2009 14:35:22 -0400 > From: pgrinberg at nyc.saic.com > To: fedora-kernel-list at redhat.com > Subject: Recompile kernel without SMP > > Hi there, > > I am trying to recompile kernel without SMP. So far I've been > unsuccessful. Meaning I am able to compile, but it was still SMP.. > > Can someone tell me what I am doing wrong? > And why I don't get "kernel-headers" build? > > It is probably related to spec parameters.... > > So far this is what I've done: > > cd ~/ > rpmdev-setuptree # as regular user > cd rmpbuild > yumdownloader --source kernel # as regular user > > cd ~/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.i686/ > cp configs/kernel-2.6.29.6-i586.config .config > make menuconfig # console setup > > Select option: Processor type and features. > Disable "Symmetric multi-processing support" (SMP) > > cp .config ~/rpmbuild/SOURCES/config-i686-generic > cp .config ~/rpmbuild/SOURCES/config-i686 > cd ~/rpmbuild/SPECS > nano kernel.spec > Add line: > % define buildid .NONSMP > Replace: > > # Allow kernel-firmware building > #%define with_firmware %{?_with_firmware: 1} %{?!_with_firmware: 0} > %define with_firmware %{?_with_firmware: 0} %{?!_with_firmware: 1} > > #%define with_firmware %{?_without_firmware: 0} %{?!_without_firmware: > 1} > %define with_firmware %{?_without_firmware: 1} %{?!_without_firmware: > 0} > > # Allow kernel-headers building > > # Allow kernel-devel building > > # Create RPM package > rpmbuild -bb --with firmware --target=i686 kernel.spec > > # To actually install kernel > su > rpm -ivh kernel-firmware-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > kernel-PAE-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > kernel-PAE-devel-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > > > > Just in case: > $ cat config-i686-PAE | egrep -i "smp" | more > CONFIG_BROKEN_ON_SMP=y > # CONFIG_SMP is not set > CONFIG_X86_FIND_SMP_CONFIG=y > # CONFIG_X86_VSMP is not set > CONFIG_SCSI_SAS_HOST_SMP=y > CONFIG_VIDEO_VP27SMPX=m > > > > > > Best, > Paul > I just got bit by a similar problem in trying to build kernel-2.6.31-0.125.4.2.rc5.git2.fc12.src.rpm I followed the steps outlined in http://fedoraproject.org/wiki/Docs/CustomKernel I only wanted to build i686 architecture - without SMP - without cpu id support - without multicore support - without hyperthreading support - with kernel config support - with kernel config via /proc support - with frequency default governor set to Performance - with preemptible kernel - with rt2860 module support - with NTFS read/write support Well, it ended up building i686-PAE Debug kernel with SMP support. It seems as if the architecture is i686, then only i686 PAE Debug gets built. I do not know where the problem lies, but ....SOURCES/Makefile.config might be the place where the target kernel build is being selected. To get around it, I edited ...SOURCES/Makefile.config and removed all rules and definitions pertaining to i686-PAE and only left the simple i686 def and rule. PS: I do not know if this is necessary, but after I copied .config to ...SOURCES/config-i686 I also copied it to ...SOURCES/config-x86-generic Then running rpmbuild -v -bb --target=i686 kernel.spec is proceeding without problems MK _________________________________________________________________ Windows Live?: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 From pgrinberg at nyc.saic.com Fri Aug 14 21:24:22 2009 From: pgrinberg at nyc.saic.com (Paul Grinberg) Date: Fri, 14 Aug 2009 17:24:22 -0400 Subject: Recompile kernel without SMP In-Reply-To: References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> Message-ID: <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> Markus, Thank you for your reply! I already feel better knowing that I'm not alone :) Maybe someone might have a clue "Why".... Best, Paul -----Original Message----- From: Markus Kesaromous [mailto:remotestar at live.com] Sent: Friday, August 14, 2009 4:52 PM To: Paul Grinberg; Linux Kernel List Subject: RE: Recompile kernel without SMP > Date: Fri, 14 Aug 2009 14:35:22 -0400 > From: pgrinberg at nyc.saic.com > To: fedora-kernel-list at redhat.com > Subject: Recompile kernel without SMP > > Hi there, > > I am trying to recompile kernel without SMP. So far I've been > unsuccessful. Meaning I am able to compile, but it was still SMP.. > > Can someone tell me what I am doing wrong? > And why I don't get "kernel-headers" build? > > It is probably related to spec parameters.... > > So far this is what I've done: > > cd ~/ > rpmdev-setuptree # as regular user > cd rmpbuild > yumdownloader --source kernel # as regular user > > cd ~/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.i686/ > cp configs/kernel-2.6.29.6-i586.config .config > make menuconfig # console setup > > Select option: Processor type and features. > Disable "Symmetric multi-processing support" (SMP) > > cp .config ~/rpmbuild/SOURCES/config-i686-generic > cp .config ~/rpmbuild/SOURCES/config-i686 > cd ~/rpmbuild/SPECS > nano kernel.spec > Add line: > % define buildid .NONSMP > Replace: > > # Allow kernel-firmware building > #%define with_firmware %{?_with_firmware: 1} %{?!_with_firmware: 0} > %define with_firmware %{?_with_firmware: 0} %{?!_with_firmware: 1} > > #%define with_firmware %{?_without_firmware: 0} %{?!_without_firmware: > 1} > %define with_firmware %{?_without_firmware: 1} %{?!_without_firmware: > 0} > > # Allow kernel-headers building > > # Allow kernel-devel building > > # Create RPM package > rpmbuild -bb --with firmware --target=i686 kernel.spec > > # To actually install kernel > su > rpm -ivh kernel-firmware-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > kernel-PAE-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > kernel-PAE-devel-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > > > > Just in case: > $ cat config-i686-PAE | egrep -i "smp" | more > CONFIG_BROKEN_ON_SMP=y > # CONFIG_SMP is not set > CONFIG_X86_FIND_SMP_CONFIG=y > # CONFIG_X86_VSMP is not set > CONFIG_SCSI_SAS_HOST_SMP=y > CONFIG_VIDEO_VP27SMPX=m > > > > > > Best, > Paul > I just got bit by a similar problem in trying to build kernel-2.6.31-0.125.4.2.rc5.git2.fc12.src.rpm I followed the steps outlined in http://fedoraproject.org/wiki/Docs/CustomKernel I only wanted to build i686 architecture - without SMP - without cpu id support - without multicore support - without hyperthreading support - with kernel config support - with kernel config via /proc support - with frequency default governor set to Performance - with preemptible kernel - with rt2860 module support - with NTFS read/write support Well, it ended up building i686-PAE Debug kernel with SMP support. It seems as if the architecture is i686, then only i686 PAE Debug gets built. I do not know where the problem lies, but ....SOURCES/Makefile.config might be the place where the target kernel build is being selected. To get around it, I edited ...SOURCES/Makefile.config and removed all rules and definitions pertaining to i686-PAE and only left the simple i686 def and rule. PS: I do not know if this is necessary, but after I copied .config to ...SOURCES/config-i686 I also copied it to ...SOURCES/config-x86-generic Then running rpmbuild -v -bb --target=i686 kernel.spec is proceeding without problems MK _________________________________________________________________ Windows Live(tm): Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_B R_sync:082009 From remotestar at live.com Sat Aug 15 21:15:50 2009 From: remotestar at live.com (Markus Kesaromous) Date: Sat, 15 Aug 2009 14:15:50 -0700 Subject: Radeon driver broken in 2.6.31-0.125.4.2.rc5.git2.fc11 Message-ID: I had no problems with the radeon drivers in 2.6.29.6-213 2.6.29.6-217.2.3 2.6.30.4-25 But in 2.6.31-0.125.4.2.rc5.git2, X is unable to start. This is Xorg.0.log: X.Org X Server 1.6.1.901 (1.6.2 RC 1) Release Date: 2009-5-8 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.18-128.1.6.el5 i686 Current Operating System: Linux localhost.localdomain 2.6.31-0.125.4.2.rc5.git2.fc11.i686 #1 PREEMPT Fri Aug 14 19:46:56 PDT 2009 i686 Kernel command line: ro root=UUID=7cf783f9-8bbb-421c-a919-fd7f6d9ab463 rhgb quiet Build Date: 18 May 2009 02:47:59PM Build ID: xorg-x11-server 1.6.1.901-1.fc11 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 15 08:06:39 2009 (II) Loader magic: 0x640 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on linux (--) using VT number 7 (--) PCI:*(0 at 1:0:0) ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] rev 0, Mem @ 0xf0000000/134217728, 0xfeaf0000/65536, I/O @ 0x0000c800/256, BIOS @ 0x????????/131072 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default ati Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default ati Device 0" (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (2) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (II) No APM support in BIOS or kernel (II) System resource ranges: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [21] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [23] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [25] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [27] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [29] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/lib/xorg/modules/extensions//libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: "ati" (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so (II) Module ati: vendor="X.Org Foundation" compiled for 1.6.1, module version = 6.12.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "radeon" (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" compiled for 1.6.1, module version = 6.12.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "vesa" (II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.2.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "fbdev" (II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so (II) Module fbdev: vendor="X.Org Foundation" compiled for 1.6.0, module version = 0.4.0 ABI class: X.Org Video Driver, version 5.0 (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), ATI Radeon Mobility X300 (M24) 3152 (PCIE), ATI FireGL M24 GL 3154 (PCIE), ATI Radeon X600 (RV380) 3E50 (PCIE), ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP), ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP), ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP), ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP), ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP), ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650, ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP), ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330M/340M/350M (U2) 4337, ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI), ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP), ATI Radeon X800PRO (R420) JI (AGP), ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP), ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP), ATI Radeon Mobility 9800 (M18) JN (AGP), ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP), ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP), ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP), ATI Radeon Mobility M7 LW (AGP), ATI Mobility FireGL 7800 M7 LX (AGP), ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP), ATI FireGL Mobility 9000 (M9) Ld (AGP), ATI Radeon Mobility 9000 (M9) Lf (AGP), ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP), ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP), ATI Radeon Mobility 9600 (M10) NQ (AGP), ATI Radeon Mobility 9600 (M11) NR (AGP), ATI Radeon Mobility 9600 (M10) NS (AGP), ATI FireGL Mobility T2 (M10) NT (AGP), ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI), ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI), ATI Radeon Mobility X300 (M22) 5460 (PCIE), ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE), ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE), ATI Radeon X800PRO (R423) UI (PCIE), ATI Radeon X800LE (R423) UJ (PCIE), ATI Radeon X800SE (R423) UK (PCIE), ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE), ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE), ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE), ATI FireGL unknown (R423) UR (PCIE), ATI FireGL unknown (R423) UT (PCIE), ATI Mobility FireGL V5000 (M26) (PCIE), ATI Mobility FireGL V5000 (M26) (PCIE), ATI Mobility Radeon X700 XL (M26) (PCIE), ATI Mobility Radeon X700 (M26) (PCIE), ATI Mobility Radeon X700 (M26) (PCIE), ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834, ATI Radeon Mobility 9100 IGP (U3) 5835, ATI Radeon XPRESS 200 5954 (PCIE), ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP), ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI), ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE), ATI Radeon XPRESS 200M 5975 (PCIE), ATI Radeon XPRESS 200 5A41 (PCIE), ATI Radeon XPRESS 200M 5A42 (PCIE), ATI Radeon XPRESS 200 5A61 (PCIE), ATI Radeon XPRESS 200M 5A62 (PCIE), ATI Radeon X300 (RV370) 5B60 (PCIE), ATI Radeon X600 (RV370) 5B62 (PCIE), ATI Radeon X550 (RV370) 5B63 (PCIE), ATI FireGL V3100 (RV370) 5B64 (PCIE), ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE), ATI Radeon Mobility 9200 (M9+) 5C61 (AGP), ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Mobility Radeon X800 XT (M28) (PCIE), ATI Mobility FireGL V5100 (M28) (PCIE), ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE), ATI Radeon X850 XT PE (R480) (PCIE), ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE), ATI unknown Radeon / FireGL (R480) 5D50 (PCIE), ATI Radeon X850 XT (R480) (PCIE), ATI Radeon X800XT (R423) 5D57 (PCIE), ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE), ATI Radeon X700 PRO (RV410) (PCIE), ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE), ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800, ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800, ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300, ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800, ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505, ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL, ATI Mobility Radeon X1400, ATI Radeon X1300/X1550, ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300, ATI Mobility Radeon X1300, ATI Mobility Radeon X1300, ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300, ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350, ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550, ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450, ATI Radeon X1300/X1550, ATI Mobility Radeon X2300, ATI Mobility Radeon X2300, ATI Mobility Radeon X1350, ATI Mobility Radeon X1350, ATI Mobility Radeon X1450, ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350, ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600, ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600, ATI Mobility FireGL V5200, ATI Mobility Radeon X1600, ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400, ATI Mobility FireGL V5250, ATI Mobility Radeon X1700, ATI Mobility Radeon X1700 XT, ATI FireGL V5200, ATI Mobility Radeon X1700, ATI Radeon X2300HD, ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300, ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900, ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950, ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560, ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400, ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560, ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835, ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740, ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT, ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600, ATI Radeon 4800 Series, ATI Radeon HD 4870 x2, ATI Radeon 4800 Series, ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2, ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270, AMD FireStream 9250, ATI FirePro V8700 (FireGL), ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98, ATI Radeon 4800 Series, ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98, ATI Radeon RV730 (AGP), ATI FirePro M5750, ATI Radeon RV730 (AGP), ATI RV730XT [Radeon HD 4670], ATI RADEON E4600, ATI RV730 PRO [Radeon HD 4650], ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL), ATI FirePro V3750 (FireGL), ATI RV610, ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT, ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610, ATI FireMV 2260, ATI RV670, ATI Radeon HD3870, ATI Mobility Radeon HD 3850, ATI Radeon HD3850, ATI Mobility Radeon HD 3850 X2, ATI RV670, ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2, ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850, ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon RV710, ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series, ATI RV630, ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT, ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP, ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630, ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600, ATI FireGL V3600, ATI Radeon HD 2600 LE, ATI Mobility FireGL Graphics Processor, ATI Radeon RV710, ATI Radeon HD 3470, ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series, ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430, ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450, ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO, ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670, ATI Mobility FireGL V5700, ATI Mobility FireGL V5725, ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics, ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics, ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics, ATI Radeon 3000 Graphics, ATI Radeon HD Graphics, ATI Radeon Graphics, ATI Mobility Radeon HD Graphics, ATI Mobility Radeon Graphics, ATI Radeon Graphics (II) VESA: driver for VESA chipsets: vesa (II) FBDEV: driver for framebuffer: fbdev (II) Primary Device is: PCI 01 at 00:00:0 (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [21] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [23] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [25] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [27] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [29] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (WW) Falling back to old probe method for vesa (WW) Falling back to old probe method for fbdev (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 1.6.1.901, module version = 0.0.2 ABI class: X.Org Video Driver, version 5.0 (II) resource ranges after probing: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [20] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [21] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [22] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [24] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [25] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [26] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [27] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [28] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [29] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [30] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [31] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [32] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [33] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [34] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) RADEON(0): Creating default Display subsection in Screen section "Builtin Default ati Screen 0" for depth/fbbpp 24/32 (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (==) RADEON(0): RGB weight 888 (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) (--) RADEON(0): Chipset: "ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP)" (ChipID = 0x4e50) (II) RADEON(0): AGP card detected drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 (II) [drm] DRM interface version 1.3 (II) [drm] DRM open master succeeded. (II) RADEON(0): Output VGA-0 has no monitor section (II) RADEON(0): Output LVDS has no monitor section (II) RADEON(0): EDID for output VGA-0 (II) RADEON(0): EDID for output LVDS (II) RADEON(0): Not using default mode "640x350" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x400" (vrefresh out of range) (II) RADEON(0): Not using default mode "720x400" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1152x864" (vrefresh out of range) (II) RADEON(0): Not using default mode "1280x960" (hsync out of range) (II) RADEON(0): Not using default mode "1280x960" (vrefresh out of range) (II) RADEON(0): Not using default mode "1280x1024" (hsync out of range) (II) RADEON(0): Not using default mode "1280x1024" (vrefresh out of range) (II) RADEON(0): Not using default mode "1280x1024" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1792x1344" (hsync out of range) (II) RADEON(0): Not using default mode "1792x1344" (vrefresh out of range) (II) RADEON(0): Not using default mode "1856x1392" (hsync out of range) (II) RADEON(0): Not using default mode "1856x1392" (vrefresh out of range) (II) RADEON(0): Not using default mode "1920x1440" (hsync out of range) (II) RADEON(0): Not using default mode "1920x1440" (vrefresh out of range) (II) RADEON(0): Not using default mode "832x624" (vrefresh out of range) (II) RADEON(0): Not using default mode "1400x1050" (hsync out of range) (II) RADEON(0): Not using default mode "1400x1050" (vrefresh out of range) (II) RADEON(0): Not using default mode "1920x1440" (vrefresh out of range) (II) RADEON(0): Not using default mode "2048x1536" (hsync out of range) (II) RADEON(0): Not using default mode "2048x1536" (vrefresh out of range) (II) RADEON(0): Not using default mode "2048x1536" (vrefresh out of range) (II) RADEON(0): Printing probed modes for output LVDS (II) RADEON(0): Modeline "1280x800"x60.0 68.90 1280 1288 1328 1408 800 800 803 816 (48.9 kHz) (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) RADEON(0): Output VGA-0 disconnected (II) RADEON(0): Output LVDS connected (II) RADEON(0): Using exact sizes for initial modes (II) RADEON(0): Output LVDS using initial mode 1280x800 initing gart:8000000 vram: s:8000000 v:7c00000 (II) UnloadModule: "radeon" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. _________________________________________________________________ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCB&publ=WLHMTAG&crea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 From zaitcev at redhat.com Sat Aug 15 21:23:46 2009 From: zaitcev at redhat.com (Pete Zaitcev) Date: Sat, 15 Aug 2009 15:23:46 -0600 Subject: Radeon driver broken in 2.6.31-0.125.4.2.rc5.git2.fc11 In-Reply-To: References: Message-ID: <20090815152346.731de2fb@redhat.com> On Sat, 15 Aug 2009 14:15:50 -0700, Markus Kesaromous wrote: > But in 2.6.31-0.125.4.2.rc5.git2, X is unable to start. BTW, it works here on Rawhide, same kernel (a rebuild, obviously): > Current Operating System: Linux localhost.localdomain > 2.6.31-0.125.4.2.rc5.git2.fc11.i686 #1 PREEMPT Fri Aug 14 19:46:56 > PDT 2009 i686 Kernel command line: ro > root=UUID=7cf783f9-8bbb-421c-a919-fd7f6d9ab463 rhgb quiet Build Date: > 18 May 2009 02:47:59PM Build ID: xorg-x11-server 1.6.1.901-1.fc11 .................... > (II) RADEON(0): Output VGA-0 disconnected > (II) RADEON(0): Output LVDS connected > (II) RADEON(0): Using exact sizes for initial modes > (II) RADEON(0): Output LVDS using initial mode 1280x800 > initing gart:8000000 vram: s:8000000 v:7c00000 > (II) UnloadModule: "radeon" > (EE) Screen(s) found, but none have a usable configuration. Here it does: Current Operating System: Linux niphredil.zaitcev.lan 2.6.31-0.125.4.2.rc5.git2.fc12.x86_64 #1 SMP Tue Aug 11 21:00:45 EDT 2009 x86_64 Kernel command line: ro root=/dev/N1/Fedora selinux=0 Build Date: 11 August 2009 02:35:39PM Build ID: xorg-x11-server 1.6.99-33.20090807.fc12 .............. (II) RADEON(0): Output VGA-0 disconnected (II) RADEON(0): Output LVDS connected (II) RADEON(0): Using exact sizes for initial modes (II) RADEON(0): Output LVDS using initial mode 1280x800 +0+0 (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. (II) RADEON(0): mem size init: gart size :2000000 vram size: s:8000000 visible:7c00000 (==) RADEON(0): DPI set to (96, 96) (II) Loading sub module "fb" It looks like some kind of difference between Rawhide and F11. -- Pete From remotestar at live.com Sat Aug 15 22:32:43 2009 From: remotestar at live.com (Markus Kesaromous) Date: Sat, 15 Aug 2009 15:32:43 -0700 Subject: Radeon driver broken in 2.6.31-0.125.4.2.rc5.git2.fc11 In-Reply-To: <20090815152346.731de2fb@redhat.com> References: <20090815152346.731de2fb@redhat.com> Message-ID: ---------------------------------------- > Date: Sat, 15 Aug 2009 15:23:46 -0600 > From: zaitcev at redhat.com > To: remotestar at live.com > CC: fedora-kernel-list at redhat.com > Subject: Re: Radeon driver broken in 2.6.31-0.125.4.2.rc5.git2.fc11 > > On Sat, 15 Aug 2009 14:15:50 -0700, Markus Kesaromous wrote: > >> But in 2.6.31-0.125.4.2.rc5.git2, X is unable to start. > > BTW, it works here on Rawhide, same kernel (a rebuild, obviously): > >> Current Operating System: Linux localhost.localdomain >> 2.6.31-0.125.4.2.rc5.git2.fc11.i686 #1 PREEMPT Fri Aug 14 19:46:56 >> PDT 2009 i686 Kernel command line: ro >> root=UUID=7cf783f9-8bbb-421c-a919-fd7f6d9ab463 rhgb quiet Build Date: >> 18 May 2009 02:47:59PM Build ID: xorg-x11-server 1.6.1.901-1.fc11 > .................... >> (II) RADEON(0): Output VGA-0 disconnected >> (II) RADEON(0): Output LVDS connected >> (II) RADEON(0): Using exact sizes for initial modes >> (II) RADEON(0): Output LVDS using initial mode 1280x800 >> initing gart:8000000 vram: s:8000000 v:7c00000 >> (II) UnloadModule: "radeon" >> (EE) Screen(s) found, but none have a usable configuration. > > Here it does: > > Current Operating System: Linux niphredil.zaitcev.lan 2.6.31-0.125.4.2.rc5.git2.fc12.x86_64 #1 SMP Tue Aug 11 21:00:45 EDT 2009 x86_64 > Kernel command line: ro root=/dev/N1/Fedora selinux=0 > Build Date: 11 August 2009 02:35:39PM > Build ID: xorg-x11-server 1.6.99-33.20090807.fc12 > .............. > (II) RADEON(0): Output VGA-0 disconnected > (II) RADEON(0): Output LVDS connected > (II) RADEON(0): Using exact sizes for initial modes > (II) RADEON(0): Output LVDS using initial mode 1280x800 +0+0 > (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. > (II) RADEON(0): mem size init: gart size :2000000 vram size: s:8000000 visible:7c00000 > (==) RADEON(0): DPI set to (96, 96) > (II) Loading sub module "fb" > > It looks like some kind of difference between Rawhide and F11. > > -- Pete > WOw - that's great that your build went better. I downloaded my source tarball from: http://mirrors.kernel.org/fedora/development/source/SRPMS/kernel-2.6.31-0.125.4.2.rc5.git2.fc12.src.rpm Where can I download the source tarball you used? Cheers, Markus _________________________________________________________________ Windows Live?: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 From kyle at mcmartin.ca Sat Aug 15 23:16:11 2009 From: kyle at mcmartin.ca (Kyle McMartin) Date: Sat, 15 Aug 2009 19:16:11 -0400 Subject: Radeon driver broken in 2.6.31-0.125.4.2.rc5.git2.fc11 In-Reply-To: References: <20090815152346.731de2fb@redhat.com> Message-ID: <20090815231611.GJ25206@bombadil.infradead.org> On Sat, Aug 15, 2009 at 03:32:43PM -0700, Markus Kesaromous wrote: > > > > ---------------------------------------- > > Date: Sat, 15 Aug 2009 15:23:46 -0600 > > From: zaitcev at redhat.com > > To: remotestar at live.com > > CC: fedora-kernel-list at redhat.com > > Subject: Re: Radeon driver broken in 2.6.31-0.125.4.2.rc5.git2.fc11 > > > > On Sat, 15 Aug 2009 14:15:50 -0700, Markus Kesaromous wrote: > > > >> But in 2.6.31-0.125.4.2.rc5.git2, X is unable to start. > > Using the F12 kernel on F-11 is unsupported. You get to keep both pieces. regards, Kyle From SteveD at redhat.com Mon Aug 17 13:49:42 2009 From: SteveD at redhat.com (Steve Dickson) Date: Mon, 17 Aug 2009 09:49:42 -0400 Subject: NFSv4.1 (DEVELOPER ONLY) Message-ID: <4A895FF6.3080507@RedHat.com> I just noticed NFSv4.1 is set to "DEVELOPER ONLY" in the mainline kernel and I wonder if there an guess as to when this will be moved "EXPERIMENTAL"? I was hoping to enable this in upcoming Fedora Development builds so we can get a broader base of testing but I'm a bit hesitant with it being a "DEVELOPER ONLY"... Although, I have done (and will continue to do) regression testing with this enable and have seen any problems, plus this new code does not even come into play unless the mount command explicitly as for it (ala -o minorversion=1) on v4 mounts... which seems to be fairly stable... steved. From androsadamson at gmail.com Mon Aug 17 16:19:27 2009 From: androsadamson at gmail.com (William A. (Andy) Adamson) Date: Mon, 17 Aug 2009 12:19:27 -0400 Subject: [pnfs] NFSv4.1 (DEVELOPER ONLY) In-Reply-To: <4A895FF6.3080507@RedHat.com> References: <4A895FF6.3080507@RedHat.com> Message-ID: <89c397150908170919n5e108b8fq9e23e78e5ea2d8e3@mail.gmail.com> I think NFSv4.0 should be moved from EXPERIMENTAL before NFSv4.1 gets moved from DEVELOPER -> EXPERIMENTAL! What is left to do in NFSv4.0 to allow this to happen? -->Andy On Mon, Aug 17, 2009 at 9:49 AM, Steve Dickson wrote: > I just noticed NFSv4.1 is set to "DEVELOPER ONLY" in the > mainline kernel and I wonder if there an guess as to when > this will be moved "EXPERIMENTAL"? > > I was hoping to enable this in upcoming Fedora Development > builds so we can get a broader base of testing but I'm a bit > hesitant with it being a "DEVELOPER ONLY"... > > Although, I have done (and will continue to do) regression testing > with this enable and have seen any problems, plus this new code > does not even come into play unless the mount command explicitly as > for it (ala -o minorversion=1) on v4 mounts... which seems to be > fairly stable... > > steved. > > _______________________________________________ > pNFS mailing list > pNFS at linux-nfs.org > http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs > From bfields at fieldses.org Mon Aug 17 16:37:13 2009 From: bfields at fieldses.org (J. Bruce Fields) Date: Mon, 17 Aug 2009 12:37:13 -0400 Subject: [pnfs] NFSv4.1 (DEVELOPER ONLY) In-Reply-To: <89c397150908170919n5e108b8fq9e23e78e5ea2d8e3@mail.gmail.com> References: <4A895FF6.3080507@RedHat.com> <89c397150908170919n5e108b8fq9e23e78e5ea2d8e3@mail.gmail.com> Message-ID: <20090817163713.GB27331@fieldses.org> On Mon, Aug 17, 2009 at 12:19:27PM -0400, William A. (Andy) Adamson wrote: > I think NFSv4.0 should be moved from EXPERIMENTAL before NFSv4.1 gets > moved from DEVELOPER -> EXPERIMENTAL! > > What is left to do in NFSv4.0 to allow this to happen? Todo's I know of that should probably be fixed first: - on the client side (we probably want to move client and server out of experimental at roughly the same time, if possible?) there's the mount negotiation to finish. Steve intends his mount configuration stuff to be a first step. - server-side exports coordinated with v2/v3: I need to take a day or two to think about Steve's patches. Will do that soon! - server-side reboot recovery code: the other kernel people really hate the current v4 recovery code, and it has indeed been a generator of weird bugs. I tried to pick this up early this week and write down a basic design, then got distracted. Would like to get this fixed sooner rather than later just because it will likely be a backwards-incompatible change, hence easier to do while there are fewer users. - proper delegation enforcement: currently e.g. if you edit a delegated file with a text editor, delegation-holding clients don't get an update (because the server is not correctly breaking leases on rename/unlink). I have a patch series that needs a few more bug fixes and some review. Some other todo's I can think of that I'm not might also block EXPERIMENTAL removal (but I'm not as sure): - Turn on 4.0 reply cache. Theoretical problem, not sure if we've seen it in practice. - Make sure deferrals don't replay non-idempotent operations. (Neil is close to fixing this.) Theoretical problem, not sure if we've seen it in practice. This is a little off the top of my head; anything I've forgotten? --b. From SteveD at redhat.com Mon Aug 17 18:09:06 2009 From: SteveD at redhat.com (Steve Dickson) Date: Mon, 17 Aug 2009 14:09:06 -0400 Subject: [pnfs] NFSv4.1 (DEVELOPER ONLY) In-Reply-To: <20090817163713.GB27331@fieldses.org> References: <4A895FF6.3080507@RedHat.com> <89c397150908170919n5e108b8fq9e23e78e5ea2d8e3@mail.gmail.com> <20090817163713.GB27331@fieldses.org> Message-ID: <4A899CC2.1080803@RedHat.com> On 08/17/2009 12:37 PM, J. Bruce Fields wrote: > On Mon, Aug 17, 2009 at 12:19:27PM -0400, William A. (Andy) Adamson wrote: >> I think NFSv4.0 should be moved from EXPERIMENTAL before NFSv4.1 gets >> moved from DEVELOPER -> EXPERIMENTAL! >> >> What is left to do in NFSv4.0 to allow this to happen? > > Todo's I know of that should probably be fixed first: > > - on the client side (we probably want to move client and server > out of experimental at roughly the same time, if possible?) > there's the mount negotiation to finish. Steve intends his > mount configuration stuff to be a first step. Which was committed... > - server-side exports coordinated with v2/v3: I need to take a > day or two to think about Steve's patches. Will do that soon! This has been in Fedora's rawhide kernel since early July... with now issues.. yet! ;-) > - server-side reboot recovery code: the other kernel people > really hate the current v4 recovery code, and it has indeed > been a generator of weird bugs. I tried to pick this up early > this week and write down a basic design, then got distracted. > Would like to get this fixed sooner rather than later just > because it will likely be a backwards-incompatible change, > hence easier to do while there are fewer users. > - proper delegation enforcement: currently e.g. if you edit a > delegated file with a text editor, delegation-holding clients > don't get an update (because the server is not correctly > breaking leases on rename/unlink). I have a patch series that > needs a few more bug fixes and some review. Are these in a bug report somewhere? And it sound like that latter is a bit more important than the former.. > > Some other todo's I can think of that I'm not might also block > EXPERIMENTAL removal (but I'm not as sure): > > - Turn on 4.0 reply cache. Theoretical problem, not sure if > we've seen it in practice. Won't enabling nfs41 help with this? > - Make sure deferrals don't replay non-idempotent operations. > (Neil is close to fixing this.) Theoretical problem, not sure > if we've seen it in practice. So probably not a show stopper... steved. From jarod at redhat.com Mon Aug 17 22:00:33 2009 From: jarod at redhat.com (Jarod Wilson) Date: Mon, 17 Aug 2009 18:00:33 -0400 Subject: Recompile kernel without SMP In-Reply-To: <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> Message-ID: <200908171800.34294.jarod@redhat.com> On Friday 14 August 2009 17:24:22 Paul Grinberg wrote: > Markus, > > Thank you for your reply! I already feel better knowing that I'm not > alone :) > Maybe someone might have a clue "Why".... Fedora doesn't ship any single-proc kernels anymore except for on powerpc32. The spec file and sources don't contain an UP target or the necessary support bits (config-foo) to build one for anything but powerpc32, because its mostly pointless. > -----Original Message----- > From: Markus Kesaromous [mailto:remotestar at live.com] > Sent: Friday, August 14, 2009 4:52 PM > To: Paul Grinberg; Linux Kernel List > Subject: RE: Recompile kernel without SMP > > > > Date: Fri, 14 Aug 2009 14:35:22 -0400 > > From: pgrinberg at nyc.saic.com > > To: fedora-kernel-list at redhat.com > > Subject: Recompile kernel without SMP > > > > Hi there, > > > > I am trying to recompile kernel without SMP. So far I've been > > unsuccessful. Meaning I am able to compile, but it was still SMP.. > > > > Can someone tell me what I am doing wrong? > > And why I don't get "kernel-headers" build? > > > > It is probably related to spec parameters.... > > > > So far this is what I've done: > > > > cd ~/ > > rpmdev-setuptree # as regular user > > cd rmpbuild > > yumdownloader --source kernel # as regular user > > > > cd ~/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.i686/ > > cp configs/kernel-2.6.29.6-i586.config .config > > make menuconfig # console setup > > > > Select option: Processor type and features. > > Disable "Symmetric multi-processing support" (SMP) > > > > cp .config ~/rpmbuild/SOURCES/config-i686-generic > > cp .config ~/rpmbuild/SOURCES/config-i686 > > cd ~/rpmbuild/SPECS > > nano kernel.spec > > Add line: > > % define buildid .NONSMP > > Replace: > > > > # Allow kernel-firmware building > > #%define with_firmware %{?_with_firmware: 1} %{?!_with_firmware: 0} > > %define with_firmware %{?_with_firmware: 0} %{?!_with_firmware: 1} > > > > #%define with_firmware %{?_without_firmware: 0} %{?!_without_firmware: > > 1} > > %define with_firmware %{?_without_firmware: 1} %{?!_without_firmware: > > 0} > > > > # Allow kernel-headers building > > > > # Allow kernel-devel building > > > > # Create RPM package > > rpmbuild -bb --with firmware --target=i686 kernel.spec > > > > # To actually install kernel > > su > > rpm -ivh kernel-firmware-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > > kernel-PAE-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > > kernel-PAE-devel-2.6.29.6-217.2.3.nonsmp.fc11.i686.rpm > > > > > > > > Just in case: > > $ cat config-i686-PAE | egrep -i "smp" | more > > CONFIG_BROKEN_ON_SMP=y > > # CONFIG_SMP is not set > > CONFIG_X86_FIND_SMP_CONFIG=y > > # CONFIG_X86_VSMP is not set > > CONFIG_SCSI_SAS_HOST_SMP=y > > CONFIG_VIDEO_VP27SMPX=m > > > > > > > > > > > > Best, > > Paul > > > > > > I just got bit by a similar problem in trying to build > > kernel-2.6.31-0.125.4.2.rc5.git2.fc12.src.rpm > > I followed the steps outlined in > > http://fedoraproject.org/wiki/Docs/CustomKernel > > > > I only wanted to build i686 architecture > > - without SMP > > - without cpu id support > > - without multicore support > > - without hyperthreading support > > - with kernel config support > > - with kernel config via /proc support > > - with frequency default governor set to Performance > > - with preemptible kernel > > - with rt2860 module support > > - with NTFS read/write support > > > > Well, it ended up building i686-PAE Debug kernel with SMP support. > > > > It seems as if the architecture is i686, then only i686 PAE Debug gets > built. > > > > I do not know where the problem lies, but ....SOURCES/Makefile.config > > might be the place where the target kernel build is being selected. > > To get around it, I edited > ...SOURCES/Makefile.config and removed all rules and definitions > pertaining to i686-PAE and only left the simple i686 def and rule. > > PS: I do not know if this is necessary, but after I copied .config to > ...SOURCES/config-i686 > I also copied it to > ...SOURCES/config-x86-generic > > Then running rpmbuild -v -bb --target=i686 kernel.spec > is proceeding without problems > > MK -- Jarod Wilson jarod at redhat.com From pgrinberg at nyc.saic.com Mon Aug 17 22:20:24 2009 From: pgrinberg at nyc.saic.com (Paul Grinberg) Date: Mon, 17 Aug 2009 18:20:24 -0400 Subject: Recompile kernel without SMP In-Reply-To: <200908171800.34294.jarod@redhat.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> <200908171800.34294.jarod@redhat.com> Message-ID: <12AE7DE71168B8419F619FF3079F969C0B1E1726@nyc-1250-srv04.nyc.com> Jarod, Thank you for the reply! Do you know how to "fix" it. What needs to be done to compile non-SMP? Best, Paul -----Original Message----- From: Jarod Wilson [mailto:jarod at redhat.com] Sent: Monday, August 17, 2009 6:01 PM To: fedora-kernel-list at redhat.com Cc: Paul Grinberg; Markus Kesaromous Subject: Re: Recompile kernel without SMP On Friday 14 August 2009 17:24:22 Paul Grinberg wrote: > Markus, > > Thank you for your reply! I already feel better knowing that I'm not > alone :) > Maybe someone might have a clue "Why".... Fedora doesn't ship any single-proc kernels anymore except for on powerpc32. The spec file and sources don't contain an UP target or the necessary support bits (config-foo) to build one for anything but powerpc32, because its mostly pointless. From jwboyer at gmail.com Tue Aug 18 00:12:17 2009 From: jwboyer at gmail.com (Josh Boyer) Date: Mon, 17 Aug 2009 20:12:17 -0400 Subject: Recompile kernel without SMP In-Reply-To: <12AE7DE71168B8419F619FF3079F969C0B1E1726@nyc-1250-srv04.nyc.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> <200908171800.34294.jarod@redhat.com> <12AE7DE71168B8419F619FF3079F969C0B1E1726@nyc-1250-srv04.nyc.com> Message-ID: <20090818001217.GF3095@hansolo.jdub.homelinux.org> On Mon, Aug 17, 2009 at 06:20:24PM -0400, Paul Grinberg wrote: >Jarod, > >Thank you for the reply! Do you know how to "fix" it. What needs to be >done to compile non-SMP? Why do you want this non-SMP kernel? As Jarod said, it's mostly pointless for x86 to build UP. Most of the SMP operations are runtime patched so you don't have the SMP overhead on a UP machine as I understand things. josh From pgrinberg at nyc.saic.com Tue Aug 18 00:17:29 2009 From: pgrinberg at nyc.saic.com (Paul Grinberg) Date: Mon, 17 Aug 2009 20:17:29 -0400 Subject: Recompile kernel without SMP In-Reply-To: <20090818001217.GF3095@hansolo.jdub.homelinux.org> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> <200908171800.34294.jarod@redhat.com> <12AE7DE71168B8419F619FF3079F969C0B1E1726@nyc-1250-srv04.nyc.com> <20090818001217.GF3095@hansolo.jdub.homelinux.org> Message-ID: <12AE7DE71168B8419F619FF3079F969C0B1E1753@nyc-1250-srv04.nyc.com> Josh, I have a good reason for that. I use Cisco VPN client for Linux, and it does not work with SMP kernel. So I have to use Windows to login VPN....which is very annoying :))) Also, it is probably good from the learning perspective.... Best, Paul -----Original Message----- From: Josh Boyer [mailto:jwboyer at gmail.com] Sent: Monday, August 17, 2009 8:12 PM To: Paul Grinberg Cc: Jarod Wilson; fedora-kernel-list at redhat.com; Markus Kesaromous Subject: Re: Recompile kernel without SMP On Mon, Aug 17, 2009 at 06:20:24PM -0400, Paul Grinberg wrote: >Jarod, > >Thank you for the reply! Do you know how to "fix" it. What needs to be >done to compile non-SMP? Why do you want this non-SMP kernel? As Jarod said, it's mostly pointless for x86 to build UP. Most of the SMP operations are runtime patched so you don't have the SMP overhead on a UP machine as I understand things. josh From davej at redhat.com Tue Aug 18 00:27:22 2009 From: davej at redhat.com (Dave Jones) Date: Mon, 17 Aug 2009 20:27:22 -0400 Subject: Recompile kernel without SMP In-Reply-To: <12AE7DE71168B8419F619FF3079F969C0B1E1753@nyc-1250-srv04.nyc.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> <200908171800.34294.jarod@redhat.com> <12AE7DE71168B8419F619FF3079F969C0B1E1726@nyc-1250-srv04.nyc.com> <20090818001217.GF3095@hansolo.jdub.homelinux.org> <12AE7DE71168B8419F619FF3079F969C0B1E1753@nyc-1250-srv04.nyc.com> Message-ID: <20090818002722.GB25168@redhat.com> On Mon, Aug 17, 2009 at 08:17:29PM -0400, Paul Grinberg wrote: > Josh, > > I have a good reason for that. I use Cisco VPN client for Linux, and it > does not work with SMP kernel. Have you tried the vpnc package ? The binary cisco module has an hurrendous track record of problems with the Fedora kernel, as it seemingly makes assumptions about networking internals that constantly change upstream, leading to all sorts of horrible corruption bugs. vpnc isn't perfect, but for many cisco setups, it's adequate, and does all the complicated stuff in userspace. Dave From pgrinberg at nyc.saic.com Tue Aug 18 00:44:42 2009 From: pgrinberg at nyc.saic.com (Paul Grinberg) Date: Mon, 17 Aug 2009 20:44:42 -0400 Subject: Recompile kernel without SMP In-Reply-To: <20090818002722.GB25168@redhat.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <12AE7DE71168B8419F619FF3079F969C0B1E11EC@nyc-1250-srv04.nyc.com> <200908171800.34294.jarod@redhat.com> <12AE7DE71168B8419F619FF3079F969C0B1E1726@nyc-1250-srv04.nyc.com> <20090818001217.GF3095@hansolo.jdub.homelinux.org> <12AE7DE71168B8419F619FF3079F969C0B1E1753@nyc-1250-srv04.nyc.com> <20090818002722.GB25168@redhat.com> Message-ID: <12AE7DE71168B8419F619FF3079F969C0B1E175D@nyc-1250-srv04.nyc.com> Dave, I did, vpnc works for some of the VPNs, but not for the others. Nature of my work requires to deal with multiple RA solutions. Thanks for the advice though. Here is what I got from Cisco: "Unfortunately it is not as simple as providing you with which options to compile the kernel with. Since the issue is the kernel is locking up it is something fundamentally wrong with either the updated kernel code or the vpn client." and then they said that it will take loooong time to fix it, because Cisco VPN client is not a priority. (everyone is moving towards SSL VPN solutions....). Best, Paul -----Original Message----- From: Dave Jones [mailto:davej at redhat.com] Sent: Monday, August 17, 2009 8:27 PM To: Paul Grinberg Cc: Josh Boyer; fedora-kernel-list at redhat.com; Markus Kesaromous Subject: Re: Recompile kernel without SMP On Mon, Aug 17, 2009 at 08:17:29PM -0400, Paul Grinberg wrote: > Josh, > > I have a good reason for that. I use Cisco VPN client for Linux, and it > does not work with SMP kernel. Have you tried the vpnc package ? The binary cisco module has an hurrendous track record of problems with the Fedora kernel, as it seemingly makes assumptions about networking internals that constantly change upstream, leading to all sorts of horrible corruption bugs. vpnc isn't perfect, but for many cisco setups, it's adequate, and does all the complicated stuff in userspace. Dave From jarod at redhat.com Tue Aug 18 13:44:08 2009 From: jarod at redhat.com (Jarod Wilson) Date: Tue, 18 Aug 2009 09:44:08 -0400 Subject: Recompile kernel without SMP In-Reply-To: <12AE7DE71168B8419F619FF3079F969C0B1E1753@nyc-1250-srv04.nyc.com> References: <12AE7DE71168B8419F619FF3079F969C0B1E114A@nyc-1250-srv04.nyc.com> <20090818001217.GF3095@hansolo.jdub.homelinux.org> <12AE7DE71168B8419F619FF3079F969C0B1E1753@nyc-1250-srv04.nyc.com> Message-ID: <200908180944.08608.jarod@redhat.com> On Monday 17 August 2009 20:17:29 Paul Grinberg wrote: > Josh, > > I have a good reason for that. I use Cisco VPN client for Linux, and it > does not work with SMP kernel. I vaguely recall using the cisco vpn client for linux on an smp kernel just fine, but I stopped using it years ago, as vpnc works well enough as a replacement for it. > >Thank you for the reply! Do you know how to "fix" it. What needs to be > >done to compile non-SMP? I do know how, but its semi-involved, and I'm afraid I'm a bit tied up with other slightly more pressing work. Short version is that you need to add a config-foo target in merge.pl, iirc, add that to the spec as another Source, tweak instances of %with_up within the spec file, and that would at least get you close. But again, I think this is really pointless, since 1) I'm pretty sure the cisco vpn client runs fine on smp 2) if it doesn't, vpnc works reasonably well to replace it and 3) you can likely just boot the current smp-enabled kernel with maxcpus=1 added to the command line to get up behavior if you absolutely must run the cisco vpn client in a single-processor environment. -- Jarod Wilson jarod at redhat.com From cebbert at redhat.com Tue Aug 18 15:52:22 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 18 Aug 2009 11:52:22 -0400 Subject: [PATCH 0/3] iwl3945 driver fixes for Fedora 11 (2.6.29) In-Reply-To: <20090814144425.GM2650@tuxdriver.com> References: <1248359742-15865-1-git-send-email-sgruszka@redhat.com> <20090814143502.GA3832@dhcp-lab-161.englab.brq.redhat.com> <20090814144425.GM2650@tuxdriver.com> Message-ID: <20090818115222.51862217@dhcp-100-2-144.bos.redhat.com> On Fri, 14 Aug 2009 10:44:25 -0400 "John W. Linville" wrote: > On Fri, Aug 14, 2009 at 04:35:03PM +0200, Stanislaw Gruszka wrote: > > On Thu, Jul 23, 2009 at 04:35:39PM +0200, Stanislaw Gruszka wrote: > > > Due to backport of patch > > > > > > linux-2.6-iwl3945-report-killswitch-changes-even-if-the-interface-is-down.patch > > > > > > we have bunch of iwl3945 bugs (race conditions) that are not reproducible > > > on vanilla 2.6.29. These patches address them (at least some of them). > > > > I see in cvs that F10 is moving to 2.6.29, so these patches should go F-10 too. > > I'm heading out for the weekend. Would someone else care to shepherd this? I've added those three plus the recent TX queue fix from F-11. From remotestar at live.com Fri Aug 21 05:21:37 2009 From: remotestar at live.com (Markus Kesaromous) Date: Thu, 20 Aug 2009 22:21:37 -0700 Subject: rpmbuild warning message Message-ID: In building 2.6.29..6-217.2.8.fc11 from source rpm for i586 architecture on a machine with amd athlon64 cpu, I get this warning message: arch/x86/kernel/pvclock.c:63:7: warning: "__x86_64__" is not defined Thing is, I have no problems running i586 kernel, and even the resulting kernel runs fine. It appears to be an error in the code, where #elif __x86_64__ ought to be changed to #elif defined(__x86_64__) Cheers, MK _________________________________________________________________ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCB&publ=WLHMTAG&crea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 From pebolle at tiscali.nl Fri Aug 21 09:30:46 2009 From: pebolle at tiscali.nl (Paul Bolle) Date: Fri, 21 Aug 2009 11:30:46 +0200 Subject: rpmbuild warning message In-Reply-To: References: Message-ID: <1250847046.1710.6.camel@localhost.localdomain> On Thu, 2009-08-20 at 22:21 -0700, Markus Kesaromous wrote: > In building 2.6.29..6-217.2.8.fc11 from source rpm for i586 > architecture on a machine with amd athlon64 cpu, I get this warning > message: > > arch/x86/kernel/pvclock.c:63:7: warning: "__x86_64__" is not defined See commit 2ad76643ff58bb8841f391ea8327c14abe273ea3 ("x86: Fix warning in pvclock.c") for the identical fix in the upstream kernel (i.e. Linus' git tree). Paul Bolle From remotestar at live.com Fri Aug 21 15:24:24 2009 From: remotestar at live.com (Markus Kesaromous) Date: Fri, 21 Aug 2009 08:24:24 -0700 Subject: rpmbuild warning message In-Reply-To: <1250847046.1710.6.camel@localhost.localdomain> References: <1250847046.1710.6.camel@localhost.localdomain> Message-ID: ---------------------------------------- > From: pebolle at tiscali.nl > To: remotestar at live.com > Date: Fri, 21 Aug 2009 11:30:46 +0200 > CC: fedora-kernel-list at redhat.com > Subject: Re: rpmbuild warning message > > On Thu, 2009-08-20 at 22:21 -0700, Markus Kesaromous wrote: >> In building 2.6.29..6-217.2.8.fc11 from source rpm for i586 >> architecture on a machine with amd athlon64 cpu, I get this warning >> message: >> >> arch/x86/kernel/pvclock.c:63:7: warning: "__x86_64__" is not defined > > See commit 2ad76643ff58bb8841f391ea8327c14abe273ea3 ("x86: Fix warning > in pvclock.c") for the identical fix in the upstream kernel (i.e. Linus' > git tree). > > > Paul Bolle Thank you Paul. There are numerous other warnings which seem to be inconsequential as far as compilation goes. I was wondering if there is a concerted effort to thouroughly lint the kernel and get rid of all those warnings. Cheers, MK _________________________________________________________________ Windows Live: Keep your friends up to date with what you do online. http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009 From pebolle at tiscali.nl Fri Aug 21 16:08:44 2009 From: pebolle at tiscali.nl (Paul Bolle) Date: Fri, 21 Aug 2009 18:08:44 +0200 Subject: rpmbuild warning message In-Reply-To: References: <1250847046.1710.6.camel@localhost.localdomain> Message-ID: <1250870924.17766.10.camel@x61.thuisdomein> On Fri, 2009-08-21 at 08:24 -0700, Markus Kesaromous wrote: > There are numerous other warnings which seem to be inconsequential as > far as compilation goes. I was wondering if there is a concerted > effort to thoroughly lint the kernel and get rid of all those > warnings. The kernel build system is very quiet by default. As far as I know it is that quiet (among other things) to make warnings stand out. Valid fixes for warnings (as the commit I pointed you to) should be accepted without too much trouble. Paul Bolle From mbejaranoc at gmail.com Wed Aug 19 08:19:25 2009 From: mbejaranoc at gmail.com (Manuel Bejarano) Date: Wed, 19 Aug 2009 10:19:25 +0200 Subject: Dell Mini 10v Microphone FIX Message-ID: <1250669968.2554.6.camel@helena> Hi! The internal mic does not work under Fedora 11 latest kernel (2.6.29.6-217.2.8.fc11). People from Ubuntu [1] submitted a patch backported from 2.6.30 since it is fixed on this version. Could it be possible to apply it for the next fedora's kernel release? Regards, Manuel Bejarano. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/394793 From rolf.offermanns at gmx.net Fri Aug 28 12:34:49 2009 From: rolf.offermanns at gmx.net (Rolf Offermanns) Date: Fri, 28 Aug 2009 14:34:49 +0200 Subject: F11 - vmlinuz-2.6.29.6-217.2.16.fc11.i586 does not boot Message-ID: <4A97CEE9.5090908@gmx.net> Hi All, I recently updatet my kernel first to vmlinuz-2.6.29.6-217.2.8.fc11.i586 and then to vmlinuz-2.6.29.6-217.2.16.fc11.i586 and neither of them bootet on my system. Currently I am back to vmlinuz-2.6.29.6-217.2.3.fc11.i586 which runs fine. My kernel commandline looks like this: "rhgb quiet nomodeset" (mode setting never worked right for me). The only thing I get to see when booting one of the not working kernels is the output of the usb probing with my mouse being the last device found. After this the system just does nothing. It does not hang completely though since I am able to reboot with ctrl-alt-delete. If I press those keys, the kernel prints "md: stopping all devices" (or something very similar) and reboots. I thought about filling a bug, but I don't really know what to write besides "does not boot". Does anyone have the slightest idea what the problem might be? Thanks, Rolf. From schaiba at gmail.com Fri Aug 28 12:42:11 2009 From: schaiba at gmail.com (Aioanei Rares) Date: Fri, 28 Aug 2009 15:42:11 +0300 Subject: F11 - vmlinuz-2.6.29.6-217.2.16.fc11.i586 does not boot In-Reply-To: <4A97CEE9.5090908@gmx.net> References: <4A97CEE9.5090908@gmx.net> Message-ID: <4A97D0A3.40302@gmail.com> On 08/28/2009 03:34 PM, Rolf Offermanns wrote: > Hi All, > > I recently updatet my kernel first to vmlinuz-2.6.29.6-217.2.8.fc11.i586 > and then to vmlinuz-2.6.29.6-217.2.16.fc11.i586 and neither of them > bootet on my system. > > Currently I am back to vmlinuz-2.6.29.6-217.2.3.fc11.i586 which runs fine. > > My kernel commandline looks like this: "rhgb quiet nomodeset" (mode > setting never worked right for me). > > The only thing I get to see when booting one of the not working kernels > is the output of the usb probing with my mouse being the last device > found. After this the system just does nothing. It does not hang > completely though since I am able to reboot with ctrl-alt-delete. If I > press those keys, the kernel prints "md: stopping all devices" (or > something very similar) and reboots. > > I thought about filling a bug, but I don't really know what to write > besides "does not boot". > > Does anyone have the slightest idea what the problem might be? > > Thanks, > Rolf. > > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list > > Try removing your USB mouse and see if it boots. From remotestar at live.com Fri Aug 28 20:07:03 2009 From: remotestar at live.com (Markus Kesaromous) Date: Fri, 28 Aug 2009 13:07:03 -0700 Subject: Release F11 stuck at 2.6.29 ??? Message-ID: When will 2.6.30 and 2.6.31 be released as updates for F11???? Why is F11 being kept at 2.6.29? That is what F11 was initially released at, and it is still stuck at this release? I would like to know if and when 2.6.3X will be released as an updated for F11. MK _________________________________________________________________ Windows Live: Keep your friends up to date with what you do online. http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009 From jwboyer at gmail.com Fri Aug 28 20:11:49 2009 From: jwboyer at gmail.com (Josh Boyer) Date: Fri, 28 Aug 2009 16:11:49 -0400 Subject: Release F11 stuck at 2.6.29 ??? In-Reply-To: References: Message-ID: <20090828201149.GB9390@hansolo.jdub.homelinux.org> On Fri, Aug 28, 2009 at 01:07:03PM -0700, Markus Kesaromous wrote: > >When will 2.6.30 and 2.6.31 be released as updates for F11???? >Why is F11 being kept at 2.6.29? That is what F11 was initially >released at, and it is still stuck at this release? > >I would like to know if and when 2.6.3X will be released as an updated for F11. If you just can't wait, you could always try rawhide. It has the latest kernel available. josh From drago01 at gmail.com Fri Aug 28 20:17:30 2009 From: drago01 at gmail.com (drago01) Date: Fri, 28 Aug 2009 22:17:30 +0200 Subject: Release F11 stuck at 2.6.29 ??? In-Reply-To: References: Message-ID: On Fri, Aug 28, 2009 at 10:07 PM, Markus Kesaromous wrote: > > When will 2.6.30 and 2.6.31 be released as updates for F11???? > Why is F11 being kept at 2.6.29? That is what F11 was initially > released at, and it is still stuck at this release? > > I would like to know if and when 2.6.3X will be released as an updated for F11. There are 2.6.30 builds in updates-testing From remotestar at live.com Fri Aug 28 20:23:32 2009 From: remotestar at live.com (Markus Kesaromous) Date: Fri, 28 Aug 2009 13:23:32 -0700 Subject: Release F11 stuck at 2.6.29 ??? In-Reply-To: <20090828201149.GB9390@hansolo.jdub.homelinux.org> References: <20090828201149.GB9390@hansolo.jdub.homelinux.org> Message-ID: ---------------------------------------- > Date: Fri, 28 Aug 2009 16:11:49 -0400 > From: jwboyer at gmail.com > To: remotestar at live.com > CC: fedora-kernel-list at redhat.com > Subject: Re: Release F11 stuck at 2.6.29 ??? > > On Fri, Aug 28, 2009 at 01:07:03PM -0700, Markus Kesaromous wrote: >> >>When will 2.6.30 and 2.6.31 be released as updates for F11???? >>Why is F11 being kept at 2.6.29? That is what F11 was initially >>released at, and it is still stuck at this release? >> >>I would like to know if and when 2.6.3X will be released as an updated for F11. > > If you just can't wait, you could always try rawhide. It has the latest > kernel available. > > josh Hi Josh, I did try it (and I posted that on fedora-list). It does not support my radeon 9600 graphics chip. I thought the problem was with xorg driver, but that same driver works just fine in 2.6.29.6-217.2.8.fc11.i586 Today, yum updates daemon flagged that 2.6.29.6-217.2.16.fc11.i586 is available. So I am presently running the update process. The thing is I see already that 2.6.31 is being labeled as a fedora 12 package!! That is why I said that it would appear that F11 seems to be stuck at 2.6.29. Cheers, MK _________________________________________________________________ Windows Live: Keep your friends up to date with what you do online. http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009 From remotestar at live.com Fri Aug 28 23:53:21 2009 From: remotestar at live.com (Markus Kesaromous) Date: Fri, 28 Aug 2009 16:53:21 -0700 Subject: Installing and running rawhide Message-ID: _________________________________________________________________ Hotmail? is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_faster:082009 From georgi at forkbomb.nl Sat Aug 29 05:42:24 2009 From: georgi at forkbomb.nl (Georgi Hristozov) Date: Sat, 29 Aug 2009 08:42:24 +0300 Subject: Release F11 stuck at 2.6.29 ??? In-Reply-To: References: <20090828201149.GB9390@hansolo.jdub.homelinux.org> Message-ID: <105690ab0908282242x1fa92832w9d41f45a71e552fa@mail.gmail.com> On Fri, Aug 28, 2009 at 11:23 PM, Markus Kesaromous wrote: >> > > Hi Josh, > > I did try it (and I posted that on fedora-list). It does not support my radeon 9600 graphics chip. I thought the problem was with xorg driver, > but that same driver works just fine in 2.6.29.6-217.2.8.fc11.i586 > > Today, yum updates daemon flagged that 2.6.29.6-217.2.16.fc11.i586 > is available. So I am presently running the update process. > > The thing is I see already that 2.6.31 is being labeled as ?a > fedora 12 package!! > That is why I said that it would appear that F11 seems to be stuck at 2.6.29. > > Cheers, > > MK > Hi, 2.6.31 is currently in testing phase upstream, as well as F12, so don't expect to see it in the stable F11 (at least in the next few weeks). It's place is in rawhide. F11 is based on 2.6.29 and 2.6.30 has been pushed to updates-testing to avoid forcing the user to upgrade to rawhide if a new driver is needed. So F11 is not stuck at 2.6.29 and maybe it will migrate to 2.6.30 in the future. The kernel upgrades are a serious business and it's normal for the developers to be more conservative. By the way, if you experience any problems with rawhide, report them on bugzilla, not on the mailing lists. Or at least at Fedora-testing :) Cheers, Georgi From develop at tom-ipp.info Fri Aug 28 23:52:16 2009 From: develop at tom-ipp.info (tom-ipp) Date: Sat, 29 Aug 2009 01:52:16 +0200 Subject: snd-vxpocket in kernel not enabled in fedora ? Message-ID: <4A986DB0.5010301@tom-ipp.info> 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 should be included in the fedora kernel... Compilation of the module from alsa 1.0.20 lib is ok. Thanks Thomas