Messages

1

Angstrom & OpenZaurus / Opie + X/matchbox?

« on: April 29, 2005, 01:12:00 am »

I have OZ (collie) installed on my 5500 /w opie. It works great and I was wondering if i could X to work on it as well.

I followed the Opie + GPE HOWTO off the OZ homepage to get some results and I could launch X /wout a window manager thanks to that (however, i have no idea how to start gpe).

Anyway, I then started playing with matchbox and could manually load it on my X session using matchbox-desktop and matchbox-panel.

But, i cant do much, as i get lots of error messages about pixmaps (thanks to pixbuf, I assume). I think it may be a libpng issue. Anyone experience this before?

example error message:

Code: [Select]

(gpe-conf:2798): GdkPixbuf-WARNING **: Can not open pixbuf loader module file '/opt/QtPalmtop/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
GPE-ERROR: Couldn't recognize the image file format for file '/usr/share/gpe/pixmaps/default/delete.png'Then I liked stuff from /usr/lib/gtk-2.0 to /opt/QtPalmtop/etc. Now i get these errors:

Code: [Select]

GPE-ERROR: Couldn't recognize the image file format for file '/usr/share/gpe/pixmaps/default/delete.png'
ah!!

2

Angstrom & OpenZaurus / Openvpn

« on: April 26, 2005, 11:52:28 pm »

I managed to compile & package OpenVPN 2.0 RC 20 for the Z C3000. Now I'm looking for a way to get the tun.o kernel module... I tried compiling the kernel on the Z itself, but that borked
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75406\"][{POST_SNAPBACK}][/a][/div]

On collie, i was able to simply modprobe tun (or add it to /etc/modules and reboot). Are you sure its not already there? See if you can just ipkg install it from the feeds, too. Otherwise, OpenVPN worked just fine! I can now violate all kinds of security policies at work! yay!

3

Angstrom & OpenZaurus / Oz 3.5.3 Wellenreiter Ii -- We V16/we V17

« on: April 26, 2005, 11:46:14 pm »

Just did a fresh install of collie and full upgrade, prob still exists for me and my 5500.

Just some insight, i believe this is a problem with the version of wireless-extentions (or WE).  The commands that the GUI are issuing are probably working just fine. however, if i remember correctly, it must not be verifying the error code and quiting on what is essentially a warning message.