BIOS may be corrupt message

I copied the part of the kernel log here.I do not have any problems,I boot into Ubuntu nearly in 25 seconds.But the BIOS may be corrupt message makes me worried.I searched a lot on google,but I do not understand the logs.

Code:

May 21 11:09:58 ceylan-desktop kernel: imklog 4.2.0, log source = /proc/kmsg started.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Initializing cgroup subsys cpuset
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Initializing cgroup subsys cpu
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Linux version 2.6.32-22-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 (Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] KERNEL supported cpus:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Intel GenuineIntel
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   AMD AuthenticAMD
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   NSC Geode by NSC
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Cyrix CyrixInstead
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Centaur CentaurHauls
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Transmeta GenuineTMx86
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Transmeta TransmetaCPU
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   UMC UMC UMC UMC
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] BIOS-provided physical RAM map:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 0000000000100000 - 000000007f7a0000 (usable)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 000000007f7a0000 - 000000007f7ae000 (ACPI data)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 000000007f7ae000 - 000000007f7e0000 (ACPI NVS)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 000000007f7e0000 - 000000007f800000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] DMI 2.4 present.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] last_pfn = 0x7f7a0 max_arch_pfn = 0x100000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] MTRR default type: uncachable
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] MTRR fixed ranges enabled:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   00000-9FFFF write-back
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   A0000-DFFFF uncachable
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   E0000-EFFFF write-through
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   F0000-FFFFF write-protect
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] MTRR variable ranges enabled:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   0 base 000000000 mask F80000000 write-back
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   1 base 07F800000 mask FFF800000 uncachable
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   2 disabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   3 disabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   4 disabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   5 disabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   6 disabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   7 disabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Scanning 0 areas for low memory corruption
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] modified physical RAM map:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 0000000000010000 - 000000000009fc00 (usable)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 000000000009fc00 - 00000000000a0000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 00000000000e4000 - 0000000000100000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 0000000000100000 - 000000007f7a0000 (usable)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 000000007f7a0000 - 000000007f7ae000 (ACPI data)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 000000007f7ae000 - 000000007f7e0000 (ACPI NVS)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 000000007f7e0000 - 000000007f800000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 00000000fee00000 - 00000000fee01000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  modified: 00000000fff80000 - 0000000100000000 (reserved)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] initial memory mapped : 0 - 00c00000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] init_memory_mapping: 0000000000000000-00000000377fe000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Using x86 segment limits to approximate NX protection
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  0000000000 - 0000400000 page 4k
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  0000400000 - 0037400000 page 2M
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]  0037400000 - 00377fe000 page 4k
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] kernel direct mapping tables up to 377fe000 @ 10000-15000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] RAMDISK: 37856000 - 37fef072
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Allocated new RAMDISK: 008de000 - 01077072
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Move RAMDISK from 0000000037856000 - 0000000037fef071 to 008de000 - 01077071
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: RSDP 000fb030 00014 (v00 ACPIAM)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: RSDT 7f7a0000 00038 (v01 A_M_I_ OEMRSDT  04000815 MSFT 00000097)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: FACP 7f7a0200 00084 (v02 A_M_I_ OEMFACP  04000815 MSFT 00000097)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: DSDT 7f7a05c0 06909 (v01  A0798 A0798000 00000000 INTL 20051117)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: FACS 7f7ae000 00040
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: APIC 7f7a0390 0006C (v01 A_M_I_ OEMAPIC  04000815 MSFT 00000097)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: MCFG 7f7a0400 0003C (v01 A_M_I_ OEMMCFG  04000815 MSFT 00000097)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: OEMB 7f7ae040 00080 (v01 A_M_I_ AMI_OEM  04000815 MSFT 00000097)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: HPET 7f7a6ed0 00038 (v01 A_M_I_ OEMHPET  04000815 MSFT 00000097)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] 1151MB HIGHMEM available.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] 887MB LOWMEM available.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   mapped low ram: 0 - 377fe000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   low ram: 0 - 377fe000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   node 0 low ram: 00000000 - 377fe000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   node 0 bootmap 00011000 - 00017f00
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #1 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #2 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #3 [0000100000 - 00008d9e98]    TEXT DATA BSS ==> [0000100000 - 00008d9e98]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #4 [000009fc00 - 0000100000]    BIOS reserved ==> [000009fc00 - 0000100000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #5 [00008da000 - 00008dd210]              BRK ==> [00008da000 - 00008dd210]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #6 [0000010000 - 0000011000]          PGTABLE ==> [0000010000 - 0000011000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #7 [00008de000 - 0001077072]      NEW RAMDISK ==> [00008de000 - 0001077072]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   #8 [0000011000 - 0000018000]          BOOTMAP ==> [0000011000 - 0000018000]
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] found SMP MP-table at [c00ff780] ff780
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Zone PFN ranges:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   DMA      0x00000010 -> 0x00001000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Normal   0x00001000 -> 0x000377fe
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   HighMem  0x000377fe -> 0x0007f7a0
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Movable zone start PFN for each node
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] early_node_map[2] active PFN ranges
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]     0: 0x00000010 -> 0x0000009f
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]     0: 0x00000100 -> 0x0007f7a0
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] On node 0 totalpages: 522031
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] free_area_init_node: node 0, pgdat c0798720, node_mem_map c1079200
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   DMA zone: 32 pages used for memmap
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   DMA zone: 0 pages reserved
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   DMA zone: 3951 pages, LIFO batch:0
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Normal zone: 1744 pages used for memmap
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   Normal zone: 221486 pages, LIFO batch:31
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   HighMem zone: 2304 pages used for memmap
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]   HighMem zone: 292514 pages, LIFO batch:31
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Using APIC driver default
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x808
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: IRQ0 used by override.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: IRQ2 used by override.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: IRQ9 used by override.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] SMP: Allowing 4 CPUs, 2 hotplug CPUs
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] nr_irqs_gsi: 24
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e4000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Allocating PCI resources starting at 7f800000 (gap: 7f800000:7f600000)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] PERCPU: Embedded 14 pages/cpu @c2400000 s36024 r0 d21320 u1048576
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] pcpu-alloc: s36024 r0 d21320 u1048576 alloc=1*4194304
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] pcpu-alloc: [0] 0 1 2 3 
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 517951
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=49441cd5-35e9-47fb-8934-64809ec75ece ro quiet splash
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Enabling fast FPU save and restore... done.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Enabling unmasked SIMD FPU exception support... done.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Initializing CPU#0
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] allocated 10442560 bytes of page_cgroup
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Initializing HighMem for node 0 (000377fe:0007f7a0)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Memory: 2043556k/2088576k available (4673k kernel code, 43444k reserved, 2121k data, 656k init, 1179272k highmem)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] virtual kernel memory layout:
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]     fixmap  : 0xfff1d000 - 0xfffff000   ( 904 kB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]     vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]       .init : 0xc07a3000 - 0xc0847000   ( 656 kB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]       .data : 0xc0590653 - 0xc07a2e48   (2121 kB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000]       .text : 0xc0100000 - 0xc0590653   (4673 kB)
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Hierarchical RCU implementation.
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] NR_IRQS:2304 nr_irqs:440
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Console: colour VGA+ 80x25
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] console [tty0] enabled
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] hpet clockevent registered
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Fast TSC calibration using PIT
May 21 11:09:58 ceylan-desktop kernel: [    0.000000] Detected 2499.503 MHz processor.
May 21 11:09:58 ceylan-desktop kernel: [    0.004005] Calibrating delay loop (skipped), value calculated using timer frequency.. 4999.00 BogoMIPS (lpj=9998012)
May 21 11:09:58 ceylan-desktop kernel: [    0.004020] Security Framework initialized
May 21 11:09:58 ceylan-desktop kernel: [    0.004039] AppArmor: AppArmor initialized
May 21 11:09:58 ceylan-desktop kernel: [    0.004045] Mount-cache hash table entries: 512
May 21 11:09:58 ceylan-desktop kernel: [    0.004167] Initializing cgroup subsys ns
May 21 11:09:58 ceylan-desktop kernel: [    0.004172] Initializing cgroup subsys cpuacct
May 21 11:09:58 ceylan-desktop kernel: [    0.004175] Initializing cgroup subsys memory
May 21 11:09:58 ceylan-desktop kernel: [    0.004181] Initializing cgroup subsys devices
May 21 11:09:58 ceylan-desktop kernel: [    0.004183] Initializing cgroup subsys freezer
May 21 11:09:58 ceylan-desktop kernel: [    0.004185] Initializing cgroup subsys net_cls

 

