[arch-dev-public] [arch-general] [signoff] kernel26 2.6.30-3

[Thomas Bächler]

Tobias Powalowski schrieb:
> Could it be that the new netcfg scripts are a bit buggy here, my custom bridge 
> script fails too with the same error.
> Digging a bit in netcfg code shows it uses ip link | grep UP which is not 
> working here it says UNKNOWN, maybe James can enlighten us more.

My guess as well, the link detection might be broken. netcfg should 
really have an option to force enabling the interface even if link 
detection fails.

However, when no link is detected, some ethernet drivers disable TX 
completely. When it was first introduced for my old dmfe card, it was 
broken and I could receive packets, but nothing was ever transmitted - 
after my bug report they reverted the changes and reintroduced a working 
link detection in the next version. My point is, even if you fix netcfg, 
Eric's driver might be just as broken so he still has to reconnect the 
cable to make it work.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://www.archlinux.org/pipermail/arch-dev-public/attachments/20090615/8d79fd75/attachment.pgp>