You are not logged in.
nforce3 chipset, libata & sata_nv modules
The 'arch' kernel on the 0.7.1 isos results in Kernel Panic after attempting to load a bunch of scsi modules I don't need
The 'arch-noscsi' kernel boots fine, but doesn't detect my single hard drive, an SATA. Modprobing libata & sata_nv will let me find the device via /proc, but unable to access it via a /dev node.
The Minimax livecd is flakey at best on my system, and not reliable enough to try a full install.
I tried to follow the wiki docs on installing arch linux from an exising linux partition, which worked, but again none of the arch kernels will boot due to kernel panic trying to load a ton of scsi modules. I attempted to blacklist the modules, but it seems the kernel insists on loading them.
Why is it impossible for Arch to provide a SATA non-SCSI kernel such as the one slackware has been providing for some time now?
Any ideas or methods to try other than what I've already mentioned?
Offline
there should be only a single standard kernel26 now for scsi and non-scsi, they got rid of the distinction a while ago, I am pretty sure it was before 7.1.
I have a SATA hard drive on an nforce3, it works fine for me.
Offline
with tpowa's help via #archlinux I was able to get up & running
I used a rescue CD provided by tpowa to boot into the system, then by editing /etc/mkinitrd.conf and running 'mkinitrd auto -show' a slimmed down initrd.img was created that didn't bomb me with scsi modules. after editing grub all is well.
tpowa's disc is kernel 2.6.17 with more advanced/compatible (in my case) hardware detection boot disc. You need to have an arch installation to boot to for it to be any use. Hopefully this makes it into 0.8 discs, as I understand it is in testing right now.
I've mirrored the ISO (with permission), here
append a proper 'root=' option in addition to the onscreen instructions at the boot prompt, where root=/dev/<arch_partition>
Offline