From: Ian Campbell <ijc@hellion.org.uk>
To: Mike Egglestone <mike@estone.ca>
Cc: 748052@bugs.debian.org, JBeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile
Date: Wed, 21 May 2014 19:42:45 +0100 [thread overview]
Message-ID: <1400697765.29121.115.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <fc.011fc823e66ace343b9aca005d0d88ff.e66ace35@estone.ca>
On Wed, 2014-05-21 at 10:44 -0700, Mike Egglestone wrote:
> I've run Make -C xen and it compiled fine.
> How now do I boot with the xen.gz?
Copy xen/xen.gz to /boot and add an entry to your grub config
(/boot/grub/grub.cfg) which references it, you can just copy one of the
existing Xen entries and change the path.
> Also Jan mentioned that I could try one of the newer xen's.
> Should I patch this source code, or upgrade it first before booting
> it?
Probably best/easiest to boot with something like what you are using
already but built yourself first before starting to change things. So
I'd suggest starting with the xen.gz which you've just built.
Ian.
prev parent reply other threads:[~2014-05-21 18:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140513155528.2659.84403.reportbug@xen-3>
[not found] ` <1400084844.26934.6.camel@kazak.uk.xensource.com>
[not found] ` <fc.011fc823e66acb533b9aca005d0d88ff.e66acb56@estone.ca>
[not found] ` <1400148065.4386.11.camel@kazak.uk.xensource.com>
[not found] ` <1400149218.4386.24.camel@kazak.uk.xensource.com>
[not found] ` <fc.011fc823e66acbd03b9aca005d0d88ff.e66acbd5@estone.ca>
2014-05-16 8:58 ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110" Ian Campbell
2014-05-16 10:08 ` Jan Beulich
2014-05-16 10:14 ` Andrew Cooper
2014-05-16 14:48 ` Ross Philipson
2014-05-16 15:18 ` Jan Beulich
2014-05-16 15:31 ` Ian Campbell
2014-05-16 15:51 ` Jan Beulich
2014-05-16 16:04 ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile Mike Egglestone
[not found] ` <fc.011fc823e66acc6f3b9aca005d0d88ff.e66acc76@estone.ca>
2014-05-19 10:56 ` Jan Beulich
2014-05-16 15:55 ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110" Jan Beulich
2014-05-16 17:05 ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile Mike Egglestone
[not found] ` <fc.011fc823e66acc853b9aca005d0d88ff.e66acc88@estone.ca>
2014-05-19 9:01 ` Ian Campbell
[not found] ` <1400490091.32311.16.camel@kazak.uk.xensource.com>
2014-05-20 16:25 ` Mike Egglestone
[not found] ` <fc.011fc823e66acdde3b9aca005d0d88ff.e66acde1@estone.ca>
2014-05-21 8:32 ` Jan Beulich
2014-05-22 17:19 ` Mike Egglestone
[not found] ` <fc.011fc823e66aced13b9aca005d0d88ff.e66aced4@estone.ca>
2014-05-23 7:52 ` Jan Beulich
[not found] ` <537F1A700200007800015391@mail.emea.novell.com>
2014-05-23 9:21 ` Ian Campbell
2014-05-23 9:35 ` Jan Beulich
2014-05-23 10:08 ` Ian Campbell
2014-05-23 10:14 ` Jan Beulich
2014-05-23 18:53 ` Mike Egglestone
2014-05-23 20:00 ` Mike Egglestone
2014-05-21 17:44 ` Mike Egglestone
[not found] ` <fc.011fc823e66ace343b9aca005d0d88ff.e66ace35@estone.ca>
2014-05-21 18:42 ` Ian Campbell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1400697765.29121.115.camel@dagon.hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=748052@bugs.debian.org \
--cc=JBeulich@suse.com \
--cc=mike@estone.ca \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).