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.

Messages - toppot

Pages: 1 [2] 3 4
Installation issues / Re: VNC to the core?
« on: February 18, 2012, 07:20:08 am »
i mean Remote desktop so i can access it like i was at the core itself

I believe your question was understood - and the answer was correct. There is something strange in your request. When it is a core, all you would ever need to control it is ssh and the web-interface. The only thing you could do more than that by seeing the core's own screen would be to watch media... But then you are using it as a hybrid, and that you would do in a living area, right?

Could you explain why you would like to "be next to it" - which kinds of "commands" do you believe only can be given directly at the console? Perhaps it is just a small misunderstanding that could help you to use the system more efficiently..


Installation issues / Re: Core as a VM on a mac OSX server
« on: February 13, 2012, 11:28:09 am »
i do not know of anyone that has made it work in vmware, but it has been known to work in virtualbox.
it needs to be the dhcp server if you want the network plug and play stuff to work and if you want to run media directors. which means you need at least two physical networks on the vm host as well.

I have installed - and working - both 8.10 and 10.04 in VMWare server 2.0.2 (think it is .0.2)... Working very smooth. I install with 1 bridged card (for external), and 1 host-only card (for internal). You can then deactivate the LMCE firewall... Then when everything is working and stable you can deactivate your current dhcp, and then also make the internal card bridged... It will of course mean changing your current fixed IP mappings - and that everything from the inside will be NATed trough LMCE..

This for me is not the optimal any more, I will soon install on iron, and then have dual internal networks, one for LMCE and one for the rest - and with the LMCE firewall off. But the dual network is not the primary reason for my changes, it is actually to support PCI cards (and USB 2.0, which is not on my current server - since it is old, but has 12 Gigs of RAM and runs "the rest").


Users / Re: How much HD space do I need for Core + MDs?
« on: January 31, 2012, 05:52:45 pm »
You just described me in 8 simple sentences, you stupid lego-eater.

Lego-eater... So strange what you associate a nationality with... Could have been H.C. Andersen (and the little Mermaid), Tivoli, B&O (which is a dinosaur productline/brand), Wind Power (which incidentally is my game - We are world leaders here), Carlsberg (also my game, in a different way), Bacon - or Lego... Funny thing is that I actually (through a shared interest in Arabian horses) knows some of the billionaire (not in play money....) Lego owning family.

Where are you from, rabbit-eater??  8)

Users / Re: How much HD space do I need for Core + MDs?
« on: January 31, 2012, 09:57:09 am »
Your reply was useless, too.  Mocking inexperienced users has got to be the single best way to destroy the LinuxMCE community.  Keep it up and watch the damned project crash and burn because its users are all going to flock to XBMC, if they haven't already started to, if this type of shit keeps up.

Peace dude... and calm  8)

There's caring mocking and evil mocking - sometimes in writing telling the difference is impossible...
btw: users get attracted or is put off by a number of reasons, the tone on the main board is in my opinion actually quite important to keep people on board - we should be nice and polite - but at the same time there should be "rummelighed" (a danish word not easily translateable to any language, googles best shot is spaciousness - but it all about sentiment), thus leaving room for all kinds of behaviour/people:

1. Those that has poor language skills like myself.
2. Those taht spel por
2. Those that can't count.
3. Those that ask silly questions.
4. Those that gives silly answers.
5. Those that use sarcasm.
6. Those that are put off by sarcasm.
7. Those that needs to blow out steam.
8. Those that gives long boring answers to something that is water under the bridge, and do so in the shape of lists....

I hope you get my point - actually my own moral standard only allows me to mock those I believe to be strong/knowledgeable... Meaning it's a weird display of respect. But that's just me. There where, I am sure, no intent to put you down or annoy - just to also throw in a bit of relaxed comments. Posde does this from time to time :)

I hope you got the frustration out - and feel motivated to continue working with this "waste of time" and "butt f****** ugly" system  ;) I for one loves the challenge and the possibilities.


