Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 80238 - [xorg] r128 driver can't run on vesa framebuffer : unresolved symbols
Summary: [xorg] r128 driver can't run on vesa framebuffer : unresolved symbols
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-31 11:04 UTC by Hubert Mercier (RETIRED)
Modified: 2005-10-12 19:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hubert Mercier (RETIRED) gentoo-dev 2005-01-31 11:04:40 UTC
I'm currently running Xorg on fbdev, because of TV-out facilities (vesa framebuffer activates TV output directly at boot time). But if i choose r128 driver, xorg refuses to launch. I have to run with generic vesa driver to get X. 

Reproducible: Always
Steps to Reproduce:
1.get a vesa framebuffer kernel
2.emerge xorg
3.try to use r128 driver on top of fbdev

Actual Results:  
Xorg refuses to launch and tells me :

(II) R128(0): PCI bus 1 card 0 func 0
(**) R128(0): Depth 16, (--) framebuffer bpp 16
(II) R128(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) R128(0): Default visual is TrueColor
(**) R128(0): Option "UseFBDev" "true"
(==) R128(0): RGB weight 565
(II) R128(0): Using 6 bits per RGB (8 bit DAC)
(**) R128(0): Using framebuffer device
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) Module fbdevhw: vendor="X.Org Foundation"
        compiled for 6.8.0, module version = 0.0.2
        ABI class: X.Org Video Driver, version 0.7
(--) R128(0): Chipset: "ATI Rage 128 Pro GL PF (AGP)" (ChipID = 0x5046)
(--) R128(0): Linear framebuffer at 0xf8000000
(--) R128(0): MMIO registers at 0xef800000
(--) R128(0): BIOS at 0xf7fe0000
Symbol xf86PrintEDID from module /usr/X11R6/lib/modules/drivers/r128_drv.o is
unresolved!
Symbol xf86SetDDCproperties from module
/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
Symbol xf86DoEDID_DDC2 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is
unresolved!
Symbol xf86SetDDCproperties from module
/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/r128_drv.o
is unresolved!
Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/r128_drv.o
is unresolved!

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


Expected Results:  
X should have started correctly, using fbdev device.

First : xorg.conf of course.

Section "Module"

    Load        "dbe"   # Double buffer extension
    SubSection  "extmod"
      #Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
    Load        "type1"
    Load        "freetype"
    #Load       "glx"
    #Load       "dri"

EndSection


Section "Files"

    RgbPath     "/usr/lib/X11/rgb"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
    #FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/local/"
    #FontPath   "/usr/share/fonts/Speedo/"
    #FontPath   "/usr/share/fonts/TrueType/"
    #FontPath   "/usr/share/fonts/freefont/"
    ModulePath "/usr/X11R6/lib/modules"

    #ModulePath "/usr/X11R6/lib/modules-extra/gatos"

EndSection


Section "ServerFlags"

EndSection


Section "InputDevice"

    Identifier  "Keyboard1"
    Driver      "kbd"
    Option "AutoRepeat" "500 30"
    Option "XkbModel"   "pc105"
    Option "XkbLayout"  "fr"

EndSection


Section "InputDevice"

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "PS/2"
    Option "Device"      "/dev/input/mice"

EndSection


Section "Monitor"

    Identifier  "TV"
    HorizSync   30-50
    VertRefresh 60

EndSection


Section "Device"

    Identifier  "ATI Rage128 Pro"
    Driver      "r128"
    Option      "UseFBDev"      "true"
    Option      "TVOut"

    #Option     "HWCursor"      "false"
    #Option     "SWCursor"      "true"
    #Option     "no_accel"
    #Option     "sw_cursor"
    #VideoRam    32768
    # Insert Clocks lines here if appropriate

EndSection


Section "Screen"
    Identifier  "Screen 1"
    Device      "ATI Rage128 Pro"
    Monitor     "TV"
    DefaultDepth 16

    Subsection "Display"
        Depth       8
        Modes
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "800x600"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "800x600"
        ViewPort    0 0
    EndSubsection
EndSection


Section "ServerLayout"

    Identifier  "Simple Layout"
    Screen "Screen 1"
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection


