Matrox FB problem in latest 2.4.21-rc1-BK
Hello,
I just compiled 2.4.21-rc1 + bk cset-1.1137, and now the Matrox framebuffer always starts in 640x480 mode, whatever the mode I tell it. Moreover, fbset returns "ioctl: FBIOPUT_VSCREENINFO: invalid argument". This is on a G400, and still works correctly on 2.4.21-rc1, so the problem really is within the latest BK changes. I don't understand, since this cset doesn't contain matrox changes, and no FB changes except intel's !
This is on a dual Athlon-XP 1800, Asus A7M266-D, 512 MB RAM, G400 video card.
I will try to revert changes one by one, but by the time, here is my epurated .config (# lines removed). I append "video=matrox:vesa:0x107" to the cmdline.
Cheers,
Willy
CONFIG_X86=yCONFIG_UID16=yCONFIG_EXPERIMENTAL=yCONFIG_MODULES=yCONFIG_KMOD=yCONFIG_MK7=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_CMPXCHG=yCONFIG_X86_XADD=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_HAS_TSC=yCONFIG_X86_GOOD_APIC=yCONFIG_X86_USE_3DNOW=yCONFIG_X86_PGE=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_F00F_WORKS_OK=yCONFIG_X86_MCE=yCONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_NOHIGHMEM=yCONFIG_MTRR=yCONFIG_SMP=yCONFIG_X86_TSC=yCONFIG_HAVE_DEC_LOCK=yCONFIG_NET=yCONFIG_X86_IO_APIC=yCONFIG_X86_LOCAL_APIC=yCONFIG_PCI=yCONFIG_PCI_GOANY=yCONFIG_PCI_BIOS=yCONFIG_PCI_DIRECT=yCONFIG_ISA=yCONFIG_PCI_NAMES=yCONFIG_HOTPLUG=yCONFIG_SYSVIPC=yCONFIG_SYSCTL=yCONFIG_KCORE_ELF=yCONFIG_BINFMT_AOUT=mCONFIG_BINFMT_ELF=yCONFIG_PM=yCONFIG_APM=yCONFIG_APM_IGNORE_USER_SUSPEND=yCONFIG_APM_DO_ENABLE=yCONFIG_PARPORT=mCONFIG_PARPORT_PC=mCONFIG_PARPORT_PC_CML1=mCONFIG_PARPORT_PC_FIFO=yCONFIG_PARPORT_PC_SUPERIO=yCONFIG_PNP=yCONFIG_ISAPNP=yCONFIG_BLK_DEV_FD=yCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_NBD=mCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_SIZE=4096CONFIG_BLK_DEV_INITRD=yCONFIG_PACKET=yCONFIG_PACKET_MMAP=yCONFIG_NETLINK_DEV=yCONFIG_NETFILTER=yCONFIG_FILTER=yCONFIG_UNIX=yCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_FWMARK=yCONFIG_IP_ROUTE_NAT=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_TOS=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_ROUTE_LARGE_TABLES=yCONFIG_NET_IPIP=mCONFIG_NET_IPGRE=mCONFIG_INET_ECN=yCONFIG_IP_NF_CONNTRACK=mCONFIG_IP_NF_FTP=mCONFIG_IP_NF_AMANDA=mCONFIG_IP_NF_TFTP=mCONFIG_IP_NF_IRC=mCONFIG_IP_NF_QUEUE=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_MATCH_LIMIT=yCONFIG_IP_NF_MATCH_MAC=yCONFIG_IP_NF_MATCH_PKTTYPE=yCONFIG_IP_NF_MATCH_MARK=yCONFIG_IP_NF_MATCH_MULTIPORT=yCONFIG_IP_NF_MATCH_TOS=yCONFIG_IP_NF_MATCH_ECN=yCONFIG_IP_NF_MATCH_DSCP=yCONFIG_IP_NF_MATCH_AH_ESP=yCONFIG_IP_NF_MATCH_LENGTH=yCONFIG_IP_NF_MATCH_TTL=yCONFIG_IP_NF_MATCH_TCPMSS=yCONFIG_IP_NF_MATCH_HELPER=mCONFIG_IP_NF_MATCH_STATE=mCONFIG_IP_NF_MATCH_CONNTRACK=mCONFIG_IP_NF_MATCH_UNCLEAN=mCONFIG_IP_NF_MATCH_OWNER=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_MIRROR=yCONFIG_IP_NF_NAT=mCONFIG_IP_NF_NAT_NEEDED=yCONFIG_IP_NF_TARGET_MASQUERADE=mCONFIG_IP_NF_TARGET_REDIRECT=mCONFIG_IP_NF_NAT_AMANDA=mCONFIG_IP_NF_NAT_LOCAL=yCONFIG_IP_NF_NAT_SNMP_BASIC=mCONFIG_IP_NF_NAT_IRC=mCONFIG_IP_NF_NAT_FTP=mCONFIG_IP_NF_NAT_TFTP=mCONFIG_IP_NF_MANGLE=yCONFIG_IP_NF_TARGET_TOS=yCONFIG_IP_NF_TARGET_ECN=yCONFIG_IP_NF_TARGET_DSCP=yCONFIG_IP_NF_TARGET_MARK=yCONFIG_IP_NF_TARGET_LOG=yCONFIG_IP_NF_TARGET_ULOG=mCONFIG_IP_NF_TARGET_TCPMSS=yCONFIG_IP_NF_ARPTABLES=mCONFIG_IP_NF_ARPFILTER=mCONFIG_VLAN_8021Q=yCONFIG_BRIDGE=mCONFIG_NET_SCHED=yCONFIG_NET_SCH_CBQ=mCONFIG_NET_SCH_HTB=mCONFIG_NET_SCH_CSZ=mCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=mCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=mCONFIG_NET_SCH_INGRESS=mCONFIG_NET_QOS=yCONFIG_NET_ESTIMATOR=yCONFIG_NET_CLS=yCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_ROUTE=yCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=mCONFIG_NET_CLS_RSVP=mCONFIG_NET_CLS_RSVP6=mCONFIG_NET_CLS_POLICE=yCONFIG_NET_PKTGEN=mCONFIG_IDE=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_BLK_DEV_IDECD=yCONFIG_BLK_DEV_IDESCSI=yCONFIG_BLK_DEV_IDEPCI=yCONFIG_BLK_DEV_GENERIC=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_BLK_DEV_AMD74XX=yCONFIG_BLK_DEV_VIA82CXXX=yCONFIG_IDEDMA_AUTO=yCONFIG_BLK_DEV_IDE_MODES=yCONFIG_SCSI=yCONFIG_BLK_DEV_SD=yCONFIG_SD_EXTRA_DEVS=40CONFIG_CHR_DEV_ST=yCONFIG_BLK_DEV_SR=yCONFIG_SR_EXTRA_DEVS=2CONFIG_CHR_DEV_SG=yCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_AIC7XXX=yCONFIG_AIC7XXX_CMDS_PER_DEVICE=253CONFIG_AIC7XXX_RESET_DELAY_MS=5000CONFIG_AIC7XXX_DEBUG_MASK=0CONFIG_AIC7XXX_REG_PRETTY_PRINT=yCONFIG_NETDEVICES=yCONFIG_DUMMY=mCONFIG_BONDING=mCONFIG_TUN=mCONFIG_ETHERTAP=mCONFIG_NET_ETHERNET=yCONFIG_HAPPYMEAL=mCONFIG_NET_VENDOR_3COM=yCONFIG_VORTEX=mCONFIG_NET_PCI=yCONFIG_PCNET32=mCONFIG_ADAPTEC_STARFIRE=mCONFIG_TULIP=mCONFIG_TULIP_MWI=yCONFIG_TULIP_MMIO=yCONFIG_DE4X5=mCONFIG_EEPRO100=mCONFIG_E100=mCONFIG_NE2K_PCI=mCONFIG_8139TOO=mCONFIG_SIS900=mCONFIG_SUNDANCE=mCONFIG_TC35815=mCONFIG_VIA_RHINE=mCONFIG_ACENIC=mCONFIG_DL2K=mCONFIG_E1000=mCONFIG_TIGON3=mCONFIG_INPUT=mCONFIG_INPUT_KEYBDEV=mCONFIG_INPUT_MOUSEDEV=mCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_EVDEV=mCONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_SERIAL=yCONFIG_SERIAL_CONSOLE=yCONFIG_UNIX98_PTYS=yCONFIG_UNIX98_PTY_COUNT=256CONFIG_PRINTER=mCONFIG_LP_CONSOLE=yCONFIG_PPDEV=mCONFIG_I2C=yCONFIG_I2C_ALGOBIT=mCONFIG_I2C_CHARDEV=yCONFIG_I2C_PROC=yCONFIG_MOUSE=yCONFIG_PSMOUSE=yCONFIG_IPMI_HANDLER=mCONFIG_WATCHDOG=yCONFIG_I810_TCO=mCONFIG_SOFT_WATCHDOG=mCONFIG_AMD7XX_TCO=mCONFIG_AMD_RNG=mCONFIG_INTEL_RNG=mCONFIG_AMD_PM768=mCONFIG_NVRAM=yCONFIG_RTC=yCONFIG_AGP=yCONFIG_AGP_AMD=yCONFIG_DRM=yCONFIG_DRM_NEW=yCONFIG_DRM_MGA=mCONFIG_VIDEO_DEV=yCONFIG_VIDEO_PROC_FS=yCONFIG_I2C_PARPORT=mCONFIG_REISERFS_FS=yCONFIG_EXT3_FS=yCONFIG_JBD=yCONFIG_FAT_FS=yCONFIG_MSDOS_FS=mCONFIG_VFAT_FS=yCONFIG_CRAMFS=yCONFIG_TMPFS=yCONFIG_RAMFS=yCONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_ZISOFS=yCONFIG_JFS_FS=mCONFIG_MINIX_FS=yCONFIG_PROC_FS=yCONFIG_DEVPTS_FS=yCONFIG_ROMFS_FS=mCONFIG_EXT2_FS=yCONFIG_UDF_FS=mCONFIG_UFS_FS=yCONFIG_NFS_FS=yCONFIG_NFS_V3=yCONFIG_NFSD=yCONFIG_NFSD_V3=yCONFIG_SUNRPC=yCONFIG_LOCKD=yCONFIG_LOCKD_V4=yCONFIG_ZISOFS_FS=yCONFIG_PARTITION_ADVANCED=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_SUN_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"CONFIG_NLS_CODEPAGE_437=yCONFIG_NLS_CODEPAGE_850=yCONFIG_NLS_ISO8859_1=yCONFIG_VGA_CONSOLE=yCONFIG_VIDEO_SELECT=yCONFIG_FB=yCONFIG_DUMMY_CONSOLE=yCONFIG_VIDEO_SELECT=yCONFIG_FB_MATROX=yCONFIG_FB_MATROX_G450=yCONFIG_FB_MATROX_G100=yCONFIG_FB_MATROX_I2C=mCONFIG_FB_MATROX_MAVEN=mCONFIG_FB_MATROX_PROC=mCONFIG_FBCON_CFB8=yCONFIG_FBCON_CFB16=yCONFIG_FBCON_CFB24=yCONFIG_FBCON_CFB32=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=yCONFIG_SOUND=mCONFIG_SOUND_CMPCI=mCONFIG_SOUND_CMPCI_CM8738=yCONFIG_SOUND_CMPCI_SPEAKERS=2CONFIG_SOUND_EMU10K1=mCONFIG_MIDI_EMU10K1=yCONFIG_SOUND_ICH=mCONFIG_USB=mCONFIG_USB_DEVICEFS=yCONFIG_USB_EHCI_HCD=mCONFIG_USB_OHCI=mCONFIG_USB_AUDIO=mCONFIG_USB_STORAGE=mCONFIG_USB_HID=mCONFIG_USB_HIDINPUT=yCONFIG_USB_HIDDEV=yCONFIG_USB_KBD=mCONFIG_USB_MOUSE=mCONFIG_USB_PWC=mCONFIG_DEBUG_KERNEL=yCONFIG_MAGIC_SYSRQ=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=m
PATCH 1/1 [2.4] was: Matrox FB problem in latest 2.4.21-rc1-BK
Hi again,
OK I found it to be a typo in cset-1.1134 (intel fb fixes) which disabled CFB8. It now works with this patch. Christoph, you might also have the typo in your tree.
Cheers,
Willy
drivers/video/Config.in +1 -1
@@ -299,7 +299,7 @@ "$CONFIG_FB_PMAG_BA" = "y" -o "$CONFIG_FB_PMAGB_B" = "y" -o \ "$CONFIG_FB_MAXINE" = "y" -o "$CONFIG_FB_TX3912" = "y" -o \ "$CONFIG_FB_SIS" = "y" -o "$CONFIG_FB_NEOMAGIC" = "y" -o \ - "$CONFIG_FB_STI" = "y" -o "$CONFIG_FB_HP300" = "y" -o + "$CONFIG_FB_STI" = "y" -o "$CONFIG_FB_HP300" = "y" -o \ "$CONFIG_FB_INTEL" = "y" ]; then define_tristate CONFIG_FBCON_CFB8 y else
Quoted 13 lines · Willy TARREAU
Hello,
I just compiled 2.4.21-rc1 + bk cset-1.1137, and now the Matrox framebuffer always starts in 640x480 mode, whatever the mode I tell it. Moreover, fbset returns "ioctl:
FBIOPUT_VSCREENINFO: invalid argument". This is on a G400, and still works correctly on 2.4.21-rc1, so the problem really is within the latest BK changes. I don't understand, since this cset doesn't contain matrox changes, and no FB changes except intel's !This is on a dual Athlon-XP 1800, Asus A7M266-D, 512 MB RAM, G400 video card.
I will try to revert changes one by one, but by the time, here is my epurated .config (# lines removed). I append "video=matrox:vesa:0x107" to the cmdline.
Re: [PATCH][2.4] was: Matrox FB problem in latest 2.4.21-rc1-BK
Quoted 5 lines · Willy TARREAU
Hi again,
OK I found it to be a typo in cset-1.1134 (intel fb fixes) which disabled CFB8. It now works with this patch. Christoph, you might also have the typo in your tree.
The patch below fixes another place in the same file:
I'm not sure whether the new "y"-o (no space) gets correctly parsed by all config tools, but the "$CONFIG_FB_STI" = "y" (not introduced by the recent patch) seems to be definitely wrong.
Quoted 3 lines
Cheers,
Willy
...
cu
Adrian
drivers/video/Config.in renamed from drivers/video/Config.in.old +2 -2
@@ -299,7 +299,7 @@ "$CONFIG_FB_PMAG_BA" = "y" -o "$CONFIG_FB_PMAGB_B" = "y" -o \ "$CONFIG_FB_MAXINE" = "y" -o "$CONFIG_FB_TX3912" = "y" -o \ "$CONFIG_FB_SIS" = "y" -o "$CONFIG_FB_NEOMAGIC" = "y" -o \ - "$CONFIG_FB_STI" = "y" -o "$CONFIG_FB_HP300" = "y" -o + "$CONFIG_FB_STI" = "y" -o "$CONFIG_FB_HP300" = "y" -o \ "$CONFIG_FB_INTEL" = "y" ]; then define_tristate CONFIG_FBCON_CFB8 y else
@@ -402,7 +402,7 @@ "$CONFIG_FB_3DFX" = "m" -o "$CONFIG_FB_RADEON" = "m" -o \ "$CONFIG_FB_SGIVW" = "m" -o "$CONFIG_FB_SIS" = "m" -o \ "$CONFIG_FB_PVR2" = "m" -o "$CONFIG_FB_VOODOO1" = "m" -o \ - "$CONFIG_FB_CYBER2000" = "m" -o "$CONFIG_FB_STI" = "y"-o \ + "$CONFIG_FB_CYBER2000" = "m" -o "$CONFIG_FB_STI" = "m" -o \ "$CONFIG_FB_INTEL" = "m" ]; then define_tristate CONFIG_FBCON_CFB32 m fi
Re: [PATCH][2.4] was: Matrox FB problem in latest 2.4.21-rc1-BK
In reply to Willy TARREAUQuoted 5 lines · Willy TARREAU
Hi again,
OK I found it to be a typo in cset-1.1134 (intel fb fixes) which disabled CFB8. It now works with this patch. Christoph, you might also have the typo in your tree.
Yes, sorry for the typo.