Displaying 20 results from an estimated 154 matches for "busids".
Did you mean:
busid
2013 Feb 16
8
Bugfix + dri1 cleanup patches
Had those patches living in my local tree for a while now.
Here is a respin on top of latest master
Patch 1: regression fix, preventing the ddx from loading if kernel
module is not loaded
Patches 2-5: Completely nuke dri1, make dri2 hard dependency
Patches 6-7: Assist people with first-time build of nouveau
Git complains about whitespace errors in patch 7, which for the sake
of me I cannot
2017 Mar 01
2
[systemd-devel] udev virtio by-path naming
On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
> >>>> One could argue about back-level compatibility, but virtio by-path
> >>>> naming has changed multiple times. We have seen virtio-pci-virtio<n>
> >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It
> >>>> might be a good time now
2017 Mar 01
2
[systemd-devel] udev virtio by-path naming
On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
> >>>> One could argue about back-level compatibility, but virtio by-path
> >>>> naming has changed multiple times. We have seen virtio-pci-virtio<n>
> >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It
> >>>> might be a good time now
2012 Nov 01
5
[PATCH 0/4] nouveau: xserver 1.13 compat fixes
Here are a few patches adding some missing functions in
NvPlatformProbe, which iirc is being used as of xserver 1.13
First patch adds a nouveau_kernel_mode_enabled helper, similar
to xf86-video-radeon
Second and third use the function in Nv{Pci,Platform}Probe
And last one ensures we can still use ZaphodHead and relative
head positioning via xorg.conf
The coding style may be a bit off, despite my
2013 Jul 22
0
[RFC PATCH] Support running nested in a Mir compositor
From: Christopher James Halse Rogers <raof at ubuntu.com>
Barring some (admittedly significant) missing optimisations? this is reasonably
complete, but can't be applied until the Xserver patch has landed,
and that needs more work.
This demonstrates the approach, however.
There's probably some code to be shared with XWayland support, around the
output handling (or lack thereof) and
2012 Jul 04
0
[PATCH] Add xwayland support (v2)
v2: Fix build against Xservers without Wayland support
Don't try to acquire/drop drm master under Wayland
Refresh for xserver 1.13 kill-all-direct-access-to-xf86Screens
Remove #ifdef soup in favour of xwayland compat header
Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers at canonical.com>
---
configure.ac | 7 ++
src/Makefile.am |
2007 Jun 09
2
Fedora and direct rendering
Hello,
I'm using Fedora 7 and I thought I should try nouveau. I couldn't get
direct rendering to work.
I found out that the Mesa package that ships with Fedora 7 doesn't
include a DRI interface for the nouveau module. So I fetched the latest
Mesa source from git, compiled with 'mke DRI_DIRS=nouveau linux-dri-x86'
and copied the produced ./lib/nouveau_dri.so in the
2017 Mar 01
0
[systemd-devel] udev virtio by-path naming
On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote:
> On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
>>>>>> One could argue about back-level compatibility, but virtio by-path
>>>>>> naming has changed multiple times. We have seen virtio-pci-virtio<n>
>>>>>> (not predictable), pci-<busid> and
2017 Mar 01
3
[systemd-devel] udev virtio by-path naming
On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote:
> On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote:
> > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
> >>>>>> One could argue about back-level compatibility, but virtio by-path
> >>>>>> naming has changed multiple times. We have seen
2017 Mar 01
3
[systemd-devel] udev virtio by-path naming
On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote:
> On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote:
> > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
> >>>>>> One could argue about back-level compatibility, but virtio by-path
> >>>>>> naming has changed multiple times. We have seen
2017 Mar 01
0
[systemd-devel] udev virtio by-path naming
On 01.03.2017 16:58, Daniel P. Berrange wrote:
> On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote:
>> On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote:
>>> On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
>>>>>>>> One could argue about back-level compatibility, but virtio by-path
>>>>>>>>
2012 Jul 06
8
[Bug 51798] New: Cannot enable second video card on nvidia quadro NVS420
https://bugs.freedesktop.org/show_bug.cgi?id=51798
Bug #: 51798
Summary: Cannot enable second video card on nvidia quadro
NVS420
Classification: Unclassified
Product: xorg
Version: 7.7 (2011)
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority:
2012 May 23
1
[PATCH (nouveau)] Add xwayland support
Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers at canonical.com>
---
This is mostly just for testing, although it should be safe to apply to nouveau
trunk.
src/nouveau_dri2.c | 34 +++++++++++
src/nv_driver.c | 163 +++++++++++++++++++++++++++++++++++++++++++++++-----
src/nv_type.h | 7 +++
3 files changed, 191 insertions(+), 13 deletions(-)
diff
2008 Jul 22
2
Dual video card, 1 monitor each (ref dual head) CentoS4.6 xorg does only 1 head
I need to start running a dual head on one of my machines. Eventual
target is CentOS 5.x. Decided to test first on my 4.6 setup (eventually
it will achieve 5.x). Both machines are fully up to date.
The test machine is 4.6, 2 radeon video cards. Searched the web, CentOS
site, even bugzilla. This bugzilla entry from a 4.2 system),
http://bugs.centos.org/view.php?id=1875
had only a WFM response.
2010 Jan 21
1
netgear wg111v2
Hi folks
I have a Centos 5.3 Box and need to know how to configure a Netgear wg111v2 USB WLAN adapter. I already have an wireless LAN build with an AP and a windows XP PC with another Netgear wg111v2 USB adaptor running on it..
Thanks
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2004 Mar 03
2
x-server with 2screens blanks while starting wine
Hi!
I just setup my ati radeon 9500 with fglrxconfig from the ati 3.7 drivers on a 2.6 kernel. I use primary a monitor and configured the x config file to use the tv as a second monitor which uses a different driver (graphic device section) due to different resolutions. All works pretty perfect, except for wine. No matter what i start in wine, my primary monitor blanks out while the tv keeps on
2011 Sep 02
2
New wireless controller
I just installed an Asus PCE-n13 wireless card into one of my CentOS 5.6 systems. It uses the RaLink 2680 chip set and I was able to get the driver loaded using modprobe rt2x00pci.ko. I saw no error and now see that the module is loaded along with mac80211 and other dependencies.
Now I need to know how to create the wlan0 device. I can find nothing via Google searches on how to create that
2010 Jun 29
2
Xserver
Hi all,
I am trying to execute Xserver on Dom0 but an error occurres.
I have a fresh Debian Lenny install. I''ve installed Xen via aptitude,
restarted the system with Xen kernel, and then installed xfce4 with all
dependencies.
When i try startx i get this errors:
(WW) RADEON; No matching Device section for instalnce (BusID PCI:4:0:1)
found
Fatal server error:
xf86MapVidMem:
2012 Aug 15
5
PV USB Use Case for Xen 4.x
Good Afternoon. My colleague Stefan (sstan) was asked on the IRC
channel to provide our use case for PV USB in our environment. This is
possible with the current xm stack but not available with the xl stack.
Currently we use PVUSB to attach a USB Smartcard reader through our dom0
(SLES 11 SP1) running on an HP Blade Server with the Token mounted on an
internal USB Port to our domU CA server
2006 Feb 20
0
crashed would be solved by sudo ?
Hi all,
Most of time I like to try out wine with game console emulators which use
fare amount of d3d or opengls, to see how much wine supports on this.
Suddenly today that the wine does not work with any emulator I have tried with,
came up with error message that is followed. But I accidentally found a workround that
with ``sudo'', the problem won't occor. Any idea ?