I have ubuntu 10.10 installedWhen it was new It was too speedy in starting upbut, Now It is taking about two to three minutes to getting started.I tried to remove some applications from System/Preferences/Startup Applications,But no differenceI want to speed my systemIt has no problem in speed after starting up
View 14 RepliesI have f11 installed on as a vm on virtualbox 3.0.4. It takes forever to boot. I modified /etc/udev/udev.conf and changed udev_log="info" to udev_log="debug" and rebooted the system. When the progress bars came up I hit Esc and watched the boot process. Udev runs through approximately 7-800 items before it ever tries to load anything else. Is there a way that I can change this? I have been through the forums and can't find anything similar to this. I thought maybe that it was the "Floppy" issue so I went ahead and blacklisted the floppy drive (as this is a vm I don't have access to the BIOS) anyway.
View 2 Replies View RelatedI have just installed Ubuntu for the first time using a USB drive and everything went fine during installation. However now during the boot phase I see 10 or so lines of
[14.24024] ata5: COMRESET failed (error=-16)
The numbers prior to COMRESET change with each line but the rest remains the same. I am extremely new to Ubuntu or Linux for that matter as this boot process is also taking about 3-4 or even 5minutes as it slowly cycles through each error. Once 10 or so lines have popped up the computer finishes starting and I can log in fine and everything.
I am using Debian sid 4.1.3-1 and when i shutdown the system it takes 3 - 5 minutes before actually shutdown, there is only a black screen until the hdd led start flashing and after that the system finally shutdown. The weird part is that sometimes it happen in less than 30 seconds , how can i figure out where the problem is ?
View 8 Replies View RelatedWhen i log in, i used to be able to be able to start doing things on my desktop straight away. Now when i log in, it takes about 8 seconds for the panel to appear etc. I looked at startup applications and the problem isnt in there i believe, as i have less running than what comes with a fresh install.
View 1 Replies View RelatedI've been running 10.04 (lucid, Kernel Linux 2.6.32-25-generic, GNOME 2.30.2) for about 3 or 4 months and everything has been great, until yesterday.
All of the sudden, bootup has started taking longer than usual and the panel at the top of the screen with "applications", "places", etc. doesn't appear until the machine has been running for at least 2 minutes.
Also- the mouse and keyboard (and my external hard drive), all of which are usb, do not respond until about 2 minutes after startup appears to have finished.
So, basically, here's what happens when I power the machine on:
1. Everything functions quickly, and as normal, until my desktop picture shows and the icons on it appear.
2. Whereas before I would have had mouse and keyboard use (and use of the top panel with applications, places, etc.) at this point, I don't have use of any of these.
3. So I just wait, without keyboard or mouse, etc. for about 2-3 min and all of the sudden the top panel emerges, the mouse and keyboards start working, and then the external hard drive appears.
4. As if this weren't annoying enough, after everything above starts to work, opening applications (e.g. firefox) takes a lot longer than it used to. Basically, starting any application after startup takes a long time the first time it's opened.
I don't understand why this is happening. Before this, startup was super fast, and everything was working great. I dont know how to check into recently loaded updates, but perhaps something got changed there that is causing the problem.
I haven't changed anything hardware related at all, so I don't imagine the change in performance is due to anything on that front, but I could be wrong.
why it's hanging up.It hangs up 5 mins after startup whether or not any application is running.
View 2 Replies View RelatedI'm using mencoder to capture audio from a Encore ENLTV-FM3 video capture device. I have recently noticed that, since one week ago, when the machine was forcibly restarted due to a power outage, all recordings are slightly pitched, they play back slower than they should.
I narrowed down the problem to the following command line:
$ time mencoder -really-quiet -tv driver=v4l2:device=/dev/video1:chanlist=us-cable:audiorate=32000:alsa:adevice=hw.1:input=0:amode=1:normid=11 -endpos 00:10:00 -ovc copy -oac pcm -of rawaudio -o test-32000.wav tv://69
real 9m54.886s
user 0m5.536s
sys 0m1.740s
$ ls -l test-32000.wav
-rw-r--r--@ 1 martin martin 76800000 Mar 15 17:20 test-32000.wav
Somehow, mencode managed to gather precisely 10 minutes worth of raw audio in 9m 55s. That's not physically possible, unless the capture device's A/D converters are "overclocked". I can't think of any other explanation besides hardware failure. Can that be? Could it be that something got burnt during the power outage and now the capture device's internal clock went nuts?
Since the machine's restart, I've also noticed dmesg is flooded with entries like this:
CE: hpet increased min_delta_ns to XXX nsec
Which seem to indicate that the computer's high precision event timer is somehow out of sync. Does this have to do with the audio issue? Can it be that the audio converter's sample rate is linked to the HPET? I'm totally lost here. Has anyone bumped into something similar?
Ever since a standard update a couple weeks ago I've had a myriad of problems, the biggest one though being boot time. Here's what happens when I turn on the machine: From bootloader (splash) to kernel loader (blinking cursor) = 50 sec. Kernel loader to splashscreen = 20 sec. Splashscreen to login prompt = 55 sec.login prompt to keyboard working = 26 sec. (wireless, wired works right away) Logging in to Desktop = 25 sec. 176 secs = ALMOST 3 MINUTES UNTIL I'M IN THE DESKTOP!!
That's worse than Vista. I've tried a number of things. For the Bios I read disabling floppy helps. I tried installing bootchart to see what's going on but it won't load save the .png file..? I installed bum and disabled some services. I tried profiling in grub... Nothing has made anything any better.
No idea why it takes so long for my wireless keyboard to start working. I'm really not sure where to start here since it's loading so slow at every point of the startup process.
I have a troubling issue. I log into Linux Mint 9 (fully up-to-date) on my Samsung Q320 laptop with power connected and after a few minutes it seems like the entire X session dies, I am logged out, all processes are killed and I am presented with the normal GDM login screen. When I first installed Linux Mint, this never happened. I have the NVidia closed-source driver installed and when the system logs me out, it immediately restarts X loading the NVidia driver which flashes the logo on screen. This all happens instantaneously, so it is not a reboot of the machine, just a restart of the display manager it seems.
There does not seem to be any cause for this. I have disabled all screen saver and power management settings that may lead my system to auto-logout of Gnome. The system log doesn't indicate anything unusual happening. Confused about where to to take it from here bar and fresh install of the OS. Perhaps there are some X11 logs I should be checking.
Update: Moved to Ubuntu 10.10 and its recommended NVidia driver and have not experienced this problem since.
Anybody notice a slowdown in their boot times? I have had F11 (64 bit) running for about three days and it is taking twice as long to boot as when I first installed. I have not done much other than configure my wireless printer and change a few icons. I have Compiz cube effects running but I did that right away and it made no difference in my system speed. If anything I thought I should be booting faster after disabling a few things in the start up menu that I dont need.
I went from about a 30 second total boot to almost a minute to the login screen
top - 15:13:37 up 11 min, 2 users, load average: 0.35, 0.24, 0.12
Tasks: 150 total, 1 running, 149 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.8%us, 1.1%sy, 0.0%ni, 98.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 3062244k total, 523208k used, 2539036k free, 31580k buffers
Swap: 5111800k total, 0k used, 5111800k free, 206328k cached
I just want to find out if anybody else is having a similar issue before I start trying to disable services one by one. When I boot in to F15, everything runs fine up to were it starts loading the CUPS module then it hangs for about 2 to 3 minutes, the next thing to load is Samba shares. So it could be either of these or it could have nothing to do with them. Just to add that I made 100% sure that all my samba shares mount fine and are online and have no shares mounting in my fstab file.
View 2 Replies View RelatedMy ubuntu(10.10) installation takes a relatively longer time (90 seconds) to boot. I think part of the problem might be related to an error message during boot related to usb drivers.
Code:
[2.717076] usb 4-1: new low speed USB device using ohci_hcd and address 2
[3.244051] usb 4-2: new full speed USB device using ohci_hcd and address 3
[12.029046] /build/buildd/linux-2.6.35/drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed
I have attached the relevant part of dmesg output also.
I just installed fedora 12 on my new harddrive, and it's booting up extremely slow (but once I'm logged into the system, it all seems to run fine). Right now my set-up looks like this: 1TB HD: new install of fedora 12 300GB HD: Windows xp & my previous install of fedora 12
My previous installation of fedora 12 never booted this slow until after I installed Fedora 12 on my new HD. It seems to freeze right before the log in screen, and after I log in, both installations take about a minute to get to a usable desktop. I pressed the Esc key during startup to see if anything was wrong, and it didn't hang up on anything. However, as it was loading the login screen (where it first begins to get sluggish), I was kicked out of the terminal view and forced to wait in the gui for log in.
On my PC, I use GRUB to manage my dual-boot startup on my PC. Every time I update my Linux, It adds another 2 startup options on my HD for every distro I have. (The Normal and Recovery modes for the new version.) I would like to add the VortexBox distro someday.
Is there a way for me to get rid of the older versions of Linux distro's on my GRUB menu so I just see the newest? I have 6 options for Ubuntu 10.10 and 4 options for UGE 2.8..
I have two hard drives in my desktop. One HD has a working Ubuntu system-hence the ability to post here- and the other contains Windows XP Pro. When the XP drive crashed I was able to re-install an image I had saved using Acronis. Unfortunately the dual-boot option at startup is no longer available. I can only boot to Ubuntu. Not so bad really but there are some programs on Windows that I need to use. Is there any way, using Grub perhaps, that I can reconfigure an MBR to include the second hard drive and the Windows system?
View 1 Replies View RelatedAfter Gnome logon it may hangs in any moment (window scroll, app start, opening url)
If sound was playing in that moment it continuously repeats last sample (about 1 second length), but do not respond to mouse move/click or keyboard. If to let it stay in this state nothing change - sound sample still repeats and no response to input. I need to reboot it by reset button. Sometime when I press reset nothing happen then after couple of seconds computer turns off, after 1-2 sec on and then starts booting.
During first 15-20 minutes after booting it may hangs multiple times but after that it works without problems.
Tried do not logon 20 minutes after boot - do not help, it hangs anyway. Only helps logon and do nothing for awhile.
This behavior have started after F12 installation. F13 installation changed nothing, only F11 worked perfectly.
When booting up eb4 distro (eebuntu)mouse pointer although active during start-up disappears when gnome is started for 5-10 minutes, sometimes longer. Gnome failsafe it will appear but I can not identify the fault.
View 1 Replies View Relatedhow to disable boot,startup the clamav on rhel/centos.
View 1 Replies View RelatedI have installed Koha on Debian Lenny. It does work well, but I have to manually start the koha-zebra-ctl.sh by entering /usr/share/koha/bin/koha-zebra-ctl.sh start The is, however, that this starts at boot from /etc/init.d/koha-zebra-daemon. Like /etc/init.d/koha-zebra-daemon start (does not work now) In the koha-zebra-daemon file I have:
#!/bin/sh
# Quick start-stop-daemon example, derived from Debian /etc/init.d/ssh
set -e
# Must be a valid filename
[code]....
I have made a symbolic link;
ln -s /usr/share/koha/bin/koha-zebra-ctl.sh /etc/init.d/koha-zebra-daemon
I have tried checking whether the symbolic link exists with readlink, but this never seems to return anything anywhere.
Machine Specs: Asus P5B Deluxe w/ Intel Core 2 Duo E8400, 8gigs of ram and an Asus GeForce 8400 GS. I downloaded and installed the x86_64 DVD Installation disc for Fedora 11 the day of the release. I allowed the installer to utilize 100% of the disk with the default partition configuration. I only installed KDE.
Upon first boot the machine didn't boot in under 20 seconds, but it wasn't slow enough to give it any though. Once logged in, everything ran great. The system has been running great since the launch date. I rebooted once or twice since them and thought the same thing as the first boot, not particularly fast, but not slow enough to care.
This morning I rebooted and it almost seemed broken. It takes about 20 minutes to get past the loading bar, and way too much time to log in. When the loading bar is going I hit escape. It looked like "Starting system message bus" took the longest, but it wasn't the only slow thing. After some more time, the background for the log in prompt appeared. Once the log in prompt fully appeared I mistyped my password. It took a good four minutes to authenticate unsuccessfully. I reentered my information correctly. It took another four minutes for the prompt to disappear, then it continued to load very slowly.
Hardware: Toshiba NB200 with Atom 280 & 2GB, 160 GB HD Everything works great except the boot time. My default boot is F11 & when the system starts in "yuk" Windows it only takes a few seconds! but when I start in F11 it takes 15 - 20 minutes for it to start. No error messages, nothing in dmesg, standard configuration. The same system with Win XP & F10 worked fine?
View 4 Replies View RelatedIt's been a while since this problem started. I have an Acer Aspire 4720z laptop with Ubuntu 10.10 installed. My laptop takes a whole damn 1.5 minutes to boot up and login (measured according to bootchart; I have auto-login enabled) (The majority of this 1.5 minutes is taken up after boot up, so it might indicate a problem with Xorg.)I don't know whether this is relevant, but when I boot up, a message gets displayed: "ata4.01: failed to resume link (SControl 0)". Also, this problem started right around the time I upgraded from Lucid to Maverick, so it could be some problem with my upgrade.find the source of this issue.ATTACHED: bootchart image from last login.boot.log:
Code:
fsck from util-linux-ng 2.17.2
udevd[370]: can not read '/etc/udev/rules.d/z80_user.rules'
[code]....
Every time I boot up OpenSUSE 11.3 it hangs at the same "position" for approximately 3 minutes and then continues to boot. Unfortunately I see no corresponding error log e.g. in dmesg output. Hence, I don't know what is the reason for that. Here is my dmesg output. The delay occurs at 20 seconds after beginning of boot process (line 1085). I also analyzed the boot process with bootchart.
My computer: Notebook Lenovo ThinkPad R400.
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.
This is kind of cross post from the 10.10 beta forum, but since that thread went by without a solution, forum (and thread) are locked and this problem still exists, I'll try again.
When I reboot my machine, it seems to go pretty quickly. However looking at the log it seems that most everything is running after about 8.6 seconds, and then USB starts loading up. The first log entry regarding USB comes at 32 seconds, second one at 62 seconds. The keyboard starts working at 84 seconds and the mouse at 166 seconds.
Note, this same system was running 9.10, 10.4 and various other distros I tested without such problems...
I've removed all hubs, everything is directly connected to the computer. code...
I have a Dell Vostro 200. Have been running Ubuntu on it for 18 months - no probs. Recently it became very slow to boot. 5-10 minutes before Ubuntu startup screen appears. Have installed Ubuntu 10.10 (on a reformatted hard drive) today. No change. It's fairly certain to be a hardware problem but I don't know where to start.
View 3 Replies View RelatedSo my Dell latitude E6400 running fedora 12 (2.6.32.11-99.fc12.i686.PAE) is usually connected to a big screen (1920x1200).
Now each time I boot, X becomes unresponsive shortly before or after login for a couple of minutes, and then goes back to normal. This happens both with and without connection to the big screen.
The error messages associated to this seem to be like this, my /var/log/Xorg.0.log is cluttered with them :
Code:
I normally start my computer in the morning, walk off for some tea, and come back when X is functioning, but when I'm in a hurry it's pretty, or very, annoying ... drinking tea / coffee to wait for a computer to start is something people did in the 90s, it shouldn't be default behaviour in 2010 ...
I have a little problem here. I tried to copy include directory from g++ to a place where it suppose to be and when i couldn't because of the rights i wrote something like this in the bash:
Code:
Code:
cause i hate when I can't do what I want without tiping command
After few minutes all daemons crashed and now I can't boot normally
in console i've tried
Code:
And that stopped on /prc/756 directory
Well now i can boot normally but most of programs are not working, i can't get to the internet? and it looks like there is no way to become a root cause there is no sudo/
Can i reinstall ubuntu and keep all packages and files on its places?
I have installed a new Linux distro (just to test it) on my usb memory stick, and I'm trying to run it. I don't know if what I did is correct so far, anyways here's what I have:
Grub on sda (internal hard disk)
sdb with no boot loader (memory stick)
In grub I've been doing:
root (hd1,0)
kernel /kernel-genkernel-x86_64-2.6.37-sabayon root=/dev/sdb1 vga=normal
initrd /initramfs-genkernel-x86_64-2.6.37-sabayon
boot
This seems to work (as opposed to when I forgot the root= parameter, which almost destroyed my linux on sda1 ), but during startup the system complains about no root bein found on /dev/sdb1. I also tried (hd1,0), but it didn't change much.
I'm sure I can boot an OS from usb on my computer, so doesn anyone know what I'm doing wrong?