SliTaz Forum

Error when loading kernel log daemon

(7 posts) (3 voices)

• Started 11 years ago by arodulfo
• Latest reply from arodulfo
• This topic is not resolved

Tags:

No tags yet.

1. 

   arodulfo
   

   offline

   Member

   Dear guys,

   I have recently noticed my system is issuing some complaints when it is loading the kernel log daemon.
   Here's its output:
   

   Starting kernel log daemon: klogd
   [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder es 128
   [drm:drm_edid_block_valid] *ERROR* Raw EDID

   The last two lines are issued four times.

   Even if the system seems to work according to expectations, I'd like to remove these error messages if possible.

   Maybe I did anything wrong when installing it? Any other idea?

   Kind regards,
   Antonio

   Posted 11 years ago #
2. 

   ernia
   

   offline

   Member

   did you try another monitor?
   it could be an hardware issue.
   http://www.webopedia.com/TERM/E/EDID.html

   Posted 11 years ago #
3. 

   arodulfo
   

   offline

   Member

   @ernia: We're using this monitor as the basement to build everything up on. Once we get it working as expected, we build an image that we load on other clone systems and run there as if they were our development system. I've seen the same error complaint displayed on their screens.

   Thank you so much for your feedback. I'm not quite worried about it; I've seen no operational problem that I could trace back to this error. I'm just a bit paranoid about errors and warnings in computers; I have always believed they're issued for a good reason, even if they overall behavior is not widely affected.

   When any embedded development is released, it must be working for days and weeks without any power cycling or restarting. That's why we chose linux and, after many experiences, SliTaz.

   I feel we made the best possible choice and just want to solve any problem, actual or potential, and keep them from avoiding these systems to excel.

   I'll try to take a look at the link you included and learn about EDID and so.
   Kind regards,
   Antonio

   Posted 11 years ago #
4. 

   arodulfo
   

   offline

   Member

   @ernia: I have spared a minute to explore the link you included in your message and read about EDID and its general purpose.

   Now I understand your comment about the monitor.
   I can't tell if the EDID process should be 100% successful in our case or not. One of the participants in the project has been in charge of building a "monitor" out of several parts, one of them being the LCD display. I will ask them ASAP about how they did connect this LCD display to the main SBC (where SliTaz is running) and try to see if there's an overall reason for such errors to be encountered and reported.

   Posted 11 years ago #
5. 

   rerivero
   

   offline

   Member

   You can try adding the command 'nomodeset' to the kernel line in boot/grub/menu.lst
   example:
   kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sda8 nomodeset

   Posted 11 years ago #
6. 

   arodulfo
   

   offline

   Member

   @rerivero: Thanks a lot for your contribution.

   However, I'm sorry to tell you it is not useful for our graphics application, based on xorg.
   Of course, when including nomodeset in kernel loading line of /boot/grub/menu.lst all errors do disappear, but the system is not entering graphic mode; remains in the console (tty1) and yields a lot of exceptions for X not being available.

   So I went back to the error prone system and to use it WITH all those errors: as long as they are not interfering with the normal application behavior...

   Posted 11 years ago #
7. 

   arodulfo
   

   offline

   Member

   Dear all,

   I have been quite busy with other aspects of the project. Now I'm having a small time to "clean the house" and want to get one step beyond, if possible.

   I located my graphics card "PCI slot" (it is an SBC after all) as being 00:02.0.
   My system answer to dmesg | grep "00:02.0" is:
   

   ...
   i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
   i915 0000:00:02.0: setting latency timer to 64
   i915 0000:00:02.0: LVDS-1: EDID block 0 invalid
   vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem, decodes=io+mem:owns=io+mem
   [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

   The display has been flawlessly working since the very beggining, so I didn't really worry about these EDID-related errors until right now. Should I worry? Should I plainly ignore them right away?

   Thank you so much for being there!
   Kind regards,
   Antonio

   Posted 10 years ago #

RSS feed for this topic

Reply

You must log in to post.