Problems with Hdparm with my laptop

Forum: HD Install
Topic: Problems with Hdparm with my laptop
started by: Ittindi

Posted by Ittindi on June 29 2006,03:49

Hello, I'm pretty much a noob to linux, I installed DSL to my laptop a few months ago,(It's a IBM thinkpad 600 with original 3gig HD and 32megs of ram 232mhz PII) with a older version of DSL but formatted it after I couldn't find much use out of it, I performed a full hd install and managed to tinker around with hdparm and was able to enable IO 32bit and ultra dma modes on it. Well, I decided now that I have a wireless card I would install DSL again seeing how linux seems to be better for wardriving, but I've encountered a problem, I can enable UDMA easily, but when I try to enable IO 32bit which I was able to do with the last version of DSL, I get this message:
setting 32-bit IO_support flag to 1
HDIO_SET_32BIT failed: invalid argument
I get this same invalid argument message when I try to set PIO on the IDE as well. Didn't have this message on the earlier version of DSL either, any help will be appreciated.

Posted by Ittindi on June 30 2006,20:28

Can anyone here help me with this?=/

Posted by mikshaw on July 01 2006,02:13

If you hadn't said that you didn't have this problem with earlier versions of DSL i'd have thought it might be an issue with hdparm, but considering most software in DSL that continues to work fine has not been altered I'd have to say that the problem is most likely your hardware. This might not be the case, however, if the "earlier version" was 2.1, which was a brief foray into uncharted waters and quickly withdrawn.

Posted by Ittindi on July 02 2006,06:38

Well, the only thing I did hardware wise is update my bios to the newest version from the IBM website, but windows didn't have a problem with it, so I really don't know.

Posted by brianw on July 05 2006,02:10

Which version of DSL did you use before. As mikshaw said DSL used a different kernel for a couple of versions which may explain the difference. Try using the old version from the livecd and pass the parameters that you use to make sure that the bios upgrade did not cause the problem.