** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/68440
Title:
X does not work in Xen, causes crash
--
ubuntu-bugs mailing list
** Tags added: xen
** Tags removed: cft-2.6.27
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Confirmed
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm seeing the blank screen on an freshly upgraded 8.10 64-bit AMD
system with a Intel 82Q35 Express Integrated Graphics Controller. My
xorg.conf is setup to use the vesa controller: I can ssh in, but the
keyboard and mouse don't do anything and the screen stays blank, even if
I chvt. In
I think I'm seeing this issue too on a fairly default hardy system.
Thinkpad X60s laptop, intel video.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
the problem is that there is noo 2.6.27-xen kernel (which can work as a
dom0).
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
same here...
x3100+xen+X-hang
the interesting thing is that the vba16fb driver seems to crash the maschine,
too, if enabled.
Isn't the xen-kernel pae-enabled? Perhaps there is a bug in the ram-allocation
code for the gpu in the kernel and/or in the x-driver?
--
X does not work in Xen, causes
btw, same in intrepid
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm running with an Intel 915GM on a Pentium M 2ghz laptop, running Ubuntu
8.04 2.6.24-21-xen .
The workaround of using Vesa works. I get a 1600x1200 display on my vga monitor.
If I use the Intel driver I get a black screen as other do. What is
strange is that I can't get in with ssh. ssh from
just to confirm El Diablo's solution workaround the problem -- and
without the resolution wart.
my laptop is Thinkpad X61s with intel GM965 video card.
#uname -a
Linux koala 2.6.24-19-xen #1 SMP Sat Jul 12 03:55:08 UTC 2008 i686 GNU/Linux
--
X does not work in Xen, causes crash
Looks like no-one is interested in fixing this bug (reported on 2006-10-26!!!).
I'm getting additional servers soon, the only serious choice I can make is to
install another distribution.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug
Seeing the same on an intel D945GCLF motherboard (atom CPU) with 945
chipset.
The issue looks very similar to the issues that I've had with nvidia
graphics adapters when using xen over the last year or more. The problem
there, as is clearly communicated by nvidia, is that Xen has no support
for
As El Diablo mentions, the hack above works to get X up and running.
Unfortunately, you remain stuck in a 800x600 resolution. I found that
using the intel driver works just as well (or just as badly) as the vesa
driver. I'm running latest versions of everything:
libc6-xen-2.7-10ubuntu3
Actually, I made a mistake: if I reboot using drivers other than vesa my
machine hangs quietly when gdm starts up. With the vesa driver,
everything but the resolution works.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because
Ok, I'm no Xen guy... however after experiencing a load of lock up's
when booting the 8.04 Xen kernel (64bit) , destroying my fs by powering
down by holding the button... I found this lame fix:
Now I can't speculate as to what is wrong, and I'm not going to...
however try this (It also worked
Ah, since we're seeing kernel oopses, it must be a kernel bug.
Refiling.
** Changed in: linux (Ubuntu)
Sourcepackagename: xorg = linux
Status: Confirmed = New
** Changed in: xorg-server
Status: New = Incomplete
--
X does not work in Xen, causes crash
** Changed in: xorg (Ubuntu)
Sourcepackagename: xserver-xorg-video-intel = xorg
Status: Incomplete = Confirmed
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same Problem here. Everything works until kdm tries to start. My graphic
hardware is an intel GMA 945 (Mobile 945GM/GMS, 943/940GML) too. I tried
the linux-image-2.6.24-19-xen. The screen goes blank. And nothing
happened until I press Strg+Alt+Entf, then two of the keyboard leds
starts blinking
All of the above is true, many times observed and confirmed for a long, long,
long time.
What more is needed?
Why is the status of this bug still Incomplete?
When will be there an ETA of assigning it and starting work on it?
I am surprised to see relatively minor annoyances filed with High
Agreed. This bug is 18 months old. It's probably still marked incomplete
because it's been filed under the xserver-xorg-video-intel package,
despite not an Intel specific issue -- it happens on old nVidia cards
too, as I've previously commented.
--
X does not work in Xen, causes crash
Also seeing the problem.
Intel Graphics.
My Caps and Num lock still working.
Can reboot with Ctrl + PrintScreenS - U - B
Standard install, just installed xen and rebooted again to trigger.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug
Same thing here with xen 3.2 and 2.6.24-18-xen on x86_64 with Intel driver.
The screen goes blank, but I can connect via ssh.
The ps command shows kdm as the last process and hangs.
strace shows:
open(/proc/5478/status, O_RDONLY) = 6
read(6, Name:\tXorg\nState:\tD (disk sleep)..., 1023) = 601
Xorg.0.log attached
** Attachment added: Xorg log file
http://launchpadlibrarian.net/15081341/Xorg.0.log
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same problem here using xen 3.2 and linux-image-xen (I've tested
2.6.24-16 to 2.6.24-18). I've tried to build a more recent version of
xserver-xorg-video-intel (the 2.3.1) and now I'm able to get a working
Xserver. But the problem is still there because as soon as I start X,
the kernel becomes
** Attachment added: dmesg
http://launchpadlibrarian.net/14987359/dmesg
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: oops
http://launchpadlibrarian.net/15004134/oops
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I've got the same problem in Hardy ... If i use the vesa-driver, all
things works fine but I can't work with a resolution of 800x600
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this behavior in Hardy. I'm not sure if the machine
crashes hard after the lcd goes blank because I can't get any response
at all.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Yes, this still happens with today's Hardy.
I'd like to remind you once again that Xen worked fine on this same
hardware with Fedora 8 (with X.org too, of course). Maybe comparing the
drivers in them can shed some light.
--
X does not work in Xen, causes crash
I notice that everyone confirming this bug has Intel hardware, so I'm
re-filing to xserver-xorg-video-intel, although it should be noted that
Ian was seeing the issue with the -vesa driver, so this *might* be more
than a driver bug. However, I think giving visibility of this to the
Intel folks
Can someone confirm this as still happening with latest Hardy?
Also, for reproducing this issue is it sufficient to simply install and
start up Xen, or are there any additional steps required to trigger it?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Incomplete
For reference, this happened to me on two different machines with nVidia
GeForce 4 MXs too.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: xorg-server
Importance: Undecided
Status: New
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same problem as the former comment (GMA X3100 on an XPS-m1330 on Hardy),
although using GDM.
I'd suggest it's quite important, as Xen is effectively unusable for a
normal user.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification
Some here... with intel GMA X3100 (chipset GM965 in board)
All system start ok, until kdm start, if this moment the screen go black, and
the system stop responding.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a
Same problem here using the Intel driver (default Xorg settings) with
Hardy Heron beta on a Dell OptiPlex 745 machine. I am attaching a copy
of the dmesg for the working machine (i.e. booting without Xen) and the
Xorg log.
Please note that I was able to get Xen to work with Fedora 8 on this
same
And now the Xorg log... what a pity one cannot attach multiple files on
the same comment.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/12941764/Xorg.0.log
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because
Confirming problem with Intel driver on X.org running on linux-
image-2.6.24-12-xen on Hardy.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Works for me if I explicitly tell Xorg to use the vesa driver.
I'm on an HP Business notebook NC6400, with intel 945 + ICH7 integrated
chipset and a Core 2 Duo T5600 CPU.
Using the vesa driver is of course not a real option, but I imagine
there's some incompatibility between the intel Xorg
I can also confirm this problem on Gutsy, running linux-
image-2.6.22-14-xen. If you need me to get any information from my
system, reply here and I'll get it for you.
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are
** Changed in: xorg (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Hello :-),
unfortunately I can confirm this problem on Gusty. Without starting the
xserver everything is working fine. If i start X the system 'crashes'. I
get a black screen, i can not change to console and even Numlock or Caps
isn't working.
If you need more inforation feel free to ask. I will
Bryce Harrington writes ([Bug 68440] Re: X does not work in Xen, causes
crash):
Can you please report if this still occurs with Gutsy?
Is there a 2.6.19+ Xen kernel for gutsy yet ? Since I filed that
report I had to repurpose the motherboard I was using for my Xen setup
and the new one has
Can you please report if this still occurs with Gutsy?
--
X does not work in Xen, causes crash
https://bugs.launchpad.net/bugs/68440
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
the only difference I could tell from the logs was that Mode 15c was
blank running natively.
--
X does not work in Xen, causes crash
https://launchpad.net/bugs/68440
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I still have this problem with feisty's X server packages.
(I'm still using edgy's hypervisor and dom0 kernel because feisty doesn't have
these yet).
--
X does not work in Xen, causes crash
https://launchpad.net/bugs/68440
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: xorg.0.log from native, working
http://librarian.launchpad.net/4937499/Xorg.0.log.noxen
--
X does not work in Xen, causes crash
https://launchpad.net/bugs/68440
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: xorg.0.log from under-xen, non-working situation
http://librarian.launchpad.net/4937498/Xorg.0.log
--
X does not work in Xen, causes crash
https://launchpad.net/bugs/68440
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
49 matches
Mail list logo
