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 - internix

Pages: [1]
I will do that once I find out how to modify the image in a persistent way. Right now I found I have to re-edit whenever I regenerate the MD.

They're crappy indeed, but the trick with udev worked. I made a file in /etc/udev/rules.d with the name "ethernet.rules". In it I have the following two lines:

KERNEL=="eth*", SYSFS{address}=="00:50:da:4f:11:51", NAME="eth0"
KERNEL=="eth*", SYSFS{address}!="00:50:da:4f:11:51", NAME="eth1"

This works because I only have two ethernet interfaces in the machine. One, eth0, is always correctly identified. The other has a mac address which is different from the first one and will be called eth1.

I rebooted and lo and behold the whole house had internet access through the core. I was able to install orbiters on my other PC's and control everything connected to the core. Tomorrow I'll try remote booting a MD.

Guys, thanx a lot for the quick assistance. It saved a bundle of time. Once I'm done with the setup I will create a description of the whole process in the wiki.

Thnx for your good advice. I just tried the iftab route. As it turns out, the driver forcedeth, which handles my eth port, seems to have a bug in getting the mac address from the device. Instead it returns a random address of its own making. This defeats keeping the mac addresses in iftab. I'll try the udev route next and report back.

I've finally  taken the plunge to go for a dedicated core. I set it up with the 64-bit DVD on an Intel machine as a hybrid so it is easier to debug. Later on I will switch off the MD functions. Seemed to work fine. Until I wanted to hook it up to the rest of the network. I have an NVIDIA chipset on my mainboard with an integrated ethernet controller. I added an additional pci card for the second ethernet  port. The added interface is 100Mb so I connected this to my router and internet. This works fine. The integrated ethernet port is 1Gb and should interface to the rest of my network.

When I go into KDE and have look at the ethX ports I see the eth0 ports as expected. Instead of an eth1 port I saw at first an eth2 port, which was disabled. I could enable it and send traffic over it. Offcourse there were no DHCP services as de DHCPD expected to work with the eth1 port. The funny thing is I can configure everything around this eth2 port and I did, but when I rebooted the eth2 interface was lost in the woods. Instead I had now an eth3 port. At every reboot the number goes up by one.

Does anyone of you an idea were to look for a solution?

Thnx in advance


Users / Re: SOLUTION: TT1500 (budget_ci) conflicted with snd_aw2 driver
« on: October 29, 2008, 06:20:52 pm »
Thnx! This was the cure for my problem with a KNC1-C TV card also. After installing I was able to configure the card in MythTV but after a reboot I lost sound and the card wouldn't start up in MythTV. MythTV reported that all resources for the requested program were in use. Investigation of the card in MythTV Setup showed that the card was not responding anymore. After reading this post I checked the installed drivers with lspci and found the snd_aw2 driver was loaded before the budget_av driver blocking it from working as the post spelled out.

Again thanks a lot for this.

Best regards,


Users / Re: Microsoft is watching LinuxMCE too...
« on: October 22, 2007, 11:18:01 pm »
In the mean time some things have changed at Microsoft. Using the XBOX360 as an extender it is now possible to watch all movies stored on the Homeserver. You'll have to go through the MCE though. The XBOX360 is capable of showing movies off the Homeserver itself, but oddly enough it doesn't support the DVR-MS format. Only MPEG's can be shown.

The LMCE solution is much more powerful, if only getting it to work would be somewhat easier:--)




I also have the problem with the Bluetooth. I tried 0000 and 1234. Both didn't work.

Installation issues / Re: MCEUSB2 not working when connected
« on: September 12, 2007, 07:14:09 pm »
Thanks for all the replies. It is working for me now after copying the misc directory from the /lib/modules/2.6.20-15-generic directory to the /lib/modules/2.6.20-16-generic directory since it was missing from the latter. The other parts were installed already since they don't depend on the kernel version. After running depmod -ae in order to build a new dependency tree of the modules in the new kernel and running modprobe lirc_MCEUSB2  the MCEUSB2 module loaded and the machine responded to the remote.

Thanks for the help!

Installation issues / Re: MCEUSB2 not working when connected
« on: September 12, 2007, 05:31:38 pm »
No explicit update was done. The upgrade of the kernel was the side effect of installing the native NVidia driver as done by the LMCE install program

Installation issues / Problems getting a KNC1 DVB-S working in MythTV
« on: September 12, 2007, 12:39:19 pm »
I'm trying to get a KNC1 DVB-S card working in LMCE. After inserting the card the drivers get installed (budget_av). Using dvb-apps from the site I was able to produce a channels.conf file with the scan utility. This shows that the driver is working and that reception from the satellite is working.

I next setup the card in MythTV, defined sources and so on. Then using the channel editor I tried to do a channel scan by importing the channels.conf file. MythTV shows a very quick scan and finds no channels.

Anybody any idea?



Installation issues / MCEUSB2 not working when connected
« on: September 12, 2007, 12:32:47 pm »
I used the 2 CD install method to get LMCE going. It all worked flawlessly. Then I decided to connect a MCEUSB2 infrared controller using the Microsoft remote. When I connected the controller some activity was going on to install the new software for it and I received a notification that MCEUSB2 now was installed. It didn't however.

Diving into the modules directory, the MCEUSB2 module wasn't installed in the correct version of the OS. With the Kubunto live CD kernel 2.6.15 is installed. During the installation of LMCE a newer version (2.6.16) is installed. The MCEUSB2 module is present in the modules directory of the 2.6.15 directory but is not present in the modules directory of the 2.6.15 directory. copying the MCEUSB2 module to the 2.6.15 directory fixed the problem in my case. After a reload I was able to use the remote to control my Mediacenter.



Installation issues / Re: Can't start the AV Wizard!
« on: September 12, 2007, 12:25:00 pm »
I have the same problems with the screen going blank, but there is an easy work-around. After hitting ESC (one time is enough) LCME comes up and can be configured (in 640x480). When LMCE is configured just go into webadmin and change the resolution of the MD to your liking. It may also work to use the keys 6 to 0 on the keyboard after the beeps to change the resolution.

Pages: [1]