9.10 beta fails to boot into LiveCD (flashing text on beta/straight black on later images) - black screen

[Tomas Cassidy]

Version: 9.10 beta
Graphics: nvidia 8600GT
Motherboard: Gigabyte GA-G31M-S2L

I'm trying to boot into the Mythbuntu 9.10 beta LiveCD environment. When the cd boots the list of options appears. If I select the option to start the LiveCD environment, the boot appears to start fine with dmesg output text scrolling down the screen. The screen then freezes mid-boot with some of the dmesg output text flashing on the screen.

[Mario Limonciello (superm1)]

Two things:

1) Did you check the media for errors? There is an option in the CD boot
menu

2) I suspect it will fail too, but could you by chance compare with an
ubuntu disk to make sure it's nothing in our startup process causing the
problems?

On Tue, Oct 6, 2009 at 04:31, Tomas Cassidy <
<email address hidden> <tomas.cassidy%<email address hidden>>>wrote:

> Public bug reported:
>
> Version: 9.10 beta
> Graphics: nvidia 8600GT
> Motherboard: Gigabyte GA-G31M-S2L
>
> I'm trying to boot into the Mythbuntu 9.10 beta LiveCD environment.
> When the cd boots the list of options appears. If I select the option
> to start the LiveCD environment, the boot appears to start fine with
> dmesg output text scrolling down the screen. The screen then freezes
> mid-boot with some of the dmesg output text flashing on the screen.
>
> ** Affects: mythbuntu
> Importance: Undecided
> Status: New
>
> --
> 9.10 beta fails to boot into LiveCD (flashing text)
> https://bugs.launchpad.net/bugs/444395
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>
Sent from Austin, Texas, United States

[Tomas Cassidy (tomas-cassidy)]

I tested both Mythbuntu beta and Ubuntu beta discs in virtualbox-ose on my laptop (different computer to the original test machine) and both were fine with the disc check and LiveCD environment. I tested both discs in the original test machine and both passed the disc check successfully. Both are failing on booting to the LiveCD environment, so it must be a bug with Ubuntu and not Mythbuntu. Can this bug be transferred to Ubuntu or do I have to create a new bug?

[MarcRandolph (mrand)]

Not much the Mythbuntu group can do to fix this... forwarding on to (hopefully) the correct group.

[swoody (swoody)]

Hello Tomas, and thank you for taking the time to report this bug. Can you tell us what the flashing text indicated? Also, are you sure you have the correct architecture for both your computers (i.e. x86 vs. amd64)? If you try booting a liveCD for the wrong arch. you may encounter many different errors while booting.

[emarkay (mrk)]

Is this an AGP card? If so, see if setting the AGP aperture to 255Mb or greater in your BIOS helps.

[emarkay (mrk)]

This same bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446208
was marked as duplicate of this one.

[Tomas Cassidy (tomas-cassidy)]

The following two lines are all I could make out from the flashing text:
end_request: I/O error, dev sr0, sector 1431904
Buffer I/O error on device sr0, logical block 357976

I tried to make a usb boot stick using the "usb startup disk creator" from the system->administration menu but I couldn't get the computer to boot into the usb stick (USB-FDD, USB-ZIP, USB-CDROM, and USB-HDD options all failed to detect the usb stick).
I successfully booted into "Mythbuntu 8.04 x86" and "Mythbuntu jaunty alpha3 AMD64" LiveCD environments, so the cdrom drive is working fine.

The nvidia card is a PCI Express card (there are no AGP slots on the motherboard).

My next option will be to try the Ubuntu karmic beta x86 disc to see if it's a problem with just the amd64 release (when the disc finally downloads).

[Tomas Cassidy (tomas-cassidy)]

The same problem is occuring with the Ubuntu karmic beta x86 disc. The disc reported no errors when doing the error-check from the boot menu.

[MarcRandolph (mrand)]

Thomas, thank you for continuing to help debug this. Does booting in safe graphics (or any other) mode help?

[Mario Limonciello (superm1)]

Safe graphics mode was not available on live CD versions before 1.200 of
casper due to bug 423969. So tonight's build of mythbuntu 20091010, or
today's build of ubuntu 20091009 will support it properly.

On Fri, Oct 9, 2009 at 10:35, MarcRandolph <email address hidden> wrote:

> Thomas, thank you for continuing to help debug this. Does booting in
> safe graphics (or any other) mode help?
>
> --
> 9.10 beta fails to boot into LiveCD (flashing text)
> https://bugs.launchpad.net/bugs/444395
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>
Sent from Austin, Texas, United States

[Tomas Cassidy (tomas-cassidy)]

