#7523: Intel Extreme driver showing blank with N10 (GMA 3150) ----------------------------------------------+---------------------------- Reporter: 6foot3 | Owner: brecht Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: x86 ----------------------------------------------+---------------------------- Comment (by 6foot3): Spent some time trying to figure out how the logging works in order to try and make sure that the syslog i attach contains the relevant entries. Here's my take on how it works:[[BR]] All entries are appended to the current syslog untill it reaches a size of 512kb. At that point the syslog is renamed to syslog.old and a new syslog is generated. I had been thinking that everytime the system was booted, a new syslog was created but, my observations are that this is not the case. The syslog entries after a reboot just continue to be added to the existing syslog.[[BR]] In safe mode the log grows a lot more slowly as there is a lot less activity going on. Where there are no open networks within range and not in safe mode, the system appears to be continuously trying to identify a suitable network to connect to. As a result, if the system is just left doing nothing, after a while most of the entries in syslog and syslog.old will consist of these network messages.[[BR]] Based on my observations and new understandung of how the syslog works, here is how captured what I believe is a relevant syslog.[[BR]] I booted up in safe graphics mode and watched the syslog grow from the constant network activity until it was almost 512kb in size then, I initiated a restart. I allowed the system to boot normally until I got the blank screen following the start up sequence. I used ctrl-alt-del to reboot the system and selected safe graphis mode and safe mode from the bootloader safe mode options. Having completed booting I copied the syslog to another location and renamed it "syslog_r42159_screen blank,txt".[[BR]] I suppose that most kernel and driver developers would be able to identify a shutdown/start-up sequence in the syslog. I believe that the syslog I'm attaching contains a shutdown/boot-up sequnce into normal mode, followed by another shutdown/boot-up sequence, this time into safe mode.[[BR]] If I am mistaken in any of my conclusions, I welcome any explanation of how things actually work. -- Ticket URL: <http://dev.haiku-os.org/ticket/7523#comment:16> Haiku <http://dev.haiku-os.org> Haiku - the operating system.