You are not logged in.
Running fully updated system on IP35 Pro motherboard. IDE drive is the boot drive and I also have a SSD connected to the SATA controller. The SSD does not show up because the "ahci" module is not loaded.
I have regenerated the initramfs many times with no luck (mkinitcpio -p linux). Then I went and edited mkinitcpio.conf and have:
MODULES=(libahci ahci)
...
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)Regenerated initramfs many times again. STILL doesn't load the module at boot!
"modprobe ahci" works.
WTF am I doing wrong?!
Edit:
Solution: There was a blacklist entry specifically for the AHCI module (I have no idea why) and /etc/modprobe.d had been moved to a different (user's) directory (!).
Last edited by oz (2018-11-05 18:54:22)
Offline
What error messages is the issue causing? `modprobe ahci` is that being executed from the rescue shell? Before that does lsmod show ahci is absent and after that it is loaded?
If you have some persistent storage available from the rescue shell can you dump the output of dmesg to it, then post it when the system has internet access.
Offline
No error messages when booting off IDE. Just the SATA drive isn't there until I manually load the module.
I tried moving the install to the SSD. Same problem except worse because it can't boot (unable to find the root UUID). Again, I can modprobe from the rootfs emergency shell which means the AHCI module is in the initramfs but it absolutely refuses to load the module automatically during boot. ?!
There is nothing in dmesg about the SATA controller (no errors either) until I manually load the AHCI module, then it detects everything normally.
Maybe some sort of bug in Arch Linux itself? When I installed the system there was nothing connected to the SATA port, just an IDE drive. Now later I'm adding a SATA drive and trying to bring the AHCI system online. AHCI is such a basic thing, it would normally be loaded at the very beginning on such systems so most people would never be in such a situation
Last edited by oz (2018-11-05 18:01:36)
Offline
Please provide the output of `dmesg` and `lspci -nnk`
Edit:
AHCI would normally be loaded by matching one of its aliases against a VID:PID of one of the system's PCI devices.
Last edited by loqs (2018-11-05 18:19:12)
Offline
You have to understand that posting dmesg is against my companies policies due to security issues. I can not post information that could identify a specific machine; serial numbers, UUID's, that type of stuff. Somewhere there is a dmesg scrubbing script but I don't think it ever worked correctly.vvlspci should be OK but I have to get approval.
This is the relevant controller:
00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02)
Subsystem: ABIT Computer Corp. 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [147b:1083]
Kernel modules: ahciHowever, the system is fully booted and ahci module is *not* loaded even though it shows it right there. The drive does not exist. modprobe manually fixes everything. There are no errors in the dmesg output.
Edit:
I'm making some progress. It turns out that this machine has been heavily hacked apart for all sorts of uses. Something weird has probably been done to it which is not a problem with Arch.
Last edited by oz (2018-11-05 18:42:33)
Offline
Should match
alias: pci:v00008086d00002922sv*sd*bc*sc*i*Offline
OK. I found the problem. /etc/modprobe.d had been changed and in that other directory there was a blacklist entry for the AHCI modules (WHY?!).
Anyway, it's working now.
Offline