Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - danielmayer

Pages: [1]
Hi all,
now for the first time I'm perhaps able to give st. to the community instead of always asking ;)

"mini-howto" for a LMCE-core in a VM: (please read it fully before beginning as its "golden thread" is not straight ;))

My server:
Tyan n6650w, currently one Quad-Opteron 2352, 8GB RAM, 8x1TB HDDs at an Adaptec 2820SA, ATI 2600XT. The server has uses a Technisat Skystar HD2.

Very Important: The Host-CPU(s) needs to support VT-d (Intel) or AMD-V (AMD). The Barcelona-Opterons are quite fine for this. I did not look up for other CPUs, but newer AMD should all have this feature.
My "Host", as the physical server ist to be called in this text, runs at Kubuntu 9.04 x64, patched with latest updates. You can choose the "type" (x32/x64) for each virtual machine individually, so it does not hinder LMCE-x32.

1) Set up your Host/Server with any Linux that supports hardware-KVM. Kubuntu 9.04 is nice as it features the latest KVM-packages. Install all KVM packages, if not already. Install and use "virt-manager" on KDE for an easy installation of a Kubuntu 8.10 guest, but install the VM in the "System" section, as it gives a necessary NIC-option: Bridged-Mode for the NIC! If there's no "System" available, start virt-manager from the console "virt-manager -c qemu://meinserver/system"

1a) In the install options, when assigning the NIC, take "bridged mode -> share physical network (eth0)". You can assign it later an IP in the "normal" network-range, LMCE will detect and configure quite fine a kind of double-bridge which runs smoothly.

1b) Install the guest-Kubuntu as usual now. I recommend saving the "pure" Kubuntu guest for faster recovery if st. does not work later.

1c) After installation, start the VM and look if everything is ok. I recommend to assign the 192.168.80.x IP-range to every PC in the house or change the LMCE-install-files...
My Host uses Assign the virtual Kubuntu e.g. the IP, netmask, gateway [Host-IP, in this example] and do all the updates. I strongly recommend to shut down every DHCP-server as the LMCE-core, installed in the next step, should be the only one in the LAN.

1d) Install LMCE in the VM as usual. I recommend to edit the installer-files before starting the installation with the current usage: "vim", set device-type to Core, Ext-DHCP no, run dhcp-server yes and put in the IP-values for your "external" network, see above.
When the installer has finished and restarts the VM, it should run quite fine. The pluto-admin page should be available from every PC in the house with the standard address ( or .252 in this example). As it happens, the VM will use two IPs, the one assigned in 1c) and the .1-default IP. Not necessary, but it does no damage.

It's now time to put the TV-card(s) into the VM.

2) Grab the 2.6.30-rc7 (the latest available) source, unpack it on the Host to e.g. /usr/src/linux-2.6.30-rc7 and do a "make menuconfig"

3) Follow the instructions in: to assign the card to the virtual machine. I tried those instructions for many times without success because they miss to state that a 2.6.30.x-kernel is needed!!
- I tried the, but it misses the pci-reset-ability or anything else. 2.6.29. is bad, 2.6.30 is your friend.

3a) After compiling and installing the new kernel, enter /etc/libvirt/qemu and search for your VMs' .xml file. Edit it (e.g. "vim lmce810.xml") and add the following lines:
    <hostdev mode='subsystem' type='pci'>
        <address bus='0x01' slot='0x04' function='0'/>   
Of course, you need your own values. My card is located at 01:04.0, so simply adapt it to your needs.
Save the file and do the reboot with the new kernel.
(you can do this step any time, but you need a restart of the libvirt to load the edited .xml; simply restarting virsh/virt-manager isn't enough)

4) After you now did the remaining steps of the KVM-link above (3-6), test if everything is ok:
- kernel 2.6.30.x is running on the Host?
- do a "lspci -v" on the Host. The DVB-card should now list the driver "pci-stub"

5) start up the VM-LMCE. Login on the ususal ways, e.g. via putty from any Windows-PC. On the VM, do a "lspci". The dvb-card should be present.

8) Install the drivers for the dvb-card on the VM and have fun.


It's a crude howto, but those of you with some linux knowledge should get the points. When setting up the whole system again, I'll take some screenshots to give a "nice" Howto. Please excuse the bad englisch, I lack the practise...

This should be possible with multiple PCI-cards. It may even possible *only* with all PCI-cards, as the KVM-Howto mentions that all PCI-devices behind a bridge need to be assigned in whole.
I did shutdown the firewire-port in BIOS to have the DVB-card as the only device behind a bridge on my mainboard.
If you experience problems which sound like this, try "lspci -t" on the Host and have a look for your DVB-cards.
On my Host it looks (now, after disabling firewire) like:
           +-06.0-[0000:01]----04.0                                           (<- DVB-card)
           |                    \-00.1-[0000:04]--
           |                 \-00.1


