Fedora :: Slow Down Boot Messages?
Aug 3, 2011I'm getting a boot message that goes by too quickly to read. Is there a way to slow them down?
View 11 RepliesI'm getting a boot message that goes by too quickly to read. Is there a way to slow them down?
View 11 RepliesDuring boot-up and shutdown of Fedora-14-x86_64-Live-Desktop.iso live USB, I just see some graphical stuff. What needs to be done so that the screen shows text messages about what's happening during boot-up and shutdown?
View 2 Replies View RelatedWhat /where is the file, that shows boot up messages.
View 2 Replies View RelatedWhen i logged into my desktop, i got a notification that said there was boot messages. I remember trying to find this before in /var/log, so that i could investigate why i couldn't get the nvidia drivers to work (which i now know is because i'm using 14-beta, which has a debugging kernel), but couldn't find it.
Code:
Welcome to Fedora
Starting udev: [ OK ]
[code]....
I have a number of applications (Evolution, Openoffice Writer & Calc, Firefox) that are popping up an error message when I close them, but the window snaps closed before I can read the message. The applications run fine as far as I can tell. how to slow or pause the error message so I can figure out what's going on.
View 9 Replies View RelatedEvery time I log in, I get a "Boot Messages" indicator in my notification area. I click it and it shows me what happened during boot (uneventful, no error messages). I would like to remove this icon, it's very annoying. I can right click it and click quit but I don't like doing this every time I log in.
Is there an easy way to stop it from starting up (I couldn't find it in Startup Applications)?
I've a headless custom device that boots from USB using live image. Since I cannot access the device through the network, I need a way to persist boot related log files (dmesg, boot.log, messages) to view them on another computer. I also need to know how can I run custom commands on startup of live image.
View 3 Replies View RelatedI've a headless custom device that boots from USB using live image. Since I cannot access the device through the network, I need a way to persist boot related log files (dmesg, boot.log, messages) to view them on another computer. I also need to know how can I run custom commands on startup of live image.
View 3 Replies View RelatedG'day. My distro is Fedora 13. I received the above subject error message at boot. My /etc/fstab is attached as follow:
#
# /etc/fstab
# Created by anaconda on Fri Mar 5 12:44:10 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
[code].....
when boot is done and switched to X11 I get major time delays due to graphic init (as far as I can tell).
Here is the relevant part from Xorg.0.log:
Code:
63.420] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 63.420] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[Code].....
I installed kernel 2.6.32.9-67 via a yum update this morning. When I rebooted, the machine appeared to freeze with a single blinking underscore cursor. I used a live CD to edit grub.conf and reboot into the old kernel, which started normally. Later, I tried booting into the new kernel via grub again. After about two minutes, the blinking cursor is replaced by the normal boot screens and the machine works fine. This is on a seven year old PC with AMD Althon XP 2000+, 768MB RAM, VIA KT400 chipset and the NVIDIA 173xx driver from RPM Fusion.
View 6 Replies View RelatedSince the yesterdays updates the boot process lasts terribly long of my Fedora 12 on a x86_64 system. It lasts about 10 minutes or longer. The strangest thing is that if I press keys (any of them) it goes faster (about 1 minute). There are no errors or other things which might be the reason for such a behaver.
View 7 Replies View RelatedAnybody 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
After I upgrade fedora from 14 to 15 on thinkpad T510, it takes a long long time to boot up@~~~ .I look at the boot up prompt, it just stuck at the network service part.... for about 4 minutes!!!I followed thread url.
After I did
# echo "options iwlagn 11n_disable=1" >/etc/modprobe.d/Intel-80211n.conf
# reboot
I am able to use my wireless now, but when fedora15 is boot up, it does not auto connect for me, I need to connect the wireless myself.
Here is what I find. During bootup, it stuck at Network service part for around
[fanw@f14 ~]$ systemctl list-units --failed
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
network.service loaded failed failed LSB: Bring up/down networking
sssd.service loaded failed failed System Security Services Daem
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
code....
Everytime I boot, I get a "Boot messages" applet in the top panel. The only error message is:*"Starting NFS statd: [FAILED]"
But in System => Administration => Services, NFS*is disabled and stopped. Of course, I don't use NFS*in any way.
I'm using Fedora 12 since 2 years lately, I really enjoy this S.O., it's quite robust and wonderful, but a couple of months ago it is really slow to boot up when startup the computer, I've checked everything, but seems to be ok, I had a partition lost arround that date, but recover successfully, it happens when I run gparted that It cannot see partition on my 500 GB disk, but still boots up. When running Mandriva live cd, it can see (?) all partitions on that disk, even with Fedora Dolphin I can access this partitions. What could it be?
View 6 Replies View RelatedI installed fedora15 on my laptop. and after an upgrade, with the kernel 2.6.40-4.fc15.x86_64, my fedora boot is taking almost 10 minuts.....Its take so manytimes to boot. does someone knows why?I installed jdk, eclipse, glassfish, firebird and postgres for my workspace.....
---------- Post added at 11:16 AM ---------- Previous post was at 10:55 AM ----------
ok I I figured out why the long time to boot.I have here installed glassfish and I add a Line on /etc/hosts like that:
Code:
[vinny@vinny-fedora ~]$ cat /etc/hosts
127.0.0.1localhost.localdomain localhost
#127.0.0.2 vinny-fedora
::1localhost6.localdomain6 localhost6
127.0.0.1 vinny-fedora
If I comment the last line, the starting is normal. But without this line I cant start up Glassfish. is there another way to sat my hostname?
After a new Fedora 12 installation, i cannot automount my Windows partition. My system is setup originally at windows XP ,partitioned, then change to Fedora 10. Change to Fedora 11 through update.System very slow.
I decided to upgrade to fedora 12 by DVD installer, then i have to mount manually to access my back-up, when typing su -c '/sbin/fdisk -l' at terminal, this is the code:
I'm running a dual partitioned (Vista / Fedora 11 x86_64) Intel X25-M Mainstream SSD.
Whilst Vista boots in about 15 seconds, Fedora takes around twice as long; in fact far longer than Fedora 9 on my old Western Digital Raptor drive.
Is this to be expected, or might I have some sort of configuration problem? Has anyone else had similar experiences?
I've enabled BOOTLOGD_ENABLE=Yes in /etc/default/bootlogd on my Squeeze (Upgrade from Lenny) installed on the notebook, but after Retsrat NO bootlog messages in /var/log/boot. Is it a BUG?
View 2 Replies View RelatedEDIT: not fully solved; there is (at time of writing) still an issue about bootlogd buffering until the logfile is accessible but that's probably as far as we are going to get for now, until someone peeks into the bootlogd source code.
Is it possible to review boot messages after boot? Kernel messages are available via dmesg (and many are logged early in the rc.M script by the /bin/dmesg -s 65536 > /var/log/dmesg) but many console boot messages are not kernel messages. During boot, messages can be viewed using Shift+PgUp but when the rc.S script finishes, init starts an agetty on tty1 which prints a login prompt. Then tty1 is no longer the console and Shift+PgUp cannot be used to scroll back through the boot messages. Any delayed boot messages do not have effective carriage returns so "marquee" across the screen, one following another, a line below.
Is it possible to leave tty1 as the console by de-configuring the tty1/agetty line in inittab, thus allowing Shift+PgUp to be used to scroll back through older messages and allowing proper horizontal alignment for delayed boot messages? I would try it but the inittab line x1:4:respawn:/etc/rc.d/rc.4 runs /usr/X11R6/bin/xdm and this grabs the first unused tty<n>. The xdm man page and xdm config file comments do not reveal whether it is possible to make xdm use a specific tty<n>.
Another solution may be something like the sysvinit binary that intercepts all console writes and then dumps them to log at the end of the boot process but if it were that easy or useful it would already be done and publicised (wouldn't it?).
I'm running slack64 13.0. At initial boot i see the two penguins and text from th kernel scrolls past until my root partition is mounted where upon all messages stop until the console prompt or KDM pops up. Everything seems to be operating as normal but i've no idea whats happening during the rc scripts (FS checking, etc). When shutting down though the rc.6/rc.0 script messages appear in the console though.
To my knowledge i've not changed anything that would effect this (just modified inittab for runlevel 4 & tty4,5,6 in runlevel 4).
There's nothing in dmesg but most messages don't get logged there as i understand.
I have a syslog-ng running and kernel build of 2.6.34.8 I use a syslog API in my program with facility LOG_LOCAL5 and and levels debug err and crit and info. when I ran on the older syslog facility I had everything logged fine as I intended. now I have written these rules into the syslog-ng.conf:
options {
flush_lines (0);
time_reopen (10);
log_fifo_size (1000);
[code]....
the last two rules show my program gnssapp. the result is all debug levels or crit or err levels I don't see any of them !
An issue that has been hassling me for years since I started using Linux (Debian!) is related to the boot messages that quickly scroll on the video during the boot process. The main hassle is related to the fact that I cannot get a log of those messages. The second hassle is due to the fact that with my brand new netbook (Toshiba NB200) I cannot even stop the scroll and go back along the message stream with SHIFT+PageUpDown to understand what's going on. Of course I know that I can get a log of the boot process with 'dmesg' but I get the feeling that the very first lines show some problem I cannot grab at all.
View 2 Replies View RelatedMy memory could be failing but I thought there was a tool, possibly in Yast, to access the boot logs in earlier versions. Can't find it now though. Is there such a tool other than console?I should clarify in case I am using the wrong terminology that I seek the log which scrolls up the screen during the booting process. Reason is that I see several errors and warnings there and wish to investigate further.
View 9 Replies View RelatedI just upgraded to 10.04 through the Update Manager. During the updated however I got an error telling me that it was unable to install something. Sorry, I can't remember what it was; it didn't stop the updated so I assumed it wasn't that important. Anyways, I don't know if this is because of that error, but during the boot process and when shutting the computer I get console messages. When I boot it tells me that "mounting none on /dev failed No such device" and when I shut down I get these messages.I see this was asked before and that it isn't a big issue, but I'd still like to solve it. The problem is that I'm pretty new to Ubuntu and Linux in general I don't know how to follow the very general instructions given in that thread.
View 2 Replies View RelatedI have Ubuntu 9.10. The batter drained several days ago, and now when I attempt to boot I simply get a string of indecipherable error messages which last for about 5 minutes, and the screen then goes completely black. I am not able to even get to the login screen. Windows 7 Starter boots fine, so it's definitely a software issue. Any solutions short of completely reinstalling? I really don't want to lose all of my data.
View 2 Replies View RelatedThis is what my computer looks like while it's booting. Gdm pops up shortly, and I can use my computer with no problems. More recently, I screwed up something in gdm, so I can't do anything with my ubuntu computer.
View 3 Replies View Relatedi bought a new DVD-RW:url
(sorry, i couldn't find english results for it)
Code:
$ dmesg | tail
[ 246.543039] hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
[ 246.543047] hda: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
[ 246.543052] hda: possibly failed opcode: 0xa0
code....
besides those error messages it seems to work.if there is an iso-cd in the drive i get similar messages during boot and need to hit ctrl+c to go on with booting.
a search gave me this: url
I looked in /var/log/messages and also tried dmesg both seem to contain something different than what I saw while booting up. But I am looking for the ones displayed while booting, where it says whether the particular step was ok and if failed it prints few things. I would like to know where I can find those messages.
View 6 Replies View Related