Ubuntu Installation :: Initial Install Seems To Hang For Very Long Time
Nov 19, 2010
I'm attempting to install Kubuntu on a new laptop but seem to be having some strange issues. It's a Dell Latitude E5410 with 160GB HDD, 2GB RAM and Intel Core i5-520M(2.4GHz). I'm trying to install Kubuntu 10.10. When I restart the machine and boot from the CD for an initial install it seems to hang for a VERY long time. It will eventually get to the boot options (after hours) but seems sluggish. Once the install gets going everything seems decent except for that I can't seem to get it to finish. I know the CD is good since I used it to get Kubuntu on 2 desktops and another laptop in the last 48 hours. I've also burned another CD just to make sure. The checksum was spot on. Does anyone know what I can do to get this remedied?
My problem starts with trying to run "apt-get update", I get a long hang time for some reason. It hangs at Waiting For Headers, but there is more going on I believe so I decided to run "strace apt-get update" to find out what is going on. Now, this was my attempt at Canadian repos. After waiting for about 2 minutes on the strace I get a list of the following...
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
I am trying to install rhythmbox-0.13.1.tar.gz in my fedora 10 for a long time but i am in vain I downloaded it and i put it in my desktop.Then i did this:
# cd ~/Desktop # tar -zxvf rhythmbox-0.13.1.tar.gz Doing this a new folder named tar -zxvf rhythmbox-0.13.1 is created in my desktop. then i did this: # cd rhythmbox-0.13.1
I have just made a clean install of Ubuntu 9.10 and after installing all updates, GDM is taking a long time (about one minute) to come up after a clean boot, resulting in a regular console prompt.
If I issue "sudo service gdm start" it does come up promptly.
What can I do? Where can I see startup logs to try and identify any problems?
I keep hearing about how Ubuntu is supposed to be so much faster than Windows 7, but have yet to see any major difference in their boot times. I am dual-booting Windows 7 and Ubuntu 10.04 on an intel Centrino 2 processor with 4Gb of ram and both OS's take about the same time to boot. After I get to the bootmanager to select OS, if I click on Windows 7 it almost immediately goes to the GUI load screen with the windows logo. On the other hand, if I boot into Ubuntu I get a black screen for ~30 seconds before the Ubuntu logo even appears. Comparing GUI boot times, Ubuntu is clearly the winner, but they take the same time total.
Does anyone know what is making the long black screen or how to reduce the time? I would really like to show people how fast Ubuntu really boots.Immediatly before Ubuntu Gui starts, an message shows up for a second saying something like "Unknown adaptor version (2): You may experience some problems", it flies past so quickly that may not be verbatim.
I'm trying to fix a friends EeePC notebook (Asus) running a recently upgraded Ubuntu 10.04 from Karmic Koala. She used the update manager for the upgrade to 10.04 LTS and everything was fine until she had tried to install something from the Ubuntu Software Center (she doesn't remember what happened). After that, both Update manager and Synaptic stopped working.Update manager gives the following error:Quote:Software index is broken. ... Try to use synaptic for something?!...
Then Synaptic manager gives the following error:Quote:E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. E: _cache->open() failed, please report.And when I try that command, the terminal just keeps blinking with the cursor and does nothing for more than an hour. This is the output of the comand:Quote:
jasna@Jasna:~$ sudo dpkg --configure -a [sudo] password for jasna: Setting up moodle (1.9.4.dfsg-0ubuntu4) ...
Shutting down my machine takes a very long time! Not convenient when one want to pack his laptop (I don't dare to when the fan is still blowing).
Upon shutdown, I press 'esc' and see what's happening. The last commands seem to hang. First, shutting down the network interfaces seem to last long than needed (eth0, pan0, wlan0). Sometimes, it stalls also on "networkmanager disconnecting from DBUS" (or something like this ) (which is the very last command executed). Hmm, I will write the exact command down.
I recently broke down in the face of morbid curiosity and clicked that little version update button. it seems to run flawlessly (after i uninstalled the pesky touchpad) but it takes a long time to boot up now. at least a full minute. is this normal?
I will add also that it said my version of grub had been modified (which i dont remember doing, but may have) so i told it to leave the current one in place.
It takes me a while to log in the splash screen just sits there for ages before i get to the desktop. Never used to be this slow and I'm not sure why. Firstly, I'm running Ubuntu 11.04, standard DE. I do have conky starting up in a script but it has the & at the end of the line so I didn't think this would cause it (or is there some special case for log in time on how & is treated?). However as a test I will comment out the line in the script and see if it is the cause.
However just for general knowledge and in case that isn't the problem, how does one go seeing what is happening during the time from when one log's in and the desktop is displayed? Is there some kind of log that shows the date/time that can be enabled or is there a debug mode that can be enabled somehow via special keys or maybe from grub?
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
Trying to install Ubuntu (tried several releases) on HP Pavillion Pentium 4 Proccessor 515 2.93 Gig 1M L2 cache 533mhz 90nm . Have 1 gig ram and 1Tb hd. Hangs on initial install screen for ever. Tried versions from 8.10 (origional disk) to 11.01. Machine works perfectly on Windows XP but who wants that? The model is pavillion 1000 system number pl397aa.
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
in ubuntu 10.04 After logging in t All I had was the wallpaper & my widgets for around a minute, and then the usual upper and lower panels appeared.. didnt had this problem in 9.10
After I installed a new hard drive, when I booted up into Ubuntu, it would give me this error: "failed command: WRITE DMA". So I tried the workarounds and I guess it just covered the log with the Boot Splash, now it's taking a long time just to boot up.
My machine is taking ages to get from the login screen after booting to actually showing the gnome desktop (as in, over a minute). The bootchart is at golg-lucid-20101111-1.png
i reached step six where it states "6. When the root and swap partitions are formatted the base installation will begin. Note that your system may appear to hang at different points during the install but it hasn't. Just be patient." I have been staring at a blank blue screen with this blinking cursor at the bottom for 30 minutes and i was just wondering how much more "patient" will it take. for some system details. the system is clean / fist time run and anything installed on it.
I messed up the first installation of Fedora on my server. My setup is as follows: Fedora and Gnome - NFS system, No dual boot (Windows or anything) Fedora ISO DVD downloaded No kickstart or other tools. how to set this up, from the time I insert the disk and have it boot up (configged already to boot from it). I know how to wipe it clean at intall time. Is that the root directory? And, is /boot the actual boot directory? I'm just having a hard time uderstanding that. As I said, I just want a quick itemized list, step 1, step 2, etc, from partitioning, creating file system, mounting, etc. in the right order.
I'm running ubuntu on an i5-650, Intel H55 mobo system. I have 4GB RAM.I was running Lucid (AMD64) very happily, but then had a severe failure of the Samsung HD502HJ hdd (the smart report is showing more than 1000 bad sectors, increasing everytime I try to access the disk).I have replaced that drive with a Seagate ST3500418AS. Using ddrescue I was able to recover all but 9MB of the drive content. However, with my /etc, /proc and /opt directories having gone missing, I decided that attempting to recover the installation was a lost cause so I went ahead and installed Maverick onto the new drive.As part of this process I created a separate partition for my /home directory (recovered from the old drive).
Now, having installed only a few 'essential' packages (eg autofs5), I've realised that a lot of actions are taking well in excess of a minute to take effect. For instance, clicking on 'Places->Computer', it takes approximately 100 seconds before the Nautilus window appears.According to System Monitor, there is nothing using any significant resource during this time - it's as though something is waiting for a timeout to complete before actioning my command.If I look at the processes in System Monitor during this time, I can see that the Nautilus process is showing 'autofs4_wait'.
I have been using Karmic as a tool to extract important data from Windows Operating Systems where say viruses have necessitated a complete reinstall. I run the Karmic install disk and use the 'try before installing'option. It works well and I am able to 'rescue' anything I want by saving to a USB drive.Problem is that Karmic does take a relatively long time to load on a 'slow' PC.Does anyone have any suggestions on a 'slimmed down' Ubuntu that could be used in the same way which will load up quickly ?In most circumstances all I want to do is mount the C Drive of the stuffed PC and copy files to an external USB drive.
My PC is a Core2Duo7400/4gbRAM/9600GT. I install Enlightenment e17 on Ubuntu 10.04. It works perfect and runs very fast, but I have a little problem. When I open any browser (Firefox, Chrome, Opera) and a right would click -> save image takes a long time to open the box. I've noticed that happens only once, at first. if I open nautilus, it is the same, it takes quite at first, but only once. I think it is being loaded "some" of gnome and I want to load on boot.
I compressed a directory containing many image files. The directory amounted to 5.3gig. Compressed with TAR using .tgz the compression took a couple minutes at most and compressed down to 4.3 gig. Compressed using .bz2 the compression took about 90 minutes and compressed down to 4.2 gig. Hardly worth the extra time. Do these numbers look normal to you?
I don't know if it is just me but it seems like Ubuntu takes a long time to start up programs. For example, it takes me 10 seconds to start up "Ubuntu software center". My computer is a relatively fast one. It has 4 gb of ram and an intel core duo processor. I didn't install that many programs. Does anyone know what might be the source of the problem and how to fix it?
