How much memory does your system have?
Best guess in the 64 bit case is that the physical memory the kernel is
doing DMA to isn't within the range of the card. You might be able to
test this by booting with the max_addr=4G parameter in the 64 bit case.
If it is, we'll have to get the DMA mask for this thing set up
correctly.
James
James,
It's got 8Gig.
I'll try your suggestion tonight, when I get home.
Cheers,
Eddie
OK, adding addappend = " max_addr=4G" to my lilo.conf made no
difference. It still booted with all 8G. :(
But, changing it to addappend = " mem=4G" seemed to do the trick.
And, your guess might be correct. I now see the correct messages for
the MegaRAID:
scsi 4:4:0:0: Direct-Access MegaRAID LD 0 RAID5 1430G N661 PQ: 0 ANSI: 2
sd 4:4:0:0: [sda] 2930307072 512-byte hardware sectors: (1.50 TB/1.36 TiB)
sd 4:4:0:0: [sda] Write Protect is off
sd 4:4:0:0: [sda] Mode Sense: 00 00 00 00
sd 4:4:0:0: [sda] Asking for cache data failed
sd 4:4:0:0: [sda] Assuming drive cache: write through
sd 4:4:0:0: [sda] 2930307072 512-byte hardware sectors: (1.50 TB/1.36 TiB)
sd 4:4:0:0: [sda] Write Protect is off
sd 4:4:0:0: [sda] Mode Sense: 00 00 00 00
sd 4:4:0:0: [sda] Asking for cache data failed
sd 4:4:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 4:4:0:0: [sda] Attached SCSI disk
sd 4:4:0:0: Attached scsi generic sg1 type 0
Cheers,
Eddie
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
