You are not logged in.
Pages: 1
Does archlinux automatically setup stuff like the hard drive? I was looking at dmesg and saw:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
That doesn't seem very good.
Offline
there is no problem in there but if you feel bether you can append this to you lilo.conf @ /etc/lilo.conf
append = "idebus=33"
then run lilo
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------
Offline
Consider this 'warning' as simply a statement by the kernel that it is starting out with a sane i/o setting. Assuming the proper compile time options are set, the kernel is very good about configuring hardware for the best i/o speeds. FWIW, this message has confused quite a few unfamiliar users.
The append isn't necessary and could actually cause problems with some hardware. It is generally best to let the kernel decide what should be done and only use the append option when you really need it. For example, really huge frame buffer text modes on that 19" video system.
If you are concerned about the speed of the IDE settings, use hdparm to test the drive i/o speeds.
BluPhoenyx
Offline
in kernel sources /your/kernel/source/Documentation/ide.txt
idebus=xx" : inform IDE driver of VESA/PCI bus speed in MHz,
where "xx" is between 20 and 66 inclusive,
used when tuning chipset PIO modes.
For PCI bus, 25 is correct for a P75 system,
30 is correct for P90,P120,P180 systems,
and 33 is used for P100,P133,P166 systems.
If in doubt, use idebus=33 for PCI.
As for VLB, it is safest to not specify it.
Bigger values are safer than smaller ones.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------
Offline
I don't doubt your research and for the most part, the info is correct (although much has been carried over from the earlier kernel versions.) Yet, I stand by my prior statements that this is superfluous. I do this from experience with a large variety of kernels on a large variety of hardware.
FWIW, it's still best to let the kernel configure things unless you are using fairly old hardware. This is due primarily to a couple of things. One, the kernel hardware and system BIOS support have come a long way over the years. Another is the differences between hardware manufacturers. Even systems with the same chipsets may function slightly differently. Compound this with the various IDE drives and you have the possibility for data damage.
That said, I have only had to use the idebus option once, IIRC and even then it was on an odd 486 system.
BluPhoenyx
Offline
"this is superfluous"
correct
????!!!!! werd do not recal posting this very same post
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------
Offline
Pages: 1