Ubuntu
linux package

upgrade to kernel 2.6.27-13 broke the system

Bug #337214 reported by Michele Nasti on 2009-03-03

This bug report is a duplicate of: Bug #337019: [Intrepid] screen goes black after upgrading to kernel 2.6.27-13-generic. Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

Today I upgraded my ubuntu via update-manager and there were some upgrades regarding the last kernel, the 2.6.27-13 one. There was all, modules, headers, backports and so on. I upgraded and than, on reboot, I couldn't use the system. It started loading, with the ubuntu splash screen, but when it comes out to start the gdm there was no response at all. I couldn't switch to other terminals neither see the boot log. So I'm back with kernel 2.6.27-12 right now. If you need any information, I'm ready to help.

forgot: I'm using Intrepid Ibex 8.10 on my Dell laptop xps m1330. As far as I've seen, also some toshiba users have the same problem on the forums: http://georgia.ubuntuforums.org/showthread.php?t=1084783

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Package: linux-image-2.6.27-12-generic 2.6.27-12.28
ProcCmdLine: root=UUID=69fe1494-dad5-43f1-8f69-71f9f00b8da6 ro splash vga=792
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-12.28-generic
SourcePackage: linux

Tags:

Revision history for this message

Michele Nasti (artlover) wrote on 2009-03-03:

#1

BootDmesg.txt Edit (45.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (53.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")
HalComputerInfo.txt Edit (2.7 KiB, text/plain; charset="utf-8")
LsUsb.txt Edit (808 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (15.8 KiB, text/plain; charset="utf-8")
ProcCpuInfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Andy Whitcroft (apw) wrote on 2009-03-05:

#2

When you say "start the gdm there was no response" what do you mean specifiically? Was there anything visibile on the screen? Was the screen black? Is there disk activity? If you have another machine is the machine visible on the network?

Changed in linux:
status:	New → Incomplete

Revision history for this message

Michele Nasti (artlover) wrote on 2009-03-05:

#3

Well, actually the gdm doesn't start at all: i mean that there is a complete black screen, I only see the bluetooth and wifi led, but i can't do anything like switching to a terminal. maybe if I post a video of it it could be better? I don't think I can test the network pinging because I don't have a way to check without wireless. This afternoon i'll try out at home if I can.

Revision history for this message

Michele Nasti (artlover) wrote on 2009-03-05:

#4

I've started the recovery mode and xfix routine - to adjoust the graphic settings. It seems that the problem is with the nvidia driver, since the system started up without compiz and without nvidia drivers. Now I'm experiencing that with nvidia drivers rev177 I can't solve the issue and I'm trying rev173

So, the kernel update doesn't set up a proper graphical configuration and this causes ubuntu to boot and stop just before the graphic session.

Revision history for this message

Stefan Bader (smb) wrote on 2009-03-05:

#5

No, a video is not needed. It sounds pretty much like a duplicate of bug #337019. It would be ideal if you could help with dmesg logs from the failing case as well. I will mark this one duplicate. Please join efforts on the other bug. Can you connect to a wired network? If yes you might be able to modify /etc/network/interfaces by removing the comment or adding a line like this:

iface eth0 inet dhcp

This would enable network without network manager.

Revision history for this message

Michele Nasti (artlover) wrote on 2009-03-05:

#6

well, I think the problem is the same. I'll go on the other side. But as far as I'm concerned I think that the problem is with the nvidia kernel module.
I'll join the other bug, thanks for the support.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #337019 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.