CentOS 5 :: How To Speed Up Boot Time / Disable Or Change Eth0 At Boot / Searching?
Jan 11, 2010
This on a Vostro 1220 Laptop w/ Intel 5300 wireless:
A.I have long boot up time.I think it's because of the eth0 network search which I don't use.I have an intel wireless 5300 card running.How can I speed up the boot time, i.e. disable or change the eth0 at boot, the searching?
B:When I restart or shutdown, the screen flashes repeatedly and gets some garbled colors along the top before finally rebooting looks like windows ME or something).This vostro has an intel x4500HD vid chipset in it.
C.How do I get into gnome configuration editor to turn on Metacity compositing? Alt-F2 and run gconf-editor doesn't do it. I don't do compiz, but need compositing.
D.I need to install Chromium Browser as it sync my bookmarks.I have RPMforge enabled btw also...how can I do that? I.e. rpm repo for chromium?
This will help me get off to a running start so I can get up to speed on CentOS..
I have set 'ONBOOT=no' in interface script '/etc/sysconfig/network-scripts/ifcfg-eth0:2' but my interface bring up at boot time, what is the problem , I have checked it 3 or 4 diff os/machine but the same issue. Can anyone please help me to disable virtual IP's at boot time that network script make it up every boot time.
During installation I set eth0 to use dhcp to get an IP address. I then installed gnome and networkmanger which handles my interfaces and works fine. But during bootup the system pauses for 5 seconds or so while it polls for dhcp. It then times out and gives me a 169.254.xx which is then replaced when networkmanager starts up at the end of bootup.
How do I stop the polling to cut out the 5 seconds?
Despite the fact that Ubuntu 9.10 boots up faster than its predecessors (I didn't time the boot up myself, so I can't say for sure), my Ubuntu laptop still takes around 50 seconds to boot up fully. Now I'm not happy with that, and I want it to boot up even faster.
Are there any easy special tricks to speed up the boot time?Coming from Linux Mint (GNOME), I could get to the Desktop from cold in less than 25 secs.Now in openSuse 11.3 (KDE4.5) it takes more than twice that.Is this a function of KDE or have Ubuntu done something that openSuse hasn't to speed up the boot?
I'm curious if there are any tools that can help speed up the time it takes for my computer to boot up. I've used different utilities to help my Vista boot up time, so I'm curious if the same sort of things are available for Ubuntu.
I am working on shortening my boot time on my laptop, so I am using bootchart to help me pinpoint the slow areas. So far, I got it down to about 40 seconds (from 2:33! -- dosfsck was running every boot). I don't use LVM (I am dual booting with Windows and it's hard enough with static partitions), and I have tried to disable LVM in every way I can imagine except uninstalling it (system-config-kickstart depends on it), but I still see it being initialized at boot time. How do I prevent the system from even considering LVM during boot??
My bootchart is here, and in case it is useful to anyone, my bootchart.tgz and boot.log..I'm running Fedora 14, and it's up to date.
I have just installed ssh-server in my Ubuntu 10.04, and really want to know how to enable/disable it and I also want to be sure if the changes will take effect after the next boot or not, and how to do that?
I am using Arch Linux and want to disable console messages which are displayed when the kernel boots. I have tried the quiet and loglevel=2 options in /boot/grub/menu.1st as given below:
These days I see the disk check that is popping up when my Ubuntu is booting up quite frequently. It says 'press C to cancel' but C (or Shift C or CTRL C or CTRL ALT C) does not have any effect. Pressing CTRL+ALT+DELETE reboots but again ends up in the vicious loop of disk check. How to bypass it? When I need to critically enter the desktop for an urgent pressing info waiting for 20 to 25 minutes disk check is kind of difficult.
i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.
I have just upgraded a CentOS 5.2 box to Centos 5.3
I did have a bridged networking setup for Virtualbox which worked well. eth0 was bridged with br0. br0 boot protocol was DHCP and it sent its DHCP_HOSTNAME to the windows DHCP servers.
since the upgrade the br0 does not get an address but the eth0 does. I found that the scripts in /etc/sysconfig/network-scripts/ifcfg-* are getting rewritten.
I figure I may not need to have a bridge any more so I stripped that out to try to get a simple network setup working. I now just have eth0. I edited /etc/sysconfig/network-scripts/ifcfg-eth0 so that it looked like this,
when I installed Ubuntu 9.10 I put in one time setting but it was wrong, and now I don't know where to change it. I tried to change the time preferences, but on reboot I am back to the wrong time.
I know the data is in there somewhere and I can change if I knew where it was.
How can I change the automatic fsck execution at boot time to be above 30 boots? I reboot the system sometimes 3 to 4 times a day. Intel 3 GHz, tower, i386 lenny vmlinuz-2.6.31-686
and it starts successfully and the CMS can use it. To start OO at boot time, I wrote a script called 'openofficeserver' and saved it to /etc/init.d. It looks as follows
I have a SSH box which is command line only and no X, this will be used remote and i'm trying to get the wireless network configured to start at boot. I'm using wpa_supplicant as the access point is secure with WPA2 At present if I send the following commands the machine will connect to the wifi and be reachable via ssh
This does not start at boot but requires manual input of the above commands. I've just come to a complete blank on geting this to start at boot time. Also I would like to set a fixed IP for this box.
I'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
I downloaded the 7 Cds .iso and I proceed to make a copy in a cds. I change the boot in my PC and restart the PC to read the cds. But the program instalation not running. What I need to do?
I've been a long time Windows user, but I've started a small firm and because of lack of funds, I've decided to install Ubuntu on my company's PCs.I have 8 PCs in total - 6 of them with Intel CPUs, and the last two with AMD CPUs. I bought the extra two computers because I've managed to find an extra two people to work at my company, and AMD-based PCs are cheaper so I've decided to buy them instead of Intel.Long-story short, I've installed Ubuntu 9.10 and boot time takes about half-an-hour. After the computers finally boot, USB hardware doesn't work at all. I was forced to buy PS/2 keyboards & mice and they both work fine after the PCs boot.I don't know what's causing this delay.I've enabled Cool 'n Quiet from BIOS.I've tried several instructions like editing the /etc/modules file.I've installed cpufreqd, tried to configure it, but it didn't work.I've check the CPU stats and my CPUs are running at 800MHz. I can't believe nobody managed to fix the 800MHz problem as I've noticed it's quite common among AMD Ubuntu users. I think I've tried almost anything that I've found on this forum.I can't keep asking my employees not to reboot their PCs. Both Chrome/Firefox crash a lot on Ubuntu so they're forced to restart their computers.The computer specs are: AMD Athlon II X2 240 dual-core @ 2.800MHz, 2GB RAM, 500GB HDD, etc.
I am having dual boot system(windows 7 and Fedora 12).When i switch on my system.It show the the timer 3 sec in order to get boot selection window(means window which asks that what to start fedora 12 or windows 7).I want to increase this time from 3 to 10 sec.
Splashtop caught my imagination of my own tv like computer-"1button and ready to go " have tried puppy xpudWebConverger still unhappy Now lucid aming for 10 sec boot-Keeping ma fingers crossed installed a minimal karmic and am getting a decent 27 sec I Jus Wanted to ask: Is there a way to remove the grub an directly boot into ubuntu -not just hiding it by editing grub.d files and any other ways to reduce boot time.......
I've got two laptops running Ubuntu. Both have had Lucid installed from the live cd. I have upgraded one of them to Maverick. Both distributions are running great after they boot up, but I haven't experienced any faster boot times with either distibution. Both boot to Bios and then the screen goes black with a blinking cursor in upper left corner of the screen. The black screen remains for 30 to 45 seconds and then I get the Ubuntu splash screen for maybe 5 seconds, and then desktop. Why am I not seeing faster boot times? I realize 45 to 60 seconds is good compared to other os's, but I anticipated much faster boot times. Shut down on the other hand is quite fast at maybe 5 to 10 seconds. Does anyone else get this black screen on boot? Seems like wasted time cause I can't tell what's going on during the time there is a black screen. This is not a real big deal breaker, as I don't reboot very often, but I just wonder why bootup isn't faster.
i was attempting to "speed up boot time" by using the "dash" shell instead of "bash"there is a post on here which describes this.i installed the scripts and uhhhh....rebootednow it seems that i kinda sorta forgot to install "dash" before reboot and now ihave no system shell.no root user accessonly my regular user works, kinda...it seems that i cannot edit anything eitherit won't do any temp dataso with mc i cannot save any edited files.....prompt looks like thismichael@(none):i am hoping i just need to install dash....but with limited power at the command prompt this may be interesting.
