Hi All, I've got this 'ips' driver from the SUNWips_nv pkg on the OpenSolaris ServeRAID project page. I'm trying to get it to work with my ServeRAID 7K card in an IBM x346.
The project page states that the community is working on ServeRAID 4x,5x, and 6x support while Sun is working on ServeRAID 7x and 8x support, but the page isn't clear as to whether or not the Community and Sun project teams are working in the same source code, or whether or not the downloadable pkg contains the work of both teams, or just the community work. To compound the confusion, My ServeRAID 7K card actually has the same PCI ID (pci9005,250) as the ServeRAID 6M, and that is one of the PCI ID's this package adds to /etc/driver_aliases. I'm not naive enough to expect it to work just because the PCI ID's match, but it does see to be worth a try. It's not working, but I can't tell if I've hit the end of the road or if there is more I can do? When the kernel boots, it prints these messages: > SunOS Release 5.11 Version snv_91 32-bit > Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: Last shutdown is later than time on time-of-day chip; check date. > Configuring /dev > WARNING: mutex_init: d1089552 is not 4 byte aligned; caller > ips_attach+3ad in module ips. This is unsupported and may cause a panic. > Please report this to the kernel module supplier. > WARNING: mutex_init: d108955a is not 4 byte aligned; caller > ips_attach+3de in module ips. This is unsupported and may cause a panic. > Please report this to the kernel module supplier. > WARNING: mutex_init: d108965e is not 4 byte aligned; caller > ips_attach+40f in module ips. This is unsupported and may cause a panic. > Please report this to the kernel module supplier. Are these a sign of real problems? Is sNV_b91 too new for this driver? Since this is a network boot to do an install I eventually see the follwoing menu. I select 'Single user shell' from the following menu, and the system basically hangs itself up, and needs to be power cycled. > 1. Solaris Interactive (default) > 2. Custom JumpStart > 3. Solaris Interactive Text (Desktop session) > 4. Solaris Interactive Text (Console session) > 5. Apply driver updates > 6. Single user shell > > Enter the number of your choice. > Selected: 6 > > Single user shell > > Searching for installed OS instances... > I've tried #1 also and it hangs on there too. I've booted the kernel with -kd, and dropped to the debugger. Running '::ptree' shows that it's hung up in either 'install-discovery' (Menu choice #1) or 'install-recovery' (Choice #6). I assume it's trying to search for disks. Any ideas? Is this driver just not ready yet? -Kyle _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
