FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 04-20-2008, 03:44 PM
waldek
 
Default

Thomas Bächler wrote:

> The new 2.6.25 kernel and most of the external modules are in [testing].
...
> I wish you all happy testing.

Hi Thomas,
I've noticed that "loop" is not part of the kernel anymore, but available as
a module.

cheers

waldek
 
Old 04-20-2008, 04:06 PM
Thomas Bächler
 
Default

waldek schrieb:

Hi Thomas,
I've noticed that "loop" is not part of the kernel anymore, but available as
a module.


That was intentional. If you frequently use loop mounts, add the module
to rc.conf: MODULES=(...... loop)
 
Old 04-20-2008, 05:07 PM
Dimitrios Apostolou
 
Default

Dream Team wrote:

Le Sunday 20 April 2008 15:23:38 Erwin Van de Velde, vous avez écrit :

On Saturday 19 April 2008, Thomas Bächler wrote:

- Removed mactel patch

The removal of these patches was because a) there are no new patches
available for 2.6.25 and b) I am trying to reduce the amount of
patching, especially if it only benefits a few people or can be
potentially dangerous.
As far as I know, the mactel patch is required for some hardware support
on intel-based mac systems and contains important fixes. This does not seem

like one patch too many, but an essential one for all users who, like me,
have mac hardware.
I do understand your wish to reduce the number of patches, but throwing out
patches required for support of important hardware does not seem the way to
go to me.

Regards,
Erwin


I also am using arch on my mac, and I find this essential and should not be
removed if you find 2.6.25 compatible patchs (I am sure that they will come
out in not so many time)


Arnaud


Hi, I would suggest to test the new kernel on your mac before
complaining, perhaps it supports it better now. And if after that much
time this patch is necessary for such common hardware and hasn't been
imported upstream, I think you should contact the LKML.



Dimitris
 
Old 04-20-2008, 05:15 PM
Thomas Bächler
 
Default

Travis Willard schrieb:

On Sat, Apr 19, 2008 at 7:40 PM, Simo Leone <simo@archlinux.org> wrote:

On Sat, Apr 19, 2008 at 06:09:08PM +0200, =?ISO-8859-1?Q?Thomas_B=E4chler_ wrote:
> - aufs (Simo, could you have a look, you must probably update it)
I'll fix this very soon. It just needs a hug. I'm going to update this
to a later snapshot (aufs doesn't really do releases). That alright?

> - catalyst
Got this one, had to patch 2 or 3 lines due to some api changes in
2.6.25, no big deal (tm). Also updated it to 8.4 while I was at it.



Holy crap you rule Simo. I have guests over this weekend and haven't
really been able to look at it yet.



Apparently, our fix does not work on x86_64, see the thread in the
Desktop section of our forum.
 
Old 04-20-2008, 05:23 PM
Dream Team
 
Default

Le Sunday 20 April 2008 19:07:11 Dimitrios Apostolou, vous avez écrit*:
> Dream Team wrote:
> > Le Sunday 20 April 2008 15:23:38 Erwin Van de Velde, vous avez écrit :
> >> On Saturday 19 April 2008, Thomas Bächler wrote:
> >>> - Removed mactel patch
> >>>
> >>> The removal of these patches was because a) there are no new patches
> >>> available for 2.6.25 and b) I am trying to reduce the amount of
> >>> patching, especially if it only benefits a few people or can be
> >>> potentially dangerous.
> >>
> >> As far as I know, the mactel patch is required for some hardware support
> >> on intel-based mac systems and contains important fixes. This does not
> >> seem like one patch too many, but an essential one for all users who,
> >> like me, have mac hardware.
> >> I do understand your wish to reduce the number of patches, but throwing
> >> out patches required for support of important hardware does not seem the
> >> way to go to me.
> >>
> >> Regards,
> >> Erwin
> >
> > I also am using arch on my mac, and I find this essential and should not
> > be removed if you find 2.6.25 compatible patchs (I am sure that they will
> > come out in not so many time)
> >
> > Arnaud
>
> Hi, I would suggest to test the new kernel on your mac before
> complaining, perhaps it supports it better now. And if after that much
> time this patch is necessary for such common hardware and hasn't been
> imported upstream, I think you should contact the LKML.
>
>
> Dimitris

