Re: IDE ultraDMA problem (hackers WAS via IDE controller problem) - SOLVED !!
On Wednesday 15 August 2007 16:07, Mario Lobo wrote:
> Besides, the VIA8237A SATA150 controllers ids itself as 0x5337, which is
> not even in the data base at http://pci-ids.ucw.cz/iii/?i=1106
>
> So I added a new id to ata-pci.h:
> #define ATA_VIA8237AS 0x53371106
>
> and added this line to ata-chipset.c:
> { ATA_VIA8237AS, 0x00, 7, 0x00,ATA_SA150, "8237A" },
>
> now, all my controllers get properly identified and work !.
>
> my mobo is an ASUS P5VD2-X.
>
> DEFINETLY ( at least for the mobo I have at home), the ids ARE:
>
> 5337 is for VT8237A SATA150
> 0571 is for VT8237A Bus Master IDE
> 016a is for jmicron SATA300
>
> And these ids are confirmed by the XP drivers downloade from ASUS!
>
> Either ASUS played around with ids in this mobo or the database is screwed
> up.
I really ment VIA on the last statement. sorry.
--
**
//| //| Mario Lobo
// |// | http://www.ipad.com.br
// // ||| FreeBSD since 2.2.8 - 100% Rwindows-free
**
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IDE ultraDMA problem (hackers WAS via IDE controller problem) - SOLVED !!
On Tuesday 14 August 2007 19:33, John Baldwin wrote:
> On Saturday 11 August 2007 12:11:21 pm Mario Lobo wrote:
> > after a long,long search, I found that chip id 0x53371106 belongs to
> > SATA150 controller, not PATA !! Then I enabled all mass storage
> > controllers on the board ( although no SATA drives present ), then two
> > more ids showed up:
> >
> > chip=0x016a10de (jmicron SATA300)
> > chip=0x05711106 <- thats it !!
> >
> > Then I went iinto /usr/src/sys/dev/ata/ata-pci.h and changed the line
> >
> > from
> > #define ATA_VIA8237A0x05911106
> > to
> > #define ATA_VIA8237A0x05711106
> >
> > recompiled, install and BANG!
>
> 6.x already has support for this ID as:
>
> #define ATA_VIA82C571 0x05711106
>
> so you shouldn't have needed to change the code at all.
sounds right but it isn't.
Look at e the code from /usr/src/sys/dev/ata/ata-chpset.c
--
if (pci_get_devid(dev) == ATA_VIA82C571) {
if (!(idx = ata_find_chip(dev, ids, -99)))
return ENXIO;
}
else {
if (!(idx = ata_match_chip(dev, new_ids)))
return ENXIO;
}
--
new_ids doesn't have an id for ATA_VIA8237A (ata-pci.h defines ATA_VIA8237A as
0x0591, which is not what my mobo gives out !) .
Besides, the VIA8237A SATA150 controllers ids itself as 0x5337, which is not
even in the data base at http://pci-ids.ucw.cz/iii/?i=1106
So I added a new id to ata-pci.h:
#define ATA_VIA8237AS 0x53371106
and added this line to ata-chipset.c:
{ ATA_VIA8237AS, 0x00, 7, 0x00,ATA_SA150, "8237A" },
now, all my controllers get properly identified and work !.
my mobo is an ASUS P5VD2-X.
DEFINETLY ( at least for the mobo I have at home), the ids ARE:
5337 is for VT8237A SATA150
0571 is for VT8237A Bus Master IDE
016a is for jmicron SATA300
And these ids are confirmed by the XP drivers downloade from ASUS!
Either ASUS played around with ids in this mobo or the database is screwed up.
--
**
//| //| Mario Lobo
// |// | http://www.ipad.com.br
// // ||| FreeBSD since 2.2.8 - 100% Rwindows-free
**
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IDE ultraDMA problem (hackers WAS via IDE controller problem) - SOLVED !!
*** Re-cap of problem: FreeBSD 6.2-STABLE was not recognizing the VT8237A south bridge ultraDMA ata controller on a P5VD2-X ASUS mobo. FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_hpet0: iomem 0xfe80-0xfe8003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 2000 acpi0: Power Button (fixed) acpi0: reservation of fe80, 100 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 nvidia0: mem 0xdc00-0xdcff,0xc000-0xcfff,0xdd00-0xddff irq 24 at device 0.0 on pci2 nvidia0: [GIANT-LOCKED] atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.0 on pci0 ata0: on atapci0 ata1: on atapci0 *** end of recap pciconf -lv gave me this clue: [EMAIL PROTECTED]:15:0: class=0x01018a card=0x81cf1043 chip=0x53371106 rev=0x07 hdr=0x00 vendor = 'VIA Technologies Inc' class = mass storage subclass = ATA after a long,long search, I found that chip id 0x53371106 belongs to SATA150 controller, not PATA !! Then I enabled all mass storage controllers on the board ( although no SATA drives present ), then two more ids showed up: chip=0x016a10de (jmicron SATA300) chip=0x05711106 <- thats it !! Then I went iinto /usr/src/sys/dev/ata/ata-pci.h and changed the line from #define ATA_VIA8237A0x05911106 to #define ATA_VIA8237A0x05711106 recompiled, install and BANG! nvidia0: mem 0xdc00-0xdcff,0xc000-0xcfff,0xdd00-0xddff irq 24 at device 0.0 on pci2 nvidia0: [GIANT-LOCKED] pcib3: irq 31 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f mem 0xdfefe000-0xdfef irq 28 at device 0.0 on pci3 atapci0: AHCI Version 01.00 controller with 2 ports detected ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 atapci1: port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f,0xe800-0xe8ff irq 21 at device 15.0 on pci0 ata5: on atapci1 ata6: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 15.1 on pci0 ata0: on atapci2 ata1: on atapci2 ad0: 114498MB at ata0-master UDMA100 ad1: 117246MB at ata0-slave UDMA133 ad2: 76351MB at ata1-master UDMA133 acd0: DVDR at ata1-slave UDMA66 Normal life returned :-D I dont know if this fix applies to ALL mobos that use VIA chipset (VT8237A) but it shure did to my ASUS mobo Thanks Wojciech Puchar and Sten Daniel Soersdal for your kind attention. -- ** //| //| Mario Lobo // |// | http://www.ipad.com.br // // ||| FreeBSD since 2.2.8 - 100% Rwindows-free ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IDE ultraDMA problem
On Wednesday 08 August 2007 22:00, you wrote: > > use some FAST WM without unneeded things (eg. icewm) just to run your > music program. Point taken ! > > please show me dmesg lines about your disk and controller, when running > with DMA. > > possibly IDE driver needs patching. > The attached IDE.txt contains not only dmesg output but also the output from: pciconf -lv atacontrol list and atacontrol cap as resquested by Sten Daniel Soersdal > > are you sure YOUR HDs? or all HDs doesn't work right with freebsd. > Mine do. They have ALWAYS worked right with FreeBSD. Like I said my previous board had them working at ultraDMA 100. -- ** //| //| Mario Lobo // |// | http://www.ipad.com.br // // ||| FreeBSD since 2.2.8 - 100% Rwindows-free ** # lobo/root [18:08:03] [~]>dmesg Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #21: Sat Aug 4 14:48:20 BRT 2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LOBO ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) D CPU 3.20GHz (3199.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd,> AMD Features=0x2010 AMD Features2=0x1 Cores per package: 2 real memory = 1072562176 (1022 MB) avail memory = 1032024064 (984 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_hpet0: iomem 0xfe80-0xfe8003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 2000 acpi0: Power Button (fixed) acpi0: reservation of fe80, 100 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 nvidia0: mem 0xdc00-0xdcff,0xc000-0xcfff,0xdd00-0xddff irq 24 at device 0.0 on pci2 nvidia0: [GIANT-LOCKED] atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.0 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xf800-0xf81f at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xf400-0xf41f at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xf000-0xf01f at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xec00-0xec1f at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xd000-0xd0ff at device 16.4 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 pcib3: at device 19.1 on pci0 pci4: on pcib3 pci4: at device 3.0 (no driver attached) pcm0: port 0xdc00-0xdcff irq 19 at device 5.0 on pci4 re0: port 0xd800-0xd8ff mem 0xdfeff000-0xdfeff0ff irq 20 at device 7.0 on pci4 miibus0: on re0 rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1a:92:91:29:d4 re0: [FAST] pcib4: on acpi0 pci128: on pcib4 acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 usca
Re: IDE ultraDMA problem
Mario Lobo wrote: Hello to all; I had a MSI mobo 645 Ultra with 1.5G ram, pentium 4 1.7 Ghz, 3 IDE HD, 1 SAMSUNG 80 G, 1 SAMSUNG 120 G, maxtor 120 G and a LG DVD writer. FreeBSD 6.2 recognized all HDs as ultraDMA 100. Fine. Then a bought a ASUS p5vd2-x, 1G ram, Gforce 7200 video(pci-e), pentium D 940 Dual core and kept the same drives. After tuning and recompiling the kernel a couple times, I got almost everything working great ! SMP, acpi, network, you name it, EXCEPT ultraDMA. if I leave: hw.ata.atapi_dma: 1 hw.ata.ata_dma: 1 FreeBSD reports them (all) at ultraDMA 33. The system boots ok but after 7 or 10 minutes (even if doing nothing), I start geting messages from g_vfs_(); WRITE DMAERROR that can come from any of the drives until the system becomes unstable and ends up rebooting itself. if I leave: hw.ata.atapi_dma: 0 hw.ata.ata_dma: 0 The HDs get down to PIO 4 and the system works fine but at an incredible performance cost. Finacial issues force me to make this work instead of buying more stuff. Thanks for any suggestions, Sorry, i that should be atacontrol cap not atacontrol info -- Sten Daniel Soersdal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IDE ultraDMA problem
Mario Lobo wrote: Hello to all; I had a MSI mobo 645 Ultra with 1.5G ram, pentium 4 1.7 Ghz, 3 IDE HD, 1 SAMSUNG 80 G, 1 SAMSUNG 120 G, maxtor 120 G and a LG DVD writer. FreeBSD 6.2 recognized all HDs as ultraDMA 100. Fine. Then a bought a ASUS p5vd2-x, 1G ram, Gforce 7200 video(pci-e), pentium D 940 Dual core and kept the same drives. After tuning and recompiling the kernel a couple times, I got almost everything working great ! SMP, acpi, network, you name it, EXCEPT ultraDMA. if I leave: hw.ata.atapi_dma: 1 hw.ata.ata_dma: 1 FreeBSD reports them (all) at ultraDMA 33. The system boots ok but after 7 or 10 minutes (even if doing nothing), I start geting messages from g_vfs_(); WRITE DMAERROR that can come from any of the drives until the system becomes unstable and ends up rebooting itself. if I leave: hw.ata.atapi_dma: 0 hw.ata.ata_dma: 0 The HDs get down to PIO 4 and the system works fine but at an incredible performance cost. Finacial issues force me to make this work instead of buying more stuff. Thanks for any suggestions, There are usually one of two reasons for this; 1) Cable not being correct for slots (which UDMA33 suggests) 2) Controller not supported by driver (the controller does/requires something special) I have had perfectly working cables not work just because the motherboard manufacturer decided they wanted to reorder some of the pins on the motherboard (and i wasn't using cables that came with the motherboard). Perhaps you could post 'pciconf -lv' together with 'atacontrol list' and 'atacontrol info ' where is the names of the devices connected. E.g. acd0 ad0 ad1 etc.. dmesg should probably help? -- Sten Daniel Soersdal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IDE ultraDMA problem
Hello to all; I had a MSI mobo 645 Ultra with 1.5G ram, pentium 4 1.7 Ghz, 3 IDE HD, 1 SAMSUNG 80 G, 1 SAMSUNG 120 G, maxtor 120 G and a LG DVD writer. FreeBSD 6.2 recognized all HDs as ultraDMA 100. Fine. Then a bought a ASUS p5vd2-x, 1G ram, Gforce 7200 video(pci-e), pentium D 940 Dual core and kept the same drives. After tuning and recompiling the kernel a couple times, I got almost everything working great ! SMP, acpi, network, you name it, EXCEPT ultraDMA. if I leave: hw.ata.atapi_dma: 1 hw.ata.ata_dma: 1 FreeBSD reports them (all) at ultraDMA 33. The system boots ok but after 7 or 10 minutes (even if doing nothing), I start geting messages from g_vfs_(); WRITE DMAERROR that can come from any of the drives until the system becomes unstable and ends up rebooting itself. if I leave: hw.ata.atapi_dma: 0 hw.ata.ata_dma: 0 The HDs get down to PIO 4 and the system works fine but at an incredible performance cost. Finacial issues force me to make this work instead of buying more stuff. Thanks for any suggestions, -- ** //| //| Mario Lobo // |// | http://www.ipad.com.br // // ||| FreeBSD since 2.2.8 - 100% Rwindows-free ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
