On Fri, May 31, 2002 at 18:13 -0400, Richie de Almeida wrote:
> I kinda figured something was a little odd with -17mdk as I did try to compile
> it myself and selecting compiling for Athlon/K7 always failed and even when I
> didn't I got some funny messages about 'int's not being the right size-- I
> take it that gcc 3.1 uses more bytes for some data types-- whatever-- I'm
> going to install gcc 3.1 this weekend and see if things get better.
>
> FWIW, I got the boot parameters going, using "ide0=0x1f0 ide0=ata66' on
> 2.4.18-7mdk. Strange how these parameters are asking for ata66 yet the
> system enables ata100 (hdparm tells me I'm at udma5)... Regardless it's
> great to have another method to fall back on if later kernels don't behave as
> nicely as -13mdk and -17mdk...
I've been following this thread from the start and now tried to
experiment with my harddisk. I did not find hdparm!
I did a 'urpmi hdparm' and it installed the packages 'pciutils' and
'powertweak'. But still I get 'bash: hdparm: command not found' when I
try to start it. slocate does not find hdparm (yes, I did updatedb).
# slocate hdparm
/usr/lib/powertweak/plugins/libhdparmtweaks.so.0
/usr/lib/powertweak/plugins/libhdparmtweaks.so.0.0.0
WTF?
wobo
--
Registered Linux User 228909 Powered By Mandrake Linux 8.1
---------------------------------------------------------------------
Microsoft, Windows, Bugs, Lacking Features, IRQ Conflicts, System
Crashes, Non-Functional Multitasking and The Blue Screen of Death
("BSOD") are registered trademarks of Microsoft Corp., Redmond,
Washington, USA.
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
