On Wed, 07 Mar 2012 20:31:02 +0200, Johan Scheepers wrote: > On 07/03/2012 16:34, Camaleón wrote: >> On Wed, 07 Mar 2012 08:13:50 -0600, hvw59601 wrote: >> >>> Johan Scheepers wrote: >>>> On 07/03/2012 14:51, Camaleón wrote: >>>>> On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote: >>>>> >>>>>> On wheezy testing how can the screen output be logged. >>>>>> >>>>>> There seem to to be a bit problem with some missing modules. Too >>>>>> fast can not read it. >>>>> (...) >>>>> >>>>> Boot logs go under "/var/log/messages" and "/var/log/boot" (should >>>>> bootlodg has been enabled). >>>>> >>>>> Also, "dmesg|grep module" could also help. >>>>> >>>>> Greetings, >>>>> >>>> Thanks , >>>> bootlogd enabled but not working. >>>> Debian Bug report logs - #564149<mailto:564...@bugs.debian.org> on >>>> squeeze. Seem to be not working in wheezy too >> You can also delay the kernel boot messages by appending >> "boot_delay=miliseconds" at GRUB's kernel line. > Too tecnical for me
You can ask whatever you don't understand. >> How about dmesg? > Have a lot of output. You can filter the output as I told you. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jj8adf$ujn$2...@dough.gmane.org