I would say the following:

Has this machine served you well so far?
Have any encountered any weird issues or problems?
Does everything work as expected?
Are there any crashes, lags, etc?

If the answers are yes, no, yes, no, then forget about it.

System messages are useful alongside physical symptoms of problems.
There's no system log that has no warnings and errors. If you try to debug every single one, just turn the machine off, it's easier. The only important thing is make sure your personal data is safely backed up.

Mrk

 

Ok,I will forget about it.Boot up time 22seconds ,shut off time 3 seconds.I can do everything and much more than I had done on Windows.So I think I should sit back and learn some common used linux commands now.

 

Boot time is a bit high for Lucid but I wouldn't worry about the BIOS message, if it was really corrupt, your system wouldn't boot. What you should try now is make sure to select only hdd in boot sequence under BIOS option and also turn off floppy support from the peripheral section if you can, the floppy seek adds time to the boot process, this is if you are not currently using any floppy. When was the last time you flashed your BIOS? Are you using a updated one?

 

mrk is right if you dont have any problem no need to do weirds thing on poor machine but if face you can flush your bios and reinstall it

it will remove your bios software and reinstall it best is its done by some expert

also there are many risk involved in that so its highly recommend only if you are facing any boot problems ....etc

also i sugest you to install and run

rkhunter -c

