Displaying 20 results from an estimated 400 matches similar to: "[Bug 27905] New: DVI monitor is blank - DVI detected as Display Port ?"
2013 May 15
8
[Bug 64645] New: Massive corruption
https://bugs.freedesktop.org/show_bug.cgi?id=64645
Priority: medium
Bug ID: 64645
Assignee: nouveau at lists.freedesktop.org
Summary: Massive corruption
QA Contact: xorg-team at lists.x.org
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: roucaries.bastien+bugs at gmail.com
2009 Nov 13
1
Xorcom Astribank udev issue in Ubuntu 9.10
Hi,
I have upgraded an Asterisk installation with a Xorcom BRI Astribank
that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no
longer initialized.
When I reload the udev rules, I see that the rules seems to be correctly
loaded:
udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file
However, these rules do not seem to be triggered:
# udevadm trigger
2012 Feb 06
8
Cdrom on Linux domU PV
I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty).
With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk
(not cdrom) and only administrators can mount it.
I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing.
Is possible use cdrom on linux domU pv full working where also normal user
can mount it without
2005 Dec 06
1
RE: Hotplug scripts not working... xen/ia64 domU stoppedworking
> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xensource.com]
> Sent: Tuesday, December 06, 2005 9:16 AM
> To: Dave Thompson (davetho)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working...
> xen/ia64 domU stoppedworking
>
> On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson
> (davetho) wrote:
>
> >
2009 Feb 27
6
[Bug 20363] New: nouveau - slight pixel corruption in text
http://bugs.freedesktop.org/show_bug.cgi?id=20363
Summary: nouveau - slight pixel corruption in text
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
2019 Oct 28
3
udev on CEntOS7 - can't get a match, looking for tips...
The mtx binary requires my tape library to be assigned a sg# driver, but
the kernel periodically renumbers the sg devices. Normally, we would
write a udev rule to manually assign a persistent name, but it looks
like things have changed as I can't seem to get a match on CEntOS7. I'd
appreciate any feedback or pointers to help me get my rule working. My
two attempts are below.
cat
2005 May 16
1
TEXTFIELD_ENTER_ONLY doesn''t work
Hi Lyle,
I noticed that when creating a FXTextField with TEXTFIELD_ENTER_ONLY it
still sends messages
to its target when other keys than KEY_Return are pressed.
I usually create a textfield this way:
textfield = FXTextField.new(self, 50, self, ID_INPUT, TEXTFIELD_ENTER_ONLY)
textfield.setText(aStr)
textfield.setFocus
textfield.move(x, y, w, h)
textfield.show
This way only the enter key should
2013 Aug 29
2
Re: [PATCH V1 17/29] xen/arm: Mark each device used by Xen as disabled in DOM0 FDT
Hi Julien
> On some board, there is no alias to the UART. To avoid modification in
> the device tree, dt-uart should also search device by path.
>
> To distinguish an alias from a path, dt-uart will check the first character.
> If it''s a / then it''s path, otherwise it''s an alias.
>
> Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
>
2016 Jun 15
0
Getting HTTP path-prefix to work with syslinux.efi
On Tue, Jun 14, 2016 at 4:44 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote:
>>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP.
>>
>>
>> There's a lot of variation. Do you have a shell option
>> in your boot selections?
>
>
> None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020
>
2016 Jun 14
2
Getting HTTP path-prefix to work with syslinux.efi
>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP.
>
> There's a lot of variation. Do you have a shell option
> in your boot selections?
None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020
(firmware A16) seem have a built-in EFI shell option, but in all three
cases I had success running the external EFI shell from
2020 Feb 03
0
Re: USB devices with same vendor:product id
Hi Maxime,
Quoting Maxime Accadia (2020-02-03 14:20:47)
> Hi,
>
> We have a VM with several USB devices attached. Everything works well,
> but sometimes, after a reboot of the host, some usb device get a
> different bus/device number and that prevent the reboot of the VM :
> ...
> Any idea on how to handle this case ?
>
> We were thinking about using udev, but it
2019 Jan 23
0
[PATCH v2] fix build failure when CONFIG_KLIBC_ZLIB is not set
When CONFIG_KLIBC_ZLIB is not set, related functions
shall not be called otherwise build failure is encountered:
KLIBCLD usr/kinit/static/kinit
usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed':
/root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_'
/root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined
2019 Jan 24
0
[klibc:master] fix build failure when CONFIG_KLIBC_ZLIB is not set
Commit-ID: 534a04d85defc627b031906d27cd9d09a913adc4
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=534a04d85defc627b031906d27cd9d09a913adc4
Author: Christophe Leroy <christophe.leroy at c-s.fr>
AuthorDate: Wed, 23 Jan 2019 06:16:01 +0000
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Thu, 24 Jan 2019 23:11:11 +0000
[klibc] fix build failure
2013 Feb 07
1
[PATCH] New API: is_whole_device
---
daemon/devsparts.c | 27 +++++++++++++++++++++++++++
generator/actions.ml | 17 +++++++++++++++++
src/MAX_PROC_NR | 2 +-
3 files changed, 45 insertions(+), 1 deletion(-)
diff --git a/daemon/devsparts.c b/daemon/devsparts.c
index 9a2ce9a..1939f2a 100644
--- a/daemon/devsparts.c
+++ b/daemon/devsparts.c
@@ -245,6 +245,33 @@ do_part_to_partnum (const char *part)
}
int
2019 Jan 22
1
[PATCH] fix build failure when CONFIG_KLIBC_ZLIB is not set
When CONFIG_KLIBC_ZLIB is not set, related functions
shall not be called otherwise build failure is encountered:
KLIBCLD usr/kinit/static/kinit
usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed':
/root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_'
/root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined
2015 Jul 02
2
EFI: PXE: "My IP is 0.0.0.0"
OK there are problems.
From
https://sourceforge.net/p/edk2/mailman/message/31604654/
""In current EDKII implementation, all the network servicebinding protocols for a
NIC device are installed together on the NIC's device handle, so you can get all
of them when you have chosen a special NIC handle.""
Unfortunately there are PCs with UEFI implementations not following the
2015 Jul 03
0
EFI: PXE: "My IP is 0.0.0.0"
On Thu, Jul 2, 2015 at 9:58 AM, Patrick Masotta <masottaus at yahoo.com> wrote:
> OK there are problems.
>
> From
> https://sourceforge.net/p/edk2/mailman/message/31604654/
> ""In current EDKII implementation, all the network servicebinding protocols for a
> NIC device are installed together on the NIC's device handle, so you can get all
> of them when you
2008 Nov 25
1
Correct way to change I/O scheduler in a iSCSI dev
Hi,
What's the correct way to change configuration parameters for an iSCSI
device? For example I/O scheduler, max_sectors_kb, etc...
I could add commands to the S99local script:
echo noop > /sys/block/sdb/queue/scheduler
echo 64 > /sys/block/sdb/queue/max_hw_sectors_kb
Unfortunately, iSCSI device names might change from sdb to, say, sdc
(server reboot, iSCSI target reconnection).
2015 Jul 03
2
EFI: PXE: "My IP is 0.0.0.0"
>>>
Lovely, the ServiceBindings are on a handle that resembles the NIC
while the Pxebc is IP-type specific.? Looks like we should try to do a
ServiceBinding based on Pxebc but fall back to MAC-based searching,
saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.?
Presumably the UDP and TCP handles _should_ be the same...
--
-Gene
<<<
OK now it
2009 Jul 31
1
[PATCH] [memdisk] Additional EDD Device Parameter Table fields
Some additional fields from the EDD-4 spec. draft for the Device
Parameter
Table have been added into the structure in setup.c and memdisk.inc.
These
were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM
ThinkPads.
---
memdisk/memdisk.inc | 11 +++++++++++
memdisk/setup.c | 10 ++++++++++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/memdisk/memdisk.inc