Displaying 4 results from an estimated 4 matches for "mpiechotka".
Did you mean:
piechotka
2017 Jan 23
2
[Bug 99502] New: W530 hangs when iGPU is disabled and EFI started in dock
...dock
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at lists.freedesktop.org
Reporter: mpiechotka at nvidia.com
QA Contact: xorg-team at lists.x.org
W530 hangs (black screen, does not react on power button) on nouveau load when
EFI booted in dock and iGPU is disabled in BIOS. When I boot EFI outside dock
it does not happen even when I dock the laptop before loading kernel. It does
not...
2017 Jan 23
2
[Bug 99501] New: xrandr rotation does not work with reverse prime
...prime
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at lists.freedesktop.org
Reporter: mpiechotka at nvidia.com
QA Contact: xorg-team at lists.x.org
When I used reverse prime (setprovideroutputsource) the xrandr rotation
'succeeded' but the screens were in normal position.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part -----...
2017 Feb 25
1
[Bug 99954] New: Errors when using VirtualBox with 3D acceleration: gr: ILLEGAL_CLASS ch 6 [007f7f8000 VirtualBox[5063]] subc 0 class c000 mthd 2390 data 00000000
...000000
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at lists.freedesktop.org
Reporter: mpiechotka at nvidia.com
QA Contact: xorg-team at lists.x.org
On W530 with iGPU disabled I see the errors in dmesg log when I try to run
VirtualBox with 3D acceleration:
[ 8781.350709] nouveau 0000:01:00.0: gr: ILLEGAL_CLASS ch 6 [007f7f8000
VirtualBox[5063]] subc 0 class c000 mthd 2390 data 0000000...
2011 Aug 06
0
help recover from unmountable btrfs
...tem from being mounted, I found out how to adjust
some system blocks so that the kernel could get past that check and
mount the filesystem. In one case, I could get all the data I wanted
from the filesystem; in another, many checksums failed and I ended up
throwing it all away, so no guarrantees. mpiechotka''s running into the
problem and bringing it up on IRC prompted me to post for wider
consumption this patch for btrfsck, that will tell you what to do to
make the filesystem mountable again.
Add verbosity to btrfsck so that we can manually recover from a failure
to update the roots.
Signed...