Bug 60069

Summary: i810 unresolved symbol on kernel 2.4.9-21
Product: [Retired] Red Hat Linux Reporter: haplowtf
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-02-25 10:33:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
startx trace output
none
X config file
none
X log none

Description haplowtf 2002-02-19 18:01:59 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.9-21 i686)

Description of problem:
X  (version 4.0.3-5) worked on kernel 2.4.9-12. After updating the kernel to
2.4.9-21 X just gives a blank screen. The X trace output mentions VBEInit and
vbeDoEDID as unresolved symbols in /usr/X11R6/lib/modules/drivers/i810_drv.o

Version-Release number of selected component (if applicable):
XFree86 4.0.3-5
Kernel 2.4.9-21

How reproducible:
Always

Steps to Reproduce:
1.rpm -U kernel-2.4.9-21.i686.rpm kernel-headers-2.4.9-21.i386.rpm
2.reboot
3.startx
	

Actual Results:  Got a blank screen. Alt-F1 returns to the terminal with the
startx trace output.

Expected Results:  X should have started.

Additional info:

From the startx trace output:
Symbol VBEInit from module /usr/X11R6/lib/modules/drivers/i810_drv.o is
unresolved!
Symbol vbeDoEDID from module /usr/X11R6/lib/modules/drivers/i810_drv.o is
unresolved!

I installed the 2.4.9-12 kernel and that works fine.
Comment 1 haplowtf 2002-02-19 18:27:27 UTC 
Created attachment 46063 [details]
startx trace output
Comment 2 Mike A. Harris 2002-02-23 02:32:40 UTC 
Attach X config file, and X logs please.
Comment 3 haplowtf 2002-02-25 09:41:55 UTC 
Created attachment 46580 [details]
X config file
Comment 4 haplowtf 2002-02-25 09:44:08 UTC 
Created attachment 46581 [details]
X log
Comment 5 Mike A. Harris 2002-03-14 18:21:46 UTC 
Upgrading the kernel should not in any way cause this.  The kernel
has nothing to do with XFree86 module symbols.  This message only
comes up when XFree86 tries to load a module and cannot resolve the
module's symbols.  That occurs when the config file is missing some
module load statements to load the modules that provide the given
symbols, or when the module has a bug in which the module does not
request the symbol lists properly.

In this case, it looks like probably the latter.  If the problem persists
try upgrading to XFree86 4.1.0-15 which we've released as erratum.