SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all.
I think this is a pretty stupid question, but... it is my problem.
I cannot retrieve messages that my Slackware 12 shows to me during boot. When it boot I can see some messages with the prefix FATAL, but, once booted, I cannot retrieve again these messages. I tryed with dmesg, but I don't see all messages.
Any suggest?
Thanks in advance.
You should see all the messages by issuing "dmesg", from the beginning of the boot process. The first line should print out your kernel version, such as:
Code:
mingdao@wired_silas:~$ dmesg
Linux version 2.6.21.5-smp (root@midas) (gcc version 4.1.2) #2 SMP Tue Jun 19 14:58:11 CDT 2007
unless your system has been up so long that other kernel messages have pushed your buffer too large. Issue and read "man dmesg".
Is your problem that you can't scroll back in the terminal where you're trying to read the messages? Or can you scroll back to where you issued "dmesg" and they do not start with that line which states your kernel version?
I have three computers in this LAN atm running Slackware-12.0. No problem on any of them outputting all of dmesg. What do you get when you issue "dmesg | less":
Code:
mingdao@wired_silas:~$ dmesg | less
Linux version 2.6.21.5-smp (root@midas) (gcc version 4.1.2) #2 SMP Tue Jun 19 14:58:11 CDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000e4000 size: 000000000001c000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000007fe30000 end: 000000007ff30000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000007ff30000 size: 0000000000010000 end: 000000007ff40000 type: 3
copy_e820_map() start: 000000007ff40000 size: 00000000000b0000 end: 000000007fff0000 type: 4
copy_e820_map() start: 000000007fff0000 size: 0000000000010000 end: 0000000080000000 type: 2
copy_e820_map() start: 00000000fff80000 size: 0000000000080000 end: 0000000100000000 type: 2
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007ff30000 (usable)
BIOS-e820: 000000007ff30000 - 000000007ff40000 (ACPI data)
BIOS-e820: 000000007ff40000 - 000000007fff0000 (ACPI NVS)
BIOS-e820: 000000007fff0000 - 0000000080000000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
1151MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000ff780
Entering add_active_range(0, 0, 524080) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 524080
early_node_map[1] active PFN ranges
0: 0 -> 524080
On node 0 totalpages: 524080
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 2302 pages used for memmap
HighMem zone: 292402 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP 000FAAC0, 0021 (r2 ACPIAM)
ACPI: XSDT 7FF30100, 003C (r1 A M I OEMXSDT 10000409 MSFT 97)
ACPI: FACP 7FF30290, 00F4 (r3 A M I OEMFACP 10000409 MSFT 97)
ACPI: DSDT 7FF303E0, 362A (r1 A0091 A0091006 6 MSFT 100000D)
ACPI: FACS 7FF40000, 0040
ACPI: APIC 7FF30390, 004A (r1 A M I OEMAPIC 10000409 MSFT 97)
ACPI: OEMB 7FF40040, 003F (r1 A M I OEMBIOS 10000409 MSFT 97)
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
val3xiv,
I sympathize with your problem. I am sure that you are correct that not all messages seen at boot are stored in dmesg.
I had a similar issue some while back, and never really got to the bottom of it.
I think the answer lies somewhere in the fact that dmesg reports kernel messages. Your FATAL messages are (I think) coming from userspace.
Usually a problem will show up in one of the log files in /var/log, especially syslog or messages (see /etc/syslog.conf to see how these messages get divided according to severity).
The trouble is that the boot messages go past so fast that you can't easily read it. You may be able to slow it down by using a high resolution framebuffer mode eg 791.
The FATAL may not be as serious as it sounds. It could just be a module unable to load because you compiled it into the kernel.
val3xiv,
I sympathize with your problem. I am sure that you are correct that not all messages seen at boot are stored in dmesg.
I had a similar issue some while back, and never really got to the bottom of it.
I think the answer lies somewhere in the fact that dmesg reports kernel messages. Your FATAL messages are (I think) coming from userspace.
Usually a problem will show up in one of the log files in /var/log, especially syslog or messages (see /etc/syslog.conf to see how these messages get divided according to severity).
The trouble is that the boot messages go past so fast that you can't easily read it. You may be able to slow it down by using a high resolution framebuffer mode eg 791.
The FATAL may not be as serious as it sounds. It could just be a module unable to load because you compiled it into the kernel.
tobyl
Ty tobyl. You focused perfectly my problem.
I know that with SHIFT PGUP I can read all my boot messages as soon as my boot process is ended, but my question is another: how can I retreive all my boot messages later and, for example, store them in a text file?
Still haven't found a solution.
Other ideas?
Thanks again
how can I retreive all my boot messages later and, for example, store them in a text file?
If you don't mind modifying your boot scripts, you can use the logger command to force commands to log their output. For example, in /etc/rc.d/rc.inet1 if /usr/bin/logger is executable (and syslogd is running), commands are logged to syslog. If /usr/bin/logger is not executable, commands output to stdout/stderr.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
