LMCE 1.1 RC1: 2 Problems

[avajon]

hey,

first of all: this release is much better than the others. But i also have two problems:

1.) I have a Skystar2 for DVB-S - this card works very good. But i also need DVB-T, so i bought the Haupage WinTV Nova-T USB2 Stick. I've downloaded the correct firmware but it doesn't create a frontend?!?! Dmesg output is:
^{dcerouter_23319:/# dmesg |grep dvb
[   13.479103] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware
[   13.531084] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw'
[   14.162170] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
[   14.162230] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   14.370884] dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick'
[   14.370891] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
[   14.370908] usbcore: registered new interface driver dvb_usb_dib0700}

How can i create this frontend??

2. I also have a lot of EIB Devices (lights, drapes, ...). This devices are connected with the serial port. It worked great for the last 4 months (but not with LMCE, i used Pluto). When i go in the Web-Admin to Configuration->Interfaces and choose "EIB" I can't change my serial port. There is only a message "No serial port found". But why? I have a serial port - it works very fine with pluto. What can be the error?

Thanks in advance and please forgive me my bad (austria-) english. :-)

ciao
avajon

[kir]

Hi!

Regarding 2nd issue: can you try run from console the: /usr/pluto/bin/UpdateAvailableSerialPorts.sh    (it should run quickly). After this, reload the router and then try to see in Web-Admin if there are any changes in ports list. There is a recently detected issue with not always updating serial ports list, so maybe you has the same problem.

Regards, Kir

[avajon]

Hi Kir,

thanks for the advice! It worked!

So, there is only one problem that has to be solved

thanks
avajon

[kir]

Hi Avajon,

Thanks for the feedback This issue will be finally fixed in 1.1 release.

Regards, Kir