Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 98599 - make bzImage error with fb devices (vesa/rivafb/nvidiafb)
Summary: make bzImage error with fb devices (vesa/rivafb/nvidiafb)
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-10 14:26 UTC by brankob
Modified: 2005-07-25 03:35 UTC (History)
1 user (show)

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 brankob 2005-07-10 14:26:50 UTC
with aforementioned drivers selected as modules, "make bzImage" fails. 
It fails somewhere in the final linking stage.   

Reproducible: Always
Steps to Reproduce:
1. after "make menuconfig" select "support for framebuffer devices
2.select as Modules : " VESA VGA graphics support", "nVidia Framebuffer
Support", "nVidia Riva support"  
3. make bzImage


Actual Results:  
make[1]: `arch/x86_64/kernel/asm-offsets.s' is up to date.
  CHK     include/linux/compile.h
  CHK     usr/initramfs_list
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
drivers/built-in.o(.data+0x6778): undefined reference to `cfb_fillrect'
drivers/built-in.o(.data+0x6780): undefined reference to `cfb_copyarea'
drivers/built-in.o(.data+0x6788): undefined reference to `cfb_imageblit'
drivers/built-in.o(.data+0x6790): undefined reference to `soft_cursor'
make: *** [.tmp_vmlinux1] Error 1


Expected Results:  
correct bzImage file in arch/x86_64/boot
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2005-07-10 14:52:39 UTC

*** This bug has been marked as a duplicate of 98598 ***
Comment 2 brankob 2005-07-10 15:23:40 UTC
(In reply to comment #0)

1. I forgot to menition that kernel in queestion was the newest
gentoo-sources-2.6.12.r4

2. I don't understand, how could this be aliased with a bug No. 98598.

That one mentions X11 driver in "nvidia-kernel"- nivida's closed source external
driver installer while mine covers framebuffer driver in gentoo-sources

Furthermore, poster of bug #98598 says that nvidia framebuffer works for him
(since "nv" driver in xorg.conf works) so that means his framebuffer drivers
compile and work O.K...

On the end, he doesn't even mention his kernel version, and judging from
"nvidia-kernel" version (6629) it seems his kernel was quite an old one, while
mine is probably only a few hours in portage tree, marked as stable...




Comment 3 Carsten Lohrke (RETIRED) gentoo-dev 2005-07-10 15:41:49 UTC
> 2. I don't understand

I do not either. Seems I accidentally looked at the same bug twice and took
yours as dupe. Sorry. ;)
Comment 4 Michal Januszewski (RETIRED) gentoo-dev 2005-07-11 07:40:34 UTC
Does setting VESA VGA graphics support to Y or N fix the problem? (note that the
vesafb driver will not work as a module, and vesafb-tng, which would work, is
not available on amd64)
Comment 5 Daniel Drake (RETIRED) gentoo-dev 2005-07-25 03:35:26 UTC
see comment #4