Re: kernel boot messages absent
On Thu, Oct 03, 2002 at 03:55:17AM +0200, Alexander Langer wrote: Also sprach Bernd Walter ([EMAIL PROTECTED]): You can verify with conscontrol. It should list consolectl for vga console and Muting off. from dmesg: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 Now that you wrote it isolated - the flags are missing: sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 Seems like your hints are ignored. Have you tried disabling acpi? -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
Also sprach Bernd Walter ([EMAIL PROTECTED]): from dmesg: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 Now that you wrote it isolated - the flags are missing: sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 Seems like your hints are ignored. Have you tried disabling acpi? Yes - when I disable acpi in the hints, acpi is not used (legacy devices attach to isa0 and no acpi h/w is probed) - thus the device.hints file is parsed as it should. I have no idea why it misses the flags. This is very uncommon, and my (-CURRENT)-desktop machine doesn't show this behaviour. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
erm, no. acpi.disable=0 _doesn't_ disable acpi for me. Seems like you are right and the hints are ignored. I'll try to find out why, thanks :) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
On Thu, Oct 03, 2002 at 01:20:02PM +0200, Alexander Langer wrote: erm, no. acpi.disable=0 _doesn't_ disable acpi for me. Seems like you are right and the hints are ignored. acpi.disabled=1 -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
On Thu, 3 Oct 2002, Bernd Walter wrote: On Thu, Oct 03, 2002 at 03:55:17AM +0200, Alexander Langer wrote: Also sprach Bernd Walter ([EMAIL PROTECTED]): You can verify with conscontrol. It should list consolectl for vga console and Muting off. from dmesg: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 Now that you wrote it isolated - the flags are missing: sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 flags is a very unusual place for a device to be at. This happens on systems with working consoles too: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 There is no sign of the keyboard ports where the keyboard part of sc0 really is at. This is a very old bug -- keyboard ports were not configured normally in 386BSD-0.0. My sc0 flags actually are 0x100. The virtual console flags seem to be unrelated to config flags. sc0 has been at flags here since at least 8 July. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
My sc0 device was at flags until I changed the hints line to: hint.sc.0.at=acpi A few days ago... On Thu, 3 Oct 2002, Bruce Evans wrote: On Thu, 3 Oct 2002, Bernd Walter wrote: On Thu, Oct 03, 2002 at 03:55:17AM +0200, Alexander Langer wrote: Also sprach Bernd Walter ([EMAIL PROTECTED]): You can verify with conscontrol. It should list consolectl for vga console and Muting off. from dmesg: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 Now that you wrote it isolated - the flags are missing: sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 flags is a very unusual place for a device to be at. This happens on systems with working consoles too: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 There is no sign of the keyboard ports where the keyboard part of sc0 really is at. This is a very old bug -- keyboard ports were not configured normally in 386BSD-0.0. My sc0 flags actually are 0x100. The virtual console flags seem to be unrelated to config flags. sc0 has been at flags here since at least 8 July. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
On 03-Oct-2002 Alexander Langer wrote: erm, no. acpi.disable=0 _doesn't_ disable acpi for me. Seems like you are right and the hints are ignored. I'll try to find out why, thanks :) For acpi it's 'disabled' for some reason, which is rather non-intuitive. Alex -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
Also sprach Bernd Walter ([EMAIL PROTECTED]): erm, no. acpi.disable=0 _doesn't_ disable acpi for me. Seems like you are right and the hints are ignored. acpi.disabled=1 Well, that's actually what I tried. Only disabling acpi from the loader (unset acpi_load) worked. Anyways, I just compiled a kernel with statically linked/wired GENERIC.hints, and that kernel does work properly. So indeed the problem was that the /boot/device.hints file was ignored. I don't know yet, why, but I'll take a look at it next week, when I have my other -CURRENT box as a reference/test box. Thanks for all the help :) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
Thus spake John Baldwin ([EMAIL PROTECTED]): Can anyone explain me why with a recent kernel (last kernel was from 1 year ago) the kernel boot messages disappear from the monitor once the propellor of the kernel boot has done like 5 rounds (last message is the last line of the Booting kernel in X seconds line, followed by a single - on the line, which used to be the propellor) You need to setup a /boot/device.hints file if you haven't already so that the kernel can configure it's console device. Nah, that machine already had a device.hints installed. And also with an upgraded device.hints (GENERIC.hints copied from /sys/i386/conf) the same problem occurs. And I don't think I'd have to edit device.hints on common hardware, using a GENERIC kernel, do I? It used to work before :-( Any more tips? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
On Wed, Oct 02, 2002 at 01:48:20PM +0200, Alexander Langer wrote: Thus spake John Baldwin ([EMAIL PROTECTED]): Can anyone explain me why with a recent kernel (last kernel was from 1 year ago) the kernel boot messages disappear from the monitor once the propellor of the kernel boot has done like 5 rounds (last message is the last line of the Booting kernel in X seconds line, followed by a single - on the line, which used to be the propellor) You need to setup a /boot/device.hints file if you haven't already so that the kernel can configure it's console device. Nah, that machine already had a device.hints installed. And also with an upgraded device.hints (GENERIC.hints copied from /sys/i386/conf) the same problem occurs. And I don't think I'd have to edit device.hints on common hardware, using a GENERIC kernel, do I? It used to work before :-( You can verify with conscontrol. It should list consolectl for vga console and Muting off. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
Also sprach Bernd Walter ([EMAIL PROTECTED]): You can verify with conscontrol. It should list consolectl for vga console and Muting off. from dmesg: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 but then: # conscontrol Configured: Available: Muting: off Hmm. Does look odd. My other machines do have at least one console listed in Available :) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: kernel boot messages absent
On 02-Oct-2002 Alexander Langer wrote: Hi! Can anyone explain me why with a recent kernel (last kernel was from 1 year ago) the kernel boot messages disappear from the monitor once the propellor of the kernel boot has done like 5 rounds (last message is the last line of the Booting kernel in X seconds line, followed by a single - on the line, which used to be the propellor) You need to setup a /boot/device.hints file if you haven't already so that the kernel can configure it's console device. It seems a bit like the kernel is thinking it boots from a serial console (not tried due to the lack of a serial cable, though). However, once the getty is started, the login prompt is shown on the monitor as it should. I've tried to tell the loader in loader.conf that console=vidconsole, but it doesn't help. Note that the loader itself is visible. This is the dmesg from boot -v. I've got no idea :-( Odd. Thanks for any pointers ... Uptime: 7h19m56s Terminate ACPI Rebooting... Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Tue Oct 1 15:35:39 CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc06a7000. Preloaded elf module /boot/kernel/acpi.ko at 0xc06a70b4. Calibrating clock(s) ... TSC clock: 647190907 Hz, i8254 clock: 1193189 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 647189786 Hz CPU: Pentium III/Pentium III Xeon/Celeron (647.19-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x387f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR, SSE real memory = 201261056 (196544K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x006ce000 - 0x0bfe7fff, 194093056 bytes (47386 pages) avail memory = 188153856 (183744K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6a90 bios32: Entry = 0xfd8c0 (c00fd8c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd8c0+0x11e pnpbios: Found PnP BIOS data at 0xc00f6ac0 pnpbios: Entry = f:8da2 Rev = 1.0 Other BIOS signatures found: random: entropy source mem: memory I/O Pentium Pro MTRR support enabled null: null device, zero device npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) Using $PIR table, 4 entries at 0xc00fdf80 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded07D 0x63 3 4 11 embedded0 12A 0x60 3 4 11 embedded09A 0x62 3 4 5 embedded01A 0x61 3 4 10 11 ACPI timer looks BAD min = 1, max = 5, width = 5 ACPI timer looks BAD min = 2, max = 5, width = 4 ACPI timer looks BAD min = 1, max = 16777213, width = 16777213 ACPI timer looks BAD min = 1, max = 5, width = 5 ACPI timer looks BAD min = 2, max = 5, width = 4 ACPI timer looks BAD min = 2, max = 5, width = 4 ACPI timer looks BAD min = 2, max = 16777213, width = 16777212 ACPI timer looks BAD min = 1, max = 6, width = 6 ACPI timer looks BAD min = 1, max = 5, width = 5 ACPI timer looks BAD min = 1, max = 5, width = 5 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base f800, size 26, enabled found- vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 found- vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 found- vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 map[20]: type 4, range 32, base 1050, size 4, enabled found- vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 map[20]: type 4, range 32, base 1060, size 5, port disabled found- vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=255 map[90]: type 4, range 32, base 1040, size 4, enabled found- vendor=0x8086, dev=0x7113, revid=0x02 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 map[10]: type 4, range