I tested with the 20091009.1 daily-live iso image. If I selected "safe graphics mode" and then selected the LiveCD option, the system booted successfully into the LiveCD environment. I was also able to install the nvidia driver from the restricted drivers manager and logout+login to Ubuntu with the nvidia drivers enabled.

When I tried to boot into LiveCD environment using the normal graphics mode (not selecting any alternate boot options), I only got a black screen. The boot process itself appeared to go successfully because I could go to VC1 (ctrl+alt+f1) and type "ubuntu<enter>" to login on the VC1 terminal and then "sudo halt<enter>" to successfully shutdown the system. At the end of shutdown the white text showed up saying to remove the disc from the drive before pressing Enter to shutdown.

[Deepak Ramanath (deepaknr)]

I have a similar but a little unique issue.

I tried a USB lice CD of the Ubuntu 9.10 beta. As soon as I chose the options, it takes for a while and the desktop appears. However the desktop would be a total freeze !. Neither keyboard nor mouse works.

I tried on two different machines having intel CPU but one with nvedia and the other with ATI graphics cards. In both the system the desktop just freezes.

[Surbhi Palande (csurbhi)]

@Deepak Ramanath, can you please file a different bug for this, since you do get a desktop and then it freezes ?

[Surbhi Palande (csurbhi)]

@Tomas Cassidy, thanks a lot for the bug report and helping to make Ubuntu better.
Since you can get into VT1, can you please also attach the output of the command 'ps -ef'.
Further is it possible to get the output of the following command:
1) dmesg
2) lspci -vvv
As a suggestion, you could either take a picture of the output or if possible redirect the messages
to some usb device ?

[Tomas Cassidy (tomas-cassidy)]

@Surbhi, I can't get the output of those commands as the screen is blank on the VT1 as well. I only know it goes there because I can type the commands from memory and get the end result of the computer rebooting/halting. I'll boot into the safe graphics mode and get the output of lspci -vvv. I will also try to take a picture or video of the output when i get the chance. I might also be able to mount a usb stick and copy the output from commands onto there, but i can't guarantee because I can't verify the commands that are typed in.

[Yuri Nikiforov (nikiforov2000)]

I've got simular problem, but not wil live CD. I have ubuntu 9.10 beta that I can't boot. After usual update and reboot everything is normal until X is going to be started. Instead of gdm-login screen I have console with flashing text about boot process with normal messages and login prompt. It's impossible to login because system responds very strangely on keyboard, I think 9 of 10 keypresses are missed, I can't even type my login correctly.

[Yuri Nikiforov (nikiforov2000)]

Sorry, forgot to mention. On ubuntu alpha 3/4/5/6 I didn't trapped into this. My hardware: ASUS A7V880, Athlon XP 2500+, NVidia GF6600GT AGP, 1.5Gig RAM. Hardware wasn't changed recently.

[Tomas Cassidy (tomas-cassidy)]

I was unable to get the output of anything except for lspci -vvv from the safe graphics mode. I thought that the output of dmesg/ps would be useless if it came from the safe graphics mode environment as there is no problem running in that mode.

[Surbhi Palande (csurbhi)]

@Yuri Nikiforov, can you please open a separate bug for this, since your bug is not related to live cd?

[Surbhi Palande (csurbhi)]

@Tomas Cassidy, thanks for the output of the lspci -vvv.
Can you also try doing this: Connect a usb memory stick, boot into normal graphics mode, and try redirecting the output of
ps -aef to some file on the usb stick, by typing the command blindly ? If we can have the ouput of ps -aef, then that will be very helpful !

[Tomas Cassidy (tomas-cassidy)]

I've tried doing that but got nowhere with it. When I tried I couldn't
work out if the USB stick had been mounted properly and where it was
exactly mounted. I'll try a few more things today or tomorrow to try
to get the output of ps.

On 20/10/2009, at 6:56, Surbhi Palande <email address hidden>
wrote:

> @Tomas Cassidy, thanks for the output of the lspci -vvv.
> Can you also try doing this: Connect a usb memory stick, boot into
> normal graphics mode, and try redirecting the output of
> ps -aef to some file on the usb stick, by typing the command
> blindly ? If we can have the ouput of ps -aef, then that will be
> very helpful !
>
> --
> 9.10 beta fails to boot into LiveCD (flashing text on beta/straight
> black on later images)
> https://bugs.launchpad.net/bugs/444395
> You received this bug notification because you are a direct subscriber
> of the bug.

[Surbhi Palande (csurbhi)]

@Tomas Cassidy, can you try putting the output on some file in your home folder ?
It will be a great help !

[Surbhi Palande (csurbhi)]