Users / Re: How much HD space do I need for Core + MDs?
« on: January 30, 2012, 04:51:41 pm »
A question gets asked. A detailed answer provided. Answer doesn't fit. Ask again. Interesting.

Ha Ha - good one.

I'd have to say I believe that 40Gb should suffice, granted you can live with purging caches and running out of space frequently... ::)


Users / Re: Multiswitch MythTV setup
« on: January 28, 2012, 08:22:06 am »
I've been away for a bit. I tried before leaving and today a bit, but got the same result. I currently only have one of the quattro's installed/connected to the multiswitch. What is strange is I can choose no DISEqC, or DISEqC Pos1 or 2, and still get my channels. Looking at the multiswitch it should be pos 1. Maybe it's not picky if there's only one quattro installed, I don't know.
Would be very surprised if the switch wasn't picky with only one LNB attached... When you get a lock either way, it tells me the that the DISEqC is not picked up (well, sent out) correctly... But again, try looking at the working setup from one of the regular receivers - how is DISEqC configured here? Where is it "you can choose no DISEqC, or DISEqC Pos1 or 2, and still get my channels."?? Is that on a regular sat box? Have you had it working with both LNBs installed at any point?

In the myth-tv setup I have tried exactly what you wrote, both Pos 1 and Pos 2, no luck. I also tried without a switch and just an LNB in the configuration and that actually locks on (which I don't in DISEqC mode) to some of the transponders, however no channels are found. The transponders give channels on the normal satellite receivers/boxes.
The Switch (the DISEqC part of it) probably just defaults to Pos1 when no commands are received - which is nice for now. I recommend ignoring DISEqC until you have the card working. When you write that you get lock "to some of the transponders" that really is a tell tale sign for me that the driver isn't working!
I assume your are running 10.04 with a 2.6.32 kernel. Your card have had drivers included in the kernel since 2.6.28 - but they are buggy... Please take a look at this link for hints to a solution:

I have tested one of the HVR-4000 on my Windows machine. It can get both the DVB-T and the DVB-S channels meaning that card is functional. So I think the cards don't install properly under LinuxMCE. They get listed under the MythTV-setup but something obviously goes wrong. The DVB-T part doesn't work either, but then again it didn't work under 8.10 when DVB-S did - so that might not say much.
You should be aware that due to limitations of the card Myth (or any system) can not use DVB-S and DVB-T simultaneously. Not a problem on a desktop setup, but for a server setup like Myth this limitation is important.. And I am quite sure that Myth will not "release" the DVB-S lock to allow using it as a DVB-T tuner when not requiring DVB-S... The problem is that for Myth there is no conflict, since these 2 tuners are on different adapters. (Adapter 0 should be DVB-S and adapter 1 DVB-T, if I remember correct?)

I at least can't see any other possibility for now and I don't have any other type of DVB-S card (only a DVB-T one) in order to test this theory. I guess my options now are getting hold of another DVB-S card or figuring out what can be wrong with the HVR-4000 installation. I have no experience but maybe it's be the firmware? I could sell the HVR-4000 and get something else but they're nice cards if you can receive DVB-T/S/S2 channels.
Have a stab at rectifying the driver issues :)
Or consider it this way - these cards are mostly nice in a single user setup, so for Myth you could do with any other DVB-S2 or DVB-T card, or a mix of them, and then allow your household to have direct sat feed (or DVB-T) to their windows desktops through the HVR-4000 cards.. Even if it would be redundant if you get your Myth setup working, but that's beside the point  8)

As for the T90, you're absolutely correct ^^ Just having 1-2 LNB's on it is a bit of a waste but $200 for skipping cable-TV (for about a dozen TVs) and having the flexibility to expand isn't so expensive. I was going to get Thor 5-6 for the Swedish channels but I was unaware they displaced the "nordic" beam more towards the north, so I'm unable to get it in Switzerland (where I live).

