Re: Defective Red Hat Distribution poorly represents Linux
Can everyone lay off this guy, he made a mistake and the heat is not cool. This is no way for the general masses to get a taste of Linux, cool? Please jsut let it die or offline the chap. Regards, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ATA and Stroke Patch up
pub/../ide-2.2.17/ide.2.2.17.all.20001120.patch pub/../ide-2.2.18/ide.2.2.18-22.all.20001120.patch pub/../ide.2.4.0-t11/ide.2.4.0-t11.1120.patch If you do not set CONFIG_IDEDISK_STROKE it will warn you how much it is keeping that you can not use. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0, test10, test11: HPT366 problem
2.2.x and 2.4.0-xxx, do not share the same interrupt pin hack.
This is in 2.2.x patches.
printk("%s: onboard version of chipset, pin1=%d pin2=%d\n", d->name, pin1, pin2);
#if 1
/* I forgot why I did this once, but it fixed something. */
pci_write_config_byte(dev2, PCI_INTERRUPT_PIN, dev->irq);
printk("PCI: %s: Fixing interrupt %d pin %d to ZERO \n", d->name, dev2->irq, pin2);
pci_write_config_byte(dev2, PCI_INTERRUPT_LINE, 0);
#endif
It does the undocumented "mode 3" that I had to explain to HighPoint that
ABIT violated the OEM docs.
It is a PCI-addon chipset style deployed like a legacy chipset.
Primary channel is set to IRQ X and PIN A
Secondary channel is set to IRQ X++ and PIN B
This is not allowed by the guidelines but it you do the big nasty above,
it will fix it 99% of the time.
Add the above stub to ide-pci.c near or at line 756 to look like 2.2, then
retry and see if it fixes it. Then you bitch at Linus, not me, because it
is a functional kludge, but a "kludge".
Cheers,
On Tue, 21 Nov 2000, Hakan Lennestal wrote:
>
> Hi !
>
> I'm having problems when booting 2.4.0 test10 and test11 kernels
> (perhaps some earlier kernels too).
> Approximately nine out of ten times the kernel hangs when
> trying to detect partitions on the first HPT366 disk.
>
> It looks something like this:
>
> Nov 21 08:08:40 t kernel: Uniform Multi-Platform E-IDE driver Revision: 6.31
> Nov 21 08:08:40 t kernel: ide: Assuming 33MHz system bus speed for PIO modes;
>override with idebus=xx
> Nov 21 08:08:40 t kernel: PIIX4: IDE controller on PCI bus 00 dev 39
> Nov 21 08:08:40 t kernel: PIIX4: chipset revision 1
> Nov 21 08:08:40 t kernel: PIIX4: not 100%% native mode: will probe irqs later
> Nov 21 08:08:40 t kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS settings:
>hda:DMA, hdb:pio
> Nov 21 08:08:40 t kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS settings:
>hdc:DMA, hdd:pio
> Nov 21 08:08:40 t kernel: HPT366: IDE controller on PCI bus 00 dev 48
> Nov 21 08:08:40 t kernel: HPT366: chipset revision 1
> Nov 21 08:08:40 t kernel: HPT366: not 100%% native mode: will probe irqs later
> Nov 21 08:08:40 t kernel: ide2: BM-DMA at 0xac00-0xac07, BIOS settings:
>hde:DMA, hdf:pio
> Nov 21 08:08:40 t kernel: HPT366: IDE controller on PCI bus 00 dev 49
> Nov 21 08:08:40 t kernel: HPT366: chipset revision 1
> Nov 21 08:08:40 t kernel: HPT366: not 100%% native mode: will probe irqs later
> Nov 21 08:08:40 t kernel: ide3: BM-DMA at 0xb800-0xb807, BIOS settings:
>hdg:DMA, hdh:pio
> Nov 21 08:08:40 t kernel: hda: FUJITSU MPD3064AT, ATA DISK drive
> Nov 21 08:08:40 t kernel: hdc: Hewlett-Packard CD-Writer Plus 8200, ATAPI CDROM
>drive
> Nov 21 08:08:40 t kernel: hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
> Nov 21 08:08:40 t kernel: hde: IBM-DTLA-307030, ATA DISK drive
> Nov 21 08:08:40 t kernel: hdg: QUANTUM Bigfoot TX12.0AT, ATA DISK drive
> Nov 21 08:08:40 t kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Nov 21 08:08:40 t kernel: ide1 at 0x170-0x177,0x376 on irq 15
> Nov 21 08:08:40 t kernel: ide2 at 0xa400-0xa407,0xa802 on irq 9
> Nov 21 08:08:40 t kernel: ide3 at 0xb000-0xb007,0xb402 on irq 9
> Nov 21 08:08:40 t kernel: hda: 12672450 sectors (6488 MB) w/512KiB Cache,
>CHS=788/255/63, UDMA(33)
> Nov 21 08:08:40 t kernel: hde: 60036480 sectors (30739 MB) w/1916KiB Cache,
>CHS=59560/16/63, UDMA(66)
> Nov 21 08:08:40 t kernel: hdg: 23547888 sectors (12057 MB) w/69KiB Cache,
>CHS=23361/16/63, UDMA(33)
> Nov 21 08:08:40 t kernel: Partition check:
> Nov 21 08:08:40 t kernel: hda: hda1 hda2 < hda5 hda6 hda7 >
> Nov 21 08:08:40 t kernel: hde: hde1 hde2 < hde5
>
> And then after a while it gets a DMA timeout and hangs hard.
>
> The hang can occur anywhere during the partition detection and it can for
> instance also fail at once and look like:
>
> hde:
>
> or fail even after the last partiton:
>
> hde: hde1 hde2 < hde5 hde6 hde7 hde8
>
> Approximately one out of ten reboots the detection succedes and I'm able
> to boot up the kernel and then everything works smoothly.
>
> There are no problems when booting 2.2.*-kernels with the HPT366-patch.
>
> Regards.
>
> /Håkan
>
>
> ---
> e-mail: [EMAIL PROTECTED] |
> or [EMAIL PROTECTED] |
> ---
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
BASTARDIZED FAKE RAID EXPLAINED!!!! STOP ASKING!!!!
I am so damn tired of people not reading or doning their homework before asking silly questions uder the pretext of a goofy statement! "Gee Wiz, it sez on the box it is a Raid Controller, and 'duh' Hardware, too". This is the last time I hope to explain this pile of crap. Sometime ago, people who make EIDE/ATA Host adapters, otherwise known as controllers, were smoking a lot of DOPE that day. They came to the conclusion that because Microsoft requires a driver for everything, lets kludge some bogus bullshit hack and shove it in the BIOS and call it RAID! Then the dumb asres of the world will be suckered into paying more for something that is not what it is sold as on the packaging. Now how does this KLUDGE of software in the BIOS and Software Engine work? Real simple! * It first use the BIOS to execute software raid calls like mkraid. * Then it destrokes the drive (you have less capacity, didn't you know?). * In the beginning the construction of the RAID signature blocks were just after the MBR and usually mirrored the MBR and held date and time codes that the BIOS used to toggle which LIE it would tell the INT19 calls from the BIOS as to what real and what was fake. * This is know as HOTSWAP-bootable. * After bitching out most of the card makers that LILO STOMPS all over the RAID signature, they got smart and made two copies. One on the front (useless) and one on the tail. * Since all of these only allow for simple mode raids and partitioning was not possible, because it was a kludge remember! In order to have partitions you have to have several signature blocks to maintain the date/time stamps and counters. Since there is only one signature pattern, you get one partition. * Until all of these card makers and chipset people release the signatures and how to update or read/write, Linux will not be able to protect the information or the construction of the RAID. * Now lets say one day Linux gets access or can publish this info. * How will Linux handle this info, because NOW there will be a way to make it work, using the Linux Software Raid Engine. The short version: Linux short changes your drive capacity for you to gather its own tables and signatures for a portion of the drive that if capable of supporting partitions if needed. Below is a line diagram. M==MBR B==BRS=BiosRaidSignatures L==LRS=LinuxRaidSignatures H==HASH-CRAP after LILO runs. M-- normal no raid MBB bios raid MH--LLB bios raid+linux The dashes are what you can format and use for data. Linux will have to destroke the reported geometry/capacity to protect all the signatures so that we can work with the real BIOS protion of the raid to enable the Linux soft engine. I now quit on the details because I am going to bed! Now nobody ask or bug me again of this stuff/crap until the OEM venders release their bogus IP. Everyone should note that I have had this conversation with all of the venders that make this stuff and called it what it is and stood on that point. Where are we today? One of the four players in this game is at least working to make something happen, but everyone of these four OEM's are afraid that their IP is more valuable than the others, but all agree that the Linux Engine does it better! So Good Nite and do not ask me this question again! Or the real ATA will come to life and nobody likes me when that happens. Regards, Andre Hedrick The Linux ATA/IDE (ranting piss-off over raid shit) guy! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0, test10, test11: HPT366 problem
On Tue, 21 Nov 2000, Peter Samuelson wrote: > The way I understood Hakan was: "it boots in udma4, and if it gets all > the way to userland I immediately hdparm it down to udma3, and then it > works fine". No, if it doesn not hang and we get iCRC errors it will down grade automatically, but it is a transfer rate issue than it must be hard coded to force an upper threshold limit. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0, test10, test11: HPT366 problem
Does that fix it?
On Tue, 21 Nov 2000, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > When it comes to the partition detection during bootup, udma4 or
> > udma3 doesn't seem to matter. It passes approx. one out of ten times
> > either way.
>
> How have you made it use udma3 at bootup? Something like the patch below?
>
> Index: drivers/ide/hpt366.c
> ===
> RCS file: /inst/cvs/linux/drivers/ide/Attic/hpt366.c,v
> retrieving revision 1.1.2.10
> diff -u -r1.1.2.10 hpt366.c
> --- drivers/ide/hpt366.c 2000/11/10 14:56:31 1.1.2.10
> +++ drivers/ide/hpt366.c 2000/11/21 13:27:32
> @@ -55,6 +55,8 @@
> };
>
> const char *bad_ata66_4[] = {
> + "IBM-DTLA-307045",
> + "IBM-DTLA-307030",
> "WDC AC310200R",
> NULL
> };
>
> --
> dwmw2
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0, test10, test11: HPT366 problem
On Tue, 21 Nov 2000, David Woodhouse wrote: > On Tue, 21 Nov 2000, Andre Hedrick wrote: > > > No, if it doesn not hang and we get iCRC errors it will down grade > > automatically, but it is a transfer rate issue than it must be hard coded > > to force an upper threshold limit. > > Do we downgrade gracefully, or do we just drop directly to non-DMA mode? With Grace, and now you blessed, go in peace my son. grep crc ./drivers/ide/* Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [uPATCH] fix IDE/ServerWorks OSB4 config option (test11)
Oh well mistakes in Config are okay and not fatal. Thanks for the find Bart. Cheers, On Tue, 21 Nov 2000, Bartlomiej Zolnierkiewicz wrote: > > Hi > > In drivers/Config.in CONFIG_BLK_DEV_OSB4 depends on itself... > > -- > Bartlomiej Zolnierkiewicz > <[EMAIL PROTECTED]> > > --- linux-240t11/drivers/ide/Config.inWed Nov 15 22:02:11 2000 > +++ linux/drivers/ide/Config.in Tue Nov 21 14:52:07 2000 > @@ -68,7 +68,7 @@ > dep_bool 'OPTi 82C621 chipset enhanced support (EXPERIMENTAL)' >CONFIG_BLK_DEV_OPTI621 $CONFIG_EXPERIMENTAL > dep_bool 'PROMISE PDC20246/PDC20262/PDC20267 support' >CONFIG_BLK_DEV_PDC202XX $CONFIG_BLK_DEV_IDEDMA_PCI > dep_bool ' Special UDMA Feature' CONFIG_PDC202XX_BURST >$CONFIG_BLK_DEV_PDC202XX > - dep_bool 'ServerWorks OSB4 chipset support' CONFIG_BLK_DEV_OSB4 >$CONFIG_BLK_DEV_OSB4 > + dep_bool 'ServerWorks OSB4 chipset support' CONFIG_BLK_DEV_OSB4 >$CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86 > dep_bool 'SiS5513 chipset support' CONFIG_BLK_DEV_SIS5513 >$CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86 > dep_bool 'SLC90E66 chipset support' CONFIG_BLK_DEV_SLC90E66 >$CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86 > dep_bool 'Tekram TRM290 chipset support (EXPERIMENTAL)' >CONFIG_BLK_DEV_TRM290 $CONFIG_BLK_DEV_IDEDMA_PCI > > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Announce: modutils 2.3.21 is available
On Wed, 22 Nov 2000, Jeff V. Merkey wrote: > + add RedHat ism's with a --rhc (red hat compatible) -i -m (-F) > > RedHat kind of is the standard in the commercial world in the US. Regardless of the bogus nature of this statement, boss. GNU/OS packages are to be modified locally and a generic form that does not have flavor or spin is what maintainers release. Regards, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Removable Drive Bays, What am I using.
I have finally gone and picked a drive bay that looks to work well in all cases. It does not appear to have any skew errors that are not inside the range of variations. I just picked up a dozen kits for use. I am working on a proposal to to a one week linux special purchase it discounted schedules. InClose can not handle the direct shipping, but we are looking to find one of their distributors to give Linux users an advantage. All questions can be directed to "InClose Drive Bays" <[EMAIL PROTECTED]> and will be forward to the folks inhouse. Regard, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ext2 filesystem corruptions back from dead? 2.4.0-test11
On Thu, 23 Nov 2000, Ion Badulescu wrote: > > Yesterday I had a diff -r showing that the old version > > was corrupted and the new was OK. Of course a second > > look showed that the old version also was OK, the corruption > > must have been in the buffer cache, not on disk.) > > Are these disks IDE disks by any chance? What the F*** does that have to do with the price of eggs in china, heh? Just maybe if you could follow a thread, you would see that that Alex Viro has pointed out that changes in the FS layer as dorked things. Since there have been not kernel changes to the driver that effect the code since 2.4.0-test5 or test6 and it now randomly shows up after five or six revisions out from the change, and the changes were chipset only. Please make your point. Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ext2 filesystem corruptions back from dead? 2.4.0-test11
On Fri, 24 Nov 2000, Alexander Viro wrote: > > > On Thu, 23 Nov 2000, Andre Hedrick wrote: > > > What the F*** does that have to do with the price of eggs in china, heh? > > Just maybe if you could follow a thread, you would see that that Alex Viro > > has pointed out that changes in the FS layer as dorked things. > > ? > If you have a l-k feed from future - please share. I'm not saying that Date: Thu, 23 Nov 2000 04:37:21 -0500 (EST) > fs/* is not the source of that stuff, but I sure as hell had not said > that it is. I simply don't know yet. You were pointing out changes to reproduce the effect. > > Since there have been not kernel changes to the driver that effect the > > code since 2.4.0-test5 or test6 and it now randomly shows up after five or > > six revisions out from the change, and the changes were chipset only. > > generic_unplug_device() was changed more or less recently. I doubt that > it is relevant, but... Cool, the issue was that I get tried of people blaming the ATA subsystem for things that it does not do or has control over. Basically, I kill bogus threads that try to tag me with an old problem of the past that was a hardware issue. Given the latest stats that more than 90% of the linux install base is hinged on me getting the low-level engine core correct, I go on benders when cheap shots are take across the bow. Now the only issue that is even on the radar map is a potential 1GB cross copy execution where I have a single report that md5sums do not match. I have yet to reproduce it even with the identical hardware sent to me. I questioned _A_ about this and there may be a case that is OS independent which is more important to me than other. This is a non-fixable for 6->12 months, until I kick some tail in the standards committee meetings over this point. If it is a reality, Linux and Microsoft will join as the OS's represented there and force the change. Only because there are potentical side-bars that NT is effected also in these rare cases. Cheers, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ext2 filesystem corruptions back from dead? 2.4.0-test11
On Fri, 24 Nov 2000, Alexander Viro wrote: > I don't see any attempts to tag you (or ATA subsystem, for that matter) > in that thread. And thread is hardly bogus... I agree that changes in We agree that the "thread" is valid, trust that point. There was a quick pointed question that present, "Is it an IDE disk?" to paraphase the statement. > drivers/ide/* are very unlikely to be the source of that, but information > of that kind can help to weed out some of the changes in ll_rw_blk.c. What may be even more helpful is when I get arround to making an option, for some outstanding patches for 2.5, that would allow for user-space pattern pushing through the driver that gets properly inserted in to the list/buffer-head to make it pass through the block layer. This kind of testing will allow for nibble level tracing through everything, I hope. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
NO! Doing so VIOLATES the terms and agreement that you obtained the BINARY Soft-Raid Engine and the GPL terms of the kernel. On Fri, 24 Nov 2000, James Lamanna wrote: > So, I have a system that has 2 45GB IDE drives connected > up to a Promise Technologies Fasttrack 100. > Promise Techonologies currently has a driver that you can compile > against a 2.2 kernel into a module, but it also includes one > proprietary object file. > During my linux installation I was able to preload the module and > have it detect the drives fine as a scsi device, so I was able to > install the base system onto them. > > The question is, is there a way to compile this module into the kernel > so that it will automatically detect the card? A simple linking of the > module into the scsi library by editing the Makefile doesn't seem to do > it. It doesn't detect the drives if I boot off of a floppy with this > kernel on it. > > Also, is it possible for Lilo to even boot this without a RAM disk > somewhere? I guess Lilo has to know about the drive, but it can't know > without the module...so am I screwed into using floppies with a > RAM disk image anyways? > > Thanks, > --James Lamanna > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ext2 filesystem corruptions back from dead? 2.4.0-test11
On Fri, 24 Nov 2000, Mike Ricketts wrote: > On Fri, 24 Nov 2000, Ion Badulescu wrote: > > > So I'm asking the same question, to all those who have seen unexplained > > filesystem corruption with 2.4.0: are you using IDE drives? If the answer > > is yes, can you check the logs and see if, at *any* point before the > > corruption occurred, the IDE driver choked and disabled DMA for *any* of > > your disks? > > I have both IDE and SCSI drives in my machine, but have only seen > corruption on the SCSI drives. That doesn't mean that the problem only > exists on the SCSI drives - they IDE ones are not frequently written to. > I have disabled DMA myself on all my IDE drives because if I enable it, > the IDE driver always chokes the first time they are anything like > hammered (well, it always used to - I haven't actually tried it recently). This is the kind of data point that is needed. A possible storage class independent problem. More important, what was the first kernel you began to notice this problem. Next, I need you to enable the DMA engine in ATA to verify that is happening on both classes. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
PIIX4 BX Errata for DMA errors.
Anyone having DMA errors that are dmaproc: error 14, there is not a clean workaround yet. Also the Intel erratas state that only a bus reset will clear the hang, but the details are loose. Regards, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
On Sat, 25 Nov 2000, Henning P. Schmiedehausen wrote: > No, it does not. Distributing does. You will never get this right. You > can compile into your kernel anything you like as long as you don't > give it away. And you will never boot it because the resources conflict with out the module, go try it. I promise you that it will never boot if you build it in the kernel. Also the terms of acceptance of the module also means you can not built it inter the kernel. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
Oh remember, I DEFINED the terms that the module could be created! Go and examine the wrapper and it is portions of the pdc202xx.c code that is mine. With that in mind, in order to use that GPL code, the restrictions and terms imposed were module exclusive. Regards, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] removal of "static foo = 0"
On Sun, 26 Nov 2000, John Alvord wrote: > On Sun, 26 Nov 2000 04:25:05 + (GMT), Alan Cox > <[EMAIL PROTECTED]> wrote: > > >> AB> of changes that yield a negligable advantage and reduce stability > >> AB> a tiny little bit. That is pushing Linux in the direction of this > >> AB> abyss. You notice that the view gets better, and I get nervous. > >> > >> Can somebody stop this train load of bunk? > >> > >> Uninitialized global variables always have a initial value of > >> zero. Static or otherwise. Period. > > > >That isnt what Andries is arguing about. Read harder. Its semantic differences > >rather than code differences. > > > > static int a=0; > > > >says 'I thought about this. I want it to start at zero. I've written it this > >way to remind of the fact' > > > >Sure it generates the same code > > It also says "I do not know much about the details of the kernel C > environment. In particular I do not know that all static variables are > initialized to 0 in the kernel startup. I have not read setup.S." Are you positive for modules too... Regardless of the fact you have displayed, some of us prefer to clobber it to insure that it stays zero until access. Last thing you want is an unstatic static when we go to spin a disk for data. Just how warm and fuzzy do you fell if your block drivers do not insure this point? Cheers, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] removal of "static foo = 0"
On Sun, 26 Nov 2000, Keith Owens wrote: > >Are you positive for modules too... > > Yes. I know this, I am being punchy. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: difference between kernel and bios report on drive status
It is a standards bug that your drives are mixed in the rev. Adjust the IVB option so that it does not care about these bits just the presence of either set. Cheers, On Sun, 26 Nov 2000 [EMAIL PROTECTED] wrote: > Hi there: > > I am using PROMISE ultra100 with 2 UDMA66 disks. The PROMIS > bios reports that both disks are using UDMA 4. But during kernel boot On > Fri, 24 Nov 2000, Szabolcs Szakacsits wrote: up, the master disk is using > UDMA 2 only. The reason is that master disk's pci->dma_ultra value is only > 0x40f. I hacked the kernel a bit, both hard disk using hardware configued > udma_four though. So I am wondering why not use udma_four as mode > indication? Anyone here knows or > I have to email Andre on this? > > By the way, mode4 works much faster.(hdparm -tT): > disk1: udma33, mode2, disk buffer read 14MB/s > disk2: udma66, mode4, disk buffer read 24MB/s > > both disks: buffer-cache read 88MB/s > > The second disk is only 5400RPM, the first one is 7200RPM. Both comply > > > HOW? to UDMA66. How come the 2nd one is UDMA66, but the first one is > > > > No performance loss, RAM is always fully utilized (except if no swap), > UDMA33? And how come the 2nd is faster than the first one. > > I hope this is not a kernel bug. > > Fei > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: (U)DMA, dma_intr status=0x51, error=0x84
On Sun, 26 Nov 2000, Christian Roessner wrote:
> hda: dma_intr status=0x51 {DriveReadySeekComplete Error}
> hda: dma_intr error=0x84 {DriveStatusError BadCRC}
This is what it tells you directly. You have dirty crosstalk on your
ribbon. Basically nothing is wrong, except you can not safely support
that transfer rate.
Cheers,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: ATA-4, ATA-5 TCQ status
On Mon, 27 Nov 2000, Jens Axboe wrote: > On Mon, Nov 27 2000, Sasi Peter wrote: > > Hi! > > > > I would like to ask if the tagged command queueing capability in the > > decent ATA standards is utilized in the linux IDE driver (2.2 2.2ide > ^^ > > patches, or 2.4 maybe...)? > > I hope that is supposed to be 'recent', because with the current TCQ > implementation listed in the specs Linux might as well not support it :) > It's simply not worth it. Exactly, Jens has seen the ugly beast because I have worked on coding it. I am working to get IBM to change the method of doing this to make it sane, but its not now. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
The Register (fwd)
http://www.theregister.co.uk/content/2/14907.html Everyone, do not reply to this. Because I know that Bill G. has a psuedo name here and I have not figured it out yet otherwise I would sent this direct. This is a personal poke at him, that they ingnored the subject until figuring out that Linux was a member and would have to conform to the initial SPEC that we had input on and they did not! The next punch will be to deliver adapter support before them! Also any other things that are turning quietly in the land of ATA. Cheers All, Andre Hedrick Linux ATA Development Title: The Register 28 November 2000 Update: 00:04 GMT Linux in, Redmond out of Serial ATA party By: Andrew Orlowski in San Francisco Posted: 22/11/2000 at 02:15 GMT The Serial ATA working group, charged with replacing clumsy parallel ribbons as the mass storage interface inside PCs, says it has completed version 1.0 of the specification. Publication had been mooted for 10 October, but the public version now ought to be available for comment by the end of the year. Members include APT, which provides intellectual property for storage interfaces, hard disk manufacturers Maxtor, IBM, Seagate and Quantum, and Dell and Intel. The only OS with representation on the group is Linux, and Redmond is a notable absentee - although sources say that it's now very keen to join. When it does, it won't have input to the first specification. But maybe that isn't such a big deal, as one of the promises of Serial ATA is that it presents the same view to the OS as a parallel ATA drive, and doesn't require special device drivers. Intel's Jeff Ravencraft, Serial ATA committee chair, told us that any additional effort to tweak the parallel ATA interface beyond the current ATA-100 spec wouldn't be worth the trouble. "We're not sure if it's doable, and even it was, it would be a very fragile innovation," he said. APT's business development manager Robert Streeby added that there would be reliability benefits for other PC components - particularly CPUs - once the requirement to support 5V I/O was removed. But the most obvious benefit is that PCs should finally get smaller - or at least in theory. "There's 72 square inches of cabling inside a PC. A thin replacement makes way for better ventilation, and smaller cases." The first private draft spec is intended to reach 1.5Gbps throughput speeds, although real transfer rates will max at 150Mbps. Further revisions are pegged to raise this to 300 and 600Mbps. The first spec will support a simple 1 to 1 connections, sources tell us, with one drive to one interface. It's hoped the 1.0 draft will be ratified and made public by the end of the year. Streeby sees devices coming on stream towards the end of next year, which is rather more aggressive a schedule than other will admit to. But with no modifications needed to the software stack, it's down to motherboard support, so it could conceivably squeak in. And with Apple removing the internal 1394 connectors from its latest G4 towers, Serial ATA should have the volume business to itself. ® Related Stories Linux beats Microsoft to support superfast disks Intel disses 1394 for own technology - again Today's top stories The Week's Headlines Discuss in The Register Forum BOFH 2K: Kit and Caboodle Flame of the Week Register Info Cash Register Register Full Coverage Register Links Hardware Round-up The Vulture Central Mailbag The Mac Channel If you want daily updates on news, enter your email address below, then click the 'Join List' button. Powered by ListBot
Re: IDE-driver not generalized enough ?
Yes, I have been working on that for some time. This requires that the macros be exported the arch-xxx/ide.h Additionally it takes more work to modify the request_io and release_io, but it is all doable. On Tue, 28 Nov 2000, Bjorn Wesen wrote: > Hi! Quick question: is it possible to write an IDE driver for a controller > that is not mappable using outp and those memory-mapped thingys ? > > I see all the nice overrideables in struct hwif_s but the main code still > uses OUT_BYTE which is hardcoded to an outb_p.. non-overrideable. Same > thing with ide_input/output_bytes, they do direct in/out accesses also > without consulting any hwif specific routine. > > So what do I do if my controller does not have a simple memory-mapping for > each IDE-register into the memory ? Do I have to clutter ide.h and ide.c > with #ifdef's or is there any cleaner abstraction on the way (something > like adding a hwif field to perform the OUT/IN-byte stuff, and > ide_xxput_bytes) ? > > (I have a solution working by replacing OUT_BYTE and ide_xxput_bytes, but > wanted to make it without having to patch the "official" ide.c/ide.h) > > Regards, > Bjorn > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: test-10 tulip "eth0 timed out" (smp, heavy IDE use)
Toby, Nothing can be done without the full re-write of the driver. The global request_io_lock is slammed into play way to early and release way to late. You will have to suffer with this flaw until the spin of 2.5. We are talking about a rewrite that is still at least 60 days from being ready for me to test. I still have to draft the recovery tools to mirror the disks for the data lose in the pre-alpha tests. On Tue, 28 Nov 2000, Toby Jaffey wrote: > Using 2.4-test10 I got a series of timeout errors on my tulip network > card (Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom, > Inc: Unknown device 0985 (rev 11)). Networking then completely stopped > working. Restarting the interface with ifconfig fixed the problem. > > I am using an SMP kernel, compiled with gcc 2.95.2 on an ABit BP6 (dual > celeron 500s, 128mb, PIIX4 using DMA). > > [log extract] > Nov 28 04:04:52 twoey kernel: NETDEV WATCHDOG: eth0: transmit timed out > Nov 28 04:04:52 twoey kernel: eth0: Transmit timed out, status fc664010, > CSR12 , resetting... > [end] > > This has only happenned once so far, I have not been able to repeat the > problem. At the time, I was simultanously using two cd drives to rip > audio cds with DMA turned on, also I was using both processors fully. > > -- > www.nott.ac.uk/~psystrj ... > /\_./o__ :' Mescaline, the only way to fly. ' > (/^/(_^~' '': > ___.(_.) '::: > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Patch: 2.4.0-test11ac4 version of pci and isapnp device ID'spatch
On Sat, 25 Nov 2000, Adam J. Richter wrote: > For those of you playing with Alan Cox's linux-2.4.0-test11ac4 > release, I have made a separate patch of the remaining device ID > changes which patches against that kernel and builds cleanly (the > primary difference is that it omits the files that have gained the > same ID tables in Alan's ac4 release). The patch is FTPable from: > > >ftp://ftp.yggdrasil.com/pub/dist/device_control/kernel/pci_id_tables-2.4.0-test11-ac4.patch4.gz > Hey Alan, are we now sorting sub-id's? Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE-SCSI/HPT366 Problem
Nope, I have yet to enable ATAPI-DMA because of the nature of the hooks. On Wed, 29 Nov 2000, --Damacus Porteng-- wrote: > LK Prodigies: > > This problem is current on the Linux-2.4.0-test11 kernel. Please tell me if > this has already been resolved - I am new to the list. > > Here is my setup: > Motherboard: Soyo 6BA+IV (built-in PIIX4 and HPT366 IDE controllers) > CDRWs: Yamaha 4416S (SCSI) & Yamaha 8424E (EIDE) > > Kernel: 2.4.0test11 -- I must use 2.3.X or 2.4.X since my main drives > are on the HPT366 channels. > > IDE: Using both HPT and PIIX chipsets. Base system drives are on > HPT366 channels. / == /dev/hde. Works fine. > > Software: cdrecord 1.8.1, cdrecord 1.9 > > Problem: > The problem lies with using my EIDE CDRW - I set it up properly using > IDE-SCSI. I can use my mp3tocdda shell script to encode mp3s to CD > (uses cdrecord as well) on the fly using either drive, however, when I > use cdrecord to write a data CD, the system hard-locks, no kernel > panic messages, and no Magic SysRQ keystroke works. > > Quite odd that I could do the cdrecord for audio tracks, but not > data.. > > Anyhow, I moved the CDRW to the PIIX4 channels (and changed my lilo > append line to make hda=scsi, instead of hdg=scsi) and now both the > mp3tocdda script and cdrecord for data images works fine. > > I'm thinking it's a problem with HPT366, since IDE-SCSI/PIIX4 worked > fine with the setup, and cdrecord has always been a working package > for me. > > Also, the HPT366 setup screen (VERY simple) shows the CDRW using MW > DMA 2 and is unchangable thru the HPT366 BIOS. Is there something > I should be doing with hdparm on the CD device? > > > Thanks in advance, > > Damacus Porteng > > -- > Damnit, Linus, I'm a network admin, not a kernel hacker! > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE-SCSI/HPT366 Problem
On Wed, 29 Nov 2000, Kurt Garloff wrote: > Strange. If you read data from the harddisk on an IDE channel and write it > (with cdrecord) to some CDRW on the same IDE channel, you have to expect > trouble: As with IDE there is no disconnect from the bus (as opposed to > SCSI), you risk buffer underruns. > A lockup however is not to be expected :-( It is completely expected bacause of teh active timing changes done on this chipset design. The timings are for ATA DMA and not ATAPI. You should expect a 100% hardlock on mistimed IO access. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
On Wed, 29 Nov 2000, Alan Cox wrote: > > You are wrong: If you modify the kernel you have to make it available for > > anyone who wishes to use it; that's also in the GPL. You can't add stuff > > No it isnt. Some people seem to think it is. You only have to provide a > change if you give someone the binaries concerned. Some people also think > that 'linking' clauses mean they can just direct the customer to do the link, > that also would appear to be untrue in legal precedent - the law cares about > the intent. Of the list of poeple here, only Alan was present with the discussion of the terms of how the FASTTRAK SCSI-Emulation API to ATA was defined. Since you are not in the position to define the terms of how the interaction between the two subsystems work, you have no clue that building it into the kernel will fail! Second read the causes about "COMMERIAL INTENT", somewhere around section 7 paragraph 3. I have defined the terms that are acceptable to a binary module that incorporates GPL code of MINE! This I DEFINE THE TERMS, and they are module only! Regards, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
> Anything else would mean that I can send E-Mail to Linus Torvalds > every five minutes and request a verbatim copy of his current hacking > kernel tree as it is under GPL, which he is the forced to give to me > because of the GPL. This would be utter nonsense. Ask me for the GPL code that I wrote as the author, that am working on at the rates define. I will tell you to go right to hell on a bobsled! Oh and I will push to make sure you do not waste time getting there. You are being a total ASS. As the author of GPL code I have the right to pull the GPL if I wish and never update or publish the updates, and YOU have not legal authority to force me to send you SHIT! Does that make it real clear or not? Later, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Fasttrak100 questions...
On Wed, 29 Nov 2000, James A Sutherland wrote: > Nope. RMS defined the terms which apply to GPL code. You are free to define any > other terms you like for your own code, but it is no longer GPLed in that case. And the code for FASTTRAK is not GPL, James we did this once before. If Promise were to promote and tell people to link the object to the kernel every again, I will begin a law suit. Because the harm and damage caused to the ATA subsystem is not repairable. The damages are not limited. Now I worked with Promise to get this all clean as a module that could be updated as there kernel evolves. If all of you go and SCREW up the work I did to try an allow a company that is not generally friendly to Linux as far as IP and technology issues are related, then I will stop trying to get them to expose the IP for the RAID signatures to export to the Linux SOFT RAID. THIS WILL ROYALLY SCREW EVERYBODY! HAHAHAHA. Now do not go dorking things that I am trying to make make public. This is really pissing me off! Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Fasttrak Final Point....
The terms of use of the pdc202xx.c code was handled before I GPLed that code. Thus there are no arguments that will allow GPL to touch the issue. With that said, I am hoping this dies. It is very hard to get companies to work with Linux if all the get is flames from the general masses. Regards, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE-SCSI/HPT366 Problem
On Wed, 29 Nov 2000, Damacus Porteng wrote: > Andre: > > Is that to say that I'd experience this problem with any EIDE CDRW used on one > of the HPT366 channels, or is it to say that only several CDRWs aren't > supported under this chipset? If you want to run it under PIO mode and not do DMAing then it will work. Also it goes for any device that does ATAPI DMA and not ATA DMA. There is a difference! Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test11 ext2 fs corruption
On Wed, 29 Nov 2000, Jens Axboe wrote: > On Wed, Nov 29 2000, Andrea Arcangeli wrote: > > Side note: that could generate mem/io corruption only on headactive devices > > (like IDE). > > Yep, that's why I told Linus it was a long shot and couldn't possibly > account for all the corruption cases reported. And one would expect > fs corruption to go with that as well. So it's of course a long shot, > but still worth trying for Petr. Okay, I have spent part of the afternoon kicking my FW around and have not followed all of the thread. However we are talking FSC and ATA so what are the details? And where are we poking into the driver. Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE_TAPE problem wiht ONSTREAM DI30
On Sun, 3 Dec 2000, Eckhard Jokisch wrote: > Am Don, 30 Nov 2000 schrieben Sie: > > On Thu, Nov 30, 2000 at 04:26:09PM +, Eckhard Jokisch wrote: > > > > > > I tried the ide-tape driver for several weeks now. And after some time during > > > writing or reading tar stops because of errors. > > > > > > Error messages are: > > > Nov 30 15:32:20 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0, > > > asc = 0, ascq = 2 Nov 30 15:32:25 eckhard last message repeated 1000 times > > > Nov 30 15:32:25 kernel: ide-tape: ht0: unrecovered read error on logical block >number 461706, skipping You have to love the new ARD media... > > > > I ran into such problems since februari or so and have been in contact with > > the ide-tape developers and Onstream about it. > > I recently volunteered to try improving the end of media handling (basicly by > > implementing early warning EOM) but so far have not had much time to work on it... > > Where can I start to do that? > Can you tell me how I can set the debug_level to 3 or 5? > Why do I get this errors on make modules when I compile the driver with > IDETAPE_DEBUG_LOG_VERBOSE to 1 in ide-tape.c?: gcc -D__KERNEL__ > -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer > -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686 > -malign-functions=4 -DMODULE -DMODVERSIONS -include > /usr/src/linux/include/linux/modversions.h -c -o ide-tape.o ide-tape.c > ide-tape.c: In function `idetape_sense_key_verbose': ide-tape.c:1395: warning: > function returns address of local variable ide-tape.c: In function > `idetape_command_key_verbose': ide-tape.c:1413: parse error before `case' > ide-tape.c:1424: warning: function returns address of local variable make[2]: > *** [ide-tape.o] Error 1 make[2]: Leaving directory > `/src/2.4-test11/drivers/ide' make[1]: *** [_modsubdir_ide] Error 2 make[1]: > Leaving directory `/src/2.4-test11/drivers' make: *** [_mod_drivers] Error 2 This I can fix, but the decoding noise makers are still in progress. Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Re[2]: DMA !NOT ONLY! for triton again...
Guennadi, I have watched this and even if UDMA is not supported cleanly by the drive, the classic ATA-2 Multi-wrod DMA should be. There was a time in the past where WDC had some problems, but they have fixed most if not all with "modern" drives. I will be at WDC in two weeks, and I can raise the issues with them. Please spell them out completely. Regards, On Mon, 4 Dec 2000, Guennadi Liakhovetski wrote: > Well, yes, I thought they could not have known:-)) I'm absolutely stuck. If disk is >fine, chipset is fine and supported by the kernel, then BIOS doesn't (or shouldn't) >make a difference... Then WHAT ON THE EARTH??? Mike, have you been able to recall >what BIOS option turned DMA on? Shall I write to Andre Hedrick directly? Or is there >a mailing-list smth. like linux-ide? > > > Now, the question is, can we trust a hard drive manufacturer > > support tech to know what they're talking about, with evidence to > > the contrary? :) > > Thanks > Guennadi > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.17 + ide patches + 61gb ibm disc = problem
On Tue, 5 Dec 2000, Robert B. Easter wrote: > > Uniform Multi-Platform E-IDE driver Revision: 6.30 > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > PIIX4: IDE controller on PCI bus 00 dev 21 > > PIIX4: chipset revision 1 > > PIIX4: not 100% native mode: will probe irqs later > > ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:pio, hdb:DMA > > ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:DMA > > hdb: IBM-DTLA-307060, ATA DISK drive > > hdd: IBM-DTLA-307060, ATA DISK drive > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > ide1 at 0x170-0x177,0x376 on irq 15 > > hdb: IBM-DTLA-307060, 58644MB w/1916kB Cache, CHS=7476/255/63, UDMA(33) > > hdd: IBM-DTLA-307060, 58644MB w/1916kB Cache, CHS=119150/16/63, UDMA(33) You have the classic BIOS issue it only works half way. pass the geometries to fix one side of the other. > > hdd1 [events: 0001](write) hdd1's sb offset: 60051456 > > hdb1 [events: 0001](write) hdb1's sb offset: 60050816 > > > > > I don't understand why you have set them to be slaves when they are the only > drives on the ports. Shouldn't you be setting the jumpers on both drives > into the Single Drive (default) settings? I always thought the Master and > Slave positions are to be used only when connecting two drives on one port. > > hda and hdc should be the devices. This is true, what are you running in this bizzare mode? Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Problems with PDC202xx driver
<4>ide: Assuming 33MHz system bus speed for PIO modes <4>AMD7409: IDE controller on PCI bus 00 dev 39 <4>AMD7409: chipset revision 7 <4>AMD7409: not 100% native mode: will probe irqs later <4>ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA <4>ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA <4>PDC20267: IDE controller on PCI bus 00 dev 48 <4>PDC20267: chipset revision 2 <4>PDC20267: not 100% native mode: will probe irqs later <4>PDC20267: ROM enabled at 0xe800 <4>PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. <4>ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:DMA, hdf:pio <4>ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:DMA, hdh:pio <4>hda: QUANTUM FIREBALL CX13.0A, ATA DISK drive <4>hdb: QUANTUM FIREBALL CR4.3A, ATA DISK drive <4>hdc: ATAPI CD ROM DRIVE 50X MAX, ATAPI CDROM drive <4>hde: Maxtor 91536H2, ATA DISK drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <4>ide2 at 0xc400-0xc407,0xc802 on irq 11 Nope you have a chipset that is designed wrong. On Wed, 6 Dec 2000, James Lamanna wrote: > Whenever I tried using the PDC202xx driver in > 2.4-test11 I kept receiving the line in dmsg: > PDC20267: neither IDE port enabled (BIOS) > > I traced this to ide-pci.c, line 606: > if (e->reg && (pci_read_config_byte(dev, e->reg, &tmp) > || (tmp & e->mask) != e->val)) > continue; /* port not enabled */ > > This if was returning true, and skipping the rest of the loop > (which sets up the ioports...) > So it looks like to me that it's not enabling the IOPorts > for this chipset. This seems like a really bad thing, considering > that I can gain no access to the drives currently using this driver. > Any suggestions? > > Thanks, > --James Lamanna > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: DMA !NOT ONLY! for triton again...
On Wed, 6 Dec 2000, Guennadi Liakhovetski wrote: > > Re: PCI clock... Something somewhere (can't find now) made me think that > > my MB is setting the PCI clock synchronously with the CPU clock, i.e. it > > is 25MHz in my case... Any ideas where I could see it?:-) > > I found it - it's in ide.txt too. Isn't Mark Lord around, btw?:-) Maybe he > could spread some light on the problem... > > Thanks > Guennadi > ___ > > Dr. Guennadi V. Liakhovetski > Department of Applied Mathematics > University of Sheffield, U.K. > email: [EMAIL PROTECTED] True Mark Lord is gone, but I do not go by my middle name Mark. I thought I gave you answer. Cheers, Andre (Mark) Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Trashing ext2 with hdparm
No way that this could cause corruption it is a read-only test. On Wed, 6 Dec 2000, Udo A. Steinberg wrote: > > Hi, > > Following the discussion in another thread where someone > reported fs corruption when enabling DMA with hdparm, I've > played around with hdparm and found that even the rather > harmless hdparm operations are capable of trashing an ext2 > filesystem quite nicely. > > hdparm version is 3.9 > > hdparm -tT /dev/hdb1 does the trick here. > > After that, several files are corrupted, such as /etc/mtab. > Reboot+fsck fixes the problem, however e2fsck never finds > any errors in the fs on disk. > > I'm quite sure that earlier kernel versions didn't exhibit > this kind of behaviour, although I'm not quite sure at > which point things started to break. I have test12-pre6 > here atm, but I have test-11 still lying around and will > test that in a bit. > > The drive in question is an IBM-DTLA307030 running in > UDMA Mode 5 on a PDC20265, chipset revision 2. > > I haven't seen any other corruption other than that which > hdparm reliably triggers. Might as well be a bug in hdparm, > so someone else might also want to check... > > -Udo. > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: system hang and corrupt ext2 filesystem with test12-pre5
I have not tested of checked the nature of the PCD20265 which is the onboard version. On Wed, 6 Dec 2000, Skip Collins wrote: > After running 2.4.0-test11 for a while, my system would occasionally > hang during heavy disk activity resulting in a corrupt ext2 filesystem. > Fortunately, none of the damage has been irrecoverable. I checked > linux-kernel to see if anyone else was seeing the same thing. The recent > threads on corruption seemed to be consistent with the behavior I saw: > ide disk access light remains lit, system hangs, fsck finds bad inodes. > I think test12-pre5 was supposed to fix the problem. But after upgrading > my kernel, I can still get the errors. > > I have a 900MHz Athlon/Asus A7V mobo system with an onboard ata100 > promise controller. I have only had problems when my ata100/udma5 > harddrive is connected to the promise controller. Using the ATA66 ide > bus eliminates the problem. I typically see the corruption when copying > large (~1GB) files such as vmware virtual disks. It also happens > frequently inside vmware when doing heavy disk access things like > installing software or defragging a win2000 virtual disk. > > For now I am going to fall back to the slower ide bus. But I wanted to > let people know that there still may be problems with ext2 corruption in > the latest test kernel. > > sc > please cc any replies to me > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: system hang and corrupt ext2 filesystem with test12-pre5
On Wed, 6 Dec 2000, Udo A. Steinberg wrote: > I also have an A7V and both of my IBM IDE drives are connected to the > Promise controller, running in UDMA-5 mode. There hasn't been any > corruption on either of the drives that had to do with UDMA-5 mode. > And the ext2 bugs that 2.4 kernels had, have been fixed in the latest > versions. > > What drive are you using? AFAIR, Andre Hedrick once said certain Maxtor > drives aren't quite safe with DMA. WHOA That was more than 3 years ago but that is not to day. I have been working with them internally to make things work with Linux. They have the fastest drive to date. When running internal benchmarks one can see XFER rates that go beyond 85MB/sec. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Trashing ext2 with hdparm
Did you set and mount a "/var/shm" point? On Wed, 6 Dec 2000, Udo A. Steinberg wrote: > Hi, > > Andre Hedrick wrote: > > > > No way that this could cause corruption it is a read-only test. > > As others pointed out, it's probably something related to shared > memory, but it's definitely hdparm that triggers it. I haven't > got the hdparm sources here to look at what exactly it's doing, > but there is corruption going on, not on disk, but definitely in > memory. > > -Udo. > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Problems with PDC202xx driver
On Wed, 6 Dec 2000, James Lamanna wrote: > So you are saying that the Promise Fasttrak 100 chipset is > designed wrong? Because that's exactly what I have. > and isn't this driver supposed to support it? > Or are you saying the IDE controller on the MB is wrong? Clarify things first. PDC20267 is the Ultra100 core. PDC20267 w/ a pull-up resistor reports its device class as RAID, Fasttrak100. Now if you have a device that reports it storage class as RAID then it may misbehave. Otherwise, if it is reporting "Unknown Mass Storage" then you have an Ultra/ATA controller. There are two different BIOS cores for each design. Linux cleanly supports the BIOS cores know as "Ultra" and not the ones know as "Fasttrak". Because there are different PCI config space setups for each core then we have a problem unless we go and poke around for storage classes. Does that help? Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Problems with PDC202xx driver
On Wed, 6 Dec 2000, James Lamanna wrote: > Here is an excerpt from /proc/pci: > > Bus 0, device 11, function 0: > RAID bus controller: Promise Technology, Inc. 20267 (rev 2). > IRQ 10. > Master Capable. Latency=32. > I/O at 0x9400 [0x9407]. > I/O at 0x9000 [0x9003]. > I/O at 0x8800 [0x8807]. > I/O at 0x8400 [0x8403]. > I/O at 0x8000 [0x803f]. > Non-prefetchable 32 bit memory at 0xd500 [0xd501]. > Bus 0, device 17, function 0: > Unknown mass storage controller: Promise Technology, Inc. 20265 (rev 2). > IRQ 10. > Master Capable. Latency=32. > I/O at 0x7800 [0x7807]. > I/O at 0x7400 [0x7403]. > I/O at 0x7000 [0x7007]. > I/O at 0x6800 [0x6803]. > I/O at 0x6400 [0x643f]. > Non-prefetchable 32 bit memory at 0xd480 [0xd481]. No each device reports itself differently here. Bus 0, device 11, function 0: == 20267 Bus 0, device 17, function 0: == 20265 You bought a Fasttrak 100 and your mainboard came with an Ultra 100 > > Is there a plan to support the Fasttrak BIOS core at some point (I hope..) > So I guess I'm stuck with loading their proprietary module whenever I want > to use the drive Yep, until they realize that their simple IP is nothing, and want to export the raid calls to the Linux Raid Engine, you are "stuck". > But thanks for the clarification. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RASTER driver for Xerox Printers
Who has one or knows how to kick one to life? Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: New CD-R high capacity drive specs are coming. (fwd)
Why bother, Calimetrics has a native driver solution that does a modulation on the beam power of the laser that will triple or quadruple the current media densities with out getting new media or new drives. Just so you know that all of these new drive specs that claim to be coming, I have more than likely seen or was part of, this one did not evern register as a point of interest. I call this stuff the ONION CD, becasue the energy require to burn a 10 layer media, regardless that you use a dye laser, will rip appart. As long as they stay in the WORM mode it may be safe, but if they attemp CDRW then it will die. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development On Thu, 7 Dec 2000, M Sweger wrote: > > Hi, > >See the article below. > > I just read that the specs are out for three different types of CD-R > drives in terms of disk capacity and speeds from Constellation 3D,and it > is heading towards manufacturing. It's great for movies and coporate > archiving, but was degraded for the consumer market -- Nothing above > 5Gb/side for the consumer whereas for the coporate it's 200Gb/side. I > don't think it will compete for the PC market unless the disk capacities > are upped! Probably purposely degraded so that you can't copy a HDTV DVD > to your PC CD-R disk. Here is the > http://biz.yahoo.com/bw/001207/ny_constel.html">link - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
FS Corruption Again, with known cause, and solution...
Okay gang, here is the skinny and it is fat and ugly! Sometime ago some braindead engineers, at an unamed company that developed the first DMA engine, thought it was a good idea to wack and stop the DMA engine if there was a transaction delay of 1 micro-second or more; regardless if the transfer was done! It is possible that with everyone following their lead, this may be a global ASIC error. This would explain the rise-fall-rise of the reports. Rise == the arrive of the hardware error Fall == Andrea A. elevator working to fake a scatter-gather (IMHO) Fall == attempt to address the timeouts with expiry function (may keep) Rise == newer larger drives that can produce out-of-bounds seeking. How to kill it. Basically, issue the abort of the transfer and requeue the request, and try again. Problem, if the seek repeats the process and we continuily requeue the request then we get into other issues. Workaround 1, maintain a barf counter and after N barfs perform the task in a forced PIO regardless (HUGE peformance hit, but good data). Workaround 2, slice the request after first barf and make it smaller and retry (nasty-dirty and we have to dump dma-buffers and make new-ones). Workaround 3, give up and goto bed for now Now who wants to jump on this and work with me on the re-insert of the request and try again, before we do tests on WA 1 & 2? I am brain dead from reading the code sent to me by the vender because it is been hacked and abused to death! They do not even like to show how fugly it is! Cheers, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Big IDE HD unclipping and IBM drive
On Fri, 8 Dec 2000, Matan Ziv-Av wrote: > > Hi, > > > I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with > large disks. I use a jumper to clip it to 32GB size, so the bios can > boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB, > and not the true size, and even trying to set the correct size with > WIN_SET_MAX fails. Is there a way to use this combination (Bios, HD, > Linux)? Yep you have to use code/patches that are not in the standard kernel. Which kernel are you using? Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: HPT366 + SMP = slight corruption in 2.3.99 - 2.4.0-11
This has the missing ide-pci code from 2.2.
It stablized my BP6 on the HPT core.
Cheers,
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
diff -urN linux-2.4.0-t12-7-pristine/drivers/ide/cs5530.c
linux-2.4.0-t12-7/drivers/ide/cs5530.c
--- linux-2.4.0-t12-7-pristine/drivers/ide/cs5530.c Tue Jun 20 07:52:36 2000
+++ linux-2.4.0-t12-7/drivers/ide/cs5530.c Fri Dec 8 00:14:55 2000
@@ -257,6 +257,14 @@
unsigned short pcicmd = 0;
unsigned long flags;
+#if defined(DISPLAY_CS5530_TIMINGS) && defined(CONFIG_PROC_FS)
+ if (!cs5530_proc) {
+ cs5530_proc = 1;
+ bmide_dev = dev;
+ cs5530_display_info = &cs5530_get_info;
+ }
+#endif /* DISPLAY_CS5530_TIMINGS && CONFIG_PROC_FS */
+
pci_for_each_dev (dev) {
if (dev->vendor == PCI_VENDOR_ID_CYRIX) {
switch (dev->device) {
@@ -326,14 +334,6 @@
pci_write_config_byte(master_0, 0x43, 0xc1);
restore_flags(flags);
-
-#if defined(DISPLAY_CS5530_TIMINGS) && defined(CONFIG_PROC_FS)
- if (!cs5530_proc) {
- cs5530_proc = 1;
- bmide_dev = dev;
- cs5530_display_info = &cs5530_get_info;
- }
-#endif /* DISPLAY_CS5530_TIMINGS && CONFIG_PROC_FS */
return 0;
}
diff -urN linux-2.4.0-t12-7-pristine/drivers/ide/hpt366.c
linux-2.4.0-t12-7/drivers/ide/hpt366.c
--- linux-2.4.0-t12-7-pristine/drivers/ide/hpt366.c Tue Nov 7 11:02:24 2000
+++ linux-2.4.0-t12-7/drivers/ide/hpt366.c Fri Dec 8 00:14:55 2000
@@ -346,6 +346,9 @@
static int hpt3xx_tune_chipset (ide_drive_t *drive, byte speed)
{
+ if ((drive->media != ide_disk) && (speed < XFER_SW_DMA_0))
+ return -1;
+
if (!drive->init_speed)
drive->init_speed = speed;
@@ -428,6 +431,9 @@
byte ultra66= eighty_ninty_three(drive);
int rval;
+ if ((drive->media != ide_disk) && (speed < XFER_SW_DMA_0))
+ return ((int) ide_dma_off_quietly);
+
if ((id->dma_ultra & 0x0020) &&
(!check_in_drive_lists(drive, bad_ata100_5)) &&
(HPT370_ALLOW_ATA100_5) &&
@@ -617,8 +623,14 @@
pci_write_config_byte(dev, PCI_ROM_ADDRESS,
dev->resource[PCI_ROM_RESOURCE].start | PCI_ROM_ADDRESS_ENABLE);
pci_read_config_byte(dev, PCI_CACHE_LINE_SIZE, &test);
+
+#if 0
if (test != 0x08)
pci_write_config_byte(dev, PCI_CACHE_LINE_SIZE, 0x08);
+#else
+ if (test != (L1_CACHE_BYTES / 4))
+ pci_write_config_byte(dev, PCI_CACHE_LINE_SIZE, (L1_CACHE_BYTES / 4));
+#endif
pci_read_config_byte(dev, PCI_LATENCY_TIMER, &test);
if (test != 0x78)
diff -urN linux-2.4.0-t12-7-pristine/drivers/ide/ide-dma.c
linux-2.4.0-t12-7/drivers/ide/ide-dma.c
--- linux-2.4.0-t12-7-pristine/drivers/ide/ide-dma.cThu Jul 27 16:40:57 2000
+++ linux-2.4.0-t12-7/drivers/ide/ide-dma.c Fri Dec 8 00:50:04 2000
@@ -90,6 +90,8 @@
#include
#include
+#undef CONFIG_BLK_DEV_IDEDMA_TIMEOUT
+
extern char *ide_dmafunc_verbose(ide_dma_action_t dmafunc);
#ifdef CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
@@ -515,9 +517,17 @@
return check_drive_lists(drive, (func == ide_dma_good_drive));
case ide_dma_verbose:
return report_drive_dmaing(drive);
+ case ide_dma_timeout:
+#ifdef CONFIG_BLK_DEV_IDEDMA_TIMEOUT
+ /*
+* Have to issue an abort and requeue the request
+* DMA engine got turned off by a goofy ASIC, and
+* we have to clean up the mess, and here is as good
+* as any. Do it globally for all chipsets.
+*/
+#endif /* CONFIG_BLK_DEV_IDEDMA_TIMEOUT */
case ide_dma_retune:
case ide_dma_lostirq:
- case ide_dma_timeout:
printk("ide_dmaproc: chipset supported %s func only: %d\n",
ide_dmafunc_verbose(func), func);
return 1;
default:
diff -urN linux-2.4.0-t12-7-pristine/drivers/ide/ide-pci.c
linux-2.4.0-t12-7/drivers/ide/ide-pci.c
--- linux-2.4.0-t12-7-pristine/drivers/ide/ide-pci.cTue Nov 7 11:02:24 2000
+++ linux-2.4.0-t12-7/drivers/ide/ide-pci.c Fri Dec 8 00:14:55 2000
@@ -753,6 +753,12 @@
if (hpt363_shared_pin && hpt363_shared_irq) {
d->bootable = ON_BOARD;
printk("%s: onboard version of chipset, pin1=%d
pin2=%d\n", d->name, pin1, pin2);
+#if 1
+
Re: Linux 2.2.18 almost...
On Sat, 9 Dec 2000, Michael Rothwell wrote: > Alan Cox wrote: > > > > The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place. > > I'll move it over tomorrow if nobody reports any horrors, missing files etc > > > Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26" > > can't find file to patch at input line 38909 > Perhaps you used the wrong -p or --strip option? > The text leading up to this was: > -- > |diff -u --new-file --recursive --exclude-from /usr/src/exclude > v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds > |--- v2.2.17/arch/i386/vmlinux.ldsWed May 3 21:22:13 2000 > |+++ linux/arch/i386/vmlinux.lds Sat Dec 9 21:23:21 2000 So do something silly like cp linux/arch/i386/vmlinux.lds.S linux/arch/i386/vmlinux.lds and you will see that the patch against the files are identical. /linux/arch/i386/Makefile arch/i386/vmlinux.lds: arch/i386/vmlinux.lds.S FORCE $(CPP) -C -P -I$(HPATH) -imacros $(HPATH)/asm-i386/page_offset.h -Ui386 arch/i386/vmlinux.lds.S >arch/i386/vmlinux.lds All it is is a leftover file Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [Fwd: NTFS repair tools]
On Sat, 9 Dec 2000, Ren Haddock wrote: > I think part of the problem is that there are other things labeled > DANGEROUS that actually do work fairly reliably (offhand, I'm thinking > off the IDE config stuff..). Perhaps it needs to explicitely say > 'This is broken and is gauranteed to destroy your data. Do not use it' DANGEROUS == GO_FOR_IT_DUMB_ARSE_SCREW_YOURSELF_WILDLY This is the intent, when I put and started the DANGEROUS settings. Because the volitale nature of extreme alpha code in the beginning. However as time passed, people did not think it had meaning, but that is what it orginally was defined by me. This is UNIX, and to quote one of HPA's signatures, "unix gives you enough rope to hang yourself" My personal favorite: You are going to shoot yourself in the head, aim carefully! How well you aim determines if you get a second chance! Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development PS: for the pc language crowd, note that I use "arse"!!! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: HPT366 + SMP = slight corruption in 2.3.99 - 2.4.0-11
On Sun, 10 Dec 2000, Hakan Lennestal wrote: > The problem being that the kernel hangs after a dma timeout in the > partition detection phase during bootup for speeds higher than udma 44. > This is an IBM-DTLA-307030 connected to a hpt366 pci card on a BH6 > motherboard. Well try the latest out there...test12-pre7. Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: HPT366 + SMP = slight corruption in 2.3.99 - 2.4.0-11
On Sun, 10 Dec 2000, Hakan Lennestal wrote: > In message <[EMAIL PROTECTED]>, And > re Hedrick writes: > > On Sun, 10 Dec 2000, Hakan Lennestal wrote: > > > > > The problem being that the kernel hangs after a dma timeout in the > > > partition detection phase during bootup for speeds higher than udma 44. > > > This is an IBM-DTLA-307030 connected to a hpt366 pci card on a BH6 > > > motherboard. > > > > Well try the latest out there...test12-pre7. > > Hi ! > > This is with test12-pre7 and HPT-bios 1.27. test12-pre8 and 2.2.18 is out and I do not chase BIOS revs in general. I work off the originals HPT366 1.07 this is because the lowest comman variable must be addressed and hope that the new stuff will not fail the backwards compatablity issue. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] I-Opener fix (again)
Basically if the setting of * "hdx=flash" : allows for more than one ata_flash disk to be * registered. In most cases, only one device * will be present. fails then I will look into this but, the breaking of laptops that have CFA devices that do not come on channels in a pair canb not happen. If you have a vender unique setting that will follow always the way I-Opener's are setup then that is better. Cheers, On Mon, 11 Dec 2000 [EMAIL PROTECTED] wrote: > It's been a few months (and a couple of kernel releases) since I mentioned this > before and it doesn't look like it's made it in, and I haven't seen any more > comments on it in the list archives, so I'm bringing it up again in case it > just got forgotten about somewhere along the line.. > > As I remember, Andre Hedrick had asked for clarification on my original post, > and I sent a followup message in response, but now I can't seem to find it > anywhere in the archives, so I don't know whether it never made it out of my > mailer or.. > > In any case, attached is a patch (against 2.4.0pre11) which fixes the bug which > causes disk detection issues on I-Opener (and possibly other unusual) hardware. > > The problem is that the code assumes that a flash-disk will always be the > primary disk on an interface, but on the I-Opener this is not always the case. > If a traditional disk is primary, and a flashdisk is secondary, the detection > code (wrongly) disables the primary disk that it had already previously > detected. > > I would like to see this make it into the official source as it's a very small > change that fixes some obviously wrong behavior.. > > -alex > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE bugs for intel 440LX chipset in Test12?
Anyone with a PIIX4,PIIX4AB,PIIX4EB has a hardware bug. If many of the chipset makers followed and reverse engineered their stuff against that bug then ths explains all of the timeout issues. I am working on a fix, but do not have one yet. Cheers, On Wed, 13 Dec 2000, safemode wrote: > All I can say right now is that enabling DMA on a 440LX chipset with > 2.4.0-test12 or any other kernel I can remember has caused DMA timeout > and ide-reset problems. Disabling dma on the harddrives doesn't help > that much either, I still get ide resets. What I'm looking for right > now is some information on how to log what the kernel recieves from the > harddrive and possibly what it sends so I can give rik some better > information on what's going on in this chipset. Thanks. > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.19pre1
For the Nth time I have been asked so I will has you the Nth++ time. Patch or wait.. Nobody is to comment against this thread, this is an Alan & Andre issue. Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
SerialATA Release, sortof........
FYI The Serial ATA specification (500 pages) is now available to the public under certain "click-to-accept" conditions. Click the "specification" link at the bottom of the home page at http://www.serialata.org/. I hope the conditions are acceptable. The file is zipped MS Word. This just for those that care...please do not ask me for my copy as I am a member of this working group and bound under the NDA. Regards, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: SerialATA Release, sortof........
On Tue, 19 Dec 2000, David Weinehall wrote: > On Mon, Dec 18, 2000 at 01:27:07PM -0800, Andre Hedrick wrote: > > > > FYI > > > > The Serial ATA specification (500 pages) is now available to the public > > under certain "click-to-accept" conditions. Click the "specification" > > link at the bottom of the home page at http://www.serialata.org/. > > I hope the conditions are acceptable. The file is zipped MS Word. > > Well, I think that most people can be happy with the conditions. Now, > the format, that's a completely different issue. With all your > influence, I bet you could persuade them to at least run the document > through Acrobat Distiller to turn it into a .pdf?! My bad for forwarding info from internal. I knew that my copies were in PDF, but did not know if they combined all the erratas in to a newer doc or what Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Blow Torch (Re: lockups from heavy IDE/CD-ROM usage)
On Thu, 21 Dec 2000, safemode wrote: > I get this on the 440LX with the same DMA timeout message. Everyone says it's > the board's fault as well. Funny. Anyways this happens accross just about > any Dev kernel but more so in the -test12 and up versions. . Test10 works > fine without locking. Blaming the hardware reminds me of the help given by > some other company I can't seem to remember the name to. 29063507.pdf Page 22 sections 9,10 What is the Intel solution to the is system hang? 29063507.pdf Page 25 section 16 Is this erratum valid to include all PIIX4-AB/EB, PIIX3, and PIIX a/b. It is the DAMN hardware and quit BITCHING. I told everyone once that I was working on this issue. If you think you can fix it before me, be my guest. I have given you the INTEL doc numbers and the page and the section. Go read. Regards Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: The NSA's Security-Enhanced Linux (fwd)
On Fri, 22 Dec 2000, Alex Belits wrote: > ...so this is the result of Becker's employment at NASA and government's > legal weirdness (no, I have no idea, why of all possible choices > "Director, National Security Agency" must represent US government for > copyright purpose). Director is just under "The Office Inspector General of NSA". Basically a division head that reports only to the OIG. Trust that I know what I am talking about. ;-) Cheers, Andre Hedrick CTO Timpanogas Research Group EVP Linux Development, TRG Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Microsoft Withdraws Linux NTFS Threats
On Sun, 1 Oct 2000, Jeff V. Merkey wrote: > > I will again be able to offer these NTFS tools to repair NTFS > partitions. Please begin reforwarding requests from folks with trashed > disks to me, and I'll be able to assist folks. Microsoft has apologized > and withdrawn their statements. > > We are very happy this thread ended on a happy note, instead of in > court. Microsoft will take no action against us for NTFS development on > Linux, which can now proceed without concern. Jeff ... It is fun, but I was not ware that scale of this mess was so great. All I did was to make the request for Microsoft not to blow things out of proportion. Sheesh, by letting us, without noise or action, create R/W support of NTFS for Linux they would have been able to give the appearence that they were behaving. Regardless, congrates on using the entry point. I just hope everyone at Mircosoft is still there. I would feel really bad if an aquiantence of my there had reprocussions. We would need to find a way to help them out, if they took it on the chin for us. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Microsoft Withdraws Linux NTFS Threats
On Sun, 1 Oct 2000, Jeff V. Merkey wrote: > Andre, > > This is very much a compliment of you coming from them -- they apparently > took you very seriously and viewed your proposal as a serious matter. It was > a great roller coaster ride -- let's do it again some time. Jeff, I went to slashdot.org to read the story. There was a historical referrence, in the beginning, that implies that I was accussing Microsoft of using Linux code. The reality was that I offered to help them with the solution I was working on because of the huge mess that the great taskfile debate brought out. People were pointing out that because I was exposing how to abuse it in the kernel and that a policy of preventing harmfal combinations was not acceptable. Since this information could/would/did spill over to the script kiddies, I thought it was the better part of valor (sp) to inform an aquaintance at Microsoft of the potential problem that they could see. Only because I respect that person (at MS) did I even consider discussing the issue. If they want to take a jesture of kindness and twist it to imply I am blackmailing them, Bill's view of the world is very sinical (sp). Cheers, Andre Hedrick The Linux ATA/IDE guy PS. I am not an english major be a former astronomer, so do not send me a grade on my grammer and spelling. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: hdparm -d 1 fail test9-pre8
On Mon, 2 Oct 2000, Mike Galbraith wrote:
> Greetings,
>
> In order for hdparm -d 1 to work in test9-pre8, I had to reverse
> this change. (Without being able to enable dma, performance here
> is muy el-stinko;-) Is enabling dma manually now forbidden? (or
> am I maybe missing something else?)
>
> diff -urN linux-2.4.0-test9-pre7/drivers/ide/ide-pci.c
>linux-2.4.0-test9-pre8/drivers/ide/ide-pci.c
> --- linux-2.4.0-test9-pre7/drivers/ide/ide-pci.c Sun Jul 30 06:30:13 2000
> +++ linux-2.4.0-test9-pre8/drivers/ide/ide-pci.c Mon Oct 2 10:11:36 2000
> @@ -538,7 +538,7 @@
>* Can we trust the reported IRQ?
>*/
> pciirq = dev->irq;
> - if ((dev->class & ~(0xfa)) != ((PCI_CLASS_STORAGE_IDE << 8) | 5)) {
> + if ((dev->class & ~(0xff)) != (PCI_CLASS_STORAGE_IDE << 8)) {
Why are we changing the enable code?
If you are not a registered device in the list and you do not report with
a storage class of 0x0101, then you do not get enabled, period.
This is going to break a whole bunch of cards and systems.
So undo this nonsense and stop dorking up the cards.
Sheesh the chipset folks are making ATA hosts that report as
SCSI0x0100
EIDE0x0101
RAID0x0104
MASS0x0180
Do not mess with ID clas signatures! Please!
> printk("%s: not 100%% native mode: will probe irqs later\n", d->name);
> /*
>* This allows offboard ide-pci cards the enable a BIOS,
>
> >From dmesg:
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> VP_IDE: IDE controller on PCI bus 00 dev 39
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt82c596b IDE UDMA66 controller on pci0:7.1
> ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:pio
> hda: IBM-DJNA-352030, ATA DISK drive
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> hdc: MATSHITADVD-ROM SR-8583A, ATAPI CDROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 39876480 sectors (20417 MB) w/1966KiB Cache, CHS=2482/255/63, UDMA(33)
> hdc: ATAPI 32X DVD-ROM drive, 512kB Cache, DMA
>
> please cc [EMAIL PROTECTED], as [EMAIL PROTECTED] is nothing but a
> mail black-hole. (provider must be trying to trim his customer base:)
>
> -Mike
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: PATCH 2.4.0.9.8: Fix IDE...
No kidding, it is scheduled for a RAPE and BURN for a redesign for 2.5.
Until then do not make changes that cause problems with 'class' code ID's.
Cheers,
On Mon, 2 Oct 2000, Jeff Garzik wrote:
> Linus,
>
> Ug. Why do I feel like the IDE "driver" is code layered upon code
> layered upon code, through the ages, with nary a cleanup in between?
>
> My previous patch was a fix, but (brown paper bag time) standard IDE
> devices no longer called chipset init. People either had no IDE, or
> were stuck in legacy mode. This fixes it.
>
> The IDE layer is in serious need of a cleanup though, IMHO...
>
> With this tested patch full functionality should be restored, without
> reverting to the previously-crazy code found in test9-pre7 and before.
>
> Jeff
>
>
>
>
> Index: drivers/ide/ide-pci.c
> ===
> RCS file: /usr/jgarzik/cvslan/linux_2_3/drivers/ide/ide-pci.c,v
> retrieving revision 1.1.1.9
> diff -u -r1.1.1.9 ide-pci.c
> --- drivers/ide/ide-pci.c 2000/10/02 08:32:44 1.1.1.9
> +++ drivers/ide/ide-pci.c 2000/10/02 18:28:10
> @@ -493,6 +493,7 @@
> byte tmp = 0;
> ide_hwif_t *hwif, *mate = NULL;
> unsigned int class_rev;
> + int pci_class_ide;
>
> #ifdef CONFIG_IDEDMA_AUTO
> autodma = 1;
> @@ -538,7 +539,8 @@
>* Can we trust the reported IRQ?
>*/
> pciirq = dev->irq;
> - if ((dev->class & ~(0xff)) != (PCI_CLASS_STORAGE_IDE << 8)) {
> + pci_class_ide = ((dev->class >> 8) == PCI_CLASS_STORAGE_IDE);
> + if (!pci_class_ide) {
> printk("%s: not 100%% native mode: will probe irqs later\n", d->name);
> /*
>* This allows offboard ide-pci cards the enable a BIOS,
> @@ -548,11 +550,17 @@
>*/
> pciirq = (d->init_chipset) ? d->init_chipset(dev, d->name) :
>ide_special_settings(dev, d->name);
> } else if (tried_config) {
> - printk("%s: will probe irqs later\n", d->name);
> + printk(KERN_INFO "%s: will probe irqs later\n", d->name);
> pciirq = 0;
> } else if (!pciirq) {
> - printk("%s: bad irq (%d): will probe later\n", d->name, pciirq);
> - pciirq = 0;
> + if (pci_class_ide) {
> + /* this is the normal path for most IDE devices */
> + if (d->init_chipset)
> + pciirq = d->init_chipset(dev, d->name);
> + else
> + printk(KERN_INFO "%s standard IDE storage device
>detected\n", d->name);
> + } else
> + printk(KERN_WARNING "%s: bad irq (0): will probe later\n",
>d->name);
> } else {
> if (d->init_chipset)
> (void) d->init_chipset(dev, d->name);
>
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: hdparm -d 1 fail test9-pre8
On Mon, 2 Oct 2000, Jeff Garzik wrote: I know that you are still pissed at me but do not do end runs around me. That is not cool, and you do not know where things are going. Heck, I keep changing my mind on stuff as I design it. I would be more appreciative if you at least sent it to me since I am the one that has to clean up issues that I do not get to see. > On Mon, 2 Oct 2000, Mike Galbraith wrote: > > In order for hdparm -d 1 to work in test9-pre8, I had to reverse > > this change. (Without being able to enable dma, performance here > > is muy el-stinko;-) Is enabling dma manually now forbidden? (or > > am I maybe missing something else?) > > If this change broke your DMA enabling, I think there are other bugs > lurking in the code... No you disable the enable of the device and it kicked out to legacy mode. > Can you provide a "diff -u " of dmesg, output, with, and without the > change below? > > Jeff > > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Please explain the change..
Jeff, What is the significance of the changes in ide-pci.c? What vender does something different that requires this change? Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Incomplete Adaptec 29160 support!?
Doug is not doing 'Adaptec' as far as I know. They have there own internal (Adaptec) for writing drivers. Ask them first, dsorry no more help than that from me. On Wed, 4 Oct 2000, Dave Madsen wrote: > Based on what I've been able to find out on the net, it > appears that the support of the Adaptec 29160 is not complete > (optimal?), but because the card works in a degraded mode with the > current driver, there haven't been many complaints. > > A recent benchmark in Open Magazine (1.2, Sep 2000) describes this. > Their comments on page 26 address this issue. They say the card is > recognized as a "7892", and works in Ultra2 mode instead of Ultra160. > The use Redhat 6.2 for their benchmark. > > Looking at the driver, the README.aic7xxx file does not say that the > 29160 (or any other Adaptec Ultra160 card, for that matter) is > supported. > > I sent e-mail to the driver maintainer ([EMAIL PROTECTED]) over a week > ago, but he has not replied. > > Am I missing something or is there no Ultra160 Adaptec support for > Linux? I find the former more likely than the latter, and welcome any > pointers to a driver with Ultra160 Adaptec support. > > Dave Madsen ---dcm > [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE problems 2.4.0-t9p8 and later
I did not change it and I have yet to get a good reason from the person
who did. I have explained why it was wrong to change, but I guess things
will have to start crashing again when Linus accepts changes that I never
looked at or discussed.
Take it up with ManDrake Linux folks, it was there person that submitted
the change directly. I have VETOed the change, that only works in an
environment that respects boundaries and specialities.
I do not like the final changes that are in pre9-final.
There appears no valid reason for the change.
The one line delete and replace ment for the extra 20 (twenty) is bloat.
The change dorks up the modes if it PCI or Legacy.
Since ALL modern PCI-IDE chipsets that are onboard do not behave in native
mode because the first 4 PCI BARS are empty (is everyone listening?)
This is not "native mode" but "compatable mode".
Only devices that fill the first for BARS with the legacy IO's can claim
"native"; regardless, I am sorry that your system is crapped out.
Bitch Linus and not me
Cheers,
On Thu, 5 Oct 2000, Martin Diehl wrote:
>
> Hi,
> the following change from t9p7->t9p8 in ide-pci.c
>
> - if ((dev->class & ~(0xfa)) != ((PCI_CLASS_STORAGE_IDE << 8) | 5)) {
> + if ((dev->class & ~(0xff)) != (PCI_CLASS_STORAGE_IDE << 8)) {
>
> causes a lot of trouble to me. Seems to be the same thing, which has
> already been reported to l-k, but to my best knowledge it's unsolved.
> So I had a look into this issue:
> My IDE-Chipset is a SiS 5513 integrated into SiS 5591 Northbridge.
> dev->class is 0x01018a. Hence the old test (there from 2.2.* to
> 2.4.0-t9p7) said "true" (due to the "|5") while the new one says "false".
> So the chipset mode is now identified "native" although it's in
> compatibility mode. PCI-IRQ 14 is used for both ports instead of IRQ 15
> for ide1 in compatibility mode. Needless to say, everything (including
> BM-DMA) works fine for me before t9p8 but now hangs when initializing the
> devices on the 2nd ide port. (hdc/hdd: lost interrupt). Reverting the
> changes cures everything.
> I've double checked the crucial "|5" change against the documentation
> for the SiS 5591 chipset, which I have here. Value=0x8a in PCI-register 9
> definitely means "bus master capable" (0x80) and "operating mode is
> programmable" (0x0a) and "compatibility mode" (~0x05) for both channels.
> So the old code was the correct one.
> I've seen several complains on this to l-k during the last days which
> appeared to be misunderstood as broken changes wrt PCI_CLASS_STORAGE_IDE
> (the leading 0x0101 in dev->class). The crucial point however is the
> "|5" on the trailing byte.
> So, may I ask if there was some good reason for this change?
> What have I missed?
> Comments?
>
> Regards
> Martin
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: New topic (PowerPC Linux PCI HELL)
On Wed, 13 Sep 2000, David S. Miller wrote: >Date: Wed, 13 Sep 2000 18:00:02 -0700 (PDT) >From: Matthew Jacob <[EMAIL PROTECTED]> > >This seems to be an artifact of some OBP implementations for PPC- >apples in particular. > >It assigns both I/O and Mem addrs and IRQs, but doesn't enable >either memory or I/O. So you have to do it for it. > > Yeah, but this doesn't belong in the drivers that is for sure. Verified, because it fails and it is way to late. > It belongs in arch/ppc/kernel/*pci*.c > > This is precisely the kind of compat stuff which should be fixed up in > the arch-specific PCI support code. Martin, cross-platform party on PCI stuff Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE problems 2.4.0-t9p8 and later
On Thu, 5 Oct 2000, Eric Lowe wrote: > Agreed. I ran into the same problem myself, but I figured you probably > didn't break it. Would be nice to see it fixed though, I'm trying > to help debug the new VM on that machine that just so happens to use > that chipset, and it's hard to do that when it doesn't boot at all. :) Okay, it is partly my fault because I missed the patch pre-release to Linus. I had several events that to major priority over Linux. Jeff and I agree now that there was a problem in communication and timing. It will be backed out and a better solution for the possible exception that he needs with be worked out. Some time later today I will publish a patch and post it on kerne.org Also I will get in touch with LT about me placing the patch in testing. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: good book on kernel
On Thu, 5 Oct 2000, RAJESH BALAN wrote: > Hi, > Iam interested in learning linux kernel. Can anyone > suggest a really good book for kernel internals (im > not bothered abt the price). i 've a book named > "linux kernel internals". i want something more to > follow the code completely. > tx, > rajesh balan If there was such a book, it would be an e-book. Because development is faster than a printing press. Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to burn CDs under 2.4.0-test9
On Thu, 5 Oct 2000, Jeff V. Merkey wrote: > I am seeing this as well. I got around it by setting speed=2. If you > are using one of the newer R/W CD/DVD drives (which are slower than > crap, BTW on Linux), you should set the speed manually and try > progressively slower settings until you find one that works. > cdrecord -v speed=2 dev=1,0,0 file.iso Sorry Jeff, I have to call you on that one. HP's are the know to burn at 4x and 8x clean. I just got my 8x CD-RW HP 9100 series and will verify the issues. Also will try to verify on my Panasonic DVD-RAM ATAPI. Linux DVD-RAM is looking like it will be showcased at Comdex in the DVD-RAM Pavilion. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to burn CDs under 2.4.0-test9
On Thu, 5 Oct 2000, J. Dow wrote: > For that matter Andre a 4 speed HP can certainly burn at 4 speed except > that cdrecord and the OS conspire to prevent this through a mathematical > error. It's rather a tad frustrating. Explain, please #!/bin/sh # # mkisofs -r -o cd_image -R -x $(object_path) $(target_path) ISO9660_PATH=/home/iso9660 # mkisofs -r -o $ISO9660_PATH/cd_image -R -x "$1" "$2" #!/bin/sh # checkit -- cd-rw loop mount and check # # mkisofs -r -o cd_image -R -x $(object_path) $(target_path) # cdrecord -v speed=4 dev=0,0,0 -eject -data cd_image ISO9660_PATH=/home/iso9660 # # cdrecord -v speed=4 dev=0,0,0 -eject -data $ISO9660_PATH/cd_image mount -t iso9660 -o rw,loop=/dev/loop0 $ISO9660_PATH/cd_image /cdrom #!/bin/sh # burnit -- cd-rw write to media # # mkisofs -r -o cd_image -R -x $(object_path) $(target_path) # cdrecord -v speed=4 dev=0,0,0 -eject -data cd_image ISO9660_PATH=/home/iso9660 # cdrecord -v speed=4 dev=0,0,0 -eject -data $ISO9660_PATH/cd_image This is my script series for a 4X burn Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Integrating Andre IDE patch into 2.2.18/19 kernel
2.2 and 2.4 are not the same anymore with ide-pci init. 2.4 got broken. In case you have not read, the backport is suspended for now. So you can not have you UltraDMA in 2.2 if you wanted. Instead of bitching about the problem, way not attempt to narrow the scope where you think is was broken. OH, and to hell with laptops for a while! On Fri, 6 Oct 2000, Bruno Boettcher wrote: > On Thu, Oct 05, 2000 at 11:56:30PM +0200, Mikael Pettersson wrote: > > On Wed, 4 Oct 2000, Jeff Nguyen wrote: > > > > >Hi Alan. > > > > > >I hope you will consider to integrate Andre IDE patche into the 2.2.18 or > > >2.2.19 kernel. > PLEASE NOT ! the 2.4 IDE driver isn't working for me at all!! at the > contrary i would rather see the 2.2 IDE driver in 2.4 :( > > > -- > ciao bboett > == > [EMAIL PROTECTED] > http://inforezo.u-strasbg.fr/~bboett http://erm1.u-strasbg.fr/~bboett > === > the total amount of intelligence on earth is constant. > human population is growing > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Hot swap IDE
Unless you have a special bay that tri-states the buss or a host that does it for the requested channel (yes that disables both devices) you can do this once per mainboard. There was a proposal for tri-stating the buss, but that was held for 2.5. There is a partial reset IOCTL in 2.4, but it needs more additions to recover the drive state. Regardless, it can/has/currently can be done, just the general kernels can not do it yet. There is a cool card by Iwill that is HPT368 based that does this nicely. You stoke the card the right way and the drive power goes away, then stroke it a different way to tri-state the channel...etc Pull ribbon first then power connector and change drives. Reconnect power first to set interface to tri-state (obviously the gound lines define the state) then the ribbon, stroke channel active, then stroke the power. Init device rescan (missing), revalidation (present), etc .. Forgot the rest but it is written somewhere in the cave. On Thu, 5 Oct 2000, Mitchell Hicks wrote: > Lots of great info on the list thank you all!!! > after reading i think most of the software raid howto's and hardware one's > also.. > I've Built a box with 3 drives and a hot spare.. > > p iii 500 256meg ram aus mother board (i think via chip set) > two promise ata66 cards and 5 30 gig maxtor drives in promise ata66 hot > swap drive bays. > > windows nt... just kidding... linux2.4.0-test9 and it's working great... > worked in test8 test6 was not good > I have not had to rebuild the array from scratch since moving to test8 (the > hotremove did not work) > > if i compile the promise drivers then when i power off a drive for testing > a failure the system freezes(i might not have done the sysrq correctly) i > have to power off the system > > if i don't compile the promise drivers i can enable DMA (and am very happy > very FAST). > > there does not seem to be a command to reset the IDE buss(this is mentioned > in the raid howto's) can i compile the IDE drivers as a module and > remove/install then while the system is running on the raid(i think not)... > I'm booting from a 20 meg none raid drive (to be raid 1 in final production) > > i can replace the drive but it must be with the same type of drive... but > the system's not really happy about the drive change and complains if the > drive was partioned .. > > ide software raid seems soo close to ready for production... > > I have turned the system OFF several times and just turned off one drive... > then the system while it's rebuilding the array... even booted with a > failed drive... > > I tried some of this stuff with 2.2.16 redhat it was ugly.. as in > complete reinstall and the system could not boot if a drive was failed (i > accepect that this could be me) > > Thank you for your time... and a GREAT OS > > Mitchell Hicks > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [preview] VIA v3.6 and AMD v1.2 IDE drivers
You are just having to much fun! On Fri, 6 Oct 2000, Vojtech Pavlik wrote: > Hi! > > For those who like to try out the very latest developments, I'm > including my latest VIA and AMD IDE tuning drivers. > > Just place all the files in drivers/ide of a 2.4 kernel and have fun. > > Of course, I'm interested in all success/failure stories. > > Thanks. > > -- > Vojtech Pavlik > SuSE Labs > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Bug in "ide-pci.c"
On Fri, 6 Oct 2000, Sean Estabrooks wrote:
> ide-pci.c bug:
>
> ide_setup_pci_baseregs() may inappropriately report device as not capable of full
>native PCI:
>
> // BUGGY LINE:
> if (pci_read_config_byte(dev, PCI_CLASS_PROG, &progif) || (progif & 5) != 5) {
> // = TWO CONDITIONS USING PROGIF
>if ((progif & 0xa) != 0xa) {
> printk("%s: device not capable of full native PCI mode\n", name);
> return 1;
>}
>
> ...
>
> In the first line of code above there is no guarantee that the first condition
>will be executed
> before the second. As progif is set to 0 before this block of code, the second test
>will always
> be true if it is executed prior to the first.
if () are serial in test.
>
>
>
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Bug in "ide-pci.c"
On Fri, 6 Oct 2000, Sean Estabrooks wrote:
> Hi Andre,
>
> The if() logic must then rely on implementation specific compiler
> details and not have any optimizations which break this code. While it may
> "WORK" it isn't particularly reliable code.
If that is the case and it is proven then there is more code than mine
that will fail. Also if the compiler is allowed in optimizations to break
specific test order, then it is a bad compiler.
Order of operation is critical in writing code.
In my world of ATA, you dork the order of a command and you get crap on
your drive. So since there is not crap on the drive in general, I am
accounting for stupid programmer errors in the past, I call your bluff.
If you issue the command register first the the rest of the register will
execute on the next command register. This is doing thing bass-ackwards.
void go_take_a_dump (float load)
{
if (pull_down_pants() && purge_bowles() && wipe_anus() && pull_up_pants())
flush(load);
else
wear(load);
}
You do this out of order and this is more descriptive.
Now if you are complaining about logical operators in the test and how
these get optimized then you point is noted.
Since I was an astronomer and +/- one AU (93,000,000 miles) is critical,
feel free to check the rules for order. Then you can call my bluff.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
FYI, I have a new baby-girl and thus the diaper-humor!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: No SCSI burning problem (was: Bug in "ide-pci.c")
On Sat, 7 Oct 2000, Jens Axboe wrote: > I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any > problems (this is on two different atapi writers). This could be an > ide-scsi bug on some models. The folks who are seeing corruption, could > they try and narrow it down? Is it random data getting written, or > data from other locations? If it is ide-scsi then it is device select bug that is know but never made it in the kernel. I have the fix. Plextor is one on the list that fails without it. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: No SCSI burning problem (was: Bug in "ide-pci.c")
> Something like this?
Close but now there is no select.
--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c Sat Sep 23
01:04:46 2000
+++ drivers/scsi/ide-scsi.c Sat Oct 7 10:52:13 2000
@@ -435,7 +435,6 @@
+ SELECT_DRIVE(HWIF(drive), drive);
if (IDE_CONTROL_REG)
OUT_BYTE (drive->ctl,IDE_CONTROL_REG);
OUT_BYTE (dma_ok,IDE_FEATURE_REG);
OUT_BYTE (bcount >> 8,IDE_BCOUNTH_REG);
OUT_BYTE (bcount & 0xff,IDE_BCOUNTL_REG);
- OUT_BYTE (drive->select.all,IDE_SELECT_REG);
if (dma_ok) {
set_bit (PC_DMA_IN_PROGRESS, &pc->flags);
It is a macro issue and ordering task-registers.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Quantum lct08 & Ultra66 on GigaByte GA-BX2000+
Read the source code and put the complete drive name in the quirk list for that chipset. On Sat, 7 Oct 2000, Mikhail Vladimirov wrote: > Hi, people! > Here I am :-) > I just want to remember: It's already test9 but... :-( > All what I certainly have is kernel panic at FS mounting point. > Nothing was changed in other words > Think everybody may have my experience, trying to install 2.4.0 to Quantum lct08 >UDMA66 drive > attached as a slave to primary Promise Ultra66 controller. > > So, I am still forced to load my poor linux from diskette with kernel 2.2.5-15 > And nobody can help me! > I'm crying :( > God knows even Windows95 works fine with both of my HDD > 2.4.0 still does not! > > Regards, > Mike > > P.S. > Everything you need (details I mean, and if you Really need it of course) you can >find > in my previous messages which (I hope) have been stored in archive > > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: No SCSI burning problem (was: Bug in "ide-pci.c")
On Sat, 7 Oct 2000, Jeff V. Merkey wrote: > append "hdd=ide-scsi" append "hdd=scsi" is better. Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Newer motherboards / CPU's / hardware with Linux
On Mon, 9 Oct 2000, Andre Tomt wrote: > > patches is ok, but I just want to know that I'm going to get more > > than 10M/s out of the drives, and not fry them. Those are my It will not fry your drives, if your drives got fried, I want to know. I want serial numbers and the maker and when/where they were returned. > > main concerns, but I'd just like to know what the average > > developer thinks of the idea of forking out cash for a highend > > system right now and wether or not it is worth it yet. > > I have been using a Asus K7M motherboard for a while, and I have nothing > but positive things to say about athlons. Both Linux 2.2.x and 2.4test > works perfectly (in 2.2.x I can't get the IDE drives above UDMA33 mode, > but my IDE drives does only about 24-25mB/s anyhows so it's not really a > concern) You are doing Ultra-66 speeds my friend. The fastest ATA drives out that are not public yet are in 39-42mB/s. Also SCSI can not sustain rates much better than maybe 60mB/s. Sure I can get 100mB/s in ATA on an analizer as can SCSI do 160mB/s in that environment. Not until media/platter densities get to 25MB/platter with 15K RPM drives will we see even disk IO approach 100mB/s. I just wish people could understand that these are max-transfer rates and that drives do not exist that can run kind of IO in a sustained rate. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Newer motherboards / CPU's / hardware with Linux
On Mon, 9 Oct 2000, blizbor wrote: > Andre, how are you benchmarking drives ? Direct access below the driver without any file-system getting in the way. No reorder of requests because of linear seeks. These are kernel level tests because timers get set upon the execution of the command block and terminate upon the interrupt regardless. This is not for the faint of heart and the new method to pump/set the request is now broken and I am try to fix it. Cool tests like forced slip-rev seeks will return zone IO data. They may be a way to test and create drive profiles that are stored and reloaded to the kernel that will add the missing supercharge on Andrea's elevator. Basically creating a physical LBA sector profile. Trust that this will be painful to create because this is the secret of the industry and I can not get access to it for Linux, even under full-disclosure NDA's. > Have you any idea did such results are really possible ? > Could you sugest me better methods ? Yes, but it will not be available until 2.5. These will be PIO and DMA-PRD chains that will then allow for nibble level verification of what the request sent and the stuff on the drive. It may allow a forced-data recovery suite to be created for when you drive craps out. This is because we will access the media directly and not allow the kernel to get in the way of critical recoveries. > Another question: looking through ide driver code I've found > that there exists bad drive list with comment saying that > it's updated when somebody emails bad words about drive. > What you think about preparing test utility and let people > around the world check and fill database of drives real "capabilities". > This way list will be almost completed now, not after few years. Can not do it until 2.5, without the UI/IOCTL needed one can never do what you are asking for without completely writing an ata-bench-module and not compile in the standard ATA/IDE driver. The rewrite of 2.5 will be based on direct pass-through commands. This will allow for 98%+ of the current IRQ disable/blocking to be removed. Also the possible creation of table-io could return a rocket-driver that is expected to give a 16-20X performance gain. Currently with much of the IO setup being done with interrupts block/masked/disable, we see a blanket system slowdown. Doing the setup/command construction ahead of time allows for reduced total system blocking. If you have not guessed by now that drive-profile and table-io are most-likely identical (caution still learning). You can see that I have a wide margin to cover before I can hit limits that are not driver imposed. This will be needed with the new SerialATA stuff, due to the single ended nature of the beasties. I can only guess that IO will approach orders of magnitude faster than what is known today. I can say no more than that it will be fast. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Newer motherboards / CPU's / hardware with Linux
On Mon, 9 Oct 2000, Andre Tomt wrote: > Using a newer ATA66 IBM 7200rpm drive, on a VIA chipset, I can sustain > 24-25mB/s in both UDMA33 and ATA66 mode. This is a Athlon Asus This okay, the drive has a physical data IO limit for sustained, not burst. Thus getting 24-25mB/s in both UDMA33/ATA66 falls under the limits of each standard. Now the drives that I have that are 37-42mB/s would exceed the UDMA33. You have to understand that in order to get data out you must issue the seek instruct (build and send) then read/write data. Much of the overhead in drive IO is getting there or building the command to do the data part of the IO. > using hdparm -X68 -d 1 -c 1 -k 1 -K 1. That's even with the linux-ide.org If you start muckying with the drive setup after you selected the kernel auto-tune or active programming you could have problems. Not all chipset code reprograms the host when changing the drive rates. Thus you can/will cause an IO sync error. > I was talking 24-25mB/s - not 100mB/s. Bg difference ;-) > > The 10k rpm u160scsi drive, yet again a IBM, sustains > about 34-38mB/s. > > Remember, I'm not talking fragmented reads here. Thats is a whole > different universe. . Recall that I told you that there is a physical limit of getting stuff off the drives. The platter density is to low and the rpm's are to slow to get there yet. Remember it took second genration ATA66 drives to fill the ATA33 bandwidth. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: dvd mounting troubles
On Mon, 9 Oct 2000, Rick Haines wrote: > I'm having real trouble mounting a dvd (udf filesystem) in my Pioneer > 104S drive. It usually failes with: > mount: wrong fs type, bad option, bad superblock on /dev/dvd, >or too many mounted file systems I suspect that it is a UDF issue and not DVD-ATAPI. Since my two DVD-ROM and DVD-RAM ATAPI now work fine. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
MAX iso9660 size?
Is there a limit? I keep getting barfs on an iso9960 image 4,592,353,280 of this size. Basically I am burning DVD's at 4.7GB tests before patching the kernel before 2.4 for expanded DVD support. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: MAX iso9660 size?
On Mon, 9 Oct 2000, Alan Cox wrote: > > Is there a limit? > > I keep getting barfs on an iso9960 image 4,592,353,280 of this size. > > That seems reasonable > > > Basically I am burning DVD's at 4.7GB tests before patching the kernel > > before 2.4 for expanded DVD support. > > You should be burning these disks UDF formatted But the original DVD was an iso9660 image, also where are tools for doing UDF? Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: MAX iso9660 size?
On Mon, 9 Oct 2000, Alan Cox wrote: > > Is there a limit? > > I keep getting barfs on an iso9960 image 4,592,353,280 of this size. > > That seems reasonable > > > Basically I am burning DVD's at 4.7GB tests before patching the kernel > > before 2.4 for expanded DVD support. > > You should be burning these disks UDF formatted This is DVD-RAM and I can dd' raw from dvdrom to dvdram with silly things like 'dd ibs=512 obs=2048 keyword=notrunc if=/dev/hdf of=/dev/hde' But my md5sums do not match but it is a valid bootable dvd-ram disk. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: dvd mounting troubles
On Mon, 9 Oct 2000, Rick Haines wrote:
> It works fine in Win2k. After reading Andre's comment I think it could
> be a udf problem as well because iso9660 cd's work fine. In fact, after
> mounting an iso9660 cdr I can now mount dvd's every try.
I tend to agree that it is FS layer and not so much in the driver.
However I am using DVD-RAM ATAPI
hdparm -i /dev/hde
/dev/hde:
Model=MATSHITADVD-RAM LF-D210, FwRev=A106, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:180,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
Drive Supports : Reserved : ATA-4
p6dnf:/src/hdparm-4.0a # mke2fs -b 2048 -m 0 /dev/sr0
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
/dev/sr0 is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=2048 (log=1)
Fragment size=2048 (log=1)
561152 inodes, 2236704 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
137 block groups
16384 blocks per group, 16384 fragments per group
4096 inodes per group
Superblock backups stored on blocks:
16384, 49152, 81920, 114688, 147456, 409600, 442368, 802816, 1327104,
2048000
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Note that this is done under ide-scsi (patched)
mount -t auto -o rw /dev/sr0 /dvdram
/dev/sr0 on /dvdram type ext2 (rw)
/dev/sr0 440262818 4402610 0% /dvdram
/dev/hdf 4484720 4484720 0 100% /dvdrom
Note that this is done under ide-cd (patched)
mke2fs -b 2048 -m 0 /dev/hde
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=2048 (log=1)
Fragment size=2048 (log=1)
561152 inodes, 2236704 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
137 block groups
16384 blocks per group, 16384 fragments per group
4096 inodes per group
Superblock backups stored on blocks:
16384, 49152, 81920, 114688, 147456, 409600, 442368, 802816, 1327104,
2048000
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
/dev/hde 440262818 4402610 0% /dvdram
/dev/hdf 4484720 4484720 0 100% /dvdrom
/dev/hde on /dvdram type ext2 (rw,noexec,nosuid,nodev)
/dev/hdf on /dvdrom type iso9660 (ro,noexec,nosuid,nodev)
> Here's an unsuccessful mount (followed by a successful):
>
> Oct 9 14:09:38 sasami kernel: VFS: Disk change detected on device ide0(3,64)
> Oct 9 14:09:40 sasami kernel: UDF-fs: No partition found (1)
If I do this under ext2 it works like a charm.
I can write just like a disk to my dvd-ram atapi.
I would tend to finger udf first now.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Incorrect UDMA timing on VIA vt82c596b
Also I need to adjust the rules for "ignore byte93" because the the various methods that are being supported. On Tue, 10 Oct 2000, Vojtech Pavlik wrote: > Try the "ignore byte93" option in the IDE menu. The IBM doesn't try to > do UDMA66 because the ZIP drive kills its 80-wire cable detection > mechanism. If you ignore byte93, which is where the IBM drive tells the > system what it thinks about the cable, the system will enable UDMA66. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Incorrect UDMA timing on VIA vt82c596b
On Tue, 10 Oct 2000, Vojtech Pavlik wrote: > On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote: > > > Also I need to adjust the rules for "ignore byte93" because the the > > various methods that are being supported. > > Yes, it would be nice if we had some better guesses on whether to think > the 80-wire cable is present. It would also be nice if the ide0=ata66 No. These are two different issues. One is host side detection and the other is drive side detection/acknowledgement. ide0=ata66 overrides the host-rules ivb-byte93 overrides the mixed drive side rules. The only think that is safe to do is allow users to randomly fake the driver over the 80c ribbon issue, but if te drive fails to sense the capacitance it must reject the attempt because of the iCRC and normal high penality of resets/downgrades t oa stable signal clock. > implied ignoring the byte93 data as well as the controller data, instead > of having two options for that. The problem is that the original ATA-5 stated that bit 13 of word93 would define the drive side detection method. Since people abused this and it was causing problems, a valid bit test was added or bit 14 of word93. Thus ((word93 & 0x6000) == 0x6000) prevents abuse, however some are not setting b13 but only b14. Thus ((word93 & 0x6000) == 0x4000) is better but still fails. I have two in methods in the works but each has its issue thus i need to find one. > Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a > setup where would be just one drive and a really short, 40-wire cable > without problems as well. I've even seen systems shipped like that. Have you read the Quantum ammendments to the signal level thresholds? The crosstalk can cause mis-clocks and data-corruption. I will bet you that these were systems that if you pull that drive out and put it into a standard system it will fail. Those are special case where an OEM has a drive maker adjust the skew tables to allow dirty tricks. Yes 'skew' you wrong and you get 'skewed'. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
Basically you have drive that caught in the word93 rules change.
However, the error you got were real and the kernel did properly respeed
the drive to one step slower. The problem above prevented you from going
from ATA66 to ATA44, thus you fell to ATA33.
You RHS 7.0 kernel does not have all the fallback and rules testing to
keep things running the very best and in the safest way. Also you do not
have the rules for testing if the driver/host/device register and report
that all signals are valid and stable.
If you did not set TUNING option if the chipset has it specifically
flagged then you will not be able to retune the chipset/drive and the IO
will be out of sync.
At best it will reject DMA attempts, at worst this will do bad things to
data.
The stuff that 2.4 has that 2.2 does not have is following the rules and
guidelines set forth by the folks writing the rules.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
diff -urN linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c
linux-2.4.0-t10-1.smsc/drivers/ide/ide-features.c
--- linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c Thu Aug 3 16:07:42
2000
+++ linux-2.4.0-t10-1.smsc/drivers/ide/ide-features.c Tue Oct 10 00:00:38 2000
@@ -224,7 +224,8 @@
#ifndef CONFIG_IDEDMA_IVB
if ((drive->id->hw_config & 0x6000) == 0) {
#else /* !CONFIG_IDEDMA_IVB */
- if ((drive->id->hw_config & 0x2000) == 0) {
+ if (((drive->id->hw_config & 0x2000) == 0) ||
+ ((drive->id->hw_config & 0x4000) == 0)) {
#endif /* CONFIG_IDEDMA_IVB */
printk("%s: Speed warnings UDMA 3/4/5 is not functional.\n",
drive->name);
return 1;
@@ -260,7 +261,7 @@
#ifndef CONFIG_IDEDMA_IVB
(drive->id->hw_config & 0x4000) &&
#endif /* CONFIG_IDEDMA_IVB */
- (drive->id->hw_config & 0x2000)) ? 1 : 0);
+ (drive->id->hw_config & 0x6000)) ? 1 : 0);
}
/*
Re: 2.4.0test-9: IDE problems
Also set this option "CONFIG_IDEDMA_IVB" because you are in the transistion period of drive manufacturing. On Tue, 10 Oct 2000, Chris Evans wrote: > > On Tue, 10 Oct 2000, Andre Hedrick wrote: > > > Basically you have drive that caught in the word93 rules change. > > > > However, the error you got were real and the kernel did properly respeed > > the drive to one step slower. The problem above prevented you from going > > from ATA66 to ATA44, thus you fell to ATA33. > > > > You RHS 7.0 kernel does not have all the fallback and rules testing to > > keep things running the very best and in the safest way. Also you do not > > have the rules for testing if the driver/host/device register and report > > that all signals are valid and stable. > > Yes, I had some "interesting" modifications to a lot of my /usr when I > tried to activate UDMA4 under RH7.0 (I don't believe my hardware is > capable of UDMA4!) > > > If you did not set TUNING option if the chipset has it specifically > > flagged then you will not be able to retune the chipset/drive and the IO > > will be out of sync. > > Shortly after my first post, I noticed and activated the Intel PIIX4 > support + tuning. This got rid of the nasty errors but didn't get my > 17Mb/sec. > > Trying your patch now. > > Cheers > Chris > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
Send me the follow files out of proc please. /proc/ide/hdx/identify (x == a,b,c,d) /proc/ide/piix /proc/ide/ide0/config files Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Chris Evans wrote: > ... > # IDE patch provides UDMA66 support, but is known to corrupt filesystems > # on a few systems, so is not applied by default. > Patch151: linux-2.2.16-ide-2805.patch > ... > # Dangerous IDE patch available but off by default > #%patch151 -p1 > ... Should I send RedHat an unpatch for 2.4? Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Unable to handle kernel NULL pointer dereference
Bob, it does help if you send the output ... my ESP is down today. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: FW: Unable to handle kernel NULL pointer dereference
Use a serial console trace to redirect the output to another thing to recorded the barf. Oct 11 12:20:07 sis620 kernel: hda: TF.0=0x00 TF.1=0x00 TF.2=0x01 TF.3=0x00 TF.4=0x00 TF.5=0x00 TF.6=0x00 TF.7=0xec size=540 Oct 11 12:20:07 sis620 kernel: hda: ide_ioctl_cmd HDIO_DRIVE_TASKFILE: ide_task_cmd WIN_IDENTIFY Oct 11 12:20:07 sis620 kernel: ide-taskfile.c,ide_taskfile_ioctl,line=662 Oct 11 12:20:07 sis620 kernel: Unable to handle kernel paging request at virtual address 0001000c Oct 11 12:20:07 sis620 kernel: printing eip: Oct 11 12:20:07 sis620 kernel: c01bab1d Oct 11 12:20:07 sis620 kernel: *pde = Oct 11 12:20:07 sis620 kernel: Oops: Oct 11 12:20:07 sis620 kernel: CPU:0 Oct 11 12:20:07 sis620 kernel: EIP:0010:[] Oct 11 12:20:07 sis620 kernel: EFLAGS: 00010282 Oct 11 12:20:07 sis620 kernel: eax: 0001 ebx: c02e0264 ecx: c4596000 edx: c3d05800 Oct 11 12:20:07 sis620 kernel: esi: b7a8 edi: 021c ebp: 0200 esp: c3c27e64 Oct 11 12:20:07 sis620 kernel: ds: 0018 es: 0018 ss: 0018 Oct 11 12:20:07 sis620 kernel: Process ide-task (pid: 538, stackpage=c3c27000) Oct 11 12:20:07 sis620 kernel: Stack: c02e0180 031d c3d826a0 c3c27f84 c3c27e84 021c c3d05800 0084 Oct 11 12:20:07 sis620 kernel:0001 ec00 0002 000a c0121fb9 c66458bc 0001 ec00 Oct 11 12:20:07 sis620 kernel:0084 0001 0002 0200 c01be95b c02e0180 c3d826a0 Oct 11 12:20:07 sis620 kernel: Call Trace: [] [] [] [] [] [] [] Oct 11 12:20:07 sis620 kernel:[] [] Oct 11 12:20:07 sis620 kernel: Code: 8b 40 0c 83 f8 10 0f 87 e7 00 00 00 ff 24 85 5c e4 23 c0 8b This is the kind of stuff that needs to be sent and a kysnoops if possible. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