@Tomas Cassidy, sorry, please ignore the above comment.. !!!! If you can get the output on the usb.. that will be great !!

[Tomas Cassidy (tomas-cassidy)]

When the computer boots into normal livecd mode, I can ping it from another mac laptop attached via ethernet which is providing internet sharing to its ethernet port. I can't seem to get any other response from the computer, regardless of what I try typing into the keyboard.

There are no problems when booting the livecd in safe graphics mode, so I'm guessing its a problem with the graphics somewhere.

Are there any other ideas on things I could try to debug this further, considering that I can't get the output of any commands (maybe boot options?).

[MarcRandolph (mrand)]

Thomas, when you say you can't get any other response out of the computer - are you hitting certain sequences that you expect would do something (i.e., hitting keyboard short-cuts that should produce some action [maybe execute "sudo reboot"])? If that were to work, other commands could be executed (while typing blind) to save off certain debug info.

Another thought that came to mind is adding a second of video card (of a different kind/brand).

[Tomas Cassidy (tomas-cassidy)]

Marc, yes that's exactly what I'm doing. I'm trying the keyboard shortcuts that should switch to VC1, login to VC1 and then reboot/halt. I've also tried to login to a VC and connect to a local webserver with w3m to get a "GET" request appearing in the apache logs. While that works from the safe graphics mode (where the graphics are working), it fails on the blank screen. The fact that both of these fail suggests that it might not be actually doing anything or even getting as far as the login prompt on startup.

The motherboard has integrated Intel GMA 3100 graphics so I will try to remove the nvidia card and boot connected to the intel graphics.

[Russell Phillips (ignissport)]

I'm also getting this problem. It fails to load on my HTPC (P4, 2GB RAM, Nvidia 6600 AGP). I have tried both the beta and the RC x86 mythbuntu images using VGA and YPbPr connections to the display panel (Samsung 40" LCD TV).

The first splash screen displays correctly (small pulsing mythbuntu logo)

I have snapped 3 shots of my LCD during the load. First, it could not load the package sources. It then dumps to shell. It crashes after about 1 minute. This was enough time to run 'top' and show that the install python script is running in the background.

The third shot is the blinking screen. At this point the console is unusable. gdm/xorg does not initialise.

Strangely enough, the same CD boots fine on my other machine (AMD Athlon X2, ATI 780G/HD3200 chipset).

[Russell Phillips (ignissport)]

OK, after trying different combinations, it worked when I swapped my 256MB AGP Nvidia 6600 for a 128MB Nvidia Geforce3 Ti200.

Also the first screen with the broken packages only occurs when I select "Install Mythbuntu" and not "Start without making changes to my computer". It's probably an unrelated bug.

[Mario Limonciello (superm1)]

Rusell:

I'm thinking that your bug with selecting "Install Mythbuntu" ending up with the problems is actually bug 457858 which was fixed shortly after RC.

Can you please confirm what happens with "Start without making changes to my computer"? I'm a bit confused if there is actually a (separate) problem there too.
Also, if there are problems there, does "F4->Safe Graphics Mode" help?

[Tomas Cassidy (tomas-cassidy)]

note: all previous tests were done using the nvidia card connected via S-VIDEO output to a TV screen.

Testing with the 20091009.1 daily-live iso image (amd64), I tried to boot into the livecd environment using the integrated Intel VGA graphics on the motherboard and a standard monitor. After startup, it showed the small white ubuntu logo in the middle of the screen while loading and then successfully booted into the livecd environment.
I then tested with the VGA graphics port on the nvidia card connected to a standard monitor. After startup, it had a blank/black screen (no white ubuntu logo) while loading but then successfully booted into the livecd environment. On this test, the graphics output didn't appear until it was showing the brown Ubuntu splash screen with the horizontal loading/status indicator.
I tested again with the S-VIDEO output connected to the TV screen and it was as originally reported. After selecting to boot into the LiveCD environment from the initial boot screen the graphics output turned blank/black and didn't show anything. I could then press the power button on the computer case once and it shutdown and ejected the CD like normal (still no graphics output while doing this).

[RobL (rlacina)]

Hi, I also get this happening on 9.10 Final Release (Build 20091028.5?) on "Try without making changes..." and also "Install..."

i.e. Boot menu shows OK, but when I try to boot to LiveCD or run the installer, I get the white pulsing Ubuntu Logo, but after a while it then drops to text mode, screen flashing, keyboard unresponsive. Last line of text is "ubuntu@ubuntu:~$". (See attached screenshot for similar example of text)

This appears to occur about the time in the boot sequence where the new brown splash screen would normally appear.

