Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
MGA driver update ... back to FBDev driver [unSolved]
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Mon Nov 19, 2012 5:50 pm    Post subject: MGA driver update ... back to FBDev driver [unSolved] Reply with quote

Hello,

I did a system update, which included Xorg.
But at restart, the MGA drivers won't load with the following message :

Quote:
[ 795.590] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
mgag200 SE A PCI, mgag200 SE B PCI, mgag200 EV Maxim,
mgag200 ER SH7757, mgag200 eW Nuvoton, mgag200eH, mgag400, mgag550
[ 795.590] (II) VESA: driver for VESA chipsets: vesa
[ 795.590] (II) FBDEV: driver for framebuffer: fbdev
[ 795.590] (++) using VT number 7

[ 795.596] (EE) mga: The PCI device 0x525 at 01@00:00:0 has a kernel module claiming it.
[ 795.596] (EE) mga: This driver cannot operate until it has been unloaded.
[ 795.596] (EE) mga: The PCI device 0x525 at 01@00:00:0 has a kernel module claiming it.
[ 795.596] (EE) mga: This driver cannot operate until it has been unloaded.
[ 795.597] vesa: Ignoring device with a bound kernel driver


I searched a bit, and found this link (but I duno if it is totally revelent).

My kernel's config is the following :
Code:
laurent@chose ~ $ zcat /proc/config.gz | grep '=[ym]'
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_ARCH_HAS_CPU_AUTOPROBE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_X86_32_LAZY_GS=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
CONFIG_HAVE_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_KTIME_SCALAR=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_TINY_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_NAMESPACES=y
CONFIG_RELAY=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_UID16=y
CONFIG_KALLSYMS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_EVENTS=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
CONFIG_SLUB=y
CONFIG_PROFILING=y
CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
CONFIG_KPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y
CONFIG_HAVE_CMPXCHG_LOCAL=y
CONFIG_HAVE_CMPXCHG_DOUBLE=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_BLOCK=y
CONFIG_LBDAF=y
CONFIG_BLK_DEV_BSG=y
CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_CFQ=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_ZONE_DMA=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_NO_BOOTMEM=y
CONFIG_MK7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_TRANSMETA_32=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
CONFIG_VM86=y
CONFIG_MICROCODE=y
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_HIGHMEM4G=y
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_HAVE_MEMBLOCK_NODE_MAP=y
CONFIG_ARCH_DISCARD_MEMBLOCK=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_NEED_PER_CPU_KM=y
CONFIG_MTRR=y
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_ARCH_RANDOM=y
CONFIG_SECCOMP=y
CONFIG_HZ_1000=y
CONFIG_SCHED_HRTICK=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_PM_RUNTIME=y
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_X86_PM_TIMER=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_PCIEASPM=y
CONFIG_PCIEASPM_DEFAULT=y
CONFIG_PCIE_PME=y
CONFIG_PCI_IOAPIC=y
CONFIG_PCI_LABEL=y
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
CONFIG_BINFMT_ELF=y
CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_HAVE_AOUT=y
CONFIG_BINFMT_MISC=y
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_LRO=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_CUBIC=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_FTP=y
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CT_NETLINK=y
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_STATE=y
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
CONFIG_NF_NAT_SIP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_DNS_RESOLVER=y
CONFIG_BQL=y
CONFIG_FIB_RULES=y
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_DMA_SHARED_BUFFER=y
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PNP=y
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_HAVE_IDE=y
CONFIG_SCSI_MOD=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_WAIT_SCAN=m
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_ATA=y
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
CONFIG_ATA_SFF=y
CONFIG_ATA_BMDMA=y
CONFIG_PATA_VIA=y
CONFIG_ATA_GENERIC=y
CONFIG_MD=y
CONFIG_FIREWIRE=y
CONFIG_FIREWIRE_OHCI=y
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
CONFIG_MII=y
CONFIG_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
CONFIG_NET_VENDOR_INTEL=y
CONFIG_E100=y
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_POLLDEV=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=y
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_WACOM=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y
CONFIG_GAMEPORT=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_KCOPY=m
CONFIG_DEVKMEM=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_PRINTER=m
CONFIG_PPDEV=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_NVRAM=y
CONFIG_HPET=y
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=m
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_PARPORT=m
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_POWER_SUPPLY=y
CONFIG_HWMON=y
CONFIG_SENSORS_VIA686A=m
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_WATCHDOG=y
CONFIG_SSB_POSSIBLE=y
CONFIG_BCMA_POSSIBLE=y
CONFIG_MFD_CORE=y
CONFIG_LPC_SCH=y
CONFIG_AGP=y
CONFIG_AGP_VIA=y
CONFIG_VGA_ARB=y
CONFIG_DRM=y
CONFIG_DRM_MGA=y
CONFIG_VIDEO_OUTPUT_CONTROL=y
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=y
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_VESA=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=m
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_HRTIMER=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=y
CONFIG_SND_MPU401_UART=y
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_DRIVERS=y
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_PCI=y
CONFIG_SND_INTEL8X0=y
CONFIG_SND_VIA82XX=y
CONFIG_AC97_BUS=y
CONFIG_HID=y
CONFIG_HIDRAW=y
CONFIG_HID_GENERIC=y
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_EZKEY=y
CONFIG_HID_KYE=y
CONFIG_HID_GYRATION=y
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LOGITECH=y
CONFIG_LOGITECH_FF=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_NTRIG=y
CONFIG_HID_PANTHERLORD=y
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
CONFIG_HID_TOPSEED=y
CONFIG_USB_HID=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_ARCH_HAS_XHCI=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
CONFIG_USB_SUSPEND=y
CONFIG_USB_MON=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_LIBUSUAL=y
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
CONFIG_EDAC=y
CONFIG_EDAC_DECODE_MCE=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_CMOS=y
CONFIG_CLKSRC_I8253=y
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_DMIID=y
CONFIG_DCACHE_WORD_ACCESS=y
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_JBD=y
CONFIG_JBD2=y
CONFIG_FS_MBCACHE=y
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_AUTOFS4_FS=y
CONFIG_FUSE_FS=y
CONFIG_CUSE=y
CONFIG_GENERIC_ACL=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_MISC_FILESYSTEMS=y
CONFIG_UFS_FS=y
CONFIG_UFS_FS_WRITE=y
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_UTF8=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_HAVE_ARCH_KMEMCHECK=y
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_DOUBLEFAULT=y
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_0X80=y
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_AUTHENC=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_586=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_HW=y
CONFIG_HAVE_KVM=y
CONFIG_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_IO=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
CONFIG_CRC32_SLICEBY8=y
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_XZ_DEC=m
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_DQL=y
CONFIG_NLATTR=y


Any idea to solve this nasty situation ?

Thanks

Laurent


Last edited by destroyedlolo on Mon Nov 19, 2012 11:11 pm; edited 2 times in total
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Mon Nov 19, 2012 7:59 pm    Post subject: Reply with quote

I don't have a Matrox, but perhaps the new driver is now i.e. KMS-only.
If it were that way, then it may likely be the same case as ati/intel - CONFIG_FB_VESA and CONFIG_FB_MATROX* must in such case be off.

Though more info about your xorg.conf would be useful.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Mon Nov 19, 2012 8:30 pm    Post subject: Reply with quote

Hum, I think there is an HUGE problem with the new version of XOrg, because I updated as well my t40 (lspci said "VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV200 [Mobility Radeon 7500]") and I got a 256 colors screen :(

This time, no problem to load the driver, but Xorg.log contains :
Code:

[    36.912] (II) LoadModule: "modesetting"
[    36.999] (WW) Warning, couldn't open module modesetting
[    36.999] (II) UnloadModule: "modesetting"
[    36.999] (II) Unloading modesetting
[    36.999] (EE) Failed to load module "modesetting" (module does not exist, 0)


... I need to find a way to compile it as well.


On the MGA machine, I don't have configuration at all, but
Code:
Section "InputClass"
        Identifier "keyboard-all"
        Driver "evdev"
        Option "XkbLayout" "us"
        Option "XkbRules" "xorg"
        Option "XkbOptions" "compose:rwin,terminate:ctrl_alt_bksp"
        MatchIsKeyboard "on"
EndSection
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Mon Nov 19, 2012 9:15 pm    Post subject: Reply with quote

The most recent xf86-video-ati definitely is KMS-only.

As for Matrox - enough already, pastebin whole log.
Post 'emerge -1pv libdrm mesa' too.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Mon Nov 19, 2012 9:59 pm    Post subject: Reply with quote

VoidMage wrote:
The most recent xf86-video-ati definitely is KMS-only.

Thanks a lot, my T40 is back with a decent video :)

