In article <1992Nov2.162544.9239@news.uit.no>, johnm@stud.cs.uit.no (John Markus Bjoerndalen) wrote:I've got a Compudyne 486DX/33 (8/120) that does this nicely. This machine is basically the Twinhead SlimNote that is sold by a bunch of different companies these days. You mostly get to pick the company you like and the color of the case ;-) .... The 486 DX notebook category is growing though, and there may be even more powerful, better machines these days. I can use Xmono at 640 x 480 with a virtual desktop of 800 x 600. I have not tried to do anything with the external video, either in mono or color. Has anyone done this with a notebook? Anything to report...? I too had problems with the trackball at first. Linux 0.98.3 solved all my troubles though. (I feel I should mention that because lots of people have been reporting that all of a sudden their X and/or their mouse and/or their serial ports broke when going to 0.98.3, but that it *was* a *big* improvement in these areas for some others of us....) The inbuilt trackball on the Compudyne is also PS/2-like. Methinks that you should probably do what I did and try out 0.98.3 (plus the two little emergency patches). (I'm not sure from the previous paragraph -- maybe you *are* using 0.98.3 already, in which case ignore that last sentence.) You must have a suitable /dev/psaux (do "mknod /dev/psaux c 10 1") and /dev/mouse (or /dev/trackball if you want to hook up an external mouse and call it /dev/mouse) (do "mkfifo -m 666 /dev/trackball"). You should copy Xconfig.mono to Xconfig and edit that as you experiment. Your trackball should be the microsoft type and it is at either /dev/trackball or /dev/mouse as you decided above. I just deleted the vga256 section altogether. You say your trackball was detected and that you can get data from it. I presume you mean that you can get data from it with the little "mouse" program in the tst directory. If you look closely you will note that the data you get from it doesn't make much sense. Check out the dx, dy, and button values you get when you move the trackball or click the buttons. Yeah, they're pretty screwy.... Now you need the little mconv program that Johan Myreen posted here a couple of weeks ago. It should be findable on an ftp site. You will need to start up mconv with "mconv /dev/psaux /dev/trackball &". Now test the mouse program. The values should look more reasonable (i.e., the y axis seems upside-down, but the rest makes sense...). Now you can try startx, and hopefully everything will be ok. You should probably put the mconv command in your /etc/rc.local or something like that. *If you do, BE SURE NOT TO FORGET THE &!!!* This is pretty easy to forget, as Johan noted that he did at first, and I did too at first (yes, despite his warning). Oops.... Best of luck...! Anxious to hear reports of other notebook Linux users! Conrad C. Nobili N1LPM Conrad_Nobili@Harvard.EDU Harvard University OIT
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Linus Torvalds | Linux 2.6.25-rc4 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Andrew Morton | 2.6.23-rc6-mm1 |
git: | |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
| Radu Rendec | htb parallelism on multi-core platforms |
