During 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 RepliesWhen I shut down fedora 14, no messages are displayed. I commented out "rhgb quiet" to display the startup messages. How do I configure Fedora 14 to display the shutdown messages when shutting down?
View 4 Replies View RelatedWhen my computer shuts down, I always get a long error message from the kernel. It's the very last thing the computer does and I can't even use the keyboard, since the system is halted. I wanted to read it more carefully (it's very long and doesn't fit the screen) and file a bug report against the kernel with it. But for that, I needed to save all that text in a file.
View 1 Replies View RelatedI had Fedora 15 installed on my laptop and I have a problem which had bothered me for a long time. Every time I turn on my laptop, I would get a messages which says "Thermal Shutdown Occurred". I tried other Linux distributions but the same problem. It operates normally with Windows 7.
View 7 Replies View RelatedDuring the boot-sequence of jessie there is more text flying by on the screen (including some errors or warnings) than I can read thorugh fast enough. I don't think this is very serious stuff, and if it were I could always look at dmesg and or syslog i /var/log but I would find it really convenient to log these messages in a file instead of sifting through or grep-ing dmesg.
When duckduckgoing this matter I found [URL] ....
I installed tried bootlogd but when configuring it to "yes" and rebooting nothing comes up in /var/log/boot.
Then I saw this line in above link
If you use systemd as your init system, you may need to use systemctl to debug boot problems.
I have Lucid installed on two PCs. The PCs are identical except one uses the on-board Intel G33 video controller while the other has an nvidia 210 video card attached. The nvidia PC restarts/shuts down without showing any console text messages, however the Intel based PC has the following problem. The software on both machines is identical (except for the nvidia packages).
On restart or shutdown on the intel based PC plymouth gives way to a console for 2 or 3 seconds showing the following (none of which are errors as far as i know)...
Code:
Broadcast Message from root@xyz-desktop
(unknown) at 11:44 ...
The System is going down for restart NOW!
* Deactivating Swap ...
* Unmounting weak filesystems ...
[Code]....
how to record/save logout/shutdown messages for OpenSuse 11.2.
View 9 Replies View RelatedWhat /where is the file, that shows boot up messages.
View 2 Replies View RelatedI'm getting a boot message that goes by too quickly to read. Is there a way to slow them down?
View 11 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]....
Every 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 Relatedeverytime I try to shutdown/reboot, it gets to the screen where it has the green/bold status messages on the side, but then it simply stops. The cursor doesn't blink, nothing happens...you could wait 10 minutes, and it would still be at that same screen. I don't know if I've described this well enough for anyone to understand, but I hope so! I don't have a camera, but if I did...I'd post a picture of where I mean...
But like I said, after getting to a certain, without actually shutting down, it simply stops and does absolutely nothing. This is rather inconvenient, and I'd like to find a solution to this if possible. EDIT: I'm sorry I didn't provide any hardware info, but I'm using Gnome...This didn't happen 100% of the time KDE like it does now though. (But it DID happen in KDE as well) I'm using OpenSUSE 11.2... I'll be back in a moment with hardware info, assuming it may aid in a solution.
[Code]...
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
View 4 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].....
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
[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'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 RelatedI'm trying to stop all boot time messages from appearing -- basically I'd like to have a simple blank screen from grub to xdm.
I tried everything -- used the "quiet" option in grub's config, added dmesg -n 1 to rc.local, changed console=ttySx, set kernel.printk in sysctl.conf to 4 1 1 7, and even eradicated rsyslogd altogether... to no avail. I still see all sorts of messages on my screen.