search for: git0.1

On 20.12.2015 09:55, poma wrote: > ... > > Syslinux MultiFS test: > > - QEMU/KVM SeaBIOS: PASSED > - Bare-metal BIOS: FAILED [1] > - OVMF: FAILED [2] > - Bare-metal UEFI: not tested > > > [1] stalled: > Loading (hd3,2)/vmlinuz-4.3.2-200.fc22.x86_64... > > > [2] "failed: No such file or directory" > >

... Syslinux MultiFS test: - QEMU/KVM SeaBIOS: PASSED - Bare-metal BIOS: FAILED [1] - OVMF: FAILED [2] - Bare-metal UEFI: not tested [1] stalled: Loading (hd3,2)/vmlinuz-4.3.2-200.fc22.x86_64... [2] "failed: No such file or directory" http://git.zytor.com/users/pcacjr/syslinux.git/tree/core/include/multifs.h?h=multifs-for-upstream#n27 * MULTIFS SYNTAX: * (hd[disk

To share with you the result of testing, Syslinux EFI x64 It actually works pretty solid. Starting graphical installation $ liveinst -G ... As seen on the screens [1], it is unnecessary to install a boot loader thus Grub 2, through the installer, but upon successful completion, it will be done manually - Syslinux EFI x64 installation. Do not reboot. Switching to a freshly installed system $

I''m currently playing around with native btrfs multi-device support in systemd. There might be a few "hotplug issues" to solve, here is the first one: A mounted (otherwise unused) multi-device volume (USB multi-slot card reader), hangs at: $ umount /mnt with (fedora) kernel 3.6.0-0.rc5.git0.1.fc18.x86_64 Any idea what to look for or what to try? Thanks, Kay [

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2) Where vanished these Chipset & Family super cool lines?

On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner <mario.kleiner.de at gmail.com> wrote: > When we are at it, the one with the title "[PATCH] drm/nouveau: Use > drm_vblank_on/off consistently" from Daniel, which has a reviewed and tested > by me also never made it into nouveau. > > Maybe pick that up as well? > > -mario > If you refer to "[1/3]

Hi All, Booting my local KVM guest with a build of 3.18-rc1 this morning, it hangs during the normal dracut splash screen When I configured the guest to use a serial console, I got the output below. The guest is a typical KVM guest created with virt-manager, using QXL as the display driver. Nothing fancy about it. I'll try and do a bisect or some other experimentation today, but I thought

Hi All, Booting my local KVM guest with a build of 3.18-rc1 this morning, it hangs during the normal dracut splash screen When I configured the guest to use a serial console, I got the output below. The guest is a typical KVM guest created with virt-manager, using QXL as the display driver. Nothing fancy about it. I'll try and do a bisect or some other experimentation today, but I thought

On 20.10.2014 21:30, poma wrote: > On 20.10.2014 08:13, poma wrote: >> >> 02:00.0 VGA compatible controller: >> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >> Chipset: G98 (NV98) >> Family : NV50 >> >> The same for all four kernel: >> - 3.18.0-0.rc0.git8.1.fc22.x86_64 >> - 3.18.0-0.rc0.git9.1.fc22.x86_64 >> -

On 21.10.2014 02:23, poma wrote: > On 20.10.2014 21:30, poma wrote: >> On 20.10.2014 08:13, poma wrote: >>> >>> 02:00.0 VGA compatible controller: >>> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >>> Chipset: G98 (NV98) >>> Family : NV50 >>> >>> The same for all four kernel: >>> -

Hi, I've encountered a severe regression in TU116 (probably also TU117) introduced in 5.3-rc4 (valid also for recent 5.4.2) [1]. The system usually hangs on the subsequent graphic mode related operation (calling xrandr after login is enough) with the following error: > kernel: nouveau 0000:01:00.0: fifo: SCHED_ERROR 08 [] ... > kernel: nouveau 0000:01:00.0: DRM: failed to idle channel

Heya, With latest Fedora Rawhide Kernel, I see a nested KVM guest hanging at boot (not unusual). Rich once suggested this[1] to try to attach gdb to the nested L2 guest to find out where_ it's stuck, tonight I set out to try it out (with KVM & TCG). Below is all what I tried. In guest hypervisor (L1): $ git clone git://github.com/libguestfs/libguestfs.git $ git log | head -1

With lightweight desktoping, the atomic modesetting seems far from robust. BUG: unable to handle kernel NULL pointer dereference at 0000000000000021 IP: dma_fence_wait_timeout+0x36/0xf0 ... Oops: 0000 [#1] SMP Modules linked in: ... nouveau ... CPU: 0 PID: 6895 Comm: Xorg Not tainted 4.10.5-1001.fc24.x86_64 #1 ... Call Trace: drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]

https://bugs.freedesktop.org/show_bug.cgi?id=112239 Bug ID: 112239 Summary: nouveau hangs video with TU116 - regression in kernel 5.3 Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: not set Priority: not set Component:

On 2019-12-16 18:08, Ilia Mirkin wrote: > Hi Marcin, > > You should do a git bisect rather than guessing about commits. I > suspect that searching for "kernel git bisect fedora" should prove > instructive if you're not sure how to do this. Thanks for your suggestion. I realize that I can do it at the Git level and it is the ultimate way to go. However, building the

Hi! I with my colleagues from Samsung trying to run systemd in Linux container. I saw that the others are experimenting in this topic, so I would like to present the results of my work and tests, perhaps it will be helpful to others. As the prototype I used a manual written by Daniel: https://www.berrange.com/posts/2013/08/12/running-a-full-fedora-os-inside-a-libvirt-lxc-guest/ After many

https://bugs.freedesktop.org/show_bug.cgi?id=76319 Priority: medium Bug ID: 76319 Assignee: nouveau at lists.freedesktop.org Summary: [NVE6] MMIO FAULT, black screen on K2100M QA Contact: xorg-team at lists.x.org Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: d-bugzilla at moens.cc

On 2019-12-16 19:45, Ilia Mirkin wrote: > The obvious candidate based on a quick scan is > 0acf5676dc0ffe0683543a20d5ecbd112af5b8ee -- it merges a fix that > messes with PCI stuff, and there lie dragons. You could try building > that commit, and if things still work, then I have no idea (and you've Nice shot Ilia! I managed to build kernel from suspected bd112af5b8ee and it fails

Btrfs has been broken for me for ages. I first reported it on this list 5 months ago[1]. Below is a very simple reproducer that anyone can run. *NB* before you run this, adjust /dev/sda & /dev/sda1 to point to an unused block device! ---------------------------------------------------------------------- #!/bin/sh - set -e while true; do parted -s -- /dev/sda mklabel msdos parted -s --

On Wed, Dec 02, 2015 at 06:40:32AM +0100, poma wrote: > On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner > <mario.kleiner.de at gmail.com> wrote: > > When we are at it, the one with the title "[PATCH] drm/nouveau: Use > > drm_vblank_on/off consistently" from Daniel, which has a reviewed and tested > > by me also never made it into nouveau. > > > >