Back to the MGA now ...
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Mon Nov 19, 2012 10:52 pm    Post subject: Reply with quote

You got it as well, thanks :)

VoidMage wrote:
I don't have a Matrox, but perhaps the new driver is now i.e. KMS-only.


Matrox is not using KMS ...

VoidMage wrote:
If it were that way, then it may likely be the same case as ati/intel - CONFIG_FB_VESA and CONFIG_FB_MATROX* must in such case be off.


But Matrox' kernel framebuffer has to be disabled.
VESA doesn't matter.

Thanks again.

Bye

Laurent
Back to top
View user's profile Send private message
chithanh
Developer
Developer


Joined: 05 Aug 2006
Posts: 2158
Location: Berlin, Germany

PostPosted: Mon Nov 19, 2012 11:00 pm    Post subject: Reply with quote

To find out which driver is currently hogging your graphics card, run "lspci -k"
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Mon Nov 19, 2012 11:16 pm    Post subject: Reply with quote

In fact, the problem is not fully solved as I lot the graphical acceleration :cry:

I can see following error in Xorg.log that I didn't had before :
Code:
[    32.947] (EE) AIGLX error: dlopen of /usr/lib/dri/mga_dri.so failed (/usr/lib/dri/mga_dri.so: cannot open shared object file: No such file or directory)
[    32.947] (EE) AIGLX: reverting to software rendering
[    34.529] (II) AIGLX: Loaded and initialized swrast
[    34.529] (II) GLX: Initialized DRISWRAST GL provider for screen 0


I duno if it impact 2D gfx as well, but clearly, I can't show video anymore.

How can I rebuild this .so ?
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Tue Nov 20, 2012 1:48 am    Post subject: Reply with quote

Chances are you can't - looking at the ebuilds, mga was still present in mesa 7.11.2, but not in 8.0.4 and IIRC, that code was dropped upstream.

Perhaps you should give KMS and xf86-video-modesetting driver a try ?
It's not - IIRC - hardware accelerated, but my personal experience on a quite outdated card (though one that did have a mesa hardware module) were that dropping the _FB_ module did lighten the load on the system quite a bit.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Tue Nov 20, 2012 9:15 am    Post subject: Reply with quote

VoidMage wrote:
Chances are you can't - looking at the ebuilds, mga was still present in mesa 7.11.2, but not in 8.0.4 and IIRC, that code was dropped upstream.

Arg, it's painfull : the advantage on Linux is we can run it on old hardware ...

VoidMage wrote:
Perhaps you should give KMS and xf86-video-modesetting driver a try ?
It's not - IIRC - hardware accelerated, but my personal experience on a quite outdated card (though one that did have a mesa hardware module) were that dropping the _FB_ module did lighten the load on the system quite a bit.


_FB_ are already disabled but I can't see any KMS for g400 :cry:

But, I can re-install mesa 7.11.2 and keep xorg-1.13 ? Or should I revert back to the previous version of Xorg ?
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Wed Nov 21, 2012 11:45 am    Post subject: Reply with quote

Hum, I'm lost in downgrade.

