On Thu, Mar 29, 2007 at 11:43:14PM -0400, Bob Miller wrote: > Please help. > > I've been trying to get a CLFS system built and installed for almost a week > now. By myself (well, with google, the clfs-support archives, and the LFS > hints by my side) I've managed to struggle through creating the entire > temporary system. I've been stuck on this VFS error for about two days now, > and I'm at my wits end. > > I'm installing CLFS SVN 03-24(?)-2007 from the 6.2.5 LiveCD for > x86_64-pure64. I've followed the instructions to the letter with two > exceptions: I'm using grub 0.97 (32 bit, custom built from LiveCD) as my > kernel, and my root partition is ext3. (Reason: 1) LILO refused to load > into my bootsector. 2) I can't rermember why I originally wanted to stick > with ext3, but now I don't want to wipe all my work AGAIN and start from > scratch.)
Those shouldn't cause any problems (the book says it's ok to use grub if it's already installed), and you should definitely stick with ext3. > These are the messages I get before the panic: > > scsi0: sata-nv > ata1: SATA Link disabled //or empty or inactive or something similar > scsi1: sata-nv > ata2: SATA Link up at 3 Gbps // and a little more I didn't write down > ata2.00: dev 0 multi count 16 > ata2.00: qc timeout > ata2.00: failed to set xfer mode // forgot to write the code, maybe 0x07? > ata2.00: limiting speed to UMDA/66 //earlier got a message about speed > being UDMA/100 > ata2: failed to recover some devices, retrying in 5 secs > > Messages repeat 2 more times before the kernel goes on for awhile before the > final panic. I think this might be part of the problem, but then again I > have around 8 SATA connectors on my motherboard, so it could also just be a > complete device probe. > It looks as if sata-nv is claiming the scsi0 and scsi1 adaptors, there is nothing connected to scsi0, and the drive on scsi1 disappears almost immediately. The plural 'devices' is because the message is for all of ATA - SATA can only have one device per conroller/socket, at this point the kernel has only enumerated the first two SATA controllers that it knows about (if you have 8, they might not all be sata-nv). I suspect a bad .config, or perhaps a bad cable (power or data) that has decided to fail (or come loose) at an inopportune moment. > Other notes about my kernel config: I know I have basic SCSI HD support and > IDE support. I tried adding IDE SCSI emulation (lspci said something about > SCSI being attached to IDE2 and IDE3.) Most people don't want ide-scsi, it was for CDRs. I say 'most' because there might still be issues in the error-handling for defective CDs or DVDs. > > I know WinXP has issues with my SATA drive not being first in the boot > sequence, and in my grub config for WinXP boot, I have to swap hd1 to hd0. > Maybe I'll try that for CLFS before I go to bed. Also, I've noticed that > kernels since 2.6.13 have had some trouble with SATA disks, though I didn't > read anyting specific about the 2.6.20.1 kernel SVN is using. Also, if I > must, I suppose I could push CLFS from my sda2 partition onto my hdc1 > partition, but I'd rather not. I'm puzzled by 'kernels since 2.6.13 have had some trouble with SATA disks' - my records (old copies of lilo.conf) show that my pure64 box has been in use since at least 2.6.12.6 (most recently with 2.6.20 and 2.6.21-rc3) without any problem with the SATA drive. Possibly, this is a pointer to a cable (or power supply) problem ? I've no experience of nvidia scsi, so I can't tell for certain if you are using the correct libata drivers, although I think you probably are. At a minimum, under ATA/ATAPI/MFM/RLL support you either want nothing (use parallel ata for the CD) or you want CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y under SCSI device support CONFIG_BLK_DEV_SD CONFIG_BLK_DEV_SR if you intend to use parallel ATA for CD CONFIG_CHR_DEV_SG - probably beneficial for parallel ATA CONFIG_SCSI_CONSTANTS=y might possibly help debug problems under Serial ATA (prod) and Parallel ATA (experimental) drivers CONFIG_ATA=y CONFIG_SATA_NV=y CONFIG_PATA_AMD=y if you want to use the CD with parallel ATA, if it's on an nvidia chip. You might also want other drivers for some of the SATA connectors, depending what your motherboard uses. If you are on 2.6.20 itself, you could also try the latest point release (2.6.20.4) in case that has fixed something. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
