Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 06:53:51PM -0800, Mike Smith wrote: The only argument for having a dysfunctional hostname of the variety you describe is vanity, which is not a valid engineering constraint. Or that you're behind a dialup connection that dynamically assigns IPs. -- Giorgos Keramidas, keramida @ ceid . upatras . gr "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Keyboard problem (was: Re: Problems installing FreeBSD 4.0 20000125-CURRENT)
Ok, guys.
This is another patch for the atkbd driver. I expect this one is
better than my previous one. Remove the previous patch and try this
one instead. Stress the keyboard (like hitting the Return key twice
when booting the system), and see if it works.
Thank you.
Kazu
I have on a number of occasions had my laptop boot with a
non-functional keyboard. Sometimes the keyboard is just locked; other
times it generates garbage. Never managed to isolate the
circumstances in which this happened (but it didn't happen with a
kernel from last September or there-abouts). Haven't had it happen on
a desktop or server yet.
I have seen this on numerious occasion, but have never tracked it down
to any one specific thing. All on desktop and servers, but thats
only because we don't do laptops.
I have not seen it in quite some time (about a month), so I am thinking
it has probably been unknowingly fixed someplace. I'll keep an eye
out for it.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
Index: atkbd.c
===
RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v
retrieving revision 1.22
diff -u -r1.22 atkbd.c
--- atkbd.c 2000/01/20 13:32:53 1.22
+++ atkbd.c 2000/01/28 02:11:50
@@ -1084,8 +1097,11 @@
return ENXIO;
}
+ /* temporarily block data transmission from the keyboard */
+ write_controller_command(kbdc, KBDC_DISABLE_KBD_PORT);
+
/* flush any noise in the buffer */
- empty_both_buffers(kbdc, 10);
+ empty_both_buffers(kbdc, 100);
/* save the current keyboard controller command byte */
m = kbdc_get_device_mask(kbdc) ~KBD_KBD_CONTROL_BITS;
@@ -1133,8 +1148,11 @@
return EIO;
}
+ /* temporarily block data transmission from the keyboard */
+ write_controller_command(kbdc, KBDC_DISABLE_KBD_PORT);
+
/* save the current controller command byte */
empty_both_buffers(kbdc, 200);
c = get_controller_command_byte(kbdc);
if (c == -1) {
/* CONTROLLER ERROR */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thursday, 27th January 2000, "Rodney W. Grimes" wrote: On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. I have seen this on numerious occasion, but have never tracked it down to any one specific thing. All on desktop and servers, but thats only because we don't do laptops. I have not seen it in quite some time (about a month), so I am thinking it has probably been unknowingly fixed someplace. I'll keep an eye out for it. I had this problem on several machines back around version 3.2. I assumed it was a problem between X11 and the keyboard driver. I added a 2 second delay before starting xdm and had no problems after that. I've not seen the problem without X11 being involved. I admit I just forgot about it after I got my workstation going. :-( Stephen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 18:53:51 -0800, Mike Smith [EMAIL PROTECTED] said: Since the hostname is simply a plain-text token for the IP address Wrong. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Kazutaka YOKOTA wrote: I have had reports on similar lockup in both 4.0-CURRENT and 3.X. I personally have not been able to reproduce it, but now my new sand box machine exhibits this problem occasionally. The I/O access to the AT keyboard by the atkbd driver have not changed much for the last couple of years, despite massive source tree reorganization. And yes, problem reports started to pop-up since sometime around the last summer. I have not been able to track down the cause of the problem, but am suspecting possibility of the clock/timer problem. It happens with me from time to time. It is NOT related to kernel, since it happens between boot0 and boot2. It will happen when I'm typing something during boot, so it's probably some sort of race. Symptons include keys having weird mappings, and some keys not mapping to anything at all, after boot. At boot2/loader, no keypress is recognized at all. Very rare. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "2 b or not to b" meaning varies depending on whether one uses the 79 or the 83 standard. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems installing FreeBSD 4.0 20000125-CURRENT
Hi, I installed 4.0 2125-CURRENT last night on a new box, and had several problems that I wanted to share: 1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone into the options menu and selected "DHCP"; when I picked my network interface it looked for and found a DHCP server and popped up the network configuration box with most of the fields filled in (including domain name); all I did was type in a hostname. sysinstall then added the domain name to the host name and I said "OK", but that hostname never made it into rc.conf (it booted up calling itself Amnesiac). 2. motd was full of garbage. I realize now that I should have saved it but I wasn't really thinking. 3. On the first reboot after installing, the keyboard was in a funny state. Some keys would provide multiple characters, some would do none. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I used the expert install and picked the "Install everything" option so I assumed I'd get everything =) On the plus side, being able to use DHCP rocks, and I really like how it installed the Linux packages when I picked Linux emulation. And 4.0 seems to work well with this random hardware (emachine 400), including the onboard sound and random ethernet card (linksys something). Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone into the options menu and selected "DHCP"; when I picked my network interface it looked for and found a DHCP server and popped up the network configuration box with most of the fields filled in (including domain name); all I did was type in a hostname. sysinstall then added the domain name to the host name and I said "OK", but that hostname never made it into rc.conf (it booted up calling itself Amnesiac). In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname field since our dhcp client integration is still a bit green and you'll just override the DHCP server assignment for the hostname with the user-defined one if it's written to rc.conf. 2. motd was full of garbage. I realize now that I should have saved it but I wasn't really thinking. Huh? 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. Ugh, either option is pretty ugly. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On 27-Jan-2000 Jordan K. Hubbard wrote: | | 3. On the first reboot after installing, the keyboard was in a funny | state. | | Urk, can't reproduce it. I need a reproducible sequence of operations | before we'll have any hope of tackling this one. | | Control-alt-del definitely didn't work, so I had to power off and | reboot. This hasn't repeated itself. | | Same here. | I seem to have this problem occasionaly, the keyboard keymap gets all screwed up somehow, and the only way to get out is to hit the reset button. But I've been having the problem for a long time, and with different boxes. It happens about every 1 out of 15 reboots but randomly. I haven't been able to connect it to any event or anything, but I notice that hitting keys during boot can increase the probability of it occurring, but again, nothing reproducible. - Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA ICQ# 882073 Date: 27-Jan-2000 Time: 16:47:01 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
% %On 27-Jan-2000 Jordan K. Hubbard wrote: % | % | 3. On the first reboot after installing, the keyboard was in a funny % | state. % | % | Urk, can't reproduce it. I need a reproducible sequence of operations % | before we'll have any hope of tackling this one. % | % | Control-alt-del definitely didn't work, so I had to power off and % | reboot. This hasn't repeated itself. % | % | Same here. % | % %I seem to have this problem occasionaly, the keyboard keymap gets all screwed %up somehow, and the only way to get out is to hit the reset button. But I've %been having the problem for a long time, and with different boxes. It happens %about every 1 out of 15 reboots but randomly. I haven't been able to connect %it to any event or anything, but I notice that hitting keys during boot can %increase the probability of it occurring, but again, nothing reproducible. Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. Russell %- %Mike Heffner [EMAIL PROTECTED] %Fredericksburg, VA %ICQ# 882073 %Date: 27-Jan-2000 Time: 16:47:01 %- % % %To Unsubscribe: send mail to [EMAIL PROTECTED] %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Garrett Wollman wrote: I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman I've seen this on a Compaq Armada laptop recently (-current from about 1/10/2000). It only happens when I interrupt the boot process with a key press (I cannot recall whether it was in /boot/loader or in boot2). I suspect the latter, but have not yet tracked the problem down. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Garrett Wollman wrote: On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman As another sort of me-to, I use a non-standard key board from an ols lunch-box portable. It seems to have stopped working correctly in the boot-loader/visual config, although it still works fine in single-user and above. I mention this only in that it might be a useful data point, it has never been enough of a hassle for me to try to understand exactally what is going on, I just hook up a spare 101-key keyboard. Brian Beattie| The only problem with [EMAIL PROTECTED] | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. If you want the added to src/lib/compat, let me know ASAP. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. OR we can make a [binary] port of it. This would not be hard to do. Let me know if you prefer this approach. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Bill Fenner wrote: Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill Hmmm, I wonder it the boot loader is doing something funny in initializing the keyboard. Maybe something changed? Brian Beattie| The only problem with [EMAIL PROTECTED] | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Garrett Wollman wrote: On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman Yeah, happens here too, every now and again. I boot straight into xdm, so it might have something to do with X, but any attempts to type in the username generate garbage. I can't switch to a text console, because Ctrl-Alt-Fx keys don't work either - all I can do is push the Big Red Button. The graphics card in my laptop is Chips Technology 6. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Bill Fenner wrote: Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill Hmmm, I wonder it the boot loader is doing something funny in initializing the keyboard. Maybe something changed? It doesn't do anything to the keyboard, it just calls the BIOS to find out whether keys have been pressed. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On 27-Jan-00 David O'Brien wrote: On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Why not check to see what the hostname is after dhclient is run and then stick that name in the network setup dialog box. If the user does edit the hostname themselves, then you can flag that event, and use that flag when writing out /etc/rc.conf to mean that the hostname variable should be set. Actually, this doesn't work all that well because the boot floppy doesn't include /bin/hostname in the crunch so /sbin/dhclient-script can't set the hostname when it is sent out by a dhcp server. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. If you want the added to src/lib/compat, let me know ASAP. -- -- David([EMAIL PROTECTED]) -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "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: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit CR twice fast problem for months. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit CR twice fast problem for months. It's always been a problem; we don't understand the mechanics of it however. Susceptibility varies widely between systems, and the best hypothesis I've been able to come up with is that there are issues with taking interrupts in vm86 mode; possibly the BIOS is being re-entered in a fashion it doesn't like. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. If we were to fix that in our rc scripts, I could remove this assumption in sysinstall in good conscience. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : In message [EMAIL PROTECTED] Mike Smith writes: : : It doesn't do anything to the keyboard, it just calls the BIOS to find : : out whether keys have been pressed. : : I've been seeing the hit CR twice fast problem for months. : : It's always been a problem; we don't understand the mechanics of it : however. Susceptibility varies widely between systems, and the best : hypothesis I've been able to come up with is that there are issues with : taking interrupts in vm86 mode; possibly the BIOS is being re-entered in : a fashion it doesn't like. Just wanted to make sure you acknowledged the problem. It sounded like you were saying that it wasn't a problem at all rather than the theory put forward wasn't likely the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. If we were to fix that in our rc scripts, I could remove this assumption in sysinstall in good conscience. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Why not check to see what the hostname is after dhclient is run and then stick that name in the network setup dialog box. If the user does edit the hostname themselves, then you can flag that event. That would work in that one specific case with that specific dhcp server. Now change the dhcp server post-install time and watch what happens. :-) What is clearly needed is some idea of "fallback hostname" vs the one you *might* be automatically assigned by "something else" (one current value for something else being DHCP) and should probably use preferentially. Split the hostname into two variables and do the appropriate rc dance magic, off ya go. Of course, this also fails to address a more fundamental failing in our rc scripts, this being that the concept of "network identity" is currently handled in too simplistic a fashion. When dealing with the "local vs on the road" scenario, many laptop users (including myself) end up hand-editing their rc.conf files or adding some cheesy menu to the rc files which say, in effect, "choose one of the following canned configurations" and then go work the appropriate variable-setting magic. The fact that I've seen so many people re-invent this particular wheel also sends a strong hint that a better, more general, mechanism is now overdue. As the original architect of FreeBSD's rc.conf (nee /etc/sysconfig) mechanism, I can also say with some assurance that it's reached its limits. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. I have had reports on similar lockup in both 4.0-CURRENT and 3.X. I personally have not been able to reproduce it, but now my new sand box machine exhibits this problem occasionally. The I/O access to the AT keyboard by the atkbd driver have not changed much for the last couple of years, despite massive source tree reorganization. And yes, problem reports started to pop-up since sometime around the last summer. I have not been able to track down the cause of the problem, but am suspecting possibility of the clock/timer problem. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
I seem to have this problem occasionaly, the keyboard keymap gets all screwed up somehow, and the only way to get out is to hit the reset button. But I've been having the problem for a long time, and with different boxes. It happens about every 1 out of 15 reboots but randomly. I haven't been able to connect it to any event or anything, but I notice that hitting keys during boot can increase the probability of it occurring, but again, nothing reproducible. If you hit any key while the keyboard driver is trying to initialize the keyboard, there is a good possibility that the driver will be screwed. But, it mustn't show problems if you hit the keyboard during the boot loader or after the driver is attached... Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit CR twice fast problem for months. It's always been a problem; we don't understand the mechanics of it however. Susceptibility varies widely between systems, and the best hypothesis I've been able to come up with is that there are issues with taking interrupts in vm86 mode; possibly the BIOS is being re-entered in a fashion it doesn't like. I wonder if the keyboard interrupt is blocked for a prolonged period in the boot loader because of vm86, and quite a number of (up to 16 or something) scan codes are waiting in the keyboard to be received by the host computer, when the kernel is loaded. The keyboard driver atkbd tries to flush pending scan codes, left over from the boot loader, before it starts initializing the keyboard. It may be failing to flush all the pending scan codes if there are too many of them. The following patch will make the driver wait slightly longer to flush inputs. I would like to see if this makes any difference. I should come up with something better this, though... Kazu Index: atkbd.c === RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v retrieving revision 1.22 diff -u -r1.22 atkbd.c --- atkbd.c 2000/01/20 13:32:53 1.22 +++ atkbd.c 2000/01/28 00:47:27 @@ -1085,7 +1098,7 @@ } /* flush any noise in the buffer */ - empty_both_buffers(kbdc, 10); + empty_both_buffers(kbdc, 200); /* save the current keyboard controller command byte */ m = kbdc_get_device_mask(kbdc) ~KBD_KBD_CONTROL_BITS; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 16:06:31 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. However, there is no need to actually use the configured hostname for this purpose. `temp-4224.lcs.mit.edu' is just that, temporary -- I want my machine to know what its *real* identity is. From my perspective, when I'm installing a FreeBSD machine, the DHCP client option serves only to quick-start the installation -- the machine will eventually have a real address. It would be useful to me if sysinstall paid attention to the hostname I specified the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. You have your mail server set to ``authenticate'' based on the HELO? That's the only thing in the SMTP protocol that the kernel's hostname setting has any impact on. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 16:06:31 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. However, there is no need to actually use the configured hostname for this purpose. `temp-4224.lcs.mit.edu' is just that, temporary -- I want my machine to know what its *real* identity is. From my perspective, when I'm installing a FreeBSD machine, the DHCP client option serves only to quick-start the installation -- the machine will eventually have a real address. It would be useful to me if sysinstall paid attention to the hostname I specified That's not correct; your DHCP configuration should reflect the hostname. Sysinstall doesn't fill in the hostname field because the crunched binary is missing the hostname(1) command. If we were to add that, it's just possible that we'd get hostnames working too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 04:06:31PM -0800, Jordan K. Hubbard wrote: IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. Not at all. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. I will state unequivocally that most DHCP clients use a local mail relay. And the local relay will use a "generic" hostname on the email address. Also, the DNS "name" has nothing to do with the host's name. The sites DNS admins will have both forward and reverse (A PTR) RR's. Also I will state in large shops, they don't hardcode IPs to particular machines. Thus over time a machine has many different IPs. People would not be too happy to see their hostnames change all the time, nor to be the typical "foo-bar-dhcp-134-89" that the assigned IP will resolve to. In a Winloose network, they don't care about matching machine names with DNS hostnames. This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) Yes, this behavior is ISC's ruled desire. From experience Ted Lemon and Co. knows that most shops don't handout hostnames, and when they do they are long nonsensical ones. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
That's not correct; your DHCP configuration should reflect the hostname. Sysinstall doesn't fill in the hostname field because the crunched binary is missing the hostname(1) command. If we were to add that, it's just possible that we'd get hostnames working too. Actually, that's not quite true and hasn't been for awhile now: jkh@highwing- grep hostname /usr/src/release/*conf* /usr/src/release/boot_crunch.conf.generic:progs dhclient arp hostname - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. Quite sure. I have several machines installed with the 26th snapshot that aren't setting the hostname correctly. You were present when the hostname issuing from the server problem was fixed, and the clients were still not picking them up then. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. Correct behaviour would be not to set the hostname unless: a) it is not already set or b) it was previously set by the DHCP client You could probably ignore b) and satisfy most people. At the moment, the hostname is _never_ set by the DHCP client _unless_ it finds a lease that is still valid. This is clearly a bug. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
That's not correct; your DHCP configuration should reflect the hostname. Sysinstall doesn't fill in the hostname field because the crunched binary is missing the hostname(1) command. If we were to add that, it's just possible that we'd get hostnames working too. Actually, that's not quite true and hasn't been for awhile now: jkh@highwing- grep hostname /usr/src/release/*conf* /usr/src/release/boot_crunch.conf.generic:progs dhclient arp hostname In that case I can only assume that the dhclient-script is looking for it in the wrong place. The last snap I installed was around the 25th and it still failed to pick up the hostname. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Bill Fenner wrote: Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Yup I've seen this too on my trusty Micron. I've found that hitting space, to get to the forth prompt, and then typing boot and then thwacking enter is a sure fire way to get it to boot correctly. Hitting enter twice in a row quickly occasionally screw up. Also sometimes I'll be able to catch the screwed up booter when I notice that it doesn't respond to me hitting enter (In 9 seconds... hit enter.. 8 seconds.. hit enter.. 7 seconds... hit reset). - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 18:11:52 -0800, Mike Smith [EMAIL PROTECTED] said: That's not correct; your DHCP configuration should reflect the hostname. No, it shouldn't. As I keep on trying to explain, the DHCP addresses are: 1) Temporary. 2) Meaningless. 3) Temporary. 4) Temporary. 5) Temporary. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 18:11:52 -0800, Mike Smith [EMAIL PROTECTED] said: That's not correct; your DHCP configuration should reflect the hostname. No, it shouldn't. As I keep on trying to explain, the DHCP addresses are: 1) Temporary. 2) Meaningless. 3) Temporary. 4) Temporary. 5) Temporary. Since the hostname is simply a plain-text token for the IP address, it has to remain bound to the IP address (whether that binding is fixed or dynamic is outside the scope of this discussion). Having a hostname that doesn't map to your IP address is a misconfiguration, and not a useful one at that. The only argument for having a dysfunctional hostname of the variety you describe is vanity, which is not a valid engineering constraint. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 09:26:44PM -0500, Garrett Wollman wrote: On Thu, 27 Jan 2000 18:11:52 -0800, Mike Smith [EMAIL PROTECTED] said: That's not correct; your DHCP configuration should reflect the hostname. No, it shouldn't. As I keep on trying to explain, the DHCP addresses are: ^^ usually 1) Temporary. 2) Meaningless. 3) Temporary. But if one does not specify a hostname in sysinstall with the intention of having DHCP hand it out and it be used; then I do have a bug to fix. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 06:22:55PM -0800, Mike Smith wrote: Correct behaviour would be not to set the hostname unless: a) it is not already set or b) it was previously set by the DHCP client You could probably ignore b) and satisfy most people. At the moment, the hostname is _never_ set by the DHCP client _unless_ it finds a lease that is still valid. This is clearly a bug. Agreed. I will happily accept a patch anybody that got to this before I manage do. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 06:53:51PM -0800, Mike Smith wrote: Since the hostname is simply a plain-text token for the IP address, it has to remain bound to the IP address (whether that binding is fixed or dynamic is outside the scope of this discussion). Having a hostname that doesn't map to your IP address is a misconfiguration, and not a useful one at that. My system has two ethernet cards, and two IP addresses. One of these is assigned by DHCP and the other is fixed, on my local network. I prefer for my hostname to relate to the local address. Just another data point. -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message Pine.BSF.4.21.0001271819180.247-10@localhost Alex Zepeda writes: : in a row quickly occasionally screw up. Also sometimes I'll be able to : catch the screwed up booter when I notice that it doesn't respond to me : hitting enter (In 9 seconds... hit enter.. 8 seconds.. hit enter.. 7 : seconds... hit reset). I've also seen this on my laptop from time to time. Half the time when this happens, the scan codes are all messed up once I get to multi-user. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Garrett Wollman writes: : On Thu, 27 Jan 2000 18:11:52 -0800, Mike Smith [EMAIL PROTECTED] said: : : That's not correct; your DHCP configuration should reflect the hostname. : : No, it shouldn't. As I keep on trying to explain, the DHCP addresses : are: : : 1) Temporary. : 2) Meaningless. : 3) Temporary. : 4) Temporary. : 5) Temporary. That reminds me. sysinstall *SHOULD*NOT* hard code the IP address that it gets from dhcp into rc.conf. I've seen this in 3.2, but haven't tried since then to reproduce this. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
That reminds me. sysinstall *SHOULD*NOT* hard code the IP address that it gets from dhcp into rc.conf. I've seen this in 3.2, but haven't tried since then to reproduce this. It doesn't do that anymore; it was a nasty hack to work around not having been able to sell BPF in the kernel in time for 3.2. Now that it's in GENERIC, we can run the DHCP client after installation. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : That reminds me. sysinstall *SHOULD*NOT* hard code the IP address : that it gets from dhcp into rc.conf. I've seen this in 3.2, but : haven't tried since then to reproduce this. : : It doesn't do that anymore; it was a nasty hack to work around not having : been able to sell BPF in the kernel in time for 3.2. Now that it's in : GENERIC, we can run the DHCP client after installation. Glad to hear it. One less thing to double check before the release... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. I have seen this on numerious occasion, but have never tracked it down to any one specific thing. All on desktop and servers, but thats only because we don't do laptops. I have not seen it in quite some time (about a month), so I am thinking it has probably been unknowingly fixed someplace. I'll keep an eye out for it. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On 28-Jan-00 Warner Losh wrote: In message [EMAIL PROTECTED] Garrett Wollman writes: : On Thu, 27 Jan 2000 18:11:52 -0800, Mike Smith [EMAIL PROTECTED] said: : : That's not correct; your DHCP configuration should reflect the hostname. : : No, it shouldn't. As I keep on trying to explain, the DHCP addresses : are: : : 1) Temporary. : 2) Meaningless. : 3) Temporary. : 4) Temporary. : 5) Temporary. That reminds me. sysinstall *SHOULD*NOT* hard code the IP address that it gets from dhcp into rc.conf. I've seen this in 3.2, but haven't tried since then to reproduce this. Warner It doesn't do this on 3.3 or 3.4. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "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: Problems installing FreeBSD 4.0 20000125-CURRENT
On 28-Jan-00 Mike Smith wrote: On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. Quite sure. I have several machines installed with the 26th snapshot that aren't setting the hostname correctly. You were present when the hostname issuing from the server problem was fixed, and the clients were still not picking them up then. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. Correct behaviour would be not to set the hostname unless: a) it is not already set or b) it was previously set by the DHCP client You could probably ignore b) and satisfy most people. At the moment, the hostname is _never_ set by the DHCP client _unless_ it finds a lease that is still valid. This is clearly a bug. Uh, no. It is set ok on the initial bootup. The lab of 30 or so FreeBSD machines I run at school use DHCP to get their hostnames and the current dhclient-script works perfectly: [0:28:21] (ttyp2) jobaldwi@raspberry:~ grep hostname /etc/rc.conf hostname="" [0:28:27] (ttyp2) jobaldwi@raspberry:~ grep host-name /var/db/dhclient.leases option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "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
