I updated some workstations of the client to Solaris 10 update 9. Upon installing my xorg.conf (dual-screen setup) I had to notice that it does not work anymore. The problem is, that the NVidia driver does not contain support for the graphic card we use.
Normally this is not a big deal, this can happen… but in this case this is about SUN Ultra 20 workstations with SUN provided NVidia Quattro FX (NV37GL) cards. Ok, they are not the most recent ones, they where bought 4 – 5 years ago, but still, they just work as needed here and the current Solaris release has no out-of-the-box support for them. I would expect this to work already in a fresh install (yes, I was not able to get the nv driver to work with two screens on this graphic card, it seems the nv driver has not support for this).
Solution for me: download the old driver from NVidia and integrate it into Jumpstart (but still, some hours are lost because of first trying to get a working dual-screen setup with the nv driver before taking an old NVidia driver and using it like before in xorg.conf).
Another glitch a co-worker discovered is that StarOffice is not included anymore. That is again something which will cause some loss of time. I will have to have a look how to handle it. Probably it is best to install it on the server and mount it via NFS on the workstations. I will see soon if this is can be done (installation of OO into a specific place which can be shared) or not.
The last week has seen some bikesheds. One of them was my commit of the doxygen infrastructure for the kernel subsystems. Some people don’t like the way doxygen requires some markup tags in the comments, some people don’t think such API docs provide additional value and some people fear that 3rd party developers may use some functions which shouldn’t be used. I don’t repeat the counter-arguments of myself and other people here, but there are people out there which already make use of the current unsatisfactory doxygen output and are happy about this infrastructure. Luckily is was superseeded by another bikeshed (and gnn@ wants to work on documenting a subsystem to show the benefits to those people which do not think yet, that this is a good idea). On a related issue, I’m waiting on a repo copy of src/sys/doc to src/tools (it’s one of two repo copies I’m waiting for, ncvs@ seems to be bussy ATM). Some doc@ people think it is more appropriate there.
The FC4 linux base port and the xorg based linux X11 libs port are scheduled for testing in an experimental ports build run, we may see the switch of the default linux base port in the not so distant future. It seems Boris is working on updates to the rest of the linuxolator infrastructure in the Ports Collection (gtk, …), so we may see a lot of updates there after the switch of the default linux base port.
In the last days I also helped/talked with my SoC students. Roman is playing a little bit with an amd64 tinderbox he got access to and as a result he committed support for building the linuxolator on amd64 as a module to perforce (call for testers: he did send a patch to emulation@, please give it a try if you own an amd64 box). Ryan is cataloging the IOCTL’s and their status (implemented, obsolete, …) in the FreeBSD wiki. I already priorized those he did so far, and gave some suggestions how to proceed with the important ones. This way he hasn’t to wait for me or Ariff when he is finished with the cataloging (being a mentor living in a different time zone means you should be ahead of your student… being ahead even before he is able to asks questions is … a boost for your own ego 😉 ).