Problem with vga (probably).

NickMrg · 2011-10-14 20:17:49

Hello guys! I'm new member of the forum so be patient! I did a quick search and i didn't find any solution to my problem so i posted here (hope in the right section). I had installed Arch on my netbook before some months and i liked it a lot so i wanna install it to my desktop too. When i'm gonna start the installation (/arch/setup) i 'm getting this error:

 [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 64
    Raw EDID:

    [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-2
    [drm] nouveau 0000:01:00.0: No native mode, forcing panel scaling

I read that i can ignore this error but i'm afraid i will have bugs after the installation. I had a problem in Ubuntu with the kernel 3 and my pc was freezing all the time (especially when i was playing a game -Savage2-). Neither ctr+alt+delete nor REISUB was working so the only solution was the reset-button! When i was booting with the previous kernel it was fine. My VGA is GeForce GTS250. I would really appreciate it if you could help me...

Last edited by NickMrg (2011-10-14 22:34:03)

Mr.Elendig · 2011-10-15 11:16:04

You can safely ignore it. If the edid is broken, and even the nvidia driver fails to read it, then you can just write a modeline instead.

NickMrg · 2011-10-15 19:03:58

So do you suggest me to give it a try and go on with the installation? I don't know what i have to write and in which file. Can you help me with that?

NickMrg · 2011-10-16 00:35:11

Well, i installed Arch on my desktop but the truth is that it's not easy to ignore it. Every 5-6 seconds the screen goes black and i'm getting the error so it's a little bit hard to open and edit a file. Is there any way to make this error stop appear all the time? Maybe, should i report this as a bug? I'm wondering, am i the only one who has the GTS250 and getting this error??

Last edited by NickMrg (2011-10-16 09:59:36)

PReP · 2012-01-10 11:46:43

I am seeing this on multiple new attempts at installing arch on machines.
One is a amd-system, with an integrated amd-video driver
and the second is my intel c2d system with both an integrated intel gma and a dedicated nvidia card.

It makes installation very messy, since the EDID probe keeps getting spammed in the terminal,
even when switching to tty2 or 3 a.so, it get's spammed in intervals on the current terminal.

Thus i have to do things like km, quickly select keycode, and the actual arch install ncurse dialog is getting messed up aswell between these intervals.

Is it the recent kernels, or something, that does this when using vga trough a DVI-adapter, or just anything else then DVI?

I belive it should tell me of the problem, but not on the running terminal, and just once in dmesg log.

I hope this can be solved upstream somewhere, where should we make this an issue?

PReP · 2012-01-10 12:02:54

Workaround; adding 'nomodeset' to the grub kernel bootline,
but it should not be needed unfortunately.

Searching the net shows this to be happening allover the place in several dists,
and seems to be due to some new edid handling in the kernel.

On another note, perhaps losely related as to the terminal spamming itself,
Is that recent kernels seems to post sdX cache writetrough messages,
on the terminal log in prompt.

Is there some change making these sorts of messages getting outputted rather then just put into a log or at boot?

NickMrg · 2012-01-25 13:20:27

PReP wrote:

Workaround; adding 'nomodeset' to the grub kernel bootline,
but it should not be needed unfortunately.

Can you tell me in which file exactly should i add "nomodeset" please? And should i add it before or after installation?

Last edited by NickMrg (2012-01-25 13:21:59)

PReP · 2012-01-26 18:04:26

In either /boot/grub/menu.lst,

The first menu-alternative, on the kernel commandline, right before "ro" (which is the last option on my line i believe)
try adding nomodeset there, in between.

It might work on the actual grub boot-menu asell (if booting from the arch-iso/usb or before starting an already installed arch), by editing the boot alternative (key E on the keyboard when the alternative is hilighted i think).

It worked on my system with an older radeon-card atleast, to prevent the spam from udev.

NickMrg · 2012-01-26 21:32:29

PReP wrote:

In either /boot/grub/menu.lst,
The first menu-alternative, on the kernel commandline, right before "ro" (which is the last option on my line i believe)
try adding nomodeset there, in between.
It might work on the actual grub boot-menu asell (if booting from the arch-iso/usb or before starting an already installed arch), by editing the boot alternative (key E on the keyboard when the alternative is hilighted i think).
It worked on my system with an older radeon-card atleast, to prevent the spam from udev.

Thank you mate! I'll give it a try and i'll let you know if worked...

cfr · 2012-01-27 04:40:34

Can anybody point to an explanation re. how to "just set a modeline" instead?

This looks to be the problem I spent Christmas trying to solve for a Mint install. In the end, I installed the proprietary drivers but that brings its own issues. (I didn't get periodic errors and blanking - in this case, it just shut down signals to the vga completely so there was no display without nomodeset.)

If I could find a work around, I could revert to the open source drivers which would probably work better with everything else (especially gnome).

nadman10 · 2012-02-02 20:37:31

I've had this happening with the newest Arch ISO and a few other various live CD's. It's not just an Arch problem. Impossible to do anything in the command line while it's happening.

Arch Linux

#1 2011-10-14 20:17:49

Problem with vga (probably).

#2 2011-10-15 11:16:04

Re: Problem with vga (probably).

#3 2011-10-15 19:03:58

Re: Problem with vga (probably).

#4 2011-10-16 00:35:11

Re: Problem with vga (probably).

#5 2012-01-10 11:46:43

Re: Problem with vga (probably).

#6 2012-01-10 12:02:54

Re: Problem with vga (probably).

#7 2012-01-25 13:20:27

Re: Problem with vga (probably).

#8 2012-01-26 18:04:26

Re: Problem with vga (probably).

#9 2012-01-26 21:32:29

Re: Problem with vga (probably).

#10 2012-01-27 04:40:34

Re: Problem with vga (probably).

#11 2012-02-02 20:37:31

Re: Problem with vga (probably).

Board footer