[prosavage8] Lucid fresh install crash/hang on login

[Invader Zim]

Binary package hint: kdebase-workspace

Description: Ubuntu 10.04 LTS
Release: 10.04

xorg:
  Instalado: 1:7.5+5ubuntu1

kdm:
  Instalado: 4:4.4.2-0ubuntu14

After fresh install from Lucid CD, after typing user/pass at KDM, screen blinks and returns to login screen.

Xorg.0.log tells me Fatal error, video driver problem with savage, some framemapping range issue.

Doing the following steps work around it, making it a very strange bug:

1. login in console
2. as root, service kdm stop
3. rmmod savage
4. modprobe savagefb (different module)
5. startx

It works!

Notice that is startx, if I try kdm start, the same problem will happen. If I try failsafe mode (vesa driver) the computer hangs in a black screen.

After startx, then no problem, nothing, I can use KDE normally. In previous releases in this same computer, no problem like this whatsoever, not a single video driver issue or Xorg issue.

Doesn't make any sense to me.

Complete showstopper.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: kdm 4:4.4.2-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
Architecture: i386
Date: Sun May 23 14:54:37 2010
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: kdebase-workspace
---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: 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
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: xserver-xorg-video-savage 1:2.3.1-1ubuntu1
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=4aef7c30-e62f-4ea9-94c2-b04dd47a1336 ro quiet splash
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-22-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/23/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1012.003
dmi.board.name: P4VP-MX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1012.003:bd02/23/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnP4VP-MX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic-pae

[Invader Zim (invasorzim0)]

Update on the issue:

Now startx also works with savage, I don't need to load savagefb anymore.

So I installed xdm, and changed from kdm to xdm, and it worked.

So it's obviously an issue with KDM.

Also to note is the fact that the fatal error that sometimes appeared in Xorg.0.log doesn't show up anymore.

The problem with the xdm workaround is there is no "shutdown" button in KDE.

[Tormod Volden (tormodvolden)]

Thanks for your report. Please reproduce the problem and run "apport-collect 584674".

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Invader Zim (invasorzim0)]

apport information

[Tormod Volden (tormodvolden)]

Please attach the Xorg.0.log with the fatal error.

[Invader Zim (invasorzim0)]

As I said before, the fatal error doesn't show up in the log anymore. There is no fatal error anymore.

I'm gonna attach the only error that show up in messages. And still, that error only occurs when, after boot up, I login at the console, and modprobe savagefb.

So there are 2 modules for savage, savage and savagefb.

But the error also happens using xdm, and I can log in normally in xdm. So the error logged is probably not related.

Also, maybe unrelated, when I press ctrl+alt+f1 on kdm/xdm to go to the console, the "kubuntu logo splash loading screen" loading dots and the blue background is still there. I use the console with the dots lighting up and a blue screen, which makes it hard to use the console. Applies to all consoles, not just "f1".

To note, the "screen blink" in kdm happens right after the screen is drawn fully white, and it quickly refreshes to the kdm background, and only then the screen goes black - as in the X server being restarted.

When I log in using xdm or startx, I can see the same white box being drawn, but its just occupying 1/4 of the screen, and after that the desktop background is drawn, along with the rest of it.

[Invader Zim (invasorzim0)]

Ok, the Fatal Error showed up again, I'm attaching it.

However, more issues have come up.

First, xdm login doesn't work anymore. It returns to xdm login sometime after pressing enter.

Then, when I tried to boot in recovery mode to copy the Xorg log before it was overwritten, the curses dialog appeared (with those options, resume, clean free space, drop to root, etc.) and when I was going to drop to root, the kubuntu splash logo appeared and I couldn't see anything else.

Trying to go drop to root shell makes it black or splash the logo with the blinking dots the same.

Booting in normal mode, at the xdm screen, I press ctrl+alf+f1 and I can't see the console, my monitor light starts blinking (as in unsupported settings, resolution/refresh/etc).

First attempt to run startx, it has hung up the pc (as when it did a while back in failsafe mode)

So I have to blindly log in, stop xdm, and type startx.

And I finally managed again to get into kde to paste this log.

This is getting increasingly annoying and unstable.

[Tormod Volden (tormodvolden)]

Normally it should not be necessary to use the savagefb module. You have all the latest updates, right? There were some savage updates that came after the (CD) release. Can you try removing the plymouth package to see if it helps?

[Invader Zim (invasorzim0)]

Well, I didn't know exactly which plymouth package, so I tried removing the package plymouth, but it breaks everything. mountall depends on it.

So I removed all plymouth that I could, logos, x11, etc.

The console problem did stop, but the kdm/xdm login problem persists.

[Invader Zim (invasorzim0)]

Got xdm login working again, by putting savagefb in /etc/modules, and blacklisting savage.

KDM still doesn't work.

[Invader Zim (invasorzim0)]

Attached the Xorg Log when I use the vesa driver in xorg.conf (computer freezes in a black screen and stops responding).

[eyeshavings (34e04o)]

I wish I knew how to be as helpful as Invader Zim. I am having the same issue. Bug 567029. How do you run anything at all, much less "apport-collect 584674" when the computer is looped at login?

quote//
1. login in console
2. as root, service kdm stop
3. rmmod savage
4. modprobe savagefb (different module)
5. startx
//quote

[Tormod Volden (tormodvolden)]

There are troubleshooting documents on the wiki, for example https://wiki.ubuntu.com/X/NonGraphicalBoot

[eyeshavings (34e04o)]

Tormod Volden wrote:
> There are troubleshooting documents on the wiki, for example
> https://wiki.ubuntu.com/X/NonGraphicalBoot
>
>
YAY! A clue! Thank you!

[Norbert Bollow (nb-bollow)]

I've just upgraded from 10.04 to 10.10; now I'm experiencing a problem which is, superficially at least, very similar. I'm using gdm however. Upon entering the correct password at gdm, the screen blinks and the gdm login screen is built up again. Another similarity is that this is also with the SAVAGE driver (I haven't yet tried using another driver package, I'll do that as soon as I can. I need to go and catch some sleep now, and will be traveling all day tomorrow.)

In order to start investigating the problem, I have booted into "recovery mode" from the grib menu, then chosen "netroot" in the Reciovery menu.

If I type 'startx' as root, it works.

If I 'su - nb' first, the type 'startx', the screen goes dark with an "Input Not Supported" box from the monitor.

The Xorg log file from the case that doesn't work (attached) is very similar to the case that does work.

The only possibly-significant difference is the final line

[ 2295.773] (--) SAVAGE(0): Chose mode 14f at 85Hz.

which doesn't have an equivalent in the Xorg log file for the case that works.

[Norbert Bollow (nb-bollow)]

I'm now convinced that my problem is a different bug, as it is not related to the SAVAGE driver, so I've created a bugtracker entry for it: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/669002

[eyeshavings (34e04o)]

Please check Bug #706783 - BIOS SETTING for VGA SHARE MEMORY SIZE was set to 32M. When changed to 64M Ubuntu Desktop Edition booted normally.

Athlon XP on Biostar Mobo M7VIG 400, w/1GB DDR2 RAM. On board video - no PCI or AGP video card.

[kurt belgrave (trinikrono)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Natty Narwhal. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.