I tried with "-depths 8" and still got the same output.
I compared the contents of libs of different -depths setting, they are all the same. The difference might be within application compiled by QT/E libs compiled with different options.
I tried to execute the framebuffer test bundled in QT/E package. It did run, and display was actually changed, though terrible. Ideally, there should be three rectangles on screen. The result was no desired rectangles, and screen was inverted (white to black and black to white). I had to reboot to resotre.
Here is the stdout and stderr output by framebuffer test program:
Code:
initPalette: error reading palette: Invalid argument
initPalette: error setting palette: Invalid argument
resetPalette: Invalid argument
The framebuffer device was opened successfully.
Fixed screen info:
id: iRex DELTA Frame
smem_start: 0xc1000000
smem_len: 786432
type: 0
type_aux: 0
visual: 3
xpanstep: 1
ypanstep: 1
ywrapstep: 1
line_length: 768
mmio_start: 0x0
mmio_len: 0
accel: 0
The framebuffer device was mapped to memory successfully.
Was in graphics mode already. Skipping
Variable screen info:
xres: 768
yres: 1024
xres_virtual: 768
yres_virtual: 1024
yoffset: 0
xoffset: 0
bits_per_pixel: 8
grayscale: 1
red: offset: 0, length: 8, msb_right: 0
green: offset: 0, length: 8, msb_right: 0
blue: offset: 0, length: 8, msb_right: 0
transp: offset: 0, length: 0, msb_right: 0
nonstd: 0
activate: 32
height: -1
width: -1
accel_flags: 0x0
pixclock: 20000
left_margin: 64
right_margin: 64
upper_margin: 32
lower_margin: 32
hsync_len: 64
vsync_len: 2
sync: 0
vmode: 0
Will rectangles from the 16 first entries in the color palette on the screen
Done.
Anyway, it proved that QT/E might be ported to iLiad.