On Sunday 06 November 2005 8:32 am, Basil Chupin wrote:
Many thanks. I shall now look at these 2 files to see what I may see.
BTW, what exactly do you mean by "fine tune"? And the other thing, what exactly is the entry/entries in /boot.local, just simply hdparm -d1 /dev/hdb ? Asking because putting the correct entry in /sysconfig/ide and 'hdparm -d1 /dev/hdb' in /boot.local do not fix the problem- the udma for hdb (aka dvd and cdrom) still won't "stick" and the only way to (temporarily) set it is via the command line as Bryan does it.
Cheers.
Once you have the command line parameters for hdparm that work for your device, cut+paste them into a line in /etc/init.d/boot.local with a comment line about what and why. The boot.local file won't be touched by future YaST, YOU or whatever updates and changes. Remember: hdparm -h will list all the things you can try on the device. The ones labeled (DANGEROUS) you can skip. As to why your device won't keep YaST's settings you will probably find that it will take a customized hdparm setting to make it work. There are the -k and -K parameters for hdparm that 'keep_settings_over_reset' and 'keep_features_over_reset' respectively, which should help your situation IF the device honors them. I had this happen to me back in the 7.3 or 8.0 days on a shiny new hard drive. A couple versions of SUSE later and YaST's IDE DMA Mode worked on it. The drive took a weird numerical value for its DMA Mode, something like 67 which wasn't listed as a legitimate value. Go figure. It worked. I had a faster device and later SUSE/YaST caught up and auto-configured it. YMMV, Stan