Displaying 20 results from an estimated 300 matches similar to: "TXTSETUP.OEM and CD-ROM?"
2013 Nov 28
3
[PATCH 1/3] inspect: recognise Debian live images as such
Check for filesystem.squashfs also in /live, since it is where
live-build places it.
---
src/inspect-fs-cd.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/inspect-fs-cd.c b/src/inspect-fs-cd.c
index 407e4f8..eaeaa6f 100644
--- a/src/inspect-fs-cd.c
+++ b/src/inspect-fs-cd.c
@@ -429,7 +429,8 @@ guestfs___check_installer_root (guestfs_h *g, struct inspect_fs *fs)
*
2013 Nov 28
3
Re: [PATCH 3/3] inspect: improve detection of FreeBSD install discs
On Thu, Nov 28, 2013 at 02:48:38PM +0100, Pino Toscano wrote:
> Check for /boot/loader.rc as "install disc" detection, using it to mark
> FreeBSD install discs.
> Also, check for /mfsroot.gz to see whether such disc is also a live one.
>
> See also RHBZ#1033207.
> ---
> src/inspect-fs-cd.c | 19 ++++++++++++++++++-
> src/inspect-fs.c | 3 ++-
> 2 files
2013 Nov 28
0
[PATCH 3/3] inspect: improve detection of FreeBSD install discs
Check for /boot/loader.rc as "install disc" detection, using it to mark
FreeBSD install discs.
Also, check for /mfsroot.gz to see whether such disc is also a live one.
See also RHBZ#1033207.
---
src/inspect-fs-cd.c | 19 ++++++++++++++++++-
src/inspect-fs.c | 3 ++-
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/src/inspect-fs-cd.c b/src/inspect-fs-cd.c
index
2007 Apr 18
0
Buy OEM Software
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 9077 bytes
Desc: not available
Url : http://lists.linux-foundation.org/pipermail/virtualization/attachments/20070414/9aa70b20/attachment.gif
2008 Nov 28
0
getting metric collection error on 10g oem for our rac databases
our sqlplus hangs after every 5-6 hrs and not giving any error.yesterday
added log groups but still facing same problem from last three days.our
production rac instances are not accessible.now oracle people
says it may be OCFS issue.can you help me to sort this issue.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2006 Apr 25
0
[PATCH] honor apic= despite MADT/MPS OEM match
While other aspects of the system configuration may still be controlled by the outcome of the table scan, if apic= was
given on the command line its effect should not be overridden here.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2007 Apr 18
0
Buy OEM Software
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 9077 bytes
Desc: not available
Url : http://lists.linux-foundation.org/pipermail/virtualization/attachments/20070414/9aa70b20/attachment.gif
2014 Feb 17
0
Rapid Prototyping &Mould Made & OEM
Dear pkg-xen-devel,
How are you ?
PowStar factory have more15-years -historythat focus in Professional Rapid Prototyping & Mould Manufacturing & OEM in China.
1.Our the technology of tolerance within +/- 0.01 mm .
2.we have technologies that use CNC Prototype machining,SLArapid laser molding, SLS rapid
2004 Jul 30
0
X100p / OEM X100p In MACs
Hello There,
I would like to ask , if the x100p / or oem x100p MD3200Chipset boards
are compatible with MACs and will they work on MACs? I've got a G4 and
I would like to get one x100p for work with asterisk and was about to
order one.
Regards
Junaid Saeed Uppal
2004 Aug 06
1
oem x100p undefined symbol ast_get_txt
I am putting together my first *. I had it running with two other pc's
running xlite and setup voicemail and a couple of menus and submenus and had
that running well. I had order a couple of oem x100p cards from
digitnetworks.
I installed them as they said with their voicepet2.2.zip drivers and did the
modprobe on zaptel and wcfxo and then ran ztcfg -vv and got this:
Zaptel Configuration
2019 Aug 14
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c.
The original commit message didn't even make sense. AMD _does_ support it and
it works with Nouveau as well.
Also what was the issue being solved here? No references to any bugs and not
even explaining any issue at all isn't the way we do things.
And even if it means a muxed design, then the fix is to make it work inside the
2019 Aug 15
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
On Thu, Aug 15, 2019 at 4:20 PM <Mario.Limonciello at dell.com> wrote:
>
> > > There are definitely going to be regressions on machines in the field with the
> > > in tree drivers by reverting this. I think we should have an answer for all of
> > those
> > > before this revert is accepted.
> > >
> > > Regarding systems with Intel+NVIDIA,
2019 Aug 15
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
On Thu, 15 Aug 2019 16:37:05 +0200,
Alex Deucher wrote:
>
> On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst <kherbst at redhat.com> wrote:
> >
> > On Thu, Aug 15, 2019 at 4:20 PM <Mario.Limonciello at dell.com> wrote:
> > >
> > > > > There are definitely going to be regressions on machines in the field with the
> > > > > in tree
2019 Aug 14
0
[PATCH 3/7] Revert "ACPI / OSI: Add OEM _OSI strings to disable NVidia RTD3"
This reverts commit 9251a71db62ca9cc7e7cf364218610b0f018c291.
This was never discussed with anybody Nouveau related and we would have NACKed
this change immediately.
We have a better workaround, which makes it actually work with Nouveau. No idea
why the comment mentions the Nvidia driver and assumes it gives any weight to
the reasoning.... we don't care about out of tree drivers.
Nouveau
2019 Aug 19
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
On Thursday, August 15, 2019 12:47:35 AM CEST Dave Airlie wrote:
> On Thu, 15 Aug 2019 at 07:31, Karol Herbst <kherbst at redhat.com> wrote:
> >
> > This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c.
> >
> > The original commit message didn't even make sense. AMD _does_ support it and
> > it works with Nouveau as well.
> >
> > Also
2019 Oct 21
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
On Mon, Oct 21, 2019 at 4:14 AM Alex Hung <alex.hung at canonical.com> wrote:
>
> We have done some tests on three of Intel + nVidia configuration
> systems with OEM _OSI strings removed - while some bugs are still
> observed, ex. one out of three has suspend/resume issues, no system
> crashes were observed - the biggest issue that worries us.
>
> The positive results
2016 Apr 05
0
Re: [PATCH 1/7] v2v: check next free oem%d.inf in /Windows/Inf
On Tue, 2016-04-05 at 15:13 +0300, Roman Kagan wrote:
> On Tue, Apr 05, 2016 at 01:47:27PM +0200, Cédric Bosdonnat wrote:
> > It seems that checking for oem%d.inf in the DeviceIds registry
> > entry
> > doesn't always list all oemXX.inf files. For example we may have
> > oem1.inf free in the registry key, but used in another one.
>
> In my experiments this
2014 May 29
2
OEM suggestions
Hey, folks,
I'm working on finding some new compute nodes. What I'm looking for is
a 64 core box, with room enough for a lot of RAM. I can get it from
Dell, or HP (bleah! a 4U box), but I need to have three quotes, y'know.
We've gotten a lot from Penguin in the past, but they're all
Supermicro, and we've had a *lot* of problems with the 64 core boxes,
so I'm looking
2019 Aug 15
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
On Thu, Aug 15, 2019 at 3:56 PM <Mario.Limonciello at dell.com> wrote:
>
> > -----Original Message-----
> > From: linux-acpi-owner at vger.kernel.org <linux-acpi-owner at vger.kernel.org> On
> > Behalf Of Dave Airlie
> > Sent: Wednesday, August 14, 2019 5:48 PM
> > To: Karol Herbst
> > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki;
2019 Sep 05
0
[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
On Thursday, September 5, 2019 5:51:23 PM CEST Karol Herbst wrote:
> is there any update on the testing with my patches? On the hardware I
> had access to those patches helped, but I can't know if it also helped
> on the hardware for which those workarounds where actually added.
Alex Hung and Mario need to answer this question I think.
> On Mon, Aug 19, 2019 at 11:52 AM Rafael J.