similar to: Syslinux EFI x64

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

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?

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]

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]

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. > > > >

Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only

On Fri, Sep 09, 2016 at 09:28:09AM +0100, John Hodrien wrote: > On Fri, 9 Sep 2016, Always Learning wrote: > > > > > On Thu, 2016-09-08 at 23:22 +0100, J Martin Rushton wrote: > > > > > Under Fedora23 issuing a yum command gets you a warning, then it > > > automatically runs the appropriate dnf command. > > > > Can you tell us the DNF for:-

https://bugs.freedesktop.org/show_bug.cgi?id=92032 Bug ID: 92032 Summary: WARNING: CPU: 0 PID: 290 at lib/dma-debug.c:1205 check_sync+0x169/0x6e0() Product: xorg Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Hi folks I use libvirt to programmatically spawn lxc containers I am facing an issue when migrating from fedora23 to fedora24 I use the stock kernel and libvirt version on both deployments, i.e.: f23: libvirt-1.2.18.3-2.fc23.x86_64 - kernel 4.5.7-202.fc23.x86_64 f24: libvirt-1.3.3.1-4.fc24.x86_64 - kernel 4.6.3-300.fc24.x86_64 First off, I need to outline that the host installation is done

On Mon, Feb 15, 2016 at 03:05:00AM -0500, Han Han wrote: >I compile the latest libvirt from fedora rawhide, but failed. >The version of my software: >wireshark-devel-2.0.1-2.fc24.x86_64 >glib2-2.47.5-2.fc24.x86_64 >gcc-5.1.1-4.fc23.x86_64 >binutils-2.26-10.fc24.x86_64 > Can you post the output of: pkg-config --print-requires wireshark If it does not output glib-2.0 and

I compile the latest libvirt from fedora rawhide, but failed. The version of my software: wireshark-devel-2.0.1-2.fc24.x86_64 glib2-2.47.5-2.fc24.x86_64 gcc-5.1.1-4.fc23.x86_64 binutils-2.26-10.fc24.x86_64 The error as following: # ./autogen.sh --prefix=/usr && make ..... wireshark/src/plugin.c:5:21: fatal error: gmodule.h: No such file or directory compilation terminated. Makefile:2442:

https://github.com/Celelibi/syslinux/tree/fix/bios/gcc5 - bios: Fix alignment change with gcc 5 0001-bios-Fix-alignment-change-with-gcc-5.patch https://github.com/Celelibi/syslinux/commit/2686a69.patch - bios: Don't try to guess the sections alignment 0002-bios-Don-t-try-to-guess-the-sections-alignment.patch https://github.com/Celelibi/syslinux/commit/ab01326.patch - ldlinux: Fix

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Does anyone know if there are any plans to update the dahdi-linux kernel module code? It no longer compiles with recent kernels, and the last release of dahdi-linux appears to have been around March of 2016. I am currently running 4.6.3-300.fc24.x86_64 (on a Fedora system obviously) and the dahdi-linux-complete-2.11.1+2.11.1 release builds and runs under this kernel, but if I try to build it under

On Mon, Feb 15, 2016 at 10:40:11AM +0100, Martin Kletzander wrote: > On Mon, Feb 15, 2016 at 03:05:00AM -0500, Han Han wrote: > >I compile the latest libvirt from fedora rawhide, but failed. > >The version of my software: > >wireshark-devel-2.0.1-2.fc24.x86_64 > >glib2-2.47.5-2.fc24.x86_64 > >gcc-5.1.1-4.fc23.x86_64 > >binutils-2.26-10.fc24.x86_64 > >

------------[ cut here ]------------ WARNING: CPU: 3 PID: 692 at drivers/gpu/drm/nouveau/nouveau_bo.c:137 nouveau_bo_del_ttm+0x7f/0x90 [nouveau] Modules linked in: ... nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper drm wmi ... CPU: 3 PID: 692 Comm: Xorg Not tainted 4.10.8-1002.fc24.x86_64 #1 ... Call Trace: dump_stack+0x63/0x86 __warn+0xcb/0xf0 warn_slowpath_null+0x1d/0x20