http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrmazda@earthlink | |.net) --- Comment #1 from Stefan Dirsch --- Isn't the issue here, that Xorg is no longer run with root privileges? I'm afraid vga boot param is no longer been used since every driver switched to KMS. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c3 --- Comment #3 from Egbert Eich --- vga= is not supported by grub2 any more. AFAIR, Felix is using a grub1 setup and starts the Xserver using 'startx' (probably as a regular user) with some scripts on top. startx really isn't supported any more either - which doesn't mean it won't work, however one needs to know very well what needs to be done to make it work. Felix: Does it work when you do the same as 'root'? This may be due newer kernels not allowing to share iomem between drivers - see: bsc#971907 Or it may be due to PCI ROM not being made accessible. See the pci=.. command line option. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c5 --- Comment #5 from Felix Miata --- Created attachment 697274 --> http://bugzilla.opensuse.org/attachment.cgi?id=697274&action=edit dmesg after startx exited normally; without vga= on host a-865 cmdline; booted to multi-user.target -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c7 --- Comment #7 from Felix Miata --- Created attachment 697276 --> http://bugzilla.opensuse.org/attachment.cgi?id=697276&action=edit dmesg after KDM3 greeter appears; without vga= on host a-865 cmdline; booted to graphical.target -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c9 --- Comment #9 from Stefan Dirsch --- Max, this is still Matrox G550. There is no KMS support available for this old GPU. IIRC Egbert only worked on KMS support for old (non-server) G200 chipsets. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c11 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #11 from Max Staudt --- I placed a Matrox Mystique in a test box and started Tumbleweed. I've been able to observe several things: 1. The mga kernel module isn't loaded by default. -> No idea why. -> No 3D acceleration, which wouldn't work anyway since Mesa has long dropped Matrox support. 2. Even without mga, X comes up with its own MGA 2D driver when run as root. -> So you may or may not need the mga module if X can access system memory as root. It does reference firmware files when checked with 'modinfo mga', so I don't know. 3. But only if vesafb isn't loaded. -> Thus, vga= must not be used to set a graphical mode. Given that the X server now runs as a regular user in Tumbleweed, I see no real solution for you, other than a hack such as setting the X server setuid root :( Debugging the mga kernel module failing to load automatically also seems pointless, given that modesetting is apparently done via direct memory access and that there is no user of the DRI1 infrastructure left (Mesa dropped the 3D support for Matrox several years ago). If you're so inclined, you can try to port the modesetting code for your card from the X driver to the new mgag200 kernel module (which was actually meant for the new G200-like chips found in server chipsets). I haven't looked into the code, so I don't know whether this is feasible. Egbert Eich has done this for the classic G200 chips. See: http://kernel.opensuse.org/cgit/kernel-source/tree/patches.drivers/drm-mgag2... If you do this, please let me know. As a former Matrox user myself, I would be very glad to see these cards supported with KMS. As for solving the problem at hand, I suggest setting a video mode in GRUB and making sure it's passed on to Linux when booting (see GRUB's gfxmode and gfxpayload settings). If your card's VESA BIOS supports your screen's native resolution, Linux will pass the setting to vesafb and you can use X with its fbdev driver. Make sure to uninstall xf86-video-mga, which is installed automatically if a Matrox card is found. Feedback as to what you've tried and whether you found a solution that works for you would be great! Maybe we'll have to kick xf86-video-mga from the default installation. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c13 --- Comment #13 from Felix Miata --- Created attachment 716675 --> http://bugzilla.opensuse.org/attachment.cgi?id=716675&action=edit oops from journalctl I discovered what follows as a consequence of investigating a mailing list thread with the closest video hardware match I could come up with (list user has Radeon 9250): "42,2 installed -> black display" https://lists.opensuse.org/opensuse/2017-03/msg00163.html # grep RETT /etc/*lease PRETTY_NAME="openSUSE Tumbleweed" # uname -a Linux a-865 4.9.11-1-default #1 SMP Sat Feb 18 17:59:27 UTC 2017 (cf9c670) i686 i686 i386 GNU/Linux # inxi -c0 -G Graphics: Card: Advanced Micro Devices [AMD/ATI] RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] Display Server: X.org 1.18.4 drivers: ati,vesa (unloaded: modesetting,fbdev,radeon) tty size: 111x36 Advanced Data: N/A for root # lspci -xxk | grep -A2 VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] (rev 01) Subsystem: Device 0082:0515 Kernel modules: radeon With this rv250 AGP card I replaced the comment 0 Matrox 550 card with because of this bug. Could this have nothing to do directly or even at all with Matrox? With the rv250 I must also remove vga= from cmdline to avoid black screen, leaving the framebuffer ttys running in 80x25 mode, and no /dev/fb* devices. (startx won't start Xorg either: "(EE) systemd-logind: failed to take device /dev/dri/card0: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." Trying locks up console I/O entirely, requiring remote login or reset button to proceed. Trying to boot directly to graphical.target fails to reach login manager KDM3: [ 43.128] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 43.129] (II) xfree86: Adding drm device (/dev/dri/card0)) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c15 --- Comment #15 from Felix Miata --- Created attachment 716701 --> http://bugzilla.opensuse.org/attachment.cgi?id=716701&action=edit systemd-analyze blame from failed attempt to boot directly to KDM3 I put the comment 0 Matrox 550 in a PC running TW that still has Linux kt400 4.4.0-2-default #1 SMP Thu Jan 21 07:47:10 UTC 2016 (b56b151) i686 athlon i386 GNU/Linux installed. I updated all except kernel to TW20170305. Xorg 1.19.1 starts to start with vga=791 included, but this is the Xorg.0.log tail: # tail Xorg.0.log [ 111.771] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard [ 111.771] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0" [ 111.771] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9) [ 111.771] (**) Option "xkb_rules" "evdev" [ 111.771] (**) Option "xkb_layout" "us" [ 111.773] (II) config/udev: Adding input device PC Speaker (/dev/input/event3) [ 111.773] (II) No input driver specified, ignoring this device. [ 111.773] (II) This device may have been added with another device file. [ 111.790] (EE) [ 111.790] (EE) Backtrace: Tail of journalctl -b: Mar 07 22:53:03 kt400 systemd[1]: Started Process Core Dump (PID 1378/UID 0). Mar 07 22:53:06 kt400 systemd-coredump[1379]: Process 1369 (X) of user 0 dumped core. Startx/KDM3 with 4.4.0 kernel produce only a black screen without or without vga= on cmdline. Attached Xorg.0.log is from booting 4.4.0 *with* vga=791 on cmdline. I've saved systemd coredumps at this juncture on kernel 4.4.0, 4.5.0, 4.6.2 & 4.9.11 in TW20170305 in case they might prove of any use. With 4.4.0, the coredumps occurred whether or not vga=791 was on cmdline, and Xorg.0.logs looked similar. With 4.5.0 and newer kernels, coredumps were only generated if vga=791 was absent from cmdline, and Xorg.0.logs were very different, with vga=791 present only 6k in size and terminating with no screens have usable configuration, while without vga=791 they were approaching 38k in size and terminated as shown above with (EE) Backtrace:. This leads me to suspect this bug may have arisen in the window between 4.4.0 and 4.5.0. Without vga= on cmdline and with kernel-default-4.9.11, KDE3 via startx is again working as expected, though with no /dev/fb* and with vttys stuck at 80x25. Attempting boot directly to graphical.target KDM3 generates no onscreen errors, but neither starts the greeter. The journal says only display-manager.service timed out/failed to start/entered failed state. CPU: Single core AMD Athlon XP 2000+ (-UP-) speed: 1674 MHz (max) Booting multi-user then doing 'systemctl isolate graphical.target' succeeds to create a usable KDM3 greeter and allow successful login. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c17 --- Comment #17 from Felix Miata --- Created attachment 716737 --> http://bugzilla.opensuse.org/attachment.cgi?id=716737&action=edit [rv250] 2 boots' dmesgs, first with vga=791 aborting Xorg, 2nd without vga= after successful startx to KDE3 session and exit -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c19 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #716737|0 |1 is obsolete| | --- Comment #19 from Felix Miata --- Created attachment 716751 --> http://bugzilla.opensuse.org/attachment.cgi?id=716751&action=edit [rv250] on TW dmesgs booted with (black screen straight away) and without vga=791 on cmdline (after startx produced black screen) Sorry, I got my miscreant mga and ati machines' problems mixed up. 716737 was from Matrox 550. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c21 --- Comment #21 from Stefan Dirsch --- Yeah. Max is probably right. KMS is possibly broken with AGP cards in general (generic issue in latest kernels maybe?). So with vga param the fallback is fbdev driver, otherwise vesa driver. X logfiles should confirm this. And yes, we no longer have any AGP machines and/or AGP cards for testing available. I believe I can still find some R300 PCIe cards, which may still work with the current radeon KMS driver. Never tested this though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c23 --- Comment #23 from Stefan Dirsch --- Thanks. But seems instead of /var/log/Xorg.0.log files you've attached the output of startx command (most of log is missing there). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c25 --- Comment #25 from Stefan Dirsch --- Xorg -retro -logverbose 9 :99 kill it with Ctrl-Alt-BS (press BS twice shortly afterwards) --> /var/log/Xorg.99.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c27 --- Comment #27 from Felix Miata --- (In reply to Max Staudt from comment #18)

