2.6.0-test1-ac1 Matrox Compile Error

2.6.0-test1-ac1 Matrox Compile Error

[Adam Voigt]

Let me know if I'm being stupid, but here's the error I get,
and my .config is below:


  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(.text+0x66e7a): In function `matroxfb_set_par':
: undefined reference to `default_grn'
drivers/built-in.o(.text+0x66e7f): In function `matroxfb_set_par':
: undefined reference to `default_blu'
drivers/built-in.o(.text+0x66e93): In function `matroxfb_set_par':
: undefined reference to `color_table'
drivers/built-in.o(.text+0x66e9b): In function `matroxfb_set_par':
: undefined reference to `default_red'
make: *** [.tmp_vmlinux1] Error 1


Config:

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
CONFIG_HAVE_DEC_LOCK=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI Support
#
# CONFIG_ACPI is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_NAMES=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEFLOPPY=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
# CONFIG_BLK_DEV_IDEPCI is not set

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set

#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_CONNTRACK is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_MATCH_LIMIT is not set
# CONFIG_IP_NF_MATCH_MAC is not set
# CONFIG_IP_NF_MATCH_PKTTYPE is not set
# CONFIG_IP_NF_MATCH_MARK is not set
# CONFIG_IP_NF_MATCH_MULTIPORT is not set
# CONFIG_IP_NF_MATCH_TOS is not set
# CONFIG_IP_NF_MATCH_RECENT is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_DSCP is not set
# CONFIG_IP_NF_MATCH_AH_ESP is not set
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
# CONFIG_IP_NF_MATCH_UNCLEAN is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
# CONFIG_IP_NF_TARGET_MIRROR is not set
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_ULOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
# CONFIG_IP_NF_ARPTABLES is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=y
# CONFIG_EEPRO100_PIO is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# I2C Hardware Sensors Mainboard support
#

#
# I2C Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD_8151 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
CONFIG_DRM_MGA=y
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
CONFIG_FB_MATROX=y
# CONFIG_FB_MATROX_MILLENIUM is not set
# CONFIG_FB_MATROX_MYSTIQUE is not set
# CONFIG_FB_MATROX_G450 is not set
CONFIG_FB_MATROX_G100A=y
CONFIG_FB_MATROX_G100=y
# CONFIG_FB_MATROX_MULTIHEAD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set
# CONFIG_USB_GADGET is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_X86_BIOS_REBOOT=y



-- 
Adam Voigt (adam@cryptocomm.com)
Linux/Unix Network Administrator
The Cryptocomm Group

Re: 2.6.0-test1-ac1 Matrox Compile Error

[nick black]

In article <1058285021.2209.13.camel@beowulf.cryptocomm.com>, Adam Voigt wrote:
> Let me know if I'm being stupid, but here's the error I get,
> and my .config is below:
> 
> 
>   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(.text+0x66e7a): In function `matroxfb_set_par':
>: undefined reference to `default_grn'
> drivers/built-in.o(.text+0x66e7f): In function `matroxfb_set_par':
>: undefined reference to `default_blu'
> drivers/built-in.o(.text+0x66e93): In function `matroxfb_set_par':
>: undefined reference to `color_table'
> drivers/built-in.o(.text+0x66e9b): In function `matroxfb_set_par':
>: undefined reference to `default_red'
> make: *** [.tmp_vmlinux1] Error 1

you'll need to build VT support.

-- 
nick black <dank@reflexsecurity.com>
"np:  nondeterministic polynomial-time
the class of dashed hopes and idle dreams." - the complexity zoo

Re: 2.6.0-test1-ac1 Matrox Compile Error

[James Simmons]

> > drivers/built-in.o(.text+0x66e7a): In function `matroxfb_set_par':
> >: undefined reference to `default_grn'
> > drivers/built-in.o(.text+0x66e7f): In function `matroxfb_set_par':
> >: undefined reference to `default_blu'
> > drivers/built-in.o(.text+0x66e93): In function `matroxfb_set_par':
> >: undefined reference to `color_table'
> > drivers/built-in.o(.text+0x66e9b): In function `matroxfb_set_par':
> >: undefined reference to `default_red'
> > make: *** [.tmp_vmlinux1] Error 1
> 
> you'll need to build VT support.

Ug. That is wrong. Fbdev driver are independent of the console layer.

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Adam Voigt]

You were right, I missed VT support on the config, added
it and no more compile errors, thanks very much.




On Tue, 2003-07-15 at 12:16, nick black wrote:
> In article <1058285021.2209.13.camel@beowulf.cryptocomm.com>, Adam Voigt wrote:
> > Let me know if I'm being stupid, but here's the error I get,
> > and my .config is below:
> > 
> > 
> >   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(.text+0x66e7a): In function `matroxfb_set_par':
> >: undefined reference to `default_grn'
> > drivers/built-in.o(.text+0x66e7f): In function `matroxfb_set_par':
> >: undefined reference to `default_blu'
> > drivers/built-in.o(.text+0x66e93): In function `matroxfb_set_par':
> >: undefined reference to `color_table'
> > drivers/built-in.o(.text+0x66e9b): In function `matroxfb_set_par':
> >: undefined reference to `default_red'
> > make: *** [.tmp_vmlinux1] Error 1
> 
> you'll need to build VT support.
-- 
Adam Voigt (adam@cryptocomm.com)
Linux/Unix Network Administrator
The Cryptocomm Group

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Dave Jones]

On Tue, Jul 15, 2003 at 05:40:52PM +0100, James Simmons wrote:

 > > you'll need to build VT support.
 > Ug. That is wrong. Fbdev driver are independent of the console layer.

Regardless, the number of people falling over this issue is still
somewhere in the region of "silly".
The only people who would want to turn off VT support are likely to
be embedded folks, so why not move this under CONFIG_EMBEDDED ?
and force it to '=y' for everyone else ?

		Dave

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Alan Cox]

On Maw, 2003-07-15 at 18:13, Dave Jones wrote:
> On Tue, Jul 15, 2003 at 05:40:52PM +0100, James Simmons wrote:
> 
>  > > you'll need to build VT support.
>  > Ug. That is wrong. Fbdev driver are independent of the console layer.
> 
> Regardless, the number of people falling over this issue is still
> somewhere in the region of "silly".
> The only people who would want to turn off VT support are likely to
> be embedded folks, so why not move this under CONFIG_EMBEDDED ?
> and force it to '=y' for everyone else ?

Seconded  - care to send me a diff for -ac2 8)

Re: 2.6.0-test1-ac1 Matrox Compile Error

[James Simmons]

> >  > > you'll need to build VT support.
> >  > Ug. That is wrong. Fbdev driver are independent of the console layer.
> > 
> > Regardless, the number of people falling over this issue is still
> > somewhere in the region of "silly".
> > The only people who would want to turn off VT support are likely to
> > be embedded folks, so why not move this under CONFIG_EMBEDDED ?
> > and force it to '=y' for everyone else ?
> 
> Seconded  - care to send me a diff for -ac2 8)

   This still doesn't solve the issue with the input api. The input layer 
can be modular on many levels. Even if we force the input core to be built in 
this will not stop people from building the keyabord drivers as modules. 
Having PS/2 support always turned to Y will not also work since there are 
systems that use just USB. Their is a point where users will just have to 
read the README and follow directions. We can't make people do the right 
thing.
   Also doing this kind of thing only covers up broken framebuffer 
drivers. Unfortunetly its going to take me months to cleanup and make the 
fbdev drivers behave right. 

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Alan Cox]

On Maw, 2003-07-15 at 18:43, James Simmons wrote:
>    Also doing this kind of thing only covers up broken framebuffer 
> drivers. Unfortunetly its going to take me months to cleanup and make the 
> fbdev drivers behave right. 

We don't have months. Should we be talking about reverting to the rather
solid 2.4 framebuffer side for 2.6 in this case ?

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Dave Jones]

On Tue, Jul 15, 2003 at 06:43:32PM +0100, James Simmons wrote:

 >    This still doesn't solve the issue with the input api. The input layer 
 > can be modular on many levels. Even if we force the input core to be built in 
 > this will not stop people from building the keyabord drivers as modules. 

