On Thu, Nov 08, 2007 at 02:27:03PM -0800, Roland Dreier wrote: > > Roland, thanks for your help. On modprobing this module simply nothing > does > > happen, absolutely nothing in dmesg. > > Do you know if mlx4_core was already loaded? It probably would be > loaded by driver autoloading based on matching the PCI device. If so > then mlx4_ib wouldn't print anything further, but IB stuff should > work, eg you should see a /sys/class/infiniband/mlx4_0 directory, etc. >
Ah, mlx4_core was already loaded. After unloading it and loading mlx4_ib again I also get kernel messages. [10010.988484] mlx4_core: Mellanox ConnectX core driver v0.01 (May 1, 2007) [10010.988490] mlx4_core: Initializing 0000:09:00.0 [10010.988532] ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 18 (level, low) -> IRQ 18 [10010.988555] PCI: Setting latency timer of device 0000:09:00.0 to 64 At least defining the ib0 interface works now, too. Presently can't further test it now, since its connected to a flaky mts2400 switch, which needs a reset. > > Can you tell me where the mlx4 ids are defined? > > drivers/net/mlx4/main.c Hmm, I already grepped there. Will look tomorrow again. Btw, does the mlx4 driver in 2.6.22 work reliable or have their been major issues fixed in 2.6.23? Thanks a lot for your help, Bernd _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
