Re: probs on 6.2-prerelease
Michael Vince wrote: > Hey all, > > I don't know if this is pre 6.2 specific but I changed my /etc/tty for > device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > login via regular KVM console, just don't get a login. > The more alarming thing was that while it appeared everything was > booting up from the boot up messages on the screen, I couldn't remotely > log into the server in fact it appears the machine didn't bring up the > Ethernet device as I couldn't even ping it. > As soon as I switched the ttyd0 back to 'off' and rebooted it I could > ssh back into the server etc. > I have a regular kernel and 1 jail and samba on this machine. > I know this isn't a "yes I'm having problems" response but thought it might be useful anyway. I'm running 6.2-pre on a Soekris Engineering Net4501 with ttyd0 enabled in /etc/ttys and I'm not having any problems with the system booting or logging in via serial console. SSH logins work fine and the network is brought-up as normal during boot. I've had this system in the same config (in regards to /etc/ttys) since the 6 was still the HEAD branch and I have yet to see problems with it. One difference here is that I don't have any virtual consoles enabled BUT ttyd0 (and pseudo-terminals), as this box doesn't have a video card, just a serial port. FreeBSD marconi.localnet 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Tue Sep 12 03:06:13 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MINIBSD6 i386 /etc/ttys: # # $FreeBSD: src/etc/etc.i386/ttys,v 1.10 2003/10/24 15:44:08 simokawa Exp $ # @(#)ttys5.1 (Berkeley) 4/17/89 ... console noneunknown off secure # ttyv0 "/usr/libexec/getty Pc" cons25 off insecure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons25 off insecure ttyv2 "/usr/libexec/getty Pc" cons25 off insecure ttyv3 "/usr/libexec/getty Pc" cons25 off insecure ttyv4 "/usr/libexec/getty Pc" cons25 off insecure ttyv5 "/usr/libexec/getty Pc" cons25 off insecure ttyv6 "/usr/libexec/getty Pc" cons25 off insecure ttyv7 "/usr/libexec/getty Pc" cons25 off insecure ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off insecure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 "/usr/libexec/getty std.9600" dialup on secure ttyd1 "/usr/libexec/getty std.9600" dialup off secure ttyd2 "/usr/libexec/getty std.9600" dialup off secure ttyd3 "/usr/libexec/getty std.9600" dialup off secure # Dumb console dcons "/usr/libexec/getty std.9600" vt100 off secure -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
On Mon, Sep 25, 2006 at 09:08:26AM -0400, Michael Proto wrote: > Michael Vince wrote: > > I don't know if this is pre 6.2 specific but I changed my /etc/tty for > > device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > > login via regular KVM console, just don't get a login. > > The more alarming thing was that while it appeared everything was > > booting up from the boot up messages on the screen, I couldn't remotely > > log into the server in fact it appears the machine didn't bring up the > > Ethernet device as I couldn't even ping it. > > As soon as I switched the ttyd0 back to 'off' and rebooted it I could > > ssh back into the server etc. > > I have a regular kernel and 1 jail and samba on this machine. > I know this isn't a "yes I'm having problems" response but thought it > might be useful anyway. > I'm running 6.2-pre on a Soekris Engineering Net4501 with ttyd0 enabled > in /etc/ttys and I'm not having any problems with the system booting or > logging in via serial console. SSH logins work fine and the network is > brought-up as normal during boot. I've had this system in the same > config (in regards to /etc/ttys) since the 6 was still the HEAD branch > and I have yet to see problems with it. One difference here is that I > don't have any virtual consoles enabled BUT ttyd0 (and > pseudo-terminals), as this box doesn't have a video card, just a serial > port. I can also report no problems running 6.2-pre on i686. I am running on several machines, using serial consoles, machines _with_ video cards, but mostly unused (one machine has a KVM connected, and it works fine, as well. No problems with video, no problems with network, no problems with ssh login, etc. -greg FreeBSD xxx.xxx.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #21: Tue Sep 19 19:37:00 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ i386 /etc/ttys: [...] ttyd0 "/usr/libexec/getty std.9600" xterm on secure [...] /boot/loader.conf [...] console=comconsole [...] -- greg byshenk - [EMAIL PROTECTED] - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
> Hey all, > > I don't know if this is pre 6.2 specific but I changed my /etc/tty for > device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > login via regular KVM console, just don't get a login. > The more alarming thing was that while it appeared everything was > booting up from the boot up messages on the screen, I couldn't remotely > log into the server in fact it appears the machine didn't bring up the > Ethernet device as I couldn't even ping it. > As soon as I switched the ttyd0 back to 'off' and rebooted it I could > ssh back into the server etc. > I have a regular kernel and 1 jail and samba on this machine. > > This might just be a ports thing but on another 6.2 server I setup a > jailed mail server with courier imap and I have noticed that it fails to > build the courier-imap port with FAM support. > I tried also installing the gamin FAM alternative which builds ok but I > get signal 11 when I try to login to the imap server. > > Does anyone else have these problems? > I've been having this for a very long time, if the serial port does not realy exist - i don't know the technical wording for this -, if the kernel detected the sio hardare, but it's not realy wired, then it the kernel will hang when getty will try to open it. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
On Mon, Sep 25, 2006 at 04:54:36PM +0300, Danny Braniss wrote: > > I don't know if this is pre 6.2 specific but I changed my /etc/tty for > > device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > > login via regular KVM console, just don't get a login. > > The more alarming thing was that while it appeared everything was > > booting up from the boot up messages on the screen, I couldn't remotely > > log into the server in fact it appears the machine didn't bring up the > > Ethernet device as I couldn't even ping it. > > As soon as I switched the ttyd0 back to 'off' and rebooted it I could > > ssh back into the server etc. > > I have a regular kernel and 1 jail and samba on this machine. > > I've been having this for a very long time, if the serial port does > not realy exist - i don't know the technical wording for this -, > > if the kernel detected the sio hardare, but it's not realy > wired, then it the kernel will hang when getty will try to open it. Per chance is the sio* device the kernel detects mapped to acpi0? :-) (Also, taking freebsd-ports off this portion of the discussion; the 2nd part of the OP's thread pertains to freebsd-ports, but not this portion). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
Danny Braniss wrote: Hey all, I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. This might just be a ports thing but on another 6.2 server I setup a jailed mail server with courier imap and I have noticed that it fails to build the courier-imap port with FAM support. I tried also installing the gamin FAM alternative which builds ok but I get signal 11 when I try to login to the imap server. Does anyone else have these problems? I've been having this for a very long time, if the serial port does not realy exist - i don't know the technical wording for this -, if the kernel detected the sio hardare, but it's not realy wired, then it the kernel will hang when getty will try to open it. danny OK good then its not just me, yes I haven't checked if the serial port is actually enabled in the bios, still I think its quite ordinary to have a machine basically fully hang up just because theres no active serial port. With no network or serial (unless you can enable/find it hardware side) I had to boot from the Freebsd install cdrom in fix it mode and mount the installed setup and revert the tty change. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
[...] > > >>Hey all, > >> > >>I don't know if this is pre 6.2 specific but I changed my /etc/tty for > >>device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > >>login via regular KVM console, just don't get a login. > >>The more alarming thing was that while it appeared everything was > >>booting up from the boot up messages on the screen, I couldn't remotely > >>log into the server in fact it appears the machine didn't bring up the > >>Ethernet device as I couldn't even ping it. > >>As soon as I switched the ttyd0 back to 'off' and rebooted it I could > >>ssh back into the server etc. > >>I have a regular kernel and 1 jail and samba on this machine. > >> > >>This might just be a ports thing but on another 6.2 server I setup a > >>jailed mail server with courier imap and I have noticed that it fails to > >>build the courier-imap port with FAM support. > >>I tried also installing the gamin FAM alternative which builds ok but I > >>get signal 11 when I try to login to the imap server. > >> > >>Does anyone else have these problems? > >> > >> > >> > > > >I've been having this for a very long time, if the serial port does > >not realy exist - i don't know the technical wording for this -, > > > >if the kernel detected the sio hardare, but it's not realy > >wired, then it the kernel will hang when getty will try to open it. > > > >danny > > > > > OK good then its not just me, yes I haven't checked if the serial port > is actually enabled in the bios, still I think its quite ordinary to > have a machine basically fully hang up just because theres no active > serial port. With no network or serial (unless you can enable/find it > hardware side) I had to boot from the Freebsd install cdrom in fix it > mode and mount the installed setup and revert the tty change. > next time, just boot single user, do a fsck / then mount -u / at which point you will be able to fix /etc/ttys or any other screwup. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
> On Mon, Sep 25, 2006 at 04:54:36PM +0300, Danny Braniss wrote: > > > I don't know if this is pre 6.2 specific but I changed my /etc/tty for > > > device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > > > login via regular KVM console, just don't get a login. > > > The more alarming thing was that while it appeared everything was > > > booting up from the boot up messages on the screen, I couldn't remotely > > > log into the server in fact it appears the machine didn't bring up the > > > Ethernet device as I couldn't even ping it. > > > As soon as I switched the ttyd0 back to 'off' and rebooted it I could > > > ssh back into the server etc. > > > I have a regular kernel and 1 jail and samba on this machine. > > > > I've been having this for a very long time, if the serial port does > > not realy exist - i don't know the technical wording for this -, > > > > if the kernel detected the sio hardare, but it's not realy > > wired, then it the kernel will hang when getty will try to open it. > > Per chance is the sio* device the kernel detects mapped to acpi0? :-) this all i can see, from dmesg: sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled and dmesg|grep acpi0 acpi0: on motherboard acpi0: Power Button (fixed) acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
Danny Braniss wrote: [...] Hey all, I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. This might just be a ports thing but on another 6.2 server I setup a jailed mail server with courier imap and I have noticed that it fails to build the courier-imap port with FAM support. I tried also installing the gamin FAM alternative which builds ok but I get signal 11 when I try to login to the imap server. Does anyone else have these problems? I've been having this for a very long time, if the serial port does not realy exist - i don't know the technical wording for this -, if the kernel detected the sio hardare, but it's not realy wired, then it the kernel will hang when getty will try to open it. danny OK good then its not just me, yes I haven't checked if the serial port is actually enabled in the bios, still I think its quite ordinary to have a machine basically fully hang up just because theres no active serial port. With no network or serial (unless you can enable/find it hardware side) I had to boot from the Freebsd install cdrom in fix it mode and mount the installed setup and revert the tty change. next time, just boot single user, do a fsck / then mount -u / at which point you will be able to fix /etc/ttys or any other screwup. danny Yeah for some reason I couldn't do that, I can't even remember all the reasons now but the main reason is because I have a USB keyboard, for some reason I can use the USB keyboard in the BIOS but as soon as the boot loader starts with the 10sec menu I loose all control of the keyboard. Booting into fixit mode from the CDROM loads the USB drivers (as well as not hanging up the OS anywhere) so I could mount the filesystem and fix it. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
On Wed, Sep 27, 2006 at 10:46:28AM +1000, Michael Vince wrote: > Yeah for some reason I couldn't do that, I can't even remember all the > reasons now but the main reason is because I have a USB keyboard, for > some reason I can use the USB keyboard in the BIOS but as soon as the > boot loader starts with the 10sec menu I loose all control of the keyboard. > Booting into fixit mode from the CDROM loads the USB drivers (as well as > not hanging up the OS anywhere) so I could mount the filesystem and fix it. I can confirm this problem, and have been fighting with it for quite some time. BIOS is configured for "USB Legacy" support (which should enable the keyboard in such environments). boot0, boot2, and loader all accept the keyboard just fine. Once the kernel loads, it loads the usb layer, detects the keyboard (via ukbd), and of course pops up the "Pick a shell" single-user prompt. But no keyboard input. This behaviour happened only on my Intel machine; my current AMD machine does not do this. The problem as I saw it (which may be an incorrect prognosis, since my AMD box says the same thing as the Intel via dmesg, but behaves fine) was that the FreeBSD kernel was considering the default keyboard device as atkbd* rather than ukbd*. It wasn't a problem outside of single-user, since usbd would load and do some magic to make it all work... but usbd doesn't get loaded in single-user. :-) The workaround I found was to use some loader.conf tweaks to disable specific AT/PS2 keyboard devices. I believe I used something like this, but I can't remember (and don't have loader.conf from my Intel box :( -- And yes, I know psm is for the mouse): hint.atkbdc.0.disabled="1" hint.atkbd.0.disabled="1" hint.psm.0.disabled="1" This oversight really needs to be addressed. I'll gladly buy anyone who wishes to solve it a new USB keyboard to test/debug with. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
On Tue, Sep 26, 2006 at 06:14:51PM -0700, Jeremy Chadwick wrote: > On Wed, Sep 27, 2006 at 10:46:28AM +1000, Michael Vince wrote: > > Yeah for some reason I couldn't do that, I can't even remember all the > > reasons now but the main reason is because I have a USB keyboard, for > > some reason I can use the USB keyboard in the BIOS but as soon as the > > boot loader starts with the 10sec menu I loose all control of the keyboard. > > Booting into fixit mode from the CDROM loads the USB drivers (as well as > > not hanging up the OS anywhere) so I could mount the filesystem and fix it. > > I can confirm this problem, and have been fighting with it for quite > some time. BIOS is configured for "USB Legacy" support (which should > enable the keyboard in such environments). boot0, boot2, and loader > all accept the keyboard just fine. Once the kernel loads, it loads > the usb layer, detects the keyboard (via ukbd), and of course pops > up the "Pick a shell" single-user prompt. But no keyboard input. > > This behaviour happened only on my Intel machine; my current AMD > machine does not do this. > > The problem as I saw it (which may be an incorrect prognosis, since > my AMD box says the same thing as the Intel via dmesg, but behaves > fine) was that the FreeBSD kernel was considering the default keyboard > device as atkbd* rather than ukbd*. It wasn't a problem outside > of single-user, since usbd would load and do some magic to make it > all work... but usbd doesn't get loaded in single-user. :-) > > The workaround I found was to use some loader.conf tweaks to disable > specific AT/PS2 keyboard devices. I believe I used something like > this, but I can't remember (and don't have loader.conf from my Intel > box :( -- And yes, I know psm is for the mouse): > > hint.atkbdc.0.disabled="1" > hint.atkbd.0.disabled="1" > hint.psm.0.disabled="1" > > This oversight really needs to be addressed. I'll gladly buy anyone > who wishes to solve it a new USB keyboard to test/debug with. Wasn't the kbdmux framework introduced some time ago to solve this? Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
On Tue, Sep 26, 2006 at 09:19:39PM -0400, Kris Kennaway wrote: > > This oversight really needs to be addressed. I'll gladly buy anyone > > who wishes to solve it a new USB keyboard to test/debug with. > > Wasn't the kbdmux framework introduced some time ago to solve this? I'm not familiar with this multiplexer driver. The manpage for it implied that configuring the driver requires kbdcontrol. /etc/rc.d/syscons controls this during multiuser boot, but nothing's going to call this for single-user. Seems like a catch 22 of sorts... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
On Sep 26, 2006, at 8:46 PM, Michael Vince wrote: Yeah for some reason I couldn't do that, I can't even remember all the reasons now but the main reason is because I have a USB keyboard, for some reason I can use the USB keyboard in the BIOS but as soon as the boot loader starts with the 10sec menu I loose all control of the keyboard. I have this issue with Sun X4100 when the keyboard is plugged into the front USB ports, but not when plugged into the rear USB ports. No clue why.