I used many, many days to get this working, so don't give up! I got it working and so can you.
And if someone asks "why the hell....": I use another VM with Windows Server+Exchange Server and the Host hosts as internal file server... other applications may come in future.
- and the weekly LMCE-experiments "8.10" do not interfere with the normal server services ;)

Pehaps a Wiki-Page would be nice? I'd do the first text ;)


Hi all,

I just tried the beta3-x64, CD1 & CD2, on a Kubuntu installation x64 via alternate-install CD.

The system is set up properly. I start the LMCE-install program and give all the answers. Then the routine begins to cache the CD1, CD2 and the "kubuntu live cd", where I use my installation CD (alternate install x64 CD).
I tried that at least six times, everytime the system totally hang up during this caching. Either during CD 2 or the Kubuntu Live CD...
Total hang up, btw, the system has to be rebooted via reset switch, no reaction from Linux anymore.
The problem was once with the CD2, two times with the Kubuntu-x64-alternate-CD. Then I though it could have a problem with the alternate-Cd, so I used the "normal" Live-CD. So another three hang-ups, totaling to six.
btw: for the installation, I have no internet connection available.
Any ideas?

A second problem: On my "big" PC, I use a SCSI-disk for the system(s) with four SATA-HDDs for data. During installation from the live-cd the fdisk detects the SCSI-disk as "sdc" with the SATA as sda, sdb, sdd and sde. Wen I choose the sdc2 as "/" and try to install grub on "/dev/sdc", the installer gives an error message (LSI 1020/1030 U320 controller, Nforce4 SATA). In the bios I choose the SCSI-hdd after the DVD-R with no other boot device options.
Why the error and is there a solution?

Oh, and a third:
Bluetooth. I use the logitech mx-5000. When starting the gui kubuntu, I need to plug out and re-plug in the bt-adapter else the keyboar/mouse aren't functional. If I boot in the repair mode, everything is fine...
I have this problem both with 7.04 and 7.10-kubuntu...

Thanks for the help

Developers / UI2 with ABlending now with ATI?
« on: November 23, 2007, 11:51:50 am »
Hi, all,
does LMCE now run with the newest ati-drivers smoothly with ui2/ab? It supports composite and aiglx now, as it seems, so the alpha-blending should work.
Anyone tested this?

Installation issues / Rendering Orbiter skin #19 - hangs.... :(
« on: June 10, 2007, 11:59:56 pm »
Hi, all!
First: Beta 2 greatly improved the installation compatibility, after I did not get any installation with one of the older versions... ;)
I installed on a new Asus M2A-VM (w/HDMI, but connected via DVI), Athlon X2EE4200+, 2x1GB RAM, onboard ATI x1250pro graphics. It was the usual tricky thing to install the ATI-drivers ("DRI missing", and all that), but after I got that smooth, the installation routine runs quite fine.... until....
the startup.
When starting "core services", the Launch Manager tries to set up the skins for the Orbiter(s). In the bottom message board, it stands at "Generating skin for Orbiter #19...", and the bar shows either "Rendering screen 5 of 5" or "Rendering screen 245 of 2xx", but doesn't get any further - even after hours...
Any ideas where the problem lies?

Installation issues / Debian 4.0 base - compatible?
« on: April 16, 2007, 10:44:35 am »
By default, the question itself reminds me bitter of Win95/98/98SE-ages.... :(
It seems impossible for Linux devs to keep a compatibility in qt3/4, gtk1x/2x, etc... - :/

I'm not a "newbie" to Linux, but try the change from SuSE to a debian-based distri. A bad choice as it seems:
I tried the ubuntu 6.10-installation about two whole days with many, many problems never seen before and a finally "fail": Asrock AM2NF3, Athlon 64X2EE4200+, DDR2, 1950ProAGP.
The installation routine did not work in normal or safe video-modes. Text-based setup did work on the 8th-try: Very, very bad USB-support in Ubuntu, as it seems. I had to disconnect all USB devices for a smooth installation without "some installation error occurred". Even then, a "select and install software" had no selection available...(?is this the normal behavior?)
The concept of not having a "root" gave problems when installing the ati-driver - it was simply not possible: sudo is not enough. I had to "install" the root user manually and change to "su". And after the successful driver-install, Gnome won't start anymore...
"Never again Ubuntu!" :(

So finally my question: Did anyone try to install LMCE on the new Debian 4.0? I give it some hopes because of the self-supported CD of LMCE.... The download takes some more.... days... so enough time to ask you :)


Pages: [1]