On 02/21/13 14:48, Daniel O'Connor wrote: > > On 22/02/2013, at 9:15, Navdeep Parhar <npar...@gmail.com> wrote: >>> uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 >>> uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 >>> uart2: <16550 or compatible> port 0x3e8-0x3ef irq 5 flags 0x30 on acpi0 >>> >>> The loader talks on the serial console fine, it's the kernel that doesn't >>> use it which is the problem. >> >> And what do you see in kenv | egrep 'uart|com' ? > > comconsole_port="0x3e8" > comconsole_speed="115200" > hint.uart.0.at="isa" > hint.uart.0.flags="0x00" > hint.uart.0.irq="4" > hint.uart.0.port="0x3F8" > hint.uart.1.at="isa" > hint.uart.1.flags="0x00" > hint.uart.1.irq="3" > hint.uart.1.port="0x2F8" > hint.uart.2.flags="0x30" > menu_command[1]="boot" > menu_command[2]="goto_prompt" > menu_command[4]="toggle_acpi" > menu_command[5]="toggle_safemode" > menu_command[6]="toggle_singleuser" > menu_command[7]="toggle_verbose" > menu_timeout_command="boot"
No hw.uart.console, hmmm. It may be time to put some printf's in comc_setup() in boot/i386/libi386/comconsole.c and see what's up. One last thing before you take that route: if you create an environment variable named hw.uart.console in loader.conf (set it to anything), do you at least see it getting unset? That'll tell you whether comc_setup() even ran. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
