On Wed, 2004-07-07, at 23:56:08 +0200, Gaudenz Steinlin wrote:

> On Sat, Jul 03, 2004 at 01:19:39AM +0200, Anders Lennartsson wrote:
> > drive. I have not tested to continue the install from there.
> 
> I'm not a SATA export, but AFAIK this is normal and expected.
I agree. Although I kind of expected this kernel to recognize the disk
as SCSI as the Debian 2.4.26 does include the libata patch.  Perhaps
2.4.27 will sort this out.

snip

> > Jul  1 12:03:36 (none) syslog.warn klogd: PCI: Enabling device 00:1f.1 (0005 -> 
> > 0007)
> > Jul  1 12:03:36 (none) syslog.info klogd: ICH5: chipset revision 2
> > Jul  1 12:03:36 (none) syslog.info klogd: ICH5: not 100% native mode: will probe 
> > irqs later
> > Jul  1 12:03:36 (none) syslog.info klogd:     ide0: BM-DMA at 0xfc00-0xfc07, BIOS 
> > settings: hda:DMA, hdb:pio
> > Jul  1 12:03:36 (none) syslog.info klogd:     ide1: BM-DMA at 0xfc08-0xfc0f, BIOS 
> > settings: hdc:DMA, hdd:pio
> > Jul  1 12:03:36 (none) syslog.info klogd: ICH5-SATA: IDE controller at PCI slot 
> > 00:1f.2
> > Jul  1 12:03:36 (none) syslog.info klogd: ICH5-SATA: chipset revision 2
> > Jul  1 12:03:36 (none) syslog.info klogd: ICH5-SATA: 100% native mode on irq 5
> > Jul  1 12:03:36 (none) syslog.info klogd:     ide2: BM-DMA at 0xef90-0xef97, BIOS 
> > settings: hde:DMA, hdf:pio
> > Jul  1 12:03:36 (none) syslog.info klogd:     ide3: BM-DMA at 0xef98-0xef9f, BIOS 
> > settings: hdg:pio, hdh:pio
> > Jul  1 12:03:36 (none) syslog.info klogd: PDC20269: IDE controller at PCI slot 
> > 03:0c.0
> > Jul  1 12:03:36 (none) syslog.info klogd: PDC20269: chipset revision 2
> > Jul  1 12:03:36 (none) syslog.info klogd: PDC20269: not 100% native mode: will 
> > probe irqs later
> > Jul  1 12:03:36 (none) syslog.info klogd: PDC20269: ROM enabled at 0xf7ee0000
> > Jul  1 12:03:36 (none) syslog.info klogd:     ide4: BM-DMA at 0xdf60-0xdf67, BIOS 
> > settings: hdi:pio, hdj:pio
> > Jul  1 12:03:36 (none) syslog.info klogd:     ide5: BM-DMA at 0xdf68-0xdf6f, BIOS 
> > settings: hdk:pio, hdl:pio
> > Jul  1 12:03:36 (none) syslog.warn klogd: hdc: PLEXTOR CD-R PREMIUM, ATAPI 
> > CD/DVD-ROM drive
> > Jul  1 12:03:36 (none) syslog.warn klogd: hde: ST3160023AS, ATA DISK drive
> > Jul  1 12:03:36 (none) syslog.warn klogd: blk: queue f885bba8, I/O limit 4095Mb 
> > (mask 0xffffffff)
> > Jul  1 12:03:36 (none) syslog.warn klogd: hdi: IC35L060AVVA07-0, ATA DISK drive
> > Jul  1 12:03:36 (none) syslog.warn klogd: blk: queue f885c450, I/O limit 4095Mb 
> > (mask 0xffffffff)
> > Jul  1 12:03:36 (none) syslog.warn klogd: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > Jul  1 12:03:36 (none) syslog.warn klogd: ide1 at 0x170-0x177,0x376 on irq 15
> > Jul  1 12:03:36 (none) syslog.warn klogd: ide2 at 0xefe0-0xefe7,0xefae on irq 5
> > Jul  1 12:03:36 (none) syslog.warn klogd: ide4 at 0xdf98-0xdf9f,0xdf96 on irq 7
> > Jul  1 12:03:36 (none) syslog.warn klogd: hde: attached ide-disk driver.
> > Jul  1 12:03:36 (none) syslog.info klogd: hde: 312581808 sectors (160042 MB) 
> > w/8192KiB Cache, CHS=19457/255/63, UDMA(33)
> > Jul  1 12:03:36 (none) syslog.warn klogd: hdi: attached ide-disk driver.
> > Jul  1 12:03:36 (none) syslog.info klogd: hdi: 120103200 sectors (61493 MB) 
> > w/1863KiB Cache, CHS=119150/16/63, UDMA(100)
> > Jul  1 12:03:36 (none) syslog.info klogd: Partition check:
> > Jul  1 12:03:36 (none) syslog.info klogd:  [PTBL] [781/128/63] p1 p2
> > Jul  1 12:03:36 (none) syslog.info klogd:  p5 >
> > Jul  1 12:03:36 (none) syslog.info klogd:  [PTBL] [7476/255/63] p1
> >
> > Well, what the kernel is expected to do depends on the source and
> > configuration, niether of which I have checked for this particular
> > kernel.
> So, no bug with 2.4, you just didn't try any further. Correct?
Correct.

