Bug#562594: Use modalias to detect modules when driver does not register

2009-12-28 Thread Jérémy Bobbio
tags 562594 + patch thanks Hi! This problem looks similar to the one I had while trying to use a daily build image on a PowerEdge R410. The network interfaces on these machines are supported by the bnx2 module, but when no firmware is available, the driver does not register itself for the device

Bug#562594: Use modalias to detect modules when driver does not register

2009-12-28 Thread Frans Pop
On Monday 28 December 2009, Jérémy Bobbio wrote: > This problem looks similar to the one I had while trying to use a daily > build image on a PowerEdge R410. > > The network interfaces on these machines are supported by the bnx2 > module, but when no firmware is available, the driver does not regis

Bug#562594: Use modalias to detect modules when driver does not register

2009-12-28 Thread Jérémy Bobbio
On Mon, 28 Dec 2009 15:17:49 +0100 Frans Pop wrote: > I think the patch needs an added test that modalias exists, something > like: elif [ -e $devpath/modalias ]; then > > And that long line could do with a split to the next line after the > pipe. The "|| true" is probably not needed as the sed s

Bug#562594: Use modalias to detect modules when driver does not register

2009-12-28 Thread Jurij Smakov
On Mon, Dec 28, 2009 at 03:17:49PM +0100, Frans Pop wrote: > On Monday 28 December 2009, Jérémy Bobbio wrote: > > This problem looks similar to the one I had while trying to use a daily > > build image on a PowerEdge R410. > > > > The network interfaces on these machines are supported by the bnx2 >

Bug#562594: Use modalias to detect modules when driver does not register

2009-12-29 Thread Frans Pop
On Tuesday 29 December 2009, Jurij Smakov wrote: > I see that modprobe has --resolve-alias flag which prints out the > module(s) matching an alias, which renders the whole sed concoction > unnecessary. I think we should keep Jérémy's solution. If --resolve-alias can return multiple modules that s