From: J Sloan <joe@tmsusa.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Partial Success with 2.5.52bk6
Date: Sat, 21 Dec 2002 11:48:56 -0800 [thread overview]
Message-ID: <3E04C5A8.6050204@tmsusa.com> (raw)
Forgive me if any of this is old news -
I loaded up 2.5.52bk6 on a couple of systems here and took it
for a spin - both systems had previously run 2.4.18-RH, 2.4.19-aa,
and 2.4.19/20-ckX
I found it rather impressive - subjectively speaking, the 2.5 kernel
had a snappier feel on the desktop. Mozilla page scrolling remained
smooth while loading a page with many images on 2.5, while scrolling
stuttered and hesitated while loading the same page on 2.4.20-ck2.
2.5 also remained usable while running dbench or ltp -
On the down side, modules that loaded automatically under 2.4 now
have to be manually loaded - for instance my iptables script has
to now first manually load each and every needed module before it
issues any iptables commands or it dies - 2.4 automagically loaded
the required modules.
And now we come to the little show stopper - one of my systems has
an intel motherboard with built-in i810 video. I can manually load
the agp module, but it yields a cosmetic oops:
[drm:drm_init] *ERROR* Cannot initialize the agpgart module.
Uninitialised timer!
This is just a warning. Your computer is OK
function=0x00000000, data=0x0
Call Trace:
[<c011fd01>] check_timer_failed+0x61/0x70
[<c011fffc>] del_timer+0x1c/0x80
[<e095a648>] i830_takedown+0x38/0x3e0 [i830]
[<e095f3f5>] i830_stub_unregister+0x35/0x60 [i830]
[<e092123f>] 0xe092123f
[<e09621e8>] __func__.30+0x0/0x9 [i830]
[<c012b474>] sys_init_module+0x1a4/0x1c0
[<c01095eb>] syscall_call+0x7/0xb
More seriously, any attempt to load the i810 drm module fails:
# modprobe i810
FATAL: Error inserting i810
(/lib/modules/2.5.52bk6/kernel/drivers/char/drm/i810.ko): Cannot
allocate memory
Any hope for i810 drm soon? Other than that it's looking sweet here.
Kudos for an awesome kernel in the making!
Best Regards,
Joe
reply other threads:[~2002-12-21 19:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E04C5A8.6050204@tmsusa.com \
--to=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome