Hi guys,
first try with 3.0 kernel,
nvidia legacy is not building, due to some makefile conftest
restriction, patches are welcome.
nvidia-173xx updated to 173.14.31 and built fine against linux 3.0.
Have fun and find issues.
greetings
tpowa
--
IonuČ›
07-24-2011, 01:09 PM
Ray Rashif
kernel 3.0 enters testing
On 24 July 2011 16:34, Tobias Powalowski
<tobias.powalowski@googlemail.com> wrote:
> Hi guys,
> first try with 3.0 kernel,
> nvidia legacy is not building, due to some makefile conftest
> restriction, patches are welcome.
>
> Have fun and find issues.
Like I mentioned on IRC, I'd like for the PKGBUILD to be cleaner (it
has collected much inconsistency in style over the years).
I suppose it's mainly a lack of motivation (no-one wants to read
through the entire thing just to fix how the PKGBUILD looks), so I
motivated myself to do it: http://paste.pocoo.org/show/445356/
Just proper spacing, organising, quoting and bracing of variables,
some blank lines, indents..stuff that makes the PKGBUILD _not_ look
like a mess; allows for easier duplication/modification.
--
GPG/PGP ID: 8AADBB10
07-24-2011, 01:52 PM
Evangelos Foutras
kernel 3.0 enters testing
On 24 July 2011 16:09, Ray Rashif <schiv@archlinux.org> wrote:
> On 24 July 2011 16:34, Tobias Powalowski
> <tobias.powalowski@googlemail.com> wrote:
>> Hi guys,
>> first try with 3.0 kernel,
>> nvidia legacy is not building, due to some makefile conftest
>> restriction, patches are welcome.
>>
>> Have fun and find issues.
>
> Like I mentioned on IRC, I'd like for the PKGBUILD to be cleaner (it
> has collected much inconsistency in style over the years).
>
> I suppose it's mainly a lack of motivation (no-one wants to read
> through the entire thing just to fix how the PKGBUILD looks), so I
> motivated myself to do it: http://paste.pocoo.org/show/445356/
>
> Just proper spacing, organising, quoting and bracing of variables,
> some blank lines, indents..stuff that makes the PKGBUILD _not_ look
> like a mess; allows for easier duplication/modification.
That's quite an improvement.
One thing I noticed; some variables still use the $var syntax after
your patch, although ${var} seems to be much more prevalent in the
PKGBUILD. I think it'd be a good idea to change them all to use the
same syntax.
07-24-2011, 09:15 PM
Gerardo Exequiel Pozzi
kernel 3.0 enters testing
On 07/24/2011 05:34 AM, Tobias Powalowski wrote:
Hi guys,
first try with 3.0 kernel,
nvidia legacy is not building, due to some makefile conftest
restriction, patches are welcome.
Have fun and find issues.
greetings
tpowa
I dislike with the kernel image filename "vmlinuz-linux". Is not
friendly for plain ISO 9660 filesystem. Of course is not a big issue,
should be referenced as "vmlinuz_linux" in config for isolinux. Maybe
the same applies for grub2 (if them does not support Rock-Ridge or
Jouliet extensions)
On 07/24/2011 06:15 PM, Gerardo Exequiel Pozzi wrote:
On 07/24/2011 05:34 AM, Tobias Powalowski wrote:
Hi guys,
first try with 3.0 kernel,
nvidia legacy is not building, due to some makefile conftest
restriction, patches are welcome.
Have fun and find issues.
greetings
tpowa
I dislike with the kernel image filename "vmlinuz-linux". Is not
friendly for plain ISO 9660 filesystem. Of course is not a big issue,
should be referenced as "vmlinuz_linux" in config for isolinux. Maybe
the same applies for grub2 (if them does not support Rock-Ridge or
Jouliet extensions)
For archiso I renamed it to vmlinuz.
Note2: What about System.map? In these days I don't use it, but maybe
some program still needs it?
On 07/25/2011 12:34 AM, Gerardo Exequiel Pozzi wrote:
On 07/24/2011 06:15 PM, Gerardo Exequiel Pozzi wrote:
On 07/24/2011 05:34 AM, Tobias Powalowski wrote:
Hi guys,
first try with 3.0 kernel,
nvidia legacy is not building, due to some makefile conftest
restriction, patches are welcome.
Have fun and find issues.
greetings
tpowa
I dislike with the kernel image filename "vmlinuz-linux". Is not
friendly for plain ISO 9660 filesystem. Of course is not a big issue,
should be referenced as "vmlinuz_linux" in config for isolinux. Maybe
the same applies for grub2 (if them does not support Rock-Ridge or
Jouliet extensions)
For archiso I renamed it to vmlinuz.
Note2: What about System.map? In these days I don't use it, but maybe
some program still needs it?
https://bugs.archlinux.org/task/25247
--
IonuČ›
07-24-2011, 09:44 PM
Gerardo Exequiel Pozzi
kernel 3.0 enters testing
On 07/24/2011 06:38 PM, Ionut Biru wrote:
On 07/25/2011 12:34 AM, Gerardo Exequiel Pozzi wrote:
On 07/24/2011 06:15 PM, Gerardo Exequiel Pozzi wrote:
On 07/24/2011 05:34 AM, Tobias Powalowski wrote:
Hi guys,
first try with 3.0 kernel,
nvidia legacy is not building, due to some makefile conftest
restriction, patches are welcome.
Have fun and find issues.
greetings
tpowa
I dislike with the kernel image filename "vmlinuz-linux". Is not
friendly for plain ISO 9660 filesystem. Of course is not a big issue,
should be referenced as "vmlinuz_linux" in config for isolinux. Maybe
the same applies for grub2 (if them does not support Rock-Ridge or
Jouliet extensions)
For archiso I renamed it to vmlinuz.
Note2: What about System.map? In these days I don't use it, but maybe
some program still needs it?
Hi guys,
first try with 3.0 kernel,
nvidia legacy is not building, due to some makefile conftest
restriction, patches are welcome.
Have fun and find issues.
greetings
tpowa
I have no sound out of the hdmi cable with a radeon card. radeon.audio defaults
to 0. When I set it to one manually, still no sound.
07-24-2011, 11:01 PM
Tom Gundersen
kernel 3.0 enters testing
On Mon, Jul 25, 2011 at 12:49 AM, Matthew Monaco <dgbaley27@0x01b.net> wrote:
> I have no sound out of the hdmi cable with a radeon card. radeon.audio
> defaults to 0. When I set it to one manually, still no sound.
I believe radeon.audio now defaults to 0 as it is known to cause
problems. For me it works fine when I force it to 1, but obviously
YMMV. I suggest looking at the kernel bugzilla for bug reports, and
possibly file your own.
kernel 3.0 enters testing
