RED Brick fails to find Ethernet Extension

[hardillb]

I've got a RED Brick and a Ethernet Extension (POE) and when I assemble then stack I can not see any networking options.

 

The Brick View doesn't list any network interfaces and ifconfig -a only list lo and a tunl0 adapter, not tf0.

 

I can't see anything obvious in the dmesg output. Any suggestions?

 

I have serveral sets of hardware and I can't get any of them to work.

[hardillb]

Just to add some more info.

 

• Master Brick + the Ethernet Extensions works fine
   
  
• RED Brick + Ethernet Extension no sign of any network interface
  
• RED Brick + Master Brick (Ambient + Motion) brickv doesn't show the master brick when plugged into the RED Brick
  
• RED Brick + Master Brick + Ethernet + Master brick. brickv shows only the RED Brick when usb attached to RED Brick, When connected to master brick it shows ambient light, motion and ethernet (not RED Brick)
  

 

RED Brick is running v1.8 card image

 

Components:

 

RED Brick v1.0 (fw 2.0.2)

Ethernet Extension v1.1

Master Brick v2.1 (fw 2.3.4)

Ambient Light v2.0

Motion Detection v1.0

[borg]

When you use the RED Brick + Ethernet Extension, do you have the RED Brick at the bottom?

 

If you use a fresh image and the Ethernet Extension works on the Master Brick and the stack connectors of the RED Brick are OK (no dirt on the contacts or similar) this must be a defective RED Brick, i think. I don't see what else could be the problem here.

[hardillb]

A totally fresh SD card image and stacking with the RED Brick on the bottom seams to be working now.

 

Does stack order matter?

 

Also I don't seam to be able to get brickv to bring up the network interface. When I hit the "connect" button I get the following error on the console:

 

Traceback (most recent call last):

  File "/opt/shared/projects/tyyrell/brickv-2.3.4/src/brickv/plugin_system/plugins/red/red_tab_settings_network.py", line 1054, in slot_network_connect_clicked

    iname_previous = self.network_all_data['manager_settings'].get('Settings', 'wired_interface', '')

TypeError: get() takes exactly 3 arguments (4 given)

 

I'm using a src build of brickv on Fedora 22.

 

I can bring the interface up manually from the command line.

 

[Nic]

Does stack order matter?

Of course, the 1st Master- or RED-Brick stacked as the lowermost brick is always responsible as the "communicator" to the extension.

[photron]

hardillb, that traceback is unexpected.

 

It seems that self.network_all_data['manager_settings'] has a wrong type.

 

What Python version are you using?

 

Could you add

 

print self.network_all_data['manager_settings']

 

in front of the

 

iname_previous = self.network_all_data['manager_settings'].get('Settings', 'wired_interface', '')

 

line in red_tab_settings_network.py, then restart Brick Viewer and click the connect button again. It should print something like this:

 

<ConfigParser.ConfigParser instance at 0x7fdaaf8fcdd0>

[hardillb]

Hi,

 

Python 2.7.10

 

And I got the following after adding the line:

 

<configparser.ConfigParser object at 0x7f5340581750>

Traceback (most recent call last):

  File "/opt/shared/projects/tyyrell/brickv-2.3.4/src/brickv/plugin_system/plugins/red/red_tab_settings_network.py", line 1056, in slot_network_connect_clicked

    iname_previous = self.network_all_data['manager_settings'].get('Settings', 'wired_interface', '')

TypeError: get() takes exactly 3 arguments (4 given)

 

 

[photron]

Strange, something funny is going on there.

 

Please try to replace this

 

try:
    import configparser
except:
    import ConfigParser as configparser # Python 2 fallback

 

in

 

brickv-2.3.4/src/brickv/plugin_system/plugins/red/config_parser.py

 

with this

 

try:
    import ConfigParser as configparser
except:
    import configparser # Python 3

[photron]

No, forget about that. Replace the whole brickv-2.3.4/src/brickv/plugin_system/plugins/red/config_parser.py file with the attached version.

config_parser.py

[hardillb]

That seams to have worked.

 

Thanks

[photron]

Okay, it seems that we were using the config parser is a wrong way. I wonder why this worked before.

 

Anyway, this change in config_parser.py will be part of the next brickv version. Thanks for reporting this problem.