View previous topic :: View next topic |
Author |
Message |
fallow Bodhisattva
Joined: 08 Jan 2004 Posts: 2208 Location: Poland
|
Posted: Sat Sep 17, 2005 3:59 pm Post subject: 2.6.14-rc1-vivid1 [mm,ck,gl and fbstuff] |
|
|
info wrote: |
Please note that this patchset is only for fun or testing mm's features with some additional stuff which isnt in mm. Please dont use it as stable patchset because there is a lot of risky stuff. |
* Please don't report any bugs to gentoo-devs or gentoo bugs
what's in a box wrote: |
Code: |
apply it on top of 2.6.14-mm1 or use gentoo ebuild.
* 2.6.13-mm4
* ck patches [ck1]
1gb_lowmem.diff
2.6.14-rc1_to_staircase12.1.diff
hz-default_values.patch
hz-no250.patch
isobatch_ionice2.diff
pdflush-tweaks.patch
rt_ionice.diff
sched-iso3.1.patch
schedbatch2.9.diff
schedrange.diff
smp-nice-support7.diff
vm-background_scan-1.diff
vm-lots_watermark.diff
vm-mapped.diff
vm-swap_prefetch-7.2.patch
--(R) some cpu scheduler patches
* fbsplash-0.9.2-r4-2.6.14-rc1.patch
* vesafb-tng-testing-2005091603.patch
* 2.6.13-mm1-dtck2.patch //dynamic timer ticks to save laptops power//
* 4705_squashfs-2.2.patch //from gentoo-sources//
* J.Moilanen's genetic lib & as-iosched support (.12-gl2) //its off by default//
genetic-as-sched-2.6.12-gl2.patch
genetic-io-sched-2.6.12-gl2.patch
genetic-lib-2.6.12-gl2.patch
* 9018-usbhid-readd-kconfig-r1.patch
* 9017-default-iosched-selection.diff
* 9019-make-colors-blue.diff | |
Everybody knows that mm is just like a kind of playground for 2.6 - so it may be bugged. If You have some problem You can post here of course, but if it seems that its an mm fault - please test pure mm then , and then in error cause , report it to LKML.
NO any kind of nvidia/ati fixes here. It works with my nvidia drivers from portage.
*** Should be no any SMP/SMT related errors this time hehe
http://vivid.dat.pl/fallow/pub/index.php?dir=vivid-sources/2.6.14-rc1-vivid1/
cheers _________________ "Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
Back to top |
|
|
babykart Guru
Joined: 08 Oct 2004 Posts: 415
|
Posted: Sat Sep 17, 2005 7:51 pm Post subject: |
|
|
hehe!!!! it works perfect on a PIV (SATA, reiser4, nvidia...) with SMP and another without....
thx for this excellent job fallow _________________ >> Gentoo-FR <<
----- |
|
Back to top |
|
|
m0p Apprentice
Joined: 20 Jun 2005 Posts: 205 Location: en_GB
|
Posted: Sat Sep 17, 2005 9:19 pm Post subject: |
|
|
I'll try it later. I hope ATi drivers patch for 2.6.12 still works for 2.6.14. |
|
Back to top |
|
|
thubble Tux's lil' helper
Joined: 16 May 2003 Posts: 119 Location: Winnipeg, Canada
|
Posted: Sun Sep 18, 2005 2:47 am Post subject: |
|
|
Works fine, except some device nodes don't show up with udev (tried with both versions 068 and 070). Specifically, the /dev/input directory isn't created, nor are the nodes it contains. Creating the directory and nodes manually works fine. There are no relevant lines in dmesg, and I haven't added any new kernel config options. This problem is easily worked around so it's not a huge deal. Everything else seems to work fine. |
|
Back to top |
|
|
AaronPPC Guru
Joined: 29 May 2005 Posts: 522 Location: Tucson, AZ
|
Posted: Sun Sep 18, 2005 2:56 am Post subject: |
|
|
Same problem here. I'll investigate further and see if the problem shows up in the -mm, -ck or vanilla levels. _________________ --Aaron |
|
Back to top |
|
|
mbar Veteran
Joined: 19 Jan 2005 Posts: 1990 Location: Poland
|
Posted: Sun Sep 18, 2005 7:10 am Post subject: |
|
|
yeah, same here, I've lost /dev/input/mice |
|
Back to top |
|
|
massimo Veteran
Joined: 22 Jun 2003 Posts: 1226
|
Posted: Sun Sep 18, 2005 8:28 am Post subject: |
|
|
mbar wrote: | yeah, same here, I've lost /dev/input/mice |
No mouse for me too. _________________ Hello 911? How are you? |
|
Back to top |
|
|
fallow Bodhisattva
Joined: 08 Jan 2004 Posts: 2208 Location: Poland
|
Posted: Sun Sep 18, 2005 10:38 am Post subject: |
|
|
OK , IT seems that its the only one problem, according to LKML its mm's fault.
I'll do next release today (vivid2) with the fix.
Any suggestions , something to add also ?
cheers _________________ "Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
Back to top |
|
|
Meqif Tux's lil' helper
Joined: 09 Mar 2003 Posts: 103 Location: Portugal
|
Posted: Sun Sep 18, 2005 10:45 am Post subject: |
|
|
It freezes on boot if I use vesafb-tng. If I disable it (I unpatched it) I can boot normally. This also happens on ck + vesafb-tng-testing-2005091603.patch, so I suppose it's a vesafb-tng bug. That aside, I also lost the /dev/input directory. |
|
Back to top |
|
|
mbar Veteran
Joined: 19 Jan 2005 Posts: 1990 Location: Poland
|
Posted: Sun Sep 18, 2005 10:49 am Post subject: |
|
|
fallow wrote: |
Any suggestions , something to add also ?
|
Yep, meh wants 250 Hz patch. |
|
Back to top |
|
|
fallow Bodhisattva
Joined: 08 Jan 2004 Posts: 2208 Location: Poland
|
Posted: Sun Sep 18, 2005 11:17 am Post subject: |
|
|
Meqif wrote: | It freezes on boot if I use vesafb-tng. If I disable it (I unpatched it) I can boot normally. This also happens on ck + vesafb-tng-testing-2005091603.patch, so I suppose it's a vesafb-tng bug. That aside, I also lost the /dev/input directory. |
Are You on x86_64?, and previous version of vesa-tng , I mean this not "testing" one is working correct for You ?
mbar wrote: | fallow wrote: |
Any suggestions , something to add also ?
|
Yep, meh wants 250 Hz patch. |
A patch to remove 250Hz setting is in ck, You mean to remove it , so to give possibility of choosing 250Hz also ?
OK - I'll remove this one.
cheers. _________________ "Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
Back to top |
|
|
bollucks l33t
Joined: 27 Oct 2004 Posts: 606
|
Posted: Sun Sep 18, 2005 12:23 pm Post subject: |
|
|
Read the 2.6.13-ck4 announce you'll see there is a reason 250 is removed on purpose. |
|
Back to top |
|
|
fallow Bodhisattva
Joined: 08 Jan 2004 Posts: 2208 Location: Poland
|
Posted: Sun Sep 18, 2005 12:28 pm Post subject: |
|
|
bollucks wrote: | Read the 2.6.13-ck4 announce you'll see there is a reason 250 is removed on purpose. |
I did it. I saw what Con said about it on #ck and I know about it. _________________ "Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
Back to top |
|
|
Meqif Tux's lil' helper
Joined: 09 Mar 2003 Posts: 103 Location: Portugal
|
Posted: Sun Sep 18, 2005 12:58 pm Post subject: |
|
|
fallow wrote: | Meqif wrote: | It freezes on boot if I use vesafb-tng. If I disable it (I unpatched it) I can boot normally. This also happens on ck + vesafb-tng-testing-2005091603.patch, so I suppose it's a vesafb-tng bug. That aside, I also lost the /dev/input directory. |
Are You on x86_64?, and previous version of vesa-tng , I mean this not "testing" one is working correct for You ? |
Nope, I'm on x86. Vesa-tng has always worked fine for me. I've been using ArchCK, which contains vesa-tng, and I've had no problems with it.
Applying vesafb-tng-0.9-rc7-r1-2.6.13-rc6.patch to this kernel results in compile errors (see below) although there are no rejects while applying the patch, so I can't test it.
Code: | drivers/built-in.o(.text+0x45ebf): In function `vesafb_thread':
: undefined reference to `io_remap_page_range'
drivers/built-in.o(.text+0x45ee9): In function `vesafb_thread':
: undefined reference to `io_remap_page_range'
make: *** [.tmp_vmlinux1] Error 1 |
EDIT: Ok, I patched 2.6.14_rc1-ck1 with vesafb-tng-0.9-rc7-r1-2.6.13-rc6.patch and it's working fine, so it's really vesafb-tng fault: the stable version is ok, while the testing one isn't working as it should. |
|
Back to top |
|
|
mbar Veteran
Joined: 19 Jan 2005 Posts: 1990 Location: Poland
|
Posted: Sun Sep 18, 2005 1:20 pm Post subject: |
|
|
bollucks wrote: | Read the 2.6.13-ck4 announce you'll see there is a reason 250 is removed on purpose. |
thanks, I wasn't aware of that. So, if I have a gentoo router (proxy, QoS, distcc and no X11) and gentoo desktop (and laptop to be exact:) ) should I use 100 Hz on router and 1000 Hz on desktop/laptop? |
|
Back to top |
|
|
fallow Bodhisattva
Joined: 08 Jan 2004 Posts: 2208 Location: Poland
|
Posted: Sun Sep 18, 2005 1:38 pm Post subject: |
|
|
OK , I'll add latest "stable" version of vesa-tng, the io_remap_page_range error can be fixed by reverse of some patch from mm.
250Hz should be better for SMP but as it seems can provide erros 1000Hz is recommended for desktops/laptops and 100Hz for servers.
cheers. _________________ "Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
Back to top |
|
|
Meqif Tux's lil' helper
Joined: 09 Mar 2003 Posts: 103 Location: Portugal
|
Posted: Sun Sep 18, 2005 1:41 pm Post subject: |
|
|
fallow wrote: | OK , I'll add latest "stable" version of vesa-tng, the io_remap_page_range error can be fixed by reverse of some patch from mm. |
Heh, thanks a lot. |
|
Back to top |
|
|
bollucks l33t
Joined: 27 Oct 2004 Posts: 606
|
Posted: Sun Sep 18, 2005 2:49 pm Post subject: |
|
|
mbar wrote: | bollucks wrote: | Read the 2.6.13-ck4 announce you'll see there is a reason 250 is removed on purpose. |
thanks, I wasn't aware of that. So, if I have a gentoo router (proxy, QoS, distcc and no X11) and gentoo desktop (and laptop to be exact:) ) should I use 100 Hz on router and 1000 Hz on desktop/laptop? |
Yes. The only caveat is if power saving is the most important thing to you on the laptop then you can use 100Hz there, but it is less than 5% difference in power usage, and does cost you in interactivity. |
|
Back to top |
|
|
|