OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

2 Pages V  < 1 2  
Reply to this topicStart new topic
> Pdaxii13v2: First Collection Of Experiences, few complaints, hints, issues
walts
post Oct 9 2007, 11:26 AM
Post #16





Group: Members
Posts: 57
Joined: 20-April 04
From: Florida, USA
Member No.: 2,933



I have a little more information and a question for Meanie (or anyone else who might want to help)

I've been going throught the code for wifi-radar with my limited knowledge of Python, and have found one error I was making...
In the "Connection Commands" portion of the Profile, I had been putting
CODE
iwconfig wlan0 up
in the "Before" box. The program actually does this if you tick the "ifup required" box in Preferences. There is no need to specify in both places, and the connection commands are executed after the ifup piece, so it's probably harmless, just redundant.


My Question:
In running wifi-radar from the command line, the following message keeps repeating every time the program makes an inquiry of the interface:
Warning: Driver for device wlan0 recommended version 18 of Wireless Extensions, but has been compiled with version 16, therefore some driver features may not be available...

I don't know what I can do to resolve this, or even if it has any bearing on my current issues. I did an ipkg upgrade earier today, so everythng should be up-to-date. I have hostap and wps_supplicant versions 0.4.7-1 installed. How that relates to any versions of Wireless Extensions I just don't know. I don't have any ability to compile anything (except what might live on the Zaurus - I have the Full install on a 3200)
Go to the top of the page
 
+Quote Post
walkman
post Oct 9 2007, 01:35 PM
Post #17





Group: Members
Posts: 76
Joined: 26-September 07
Member No.: 20,757



This was discussed many times in the forum. It seems that we do not have to care about this message as it does no any difference, or harm...

BTW, thanks for the hint with IfUp. I suspected that as well (see this thread above), but did not care too much.

But anyway, Wi-Fi radar seems to kill the network device for some reason anyway. When I will have time, I'll try to take a look at that code as well. I think wifi radar is a tool in a right direction, it just needs some improvements... Like a support for WPA, or so... It might be a good reason to start to take a look at Python at last... Although I prefer Ruby moe...
Go to the top of the page
 
+Quote Post
adf
post Oct 9 2007, 06:40 PM
Post #18





Group: Members
Posts: 2,821
Joined: 13-September 04
From: Wasilla Ak.
Member No.: 4,572



QUOTE(walkman @ Oct 9 2007, 01:35 PM) *
This was discussed many times in the forum. It seems that we do not have to care about this message as it does no any difference, or harm...

BTW, thanks for the hint with IfUp. I suspected that as well (see this thread above), but did not care too much.

But anyway, Wi-Fi radar seems to kill the network device for some reason anyway. When I will have time, I'll try to take a look at that code as well. I think wifi radar is a tool in a right direction, it just needs some improvements... Like a support for WPA, or so... It might be a good reason to start to take a look at Python at last... Although I prefer Ruby moe...

There was some work done on an fltk network settings app that might be worth looking over.... I forget who did it, though.
Go to the top of the page
 
+Quote Post
Jon_J
post Oct 10 2007, 04:45 AM
Post #19





Group: Members
Posts: 1,843
Joined: 31-December 05
From: Illinois USA
Member No.: 8,821



walkman, I would also like to know the solution to the problems with *.png images.
Maybe you missed meanie's question as quoted below.
Thank you in advance - Jon
QUOTE(Meanie @ Oct 4 2007, 07:58 PM) *
what extra symlinks did you have to add for libpng?

Go to the top of the page
 
+Quote Post
walkman
post Oct 10 2007, 06:41 AM
Post #20





Group: Members
Posts: 76
Joined: 26-September 07
Member No.: 20,757



QUOTE(Jon_J @ Oct 10 2007, 02:45 PM) *
walkman, I would also like to know the solution to the problems with *.png images.
Maybe you missed meanie's question as quoted below.
Thank you in advance - Jon
QUOTE(Meanie @ Oct 4 2007, 07:58 PM) *
what extra symlinks did you have to add for libpng?



I did not miss it. I just decided not to touch the Zaurus in these days any more. I am very busy at work and if I had it around, I would probably play with it all the time sad.gif. So actually I cannot take a closer look at exactly what was the name of the library to which I made a symbolic link.