That issue seems to have worked itself out now. I think someone already
munged the relevant Kconfig. It's been a while since l-k got a flood of
"I booted 2.5 and my keyboard doesn't work any more", whereas if you
look at all the "2.6test doesn't boot" bug reports of the last week,
and count how many of them were due to CONFIG_VT=n, you'll notice a much
bigger ratio.

 > Having PS/2 support always turned to Y will not also work since there are 
 > systems that use just USB. Their is a point where users will just have to 
 > read the README and follow directions. We can't make people do the right 
 > thing.
 >    Also doing this kind of thing only covers up broken framebuffer 
 > drivers. Unfortunetly its going to take me months to cleanup and make the 
 > fbdev drivers behave right. 

One bug at a time. With the CONFIG_EMBEDDED hack, yes it will 'hide'
this problem, but it'll likely be many months before embedded folks
start thinking of using 2.6 anyways.

		Dave

Re: 2.6.0-test1-ac1 Matrox Compile Error

[James Simmons]

> >    Also doing this kind of thing only covers up broken framebuffer 
> > drivers. Unfortunetly its going to take me months to cleanup and make the 
> > fbdev drivers behave right. 
> 
> We don't have months. Should we be talking about reverting to the rather
> solid 2.4 framebuffer side for 2.6 in this case ?

   Its not that the 2.5.X framebuffer layer is not solid. Except for the 
software cursor it behaves right. The issue I have is the quality of the 
framebuffer drivers. Lets take a example. In the new api we have two new
functions called check_var and set_par. Check_var's job is to test a 
passed in mode to see if the hardware can support it. It is not to alter 
or change any hardware states. The second function set_par does change the
hardware state. Lets look at the Mach64 driver. Mind you it does work and 
functions. We have 

static int atyfb_check_var(struct fb_var_screeninfo *var,
                           struct fb_info *info)
{
        struct atyfb_par *par = (struct atyfb_par *) info->par;
        struct crtc crtc;
        union aty_pll pll;
        int err;
                                                                                  
        if ((err = aty_var_to_crtc(info, var, &crtc)) ||
            (err = par->pll_ops->var_to_pll(info, var->pixclock,
                                        var->bits_per_pixel, &pll)))
                return err;
                                                                                  
#if 0   /* fbmon is not done. uncomment for 2.5.x -brad */
        if (!fbmon_valid_timings(var->pixclock, htotal, vtotal, info))
                return -EINVAL;
#endif
        aty_crtc_to_var(&crtc, var);
        var->pixclock = par->pll_ops->pll_to_var(info, &pll);
	return 0;
}

We can see here that we first pass var into aty_var_to_crtc to generate a
crtc struct. Then at the end we do the reverse and use that crtc to create
a var. This is horribly done. Now lets look at what is in set_par.

        if ((err = aty_var_to_crtc(info, var, &par->crtc)) ||
            (err = par->pll_ops->var_to_pll(info, var->pixclock,
                                        var->bits_per_pixel, &par->pll)))
                return err;

Its being called twice. Once in check_var and again in set_par. Mind you 
this works but the implementation is horribly done. I see this done alot 
in various drivers. The reason it was done this way was because people 
wanted a quick port to the new api without thinking much about it. 
   
    What makes me sad is I added accel hooks to speed up the console but I 
don't see anyone using there accel engines. Everyone is just using my soft 
accel functions :-( Using the soft accel was to be the exception not the 
rule.

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Jörn Engel]

On Tue, 15 July 2003 18:57:59 +0100, Dave Jones wrote:
> 
> One bug at a time. With the CONFIG_EMBEDDED hack, yes it will 'hide'
> this problem, but it'll likely be many months before embedded folks
> start thinking of using 2.6 anyways.

s/many month/half a second/

Even for embedded, 2.[56] is so much nicer that I wouldn't want to do
any new project with 2.4 anymore.  Continue the old ones, all right,
but that's about it.

Jörn

-- 
Premature optimization is the root of all evil.
-- Donald Knuth

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Dave Jones]

On Tue, Jul 15, 2003 at 08:49:09PM +0200, J?rn Engel wrote:

 > > One bug at a time. With the CONFIG_EMBEDDED hack, yes it will 'hide'
 > > this problem, but it'll likely be many months before embedded folks
 > > start thinking of using 2.6 anyways.
 > s/many month/half a second/
 > 
 > Even for embedded, 2.[56] is so much nicer that I wouldn't want to do
 > any new project with 2.4 anymore.  Continue the old ones, all right,
 > but that's about it.

