dd'ed the iso on a USB2 key then on a brand new UBS3 (a good one, Kingston Data Traveller 64 GB), both run very slow. Actually it lags regularly for minutes, making the use almost impossible. I’ve run it on 2 different computers, same problem. I’ve checked the sum,
dd'ed the iso again with no luck. Also tried to use the 1.3.0 instead of 1.3.1, no luck either.
It looks like some process consuming a lot of CPU starts in the background and one has to wait its job is over before one can take control again.
I’ve tried the trick at boot described in the issues. Things seemed to go a little bit better (it lagged again at language choice, but after that, the install steps went on smoothly). But then I could not go graphical: the 3D acceleration lead to a grey screen for too long, and the VESA driver lead to the wallpaper + mouse pointer but nothing more (no right-click menu, no plank, no tint2).
It’s a shame because it looked so promising!!
A special problem has been a bad working wireless driver on one of the computers. The laptop has this stupid chipset I’ll care not to buy such any more. I know this driver needs some more packages to install and even some compilation (I could make it work on vanilla FreeBSD). It’s the bwn one. There. When loading only bwn (without the required additional stuff) from start, it triggers a lot of error messages. On the computer using this chipset, I could not start the graphical environment at all. When getting at the graphics card choice (or driver, I don’t remember), the screen got rapidly flooded by these error messages. The second time, I was expecting it so I did select and confirmed the choice rapidly, but after several minutes, OpenBox was still not there (only these error messages in text mode). So, as I guess it would be too much to embed the additional drivers (maybe it would also be the same problems with rights, that lead FreeBSD to not distribute them?), but maybe it would be wiser to not load bwn at all at start, to avoid such error messages flood?
Well I’m disappointed to not be able to use NomadBSD. Hope a future release will fix these problems?