Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480

[Flavio <fbcyborg@xxxxxxxxx>]

Meanwhile I am performing a new suse installation (as a PV guest) using
this installation method:
http://bderzhavets.blogspot.com/2009/02/install-opensuse-11.html

It seems to work, even the mouse is not working at the moment.
Let's see what happens.

Cheers

On 13 November 2011 10:12, Flavio <fbcyborg@xxxxxxxxx> wrote:
> On 13 November 2011 01:13, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
>>
>> Sorry - I got busy.
> No problem!
>
>> Ok - while the domu is running, let's see the output of
>> in dom0: ls -alFR /sys/bus/xen* ; ifconfig ; brctl show ; & netstat -tlp |
>> grep 59
> These are the outputs produced when the new 3.1.0 kernel is running and the
> network is not working:
> http://pastebin.com/6yRqnzrh
>
>> in domu: ls -alFR /sys/bus/xen* ; ifconfig
> http://pastebin.com/eaiVdHz0
>
> Now I came back to 2.6.37 (network working) so I can use ssh.
>
>> Ok - in domu, post the output of:
>> lsmod|egrep 'vesa|cirrus'
> cirrusfb               32579  0
>
>> egrep -i 'vesa|cirrus' /boot/config*
> /boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_BOOT_VESA_SUPPORT=y
> /boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_CIRRUS=m
> /boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_UVESA=m
> /boot/config-2.6.37.1-1.2-desktop:CONFIG_FB_VESA=y
> /boot/config-2.6.37.1-1.2-desktop:CONFIG_SND_HDA_CODEC_CIRRUS=y
> /boot/config-3.1.0-1.2-desktop:CONFIG_FB_BOOT_VESA_SUPPORT=y
> /boot/config-3.1.0-1.2-desktop:CONFIG_FB_CIRRUS=m
> /boot/config-3.1.0-1.2-desktop:CONFIG_FB_UVESA=m
> /boot/config-3.1.0-1.2-desktop:CONFIG_FB_VESA=y
> /boot/config-3.1.0-1.2-desktop:CONFIG_SND_HDA_CODEC_CIRRUS=y
>
>> ls -alF /sys/bus/pci/devices/0000:00:02.0 (your video device)
> lrwxrwxrwx 1 root root 0 Nov 13 09:57
> /sys/bus/pci/devices/0000:00:02.0 ->
> ../../../devices/pci0000:00/0000:00:02.0/
>
>> ls -alF /sys/bus/pci/drivers/{vesa,cirrus}*
> ls: cannot access /sys/bus/pci/drivers/vesa*: No such file or directory
> /sys/bus/pci/drivers/cirrusfb:
> total 0
> drwxr-xr-x  2 root root    0 Nov 13 09:57 ./
> drwxr-xr-x 23 root root    0 Nov 13 09:57 ../
> --w-------  1 root root 4096 Nov 13 09:58 bind
> lrwxrwxrwx  1 root root    0 Nov 13 09:58 module -> 
> ../../../../module/cirrusfb/
> --w-------  1 root root 4096 Nov 13 09:58 new_id
> --w-------  1 root root 4096 Nov 13 09:58 remove_id
> --w-------  1 root root 4096 Nov 13 09:57 uevent
> --w-------  1 root root 4096 Nov 13 09:58 unbind
>
>> modprobe cirrusfb
> module is already loaded but no errors reported.
>
>>
>> Let's see which driver is servicing the video card. On my systems, cirrusfb 
>> is
>> a module, vesa is builtin. Builtins will not show up as a kernel driver in
>> lspci -vvv. Then we'll see whether the cirrusfb module gets an error on
>> loading.
> It seems not during loading even I've found this in the dmesg:
> [   32.626308] cirrusfb 0000:00:02.0: BAR 0: can't reserve [mem
> 0xf0000000-0xf1ffffff pref]
> [   32.626312] cirrusfb 0000:00:02.0: cannot reserve region 0xf0000000, abort
> [   32.626324] cirrusfb: probe of 0000:00:02.0 failed with error -16
>
>> Hmm - that's an error I would expect with earlier versions of xen. Eg - xen <
>> 3.4.0 can't boot a pvops domu, without backported patches. What distribution
>> is your dom0, and what xen version?
> First of all, I say that my dom0 works like a charm with most of my domUs.
> Gentoo Linux x86_64 kernel 3.1.0-gentoo
> app-emulation/xen-4.1.2
> app-emulation/xen-tools-4.1.2
> I'm using xl toolstack.
>
>
>> Which is what we are checking above.
> Mmmh, I think it is not, after having seen the result above :|
> Do you agree?
>
>>
>> Finally, post your full dmesg from your domu. Maybe something will jump out 
>> at
>> me.
> Yes, here it is: http://pastebin.com/vNpumSik
>
> Thanks a lot,
> --
> Flavio
>



-- 
Flavio

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users