System AMD Athlon 64x2, nVidia 6600GT Graphics (XFX) with Asus Widescreen monitor via DVI connector, Gigabyte GA-K8NF-9 motherboard, 1 GB Ram, Logitech G11 USB keyboard and Microsoft Bluetooth mouse

Tried Normal + Safe Graphics mode, also various other kernel parameters via F6 on boot screen - same result every time.

Note: With prior releases (8.04/8.10/9.04) I've always had to use safe graphics mode to use the live CD or run the installer on this system.

The CD I'm using checks OK using CD Checker on boot screen and also boots OK in Virtualbox on this system.

[pauljohn32 (pauljohn32)]

Me too.

This is caused by a mismatch of the video configuration from your old Ubuntu with the new one.

Here is a solution. Log in with recovery mode, move /etc/X11/xorg.conf out, so the system starts without taking into account your old settings. It will boot into a generic/open set of drivers. From there, you can install what you need.

[RobL (rlacina)]

pauljohn32 - this might be the case if I was upgrading an existing system, but it's happening in LiveCD mode as well as running the installer for a fresh install onto a new partition (for testing). At this point there clash with old driver settings and is no old xorg.conf to remove. Looking at similar bug reports in the forums and in launchpad, it seems to be mostly affecting nVidia users (possibly running amd64).

I haven't seen any fix offered that works,

My current version that I use is still at 8.04 and I what I normally do is install the newer versions of Ubuntu into a new partition to play with and see if it's worth making the change. 8.10 & 9.04 didn't really seem to offer me any significant benefits than what 8.04 did, so I've stuck with it. 9.10 with it's faster boot times could have been the trigger to move up, but I can't run it on my system apart from in virtualbox

One of the reasons I have stayed with Ubuntu is because it has always worked on my PC. this release is the first one that won't run.

Rob.

[MountainX (dave-mountain)]

I think I'm having the same problem with the Mythbuntu 9.10 release on a Thinkpad T61p.

I posted here: http://ubuntuforums.org/showthread.php?p=8257908

 Mythbuntu 9.10 will not boot up
I hope I'm posting this in the right place now... I have a grub2 boot partition on (hd0,1). I installed Mythbuntu 9.10 32bit on (hd0,9), a logical partition and I installed the boot loader into that partition using the advanced option at the end of the installation process. I have the grub2 on the boot partition set to chainload Mythbuntu on (hd0,9).

What happens is that Mythbuntu seems to go through the bootup process correctly but it stops at the console login and the whole screen is flashing/blinking. In fact, even keyboard input is sporatic. I'm afraid the system is in a state that could damage the harrdware. It is not even possible to type enough to log in. The only option is to reboot.

I thought the problem was related to a defective installtion, so I installed fresh again (reformatted partition). I get the exact same problem after the second install.

I have Kubuntu, sidux and openSUSE on other partitions. All will boot up correctly. Mythbuntu is the only OS that will not boot. However, if I install Mythbuntu without putting the boot loader into its partition (i.e., using the whole hard drive) Mythbuntu will boot correctly on this computer.

My computer is a Thinkpad T61p.

