Re: [gentoo-user] 2.4 -> 2.6 wierdness

[Holly Bostick]

Martins Steinbergs schreef:
>> On Wednesday 06 July 2005 12:55, Holly Bostick wrote:
>>
>>>
>>
>>To me, errors in agpgart first suggest that either support for your
>>motherboard's agp chipset is not compiled into the kernel, or --if
>>compiled as a module, is not loaded; and secondly, the outside chance
>>that-- if using an ATI card-- the InternalAGPGART setting is wrong;
<snip>
>>
>>What does dmesg or /var/log/messages say about agpgart? Did it try to
>>load and fail? What does lsmod say is loaded? If nothing, can you
>>modprobe your agpgart module? What is your mobo and video card? If an
>>ATI or nVidia video card, did you re-emerge the drivers after compiling
>>the kernel?
>>
>>Basically, I'd just like to confirm that genkernel didn't drop the ball.
>>
>>Holly

> these are my autoload modules, commented are ones that some HOWTO pointed to
> but never worked.
>
> /etc/modules.autoload.d/kernel-2.6
> agpgart
> #via-agp
> #ati-agp
> fglrx
> #radeon
> rtc
> snd-via82xx
> r8169
> #drm
> amd64-agp

OK, so you have both the via and ati agpgarts commented out, the
amd64-agp module set to load and you *are* using a ATI card with the
fglrx drivers. I don't have an amd64 board, so I don't know if that
module is the correct one for your motherboard, but if you don't have a
VIA-based or ATI-based motherboard (yes, ATI does make motherboards,
lately), you can remove the commented entries for via-agp and ati-agp,
because they have nothing to do with you anyway, and there's no point.

Could you please tell us your motherboard make and model, so we could
determine what module you actually need? The output of lsmod would also
help, to show us what modules are actually loaded.

I also see that you have 'drm' commented. That's not good-- not because
you should be using kernel DRM (first rule of ATI drivers is: 'disable
kernel DRI'), but because it suggests that DRM is going to be set in
some way in your kernel config.... and the default is to compile it
directly into the kernel, which is not affected by
modules.autoload.d/kernel-anything (because it's not a loadable module).

OK so from this point, we could d*ck around with the kernel, or we could
narrow down the problem. I think narrowing down the problem is easier,
especially since you don't seem in a rush to check your logs or post the
logs or give us any details as to what your hardware actually is, or
whatever.

Try this:

open up xorg.conf (/etc/X11/xorg.conf) in a text editor as root (nano
works good for this) and change the following:

# === ATI device section ===

Section "Device"
    Identifier                          "ATI Graphics Adapter"
    Driver                              "fglrx"

to

# === ATI device section ===

Section "Device"
    Identifier                          "ATI Graphics Adapter"
    Driver                              "vesa"

I am assuming with this edit that your server flags at the end of the
config file looks like this:

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen0"
    Device      "ATI Graphics Adapter"
    Monitor     "Monitor0"
    DefaultDepth 24
    #Option "backingstore"

    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1280x960" "1152x864" "1024x768"
"800x600" "640x480"
        ViewPort    0 0  # initial origin if mode is smaller than desktop
#        Virtual     1280 1024
    EndSubsection
EndSection

------------------------------------------------------------------

(which means that the 'screen'-- which is a combination of the video
card and monitor settings specified above this area) is using the
settings for the ATI Graphics adapter device (whose driver we have just
changed to vesa from fglrx). But my xorg.conf looks like this because I
at some point used fglrxconfig, and maybe you haven't.

If your screen section does *not* look like what's above, for whatever
reason, then you can also switch to the vesa driver from the fglrx
driver by editing the Screen section itself:

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen0"
==> Device      "Standard VGA"


--------------------------------------------------------

...because in the Device section exists a default setting:


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier  "Standard VGA"
    VendorName  "Unknown"
    BoardName   "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset     "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver      "vesa" (normally this says 'vga', but I changed it to
vesa, as vga doesn't seem to work for me)

---------------------------------------------------------------

Anyway, what I'm getting at here is

1) Switch to the vesa driver

2) Try to start X and see if it will start.

If it will, then the problem is specifically around the fglrx driver
(you didn't recompile it, so it won't load, or genkernel added something
that conflicts with it, so it won't load).

If it still won't start, the problem is with X itself-- check the logs
to see if it's a settings issue, or try Jerry's suggestion of
recompiling x.org, and/or revdep-rebuild.

Hope this helps,
Holly
-- 
gentoo-user@g.o mailing list