[arch-dev-public] linux-3.8.0-1
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
greetings tpowa
On 02/20/2013 07:50 PM, Tobias Powalowski wrote:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
greetings tpowa
Hi,
Just place it in staging.
Am 20.02.2013 19:13, schrieb Ionut Biru:
On 02/20/2013 07:50 PM, Tobias Powalowski wrote:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
greetings tpowa
Hi,
Just place it in staging.
Done, please all maintainers grab 3.8.0 from staging and try to build your modules against it.
Thanks greetings tpowa
On Wed, Feb 20, 2013 at 07:19:08PM +0100, Tobias Powalowski wrote:
Am 20.02.2013 19:13, schrieb Ionut Biru:
On 02/20/2013 07:50 PM, Tobias Powalowski wrote:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
greetings tpowa
Hi,
Just place it in staging.
Done, please all maintainers grab 3.8.0 from staging and try to build your modules against it.
Thanks greetings tpowa
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
here a simple patch for the nvidia drivers for 3.8
On 20/02/13 20:19, Tobias Powalowski wrote:
Am 20.02.2013 19:13, schrieb Ionut Biru:
On 02/20/2013 07:50 PM, Tobias Powalowski wrote:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
greetings tpowa
Hi,
Just place it in staging.
Done, please all maintainers grab 3.8.0 from staging and try to build your modules against it.
I rebuilt all modules against 3.8 and moved everything to [testing].
Also a note to Virtualbox's maintainers; it doesn't build with gsoap>=2.8.13; a couple of header files don't get generated and the build later fails when kmk_builtin_mv is called with no files to move.
For now I rebuilt Virtualbox using gsoap 2.8.11 (2.8.12 works too).
On Thu, Feb 21, 2013 at 4:28 AM, Evangelos Foutras evangelos@foutrelis.com wrote:
On 20/02/13 20:19, Tobias Powalowski wrote:
Am 20.02.2013 19:13, schrieb Ionut Biru:
On 02/20/2013 07:50 PM, Tobias Powalowski wrote:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
greetings tpowa
Hi,
Just place it in staging.
Done, please all maintainers grab 3.8.0 from staging and try to build your modules against it.
I rebuilt all modules against 3.8 and moved everything to [testing].
Also a note to Virtualbox's maintainers; it doesn't build with gsoap>=2.8.13; a couple of header files don't get generated and the build later fails when kmk_builtin_mv is called with no files to move.
Yep, I'm looking for a workaround.
I'm wondering if the addition of the patch was needed. I use vbox without the patch with a 3.8.0 since yesterday with no issue.
Cheers,
On 21 February 2013 17:11, Sébastien Luttringer seblu@seblu.net wrote:
I'm wondering if the addition of the patch was needed. I use vbox without the patch with a 3.8.0 since yesterday with no issue.
It's needed for virtualbox-guest-dkms to work; see:
https://forums.virtualbox.org/viewtopic.php?f=3&t=53708 https://www.virtualbox.org/changeset/44317/vbox
Am 20.02.2013 18:50, schrieb Tobias Powalowski:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
Just a quick note as I cannot debug this atm. Updating from 3.7 to 3.8 breaks wireless connections on my netbook. The relevant message in the journal seems to be "kernel: wlan: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded".
I use the brcmsmac module on a BCM4313 chip. /etc/conf.d/wireless-regdom is set to DE (but well, this works fine with previous kernels).
PS: Is there an easy way to disable this regulatory checks?
Greetings,
Pierre
On 25 February 2013 17:27, Pierre Schmitz pierre@archlinux.de wrote:
Just a quick note as I cannot debug this atm. Updating from 3.7 to 3.8 breaks wireless connections on my netbook. The relevant message in the journal seems to be "kernel: wlan: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded".
I actually see this from time to time with Intel card too when using 3.8. But I usually get connected after a few attempts.
Lukas
Am 25.02.2013 18:27, schrieb Pierre Schmitz:
Am 20.02.2013 18:50, schrieb Tobias Powalowski:
Hi, I built the kernel, now there are issues with nvidia, lirc and propably other binary modules, Do you want the kernel already in testing or should I place it somewhere else for the maintainers of the modules?
Just a quick note as I cannot debug this atm. Updating from 3.7 to 3.8 breaks wireless connections on my netbook. The relevant message in the journal seems to be "kernel: wlan: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded".
I use the brcmsmac module on a BCM4313 chip. /etc/conf.d/wireless-regdom is set to DE (but well, this works fine with previous kernels).
PS: Is there an easy way to disable this regulatory checks?
Good news: this seems to be fixed with 3.8.1.
participants (7)
-
Evangelos Foutras
-
Ike Devolder
-
Ionut Biru
-
Lukas Jirkovsky
-
Pierre Schmitz
-
Sébastien Luttringer
-
Tobias Powalowski