2.6.22-11-xen kernel does not have xenfb and xenkbd modules

[Fastguy]

Binary package hint: linux-source-2.6.22

Hi,

I can't find the xenfb and xenkbd paravirtual framebuffer related modules in the 2.6.22-11-xen kernel. These modules are used to have a functioning X server inside a DomU, where you can see the output in an SDL or VNC window in Dom0.

The source code of these modules shall be inside the source code of xen.

Emre

[Chuck Short (zulcss)]

Its built into the kernel

[Marsu42 (marsu42)]

... while that might be true or not, i could not get a debian or ubuntu domu to run sdl or vnc with kernel 2.6.22-11-xen. Console is ok, but except for the domu dmesg 'xencons_init: Initializing xen vfb' there is no trace of a vnc listener, the dom0 refuses to run xen-vncfb. And I've tried a lot of config / kernel command line possibilities.

I hope the redhat guys don't start picking on the crappy debian xen support atm :-p

[Fastguy (erenoglu)]

Hi Chuck,

OK the module is built-in, but why am I not able to modprobe it?

voyager ~ # modprobe xenfb
FATAL: Module xenfb not found.
voyager ~ # modprobe xenxkb
FATAL: Module xenxkb not found.
voyager ~ # modprobe fbdev
FATAL: Module fbdev not found.

Guess I'm missing something. In my previous installations, even if I didn't use xenfb in my xorg.conf, as soon as I modprobe it, the SDL window popped up in front of me even though it's blank.

I'll try again this evening.

Marsu42, do you have the xenfb module in your xorg.conf?

Emre

[Marsu42 (marsu42)]

No, I did a clean installation of gutsy tribe-6 w/ 2.6.22-11-xen and there's no xenfb to be seen anywhere. Where is this module supposed to help for the sdl interface, in dom0 or domu?

[Fastguy (erenoglu)]

Hi,

I confirm that it's built into the kernel as Chuck said before. You need to put "fbdev" in the driver section your xorg.conf in order to load it.

However, I can't get xorg to load with some strange errors. Then SDL (or VNC) window appears with the tty1 login prompt.

Emre

[Marsu42 (marsu42)]

Could you please post the relevant sections of your xorg.conf - if I replace the driver with "fbdev", X does not start because "open /dev/fb0: No such file or directory"

[Fastguy (erenoglu)]

Sure, it's below. However, as said before, can't get to X, only the login prompt in SDL window. X can't start

Section "Device"
    Screen 0
    Identifier "VideoCard0"
    Driver "fbdev"
    VendorName "FBDEV Configured Vendor"
    BoardName "FBDEV Configured Board"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "FBDEV Configured Vendor"
    ModelName "FBDEV Configured Model"
    HorizSync 31.5-50
    VertRefresh 50-70
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "VideoCard0"
    Monitor "Monitor0"
    DefaultDepth 16
    Subsection "Display"
        Depth 16
        Modes "800x600" "640x480"
    EndSubsection
EndSection

and the error log in my Xorg.0.log, maybe you can see if you have similar error:

(II) FBDEV: driver for framebuffer: fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 0.0.2
        ABI class: X.Org Video Driver, version 1.2
(II) FBDEV(0): using default device
(II) Running in FRAMEBUFFER Mode
(**) FBDEV(0): Depth 16, (--) framebuffer bpp 16
(==) FBDEV(0): RGB weight 565
(==) FBDEV(0): Default visual is TrueColor
(==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) FBDEV(0): hardware: xen (video memory: 1875kB)
(II) FBDEV(0): checking modes against framebuffer device...
(II) FBDEV(0): mode "800x600" test failed
(II) FBDEV(0): mode "640x480" test failed
(II) FBDEV(0): checking modes against monitor...
(--) FBDEV(0): Virtual size is 800x600 (pitch 800)
(**) FBDEV(0): Built-in mode "current": 28000.0 MHz, 35000.0 kHz, 58333.3 Hz
(II) FBDEV(0): Modeline "current" 28000.00 800 800 800 800 600 600 600 600 -hsync -vsync -csync
(==) FBDEV(0): DPI set to (75, 75)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.3
(**) FBDEV(0): using shadow framebuffer
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.1.0
        ABI class: X.Org ANSI C Emulation, version 0.3
(EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode
(EE) FBDEV(0): mode initialization failed

Fatal server error:
AddScreen/ScreenInit failed for driver 0

Emre

[Marsu42 (marsu42)]

My X outpout is still different, but I guess this is because I don't get a sdl window either (my DomU starts just with xm console and ssh). Below is my xen config file. I read that adding extra = 'video=xenfb' should help, but it doesn't for me. Please tell me how you got your sdl window running, then we can continue to work on the X server.

--

name = "xen-debian"
xen_shell = 'root, user'
kernel = '/boot/vmlinuz-2.6.22-11-xen'
ramdisk = '/boot/initrd.img-2.6.22-11-xen'
memory = 256
vif = [ 'mac=00:A0:CC:D8:CA:D1, ip=192.168.0.101' ]
root = '/dev/hda1 ro'
disk = [ 'file:/xen/domains/xen-debian/disk.img,hda1,w', 'file:/xen/doma
boot="c" # boot on floppy (a), hard disk (c) or CD-ROM (d)
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'destroy'
sdl=1
vnc=0

--

[Fastguy (erenoglu)]

Hi, in my domU config file, the only interesting sections are:
extra = 'xencons=ttyS0 console=ttyS0 video=xenfb'
vfb = [ 'type=sdl' ]

however, i can only get the console in the SDL window, not yet the full X (i used to get it on older kernels though).

[Rolf Leggewie (r0lf)]

still a problem with the latest kernels?

[Olivier Tétard (otetard)]

I didn't test on Ubuntu, but Debian fails in the same manner to run Xorg in a domU using xenfb. The problem is Xorg related and a patch[1] which solves the problem for me is available on Novel's bugzilla (#285523, [2]).

1. https://bugzilla.novell.com/attachment.cgi?id=161573
2. https://bugzilla.novell.com/show_bug.cgi?id=285523

Olivier;

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

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 installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Rolf Leggewie (r0lf)]

no further response - > closing out the linux task.

Feel free to reopen this issue with the requested information.