Well, being an extreamly new user of this software and new to the MB I'm using, this one took me for a ride last night.

What is the recomended way of dealing with a Firewire port on eth0?

During the install I kept running into trouble with my network... after a while I discovered that eth0 was atually the firewire port and eth1 was the NIC. KnoppMyth didn't allow me to select the eth interface to use, but simply assumed eth0 (at least I think thats what was going on).

I finally got this working be removing the startup of eth0 so it simply doesn't get set up (and likely damaged the install slightly in the process of mucking about).

I don't know if this is really of interest to anyone, but I for one would love it if I could select the ethernet interface I wanted MythTV to use during the auto install, if more than one were found.

Other than that, I actually had fun installing it! Good job!

Yep, been there.

For a while, this fix seemed to work:

http://lists.debian.org/debian-amd64/20 ... 00213.html

Namely, creating a file at /etc/modprobe.conf and forcing eth0 to be Ethernet, and moving eth1394 to eth1. Like I said, it seemed to work, but then I'd still get times when I'd boot the machine and the network wasn't working.

I think that one of the install scripts is supposed to do a "rmmod eth1394" but every time I try to do that manually as root nothing seems to happen and I can't get the Xterm window to respond any more.

Ultimately I gave up and just disabled my Firewire in my Shuttle's BIOS.

I had the same problem that was solved by commenting out ohci1394 in /etc/modules , and rerunning netcardconfig . By commenting out the ohci1394 the module will not load and your normal nic card will become eth0.

I used pure brute force. I may want to add some kind of firewire device later, but NOT a firewire LAN connection, since I've got far too many other viable networking options. So I simply deleted the eth1394 module from /lib/modules/2.6.9-chw-4/kernel/drivers/ieee1394/ and thus put a permanent end to it's reign of terror.

which release is this on?

i want to migrate my current backend from suse 9.2 to knoppmyth r5a10 and i use .17 with firewire to my cablebox as the capture source...

don't know how that can be done if knoppmyth assumed firewire is an ethernet port??

odd

KnoppMyth doesn't assume firewire is an ethernet port. You can use firewire for an ethernet port. Since firewire is detected, the module is loaded.

_________________
cesman

When the source is open, the possibilities are endless!

isn't the ohci1394 module that people are disabling required as part of the firewire interface? Is there another script/process to stop that will disable setting it up as ethernet vs removing the firewire interface drivers?

Yes. If folks simply let the configuration process do it's thing, they wouldn't see this problem. The scripts rmmod eth1394 before running netcardconfig. The only systems that this doesn't seem to work with are some nvidia chipset based boards (only 2 people have reported this issue).

_________________
cesman

When the source is open, the possibilities are endless!

thanks.. i use firewire and i want to rebuild my backend from suse to knoppmyth (cleaner) and didn't want to risk loosing my firewire connection to the cablebox

If you read my post you'd see that while my solution used lethal force it was a surgical strike. I very specifically removed only the eth1394 driver thus disabling only it's use for an ethernet interface. I like Cecil's solution better, but if that doesn't work for whatever reason you have an option.

I had this, so it's now 3 people

I've got an Nforce2 motherboard (Abit NF7-S)

But I just disabled the firewire port in the bios, as I doubt I'm gonna use it.

Matt

I had it too, as mentioned along with some other issues in my thread here.

As far as I know, I did let the configuration process 'do it's thing' - however, I think the first time it booted was one of those times when the firewire ethernet interface was assigned eth0 so maybe it didn't then let the module be unloaded because it was in use. Either that or the fiddling with the security settings that needed to be done before it would allow the script to su to root (also mentioned in the above thread) mean that the script didn't run cleanly first time.

I have an Asus Pundit (not Pundit-R) which doesn't have a single nvidia device in it. Instead it's an SiS firewire controller and chipset.

Steve.

Fresh install of R5A12 on an VIA EPIA M10000 also exhibits this problem.
I think netcardconfig succeeds, but the next reboot it will try DHCP somewhere late in the scripts, which uses eth0 and fails.

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

I've had the 1394 eth0 problem as well as the ADD lines on ivtv which would cause the forcedeth driver to not load and thus the box would end up orphaned... instead of killing the 1394 drivers, I just added an eth1 setup... which works around the problem...

Hey - Simple fix for this issue:

edit /etc/modules
move forcedeth above the ieee1394 line.

everything still works, just the ethernet is eth0 instead of eth1...