The problem was, that ROX always wrote that it cannot read PNG files with the error I mentioned above. Don't remember which exactly (started with "d..."). Then I found that it is a problem that the the loader for png is not registered by gdk-pixbuf-query-loaders. When I rerun that one, it said that libpng12.so.* cannot be loaded in order to register it to read PNGs. Then I checked /usr/lib and found that such a filename as required by gdk-pixbuf-query-loaders does not exist at all, because the version suffix of libpng12.so.* was different (kind of libpng12.so.0 existed, but libpng12.so.1 was required). So I just created a symlink from the filename in the error to the only libpng12.so which was there, re-run the gdk-pixbuf-query-loaders, which did not complain any more and then ran ROX and everything was alright again.

If you will wait a bit, I am planning to start to play with Zaurus in 2 weeks (after some deadlines) again. I will try to repeat the whole situation and post a precise fix. You know, when things work, it is not any more easy to find out how the problem was solved. Especially when after that I reinstalled libpng12 at least twice...

Sorry for this delay...
Go to the top of the page
 
+Quote Post
Jon_J
post Oct 10 2007, 01:31 PM
Post #21





Group: Members
Posts: 1,843
Joined: 31-December 05
From: Illinois USA
Member No.: 8,821



walkman, I found the solution to my *.png problem! smile.gif
Since meanie posted in the pdaxii13v2 thread about the correct files for libpng and cairo, I uninstalled my older version of libpng and installed the newer one. (libpng_1.2.12_armv5tel.ipk)
After this I stopped getting any errors when launching rox in a console, but all my icons and *.png images were still missing.
Read the below post, it describes where a setting in gqview was causing this and the fact that gqview has that much control over the GUI in rox and pdaxii13.
http://www.oesf.org/forum/index.php?s=&...st&p=168869
Go to the top of the page
 
+Quote Post
walkman
post Oct 28 2007, 11:59 AM
Post #22





Group: Members
Posts: 76
Joined: 26-September 07
Member No.: 20,757



QUOTE(Meanie @ Oct 5 2007, 01:58 AM) *
I have two wifi cards, one uses orinoco and the other uses hostap. both work for me. the problem as i mentioned before is that some wifi cards have identical manfids even though they are very different cards and need different drivers. Unfortunately, there is nothing that can be done for those wifi cards. It will always be working for some and not for others out of the box for wifi cards that have those conflicting manfids. removing the unwanted driver or manually fixing the config files is the only way to get those cards working...


Well, I am no Linux driver expert and I do not see deep into the driver stuff in pdaXrom. However, developers always ask for "pccardctl info" record for the card. What do they do with it? I guess, it belongs to some config, right? Theoretically (according to Google), this should go to /etc/pcmcia/config, or hostap_cs.conf. But such files do not exist in the newest pdaXrom (r198). So where are these things? Blacklisting does not work either...
Go to the top of the page
 
+Quote Post
walkman
post Nov 29 2007, 03:20 PM
Post #23





Group: Members
Posts: 76
Joined: 26-September 07
Member No.: 20,757



QUOTE(walkman @ Oct 4 2007, 05:32 PM) *
ROX
After X restart it replaces my background image. Obviously more than a file manager comes with it. But how can I put it into a plain file manager mode and keep the standard openbox desktop? I'll have to work on this in the close future.

BUG: After first attemtp to launch rox-filer it opened however without few icons. It displayed some question marks instead. When started from command line, it spit out this:
** (ROX-Filer:1760): WARNING **: Couldn't recognize the image file format for file ...
I googled around and found the problem described here. However running "$ gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders" did not help!!! Later I found the problem was with how libpng is installed. Some applications (apart from Rox) do not find the libpng library. Solution was to simply provide a correct symbolic link /usr/lib/libpng12.so.0 to the correct .so file. This seems to be a distribution issue.


I had to once again solve this issue and I remember several peopole asking abnout it. So this is how it is to be solved on the pdaXiiv2:

- uninstall whatever libpng version you have installed
- install libpng with the highest version number (currently 2.1.12)
- execute gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders

The command should finish withot an error. And there you go then...
Go to the top of the page
 
+Quote Post

2 Pages V  < 1 2
Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 28th November 2014 - 12:38 AM