It says what it means............
Until I can figure out and design an additional API layer to the IDE
subsystem driver core, I will/had advised one not to tinker with drive
settings.
struct chipset_bus_clock_list_entry thirty_three_base [] = {
{ XFER_UDMA_4 , 0x90c9a731 },
{ XFER_UDMA_3 , 0x90cfa731 },
{ XFER_UDMA_2 , 0x90caa731 },
{ XFER_UDMA_1 , 0x90cba731 },
{ XFER_UDMA_0 , 0x90c8a731 },
{ XFER_MW_DMA_2 , 0xa0c8a731 },
{ XFER_MW_DMA_1 , 0xa0c8a732 }, /* 0xa0c8a733 */
{ XFER_MW_DMA_0 , 0xa0c8a797 },
{ XFER_PIO_4 , 0xc0c8a731 },
{ XFER_PIO_3 , 0xc0c8a742 },
{ XFER_PIO_2 , 0xc0d0a753 },
{ XFER_PIO_1 , 0xc0d0a7a3 }, /* 0xc0d0a793 */
{ XFER_PIO_0 , 0xc0d0a7aa }, /* 0xc0d0a7a7 */
{ 0 , 0x0120a7a7 }
};
The setup of the timing and drive speeds are so tight, I had to hard code
the 32 bits of the timing functions. I spent about two weeks with the
engineers that conceived of the chipset. The end result was a general
agreement to create static tables. Since it is not desirable to even
create C-code for things like this, and I get a kick out doing the
impossible.
This is one of about three things in the "another day pile".
You know what, it s not "another day" today again........and it sits.
On Fri, 7 Jan 2000, Ernst Oudhof wrote:
> I had the lockup problems too but after I'd read this little note from
> my local kernel.org mirror in the directory of the ide patches I was
> able to fix it:
>
> ( content hpt366.warning )
> <QUOTE>
> Sat Sep 18 01:29:04 CDT 1999
>
> Do not change the drive settings on this chipset
> with any tools.
>
> If you did not set autodma in the kernel or pass idex-dma,
> You will be stuck in PIO mode only.
>
> Calling "hdpram -d1 /dev/hdx" will cause DMA timeout errors.
> Calling "hdpram -c1 /dev/hdx" can cause other errors not known.
>
> Sun Oct 3 23:34:17 CDT 1999
>
> HPT366 chipset code now handles the second onboard channel
> of the ABit mainboards.
>
> Andre Hedrick
> The Linux IDE guy
>
> </QUOTE>
> I thought I just didn't use this hdparm settings.. ( I think he meant
> hdparm in the notes it says hdpram.. ) but when I looked in the
> /etc/rc.d/init.d dir of my distro there was this
> in the mandrake_everytime file...
> <QUOTE>
> ## Optimisation of Hard drive.
> if grep -qi opti /proc/cmdline; then
> if [ -x /sbin/hdparm ];then
> echo hdparm
> LIST_HD=$(grep '^hd.:' /var/log/dmesg|\
> grep -ivE '(CD.*ROM|FLOPPY|TAPE|STATUS)'|cut -d: -f1|sort|uniq)
>
> if grep -i nohdparm /proc/cmdline >/dev/null ; then
> action "Hard Drive optimisations disabled" \
> echo ""
> else
> for i in $LIST_HD;do
> action "Starting Hard Drive optimisations for $i" \
> hdparm -q -c1 -q -A1 -q -m16 -q -d1 /dev/$i
> done
> fi
> fi
> fi
> </QUOTE>
SHEESH!!!!!!........IDIOTS go where FOOLS tell them not..........
If you guys really must tinker with "hdparm", please uses something like
this to test for things that should not be used.
if [ -x /usr/X11/bin/scanpci ]; then
PCIHERE="`/usr/X11/bin/scanpci -v \
| grep vendor \
| cut -c52,53,54,55,66,67,68,69 \
| grep 11030004`"
else
echo Command scanpci not found!
exit 1
fi
> In which my distro clearly uses both of the options which I shouldn't
> use as said in the warning by Andre Hedrick.. I also saw that in THIS
> code it looks for the kernel parameter nohdparm. So I added that kernel
> parameter in my lilo.conf and now my system has been working fine all
> day ( extracting and after that removing the linux kernel ( I could make
> it crash every hour or so doing this.. )).
Here is a testimoney that I am not BS everyone, so please listen.
> Have a look at your own distro if it's doing some hdparm stuff...
> ( my distro is linux-Mandrake 6.1 )
>
> This worked for me hopes it works for u too...
>
> Good luck...
>
> Ernst Oudhof
> <[EMAIL PROTECTED]>
> --
> =- To unsubscribe, email [EMAIL PROTECTED] with the -=
> =- body of "unsubscribe linux-abit". -=
>
Andre Hedrick
The Linux IDE guy
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
