Bug 123546 - Missing necessary kernel modules? fbgen.o
Summary: Missing necessary kernel modules? fbgen.o
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-19 09:36 UTC by Edward Grace
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2004-05-19 11:26:14 UTC

Attachments (Terms of Use)

Description Edward Grace 2004-05-19 09:36:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; HP-UX B.11.00 9000/785)

Description of problem:
It appears as though some common kernel modules (notably fbgen.o) are
missing from the default 2.4.21-9.EL and 2.4.21-15.EL kernels.

As a result of this inserting a third party driver module (viafb.o)
fails since it expects many of the symbols in fbgen.o to be present.

fbgen.o is present on my RH8 box under


for which things compile and resolve happily (though I cannot insert
the module since I don't have a via display).  Under the EL kernel the
"cupboard is bare", very few modules are there

ls /lib/modules/2.4.21-15.EL/kernel/drivers/video/
fbcon-vga-planes.o  intel  vga16fb.o

However, under the kernel-source for the 2.4.21-15.EL kernel the
driver source code does appear to be present.

ls /usr/src/linux-2.4.21-15.EL/drivers/video/fbgen.c

Presumably you havn't "forgotten" to compile the fbgen.o module in the
kernel release.  I imagine it is not there for good reason.  I would
like to know why it isn't there and the best way of compiling it so I
don't go and break the up2date mechanism.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Download the Via driver from
2. unzip
3. make
4. as root make install
5. depmod -a for good measure
6. modprobe viafb

Actual Results:  modprobe viafb
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_get_fix_Rf49afcda
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_set_var_Re45df3fa
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_set_cmap_Re1cd309c
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_update_var_R2a35b499
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_set_disp_R0240245b
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_switch_R8a3ae91b
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_get_var_R95c78eae
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_blank_Ra9198ecf
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_pan_display_R7f2ff96e
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: unresolved
symbol fbgen_get_cmap_R0f0bd4bd
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: insmod
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o failed
/lib/modules/2.4.21-15.EL/kernel/drivers/video/viafb.o: insmod viafb

Expected Results:  The module should be happily inserted....

Additional info:

The undefined symbols in viafb.o appear to belong to fbgen.o.  On my
RH8 box which has fbgen.o dumping the symbol information yields:

nm /lib/modules/2.4.20-28.8/kernel/drivers/video/fbgen.o | egrep " fbgen_"
000007bc T fbgen_blank_R10acb57c
000004dc T fbgen_do_set_var_R42d82c0c
000002b8 T fbgen_get_cmap_Re5c7df1e
00000000 T fbgen_get_fix_R6b4690df
0000007c T fbgen_get_var_R6642422d
00000698 T fbgen_install_cmap_Rd97bc3de
00000414 T fbgen_pan_display_R4d3cf1dc
00000350 T fbgen_set_cmap_R5a6dee09
00000558 T fbgen_set_disp_R2791dfa9
000000ec T fbgen_set_var_R8f75ba23
00000748 T fbgen_switch_Rbbfe95d3
0000070c T fbgen_update_var_Rb8eabdca

Comment 1 Rik van Riel 2004-05-19 11:26:14 UTC
In RHEL3 fbgen.o isn't a supported driver.  However, it is present in
the kernel-unsupported RPM.

If you want fbgen, please install kernel-unsupported.

Note You need to log in before you can comment on or make changes to this bug.