It seems that many patches have already been commited into vanilla kernel, but
that these patches got minor starting as 2.6.24 ... Now they only add stuff
like keyboard keys support and other stuff. I'm not concerned by most of the
corrections of this patchset, but macbook users might experience problems
with vanilla 2.6.25. (I don't have a macbook for testing)

I think they could make a kernel module for these things, but this is out of
topic here. The point is that kernel26-ice isn't patched for intel macs,
killing some keys on my keyboard but that's all. I really don't know if these
kind of patches should be kept or become part of some AUR package maintained
by users ...

Anyway, the point is that they are now outdated, so they can't be in new Arch
kernel.

Arnaud
 
Old 04-20-2008, 09:39 PM
Andreas Radke
 
Default

Am Sun, 20 Apr 2008 10:27:02 +0200
schrieb Pierre Schmitz <pierre@archlinux.de>:

> Am Samstag, 19. April 2008 18:09:08 schrieb Thomas Bächler:
> > If there are any problems due to the configuration changes or new
> > kernel bugs, please let me know.
>
> I got the following error when using the nvidia driver:
>
>
> NVRM: bad caching on address 0xffff81007c91a000: actual 0x173 !=
> expected 0x17b
> NVRM: please see the README section on Cache Aliasing for more
> information NVRM: bad caching on address 0xffff81007c91b000: actual
> 0x173 != expected 0x17b
> NVRM: bad caching on address 0xffff81007cbad000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb4000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb5000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb6000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb7000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb8000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb9000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbba000: actual 0x173 !=
> expected 0x17b
>
> Even when using the 173.08 beta driver which is meant for kernel
> 2.6.25 I got the same errors. Any ideas?

Same here:

NVRM: bad caching on address 0xffff81022ce78000: actual 0x173 != expected 0x17b
NVRM: please see the README section on Cache Aliasing for more information
NVRM: bad caching on address 0xffff81022ce79000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7a000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7b000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7c000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7d000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7e000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7f000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022c47a000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022cac1000: actual 0x173 !=
expected 0x17b

but seems to work fine so far.

-Andy
 
Old 04-20-2008, 10:19 PM
Dream Team
 
Default

Le Sunday 20 April 2008 15:23:38 Erwin Van de Velde, vous avez écrit*:
> On Saturday 19 April 2008, Thomas Bächler wrote:
> > - Removed mactel patch
> >
> > The removal of these patches was because a) there are no new patches
> > available for 2.6.25 and b) I am trying to reduce the amount of
> > patching, especially if it only benefits a few people or can be
> > potentially dangerous.
>
> As far as I know, the mactel patch is required for some hardware support
> on intel-based mac systems and contains important fixes. This does not seem
> like one patch too many, but an essential one for all users who, like me,
> have mac hardware.
> I do understand your wish to reduce the number of patches, but throwing out
> patches required for support of important hardware does not seem the way to
> go to me.
>
> Regards,
> Erwin

I also am using arch on my mac, and I find this essential and should not be
removed if you find 2.6.25 compatible patchs (I am sure that they will come
out in not so many time)

Arnaud
 
Old 04-21-2008, 01:48 AM
pyther
 
Default

<200804201523.38644.erwin.vandevelde@gmail.com> <200804210019.01554.dreamteam69@gmail.com>
Message-ID: <3aa8b0cfdfae24eaddd723301a7e40ba@localhost>
X-Sender: pyther@pyther.net
Received: from adsl-75-33-46-5.dsl.bcvloh.sbcglobal.net [75.33.46.5] with
HTTP/1.1 (POST); Sun, 20 Apr 2008 21:48:12 -0400
User-Agent: RoundCube Webmail/0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit






On Mon, 21 Apr 2008 00:19:01 +0200, Dream Team <dreamteam69@gmail.com>

wrote:

> Le Sunday 20 April 2008 15:23:38 Erwin Van de Velde, vous avez écritÂ*:

>> On Saturday 19 April 2008, Thomas Bächler wrote:

>> > - Removed mactel patch

>> >

>> > The removal of these patches was because a) there are no new patches

>> > available for 2.6.25 and b) I am trying to reduce the amount of

>> > patching, especially if it only benefits a few people or can be

>> > potentially dangerous.

>>

>> As far as I know, the mactel patch is required for some hardware support

>

>> on intel-based mac systems and contains important fixes. This does not

> seem

>> like one patch too many, but an essential one for all users who, like

> me,

>> have mac hardware.

>> I do understand your wish to reduce the number of patches, but throwing

> out

>> patches required for support of important hardware does not seem the way

> to

>> go to me.

>>

>> Regards,

>> Erwin

>

> I also am using arch on my mac, and I find this essential and should not

> be

> removed if you find 2.6.25 compatible patchs (I am sure that they will

> come

> out in not so many time)

>

> Arnaud



It is one patch to many...

If you want a mactel kernel then you make a package in aur and patch the

kernel sources with the mactel patch. We need to keep the kernel as clean

as possible. The more patches we add the more problems we have. The only

patches that should included are major security patches and/or patches that

fix major hardware issues, devices that are already supported by the

kernel.



Don't like it? Don't use arch, Simple!



We need to get back to the Arch Way!
 
Old 04-21-2008, 11:34 AM
William Barneau
 
Default

*Hi all

I am looking for a solution of Ubuntu for ARM 920

Cannot find on emmebded and seems that Nokia has tested it

Even a beginning will be fine

Thansk in advance

__________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail --
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
 
Old 04-21-2008, 03:32 PM
Attila
 
Default

On Sonntag, 20. April 2008 13:42 Attila wrote:

Sorry for commenting myself and see this please only as an information.

> Okay, now i can say that nvidia 173.08 works and it seems that if you
> run /etc/start_udev the /dev/nvdia* devices get killed.

I step back to a patched 169.12 because i have some seldom redraw problems
with 173.08.

> I recognized that my superkaramba theme shows me about 10 Grad Celsius more
> with kernel26 2.6.25 than with my own kernel package 2.6.24.5 but this is
> again only an information and a will search for the reason by msyself. Only
> for the stats: I load w83627ehf and coretemp.

For everybody else who see higher temperatures with a core2duo you be not
alone:

http://lkml.org/lkml/2008/4/18/190
http://forums.gentoo.org/viewtopic-t-684812-highlight-.html

See you, Attila
 

Thread Tools




All times are GMT. The time now is 11:18 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org