lucid beta2: impossible to install on notebook K50IN

[ZeroBeat]

Binary package hint: xorg

It's impossible to install lucid beta2 because screen ist corrupt.
It's possible to switch to terminal.
Keyboard was english although german was selected.
During boot, screen went black, become vertical stripes, went black again and is then corrupt (this is new - it's not the same error like #542639).
Greetings
ZB

ProblemType: Bug
Architecture: amd64
Date: Sat Apr 10 15:54:05 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog1: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
Lsusb:
 Bus 002 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. K50IN
Package: xorg 1:7.5+3ubuntu1
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
SourcePackage: xorg
Symptom: display
Tags: corruption lucid lucid
Uname: Linux 2.6.32-19-generic x86_64
dmi.bios.date: 01/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 222
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr222:bd01/22/2010:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K50IN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-19-generic

[Chris Halse Rogers (raof)]

There seem to be two or three bugs here - one is that the nouveau kernel module is trying to initialise your hardware, and fails. In a pleasant change of pace, it fails in such a way that the nouveau X driver doesn't try to work, so X then tries the other drivers we've listed as possible drivers for your hardware.

Then, the possible second bug - rather than trying the -nv driver, X tries the vesa driver.

Then, the the third bug - the vesa driver either doesn't know how to drive your display or doesn't know how to recover from whatever the nouveau kernel module has done.

Since you can get to a terminal there are some things that you can try:
1) To see whether it's the fault of the nouveau module corrupting the GPU state, could you please boot the livecd, adding “nouveau.fakeparam=yes” to the kernel command line (near the “quiet splash” part is fine). That will cause the nouveau module to fail to load. If this works, please attach the /var/log/Xorg.0.log file.
2) Boot up, switch to a terminal, and create the following /etc/X11/xorg.conf:
Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
EndSection
and then run “sudo service gdm restart” (or “sudo service gdm start” if the restart doesn't work). That should see if the -nv driver can drive your hardware successfully.

[ZeroBeat (zerobeat)]

@Chris Halse Rogers
Hi Chris.
Thanks for the the kind information.

Attached Xorg.0.log file

[ZeroBeat (zerobeat)]

Sorry, wrong log file.

This is the right one for part 1:

[ZeroBeat (zerobeat)]

After doing part 2 and restarting gdm i got the following error:

Ubuntu running on low graphics mode (i hope, it's the right translation form this: German Ubuntu läuft mit niedrigen Grafikeinstellungen).

(EE) [drm] failed to open device
(EE) No devices detected

Attached Xorg.0.log file

By the way, karmic is doing a fine job and i'm shure, lucid will do the same.

Yours sincerely
Mike

[Chris Halse Rogers (raof)]

BAH! Sorry! The xorg.conf in part (2) should have been:

Section "Device"
    Identifier "nvidia"
    Driver "nv"
EndSection

Rather than Driver "nouveau"; we already know that nouveau's not working! Could try this *without* setting “nouveau.fakeparam=yes” - we want to see if the nv driver can successfully bring up your display even when vesa can't.

For part (1), did VESA work successfully for you? Does it drive your display properly?

[ZeroBeat (zerobeat)]

Hi Chris.
No problem.....
Part 1:
VESA doesn't work successfully.
Driver only works with following resolutions:
640x480 at 61 Hz
800x600 at 61 Hz
Monitor was not recognized.

For Part 2:
Ubuntu running on low graphics mode (same as above, but little different error message).

(EE) No devices detected.

Some additional infos about the notebook:
ASUS
K50IN SX147
Intel Dual-Core T4300
4096 MB DDR II 800
NVIDIA® GeForce G102M, 512 MB
Display LGD 1366x768

Best regards
Mike

[Chris Halse Rogers (raof)]

On Thu, 2010-04-15 at 15:28 +0000, ZeroBeat wrote:
> Hi Chris.
> No problem.....
> Part 1:
> VESA doesn't work successfully.
> Driver only works with following resolutions:
> 640x480 at 61 Hz
> 800x600 at 61 Hz
> Monitor was not recognized.

But it *does* display correctly at those resolutions? VESA isn't
expected to recognise your display; it's a last-resort basic video
interface.

>
> For Part 2:
> Ubuntu running on low graphics mode (same as above, but little different error message).
>
> (EE) No devices detected.
>
Can you post the full Xorg.0.log (or Xorg.0.log.old) and your xorg.conf
for this case? That error surprises me!

[ZeroBeat (zerobeat)]

Hi Chris.

Part 1)
Well, VESA does display correctly using 800x600/61Hz and 640x480/61Hz. It was my fault, because I thought VESA was able to detect any kind of displays.

Part 2)
Attached Xorg.0.log

--- snip ---
(EE) No devices detected.

Fatal server error:
no screens found
--- snip ---

[ZeroBeat (zerobeat)]

Attached Xorg.0.log.old

By the way. Is it possible to boot from live-dvd using the midified xorg.conf?

[ZeroBeat (zerobeat)]

Sorry, again my fault. You asked me to boot without using nouveau.fakeparam=yes.
Well, here comes the the right files

[ZeroBeat (zerobeat)]

And the second one (without using nouveau.fakeparam=yes).
After restarting gdm, display is still corrupt.
Console works fine. And I can hear the ubuntu sound. Thats all

Have a nice weekend....
Mike

[ZeroBeat (zerobeat)]

Hi Chris.
Maybe the helps a little.
Booting with params "nomodeset xforcevesa" shows the desktop.
Attached Xorg.0.log.

Using nomodeset or xforcevesa standalone doesn't work.
Bye
Mike