Code: Select all
ebuild love-sources-2.6.0-r2.ebuild digestyou should have a directory index as in original portage.. you said your dir is /usr/local/portage. You have to put the ebuild ingaio wrote:downloaded the .ebuild file to usr/local/portage and edited my make.conf to point to that dir...
Code: Select all
/usr/local/portage/sys-kernel/love-sourcesCode: Select all
ebuild <love-sources.ebuild> digestCode: Select all
emerge love-sourcesI am. I have a Radeon 9100. I see the same problem with 2.6.0-mm1 as well so it seems to be something in the -mm tree. I did not have the problem with 2.6.0-test10-mm and I skipped over 2.6.0-test11-mm so I am not sure exactly when this problem crept in. I wonder if it is just with Radeon cards.teilo wrote:Ok. I am up and running on 2.6.0-love2. Good work, Steel300.
However, my DRI is really wacked. It's a Radeon Mobility 7500.
Anything with GL basically works, except that nothing gets erased from the screen. As objects are redrawn, the old version of the objects remains visible, thus causing a "trail" effect. This would seem to have something to do with buffering, I'm guessing. All the XScreensaver GL's screens are effected.
The glxgears program shows the same effect.
My previous kernel (2.6.0-Test11-love2) was fine, so it has to be something new here.
Anyone else noticing this?

Cool... Worked like a charm this time around... thanks for the help... unfortunately i wont have the time to work/install the new kernel now... jumping on a train in an hour visiting my fiancees family in southern sweden... which mean no computer and no gentoo for the next 5 days...at_chaos wrote:you should have a directory index as in original portage.. you said your dir is /usr/local/portage. You have to put the ebuild ingaio wrote:downloaded the .ebuild file to usr/local/portage and edited my make.conf to point to that dir...then the digest thingCode: Select all
/usr/local/portage/sys-kernel/love-sourcesafter that you can do aCode: Select all
ebuild <love-sources.ebuild> digestcorrect me if I'm wrongCode: Select all
emerge love-sources
There exists different strategies how the kernel could schedule the Input/Output. No single strategy is better than all others in every situation, therefore there exists different such strategies. With elevator= you can select a specific io-scheduler for the kernel to use.gaio wrote: Someone wrote that we should use elevator=cfq as kernel config. What exactly does this do?
And is there any readme explaining what patches have been applied to the kernel and what they do? The bootsplash i understand, but would like to know what the mm optimizations do exactly..
Ahh ... thanks for making this clear, I did think of those as one and the same. Guess, I have to do some more reading on these things...PrakashKC wrote:@asimon
Nope, you have to differentate between's Nicks as io scheduler and his CPU scheduler.The latter one was "core" of love sources (not yet inside this release) replacing Con's scheduler, but his as scheduler became default of mainline 2.6.
Yeah, Steel300 forgot to update EXTRAVERSION (againMrNugget wrote:if i do "uname -a" it shows me love1, but i've patched with love2
Code: Select all
Unable to handle kernel NULL pointer dereference at virtual address 00000024
printing eip:
c0162e3b
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c0162e3b>] Tainted: PF VLI
EFLAGS: 00210246
EIP is at set_blocksize+0x3b/0x90
eax: 00000000 ebx: 00000800 ecx: 00000200 edx: de794244
esi: de794200 edi: de794040 ebp: d6a83eb4 esp: d6a83ea8
ds: 007b es: 007b ss: 0068
Process pktsetup (pid: 6249, threadinfo=d6a82000 task=dd32e040)
Stack: d6a83ebc de794200 dfa31cc0 d6a83ed0 e1983a0b de794200 00000800 00000000
dfa31cc0 de794040 d6a83f0c c0163a96 de794040 d7600bc0 c0163370 c0163390
d6a83efc d6a82000 de79404c d6a83f0c e1988080 00000000 d7600bc0 d7600bc0
Call Trace:
[<e1983a0b>] pkt_open+0xeb/0x120 [pktcdvd]
[<c0163a96>] do_open+0x156/0x460
[<c0163370>] bdev_test+0x0/0x20
[<c0163390>] bdev_set+0x0/0x20
[<c0163e42>] blkdev_open+0x32/0x80
[<c015a73a>] dentry_open+0x15a/0x230
[<c015a5d6>] filp_open+0x66/0x70
[<c015aa83>] sys_open+0x53/0x90
[<c02f64c3>] syscall_call+0x7/0xb
Code: 75 08 8d 83 00 fe ff ff 3d 00 0e 00 00 77 07 8d 43 ff 85 d8 74 0d b8 ea ff ff ff 8b 5d f8 8b 75 fc c9 c3 8b 46 40 b9 00 02 00 00 <8b> 40 24 85 c0 74 10 0f b7 80 8e 01 00 00 0f b7 d0 66 85 c0 0f