📜 ⬆️ ⬇️

NetBSD / hpcmips

Recently, a review of the vintage NEC MobilePro 790 keyboard handheld caused a very lively discussion. But on the whole, the device is now useless due to an extinct operating system. You can try to get around this obstacle. Yes, we put NetBSD.
image
(c) Not mine


Training


A NetBSD / hpcmips 6.0.1 system will be placed on the CF card. At hand was one of 4 GB, that's enough with his head. The card can be placed either in its native slot, or in the adapter on PCMCIA - there is no difference. The sequence is approximately as follows: the backup is all over ActiveSync, because the contents of the RAM are lost, installing the kernel, installer and bootloader into the onboard flash - it is not overwritten upon reboot, take care of the installer access to the packages - there are options. The installer offers a choice to download from the official repository, FTP, from somewhere else such as NFS or from a disk partition. Initially, I intended to download directly via PCMCIA WiFi. The network picked up without the slightest problem, but then multiple unpacking errors went. I did not want to mess around, I wrote off a buggy Chinese router, so I uploaded all the packages to the card section from here: ftp.netbsd.org/pub/NetBSD/NetBSD-6.0.1/hpcmips/binary/sets . It did not help, errors remained. I can not say what it is connected with - the card is good and works with other devices without errors. Further installation had to be carried out on the GXEmul emulator. In general, a flash drive with such a scheme should be divided into two sections - into one package and, if necessary, the bootloader with all that is necessary, the second should be left empty and not broken - NetBSD will divide it into subsections during installation.

Installation


We need the pbsdboot.exe bootloader and the netbsd.gz kernel / installer from here: ftp.netbsd.org/pub/NetBSD/NetBSD-6.0.1/hpcmips/installation . It also makes sense to put a core nearby, in the unpacked form. We throw in the flash or on the FAT-section of the card. The manual recommends a newer hpcboot bootloader, but it did not work for me.
')


In the bootloader, you must specify the full path to the installer, it will look like / Internal Flash ROM / bsd / netbsd.gz, and the framebuffer parameters in the drop-down list. When you click on the Boot, the kernel starts to boot. The process is slow, takes minutes 3. This will end with the appearance of the installer. After an obvious choice of language there will be a not so obvious approach to the console for the names of the disk partitions.


Here you have to select “Utility”, then “Run / bin / sh” and execute disklabel wd0 .



The section with packages must be remembered, it will be a type name wd0e. We will need it later when specifying the source of the packages. Further actions are generally very obvious to a person who has ever installed at least Linux. Small difficulties caused except that the partitioning of the disk. NetBSD takes one partition and splits it into /, swap, and so on. It was unusual.

Job


After restarting the installer-> WinCE-> bootloader with the kernel from the package, we get the root console, there is no default password. The system is loaded for several minutes. The longest stage is the update fontconfig.



Memory in a freshly loaded system is free somewhere around 8-9 MB out of cash 32 minus a little bit. And then, honestly, there is no it - this work. X does not start. And in the emulator work. I am writing off some problems with wscons, the console and framebuffer driver. And maybe with the equipment. But all attempts to pull the available strings to success did not lead. On the emulator it looks like this:


Gxemul


Oddly enough, there is a very good emulator of this machine - GXEmul. Not all of it is emulated, but a significant part of it. For the person who started QEMU or Bochs it will not be easy to figure it out. Here is the instruction: gxemul.sourceforge.net/gxemul-stable/doc/guestoses.html#netbsdhpcmipsinstall . There is a caveat that using the -X option (a window with a framebuffer instead of a text console) does not work the arrows on the keyboard, which leads to a deadlock in the installer when splitting the slice into sections - it is in this dialog, the only one of all time, there are no shortcuts, and the choice of the “OK” item can only be made by arrows. However, if you put it on a virtual disk and use it entirely, then this moment will not arise at all. The speed of operation is surprisingly consistent with the real machine, I launch it on Pentium M 1.8. I don’t know how to load Windows CE in it. Perhaps, dump the firmware. But to do this is no pleasure, to be honest

findings


In the museum, definitely. No practical use

Source: https://habr.com/ru/post/171143/


All Articles