Anyway, a big thanks for the help and making sure I'm on the right road.
You are very welcome - I still hope you manage to get it working :)
I have the T90 myself, and living in Denmark means I never have to concern which of the beams I am trying to catch for the Nordic providers - although I am also able to get SkyUK Freesat on the same dish - even if this beam is supposedly focused very much on UK.
I would argue that you should be able (with luck and fine tuning) to catch the Thor Nordic beam on a T90 - but the thing with these beams is that they are not decreasing linearly in strength when you move out of their focus area... So somebody 50 Km from you might see very different results (better or worse). Anyway, I believe more than half of both Canal Digital and Viasat is on beams, that should be very possible to catch for you... You would need to tinker with decoding anyway, so lets get you a stable Myth before going down this route ;)


Users / Re: Post your MD Boottimes
« on: January 27, 2012, 09:44:55 am »
You can just put them to sleep. Go into Media Director in the admin page, set the PowerOff mode to S instead of H.  My P4 MD wakes up in 10 seconds.
Good to know, Aviator. Once my system is stable  ;) I will try that to speed things up and see if I can get an idea of the comparative power consumption... presumably, even asleep, they draw some juice.
Juice in "Suspend-to-RAM" is perhaps a bit over the top.. It should not use much... But please be warned - this is not something that is known to "just work"...

I'm going to borrow a cross-over cable from work today and time my MD boottimes via the network (with the hound-dog-slow hub) and direct nic to nic connection to see just how much of an impact the network speed is having.... should be interesting and if it comes out dramatic will light a fire under me to order the gig switch.

Really looking forward to this one  8)
(I would guess around 150 secs but could be surprised... Would think the limiting factor could be the rotation speed of your core HDD, which would never be a problem for recording/streaming large media files)


Users / Re: Post your MD Boottimes
« on: January 25, 2012, 10:00:58 am »
I'm surprised this thread has not seen much activity- have searched but perhaps missed something.

I'm still in the early stages of setup and I repeat rule #1 every morning ;-)

My only MD at the moment is my work notebook - an HP6710b.
CPU: Intel Coreā„¢2 Duo Processor T7500 @ 2.2Ghz
RAM: 2Gb

Before I broke it (turning on bluetooth from admin website?), I timed it at

netbooting in 500s - 8min20s. Very slow.

I don't know if the speed is to do with the fact that it may still have been setting up/installing a few things or if it is just the slow network - 10/100 hub as the bottleneck. When It's stabilised, I'll try plugging it directly into the core NIC2 with a cross-over cable to test the difference before I splash out on my Gig switch.

I would think netboot times would be of interest- do most people leave most of their MDs on all the time or do they start them as required? I guess if it's around 2min it's ok - but at 8+ min that baby had better be left running!

I tend to leave mine on.. You should see great improvements in boot times when switching to your new infrastructure. Actually since you are using a hub you have something comparable to WiFi 54Mbit... And even an upgrade to 100 Mbits switched network should yield quite some improvements - and with the relatively fast processor on your current MD Gbit network would also improve things.

Mine is an Atom MD - thus booting is quite slow!
The upside is, that even when blocking the vents in its small case it gets REALLY hot, but runs very stable (probably with decreased life span), even with full load for hours - so I can turn down the fans to minimum when idling..

BUT: I would really prefer that "Suspend to RAM" got way better implemented! I never got mine to work doing S3 - this is under 8.10, and I am switching to 10.04 very soon (2 weeks time, since I get a new server)..
Can anybody with 10.04 experience inform if S3 is working now??

Personally I do not find 2 min. booting to be OK. Something on the 20+ sec. is what I can live with, that equals the time for the projector (I don't own a TV) to get to full brightness.


Users / Re: Ubuntu TV
« on: January 19, 2012, 02:39:52 pm »
l3mce has an Internet connection using a Hayes 2400bd modem...

But through tweaking and tuning he got it up to 2460bd  8)

Users / Re: General NAS Questions
« on: January 19, 2012, 11:05:24 am »
Maybe this is a permissions issue?

No, it's not. Please remember that from the outside (where your laptop is) the whole infrastructure behind the hybrid (actually core) is considered all to be 1 IP - that is the "external" IP on your core (192.168.1.x, could be 3 or 2 or whatever in the end you assigned)... This is what NATing does for you.