Sorry, any vendor contemplating shipping 2.6test in a device at this stage
is a lunatic.  I don't care about lunatics.  As we saw recently there
are a lot of wireless routers and the like out there all stuck on some
magical 2.4.5 kernel. That sucks, but it's at least better than putting
beta quality code in something people pay money for.

		Dave

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Jörn Engel]

On Tue, 15 July 2003 20:13:28 +0100, Dave Jones wrote:
> 
> Sorry, any vendor contemplating shipping 2.6test in a device at this stage
> is a lunatic.  I don't care about lunatics.  As we saw recently there
> are a lot of wireless routers and the like out there all stuck on some
> magical 2.4.5 kernel. That sucks, but it's at least better than putting
> beta quality code in something people pay money for.

Well, the good old embedded process is this:

Take what's availlable (2.4.5 then).
Adapt to the hardware.
Test for a while.
Ship it.
Don't touch it anymore.

So what is lunatic about doing the same with 2.6test?  It may make the
test a little more expensive, but the adaptation will be cheaper, so
you are just about even.  And the result is no less frightening than a
2.4.2 kernel with various backports from 2.4.younameit, and even more
quick hacks.

The only thing we agree on is that it would be loony to port known
working hardware to a newer kernel.

Jörn

-- 
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Dave Jones]

On Tue, Jul 15, 2003 at 09:28:53PM +0200, J?rn Engel wrote:

 > So what is lunatic about doing the same with 2.6test?

Simple, there are known problems in 2.6.0test.
At the time of embedded folks using 2.4.5, there were no known problems.

		Dave

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Jörn Engel]

On Tue, 15 July 2003 20:32:24 +0100, Dave Jones wrote:
> On Tue, Jul 15, 2003 at 09:28:53PM +0200, J?rn Engel wrote:
> 
>  > So what is lunatic about doing the same with 2.6test?
> 
> Simple, there are known problems in 2.6.0test.
> At the time of embedded folks using 2.4.5, there were no known problems.

The VM was enough of a problem for one flamewar or another.  There is
even a faint memory of major construction work around 2.4.10.

You may be right for an x86 design that work out of the box, but I got
used to extensive adjustments and just as extensive test afterwards.
If those test are successful, the kernel is stable by definition,
whatever the known problems may be.

Jörn

-- 
Eighty percent of success is showing up.
-- Woody Allen

Re: 2.6.0-test1-ac1 Matrox Compile Error

[James Simmons]

> That issue seems to have worked itself out now. I think someone already
> munged the relevant Kconfig. It's been a while since l-k got a flood of
> "I booted 2.5 and my keyboard doesn't work any more", whereas if you
> look at all the "2.6test doesn't boot" bug reports of the last week,
> and count how many of them were due to CONFIG_VT=n, you'll notice a much
> bigger ratio.

Strange that CONFIG_VT would get set to no. Another huge issue is that 
people are configuring several framebuffer drivers to run the same piece 
of hardware. 

Re: 2.6.0-test1-ac1 Matrox Compile Error

[Dave Jones]

On Thu, Jul 17, 2003 at 06:03:02PM +0100, James Simmons wrote:

 > Strange that CONFIG_VT would get set to no. Another huge issue is that 
 > people are configuring several framebuffer drivers to run the same piece 
 > of hardware. 

A number of people seem to be seeing regressions with vesafb too.
Configs that worked with 2.4 give a blank screen, and lock up under 2.5
I believe vga=791 was one such option.

		Dave

Re: 2.6.0-test1-ac1 Matrox Compile Error

[James Simmons]

>  > Strange that CONFIG_VT would get set to no. Another huge issue is that 
>  > people are configuring several framebuffer drivers to run the same piece 
>  > of hardware. 
> 
> A number of people seem to be seeing regressions with vesafb too.
> Configs that worked with 2.4 give a blank screen, and lock up under 2.5
> I believe vga=791 was one such option.

They are forgetting to set CONFIG_FRAMEBUFFER_CONSOLE.

P.S
   I have had VESA compiled without framebuffer console but with mdacon 
instead. If they would log in a do a cat /dev/urandom > /dev/fb0 they 
would see that the VESA fbdev driver is functional.