similar to: Blank console but X11 works on MCP79 - old regression since 3.8

On Friday 17 November 2017 15:43:33 Ilia Mirkin wrote: > With a new kernel, mind grabbing a dmesg with drm.debug=0x1e > nouveau.debug=debug (or maybe even =trace)? Maybe also see if > fbcon/fbdev have any debug things that can be turned on? Here's diff of the 32MB and 64MB debug logs: --- nouveau-debug-32mb.txt- 2017-11-17 18:12:06.290108330 +0100 +++ nouveau-debug-64mb.txt-

Hi, for quite some time now I would like to switch from the proprietary driver to nouveau, using a GK107 (Quadro) in a thinkpad. Unfortunately the monitors connected to the lenovo "ultra dock" are not properly recognized when using nouveau. The laptop contains a multiplexer: so in the bios it can be selected, whether the docking station's DP/HDMI/VGA-Ports are "directly"

Hi Jasmin, On Sun, Mar 1, 2020 at 11:32 AM Jasmin <jasmin.pm at protonmail.com> wrote: > > Hi, > > for quite some time now I would like to switch from the proprietary driver to nouveau, using a GK107 (Quadro) in a thinkpad. > Unfortunately the monitors connected to the lenovo "ultra dock" are not properly recognized when using nouveau. DP-MST support was first

https://bugs.freedesktop.org/show_bug.cgi?id=78161 Priority: medium Bug ID: 78161 Assignee: nouveau at lists.freedesktop.org Summary: [NV96] Artifacts in output of fragment program containing not unrolled loops with conditional break Severity: normal Classification: Unclassified OS: Linux (All)

Hi, Trying a new kernel on old [NV04] system I get tons of nouveau 0000:01:00.0: gr: intr 00000001 [NOTIFY] nsource 00000040 [ILLEGAL_MTHD] nstatus 00004000 [PROTECTION_FAULT] ch 0 [DRM] subc 3 class 004a mthd 02fc data 00000003 errors when operating on console. As I updated from 4.3 kernel, a bisect does not feel like the best start. What is that 02fc method which fbcon is probably

Hello, I''m trying to get PDB working in accordance with the instructions at http://www.cl.cam.ac.uk/~sos22/replay.bk/docs/misc/XenDebugger-HOWTO and a message from this list: http://lists.xensource.com/archives/html/xen-devel/2004-08/msg00017.html When I try to build pdb I first get errors because the Makefile is configured to treat warnings as errors, and there are some warnings.

Hello, it seems, that filtering on nexthdr (TCP/UDP) content, especially src or dst port, is not working. The following has no effect on 2.4.16 or older (even 2.2) kernels: # tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match tcp dst 3128 0xffff police rate 40kbit burst 10k drop flowid :1 Even if # tc filter ls dev eth0 parent ffff: filter protocol ip pref 50 u32 filter protocol

I have just attempted to boot a windows 7 vm in safe mode with networking on Xen 3.4.2 and found that it reboots a few seconds after the logon screen appears, perhaps somebody else on the list could test this and confirm that they see the same issue? The last few lines of the qemu-dm log show the following: gpe_en_write: addr=0x1f6c, val=0x8. gpe_en_write: addr=0x1f6d, val=0x0. gpe_en_write:

Hello. I have a linux server connected to a gigabit lan, and though that lan to a 768kbps/768kbps DSL modem. I''m trying to shape my webserver running on port 80/443 down to 512kbps, while leaving all other ports alone. The current configuration script that I''m using is as follows: tc qdisc del dev eth0 root tc qdisc add dev eth0 root handle 1: htb default 99 tc class add dev

Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I

Dear all, I have big question in my mind about "tc filter" sintax. If I give "tc -s -d filter sh dev eth0" command, then the output is like below : filter parent 1: protocol ip pref 1 u32 filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:2 (rule hit 21553629 success 37907)

Hi all, I'm getting frequent system crashes (every few hours or so) and it seems that the nouveau driver is causing the issue (dmesg output below). I see it with both v5.2.8 and the v4.19 LTS kernel. Sometimes the system completely freezes and sometimes seemingly just the nouveau driver goes down. The screen freezes and colours stream across it. Often after I reboot the BIOS logo is mangled

Hi Ben, I was looking into some of the LUT-related modesetting issues. I've noticed the following... after I load nouveau, one of my secondary GPUs shows this on first modeset (with drm.debug=4): [ 2368.081307] [drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:44:DVI-I-1] [ 2368.113148] [drm:drm_add_display_info [drm]] non_desktop set to 0 [ 2368.113183]

Hi guys Can anyone give me any reason why BX should fail - tryig to install FreeBSD 4.7 on an old machine from CDROM. The machine loads a very old version of FreeBSD from hard drive (password long forgotten) so it seems to be running OK - it auto loads X windows - so the nachine seems to be running fine. Here is the output that I do not understand ;-( : int=00000000 err=00000000 efl=00030287

On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote: > On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary > > <linux at rainbow-software.org> wrote: > > @@ -483,8 +483,8 @@ > > nouveau 0000:02:00.0: disp: 0860: 00000000 -> 00000500 > > nouveau 0000:02:00.0: disp: 0864: 00000000 > > nouveau 0000:02:00.0: disp: 0868: 00000000 -> 04000500 >

On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo at tecnico.ulisboa.pt> wrote: > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote: > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo at tecnico.ulisboa.pt> wrote: > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote: > > > > As a quick check can you try changing > >

https://bugs.freedesktop.org/show_bug.cgi?id=96737 Bug ID: 96737 Summary: G98: LightDM 1 : 0 Nouveau Product: xorg Version: git Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

Hi there, I am gettings tons of messages in dmesg output such as: [...] [ 2419.238990] [drm:drm_mode_addfb2 [drm]] [FB:65] [ 2419.243388] 00a0 2 base507c_ntfy_set [ 2419.243391] 00000060 [ 2419.243391] f0000000 [ 2419.243393] 0084 1 base827c_image_set [ 2419.243394] 00000010 [ 2419.243395] 00c0 1 base827c_image_set [ 2419.243395] fb00007a [ 2419.243396] 0110 2 base827c_image_set [ 2419.243397]

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that

Le mardi 25 avril 2017 ? 11:07 +0200, Robert Moskowitz a ?crit : > > On 04/25/2017 10:58 AM, Laurent Wandrebeck wrote: > > Le mardi 25 avril 2017 ? 10:39 +0200, Robert Moskowitz a ?crit : > >> Thanks Laurent. You obviously know a LOT more about SELinux than I. I > >> pretty much just use commands and not build policies. So I need some > >> more