Date: Wed, 6 Jun 2001 11:26:41 +0000 (GMT+00:00) From: auto245751@hushmail.com To: freebsd-questions@FreeBSD.ORG Subject: Intel 815E Graphics Chipset (was: RE: FreeBSD 4.2 Installation - Keyboard Problem + RANT) Message-ID: <200106061147.EAA19071@user8.hushmail.com>
next in thread | raw e-mail | index | archive | help
--Hushpart_boundary_aWtckyjdbaoQUuHoqtWlKeiMMxeTYffw Content-type: text/plain Ok, I have my keyboard problem fixed. I was dealing with a USB keyboard, not a PS/2 keyboard (my bad). The solution was to disable the "USB legacy support" in the BIOS, which I discovered today during some experimentation. What happens now is that the keyboard won't work when it has that booting in 10 seconds thing (enter key won't work), but it DOES work like a charm after the device probes, presumably because the FreeBSD code takes over. I can live with this. I now have FreeBSD 4.2-R installed, usbd is running nicely, the third mouse button is working (which is neat, cuz I couldn't get it working with my old mouse on 3.3-R), and I feel like the stick has been pulled out of my ass. Our new goal, boys and girls, is to get X working with my Intel 815E AGP graphics chipset. By the way, X fails to start if the securelevel is > - 1. I don't know if that's mentioned in the docs, but it can be very confusing considering that a security profile configuration can raise the securelevel. Someone may want to fix that. Anyway, awaiting suggestions for my Intel 815E graphics chipset. I'll mention it on an X newsgroup or something too. At Tue, 5 Jun 2001 23:54:12 -0700, "Ted Mittelstaedt" <tedm@toybox.placo.com> wrote: > >>-----Original Message----- >>From: owner-freebsd-questions@FreeBSD.ORG >>[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of >>auto245751@hushmail.com > >>>Have you tried a different keyboard just to see if it >>>would make a difference? Sometimes there's timing differences >>>I've seen this problem on other operating systems too. >> >>I would try that if I had a different keyboard to try. I have a >>5-pin keyboard, >> and the computer I'm installing to requires a 6-pin connector. > >I think what your saying here is you have a large DIN connector keyboard >and the computer your installing to has a mini-DIN connector on it. > I >assume you have an adapter from large-to-small keyboard, right? > >> Besides, >> I don't think it sounds right that I have to invest in a new >>keyboard just >>because FreeBSD 4.2, unlike every other fucking operating system (Windoze, >> Linux, OpenBSD, etc.), won't respond to my keyboard. > >I can assure you from experience that it's _not_ every other operating >system >that doesen't have this problem with some hardware out there. I've >personally >dealt with this problem on even plain old DOS when mixing-and-matching >keyboards, >and furthermore even the IBM OS/2 installation manual specifically states >that >certain motherboards will require keyboard bios upgrades to run OS/2, > if >your >looking for something more canonical than just FreeBSD PR's. > >>And knowing my luck, >>the new keyboard will fail to fix the problem. My current keyboard >works >>fine up until FreeBSD takes over and gives me the three choices at >>the "kernel >>configuration" screen. Then my keyboard stops working. WTF? >> > >I can tell you the problem but I can't tell you how to fix the code. > The >problem >is that FreeBSD doesen't use BIOS for talking to the keyboard, it loads >a >device driver that speaks to the keyboard controller chip on the motherboard >directly. Your motherboard/keyboard controller/keyboard combination >is thus >running under "different" code when you just boot DOS or are still on >the >BIOS's POST. > >I've ALSO seen this problem on ONE other instance - setting incorrect >voltage >or clocking speed on the CPU. If the CPU is using the wrong clock >multiplier >or clock then it can make the keyboard not talk to the motherboard under >different operating systems. > >In your case it's a "difference of opinion" between the hardware you >have >and the keyboard device driver's idea of how to interface with the keyboard >controller chip/keyboard combination. I wouldn't go so far as to call >it a >bug, >but I recognize that it's a problem for a few installations. > >>Just run a search through http://groups.google.com and see how many >other >>people are encountering this same problem. I noticed someone wrote >a PR >>for this too. They, like I, are receiving a blind eye from the so-called >>"freebsd community". >> > >A developer cannot fix what they don't have in front of them - it's >been >years >since I've seen this problem myself and obviously the keyboard driver >author >has never seen it. I'm sure you have better things to do than pack >up your >system and freight it off to the developer. I find it hard to believe >that >you don't have a friend with a computer that you can't swap the keyboard >with just for testing, or couldn't you take the keyboard to work and >swap >it with a system there? It's only a keyboard for goodness sake. Any >network >server farm that uses keyboard switches has boxes of the things collecting >dust. > >>A suggested fix was to disable 0x1 in the flags for atkbd. Could >>the genius >>who came up with this solution please explain HOW TO DO THIS DURING >THE >>__INSTALLATION__. >> > >Obviously you can't. Normally, when booting the install asks if you >want to >make changes, you would select yes, then in the visual configurator >select >Input, then Keyboard, then tab to the flags and change it there. But >if >your keyboard is >dead then you can't do this. > >>For fuck's sake... you'd think this problem would be resolved by now. >> > >Just to be nice because your obviously upset I went and reviewed the >keyboard >PR's and there _has_ been work done on this. But, understand that the >0x1 >option >was stuck in there to fix a problem people were complaining about - >it >apparently >fixed the problem then caused problems for others. There's also a mention >that >increasing the probe length fixed at least one person's problem. See >PR >i386/17391 > >The 0x1 flag thing was put in there after FreeBSD 4.0. One enterprising >user >installed 4.0, then upgraded to a later version and recompiled the OS. > See >PR i386/20495 > >Just to see if it would help you, I have put up the boot images for >the >floppies >for 4.0 here: > >http://www.freebsd-corp-net-guide.com/software/KERN.FLP >http://www.freebsd-corp-net-guide.com/software/MFSROOT.FLP > >Make them and see if you can boot into the installer and move about >in it. >If so, then submit a followup to PR i386/20495 and one to PR i386/17391 >and let us know. If you ask nice someone can probably make a boot floppy >for you with the 0x1 option shut off. > > >Ted Mittelstaedt tedm@toybox.placo.com >Author of: The FreeBSD Corporate Networker's Guide >Book website: http://www.freebsd-corp-net-guide.com > Free, encrypted, secure Web-based email at www.hushmail.com --Hushpart_boundary_aWtckyjdbaoQUuHoqtWlKeiMMxeTYffw-- IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106061147.EAA19071>