Vamos ver algumas coisas do dmesg:
giovani@Saga:~$ dmesg
[ 25.856216] ADDRCONF(NETDEV_UP): eth0: link is not ready[ 25.866975] init: apport pre-start process (1232) terminated with status 1
[ 25.882476] init: apport post-stop process (1290) terminated with status 1
[ 25.884185] init: gdm main process (1288) killed by TERM signal
[ 28.499021] vboxdrv: Found 4 processor cores.
[ 28.499390] vboxdrv: fAsync=0 offMin=0x19a offMax=0xbf7
[ 28.499444] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 28.499446] vboxdrv: Successfully loaded version 4.1.2 (interface 0x00190000).
[ 28.711240] vboxpci: IOMMU not found (not registered)
[ 28.737362] Bluetooth: RFCOMM TTY layer initialized
[ 28.737368] Bluetooth: RFCOMM socket layer initialized
[ 28.737369] Bluetooth: RFCOMM ver 1.11
[ 28.739688] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 28.739691] Bluetooth: BNEP filters: protocol multicast
[ 30.332937] acer_wmi: Acer Laptop WMI Extras unloaded
[ 30.347177] init: plymouth-stop pre-start process (1735) terminated with status 1
[ 30.374140] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 33.572289] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,commit=0
[ 34.205389] EXT4-fs (sda7): re-mounted. Opts: commit=0
[ 42.516406] wlan0: authenticate with 00:26:5a:60:63:10 (try 1)
[ 42.518439] wlan0: authenticated
[ 42.546806] wlan0: associate with 00:26:5a:60:63:10 (try 1)
[ 42.550680] wlan0: RX AssocResp from 00:26:5a:60:63:10 (capab=0x431 status=0 aid=1)
[ 42.550687] wlan0: associated
[ 42.558016] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 53.157416] wlan0: no IPv6 routers present
[ 89.539404] show_signal_msg: 18 callbacks suppressed
[ 89.539408] chrome[2309]: segfault at 18 ip 00007f4edc995a31 sp 00007fff562fab30 error 4 in chrome[7f4edbd99000+3a4c000]
Vamos pesquisar se foi carregado o dispositivo de Bluetooh na inicialização, digite:
giovani@Saga:~$ dmesg |grep Blu
[ 16.296483] Bluetooth: Core ver 2.16
[ 16.296508] Bluetooth: HCI device and connection manager initialized
[ 16.296510] Bluetooth: HCI socket layer initialized
[ 16.296511] Bluetooth: L2CAP socket layer initialized
[ 16.296722] Bluetooth: SCO socket layer initialized
[ 16.297026] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 28.737362] Bluetooth: RFCOMM TTY layer initialized
[ 28.737368] Bluetooth: RFCOMM socket layer initialized
[ 28.737369] Bluetooth: RFCOMM ver 1.11
[ 28.739688] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 28.739691] Bluetooth: BNEP filters: protocol multicast
Vamos localizar as informações dos dispositivos de armazenamento (Disco rígido e CD-Rom), digite:
giovani@Saga:~$ dmesg |grep ata
[ 0.000000] BIOS-e820: 00000000bf7bf000 - 00000000bf7ff000 (ACPI data)
[ 0.000000] Memory: 4024476k/5234688k available (6105k kernel code, 1059020k absent, 151192k reserved, 4879k data, 984k init)
[ 0.665390] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
[ 0.665813] _OSC request data:1 8 1f
[ 0.672194] _OSC request data:1 1f 1f
[ 0.672227] _OSC request data:1 0 1d
[ 0.675112] libata version 3.00 loaded.
[ 1.023178] Write protecting the kernel read-only data: 10240k
[ 1.093067] ata1: SATA max UDMA/133 abar m2048@0xd5307000 port 0xd5307100 irq 41
[ 1.093068] ata2: DUMMY
[ 1.093069] ata3: DUMMY
[ 1.093070] ata4: DUMMY
[ 1.093073] ata5: SATA max UDMA/133 abar m2048@0xd5307000 port 0xd5307300 irq 41
[ 1.093074] ata6: DUMMY
[ 1.412042] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.412093] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.414813] ata5.00: ATAPI: PIONEER BD-ROM BDC-TD03, 1.10, max UDMA/100
[ 1.417785] ata5.00: configured for UDMA/100
[ 1.422064] ata1.00: ATA-8: SAMSUNG HM500JI, 2AC101V4, max UDMA/133
[ 1.422074] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.432176] ata1.00: configured for UDMA/133
[ 2.266334] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 25.459434] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
Para mais informações sobre o dmesg:
giovani@Saga:~$ man dmesg
DMESG(1)
NAME
dmesg - print or control the kernel ring buffer
SYNOPSIS
dmesg [-c] [-r] [-n level] [-s bufsize]
DESCRIPTION
dmesg is used to examine or control the kernel ring buffer.
The program helps users to print out their bootup messages. Instead of copying the messages by hand, the user need only:
dmesg > boot.messages
and mail the boot.messages file to whoever can debug their problem.
OPTIONS
-c Clear the ring buffer contents after printing.
-r Print the raw message buffer, i.e., don't strip the log level prefixes.
-s bufsize
Use a buffer of size bufsize to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default then this option can be used to view the entire buffer.
-n level
Set the level at which logging of messages is done to the console. For example, -n 1 prevents all messages, except panic messages, from appearing on the console.
All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer.
When both options are used, only the last option on the command line will have an effect.
Nenhum comentário:
Postar um comentário