> Add support for legacy boards, ensuring to enable the driver for > those boards only when 'hpsa_allow_any' is set. Applied this patch, made sure I had compiled in hpsa and not cciss to avoid any variables from initramfs, and still I get this: [ 4.015080] hpsa 0000:00:04.0: unrecognized board ID: 0x40800e11, ignoring. [ 4.098473] hpsa 0000:00:04.0: Board ID not found Boot command line was "root=/dev/sda1 console=ttyS0,9600 ro hpsa_allow_any=1" - seems correct. By looking at the code, I should see "unsupported board ID:" and it should work, but I see "unrecognized board ID:" and it does not work. Hmm, trying hpsa.hpsa_allow_any=1. Much better: [ 3.891531] hpsa 0000:00:04.0: unsupported board ID: 0x40800e11 [ 3.962367] hpsa 0000:00:04.0: unsupported board ID: 0x40800e11 [ 4.033493] hpsa 0000:00:04.0: Controller reports max supported commands of 0 Using 16 instead. Ensure that firmware is up to date. [ 4.175134] hpsa 0000:00:04.0: Physical aborts not supported [ 4.242931] hpsa 0000:00:04.0: Logical aborts not supported [ 4.309594] hpsa 0000:00:04.0: HP SSD Smart Path aborts not supported [ 4.460889] hpsa 0000:00:04.0: Controller reports max supported commands of 0 Using 16 instead. Ensure that firmware is up to date. [ 4.584679] scsi host0: hpsa [ 4.587842] hpsa 0000:00:04.0: report luns requested format 2, got 0 [ 4.613215] hpsa 0000:00:04.0: scsi 0:0:0:0: masked Direct-Access COMPAQ BD03685A24 PHYS DRV SSDSmartPathCap- En- Exp=0 [ 4.613219] hpsa 0000:00:04.0: C0:B1:T0:L0 Volume status is not available through vital product data pages. [ 4.613224] hpsa 0000:00:04.0: scsi 0:1:0:0: offline Direct-Access COMPAQ LOGICAL VOLUME RAID-1(+0) SSDSmartPathCap- En- Exp=1 [ 4.613229] hpsa 0000:00:04.0: scsi 0:3:0:0: added RAID COMPAQ Smart Array 5i controller SSDSmartPathCap- En- Exp=1 [ 6.187725] scsi 0:3:0:0: RAID COMPAQ Smart Array 5i 2.62 PQ: 0 ANSI: 0 [...] [ 6.726872] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6 [ 6.814364] Please append a correct "root=" boot option; here are the available partitions: [ 6.914403] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Controller is detected, there is something behind it but no sda is detected and no bootup. What next? And, for readability, we should use something like "Using unsupported board ID", not plain "unsupported board ID" - the last one leaves assumption that it will not work, although it should. -- Meelis Roos (mroos@xxxxxxxx)
