Date: Fri, 03 Jan 2003 18:35:02 -0500 (EST) From: "J. Seth Henry" <jshenry@comcast.net> To: questions@FreeBSD.ORG Cc: jcoombs@gwi.net Subject: Re: questions-digest V5 #1820 Message-ID: <20030103181226.A63622-100000@whitetower.gambrl01.md.comcast.net> In-Reply-To: <bulk.97388.20030103143308@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I have a command line utility that handles the lights for now, but I'm still working on shoehorning the business end into the blanksaver. I didn't have a development system over the holidays, but I plan to make another go of it this weekend. I can email you the C source for the current program, though - it's not terribly complicated. Right now, I have scripts that turn the green (power) light on during the boot sequence, and I *almost* have an X server that handles the extra keyboard/LED's. It translates the "function" buttons as F1-F10, F13 - remaps the volume/mute buttons as 147,148,149. The arrow keys are simply mapped as, well arrow keys. I thought about having them produce "ALT+RIGHT/LEFT", but I find I use them on the command line as well. Lastly, the "PRINTER" button is now an "ESCAPE" key. I really wish I could get xmodmap to recognize higher scancodes... Lastly, the power button currently calls an empty function that will toggle the screen backlight on and off. I'm still working out how this should work with the blanker, but I get the feeling it won't be a big deal. I hard-coded most of this in a modified Xfree86 3.3.6 SVGA server. 3.3.6 uses *FAR* less RAM than 4.x does, but it doesn't natively handle keycodes above 150. I have tried mucking with the 3.x version of xmodmap, but I can't make it see scancodes over 150 - even when the X server clearly generates them (I can see them using xev). Otherwise, I would simply have the server generate high value scancodes, and use Xmodmap to remap. Can't have it all, I suppose. I find I have ~4Mb of free RAM after everything is up on this testbed system. (I was swapping heavily with 4.1.2) BTW - I have a good XF86Config for 3.3.6. 800x600@16bit color. It's trimmed down to just the basics, but it works quite well. If I could just get xdm to work! ARGHH - no one on the list seems to know how to set up xdm at all, much less for remote logins. At least xfs is working, so I still get pretty fonts in applications. Once I get xdm licked, I'll be a long ways towards my dedicated x terminals. Anyway, once I get all the code finished, I'll be more than happy to share. The entire OS fits on a 340MB microdrive with nearly 50Mb to spare. Seth Henry >>> Date: Fri, 3 Jan 2003 12:53:45 -0500 From: "Joshua Coombs" <jcoombs@gwi.net> Subject: Re: 5.0RC2 on an iPaq IA1 Mine's a white unit, no onboard ethernet. The only bus powered device I'm running right now is the aue ethernet, which I can easily dump for testing. The HD is self powered. I'd love a microdrive, but figured I had this 60GB IDE drive floating loose, and the enclosure/adapter was only $35... might as well try right? : ) Previously I've been netbooting but getting ticked with random locks under load, under both Net and FreeBSD. No warning, no errors just stops dead in it's tracks. Figured getting 'local' storage might stabilize things. Have you gotten the backlight control code ported over to FreeBSD for these rigs? I'd love to have a screensaver module that just shut the LCD down. Joshua Coombs - ----- Original Message ----- From: "J. Seth Henry" <jshenry@comcast.net> To: <freebsd-questions@freebsd.org> Cc: <jcoombs@gwi.net> Sent: Friday, January 03, 2003 10:25 AM Subject: RE: 5.0RC2 on an iPaq IA1 > Don't rule out hardware problems. I have been working with 4.7R on an > IA-1. The power supplies in there aren't the greatest, and I've had > problems with wireless keyboards loading the units down to where they had > problems booting. > > I would suggest you get a self-powered USB hub, and make all your > connections through it (or try one of those keychain NAND drives). I > managed to get everything, including the wireless keyboard transciever, to > work just fine that way. > > That said, I've had the most success with booting my IA-1 from a > microdrive. I did have to boost the CF Vcc to 5V by lifting and jumpering > the middle two pins to an unused serial connector (CN10), but that done, > the system is remarkably stable. > > BTW - is your IA-1 a white or blue unit? I'm still trying to figure out > how to get FBSD to recognize the external MII PHY on the clipper ethernet > port. > > Good luck, > Seth Henry > > >>> > iPaq# usbdevs -v > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), > VIA(0x0000), rev 1.00 > port 1 powered > port 2 addr 2: full speed, self powered, config 2, USB 2.0 Storage > Adaptor(0xb001), DMI(0x0c0b), rev 11.10 > Controller /dev/usb1: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), > VIA(0x0000), rev 1.00 > port 1 powered > port 2 addr 2: full speed, power 156 mA, config 1, LINKSYS USB > Adapter(0x400b), LINKSYS Inc.(0x066b), rev 1.01 > > Suggestions on how to debug or reduce the errors? The drive has good > media > (hooked direct to IDE it tests clean using Quantum's diag util) and the > system will boot fine with a warm reboot of the comp itself, so I'm > guessing > the problem is driver related and not a fault with the HW. > > Joshua Coombs > jcoombs@gwi.net 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?20030103181226.A63622-100000>