Section "DRI"
    Mode 0666
EndSection






then, emerge info:

Portage 2.0.51-r15 (default-linux/x86/2005.0, gcc-3.3.5,
glibc-2.3.4.20040808-r1, 2.6.10 i686)
=================================================================
System uname: 2.6.10 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Nov 12 2004, 21:10:20)]
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r5
sys-devel/automake:  1.8.5-r1
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.2-r7
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer"
DISTDIR="/home/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://gentoo.mirror.sdv.fr"
MAKEOPTS=" -j2"
PKGDIR="/home/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aalib alsa apm avi berkdb bitmap-fonts crypt cups dga dvd encode f77
fbcon flac foomaticdb fortran gatos gdbm gif gpm imlib jpeg libcaca libg++
libwww lirc mad mikmod mmx motif mpeg ncurses nls oggvorbis oss pam pdflib perl
png python qt quicktime readline real rtc samba sdl slang spell sse ssl svga
tcpd theora tiff truetype truetype-fonts type1-fonts xml2 xv zlib
video_cards_rage128 linguas_fr"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS


And last : xorg output when I try to startx :

X Window System Version 6.8.0
Release Date: 8 September 2004
X Protocol Version 11, Revision 0, Release 6.8
Build Operating System: Linux 2.6.10 i686 [ELF]
Current Operating System: Linux neskaya 2.6.10 #2 Sat Jan 29 20:21:47 CET 2005 i686
Build Date: 30 January 2005
        Before reporting problems, check http://wiki.X.Org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 31 19:33:16 2005
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
Symbol xf86PrintEDID from module /usr/X11R6/lib/modules/drivers/r128_drv.o is
unresolved!
Symbol xf86SetDDCproperties from module
/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
Symbol xf86DoEDID_DDC2 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is
unresolved!
Symbol xf86SetDDCproperties from module
/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/r128_drv.o
is unresolved!
Symbol xf86ForceHWCursor from module /usr/X11R6/lib/modules/drivers/r128_drv.o
is unresolved!

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.
Comment 1 Donnie Berkholz (RETIRED) gentoo-dev 2005-01-31 11:48:45 UTC
Anyone got a good idea?
Comment 2 Adam Jackson 2005-01-31 12:36:51 UTC
i strongly suspect that you can't run _any_ driver on vesafb besides vesa(4).  there should be a kernel framebuffer driver explicitly for the rage128.
Comment 3 Donnie Berkholz (RETIRED) gentoo-dev 2005-01-31 13:02:39 UTC
So, I think we've got Alex's patch in 6.8.1.902 to use r128 without fbdev. Try changing UseFBDev to false.
Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2005-01-31 13:05:19 UTC
nevermind that's a ppc thing and you're on x86 .. try it anyhow, shouldn't need patch.
Comment 5 Hubert Mercier (RETIRED) gentoo-dev 2005-02-01 02:11:42 UTC
In fact, the only way to activate TV-out on this card is to boot on a vesa framebuffer (it works very well).

But, the only way to get a decent CPU usage while reading videos on it is to have XV extension in X. So, I have tu use r128 driver or ati driver. But, both refuse to activate TV output. After reading doc (example here for the r128 driver : http://unixhelp.ed.ac.uk/CGI/man-cgi?r128+4), I found that using the specific driver on top of the vesa framebuffer could solve my problem (it has been done successfully with other drivers, I found a few pages about this way to deal the problem). This way, the xfree driver would be able to deal with hardware functions of the card, while using framebuffer interface. But these unresolved symbols prenvent me to confirm this.

Another way to deal with could be to use another framebuffer driver (aty128). I tried this solution, but it doesn't activate TV-out at boot, and the only tool I know to do this (atitvout) is deprecated and doesn't work on my machine.

So... I don't see any other solution.

Any suggestions welcome, of course, and thanks for these.
Comment 6 Donnie Berkholz (RETIRED) gentoo-dev 2005-10-12 19:50:14 UTC
This is an upstream bug. Please file it at bugs.freedesktop.org, xorg product,
and post the URL here.