I've managed to find this nowhere on Google or http://marc.theaimsgroup.com/?l=suse-linux-e&r=1&w=2 I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Felix, El Lun 28 Mar 2005 20:39, Felix Miata escribió:
I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default.
On my 8.2 systems there is no /var/log/boot.log file at all; maybe I have wiped it from the disks long ago, I don't remember. The boot messages are in /var/log/boot.msg. Regards, -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
# /etc/syslog.conf - Configuration file for syslogd(8) # # For info about the format of this file, see "man syslog.conf". # # # # print most on tty10 and on the xconsole pipe # kern.warning;*.err;authpriv.none /dev/tty10 kern.warning;*.err;authpriv.none |/dev/xconsole *.emerg * # enable this, if you want that root is informed # immediately, e.g. of logins #*.alert root # # all email-messages in one file # mail.* -/var/log/mail mail.info -/var/log/mail.info mail.warning -/var/log/mail.warn mail.err /var/log/mail.err # # all news-messages # # these files are rotated and examined by "news.daily" news.crit -/var/log/news/news.crit news.err -/var/log/news/news.err news.notice -/var/log/news/news.notice # enable this, if you want to keep all news messages # in one file #news.* -/var/log/news.all # # Warnings in one file # *.=warning;*.=err -/var/log/warn *.crit /var/log/warn # # save the rest in one file # *.*;mail.none;news.none -/var/log/messages # # enable this, if you want to keep all messages # in one file #*.* -/var/log/allmessages # # Some foreign boot scripts require local7 # local0,local1.* -/var/log/localmessages local2,local3.* -/var/log/localmessages local4,local5.* -/var/log/localmessages local6,local7.* -/var/log/localmessages Check /var/log/localmessages for your boot messages ... Andreas Philipp wrote:
Felix,
El Lun 28 Mar 2005 20:39, Felix Miata escribió:
I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default.
On my 8.2 systems there is no /var/log/boot.log file at all; maybe I have wiped it from the disks long ago, I don't remember. The boot messages are in /var/log/boot.msg.
Regards,
El Lun 28 Mar 2005 21:01, Lawrence Bowie escribió:
Check /var/log/localmessages for your boot messages ...
Well, I know where my boot messages are and I said so. No need to post the whole syslog man page. -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
On Mon, 2005-03-28 at 21:01 -0500, Lawrence Bowie wrote:
Andreas Philipp wrote:
Felix,
El Lun 28 Mar 2005 20:39, Felix Miata escribió:
I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default.
On my 8.2 systems there is no /var/log/boot.log file at all; maybe I have wiped it from the disks long ago, I don't remember. The boot messages are in /var/log/boot.msg.
Regards,
So what does syslog (logs of a running system) have to do with the boot log (boot.msg, log of the boot messages only). They are different log files for two different processes. Please do not top post ( putting your answer before the question ) this isn't jeopardy. boot.msg is for what happens during the boot process only, /var/log/messages is for log file for what takes place while the system is running ( after the boot process ). -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
El Lun 28 Mar 2005 20:39, Felix Miata escribió:
I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default.
boot.msg is for what happens during the boot process only, /var/log/messages is for log file for what takes place while the system is running ( after the boot process ).
See my Mon, 28 Mar 2005 22:09:58 -0500 thread response to this issue. What I'm up against is a failure of the boot device to be properly used. SuSE behaves as expected. Mandrake is giving "no init found" kernel panics. I'm trying to find out why. SuSE will only boot when the BIOS is set to compatible mode, but finds the SATA boot device on /dev/hda18. When Mandrake 10.2 was installed on the same SATA device (/dev/hda7), it treated it as /dev/sda7. I've done so much messing around with it I can't remember precisely which device(s) were attached during installation, which is what is responsible for the kernel panics. I'm trying to get back to that point without reinstalling, so I boot SuSE to make configuration adjustments, then try to boot Mandrake. Mandrake for some reason is only finding the CDROM on the PATA controller, calling it /dev/hda, and apparently ignoring the SATA attached device, even though that's where the boot loader found its kernel and initrd. This is the motherboard: http://www.pcchips.com.tw/PCCWeb/Products/ProductsDetail.aspx?MenuID=92&LanID=0&DetailID=298&DetailName=Specification http://www.newegg.com/app/ViewProductDesc.asp?description=13-185-049&depa=1 -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Lawrence Bowie wrote:
Check /var/log/localmessages for your boot messages ...
This file is also 0 bytes. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Andreas Philipp wrote:
El Lun 28 Mar 2005 20:39, Felix Miata escribió:
I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default.
On my 8.2 systems there is no /var/log/boot.log file at all; maybe I have wiped it from the disks long ago, I don't remember. The boot messages are in /var/log/boot.msg.
My purpose is a diagnostic exercise. SuSE 8.2 & Mandrake 10.2 are both installed on the same system. SuSE boots. Mandrake doesn't. I need to figure out why. /var/log/boot.log on Mandrake looks like this: http://qa.mandrakesoft.com/attachment.cgi?id=2851 SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Monday 28 March 2005 7:09 pm, Felix Miata wrote:
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
Did you try dmesg, it may display what you want. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.13-default x86_64
On Mon, 2005-03-28 at 19:35 -0800, Scott Leighton wrote:
On Monday 28 March 2005 7:09 pm, Felix Miata wrote:
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
Did you try a Mandrake list to solve your Mandrake problem? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-03-28 at 22:46 -0500, Ken Schneider wrote:
On Mon, 2005-03-28 at 19:35 -0800, Scott Leighton wrote:
On Monday 28 March 2005 7:09 pm, Felix Miata wrote:
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
Did you try a Mandrake list to solve your Mandrake problem?
Further, it looks like you have the mount points messed up. I would start there to try to solve the problem. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Mon, 2005-03-28 at 22:46 -0500, Ken Schneider wrote:
On Mon, 2005-03-28 at 19:35 -0800, Scott Leighton wrote:
On Monday 28 March 2005 7:09 pm, Felix Miata wrote:
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
Did you try a Mandrake list to solve your Mandrake problem?
First thing to do was make the boot messages show up on SuSE, so that's why I started here. Then it became apparent there were overlapping issues. The project is really all about figuring out this game of so many devices pretending to be SCSI. On this particular motherboard, there is ICH6 support for up to 6 ATA devices. The OS shouldn't be pretenting any devices connected to those ports are anything but ATA devices. I doubt it's a problem tied to any specific distro.
Further, it looks like you have the mount points messed up. I would start there to try to solve the problem.
I know this is the problem. I'm trying to figure out why it's a problem, what's at its root. One might suggest I try installing a newer SuSE and see if it behaves the same. I expect it would, because I think it is the 2.6 kernel that is responsible, with 2.4 behaving as expected, but 2.6 pretending SATA is PATA. If so, it can't be done, due to an artificial obstacle: the SCSI 16 partition per device limit. I have plenty disk space, but the partition count is already 37, and all the freespace is above #18. SuSE is working because it's using hda18 for /. If I try to put another on hda19 and the kernel thinks the device is SCSI, it won't work. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Scott Leighton wrote:
On Monday 28 March 2005 7:09 pm, Felix Miata wrote:
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
Did you try dmesg, it may display what you want.
No. It overflows the screen, and also lacks the timestamps of boot.log that I use to narrow down points of interest. Where does its output come from? -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Monday 28 March 2005 7:53 pm, Felix Miata wrote:
Scott Leighton wrote:
On Monday 28 March 2005 7:09 pm, Felix Miata wrote:
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
Did you try dmesg, it may display what you want.
No. It overflows the screen, and also lacks the timestamps of boot.log that I use to narrow down points of interest. Where does its output come from?
dmesg | less No idea where the output comes from, possibly it's a specially formatted version of boot.msg, but I really don't know. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.13-default x86_64
Scott Leighton wrote:
On Monday 28 March 2005 7:53 pm, Felix Miata wrote:
Scott Leighton wrote:
Did you try dmesg, it may display what you want.
No. It overflows the screen, and also lacks the timestamps of boot.log that I use to narrow down points of interest. Where does its output come from?
dmesg | less
No idea where the output comes from, possibly it's a specially formatted version of boot.msg, but I really don't know.
Dmesg doesn't tell me anything about when the messages were generated, so is of marginal help. Redirected dmesg output to a file is equally unhelpful. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
The Monday 2005-03-28 at 23:20 -0500, Felix Miata wrote:
No. It overflows the screen, and also lacks the timestamps of boot.log that I use to narrow down points of interest. Where does its output come from?
dmesg | less
No idea where the output comes from, possibly it's a specially formatted version of boot.msg, but I really don't know.
Dmesg doesn't tell me anything about when the messages were generated, so is of marginal help. Redirected dmesg output to a file is equally unhelpful.
The /var/log/boot.msg file contains no timestamp, the same as dmesg, and that's how it is. If it overflows, use a pipe to less, as Scott told you (not to a file). Standard unix/linux, you know... -- Cheers, Carlos Robinson
Felix Miata wrote:
Andreas Philipp wrote:
El Lun 28 Mar 2005 20:39, Felix Miata escribió:
I have 8.2 installed on 2 systems. This file is dated 26 Sep 2003 and 0 bytes on both. Isn't this file supposed to be a mirror of the messages that flash on screen during boot? How do I enable saving boot messages to this file? On my Mandrake systems this is apparently enabled by default.
On my 8.2 systems there is no /var/log/boot.log file at all; maybe I have wiped it from the disks long ago, I don't remember. The boot messages are in /var/log/boot.msg.
My purpose is a diagnostic exercise. SuSE 8.2 & Mandrake 10.2 are both installed on the same system. SuSE boots. Mandrake doesn't. I need to figure out why. /var/log/boot.log on Mandrake looks like this: http://qa.mandrakesoft.com/attachment.cgi?id=2851
SuSE's /var/log/boot.msg, which has no Mandrake counterpart, bears little resemblance to Mandrake's /var/log/boot.log, and has no value for this diagnostic exercise. I need to get SuSE to generate a similar file to do me any good.
I turned out to not need the SuSE boot messages. After looking at Mandrake's logs long enough I finally realized there was no module being loaded to support the SATA portion of the ICH6. Even if SuSE had been writing corresponding logs, I don't think they wouldn't have shown a SATA module being loaded, as the disk was in a much older system when the install was done, and was running on /dev/hda, not as a SCSI device. When I first installed, I had the onboard IT8212 controller disabled, and Mandrake installed to SATA as a (!&$%@!*) SCSI device. After successful installation, my next goal was to get Mandrake to boot the device, sans its PATA to SATA converter, from the IT8212 controller as /dev/hda. Ultimately I got this to work after shifting the device from ICH6 SATA to ICH6 PATA, then building a new initrd with the it821x module built in, and then moving it to the IT8212. While I was figuring it all out, I did two kernel upgrades. The kernel upgrades were not done on the SATA controller, so the new kernel initrds were leaving out the sata module. Once I realized this, it booted fine from the original kernel and initrd. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
participants (6)
-
Andreas Philipp -
Carlos E. R. -
Felix Miata -
Ken Schneider -
Lawrence Bowie -
Scott Leighton