There is some background in this thread (http://www.linuxquestions.org/questions/linux-general-1/opensuse-wont-boot-after-i-resized-its-partition-grub2-related-766528/), but it is largely unrelated.

------------------------

Is there anything that would prevent Mythbuntu from booting from a logical partition?

I used Super Grub Disk 0.9799 to boot up Mythbuntu with these commands:

Code:
kernel (hd0,8)/vmlinuz
initrd (hd0,8)/initrd.img
boot

I get the same error as described above.

I tried the installation on a 2nd computer and I got the same or very similar result.

As soon as I hit CTRL-ALT--DEL, the flashing stops and the PC proceeds to halt processes and reboot normally.

Seems like a GDM issue if I had to guess...

[mangojohn (mangojohn)]

downloaded Mythbuntu 9.10 today 2 times. one via bit torrent other regular desktop download. Neither would load and I tried on two different hard drivres and got the same result. The program started to load and gets to the screen where you choose the method of install I chose to install the program to disk but nothing really happened the program let me pick a language but then merely displayed a small mythbuntu logo for a period of time and then eventually the disk player stopped. I checked both disks for errors and neither indicated any errors. One disk had an existing vista on it the other had just been formatted. I am not fluent in ubuntu so I will probably wait a couple months and try then. I have tried mythbuntu in the past but the program was not real user friendly. maybe this version will be workable when I can finally get it to load.

[cdyring (clausdyring)]

I have the same issue:

I upgraded from 9.04 to 9.10 via apt. Worked fine.

I then added another harddisk and added 8.04 LTS. Worked fine, but I was unable to boot into 9.10 because GRUB got overwritten. Oops.

I tried to boot into the 9.10 live CD for intel 32 bit, which I downloaded after release. Flashing screen at half second interval and poor keyboard response, will not start x. Installer will also not launch, same symptom.

I then tried the alternate installer cd, 9.10 32 bit intel. Got 9.10 installed on a new partition.

Now I have:

9.10 (old upgrade from 9.04): Boots just fine
9.10 (new) will not boot, same flashing screen problem
8.04 LTS.. haven tried it yet.

I got a picture of the screen when trying to launch the live CD.. is it any use, or is there some log I could check on the old 9.10 filesystem?

I have a nvidia gforce 6600. The old ubuntu was running on the "nvidia driver".

[cdyring (clausdyring)]

Tried to boot the new ubuntu 9.10 into recovery mode and type startx at the prompt, after login in at the terminal.

X failed, see attachment.

I have a LCD monitor from IIYAMA, prolite E1900S.

Looks like X for some reason thinks the screen does not support modes of the nvidia card?

[cdyring (clausdyring)]

error message from trying to start x on ubuntu 9.10

[Godders (frublob)]

I _was_ having the same sort of problem, i.e. unable to install Ubuntu 9.10 with flashing text during boot-up and no keyboard response when trying either the Live CD or the install.
I'm using an Nvidia 6600 and a Gigabyte KT400 with VIA VT8235. I changed the BIOS AGP slot settings from Auto to 8X and this has allowed me to install. N.B. I may have inadvertently reset the BIOS to fail-safe defaults before this but I don't think that was the problem.

[Randy Rossi (randy-rossi)]

I had the same problem with my Nvidia 8500 GT. Solution for me was to hook up my display using the VGA connector instead of the component out connector. Somehow, the display mode is different and the X server could not start up when connected via component.

[cdyring (clausdyring)]

I can confirm that. VGA connector lets the system boot, DVI connector is no go. And it is the same screen that I am connecting.

[striscio (gianpaolo-racca)]

I have the same problem with my Home Theater system: Asus M2NPV-VM with Nvidia onboard video chipset. After the silver Mythbuntu logo the screen remains black and X doesn't start. If I choose failsafe mode all I got are blinking VTs. I will try tomorrow to change AGP settings, but it's difficult to understand such a big step back in the installation experiences (it's the first time in two years I can't install Ubuntu on that machine).
I tried with a livecd and with usb startup.

[Kurt Stephens (kurt-launchpad)]

Delete /etc/X11/xorg.conf and rebooting allowed gdm to start with a stock driver, reinstall NVIDIA's drivers.

[striscio (gianpaolo-racca)]

Is there any news on this bug? I tried Mythbuntu and Ubuntu and both of them have the same behavior.

[Kurt Stephens (kurt-launchpad)]

The problem reappears after a kernel upgrade (Linux 2.6.31-15-generic-pae #50-Ubuntu SMP Tue Nov 10 16:12:10 UTC 2009 i686 GNU/Linux).

The solution is:

1) boot recovery mode.
2) telinit 3
3) reinstall NVIDIA drivers.

Details: Dell M4400 laptop:
 > lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation G96M [Quadro FX 770M] (rev a1)
03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
0c:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100

[Kurt Stephens (kurt-launchpad)]

BTW: installing a new kernel probably causes GDM to start X with a stock driver, since the nvidia kernel driver only exists for the previous kernel version. So this probable a kernel or a stock X driver problem.

[Kurt Stephens (kurt-launchpad)]

BTW^2: I did a net upgrade from 9.04 to 9.10. I got flashing VTs then and after the last kernel update. I did not have problems doing net upgrade on two other laptops, one has Intel GM950, the other has NVIDIA Quadro.

[jmer1234 (jmer1234)]

I have run into the same issue with the flashing login and unresponsive keyboard on a Dell Dimension 4500. I am now on my third install with a disk burned from an image downloaded on 2010-02-27. I believe it is the nVidia drivers. During both of the first two installs, I elected to use the nVidia/non-free drivers and was not able to log in after the install reboot. The third time, I left the default driver package selected (I can not remember exactly how the package was referred to in the drop down) and have ignored the pop-up icon asking me if I would like to enable the third-party drivers for 3d acceleration and am not having an issue at this point. I have now been able to run all of the updates, but since this is strictly to be a backend server, I am reluctant to load the nVidia drivers. I am simply adding this comment so that hopefully others will at least be able to do an install and get to the point where they can run the updates, and possiibly be able to fully utilize their nVidia cards.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.