Kernel 2.6.0-2.6.2 problems – 3393 days old

[Walden]

Well everything goes well on the install

tar -zvxf linux-2.6.2
make menuconfig
make bzImage
make install
make modules
make modules_install

everything goes off without a hitch

when i restart, everything loads just fine, except i don't have an X server. it fails and gives me

(EE) GARTInit: Unable to open /dev/agpgart (no device)
(EE) I810 (0): AGP GART support is not available yadda yadda yadda
(EE) Screen found, but none have a usable config

It gets past configuring the Screen sizes and refresh rates, it knows what type of monitor it is... last working lines

(--) I810(0): chipset: I810e"
(--) I810(0): linear frame bufffer at 0xF4000000
(--) I810(0): IO registers at addr 0xFF000000

what the hell. I did enable AGP GART what ever the hell that is when i did the menuconfig.

Everything work just peachy keen, without the X Server

What's goin' on?

[Grogan]

You needed to build both agpgart support, and AGP support for your chipset, in addition to DRI support for your chipset, under character devices.

If you want to start X for now, edit your XF86Config file and comment out glx and dri modules so they don't load.

# This loads the GLX module
# Load "glx"
# This loads the DRI module
#Load "dri"

Though I've yet to see that prevent X from starting.

I also don't know what distribution you're running or how XFree86 is configured on your system.

I usually build agpgart, agp support and DRI as modules (I manually load them with a script before starting X when I want direct rendering support), but I've shown them here as builtin for you.

[Grogan]

Btw... in 2.6.2 watch out for ps/2 mouse problems. Symptoms are mouse goes crazy for a few seconds... moving it clicks on things, menus fly, programs open, buttons get clicked. If it happens, just take your hands off the mouse immediately and wait a few seconds. After it occurs, you'd see something like this in the output of dmesg:

psmouse.c: MX Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

Several of us have been reporting this (it started in 2.6.2-rc2 apparently), but the maintainer of the input drivers hasn't been able to reproduce the problem or nail down the common denominator yet. It's very intermittent, and probably doesn't happen on all hardware.

[Walden]

D'oh the new Fedora Core 1.


Fuckin' awsome, "you the man".

Thanks a bunch.

Yeah they needed to be built-in, not just modules.