Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 2:44 PM, Freddie Cash wrote: > On Wed, Mar 16, 2011 at 2:20 PM, Garrett Cooper wrote: >> On Wed, Mar 16, 2011 at 10:20 AM, Freddie Cash wrote: >>> On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 >>> >>> Nevermind. PEBCAK error. Adding the right port address would work. >>> Amazing how easy it is to mixup a 3 and an E. :( >> >> Are you referring to the .flags value or the BOOT_COMCONSOLE_PORT value? Sorry, not the .flags value, that was set correctly. The .port value. >> Thanks, > > Both. > > The BIOS is configured to use COM3 for the remote access support, with > an address of 3E8. > > The kernel sees COM3 as uart0 with an address of 0x3e8. > > Me, in my infinite copy/paste wisdom set loader.conf and make.conf to use 3F8. > > Figured that one out by dropping to a loader prompt and reading > through the output of "show" and manually setting the hint.uart.0.port > correctly. Then setting it in loader.conf and make.conf correctly > afterward. > > -- > Freddie Cash > fjwc...@gmail.com > -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 2:20 PM, Garrett Cooper wrote: > On Wed, Mar 16, 2011 at 10:20 AM, Freddie Cash wrote: >> On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: >>> I feel like an idiot right now because I can just not figure out how >>> to make $subject work on a -CURRENT system. :( >>> >>> I've read through the Handbook chapter on this. I've done the process >>> I've used with 8.x systems. But once the kernel loads, the serial >>> console stops working. I'm obviously missing a step somewhere. >>> >>> Here's what I've done. Please point out my error(s): >>> >>> /boot/loader.conf: >>> hint.uart.0.disabled="0" >>> hint.uart.0.flags="0x30" >>> console="comconsole vidconsole" >>> comconsole_speed="115200" >>> boot_multicons="yes" >>> >>> /etc/make.conf: >>> BOOT_COMCONSOLE_PORT=0x3F8 >>> BOOT_COMCONSOLE_SPEED=115200 >> >> Nevermind. PEBCAK error. Adding the right port address would work. >> Amazing how easy it is to mixup a 3 and an E. :( > > Are you referring to the .flags value or the BOOT_COMCONSOLE_PORT value? > Thanks, Both. The BIOS is configured to use COM3 for the remote access support, with an address of 3E8. The kernel sees COM3 as uart0 with an address of 0x3e8. Me, in my infinite copy/paste wisdom set loader.conf and make.conf to use 3F8. Figured that one out by dropping to a loader prompt and reading through the output of "show" and manually setting the hint.uart.0.port correctly. Then setting it in loader.conf and make.conf correctly afterward. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 10:20 AM, Freddie Cash wrote: > On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: >> I feel like an idiot right now because I can just not figure out how >> to make $subject work on a -CURRENT system. :( >> >> I've read through the Handbook chapter on this. I've done the process >> I've used with 8.x systems. But once the kernel loads, the serial >> console stops working. I'm obviously missing a step somewhere. >> >> Here's what I've done. Please point out my error(s): >> >> /boot/loader.conf: >> hint.uart.0.disabled="0" >> hint.uart.0.flags="0x30" >> console="comconsole vidconsole" >> comconsole_speed="115200" >> boot_multicons="yes" >> >> /etc/make.conf: >> BOOT_COMCONSOLE_PORT=0x3F8 >> BOOT_COMCONSOLE_SPEED=115200 > > Nevermind. PEBCAK error. Adding the right port address would work. > Amazing how easy it is to mixup a 3 and an E. :( Are you referring to the .flags value or the BOOT_COMCONSOLE_PORT value? Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On 3/16/11 10:20 AM, Freddie Cash wrote: On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 Nevermind. PEBCAK error. Adding the right port address would work. Amazing how easy it is to mixup a 3 and an E. :( I'll hang my head in shame now. :( not a waste because I was looking for an example set of configs and steps.. :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: > I feel like an idiot right now because I can just not figure out how > to make $subject work on a -CURRENT system. :( > > I've read through the Handbook chapter on this. I've done the process > I've used with 8.x systems. But once the kernel loads, the serial > console stops working. I'm obviously missing a step somewhere. > > Here's what I've done. Please point out my error(s): > > /boot/loader.conf: > hint.uart.0.disabled="0" > hint.uart.0.flags="0x30" > console="comconsole vidconsole" > comconsole_speed="115200" > boot_multicons="yes" > > /etc/make.conf: >BOOT_COMCONSOLE_PORT=0x3F8 >BOOT_COMCONSOLE_SPEED=115200 Nevermind. PEBCAK error. Adding the right port address would work. Amazing how easy it is to mixup a 3 and an E. :( I'll hang my head in shame now. :( -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
How does one get a working serial console with gptboot?
I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 /etc/ttys: ttyu0 "/usr/libexec/getty std.115200" vt100 on secure Then I rebuilt the boot code via: cd /usr/src/sys/boot make cleandepend; make depend; make; make install And I loaded the new boot code into the GPT via: gpart bootcode -p /boot/gptboot -i 1 ada0 This motherboard (SuperMicro H8DGi-F) includes an IPMI-enabled serial-over-LAN setup, including a KVM-over-LAN. The KVM-over-LAN uses a virtual onscreen keyboard, though, so it's a pain to use, which is why I'm trying to get the serial console stuff working. The BIOS is configured to use COM3 for the remote access setup. The kernel detects this as uart0, and dmesg shows it as being detect and set as "uart0: console (115200,n,8,12). The serial console works at the boot loader screens and I can drop to a loader prompt, type away, etc. As soon as I type "boot" and the kernel loads ... the serial console dies. Any suggestions? -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
