Re: Debian-6.0.2.1-i386 and Intel 82845G - install fine,no screen on boot
I experienced video problems (less severe than those of OP)
after installing Squeeze on a new (to me) machine with the
Intel chip. After many failed attempts at fixing it, I
upgraded the kernel to 2.6.39-1-686-pae. Now everything
works!
Camaleón wrote:
> On Thu, 14 Jul 2011 11:46:30 -0700, Ed Siegner wrote:
>
>> I added "nomodeset" to the kernel command line in "grub"
>> at boot time but still no video.
>
> It would be of help to see the full X log once you added
> "nomodeset" to the kernel line, juts to see the driver
> that loads.
>
>> "dmesg" says it was passed, but didn't see anything in
>> the "Xorg.0.logs"
>>
>> Kernel command line:
>> BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686
>> root=UUID=dcbafd16-7eee-494c-b9b4-d3f982caae7d ro
>> nomodeset
>>
>> I copied the logs generated from a "no modified" boot and
>> logs generated with "nomodeset" added.
>
> Good :-)
>
> Where are they?
>
>> I check the following logs looking for a clue but none
>> spotted. The ones taken at 110714th_091713 were unmodifed
>> boot while the ones at
>> 110714th_094114 were with the "nomodeset". Are you
>> interested in looking at any of them since some are long?
>>
>> 110714th_091713_dmesg
>> 110714th_091715_messages
>> 110714th_091719_Xorg.0.log
>> 110714th_091720_debug
>> 110714th_092208_syslog
>> 110714th_094108_dmesg
>> 110714th_094109_messages
>> 110714th_094114_debug
>> 110714th_094114_kern.log
>> 110714th_094114_Xorg.0.log
>> 110714th_094118_syslog
>> 110714th_094154_wtmp
>>
>> The first couple lines from
>>
>>
https://wiki.archlinux.org/index.php/Kernel_Mode_Setting
>
> Better use this:
>
> http://wiki.debian.org/KernelModesetting
>
>> tells me I'm dealing with a new feature, different from
>> that used in "etch".
>> Looking at the archives, others are having problems but I
>> have not seen a successful resolve.
>> Have any other ideals?
>
> Nope, no more ideas... Intel driver has been there since
> years and is open source so devels can work on it and fix
> problems quite easily. And by disabling KMS you should get
> the plain fb or vesa driver.
>
> If don't get any further advice and still facing the
> problem, I would think in opening a bug report in Debian
> BTS.
>
> Greetings,
>
Reply to: