Re: Strange (?) boot-up messages
On Thu, Aug 19, 1999 at 10:40:46AM -0300, Guilherme Soares Zahn wrote:
> Hi there,
>
> here I am, still trying to fine-tune my PC and understand it a bit
> further...
That attitude seems to be the minority these days, judging from the
recent flamefests on Slashdot.
>
> Now, I've been puzzled by some messages I find in the boot sequence
> and by a particular message I find in the syslog:
>
> When I boot the system, as soon as the klogd is started here comes the
> following messages:
>
> Aug 18 16:45:27 groo kernel: klogd 1.3-3#31, log source = /proc/kmsg
> started.
> Aug 18 16:45:27 groo kernel: Cannot find map file.
> Aug 18 16:45:27 groo kernel: Loaded 25 symbols from 4 modules.
>
> OK... I'm puzzled by the 2nd one... what does he mean by 'Cannot find
> map file'? I guess he means that he can't find the /boot/map file,
No, its looking for a System.map file, which lists where all the
functions live when the kernel is in memory. (useful for debugging
kernel panics among other things).
>
> but
> it's there (together with a boot.0300 and a boot.0302 - btw, what are
> those files anyway?) Is it somehow serious or dangerous for the system?
/boot/boot.0300 is a backup of the boot sector for the master boot
record of /dev/hda. /boot/boot.0302 would be a backup of the partition
boot record of /dev/hda2. (ls -l /dev/hda shows that hda is major device
3, minor device 0; ls -l /dev/hda2 shows that hda2 is major device 3,
minor device 2)
>
> A bit later, when setting up the serial ports, it states:
>
> Aug 18 16:45:27 groo kernel: Serial driver version 4.27 with no serial
> options enabled
> Aug 18 16:45:27 groo kernel: ttyS00 at 0x03f8 (irq = 4) is a 16450
> Aug 18 16:45:27 groo kernel: ttyS03 at 0x02e8 (irq = 3) is a 16450
>
> OK... whay ttyS00 and not ttyS0?? At home it happens just the same way,
> but there I have RedHat 5.2 installed and because of that I can't seem
> to find a way to get rid of the old /dev/cua0 mouse device, because if I
> link /dev/mouse to /dev/ttyS00 can't find the latter and if I link it to
> /dev/ttyS0 it won't find a mouse... ;-/
What is the output of 'ls -l /dev/ttyS*'? You are right, /dev/cua?
devices are obsolete now.
>
> And then, by the end of the boot-up procedure, I get this one (just like
> that, doubled):
>
> Aug 18 16:45:32 groo /usr/sbin/gpm[152]: Skipping a data packet (?)
> Aug 18 16:45:32 groo /usr/sbin/gpm[152]: Skipping a data packet (?)
>
> What's that all about? ;-?
Perhaps it has something to do with your other problems?
>
> Last, in my syslog I will find, from time to time:
>
> (...) kernel: floppy0: perpendicular mode not supported by this FDC.
>
> What is 'perpendicular mode'? Do the massage mean that my FDC is wrongly
> configured for Linux or what? ;-?
Can you use your floppy drive just fine? Looking at the source in
drivers/block/floppy.c, it has something to do with seeking and getting
high transfer rates (128k/s) on special floppy drive controllers.
>
> Thanks for your attention!!!
Any time
--
Stephen Pitts
smpitts@midsouth.rr.com
webmaster - http://www.mschess.org
Reply to: