[lfs-support] LFS 7.3 Screen Flickering problem
beesnees at grm.net
Fri Nov 22 08:33:50 PST 2013
On 11/22/2013 10:23 AM, Douglas R. Reno wrote:
> If I were able to export the contents of dmesg to a file, could I use
> grep to sift through it faster?
First of all, let me gently remind you about top posting on this list.
Please don't do it.
Dmesg is nothing more than the kernel log. It already exists in a
file. Dmesg is only, I think, for the current boot and it updates at
each kernel event. If it's easier for you to go to a file, then go
ahead. The slowness is a function of your ability to read, recognize
and comprehend. So whatever helps you the most.
> On Nov 22, 2013 10:18 AM, "Dan McGhee" <beesnees at grm.net
> <mailto:beesnees at grm.net>> wrote:
> On 11/22/2013 10:01 AM, Douglas R. Reno wrote:
>> I will try it tonight when I have a chance. Is there anything
>> specific I should be looking for?
> "I can't describe it, but I know it when I see it." :)
> Sorry, I couldn't resist it.
> Dmesg output is quite verbose. I use 'dmesg | less' You'll have
> to wade through all the kernel, memory and bus stuff. Just scan
> for anything having to do with graphics: framebuffer, fb(0),
> trying to load firmware, dri, etc., etc., etc. You'll also
> recognize the names of your graphics drivers. I don't remember
> whether or not there are any references to "VESA" or "VGA," but
> there are instances of resolution.
> Going through dmesg can be tedious. However, if you're meticulous
> about it and bear with it, you will probably find something to put
> you on the right track. I many times get enough information only
> to ask the right question. But it's a start.
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lfs-support