> > >From the 2.6 hardware-summary:
> >
> > info: /bin/report-hw: discover: ata_piix;;;Intel Corporation;82801EB (ICH5) Serial 
> > ATA 150 Storage Controller;
> > info: /bin/report-hw: discover: ide-scsi;;;Linux;IDE-SCSI emulation layer;
> > info: /bin/report-hw: discover: usb-uhci;;;Intel Corporation;82801EB/ER 
> > (ICH5/ICH5R) USB UHCI #1;
> > info: /bin/report-hw: discover: usb-uhci;;;Intel Corporation;82801EB/ER 
> > (ICH5/ICH5R) USB UHCI #2;
> > info: /bin/report-hw: discover: usb-uhci;;;Intel Corporation;82801EB/ER 
> > (ICH5/ICH5R) USB UHCI #3;
> > info: /bin/report-hw: discover: ;;;Unknown;IC35L060AVVA07-0;/dev/hde
> > info: /bin/report-hw: discover: ;;;eUSB;Compact Flash;/dev/sda
> > info: /bin/report-hw: discover: ;;;eUSB;SD-MS-SM;/dev/sdb
> > info: /bin/report-hw: discover: ;;;ATA;ST3160023AS;/dev/sdc
> > error: /bin/report-hw: Unable to find lspci.
> > info: /bin/report-hw: lsmod: Module                  Size  Used by    Not tainted
> > info: /bin/report-hw: lsmod: ata_piix                7940   3
> > info: /bin/report-hw: lsmod: libata                 36480   1 ata_piix,[permanent]
> > info: /bin/report-hw: lsmod: xfs                   513720   0
> >
> > Note: The lsmod lines with ata_piix related modules are only there
> > after manually modprobing ata_piix, but the ata_piix;;;Intel ... line
> > is there both before and after the module loading.
> 
> This is very strange. It seems that hw-detect does not load the module
> allthough discover recognises it and it seems to be there.
> 
> Are you sure you waited until the third hardware detection run before
> you manually loaded the module. The module may not be available during
> the first and second run of hw-detect.

I waited until I came into the partitioner. That should be the outmost
limit, if the disk isn't recognized at that time your'e out of luck.

I then backed out of the partitioner and saved the logs to floppy, and
then executed a shell, copied the logs to a directory on the floppy,
and then manually loaded the module. Exit from the shell and then into
the partitioner. Viol�, there was the disk. Succesfully partitioned
the disk. Then saved new logs.

Anders


Reply via email to