Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
im gunna be a right upfront about this.... i am some what of a Linux newbie, but i do know my way around computers fairly well and only reciently decided to switch my laptop to Linux only, as to more diversify my knowlege of computers.
i am trying to get my sound to work, compiled the kernel with the sound drivers, found work arounds for all the other issues i had, re-re-compiled the kernel with ACPI support.
the boot hangs at the following line in the boot process:
kjournald started. Commit intervel 5 seconds
and it just hangs from there.
here are the last few lines of my boot log if it helps.
NET: Registered protocol family 17
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.40.2)
powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x10 (1150 mV)
cpu_init done, current fid 0xa, vid 0x6
ACPI wakeup devices:
LID KBC0 MSE0 PB4 P2P ELAN
ACPI: (supports S0 S3 S4 S5)
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 280k freed
kjournald starting. Commit interval 5 seconds
it just hangs from there, no hdd activity, nothing. normaly, booting from my default kernel, that is usualy the 2nd last line before init starts up, then Gentoo would normaly go through its start up process. if u guys need anymore information just say the word. ive recompiled the kernel numoreous times to get the same result.
Distribution: Slackware 11, Solaris 10, Solaris 9, Sourcemage 0.9.6
Kjournald is a journalling daemon. When your system is booting, Kjournald couldn't for some reason start. It is extremely important for Linux that it is running. I think it has something to do with your GRUB config (or LILO). Could you give me a short description about your hardware and post /boot/grub/grub.conf or /etc/lilo.conf here?
AMD Sempron 3200+
512mb ddr333 ram
60GB 5400RPM hdd
15.4" highdef screen
ATi Xpress 200m video card (get this driver running after sound)
Broadcom wireless (ndiswrapper, drivers and hardware installed, but i cant get the wireless to work, as in find my router, with SSID broadcasting turned on.)
I've noticed hangups if the root filesystem was mounted read-only at the time that the daemon tried to start.
On my systems, the ro kernel-parameter is specified so that the root filesystem initially starts read-only. The /etc/rc.d/rc.sysinit script then switches it to read-write. A glitch in that script prevented it from running, and a hang similar to this one was the result.