You are not logged in.
Pages: 1
Yesterday, when I booted up, init never got past "starting hotplug daemon" - it just hung there for a full minute before I inserted my handy live CD and rebooted.
What's going on? Is this some sort of problem in the /etc/rc.d/hotplug script causing an endless loop? Or is this something else entirely?
Offline
I am new here.i can only speak a little English.I don't know what happened to your system,but this maybe help you.
You can try to add a "@" before "hotplug" in rc.conf.it will make hotplug daemon starting in background.
I hope after that you can boot into your system,then you can check what happened.
english&linux n00b
Offline
I had that some time ago. After waiting several minutes hotplug finally finished and the system worked fine. I had this after rebooting to a fresh compiled kernel. The second time booting after this happened all seemed normal again.
Out / Gone
Mirgrating all my machines off ArchLinux . No longer part of the ArchLinux community / users .
Done. Goodbye.
Offline
maybe it's trying to recompile its big fat lists of modules and things like that.... if I were you, I'd let it run for like 15 mins if it needs to
Offline
I didn't use a custom kernel... I did a fresh install with kernel 2.6.11. I booted once and it worked fine; the second time I booted, it pulled this crap.
Offline
Okay, rebooted and read a book for 15 minutes. When I looked at my monitor again, the boot process was complete... But when I logged in, I discovered that there were no modules loaded. :shock:
So I rebooted... And hotplug hung up again. :evil:
Somehow, this doesn't seem right... Perhaps I should file a bug.
Offline
Just turn it off and load what modules you need in rc.conf and rc.local. Hotplug is always been "kinda sorta working". It's known to to unstable as That Other OS.
·¬»· i am shadowhand, powered by webfaction
Offline
Okay... Another questin then: does the rtc module load automatically? More generally, what modules should I use, other than snd-via82xx, via-rhine, etc. - which ones will be loaded as module dependencies?
Offline
I have to load rtc manually (put it explicitly in rc.conf). I'd simply check for the loaded modules (lsmod) when your system is fully functional and then put that list in rc.conf. That won't hurt.
A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
Okay... I'll have to download and use coldplug to do that though. I'm not entirely familiar with the hardware on this machine, and hotplug is not functioning at all...
Offline
Try hwd. It gives the modules you need.
Offline
It doesn't give you rtc... That makes me wonder if it misses anything else.
Offline
Holy shit... This is not a problem with hotplug. This is a kernel problem.
I tried loading the modules manually, and got nothing but string after string of errors... The modules are there, but they won't load!
Here's part of my daemon.log:
Mar 20 22:00:12 localhost modprobe: WARNING: Error inserting snd (/lib/modules/2
.6.11.3-ARCH/kernel/sound/core/snd.ko): Unknown symbol in module, or unknown par
ameter (see dmesg)
Mar 20 22:00:12 localhost modprobe: WARNING: Error inserting snd_seq_device (/li
b/modules/2.6.11.3-ARCH/kernel/sound/core/seq/snd-seq-device.ko): Unknown symbol
in module, or unknown parameter (see dmesg)
Mar 20 22:00:12 localhost modprobe: WARNING: Error inserting snd_rawmidi (/lib/m
odules/2.6.11.3-ARCH/kernel/sound/core/snd-rawmidi.ko): Unknown symbol in module
, or unknown parameter (see dmesg)
It goes on like that for every single module.
Help? :shock:
Offline
Install another kernel revision, say kernel26-mm, boot with that one, and do a "pacman -Sy kernel26". It seems that it hasn't installed properly.
Microshaft delenda est
Offline
I got a lot of similar messages with my custom 2.6.11 kernel with ck1-patchset. None of my soundmodules would load, in previous kernels there weren't any problems. I'm back to 2.6.10 now.
A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
Scarecrow: I tried that already... Booted using a Damn Small Linux CD, mounted my partitions and my proc properly, chrooted in, and reinstalled the kernel. Didn't change a damn thing. Perhaps I should remove the kernel first, then download and install kernel26?
FUBAR: 2.6.10 would be behind on the -as patchset now, wouldn't it? I know that, as a desktop user, I don't have to worry as much about security problems, but it's good to be paranoid.
And remember, the boot process went perfectly the first time... It was the second time that it screwed up, though I hadn't done anything other than install GNOME 2.10 and some other stuff (none of which should have messed with the kernel).
Offline
Okay, narrowed down the problem further:
It's the sound modules. None of the sound modules can load, even though they are definitely there... Installing alsa-driver (don't worry, I did 'depmod -a') doesn't help this. :?
Lordy... I'll bet that I'd get less trouble from the MM kernel.
Offline
Okay... Just tried the MM kernel, and got the same problem.
Kernel26-scsi - same thing.
Reinstalled module-init-tools - same old shit.
I hate to resort to Windows-ish methods, but I see only one option: I've backed up all my documents, and am now preparing to repartition my HD and do a clean install.
As of right now, I'm open to suggestions on what the bloody hell to do to fix my system... Because reinstallation will take forever with my unreliable 128 Kbps connection. So: what can I do?
Offline
It seems that there's a problem with 2.6.11 and/or hotplug and certain SB soundcards... similar problems reported @ other distros as well.
May I suggest 2.6.10 for the time being, like FUBAR did before me?
Microshaft delenda est
Offline
Might try it... But this is Via onboard audio, not Soundblaster, and my audio modules loaded fine on the first boot.
Offline
Okay... Wiped out the root partition and kept my home partition. Everything works beautifully now, no problems at all.
Offline
Ah... Reproduced and solved it after a little experimenting. I know what it is now: using Cactus's fix for warbling sound on kernel 2.6.11 seems to screw things up. No, I don't know why.
Offline
Pages: 1