and chkrootkit

also check if firewall is active or not by ufw -status or if you got gui gufw check if enable or not

if they show system is clean no need to worry untill you face some real problem it might be a bug or something

also

can you more specify about your machine

company name and model number of your laptop/desktop ....etc

 

I do not have floppy and I disabled floppy from the bios.

This PC is only 15 months old,I did not update the bios.

Firewall is active.

This machine is made by a company which sells microsoft products and gives help to organizations.The people are engineers and microsoft professionals.When I told them that I was going to only use Ubuntu as a system,they laughed at me,but now I laugh at them.
The attached file shows the hardware specs.I used system profiler and benchmark program.

I installed rootkithunter and the system is clean.

 

i ask because you can get a bios update from vender side like for example if you know the type of your mother board you can get a update from motherboard manufacture if not give on company site but most of chances its given on company site

what i was looking was like i got lenovo n100 0768-A36 not from lenovo site i get all information about my product also its driver and bios updates etc

what i was asking is it dell.....lenovo sony hp .....etc which one and which model number

 

cet, you may come across some warning messages when scanning with rkhunter. Check in /var/log/rkhunter.log
I had a few and soon found out that they were all false positives. Here is my list of false positives that I told rkhunter to ignore by editing rkhunter.conf in /etc:-

Code:

LUCID   (3/5/2010)

