Re: pata_via appears to incorrectly detects 40-pin cable
Does the laptop actually have 80 wire cables - did you see UDMA100 actually being used. If so can you send me an lspci -vxx and a dmesg. Probably we need to add it to the list of devices using short 40 wire cable tricks I have been using UDMA5/ATA100 for months, although this was set by a hdparm init.d script. Disabling the script, performing a cold reset and booting into a 2.6.21 kernel with the old ATA system enabled, hdparm -i indicated the HD was using UDMA5. I'm assuming that this means the old drivers do not limit to ATA33 unless there is a better I can check this. I removed the laptop's hard drive. It fits into a cradle which is inserted into the laptop. There is no form of cable or adapter that is placed on the HD's connector. It just plugs directly into a socket inside the laptop when the cradle is inserted. I hope this is enough information. I've included the output of dmesg and lspci -vxx. Francis 0x342 mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 2004.618 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1294252k/1309632k available (2072k kernel code, 14224k reserved, 714k data, 196k init, 392128k highmem) virtual kernel memory layout: fixmap : 0xfffaa000 - 0xf000 ( 340 kB) pkmap : 0xff80 - 0xffc0 (4096 kB) vmalloc : 0xf880 - 0xff7fe000 ( 111 MB) lowmem : 0xc000 - 0xf800 ( 896 MB) .init : 0xc03bc000 - 0xc03ed000 ( 196 kB) .data : 0xc030618f - 0xc03b8b94 ( 714 kB) .text : 0xc010 - 0xc030618f (2072 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4011.25 BogoMIPS (lpj=2005626) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff e3d3fbff CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff e3d3fbff 0410 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. CPU: AMD Mobile AMD Athlon 64 Processor 3000+ stepping 00 Checking 'hlt' instruction... OK. ACPI: Core revision 20070126 ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfd64c, last bus=1 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: (supports S0 S3 S4 S5) ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) PCI quirk: region 4000-407f claimed by vt8235 PM PCI quirk: region 8100-810f claimed by vt8235 SMB ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *5, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *9, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *11, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *5, disabled. ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 7 9 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 12 14 15) *9 ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 9 10 11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 12 devices ACPI: ACPI bus type pnp unregistered SCSI subsystem initialized libata version 2.20 loaded. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:05: iomem range 0x0-0x9 could not be reserved pnp: 00:05: iomem range 0xe-0xf could not be reserved pnp: 00:05: iomem range 0xfff0-0x could not be reserved pnp: 00:05: iomem range 0xffee-0xffef has been reserved pnp: 00:06: ioport range 0x600-0x60f has been reserved pnp: 00:06: ioport range 0x4d0-0x4d1 has been reserved pnp: 00:06: ioport range 0xfe10-0xfe11 has been reserved pnp: 00:06: ioport range 0xfe00-0xfe00 has been reserved Time: tsc clocksource has been installed. PCI: Bridge: :00:01.0 IO window: 2000-2fff MEM window: d010-d01f PREFETCH window: d800-dfff PCI: Bus 2, cardbus bridge: :00:07.0 IO window: 1c00-1cff IO window: 3000-30ff PREFETCH window: 6000-63ff MEM window: 6400-67ff PCI: Setting latency timer of device :00:01.0 to 64 ACPI: PCI Interrupt :00:07.0[A] ->
Re: pata_via appears to incorrectly detects 40-pin cable
Does the laptop actually have 80 wire cables - did you see UDMA100 actually being used. If so can you send me an lspci -vxx and a dmesg. Probably we need to add it to the list of devices using short 40 wire cable tricks I have been using UDMA5/ATA100 for months, although this was set by a hdparm init.d script. Disabling the script, performing a cold reset and booting into a 2.6.21 kernel with the old ATA system enabled, hdparm -i indicated the HD was using UDMA5. I'm assuming that this means the old drivers do not limit to ATA33 unless there is a better I can check this. I removed the laptop's hard drive. It fits into a cradle which is inserted into the laptop. There is no form of cable or adapter that is placed on the HD's connector. It just plugs directly into a socket inside the laptop when the cradle is inserted. I hope this is enough information. I've included the output of dmesg and lspci -vxx. Francis 0x342 mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 2004.618 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1294252k/1309632k available (2072k kernel code, 14224k reserved, 714k data, 196k init, 392128k highmem) virtual kernel memory layout: fixmap : 0xfffaa000 - 0xf000 ( 340 kB) pkmap : 0xff80 - 0xffc0 (4096 kB) vmalloc : 0xf880 - 0xff7fe000 ( 111 MB) lowmem : 0xc000 - 0xf800 ( 896 MB) .init : 0xc03bc000 - 0xc03ed000 ( 196 kB) .data : 0xc030618f - 0xc03b8b94 ( 714 kB) .text : 0xc010 - 0xc030618f (2072 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4011.25 BogoMIPS (lpj=2005626) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff e3d3fbff CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff e3d3fbff 0410 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. CPU: AMD Mobile AMD Athlon 64 Processor 3000+ stepping 00 Checking 'hlt' instruction... OK. ACPI: Core revision 20070126 ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfd64c, last bus=1 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: (supports S0 S3 S4 S5) ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) PCI quirk: region 4000-407f claimed by vt8235 PM PCI quirk: region 8100-810f claimed by vt8235 SMB ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *5, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *9, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *11, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *5, disabled. ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 7 9 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 12 14 15) *9 ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 9 10 11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 12 devices ACPI: ACPI bus type pnp unregistered SCSI subsystem initialized libata version 2.20 loaded. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report pnp: 00:05: iomem range 0x0-0x9 could not be reserved pnp: 00:05: iomem range 0xe-0xf could not be reserved pnp: 00:05: iomem range 0xfff0-0x could not be reserved pnp: 00:05: iomem range 0xffee-0xffef has been reserved pnp: 00:06: ioport range 0x600-0x60f has been reserved pnp: 00:06: ioport range 0x4d0-0x4d1 has been reserved pnp: 00:06: ioport range 0xfe10-0xfe11 has been reserved pnp: 00:06: ioport range 0xfe00-0xfe00 has been reserved Time: tsc clocksource has been installed. PCI: Bridge: :00:01.0 IO window: 2000-2fff MEM window: d010-d01f PREFETCH window: d800-dfff PCI: Bus 2, cardbus bridge: :00:07.0 IO window: 1c00-1cff IO window: 3000-30ff PREFETCH window: 6000-63ff MEM window: 6400-67ff PCI: Setting latency timer of device :00:01.0 to 64 ACPI: PCI Interrupt :00:07.0[A] -
Re: pata_via appears to incorrectly detects 40-pin cable
Claas Langbehn wrote: This is bug 8142. Please see http://bugzilla.kernel.org/show_bug.cgi?id=8142 Apologies if this wasn't clear from context. The drive (Hitachi TravelStar 7K100) is IDE not SATA so differs from this bug in the way that the cable check should be relevant. Francis - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pata_via appears to incorrectly detects 40-pin cable
Claas Langbehn wrote: This is bug 8142. Please see http://bugzilla.kernel.org/show_bug.cgi?id=8142 Apologies if this wasn't clear from context. The drive (Hitachi TravelStar 7K100) is IDE not SATA so differs from this bug in the way that the cable check should be relevant. Francis - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
