help needed to enable boot.log in Hardy Heron
David Armour
d.f.armour at shaw.ca
Tue Jun 24 18:45:52 UTC 2008
Hello list,
On Mon, Jun 23, 2008 at 8:24 PM, Vitorio Okio <ovitorio at hotmail.com> wrote:
> > I badly need to log all the messages I see on my screen upon the boot
> > process. <snip> The messages I need are pre-syslog messages. I
tried to
> > enable "verbose"
<snip>
> It's crazy, the boot messages are of extreme need in many situations.
> But what is their value when they scroll up with a crazy speed and
I was in the middle of writing a question along these lines, (see below)
but
Vitorio beat me to it. Thanks also to Jeremy, Chris and Karl for adding
pieces
to this still-unsolved puzzle.
I've since read that Crtl-S/Q may control the rate of start-up messages,
and/or that Crtl-Alt-F8 makes them viewable in that console. HTH.
"Jeremy Huntwork" <jhuntwork at lightcubesolutions.com> wrote
> > ... Without using bootlogd (which from googling appears to be
currently broken,
> > which is why it wasn't included), the only other thing I can
currently think of is
> > to manually modify the bootscript functions to tee output to a file
of your choice.
> > ... If I have time and can sort this out, I'll let you know...
> This would be in great help.
Ditto that. Where are the bootscripts, and just how would we modify them?
> Any suggestions folks? The file /var/log/boot exists but empty.
Karl F. Larsen wrote
> I gather you did file a bug? I checked my /var/log/boot and it is empty
Here's my original working-up of the question I was going to call [Update
Manager Ate My Soundcard!]:
Recently (June 18), I used Hardy's update manager to up-grade FirefoxB5
to Firefox3.
During the required restart, however, I noticed the following error message:
disk error...
press any key to continue:
(It's a Seagate 160Gb, installed Dec27/07, i.e. only six months' service.)
June 20, after a regular Update Manager Required Re-boot... saw following
error messages [1], although a Saturday, June21 '08 3:58pm: smartmontools'
smartctl -a /dev/sda gives the disk a "passed" grade.
[0] The specific pre-syslog boot message I want to look at: a red
[fail] in
a long list of [ok]s, although the gdm segfault and the mysterious
error 6 are of considerable interest, as well.
[1] No suitable module for running kernel found.
Incorrect checksum in table [0EMB] ... BF should be B2 [20070126]
... gdm [5613] segfault @ 7672657f... eip b77cd7e2... esp
bfc39c30 error 6
...some index files failed to download...
...drop to root shell prompt
[2] recovery mode (first time): No suitable module for running
kernel found...
got to splash screen/username... password
... stops [hard reboot]
recovery mode (2nd time): Some index files failed to download.
Ran apt-get update as root, as suggested
recovery mode (3rd time): system seemed to stall at
username/password
point, but then seemed to recover, and actually finish.
Everything *seems* okay, except for sound. [4, 5] Update Manager ate my
(onboard, no less!) soundcard?!!! How does *that* happen?
[3] # snip from June 20 dmesg output:
[ 38.782803] system 00:05: ioport range 0x480-0x48f has been reserved
[ 38.782810] system 00:05: ioport range 0x4d0-0x4d1 has been reserved
[ 38.782815] system 00:05: ioport range 0x800-0x87f has been reserved
[ 38.782819] system 00:05: ioport range 0x880-0x8ff has been reserved
[ 38.782824] system 00:05: ioport range 0xc00-0xc1f has been reserved
[ 38.782834] system 00:05: iomem range 0xfff80000-0xffffffff could not
be reserved
[ 38.782839] system 00:05: iomem range 0xffe80000-0xffefffff has been
reserved
[ 38.782844] system 00:05: iomem range 0xfed00000-0xfed003ff has been
reserved
[ 38.782860] system 00:06: iomem range 0xfec00000-0xfec00fff has been
reserved
[ 38.782865] system 00:06: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 38.782886] system 00:0c: iomem range 0x0-0x9ffff could not be reserved
[ 38.782891] system 00:0c: iomem range 0xc0000-0xdffff could not be
reserved
[ 38.782896] system 00:0c: iomem range 0xe0000-0xfffff could not be
reserved
[ 38.782901] system 00:0c: iomem range 0x100000-0x3fffffff could not
be reserved
[ 38.782905] system 00:0c: iomem range 0x0-0x0 could not be reserved
Googling on the assortment of error messages that flashed by produced the
usual crop of vaguely useful but not actually anything-at-all-like-tea
'hits',
and a survey of /var/log contents only adds to the mystery. /var/log/boot,
for example is similarly empty, presumably because /boot/init.d/bootlogd
shows BOOTLOGD_ENABLE=No.
[4] /var/log/debug lists a number of instances of:
...audio.conf Key file does not have key 'Enabled'
[5] sudo lsof /dev/snd/*
lsof: status error on /dev/snd/*: No such file or directory
lsof 4.78
aplay -l
aplay: device_list:205: no soundcards found...
lspci -v
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741
Host (rev 03)
Flags: bus master, medium devsel, latency 32
Memory at d0000000 (32-bit, non-prefetchable) [size=64M]
Capabilities: <access denied>
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port
(virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
Memory behind bridge: cde00000-cfefffff
Prefetchable memory behind bridge: bdd00000-cdcfffff
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL
Media IO] (rev 25)
Flags: bus master, medium devsel, latency 0
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
Flags: medium devsel
I/O ports at 0c00 [size=32]
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
(prog-if 80 [Master])
Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller
(A,B step)
Flags: bus master, medium devsel, latency 128
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled]
[size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled]
[size=1]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled]
[size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled]
[size=1]
I/O ports at ffa0 [size=16]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
AC'97 Sound Controller (rev a0)
Subsystem: Elitegroup Computer Systems Unknown device a00c
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at e800 [size=256]
I/O ports at ec00 [size=128]
Capabilities: <access denied>
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 17
Memory at cffdd000 (32-bit, non-prefetchable) [size=4K]
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 18
Memory at cffde000 (32-bit, non-prefetchable) [size=4K]
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0
Controller (prog-if 20 [EHCI])
Subsystem: Silicon Integrated Systems [SiS] USB 2.0 Controller
Flags: bus master, medium devsel, latency 64, IRQ 19
Memory at cffdf000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI
Fast Ethernet (rev 90)
Subsystem: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet
Adapter
Flags: bus master, medium devsel, latency 64, IRQ 16
I/O ports at e400 [size=256]
Memory at cffdc000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at cffa0000 [disabled] [size=128K]
Capabilities: <access denied>
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2
MX/MX 400] (rev b2) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at cfef0000 [disabled] [size=64K]
Capabilities: <access denied>
So, to sum up: Diagnosing/troubleshooting boot errors conveniently largely
depends on getting a bootlog which in turn means enabling bootlogd...
but the bootlog daemon has a bug, or is otherwise dis-abled in Hardy?
As a workaround to these circumstances, you may try:
Crtl-S/Q,
Crtl-Alt-F8, or
modify a bootscript to 'tee' output to a user-created file...
(Is that about it?)
Thanks in advance for any additional thoughts.
More information about the ubuntu-users
mailing list