search for: epoxied

https://bugs.freedesktop.org/show_bug.cgi?id=92852 Bug ID: 92852 Summary: NV34: WARNING: ... at drivers/gpu/drm/drm_irq.c:924 drm_vblank_count_and_time+0x71/0x80 [drm]() Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major

https://bugs.freedesktop.org/show_bug.cgi?id=92851 Bug ID: 92851 Summary: NV34: err: MEM_FAULT Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=90871 Bug ID: 90871 Summary: NV30: Xfwm4 use_compositing - garbled display Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee:

https://bugs.freedesktop.org/show_bug.cgi?id=92893 Bug ID: 92893 Summary: NV34: XPresent compositor scrambled Product: xorg Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

On 04.11.2015 11:57, Martin Peres wrote: > On 02/11/15 08:28, poma wrote: >> An interesting results. >> >> DRI2: >> >> $ vblank_mode=0 glxgears >> ATTENTION: default value of option vblank_mode overridden by environment. >> 6321 frames in 5.0 seconds = 1264.103 FPS >> 6380 frames in 5.0 seconds = 1275.943 FPS >> 6369 frames in 5.0 seconds =

Is there a way to disable the keyboard and mouse ports? I have a machine in a public area running an application that no-one needs to touch. However, someone could come up and plug a keyboard in it and mouse and be logged in as that user (not root). Is there a way to disable the mouse and keyboard so only remote ssh connections will control the PC if changes need to be made. This would also

Hi Has anyone opened up a grandstream phone or handytone ATA to find out what is inside? What is the CPU? How much RAM? Cheers Rob

Mike McCarthy, W1NR <sysop at w1nr.net> ? 2020?11?3? ?? ??7:56??? > > > Can you reproduce the problem with this document? > > > > And, when the crash happened, could you still ping the computer from > > another device in the network? > > > > Crashing hard so that only a reset helps is usually only possible with a > > kernel bug or hardware issue,

On 04.11.2015 12:27, poma wrote: > On 04.11.2015 11:57, Martin Peres wrote: >> On 02/11/15 08:28, poma wrote: >>> An interesting results. >>> >>> DRI2: >>> >>> $ vblank_mode=0 glxgears >>> ATTENTION: default value of option vblank_mode overridden by environment. >>> 6321 frames in 5.0 seconds = 1264.103 FPS >>> 6380

Hello, looking into the issue described in the advisory below I wonder how to tackle this issues. Primarily I ask myself * is there any reason not to filter all physical memory access by default * what would be the appropriate way to change the filter set? a sysctl? Regards Maximillian Dornseif FireWire/IEEE 1394 direct memory access - CAN-2004-1038 Advisory URL:

An interesting results. DRI2: $ vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. 6321 frames in 5.0 seconds = 1264.103 FPS 6380 frames in 5.0 seconds = 1275.943 FPS 6369 frames in 5.0 seconds = 1273.629 FPS 6377 frames in 5.0 seconds = 1275.322 FPS 6387 frames in 5.0 seconds = 1277.330 FPS 6407 frames in 5.0 seconds = 1281.337 FPS 6381 frames in

https://bugs.freedesktop.org/show_bug.cgi?id=98631 Bug ID: 98631 Summary: GPU lock ups when starting GDM, SDDM, and Plasma Desktop Product: xorg Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: