On Thu, May 31, 2012 at 10:53 +0200, Paul de Weerd wrote:
> I've recently bought a new Sony laptop, VPCZ23C5E. Some things on
> this machine work fine (sound, suspend, wired network), some things
> don't (X, resume, wireless). One of the problems I have is that
> -current doesn't find any disks behind the pciide(4), which is a
> "Intel 82081HBM RAID". sthen@ suggested I revert 1.163 of
> dev/pci/ahci.c, which was the clue I needed to getting things working.
>
> I built a kernel with the following diff applied:
>
> Index: ahci.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/ahci.c,v
> retrieving revision 1.188
> diff -u -r1.188 ahci.c
> --- ahci.c 5 May 2012 10:10:12 -0000 1.188
> +++ ahci.c 31 May 2012 08:19:39 -0000
> @@ -504,6 +504,8 @@
> NULL, ahci_intel_attach },
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801HBM_AHCI,
> NULL, ahci_intel_attach },
> + { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801HBM_RAID,
> + NULL, ahci_intel_attach },
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801I_AHCI_1,
> NULL, ahci_intel_attach },
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801I_AHCI_2,
>
> Now, the controller attaches as ahci(4) and disks are found behind it.
> Here's the relevant portion of the diff between the before and after
> dmesg:
>
> -pciide0 at pci0 dev 31 function 2 "Intel 82081HBM RAID" rev 0x04: DMA,
> channel 0 wired to native-PCI, channel 1 wired to native-PCI
> -pciide0: using apic 0 int 22 for native-PCI interrupt
> +ahci0 at pci0 dev 31 function 2 "Intel 82081HBM RAID" rev 0x04: msi, AHCI 1.3
> +scsibus0 at ahci0: 32 targets
> +sd0 at scsibus0 targ 0 lun 0: <ATA, SAMSUNG MZRPC128, CXM0> SCSI3 0/direct
> fixed naa.50000f0043584d30
> +sd0: 61057MB, 512 bytes/sector, 125045424 sectors, thin
> +sd1 at scsibus0 targ 1 lun 0: <ATA, SAMSUNG MZRPC128, CXM0> SCSI3 0/direct
> fixed naa.50000f0043584d30
> +sd1: 61057MB, 512 bytes/sector, 125045424 sectors, thin
>
> The BIOS on this machine does not offer any settings for configuring
> the mode the controller is set to, nor does the "RAID controller BIOS"
> (which I used to move from 'raid-0' to no raid) allow me to set it as
> a 'regular' AHCI controller.
>
> So, I'd very much like to see the above diff (or something like it) go
> in, but it basically undoes the 1.163 revision which wasn't commited
> without a reason of course. Any ideas what the best solution would be
> here ?
>
> Included below are dmesgs from the non-working snapshot (April 24th
> snap), which was installed to a umass sd; the dmesg from the new
> kernel (with the diff above applied); pcidump -vx output and sysctl hw
> output.
>
> Paul 'WEiRD' de Weerd
>
>
well, this is indeed an ID of a mobile SATA controller in the RAID mode.
the only reason to undo that revision just for 82801HBM_RAID would be
because it's a mobile version and laptop bioses are too crippled to allow
users to change the mode themselves.
