You are not logged in.
I know Free Software is about choice, but what is the prefered choice for ArchLinux right now?
Offline
hwdetect
Offline
hwdetect
THX!!
cu matsche
Offline
I use lshwd, it is fast enough for me and does what it needs to do.
Offline
hwdetect is faster.
Offline
what about setting your modules array manually in rc.conf?
Am I going to have to comment out the sys.init script after every update?
Offline
what about setting your modules array manually in rc.conf?
Am I going to have to comment out the sys.init script after every update?
hwdetect doesn't stop your modules from loading. It only autodetects your hardware and attemps to load the proper modules.
If you don't want to use, set MOD_AUTOLOAD="no".
Offline
If you don't want to use, set MOD_AUTOLOAD="no".
Why "no" is not set as default? As per the Arch Way, user is suppose to know/learn what are loaded. Auto load for new users and fresh installs, does the opposit. Moreover, hwdetect doesn't work for all custom kernels. In my case, sytem hung up at booting and I had to config rc.conf through my rescue partition.
Markku
Offline
what didn't work on your system?
please be more precise, hotplug was enabled by default now hwdetect does the job so please tell me the problem that i can fix it.
there was always autodetection in Arch hwdetect is the successor.
thanks
greetings
tpowa
EDIT:
It's easy to go in rescue mode with arch kernel, just enter "load_modules=off init s" on grub/lilo boot.
Offline
what didn't work on your system?
please be more precise, hotplug was enabled by default now hwdetect does the job so please tell me the problem that i can fix it.
Having hotplug enabled was not proper. I didn't complain when no direct harm.
Currently I am not using my machine (login problem, did a post about it), but it was hanging up when could not find something. Did the same before and I posted the result in the other forum. If I am correct, now its something different what cannot be found. I let you know later.
Markku
Offline
Moreover, hwdetect doesn't work for all custom kernels.
Thanks tpowa for the upgrade letting user know hwdetect requires kernel 2.6.12 and above.
Markku
Offline
no problem, i think we got you all now, custom kernel users
Offline
Penguin wrote:If you don't want to use, set MOD_AUTOLOAD="no".
Why "no" is not set as default?
Actually, hwdetect is disabled unless you set MOD_AUTOLOAD="yes" - so if you upgrade your system and don't update your rc.conf, hwdetect will be disabled.
Offline
I understand your point. The default what I am here speaking about is the setting in initscript package. If you take a look, in rc.conf it says:
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
Markku
Offline
So just because I dont really know the differences: Why is nobody using the good ol' hotplug?
Offline
So just because I dont really know the differences: Why is nobody using the good ol' hotplug?
That's because hotplug is quite slow. hwdetect loads the modules much faster (as fast as if they were explicitely listed in the MODULES array). Therefore, your system will boot faster.
Offline
So just because I dont really know the differences: Why is nobody using the good ol' hotplug?
Because its slow as hell. Hwdetect and lshwd (hwd in daemons) do the same thing but much faster.
hotplug = grab a snickers bar
hwd, hwdetect = hold on to your seat
Offline
So, where's a good place for me to read about the differences between hwd (which I'm using now) and hwdetect (assuming this is actually something new and different. Judd's Blog entry certainly led me to believe it is). I was simply blown away by hwd, FWIW.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
hwdetect detects everything that hotplug does and more. HWD sees about half that stuff.
Offline
In my (short) experience with Arch, hwd sees more than hotplug, and hwdetect sees more than hwd.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
new udev-076-4 will kill hotplug and pcmcia-cs because now is everything done by udev and hwdetect.
Offline
Really? :shock: Hotplug is out? Finally?
Kick ass! :twisted: :twisted: :twisted:
Offline
Cool!! I always hated hotplug, but couln't kick it away from my system.
In the last upgrade i got this:
:: udev conflicts with hotplug. Remove hotplug? [Y/n]
I was very, very happy to see how pacman removed this thing... :twisted:
All your base are belong to us
Offline
new udev-076-4 will kill hotplug and pcmcia-cs because now is everything done by udev and hwdetect.
Installed it yesterday on my laptop, looks very nice
Question: pcmciautils still puts some files into /etc/hotplug and /etc/pcmcia, are they really necessary?
Offline
Hope firmware loading via hotplug isnt broken...
Offline