mythtv and jaunty

[Bruce Labitt]

Neil Joseph Schelly wrote:
> On Friday 01 May 2009 10:02:59 pm Bruce Labitt wrote:
>   
>>> Your problem appears to be either:
>>> A. They aren't asking for DHCP.
>>> B. The switch isn't working and those packets aren't getting to your Myth
>>> box. C. The firewall isn't as disabled as you think it is.
>>>       
>
>   
>> Isn't that off?  Notice that there is no reference to either eth0 or
>> eth1...
>>     
>
> Yes, it's off. That eliminates A.
>
>   
>> Could be that the switch is not working.  I will bypass it and only
>> connect one of the tuners.
>>     
>
> I assume you connected the tuner directly with a crossover cable here?  Were 
> link lights as you'd expect when you plugged things in?  Do you have an 
> alternate switch you could use?
>
>   
>> I did remove power to one of the hdhr's for a minute and still did not
>> see any activity on tcpdump.
>>     
>
> Failing the switch/cabling issues above, are you sure these devices work?  Are 
> you sure they will query out for DHCP?  A quick Google search does suggest 
> they can be configured for static IPs, but I'm not too familiar with them.  
> Can they be reset to factory defaults?
> -N
>
>
>   
I am sure the tuners did work.  I had myth running with them on FC6.  
They were configured with DHCP.  They have not been reflashed, so I 
would expect them to still be configured with DHCP.

I took the cover of the computer and watched the boot.  On power up the 
ethernet link light is on.  During the boot process the link light goes 
off.  My dmesg is kind of confusing...

$ dmesg | grep eth
[    1.117959] Driver 'sd' needs updating - please use bus_type methods
[    1.117966] Driver 'sr' needs updating - please use bus_type methods
[    4.018867] eth0: RTL8169sb/8110sb at 0xffffc20000072800, 
00:0e:2e:d3:75:fa, XID 10000000 IRQ 22
[    4.194643] 0000:00:19.0: eth1: (PCI Express:2.5GB/s:Width x1) 
00:19:d1:55:47:1a
[    4.194646] 0000:00:19.0: eth1: Intel(R) PRO/1000 Network Connection
[    4.194674] 0000:00:19.0: eth1: MAC: 5, PHY: 6, PBA No: ffffff-0ff
[    9.899743] udev: renamed network interface eth0 to eth1
[    9.941856] udev: renamed network interface eth1_rename to eth0
[   13.012037] r8169: eth1: link down
[   13.012335] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   14.208505] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.778263] 0000:00:19.0: eth0: Link is Up 1000 Mbps Full Duplex, 
Flow Control: RX/TX
[   16.778717] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   27.500037] eth0: no IPv6 routers present
[  581.234773] r8169: eth1: link up
[  581.235180] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[  581.679437] r8169: eth1: link down
[  588.006968] r8169: eth1: link up
[  588.366237] r8169: eth1: link down
[  591.142011] r8169: eth1: link up
[  591.493417] r8169: eth1: link down
[  591.768007] eth1: no IPv6 routers present
[  625.077753] r8169: eth1: link up
[  625.564191] r8169: eth1: link down
[  641.116473] r8169: eth1: link up
[  641.577355] r8169: eth1: link down
<snip>
[  785.811102] r8169: eth1: link down
[  788.234852] r8169: eth1: link up
[  789.053659] r8169: eth1: link down
[  791.484781] r8169: eth1: link up
[  792.799372] r8169: eth1: link down
[  797.334224] r8169: eth1: link up
[  800.348486] r8169: eth1: link down
[  805.968040] r8169: eth1: link up

Why on earth would I be getting eth1 cycling on and off?  Now the link 
light is on and I can ping the tuners.  (192.168.3.2 & 3)

$ hdhomerun_config discover
hdhomerun device 101084DE found at 192.168.3.3
hdhomerun device 10117273 found at 192.168.3.2

Is it possible the ethernet card is temperature sensitive?  It didn't 
used to be...

-Bruce