1- If I'm trying to downgrade only mesa, I got :
Code:
chose laurent # emerge -vp '=media-libs/mesa-7.11.2'receiving incremental file list
Packages
     1003748 100%    8.11MB/s    0:00:00 (xfer#1, to-check=0/1)

sent 55 bytes  received 1003971 bytes  2008052.00 bytes/sec
total size is 1003748  speedup is 1.00

These are the packages that would be merged, in order:

Calculating dependencies... done!
[binary     UD ] media-libs/mesa-7.11.2 [9.0] USE="classic egl gallium llvm nptl shared-glapi -bindist -debug -gbm -gles% -motif% -openvg -osmesa -pax_kernel -pic (-selinux) -shared-dricore% (-g3dvl%) (-gles1%) (-gles2%) (-r600-llvm-compiler%) (-vdpau%) (-wayland%) (-xa%) (-xorg%) (-xvmc%)" VIDEO_CARDS="intel mga%* r128%* radeon sis%* -mach64% -nouveau -savage% -tdfx% -via% -vmware (-i915%) (-i965%) (-r100%) (-r200%) (-r300%) (-r600%) (-radeonsi%)" 0 kB
[uninstall     ] media-libs/glu-9.0.0  USE="(-multilib) -static-libs"
[blocks b      ] <media-libs/mesa-9 ("<media-libs/mesa-9" is blocking media-libs/glu-9.0.0)
[blocks B      ] <media-libs/mesa-8.0.3-r1 ("<media-libs/mesa-8.0.3-r1" is blocking app-admin/eselect-opengl-1.2.6.1)

Total: 1 package (1 downgrade, 1 binary, 1 uninstall), Size of downloads: 0 kB
Conflict: 2 blocks (1 unsatisfied)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (app-admin/eselect-opengl-1.2.6.1::gentoo, installed) pulled in by
    >=app-admin/eselect-opengl-1.2.6 required by (x11-proto/glproto-1.4.16::gentoo, installed)
    >=app-admin/eselect-opengl-1.0.8 required by (x11-base/xorg-server-1.13.0-r1::gentoo, installed)
    app-admin/eselect-opengl required by (media-libs/mesa-7.11.2::gentoo, binary scheduled for merge)

  (media-libs/mesa-7.11.2::gentoo, binary scheduled for merge) pulled in by
    >=media-libs/mesa-7.8_rc[nptl] required by (x11-base/xorg-server-1.13.0-r1::gentoo, installed)
    <media-libs/mesa-9 required by (virtual/glu-9.0::gentoo, installed)
    =media-libs/mesa-7.11.2
    >=media-libs/mesa-7.10 required by (www-client/firefox-10.0.7::gentoo, installed)
    media-libs/mesa required by (virtual/opengl-7.0::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked


2- If I'm trying to download xorg server, no dependancy is rebuilt :
Code:
chose laurent # emerge -vp --binpkg-respect-use '=x11-base/xorg-server-1.12.4'receiving incremental file list
Packages
     1003748 100%    8.25MB/s    0:00:00 (xfer#1, to-check=0/1)

sent 55 bytes  received 1003971 bytes  2008052.00 bytes/sec
total size is 1003748  speedup is 1.00

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     UD ] x11-base/xorg-server-1.12.4 [1.13.0-r1] USE="nptl udev xnest xorg -dmx -doc -ipv6 -kdrive -minimal (-selinux) -static-libs -tslib -xvfb" 5,318 kB

Total: 1 package (1 downgrade), Size of downloads: 5,318 kB


So I'm fearing destroying my system doing that ...
Which is the safest way ?
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

PostPosted: Wed Nov 21, 2012 12:39 pm    Post subject: Reply with quote

This is one area where binary distros have an advanatge. Arch packages mesa 9.0, but they also package DRI1 drivers compiled from mesa 7.11 source and they work together fine like that. That's because the libgl interface is stable, so a 7.11 driver can talk to a libgl from 9.0.

Though I suppose something similar could be done in Gentoo: An ebuild that installs mesa 9.0, but no drivers. And then another ebuild that builds mesa 7.11, but only installs specified drivers from that.

No need to mess with X, that's a separate thing from mesa.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Wed Nov 21, 2012 1:01 pm    Post subject: Reply with quote

HI Gusar,

So it means I can cheat the system ?
I mean :
  • compile mesa 7.11 (the problem for me will be do know how to tell emerge to ignore blocking)
  • Archive drivers
  • compile and install latest mesa 9.0
  • install drivers as mesa is looking for them
  • pray that mesa API will not change
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Wed Nov 21, 2012 5:20 pm    Post subject: Reply with quote

That part about binary distros might not be quite correct - see this page.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Wed Nov 21, 2012 5:39 pm    Post subject: Reply with quote

Hum, how can I ensure that llvmpipe driver is loaded on my system ?

My second remark is about the sentence "To be clear, this removes only the DRI1 3D support for older chipsets. Native 2D drivers will still be provided for the affected hardware" : I guess it is concerning Gentoo as well but in this case, why windows manipulation feel soooo slow after this update ?

I mean, I don't have Compiz or another other 3D effect on my desktop ... but clearly, moving a plain window is as slow as on my venerable Sun's Ultra60 which wasn't the case before. Is blitting part of 3D functions ?
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

PostPosted: Wed Nov 21, 2012 6:02 pm    Post subject: Reply with quote

VoidMage wrote:
That part about binary distros might not be quite correct - see this page.

Everyone who thinks llvmpipe is a valid replacement for a proper 3D driver (even a DRI1 one) is either clueless or delusional. For llvmpipe to work even sorta not completely slow as molasses, you need a multi-core CPU with modern instruction sets. A kind of CPU you will *not* find on machines with these old graphic cards that only have DRI1 drivers.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Wed Nov 21, 2012 6:30 pm    Post subject: Reply with quote

Gusar wrote:
VoidMage wrote:
That part about binary distros might not be quite correct - see this page.

Everyone who thinks llvmpipe is a valid replacement for a proper 3D driver (even a DRI1 one) is either clueless or delusional. For llvmpipe to work even sorta not completely slow as molasses, you need a multi-core CPU with modern instruction sets. A kind of CPU you will *not* find on machines with these old graphic cards that only have DRI1 drivers.

I didn't say it's a correct solution, only that not all distros solve it by picking the drivers from old mesa.
Then again, bitrot is the word - I kinda doubt getting such hardware is easy and the userbase is slowly dieing out.
I wonder how much work would it be to pull the code out of old mesa and - using the new build system as a template - pack those drivers into a separate package. Also, how long would it take for such package to get broken by upstream changes - libGL API might be stable, but dri1 is not quite the same thing; remember that in 1.13 xserver XAA got dropped.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Wed Nov 21, 2012 9:03 pm    Post subject: Reply with quote

Gusar wrote:
For llvmpipe to work even sorta not completely slow as molasses, you need a multi-core CPU with modern instruction sets. A kind of CPU you will *not* find on machines with these old graphic cards that only have DRI1 drivers.

But my question remains : is it needed for a desktop without 3D effect ?

VoidMage wrote:
I kinda doubt getting such hardware is easy and the userbase is slowly dieing out.

One of the main reason to choose Linux for joe average is it can bring back to life old / deprecated hardware that is not anymore supported by commercial OSes.
The big example is the i915 disaster : it's all but a good advertisement for Linux. "If I replace the nasty w2000 installed on my machine by Linux, am I ensured it will still work in 2 months".
It's a pity that upstream doesn't take it in account. Anyway, another story :)

Now, how can I revert back ?

PS: I duno if it's possible and how, it should be useful if portage can warn before such destructive upgrade. "caution, you're upgrading Xorg but I detected from your VIDEO_CARDS you will face problem with mga card ... :P
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

PostPosted: Wed Nov 21, 2012 9:25 pm    Post subject: Reply with quote

destroyedlolo wrote:
But my question remains : is it needed for a desktop without 3D effect ?

Nope.

destroyedlolo wrote:
Now, how can I revert back ?

It could be the easiest way is to compile mesa 7.11 manually, not with portage. You're only interested in one file anyway (mga_dri.so), which you then copy into /usr/lib/xorg/modules/dri/. Check the Arch PKGBUILD to see which configure flags to use.

destroyedlolo wrote:
PS: I duno if it's possible and how, it should be useful if portage can warn before such destructive upgrade. "caution, you're upgrading Xorg but I detected from your VIDEO_CARDS you will face problem with mga card ... :P

This has nothing to do with X, but with mesa. And there was a "warning" of sorts, though admittedly it was subtle - mesa no longer has VIDEO_CARDS="mga", something that showed up in "emerge -pu" when there was an update from 7.11 to 8
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Wed Nov 21, 2012 10:09 pm    Post subject: Reply with quote

Gusar wrote:
destroyedlolo wrote:
But my question remains : is it needed for a desktop without 3D effect ?

Nope.


So it means something else changed and remove hardware 2d accelerations :(
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

PostPosted: Wed Nov 21, 2012 10:21 pm    Post subject: Reply with quote

destroyedlolo wrote:
So it means something else changed and remove hardware 2d accelerations :(

Yeah, XAA is gone. But the driver should fall back to ShadowFB, which is pretty much the same (XAA hasn't been accelerating anything for years). You could also try activating EXA:
Code:
Section "Device"
  Identifier "Matrox Card"
  Driver "mga"
  Option "AccelMethod" "EXA"
EndSection

If that won't work well, try explicitly enabling ShadowFB:
Code:
Section "Device"
  Identifier "Matrox Card"
  Driver "mga"
  Option "ShadowFB" "true"
EndSection
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Wed Nov 21, 2012 10:38 pm    Post subject: Reply with quote

Gusar wrote:

Yeah, XAA is gone.


Yes, it's what I just found :


I'm trying EXA ...
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Thu Nov 22, 2012 12:55 am    Post subject: Reply with quote

So,

  • EXA creates an imeditate kernel panic :(
  • ShadowFB improved a bit windows movements ... but performances are too poor to allow video playing.


So the only solution I see it to revert back to x11-base/xorg-server-1.12.4 (or probably 1.11.4-r1) and mask all subsequent versions.

Bye
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

PostPosted: Thu Nov 22, 2012 8:49 am    Post subject: Reply with quote

destroyedlolo wrote:
[*]ShadowFB improved a bit windows movements ... but performances are too poor to allow video playing.

Video playing where? Mplayer, and other standalone players, should be able to use the video overlay, just configure them to use Xv. Install xvinfo, show us it's output.

If you're talking about flash... well, it's flash. Though even there, I don't have a problem on my SiS card which also requires the use of ShadowFB. For fullscreen scaling, flash can use opengl, so did you compile mga_dri.so yet? Hmm, though I'm not sure opengl works with ShadowFB. Damn, I wish I had a Matrox card, so I could play with this stuff...
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)

PostPosted: Thu Nov 22, 2012 12:58 pm    Post subject: Reply with quote

Gusar wrote:
Video playing where? Mplayer, and other standalone players, should be able to use the video overlay, just configure them to use Xv. Install xvinfo, show us it's output.

It's VLC and it is compiled with xv support :
Code:
[ebuild   R    ] media-video/vlc-2.0.3  USE="X a52 aac alsa avahi avcodec avformat cdda dbus dvbpsi dvd encode ffmpeg flac fontconfig gcrypt gnome httpd libcaca libnotify live lua matroska mmx mp3 mpeg ncurses ogg optimisememory png postproc qt4 sdl skins speex sqlite svg swscale theora truetype udev upnp v4l vlm vorbis win32codecs wma-fixed x264 xcb xml xosd xv -aalib (-altivec) -atmo (-audioqueue) -bidi -bluray -cddb -dc1394 -debug -dirac (-direct2d) -directfb (-directx) (-dshow) -dts -dvb (-dxva2) -egl -fbosd -fluidsynth -gme -gnutls -growl -ieee1394 (-ios-vout) -jack -kate -kde -libass -libproxy -libsamplerate -libtar -libtiger -linsys -lirc (-macosx) (-macosx-audio) (-macosx-dialog-provider) (-macosx-eyetv) (-macosx-qtkit) (-macosx-quartztext) (-macosx-vout) (-media-library) -modplug -mtp -musepack (-neon) -omxil -opengl -oss -portaudio -projectm -pulseaudio -pvr -rtsp -run-as-root -samba -schroedinger -sdl-image -shine -shout -sid -sse -switcher -taglib -twolame -vaapi -vcdx (-waveout) (-wingdi) -zvbi" 0 kB


xvinfo doesn't provide an optimistic output :(
Code:
chose laurent # xvinfo
X-Video Extension version 2.2
screen #0
 no adaptors present


Gusar wrote:
If you're talking about flash... well, it's flash. Though even there, I don't have a problem on my SiS card which also requires the use of ShadowFB. For fullscreen scaling, flash can use opengl, so did you compile mga_dri.so yet?

But my problem is not with flash, it's even with local avi or mkv.

[quote="Gusar"]Hmm, though I'm not sure opengl works with ShadowFB. Damn, I wish I had a Matrox card, so I could play with this stuff...
:D
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum