Re: how can I see booting messages
On 28.10.06 02:27, Jude DaShiell wrote: as root, dmesg | grep -i hdd | less should do it for you. note that dmesg buffer may be overridden after system run. check /var/log/dmesg which contains content of dmesg buffer as it was through the booting process. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. The early bird may get the worm, but the second mouse gets the cheese. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
re: how can I see booting messages
as root, dmesg | grep -i hdd | less should do it for you. dmesg doesn't store everything, I've had error messages speak that later were nowhere to be found after running dmesg but hdd information is preserved. If debian doesn't speak, I can't use it and you do need to have speech temporarily disabled during boot sequence or the system locks up, so using a trick like dmesg dmesg.log then less dmesg.log allows me to hear what dmesg.log preserves. It's like the syscap utility for dos and windows. Just put the syscap line as first line of config.sys and reboot the computer and later have a look at syscap.log in the root directory. If those two fail, a hardware solution would be a weasel card which temporarily replaces the monitor card and is hooked up to a printer or other computer. Everything that would go across the screen can be captured during boot up. I don't recommend weasel cards unless you have a spare $350.00 to spend though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: how can i see booting messages ??
Hello, Works fine for me now, but I was wondering... Is there a way to use normal terminal (the monitor, keyboard of the specific server) and also serial redirection at the same time ? When my server restarts, I can see everything on the monitor but also in my ZOC terminal session on my laptop, which is connected to the COM port on that server. It would be easy if you just connect your serial cable to a server and have instant access. The way it is configured now, I only get output on my zoc terminal session and not anymore on the server monitor as soon as grub starts booting. Grtz, Verus -Original Message- From: Miles Fidelman [mailto:[EMAIL PROTECTED] Sent: donderdag 26 oktober 2006 14:16 To: debian-user@lists.debian.org Subject: Re: how can i see booting messages ?? debian wrote: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? This question seems to get asked at least once a month. About the only thing you can do is use a terminal or terminal program with a good capture buffer. There are a whole bunch of startup messages that only go to the terminal and don't get logged anywhere. If you're setting up a server, you can set things up to use a serial terminal as your console, and then plug in a PC or laptop with a terminal emulator program that can capture all the traffic. If you're building on a desktop PC, it might be a bit harder. There are some references floating around for how to use a serial terminal as a console, maybe start with: http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-17.html http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/index.html I did this recently when building a couple of rackmount servers and it was pretty helpful to capture the traffic. Looking back at my (somewhat sketchy) notes, the basic steps involved: 1. connect both a regular terminal and a serial terminal Note: Depending on what you're using, this may be the most difficult part. In my case, I was using a PowerBook, and had to pull together the right combination of: - USB-to-RS232 adapter (it's not just a cable, there are some level changes going on so these beasts actually have a chip embedded in the cable) - RS232-to-RS232 adapter(s) for gender (male/female) and type (DCE/DTE) I can't remember what I did here anymore, I just keep the properly configured cable in my laptop case. - terminal program: these are surprisingly hard to come by these days - it's not that often one has to plug a dumb tty into a modem anymore - I ended up digging up a copy of Zterm (Mac) - configuring the terminal program (remember word length, parity, stop bits, port speed and such?) 2. finding the right BIOS settings to: - use the serial port (COM2 in my case) if a serial terminal is connected - my server also has an option to use both the serial port and the normal display 3. setting grub to use a serial terminal - somewhere in the grub config (or maybe it was typed to grub - as I said, sketchy notes serial --unit=0 --speed=9600 --word=8 --parity=no stop=1 terminal --timeout=10 serial console I believe these two commands first set up the serial port, then tell grub to use it for the terminal unless it times out in which case it uses the regular terminal. 4. telling grub to start the kernal using the serial console - in my case the boot command is: kernel kernel /vmlinuz-2.6.8-3-686 root=/dev/mapper/rootvolume-rootlv ro console=tty0 console=ttyS1,115200n8 5. going through the startup routine using only command line prompts Hopes this helps. Miles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Disclaimer : This e-mail is intended for the exclusive use by the person(s) mentioned as recipient(s). If you are not the intended recipient, please notify us immediately. This e-mail does not constitute any commitment for Sea-Ro Terminal N.V. or its subsidiaries except when expressly otherwise agreed in a written agreement between the intended recipient and the originating subsidiaries of Sea-Ro Terminal N.V. Sea-Ro Terminal and each of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. This mail has been checked for viruses by Symantec and Trend Micro.
Re: how can i see booting messages ??
It really depends on your specific hardware and BIOS. I can do it on my server, but your mileage may vary. For this one, you really do have to read the manual, and probably search online documentation as well. Miles ebian wrote: Hello, Works fine for me now, but I was wondering... Is there a way to use normal terminal (the monitor, keyboard of the specific server) and also serial redirection at the same time ? When my server restarts, I can see everything on the monitor but also in my ZOC terminal session on my laptop, which is connected to the COM port on that server. It would be easy if you just connect your serial cable to a server and have instant access. The way it is configured now, I only get output on my zoc terminal session and not anymore on the server monitor as soon as grub starts booting. Grtz, Verus -Original Message- From: Miles Fidelman [mailto:[EMAIL PROTECTED] Sent: donderdag 26 oktober 2006 14:16 To: debian-user@lists.debian.org Subject: Re: how can i see booting messages ?? debian wrote: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? This question seems to get asked at least once a month. About the only thing you can do is use a terminal or terminal program with a good capture buffer. There are a whole bunch of startup messages that only go to the terminal and don't get logged anywhere. If you're setting up a server, you can set things up to use a serial terminal as your console, and then plug in a PC or laptop with a terminal emulator program that can capture all the traffic. If you're building on a desktop PC, it might be a bit harder. There are some references floating around for how to use a serial terminal as a console, maybe start with: http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-17.html http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/index.html I did this recently when building a couple of rackmount servers and it was pretty helpful to capture the traffic. Looking back at my (somewhat sketchy) notes, the basic steps involved: 1. connect both a regular terminal and a serial terminal Note: Depending on what you're using, this may be the most difficult part. In my case, I was using a PowerBook, and had to pull together the right combination of: - USB-to-RS232 adapter (it's not just a cable, there are some level changes going on so these beasts actually have a chip embedded in the cable) - RS232-to-RS232 adapter(s) for gender (male/female) and type (DCE/DTE) I can't remember what I did here anymore, I just keep the properly configured cable in my laptop case. - terminal program: these are surprisingly hard to come by these days - it's not that often one has to plug a dumb tty into a modem anymore - I ended up digging up a copy of Zterm (Mac) - configuring the terminal program (remember word length, parity, stop bits, port speed and such?) 2. finding the right BIOS settings to: - use the serial port (COM2 in my case) if a serial terminal is connected - my server also has an option to use both the serial port and the normal display 3. setting grub to use a serial terminal - somewhere in the grub config (or maybe it was typed to grub - as I said, sketchy notes serial --unit=0 --speed=9600 --word=8 --parity=no stop=1 terminal --timeout=10 serial console I believe these two commands first set up the serial port, then tell grub to use it for the terminal unless it times out in which case it uses the regular terminal. 4. telling grub to start the kernal using the serial console - in my case the boot command is: kernel kernel /vmlinuz-2.6.8-3-686 root=/dev/mapper/rootvolume-rootlv ro console=tty0 console=ttyS1,115200n8 5. going through the startup routine using only command line prompts Hopes this helps. Miles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Disclaimer : This e-mail is intended for the exclusive use by the person(s) mentioned as recipient(s). If you are not the intended recipient, please notify us immediately. This e-mail does not constitute any commitment for Sea-Ro Terminal N.V. or its subsidiaries except when expressly otherwise agreed in a written agreement between the intended recipient and the originating subsidiaries of Sea-Ro Terminal N.V. Sea-Ro Terminal and each of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. This mail has been checked for viruses by Symantec and Trend Micro. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
On Fri, Oct 27, 2006 at 01:42:04PM +0200, debian wrote: Hello, Works fine for me now, but I was wondering... Is there a way to use normal terminal (the monitor, keyboard of the specific server) and also serial redirection at the same time ? When my server restarts, I can see everything on the monitor but also in my ZOC terminal session on my laptop, which is connected to the COM port on that server. It would be easy if you just connect your serial cable to a server and have instant access. The way it is configured now, I only get output on my zoc terminal session and not anymore on the server monitor as soon as grub starts booting. Grtz, Verus It depends. For example: Bios is usually one or the other (usually just the graphics card). Grub I think is one or the other, not both. The kernel can do both (or multiple console outputs), just tell it both in the console= line, see the serial-console howto. Unless I need the serial port for something else, I generally have the kernel send console messages to both, and have a getty run on ttyS0. If I don't need the serial console I can ignore it. When I do need it, it is already set up. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
[EMAIL PROTECTED] wrote: On Thu, Oct 26, 2006 at 06:18:38PM +0200, B_Kloss wrote: Am Donnerstag, 26. Oktober 2006 13:29 schrieb debian: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? Let's vary the question to one I sometimes have -- there's important information (i think) displayed just before I get the black screen of death, but I can't see it because it goes by too fast and CTRL-PageUP no longer works. Is there a way I can reboot (perhaps with a rescue disk) and see the messages so that i can see what they were? What is the last message you can see? Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how can i see booting messages ??
Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? Thnx, Verus. Disclaimer : This e-mail is intended for the exclusive use by the person(s) mentioned as recipient(s). If you are not the intended recipient, please notify us immediately. This e-mail does not constitute any commitment for Sea-Ro Terminal N.V. or its subsidiaries except when expressly otherwise agreed in a written agreement between the intended recipient and the originating subsidiaries of Sea-Ro Terminal N.V. Sea-Ro Terminal and each of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. This mail has been checked for viruses by Symantec and Trend Micro.
RE: how can i see booting messages ??
Title: RE: how can i see booting messages ?? use #dmesg debian #nano debian will show you the boot message Deepak Tripathi .---. Open Source Developer / \ [EMAIL PROTECTED]@./ /`\_/`\ .''`. // _ \\ : :' : | \ )|_ `. `'` /`\_` _/ \ `- \__/'---'\__/ Debian GNU/Linux -Original Message- From: debian [mailto:[EMAIL PROTECTED]] Sent: Thu 10/26/2006 4:59 PM To: debian-user@lists.debian.org Subject: how can i see booting messages ?? Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? Thnx, Verus. Disclaimer : This e-mail is intended for the exclusive use by the person(s) mentioned as recipient(s). If you are not the intended recipient, please notify us immediately. This e-mail does not constitute any commitment for Sea-Ro Terminal N.V. or its subsidiaries except when expressly otherwise agreed in a written agreement between the intended recipient and the originating subsidiaries of Sea-Ro Terminal N.V. Sea-Ro Terminal and each of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. This mail has been checked for viruses by Symantec and Trend Micro. The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. www.aztecsoft.com
Re: how can i see booting messages ??
debian wrote: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? The Scroll Lock button pauses the messages. /Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
debian wrote: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? This question seems to get asked at least once a month. About the only thing you can do is use a terminal or terminal program with a good capture buffer. There are a whole bunch of startup messages that only go to the terminal and don't get logged anywhere. If you're setting up a server, you can set things up to use a serial terminal as your console, and then plug in a PC or laptop with a terminal emulator program that can capture all the traffic. If you're building on a desktop PC, it might be a bit harder. There are some references floating around for how to use a serial terminal as a console, maybe start with: http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-17.html http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/index.html I did this recently when building a couple of rackmount servers and it was pretty helpful to capture the traffic. Looking back at my (somewhat sketchy) notes, the basic steps involved: 1. connect both a regular terminal and a serial terminal Note: Depending on what you're using, this may be the most difficult part. In my case, I was using a PowerBook, and had to pull together the right combination of: - USB-to-RS232 adapter (it's not just a cable, there are some level changes going on so these beasts actually have a chip embedded in the cable) - RS232-to-RS232 adapter(s) for gender (male/female) and type (DCE/DTE) I can't remember what I did here anymore, I just keep the properly configured cable in my laptop case. - terminal program: these are surprisingly hard to come by these days - it's not that often one has to plug a dumb tty into a modem anymore - I ended up digging up a copy of Zterm (Mac) - configuring the terminal program (remember word length, parity, stop bits, port speed and such?) 2. finding the right BIOS settings to: - use the serial port (COM2 in my case) if a serial terminal is connected - my server also has an option to use both the serial port and the normal display 3. setting grub to use a serial terminal - somewhere in the grub config (or maybe it was typed to grub - as I said, sketchy notes serial --unit=0 --speed=9600 --word=8 --parity=no stop=1 terminal --timeout=10 serial console I believe these two commands first set up the serial port, then tell grub to use it for the terminal unless it times out in which case it uses the regular terminal. 4. telling grub to start the kernal using the serial console - in my case the boot command is: kernel kernel /vmlinuz-2.6.8-3-686 root=/dev/mapper/rootvolume-rootlv ro console=tty0 console=ttyS1,115200n8 5. going through the startup routine using only command line prompts Hopes this helps. Miles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
Am Donnerstag, 26. Oktober 2006 13:29 schrieb debian: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? Thnx, Verus. Hi, in /var/log you can find various files with information about your system like dmesg messages and others Installing hwinfo with aptitude and hwinfo myhw.info creates a file with useful systeminformation. Best regards Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
On Thu, Oct 26, 2006 at 06:18:38PM +0200, B_Kloss wrote: Am Donnerstag, 26. Oktober 2006 13:29 schrieb debian: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? Let's vary the question to one I sometimes have -- there's important information (i think) displayed just before I get the black screen of death, but I can't see it because it goes by too fast and CTRL-PageUP no longer works. Is there a way I can reboot (perhaps with a rescue disk) and see the messages so that i can see what they were? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
On Thu, Oct 26, 2006 at 01:14:58PM -0400, [EMAIL PROTECTED] wrote: On Thu, Oct 26, 2006 at 06:18:38PM +0200, B_Kloss wrote: Am Donnerstag, 26. Oktober 2006 13:29 schrieb debian: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? Let's vary the question to one I sometimes have -- there's important information (i think) displayed just before I get the black screen of death, but I can't see it because it goes by too fast and CTRL-PageUP no longer works. Is there a way I can reboot (perhaps with a rescue disk) and see the messages so that i can see what they were? Not if the /var/log partition is not mounted at the time of the messages. Despite (or because of) it being old-tech, there is still a place for a serial console. Booting problems is one of them. Set things up so that console messages go to the regular screen AND the serial port. Hook up a terminal or a terminal-emulator on another computer and save the output. Or, hook up a printer with a serial interface. I don't know if its possible to get the kernel to put output to a parallel port; I don't know if your computer has a parallel port. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how can i see booting messages ??
On 10/26/2006 07:15 AM, Miles Fidelman wrote: debian wrote: Hello, I still have problems with my new installation. There is some important information (i think) displayed just after grub starts booting about the hdd, but i can't see what it is because it goes to fast and it is too far up to go with CTRL-PageUP. So, is there i way that i can pause or stop the messages so that i seen what it is ? This question seems to get asked at least once a month. About the only thing you can do is use a terminal or terminal program with a good capture buffer. There are a whole bunch of startup messages that only go to the terminal and don't get logged anywhere. Some of them can be logged by enabling boot logging: /etc/default/bootlogd If you're setting up a server, you can set things up to use a serial terminal as your console, and then plug in a PC or laptop with a terminal emulator program that can capture all the traffic. If you're building on a desktop PC, it might be a bit harder. There are some references floating around for how to use a serial terminal as a console, maybe start with: http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-17.html http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/index.html I did this recently when building a couple of rackmount servers and it was pretty helpful to capture the traffic. Looking back at my (somewhat sketchy) notes, the basic steps involved: 1. connect both a regular terminal and a serial terminal Note: Depending on what you're using, this may be the most difficult part. In my case, I was using a PowerBook, and had to pull together the right combination of: - USB-to-RS232 adapter (it's not just a cable, there are some level changes going on so these beasts actually have a chip embedded in the cable) - RS232-to-RS232 adapter(s) for gender (male/female) and type (DCE/DTE) I can't remember what I did here anymore, I just keep the properly configured cable in my laptop case. - terminal program: these are surprisingly hard to come by these days - it's not that often one has to plug a dumb tty into a modem anymore - I ended up digging up a copy of Zterm (Mac) - configuring the terminal program (remember word length, parity, stop bits, port speed and such?) 2. finding the right BIOS settings to: - use the serial port (COM2 in my case) if a serial terminal is connected - my server also has an option to use both the serial port and the normal display 3. setting grub to use a serial terminal - somewhere in the grub config (or maybe it was typed to grub - as I said, sketchy notes serial --unit=0 --speed=9600 --word=8 --parity=no stop=1 terminal --timeout=10 serial console I believe these two commands first set up the serial port, then tell grub to use it for the terminal unless it times out in which case it uses the regular terminal. 4. telling grub to start the kernal using the serial console - in my case the boot command is: kernel kernel /vmlinuz-2.6.8-3-686 root=/dev/mapper/rootvolume-rootlv ro console=tty0 console=ttyS1,115200n8 5. going through the startup routine using only command line prompts Hopes this helps. Miles Or you could prevent gdm from starting upon boot and press Shift-PageUp. Shift-PageUp won't work if gdm takes over, so gdm would have to be disabled for whatever runlevel you want to do this in. -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
