juan--nsd82 at lavera.dnsalias.net schrieb: > Hello again, > I've been thinking about it. Maybe I'm speaking nonsense here but: > > The "FSG case" (i.e: when I use original freecom kernel" and can see the > drive) shows: > ata1: PATA max UDMA/133 cmd 0x1420 ctl 0x142A bmdma 0x1400 irq 22 > ata2: PATA max UDMA/133 cmd 0x1440 ctl 0x144A bmdma 0x1410 irq 22 > ata3: PATA max UDMA/133 cmd 0x1430 ctl 0x143A bmdma 0x1408 irq 22 > > (Always PATA). > > whereas the debian kernel shows: > ata1: SATA max UDMA/133 cmd 0x1420 ctl 0x142A bmdma 0x1400 irq 22 > ata2: SATA max UDMA/133 cmd 0x1430 ctl 0x143A bmdma 0x1408 irq 22 > ata3: PATA max UDMA/133 cmd 0x1440 ctl 0x144A bmdma 0x1410 irq 22 > > And my internal drive is IDE(PATA, I guess). > > Could you please post the result of lspci on your system? It could be > that my model has VT6421 and yours has a different one. VT6421 support two SATA ports and one PATA port. Both outputs are correct - original Freecom firmware uses a driver provided by VIA, and they made it show up like that. 2.6.20 was the first kernel to support PATA port on VT6421 chipsets - maybe it doesn't support some hard disks? Some ideas (although unlikely) - maybe this drive needs some time to start after power on? If you boot from USB-stick, and reboot, do you see the drive? Also, you can try: dmesg -c cd /sys/class/scsi_host ls echo - - - > host0/scan dmesg -c echo - - - > host1/scan dmesg -c echo - - - > host2/scan etc. > Maybe I should start thinking about compiling my own kernel. Meanwhile, > if you already are running something newer than 2.6.20 I'd really like > you to send me the image for "kexec-ing" it. Sorry, I'm running 2.6.20, as my drives are correctly detected. And most probably I won't compile a new kernel before May or April - this is when FSG-3 is likely to be supported in the mainline kernel (starting with 2.6.25, perhaps). -- Tomasz Chmielewski http://wpkg.org |