Please note that this may well be a separate bug from the Matrox case.

I search fruitlessly on bugs.freedesktop.org and bugzilla.kernel.org for anything similar to comment 13 et seq.... (In reply to Felix Miata from comment #22)

I have no Radeon AGP newer than rv250. I have AGP NV11 GeForce on 32-bit host gx270 yet to try updating since August....

TW20170308 on nv11 host gx270 works as expected. I replaced the rv250 gfxcard in host a-865 with an rv200 (Radeon 7500). It solved all problems described in comment 13 et seq., suffering AFAICT only https://bugs.freedesktop.org/show_bug.cgi?id=90572 I tried the rv250 in host gx270, but it won't POST with it. Host a-865 is logistically unsuited to try replicating with another OS, so I'm trying to find some other x86 AGP host in which to try the rv250 that has a CPU with at least sse2 to see if this trouble can be replicated in Mageia, Fedora or other before filing a new bug.... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c29 --- Comment #29 from Max Staudt --- Okay, at this point, things are very unclear. Several cards behave weirdly, some don't even POST. There are too many unknown factors at play: - we have several cards: G550, rv200, rv250. - there may be a bug in the kernel's AGP support - there may be a bug in the kernel's radeon driver - some setups don't even POST (bad bios, bad card, weird hardware?) - the X logs are truncated (leftover xorg.conf?) - there's a systemd complaint at the end of the X log in comment 22 I've lost track of things. Too many machines, too many cards, too many strange behaviors, too many packages. This bug is a Bugzilla hijack feast. Okay, PCIe seems to work as expected. Phew. Let's tick that off. Looking at AGP, we don't have the means to reproduce that. All we can do is look at logs. Please open a new bug to describe one single problem. However, given that our hands are tied (as described), please understand that we will probably have to close it. Let's bury this particular bug here, as it has become too crowded. Thanks again for your testing, it is really helpful to know where we stand. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c31 --- Comment #31 from Max Staudt --- Okay, the original problem was that xf86-video-mga no longer works when vesafb is in use. Correct? It seems I missed something: [ 58.382] (EE) MGA(0): Unable to map Framebuffer F0000000 2000000. Invalid argument (22) It could be that it can no longer map the VRAM when it is already in use by vesafb. We see similar things with KMS drivers when a userspace process keeps a memory region open. So maybe a kernel change has disallowed simultaneous mappings of that memory region...? That could also explain why the mga module isn't loaded (not that it's needed anyway). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c33 --- Comment #33 from Felix Miata --- (In reply to Max Staudt from comment #32)

Can you please test the current Leap 42.1 and 42.2 KOTDs?

Did you mean to suggest I try a 4.11 kernel from head or kernel-default-4.10.2-1.1.gbfb2d22.i586.rpm 13-Mar-2017? This was filed against TW. If you can build a 42.1 4.1 or 42.2 4.4 for 32-bit I can try it in TW. :-p

http://kernel.opensuse.org/branches/openSUSE-42.1 http://kernel.opensuse.org/branches/openSUSE-42.2

ATM the Matrox is in its original host a-865. It's an AGP card, and host a-865 has a Prescott (90nm) Pentium 4 socket 478, which does not support any 64-bit CPUs that I have access to, if any such exist at all. I have no motherboard with AGP slot that support a CPU supported by Leap. Most recently installed TW kernel on a-865 is 4.9.11. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c35 --- Comment #35 from Max Staudt --- Thanks for the feedback! Hmm, I expected to see a difference between 4.1 and 4.4 since you said that a 4.2 kernel worked, but 4.4 didn't. You're right, there are no official 32 bit kernels for Leap anymore. However the 42.1 package was still able to build for 32 bits: https://build.opensuse.org/package/show/home:mstaudt:1004453boo-kernel-421/k... Could you please extract the Mageia kernel config and attach it here? Maybe I'll find a difference there... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c37 --- Comment #37 from Max Staudt --- Perfect, thanks! If you could also test the Leap 42.1 kernel I built for 32 bits, that would be helpful. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c39 --- Comment #39 from Felix Miata --- Created attachment 717679 --> http://bugzilla.opensuse.org/attachment.cgi?id=717679&action=edit tail of dmesg -w > somefile plus head of Xorg.0.log trying to run startx I tried a repeat of comment 34 except using Mageia 6, kernel 4.9.15, Xorg 1.19.2, x11-driver-video-mga-1.6.5-1. Trying to use X with or without vga= on cmdline locks up the machine, black screen, no keyb response. Which upstream bug tracker and product should I take this to, kernel, ??? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c41 --- Comment #41 from Max Staudt --- Felix, thanks for the info, I'll process it sometime soon. For the time being, here is the download repo for the 42.1 kernel: http://download.opensuse.org/repositories/home:/mstaudt:/1004453boo-kernel-4... You gan get there by clicking on "standard" in the builds list on the right sidebar of the project page, then "Go to download repository". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c43 --- Comment #43 from Max Staudt --- (In reply to Felix Miata from comment #39)

Which upstream bug tracker and product should I take this to, kernel, ???

I think bugzilla.kernel.org is the way to go for this one, as exchanging the kernel seems to fix/break things and it's either a config change or something broke in the AGP support. Please give me some more time to double check the config before reporting upstream. Also, please check the latest KOTD before any upstream report. Finally, I'm rebuilding the 4.1 kernel in OBS, but if that fails it's not important as I now have two kernel configs to compare (thanks!). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c45 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Assignee|xorg-maintainer-bugs@forge. |maximilian.staudt@suse.com |provo.novell.com | --- Comment #45 from Max Staudt --- Taking bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c47 --- Comment #47 from Max Staudt --- Turns out that the mga module is no longer included as of kernel v4.9-rc1, as it is now hidden behind the CONFIG_DRM_LEGACY option: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... Apparently xf86-video-mga has two ways of accessing the memory, either through the DRI1 module, or by direct access via libpciaccess/sysfs. The latter should still work if the X server is run as root, and it does on kernel v4.4, but not on v4.9 (thus, the bug you reported). The failure backtrace is: error in mmap called by pci_device_linux_sysfs_map_range_wc called by pci_device_linux_sysfs_map_range called by pci_device_map_range called by MGAMapMem -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c49 --- Comment #49 from Max Staudt --- This seems to stem from the new IO_STRICT_DEVMEM option introduced in kernel v4.5 - it disallows userspace /dev/mem access to regions used by the kernel. This explains why you can start X with xf86-video-mga when booting in VGA 80x25 text mode, but not when booting with vesafb. Does booting with iomem=relaxed fix your X? If yes, please add iomem=relaxed to your boot parameters when using a v4.5 kernel or newer. This is basically the other thing to do after setting the X server setuid root in order to make old user mode setting drivers (such as xf86-video-mga) work. This change in the kernel has been introduced for security reasons, just like the DRI1 drivers are no longer included by default and the X server runs in user mode. Since there is nobody using the DRI1 driver for 3D, and thus no need to build the mga.ko kernel module, I think that setting this kernel option is the most comfortable workaround for you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c51 --- Comment #51 from Felix Miata --- Startx works, but KDM3 does not. From kdm.log: xf86TokenToOptinfo: table is NULL xf86TokenToOptinfo: table is NULL error setting MTRR (base = 0xf4000000, size = 0x02000000, type = 1) Invalid argument (22) error setting MTRR (base = 0xf4000000, size = 0x02000000, type = 1) Invalid argument (22) modprobe: FATAL: Module mga not found in directory /lib/modules/4.10.4-1-default error setting MTRR (base = 0xf4000000, size = 0x02000000, type = 1) Invalid argument (22) (II) Server terminated successfully (0). Closing log file. /usr/bin/Xorg: symbol lookup error: /usr/lib/libLLVMAMDGPUCodeGen.so.3.9: undefined symbol: _ZN4llvm19MachinePassRegistry6RemoveEPNS_23MachinePassRegistryNodeE -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c53 --- Comment #53 from Felix Miata --- I tried with neither iomem=relaxed nor vga=791 and KDM3 exited without displaying anything. Then I rebooted with both and KDM3 is now working. Maybe I did forget. They're both in the Grub stanzas now. Thanks for taking and finding the solution!!! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 http://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c55 --- Comment #55 from Felix Miata --- (In reply to Max Staudt from comment #11)

As a former Matrox user myself, I would be very glad to see these cards supported with KMS.

As noted in bug 1175754 , Debian current and next have found a way support at least one older (non-200) Matrox card's ability to use widescreen displays' modes using the mga X driver, regardless whether nomodeset is included on kernel cmdline or not. -- You are receiving this mail because: You are on the CC list for the bug.