How to read the Log file of booting sequence when Knoppix can't boot?

**rajibando** · 02-08-2013, 09:33 AM

I have a longstanding problem with Knoppix, which does not boot in my HCL laptop. I have tried versions from 5.0.1 to 7.0.4, but none can boot, either from CD/DVD or from hard drive using grub&cheatcode.
I don't know where it gets stuck.
Sure, a log file can tell.
But how to read that log file when the system can't boot? Can these operations be performed in a virtual machine, and is it then possible to read the log file?
This, I hope, is an interesting question, and I hope, will interest many.

**Werner P. Schulz** · 02-08-2013, 11:39 AM

You can try "boot: knoppix vga=0 debug -b 3" from Cannot boot

**rajibando** · 02-08-2013, 06:02 PM

Originally Posted by Werner P. Schulz

You can try "boot: knoppix vga=0 debug -b 3" from Cannot boot

I will try this and get back ASAP! Thank you for your prompt suggestion, as always.

**Werner P. Schulz** · 02-08-2013, 07:23 PM

Note: Each time the message output stops, you can scroll some lines with "Shift PgUp/PgDown"

**rajibando** · 02-12-2013, 03:14 AM

Originally Posted by Werner P. Schulz

boot: knoppix vga=0 debug -b 3
...Each time the message output stops, you can scroll some lines with "Shift PgUp/PgDown"

I should have written exactly where the script stops. Then the time wasted in above messages would have been saved. I am sorry. The script stops at init 5, just after displaying the Tux in Vitruvian pose. init 6 works, and shuts down the system.

**Werner P. Schulz** · 02-12-2013, 11:12 AM

Read "Cannot boot" first!

Ok, try "boot: knoppix vga=0 debug -b 3" once more. You'll see messages

mounting /mnt-system
/KNOPPIX
/KNOPPIX-DATA
/UNIONFS
symlinks to UNIONFS
Final DEBUG Shell before starting init
At this point type

Code:

mv /etc/syslog-knoppix.conf /etc/syslog-knoppix.orig

to enable logging in '/var/log/'. (Caution: us-keyboard!) Proceed with

exit => Control D => init 5

Your Knoppix doesn't go on; therefore change with "Strg Alt F2" to the terminal and examine the logs at '/var/log/'. Perhaps you can find what is wrong with starting the GUI.

In case of HD Install: Don't forget to rename '/etc/syslog-knoppix.orig' to ' /etc/syslog-knoppix.conf'; otherwise your persistent memory has no more free space soon afterwards.

**rajibando** · 02-13-2013, 04:12 PM

examine the logs at '/var/log/'.

Which of the log files? there are two, xorg.0.log and pm-powersave.log!
It should not be xorg.0.log, since graphics is displayed alright! The console kit folder has one file that is readable.
The cups folder has 3 files that are readable.
The rest folders are empty.
I will nevertheless read them and get back. Please bear with me. Thanks/

**utu** · 02-13-2013, 04:43 PM

Greetings, rajibando.

In Werner's post #6, the mv operation must be done as root to be effective.
Likewise, later you must restore the file as root.
If you issue the mv as knoppix and not as root, nothing happens.

The purpose of the original /etc/syslog-knoppix.conf is to disable most of
/var/log/ including syslog. Werner's post #6 tells us how to re-enable full
/var/log/ capability temporarily.

I expect /var/log/syslog may be what you want.

**rajibando** · 02-13-2013, 05:35 PM

Dear Mr.Schulz,
I have attached the zipped file for Xorg.0.log.
http://knoppix.net/forum/attachment....1&d=1360772976
I hope you could find something there that would be of some help.
Maybe Nouveau driver is creating some problem?!
And greetings, Mr.Utu,
There is no file named /var/log/syslog
Thank you.