| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Issues using nouveau video driver on machine as Dom0
Hello xenners,
It has recently
been brought to my attention that linux-image-2.6.32-5-xen-amd64
(2.6.32-30) was released in the Debian sid repositories [1]. Urgency
is set to high so I'd imagine the migration to squeeze will not take
long as well. The changelog shows [2]:
xen: backport TTM patches to use PCI API. Fixes PCIe GPU (specifically
Radeon and Nouveau) on Xen (Closes: #601341).
Previously I was successful using the nouveau video driver with
Xen on my laptop with nvidia graphic when using the
Debian 2.6.32-29+xen0 kernel from the ianc (Ian Campbells) xenbits
folder.
When I tried the new sid kernel (-30), I
found that I was able to boot natively (bare-metal) with full
functionality; meaning X with gnome desktop manager was working, able
to suspended and woken up, etc. (did not test sound).
When I
tried to boot the kernel through the Xen hypervisor it hangs X &
fb console like reported in a bug report [3]. My laptop is a Lenovo
ThinkPad R61 and my lspci -vvv -s 01:00.0 output is as
followed:
01:00.0 VGA compatible controller: nVidia
Corporation G84M [Quadro NVS 140M] (rev a1) (prog-if 00 [VGA
controller])
Subsystem: Lenovo ThinkPad T61
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+
66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency:
0, Cache Line Size: 64 bytes
Interrupt: pin A
routed to IRQ 16
Region 0: Memory at d6000000
(32-bit, non-prefetchable) [size=16M]
Region 1:
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at d4000000 (64-bit, non-prefetchable)
[size=32M]
Region 5: I/O ports at 2000
[size=128]
Expansion ROM at <unassigned>
[disabled]
Capabilities: [60] Power Management
version 2
Flags: PMEClk-
DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0
PME-
Capabilities: [68] MSI: Enable- Count=1/1
Maskable- 64bit+
Address:
0000000000000000 Data: 0000
Capabilities:
[78] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency
L0s <512ns, L1 <4us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+
FLReset-
DevCtl:
Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc-
AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s
L1, Latency L0 <512ns, L1 <4us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM L0s Enabled; RCB
128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width
x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64-
WRR128-
Ctrl:
ArbSelect=Fixed
Status:
InProgress-
VC0:
Caps: PATOffset=00 MaxTimeSlots=1
RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status:
NegoPending- InProgress-
Capabilities: [128 v1]
Power Budgeting <?>
Capabilities: [600
v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel driver in use: nouveau
Attached is my dmesg output.
Please advise on how one
should proceed. I'd like to know why 2.6.32-29+xen0 works but
2.6.52-30 does not work on my system.
[1]: http://packages.debian.org/sid/linux-image-2.6.32-5-xen-amd64 or
the source package at http://packages.qa.debian.org/l/linux-2.6.html
[2] :
http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.32-30/changelog
[3]
:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601341
-M
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
dmesg
Description: Binary data
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home