Warning: Suspicious file types found in /dev:
[18:04:16]          /dev/shm/sem.ADBE_REL_walter: data        (UNCOMMENTED)         
[18:04:16]          /dev/shm/sem.ADBE_WritePrefs_walter: data    (")
[18:04:16]          /dev/shm/sem.ADBE_ReadPrefs_walter: data     (")
[18:04:16]          /dev/shm/pulse-shm-2796030377: data
[18:04:16]          /dev/shm/mono-shared-1000-shared_fileshare-walter-desktop-Linux-x86_64-40-12-0: data
[18:04:16]          /dev/shm/mono-shared-1000-shared_data-walter-desktop-Linux-x86_64-328-12-0: data
[18:04:16]          /dev/shm/mono.1642: data
[18:04:16]          /dev/shm/pulse-shm-1192406971: data
[18:04:17]          /dev/shm/pulse-shm-1882854789: data
[18:04:17]          /dev/shm/pulse-shm-2297440267: data
[18:04:17]   Checking for hidden files and directories       [ Warning ]
[18:04:17] Warning: Hidden directory found: /etc/.java         (UNCOMMENTED)
[18:04:17] Warning: Hidden directory found: /dev/.udev              (")
[18:04:17] Warning: Hidden directory found: /dev/.initramfs         (")


ALLOWDEVFILE=/dev/shm/pulse-shm-*  (UNCOMMENTED)
ALLOWDEVFILE=/dev/shm/mono*	     (ADDED)

Note: ADBE refers to Adobe Reader.

/dev/.blkid.tab: ASCII text  (Ignore FP)

Log Files are in /var/log/rkhunter.log 

You can also make a bash script to automate the following:

sudo rkhunter --propupd
sudo rkhunter --update
sudo rkhunter -c --sk

The script is here (thanks iceni60) https://www.wilderssecurity.com/showpost.php?p=1499285&postcount=17

PS. Don't worry about boot time. Depends on motherboard. My Intel quad core Q9400 is not much faster than my wife's 2Ghz dual core which still has Karmic. The DP45SG Intel motherboard I have still has a bios handoff delay although it is now only 2 5secs. Once logged in desktop is there almost instantaneously.

 

Why do you scan against rootkits?
It has no bearing whatsoever on the possible bios issues.
Mrk

 

Cet, you are not running a server, you needn't worry about rootkits.

 

Hi linuxforall,

What makes you think that all BIOS corruptions result in an unbootable system? A properly installed BIOS w/an undesirable rootkit can easily boot up a system and the user would be none the wiser. Have a read of the following article: Insecure BIOS ‘Rootkit’ Found Pre-loaded In Major Manufacturers Laptops.

I would try to find a way to dump the BIOS and compare it to a verified version of the BIOS. One thing that can usually be done is to visit the motherboard manufacturer to see if there are any BIOS updates available. Even if no updates are available, usually there are available instances of the BIOS software in an ISO file form which can be downloaded and a set of instructions on how to install the BIOS. At the very least one could install the latest BIOS available form the motherboard manufacturer (even if it is the original one) to be assured that one has the original BIOS. If then you still see a BIOS corrupt message (then it might be a feature of the original BIOS which is somewhat suspect that the motherboard manufacturer would have shipped it in that form). Prior to doing any of this - I would certainly send an email to the customer support at the motherboard manufacturer and query them about the BIOS may be corrupt message and hear what they have to say about it.

-- Tom

 

Tom, there are no BIOSes with rootkit.
And there's no such thing, properly installed with rootkit.
Mrk

 

I know long while back there was a BIOS virus but that was only executable from Windows and not Linux and for years that has been patched. Corrupt BIOS won't let you into the system.

 

Mark and linuxforall,

Search for "bios rootkit" and you are likely to find several instances of what is possible - just saying. To say that there are no BIOSes with rootkits does not mean that there cannot be or are not curretnly in existence - unfortunately, you have no evidence to say that. Perhaps you meant that you have not heard of any incidents or any in the wild searching for a home to plant itself.

What I meant by "properly installed" was gleaned from some of the reports on BIOS rootkit efforts where they (the researchers) massaged the the size and md5sum to be the same as the original BIOS in order not to be detected in that manner.

Other than that, if no manufacturers are placing any unwanted bits into the BIOS you purchase on your machine, then I agree with you - everything "should" be clean! But, I doubt that includes a message that says "BIOS may be corrupt" - which is a message logged in the kernel logs and on further inspection was the message in cet's case (post#1): AMI BIOS detected: BIOS may corrupt low RAM, working around it.

The above message indicates that the kernel incorporated features to prevent corruption in low RAM which may have conflicted with some kernel data placement as a best guess on what may have been going on at boot time. Obviously, that is not the same as what the title to this thread misleads readers to infer.

-- Tom

 

I think this page is about my problem.But I do not understand how to correct it.
ht tp://lkml.indiana.edu/hypermail/linux/kernel/0811.1/013

 

Hi cet,

The message reads:
AMI BIOS detected: BIOS may corrupt low RAM, working around it.

This indicates that with regard to any data the BIOS may have loaded into low RAM that may conflict with kernel data in low RAM, the kernel is taking action to work around the potential conflict.

You do not have a problem - the kernel took care of it on boot up as logged into the kernel logs you have posted.

-- Tom