You can now go 3 routes, each with pros and cons:

1. Move your wireless AP (WRT54G) to the internal network (like the Gb switch) - remember to disable DHCP on the wireless router, and remember to set its own IP to be in the 192.168.80.xx range - and connect one of the LAN ports to this network, NOT the WAN port. This will make it an Access Point, rather than a router... Downside, all you wireless stuff will now be in the domain of LMCE, and access to internet is routed through the core - so lets hope it is stable!

2. Allow the core to route traffic between the 2 subnets (the external and internal on the core) - not recommended for most use.

3. The easy and controllable one. Allow port forwarding through the core, with port mapping. You should forward i.e. port 12080 from the cores external IP (could be to the internal IP - BUT ON PORT 80!! now you can from the outside access the LMCE web interface on port 80 by typing (port 80 is given), and if this is your external IP on the core, you should get the LMCE web interface. If your type you should get to the NAS.. The downside here could be that from the INSIDE of the LMCE network the best way to communicate with the NAS is via - i.e. there is a risk of confusion...

Unless you have other specific reasons (like I do), and granted your core is running stable - I would go for option 1.

(there is actually a fourth option with 2 discrete wireless networks, where you would choose between the 2 when you log on to WiFi - this can have some major benefits and ease of use for the rest of the household and guests)


Installation issues / Re: Media Director with video capture
« on: January 18, 2012, 11:56:55 am »
Now... if I am understanding correctly, you are saying that MythTV embedded in LMCE could effectively replace my entire system? In other words I'd (THEORETICALLY) be able to plug the coax input(s) from the LNBs on my sat dish directly into a tv-tuner card in my core, plug my subscriber DSTV smart-card into some kind of card-reader and then install and set-up software to magically combine the two to send channels of my selection to any media director on the system?

That *must* be taking it a bit far, surely?

Hi James,

Sorry I missed your post :(

This is actually not "taking it far" at all - this is done all the time with various DVB inputs (DVB T, C or in your case S for sat). The only part not completely standard (and done all the time with great success) is the decoding part. It is not rocket science, but policy reasons prevent me from guiding you in these matters. Such a solution would also allow you to experience MUCH better tv quality for 2 reasons (granted you have a flat screen TV with digital input HDMI or DVI):

1. You would be enabled to watch HD channels (you don't have many, and this is actually not going to be the biggest improvement!)
2. You are going to experience a digital signal being fed directly (some post-processing is taking place, but nothing that seriously should alter the quality) to a digital panel - no conversion made. In your current setup you are (RF) modulating the digital DVB-S signal to analog, and then demodulating it back in the TV tuner (and probably then an A/D conversation if you have a flatscreen TV). These 2 (3) conversation really F*** up quality.

To experience the effect of this best, find somebody that has a DVB box that can output to a TV either via HDMI (or DVI) and via composite - or even RF) to a TV. And then switch between connections from the box to the TV. You will experience the quality improvements from analog to full digital being greater than the improvements from digital SD to digital HD!!

Let me know if you need more pointers :-)


Not to be a grumpy old man Schmich,

Well I managed to come out that way fine...
Hope there's no hard feelings - we all try to help each other, and one thing sure: Your intentions where as good as mine :-)

Hope to solve this issue, which can be followed in the other thread:,12308.msg86784.html


Users / Re: Multiswitch MythTV setup
« on: January 15, 2012, 12:53:30 pm »
I have 1x Quattro LNB (LOF: 9,75 / 10,60 GHz) connected to an EMP Centauri 9/16 Multiswitch. Standard satellite receivers receive the channels without any problem. However I am unable to get it to work for MythTV. I have checked the cable by using a standard receiver. My card is the Hauppauge HVR-4000 and I have a second one that I have tried as well.

One thing I am unsure about is how to configure the DISEqC page. I think I understand the concept that first DISEqC chooses between the two sets. Then the low vs high band and finally vertical vs horizontal. However I can only guess how that should look for the MythTV setup page.

I have no idea if anything else is the problem but I do know that I don't know what to do on this part of the setup so might as well tackle that first. I did get it to work back on 8.10 but I don't remember how, so it's highly likely that physically the cards aren't damaged.

When I search for channels I search for 10803000Khz, H, 22000, QPSK, 5/6 on ASTRA 2 (28.2) to find BBC News. So any pointers in the right direction is welcome. For starters I guess I choose a a DISEqC Switch with 2 ports right? Then do I get 2 Tone switches?


Let me try to help, I fear you have over complicated things a bit.
First (and I do not assume this is really needed, but do it anyway) look at one of your "normal" sat boxes under tuner or sat config (or whatever its called). Since your switch has room for 2 sat positions I assume that's what your have - funny (ab)use of the Torodial T90, but thats beside the point, perhaps your 2 positions are far apart or something.

On your sat box you will find (I am 99.99% sure) a config saying sat pos 1 (could be 28.2 or "the pther") at DISEqC port A, and the other sat at port B - or reverse. 2 thing worth nothing here. Ports in DISEqC are called A+B when we are talking very basic DISEqC switching (ver 1.0) - meaning in Myth you should never consider anything more complicated like tone-switches, cascaded DISEqC switches or anything like that.

The lessons learned:
1. Your regular sat boxes does not see the "advanced" multiswitch setup - they just see a simple setup with 2 universal LNBs controlled via DISEqC port A and B. So should your Myth setup look like.
2. Port A is 28.2 and Port B is the other - or the other way round...

Now in Myth you are on the right path - choose one switch (2 port) and then select if your desired sat is in port A or Port B. That's all!!!!!!!! Remember, the sat boxes does not "see" the multiswitch, they just see 2 universal LNBs.

I think that perhaps you have been confused by the fact that you have 2 switches built in to one box - one multiswitch, and one DISEqC 1.0 switch - I am sure of this since I read the manual for your particular switch  ;)

