Hi Alien Bob
I've installed just over 600 packages from Slackware-Arm. The partition layout has been untouched. The Kernel is that which came with the Odroid. I did a bit of hacking to get it to boot and to get the time using ntpdate, the Odroid hasn't a battery. I did a bit of hacking to get Xorg to start which was mainly setting up a conf file in /etc/X11/xorg.conf.d to explicitly set a path to the font files that I was using.
I boot directly into Slackware as follows
power on the Odroid
at the logon prompt, I logon as root!
at the command prompt
Code:
/etc/X11/init/initrc.xfce
On the command line the Fonts are OK as they in Xterm within xfce.
Could I be missing a step by not using startx to start xfce? I decided not to use startx because it put me into the TWM window manager. Once I was happy with xfce I was going to go back and configure, so that startx started xfce.
If I'd been doing an install on an X86 PC I would have used the DVD and setup. Followed the steps and everything would have worked. Though I do remember a step in setup about fonts when a message gets displayed about having to do something each time a new font is installed. Am I remembering correctly and would this be relevant?
Should I move this thread to the Arm list? If so how?
There was a similar problem that I reported in the odroid forum when using the standard Odroid Xubuntu install with the Matchbox window manager instead of XFCE. For that problem it was suggested that for the GPU
Quote:
Some Window Manager will cause issues on the Mali drivers
|
.
My objective in all this was to see if I could get as far as getting a Porteus clone running on an Odroid. In my day to day computing I use Slackware, I rarely use Ubuntu. I had hoped that by installing Slackware on the Odroid I would get finer control in configuring the software and either not see the Fonts issue or easily overcome it. Maybe I was wrong, though I can't see why it shouldn't just work irrespective of
Quote:
Some Window Manager will cause issues on the Mali drivers
|
Alex