I have a problem with the kernel update to 2.6.34.6. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update. Anyone else having this problem?
The last complete update failed on one package (Cups Common - 1.0 mb), each time I login the update is offered via update manager and each time it fails with this message:
W: Failed to fetch http://security.ubuntu.com/ubuntu/po...ntu3.6_all.deb Connection failed [IP: 91.189.88.31 80]
can anyone shed light on this - (I'm running 9.04 Jaunty)
Libnss3-1d xulrunner-1.9.1 xulrunner-1.9.1-gnome support
After click on install updates and entering password, a message says "Some of the packages could not be retrieved from the server(s). Do you want to continue, ignoring these packages? Yes/No.
If I answer No, this message appears:
W: Failed to fetch http://security.ubuntu.com/ubuntu/po....10.1_i386.deb 404 Not Found [IP: 91.189.88.31 80]
If Yes, it tries to download but immediately:
W: Failed to fetch http://security.ubuntu.com/ubuntu/po....10.1_i386.deb 404 Not Found [IP: 91.189.88.31 80]
It has always installed the updates with no problems, until these 3 updates remain in pending installation status.
Since I have updated last night from maverick to the latest beta of natty narwal, I'm having a lot of trouble getting Nautilus (desktop included) to work.
It seems to crash since the very start as when I turn off the computer, the message of "force exit" appears.
Ive just done the latest update ( AFAICT principally an upgraded kernel and firefox stuff)
I reboot the computer and then the perl script that was working whilst the upgrade was going on , now doesn't work , and i get prompted to save the *.pl file
WTF
mea culpa - on rebooting the browser , id left a stray 'print ' before writing the HTML header
When I try to update from a Debian notification of new updates the update window freezes without showing the updates. When I try to update in a terminal, I get the following message: "Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?". If another process is using it, I know nothing about it. How do I solve this problem?
My computer won't boot up from the installed version of Ubuntu. I was running 8.04 with no problems, but it stopped working after entering a command code to fix the limit for virus definitions on Avast. I removed the code, but now on boot up all I get is a blank screen and blinking cursor.
I can boot up with an Ubuntu 9.1 live disk, and it shows the installed version of Ubuntu and all my data are still there. Is there a way to do a general repair, that will enable my computer to boot up from the installed operating system?
Can't boot after upgrade to 2.6.31-19 kernel. Boot procedure stops on "Mounting root file system..." stage with message: /init: line 218: syntax error: 0xhda1.
I installed lucid the other day on my laptop, the first time it booted after installing it gave two error messages (unfortunately I can't remember what they said). The errors stopped appearing after that but once I select Ubuntu from the boot menu, it just hangs on a black screen for a good 15 seconds at the least before it runs the plymouth screen for like 2 seconds (the progress bar is already full) and then goes into the login screen. Here is my boot chart:
http://akgenome.com/files/bootchart.png
I was wondering if anyone can tell from that what is causing the issue and perhaps how to fix it? The boot log is like 3 lines long and is completely normal.
I have a dual boot (2 hard drive) system, and upgraded to 10.4. Booting into XP results in a flashing cursor that doesn't do anything. I know that GRUB screwed everything up, but I need to know what to do--and assume I don't know what I'm doing--to restore my dual boot ability.
Here's what I get after running a boot info script code...
For the past few days, my Ubuntu server (it is a desktop that functions as a server, Desktop installed) have been very slow. Today, it stopped responding to ping, I could not SSH into it (once, I managed to come so far that it asked for my password, but I got timed out) and I could not connect via VNC.
I switched it off, to boot it up again. Post completed, and the screen went black, before the white text "Read Error" appeared on the screen. I shut it down again, waited a minute or so, before switching it back on. This time, the "read error" did not show up. The "text only" startup for Ubuntu showed up, so I hoped it was all okay. It turned out it wasnt. I have some pictures: http://yfrog.com/4pimag0127xj http://yfrog.com/jnimag0128bj The top lines are code...
Any ideas on what could be the issue here, and how to fix it?
I bought a Linux magazine as a Christmas present attached to it was a 8GB distro-loaded disc sporting Ubuntu 9.10 (which is already on my system,) Mandriver, and open-SUSE 11.2 which I decided to install. Problem is, I can't get into Ubuntu anymore, where all my mail music ect is.
Ubuntu is listed with vista in window 2 of open-suse grub. When I try to boot Ubuntu I get an earlier kernel splash which is somewhat magnified and busybox v1.1.3. Vista boots OK.
Would un installing openSUSE put things back as they were? I can learn about open-SUSE using the DVD
I just recently upgraded my kubuntu install from karmic to lucid and now it takes about 10-15 minutes to boot. Directly after the upgrade it was pretty slow already, but it got worse every day from then. The karmic version was a wubi install I moved to a dedicated partition using lvpm. Here are the results from the bootinfoscript code...
My first attempt at seeking help has not been very successful. Probably to much of a narrative. If you want to know How I got in this mess see my first post.
Machine: Asus Eee PC 1015
What I know: I can't boot into anything but Live USB
What I think: Win7 starter is still there Mint9 is lurking as well Vista recovery partition exists
What I don't have: External USB DVD or CD drive Win7 Recovery
I'm running 10.10, I just recently installed a new graphics card, a Radeon HD4670, Ubuntu loads, and after it's finished loading, it goes to a black screen, and stops loading. I previously was using a nVidia 6200.
I installed kubuntu a while back on an AMD64 3200 and hit some problems I can't solve: ran out of space on /boot & opera KEYEXPIRED.This is a multiboot machine. I have the /boot partition on an extended ext4 /dev/sda5 which is 50 MB size which was fine when I first set it up. It seems however that it is no longer sufficient for GRUB2:
I have fedora 13 64 bit installed on my desktop. I have i3-530, 2G ram, wd 500g sata, ide samsumg dvd-rw, asus h55 mb, geforce 9600 low profile. problem is f13 often almost always freezes at boot up.i.e., after grub, that blue heart hangs on there waiting to be filled up.. but wait forever. what might be the problem?
I downloaded Fedora-13-i686-Live.iso from the fedora project web site, and did the instruction on how to burn it using dvd. i used nero selecting burn a CD from an image file. after doing that, i restarted my laptop to install fedora 13 choosing to start the boot at the disk dvd but it won't boot to run the installation. instead the laptop will resume booting to its previously installed OS, fedora 9.
i browse the dvd media and there are 3 folders namely EFI, isolinux, LiveOS and GPL file.
I've tried reinstalling Slackware64 13.1 to my PC a number of times over the past couple of days and I still have not been able to get it to boot.
Once it's installed I reboot and it tells me it can't find the operating system.
I've tried fdisk, cfdisk and GParted to set up the disk by deleting partitions and recreating them.
When I install and get to the section about installing LILO it says I have an OS/2 or Partition Magic boot manager on the drive, but there isn't. It asks if I want to install LILO in a compatible way with the boot manager and I say no, and install to the MBR. When I reboot it says it can't find the OS.
When I try to boot from the install DVD and get to the boot: prompt, I'll enter /dev/sda1 and it says there is no kernel.
I have recently completed a fresh install of 10.4 LTS which installed without a hitch. But I have noticed that since I have moved to Lucid on my T43 the hard drive light is constant for at least 20 mins after each boot. Everything seems to run ok albeit during this time apps take a little longer to open as the HD is busy doing some thing...I just don't know what! BTW I am running the Gnome desktop and its a fairly vanilla install.
This didn't happen in the previous Ubuntu version I had installed on here for several months prior.
Does any one have any ideas what this may be or how I could find out what it is that is using the HD for this length of time on boot.
I've created my own wheezy live usb-hdd using:# lb config -a i386 --mode debian --distribution wheezy --linux-flavours 686 -b usb-hdd --bootloader syslinux --memtest none -p xfce P: Considering defaults defined in /etc/live/build.conf P: Creating config tree # lb build The binary.img was created. Now if I try to boot from this image using qemu, I get a message "No bootable device" If I check this main partition using gparted, the flag is "lba" instead of "boot". Even doesn't work if try to change to "boot". How to solve this problem?
W: Some index files failed to download, they have been ignored, or old ones used instead. W: You may want to run apt-get update to correct these problems
I have a MSI a6000 Laptop (that has given me a lot of problems installing Ubuntu.
I finally had to run Ubuntu from a CD in nomodeset
Then when I go to install Ubuntu the only options it gives (regarding my harddrive) are to format my whole hardrive or do the partitioning. I have seen screenshots though where there is a third option on the same page to install ubuntu alongside a prior OS and dual boot.
Does anyone know why the "install alongside a prior OS (dual boot)" option doesn't show up?
I installed Kubuntu Lucid 10 days ago and it all went pretty smooth aside from the Plymouth res issue which I fixed following some online tutorial. It was working fine until yesterday when I updated the system. I think the update was primarily nvidia and maybe a new kernel, among other packages.
Now it won't boot... Plymouth shows then it goes to a blank screen, it looks like it's still working cause Ctrl + Alt + Del makes it reboot, but I can't get Ctrl + Alt + F1 to do anything and I can't get it to boot in Text mode (not sure if this was changed in Lucid). Also I can't access GRUB, it simply doesn't show up after holding Shift or any other key.
So I'm left with a completely unusable system and not sure how I can debug it since I can't get a console? Any hard way to make it boot into text mode?