One last note for your understanding. DISEqC switches BETWEEN satellites! For 99% of us any other switching taking place is to select band and polarization on that particular sat. That switching is done with the 13/18 volts, and the 22Khz signal, and for you that does not take place in the LNB but in the multiswitch - but it does not matter for Myth where it takes place, all Myth should be configured for is one universal LNB 9.75/10.6 H/V (per DISEqC port).

- Other could learn: To get accurate answers the key is to accurately describe your problem, AND your setup :-)

Hope this brings you the rest of the way  8)


Users / Re: Ubuntu TV
« on: January 13, 2012, 09:52:22 am »
Internet TV is not a solution.

Please elaborate. Why is Internet TV not a solution to be considered? I am aware that "Internet TV" alone will not in the next 4-5 years replace broadcast via Sat, cable and air, but internet is just a protocol - that can be transmitted via sat, cable and air..


Fibres, you wouldn't happen to use a Quattro LNB combined with a multiswitch? :P I just can't get it to work even tough (after a lot of trial and error) I did manage back on 8.10. Like an idiot I never wrote it down how I did it.

Not to be a grumpy old man Schmich, but when I suggested to Matt that he, for the sake of simplicity and flattening the learning curve, should just buy Quad or Octo LNB you where the first one to shoot at me for suggesting such foolishness...

Can we, as a closure on this thread conclude that:

a. You need to learn a bit more sat basics before speaking as an expert ;-)
b. Matt should keep it simple
c. Quattro LNBs is the scalable solution, but for a novice going simple is the key to success.

And to answer your question, if your DISEqC control is working (from Myth or whatever), and your multiswitch is not defect, AND everything is connected properly (easier to mistake than you might imagine) - then it WILL work. May I suggest than you run through you physical installation once again. If the same install is working for all users with regular sat boxes, then there's only 2 options. Either a faulty port in the switch (easily tested with a working sat box normally attached to another port), or incorrect DISEqC settings in Myth. Please be aware of the distinction between committed and uncommitted switches!

Would be glad to help if still needed :-)


Pages: 1 [2] 3 4