3.5.4.1 Kernel 2.6 Testing On Tosa/6000, alpha testing for keen users Options

[speculatrix]

the other thread about producing a release of OZ for Tosa was getting a bit overloaded, so I thought I'd start a fresh thread now things seem to be getting close to beta quality/release candidate levels

[koen]

the other thread about producing a release of OZ for Tosa was getting a bit overloaded, so I thought I'd start a fresh thread now things seem to be getting close to beta quality/release candidate levels

And to make it really usefull you could post all relevant the bugs numbers from http://bugs.openembedded.org

[speculatrix]

I don't know if it's just me, but I can only get WEP to work when wlan0 is in managed mode, not in ad-hoc mode.

My AP (access point) is actually a Intel 2915ABG card in my linux firewall, and runs in ad-doc mode. If I disable wep on the AP, everything works. As soon as I turn on wep, Tosa can't ping or anything... iwconfig on both AP and Tosa indicates settings look fine - I checked the WEP key very carefully.

Can someone else test ad-hoc with wep and let me know if they get it working?

thanks

[speculatrix]

the other thread about producing a release of OZ for Tosa was getting a bit overloaded, so I thought I'd start a fresh thread now things seem to be getting close to beta quality/release candidate levels

And to make it really usefull you could post all relevant the bugs numbers from http://bugs.openembedded.org

I'm thinking that this thread could be used for discussing testing, workrounds and what's going on rather than trying to replace the bug-tracker.

[koen]

the other thread about producing a release of OZ for Tosa was getting a bit overloaded, so I thought I'd start a fresh thread now things seem to be getting close to beta quality/release candidate levels

And to make it really usefull you could post all relevant the bugs numbers from http://bugs.openembedded.org

I'm thinking that this thread could be used for discussing testing, workrounds and what's going on rather than trying to replace the bug-tracker.

I was hinting at the fact that any issue (and workarounds/fixes) should be in the bugtracker. Any info that's only in this forum can be considered lost. Not all OZ developers follow this forum and the fraction of OE people using this forum is even less. So you can reach the tech-savvy people by using the bugtracker and have semi-technical chitchat here.
Searching bugzilla is infinitally easier than grepping through fora or wikis.

[koen]

maybe OZ should stop dodging the issues

How can we fix issues if people are too lazy to report into the bugtracker, but do have time to rant on fora?
I'd rather have 100 'false' bugreports and 2 'good' ones than no bugreports. If only people would spend some time in accurate reporting instead of complaining on fora.

Problems == bugs
Solutions == bugfixes

[Greg2]

sigh, another thread has become a meta discussion about OZ and its practises (and excuses) rather than actually seeking to tackle specific problems.

@ speculatrix

The only thing koen did was post a friendly reminder to use the bugtrackers...

Please don't start this today.

[speculatrix]

I can see both sides of the argument,
a/I am a software developer by trade and I know how frustrating it can be to get bad bug reports... all I am trying to say is that the discussion forums are a way of people getting a bit of help to determine if it's a case of PEBKAC (problem exists between keyboard and chair) or a real problem.
b/I am a newcomer to OZ/GPE and genuinely want to help make it better, but there is a very steep learning curve, and quite often I find that a minor mistake/assumption is compounded by a small bug in combination with a lack of a howto. I want to help!

@greg2: if this were the only time koen'd said this in recent discussions, I wouldn't have felt his answer to be unhelpful and gone off on a tangent... anyway, yes, enough already.

[lardman]

---edit--
maybe OZ should stop dodging the issues and actually bother to think about usability. maybe actually try and delegate someone as a documentor/librarian, if nothing else to create a skeleton wiki structure which everyone else can fill in?

Indeed, that's me. The only issue is that I'm very busy at the moment, plus this is supposed to be a collaborative venture and as I've been using OZ for a long time, I'm not really in the best position to know what people find difficult, etc.

The wonder of the wiki is that people can actually add change pages themselves - if the problem is that you're worried about where to put a page, then please email me and I'll take a look/create a page/etc.

Speaking of skeletons, there is a main HowTo index page and a FAQ page on the wiki so surely there must be somewhere to write things down...?


Si

[koen]

[quote=lardman,Jul 21 2006, 04:31 PM]
[quote]
The wonder of the wiki is that people can actually add change pages themselves - if the problem is that you're worried about where to put a page, then please email me and I'll take a look/create a page/etc.

[/quote]

Could the wiki ACLs be relaxed a bit? Having a wiki is IMNSHO useless, if you have to keep mailing people.

[CoreDump]

The wonder of the wiki is that people can actually add change pages themselves - if the problem is that you're worried about where to put a page, then please email me and I'll take a look/create a page/etc.

Could the wiki ACLs be relaxed a bit? Having a wiki is IMNSHO useless, if you have to keep mailing people.

The problem is probably that not every user can be trusted. With all the god damned spammers and vandals out there, we'd have to restore the pages every day or two

Yes, that stinks but there really is no alternative if you can't monitor the website 24/7

[nevarrie]

I think the first post in this forum should have list of all know bugs that contains the Items name, Description, Status, and BugTracking Id. I have started doing this at List of issues for OZ/GPE on my website. So far I have only entered in one of the bugs int eh handhelds.org bug tracked for the addition of wlan-ng options to gpe-conf network.

To me this forum should be used to discuss the discription of the bugs and what bug tracking system the bug should be in along with making sure it is in a bug tracking system.

Some people are not going to be willing to enter in new bugs, or as I have problems doing decribing the bugs so that something can be done about them.

This list maybe something that we need to put on the wiki also or have it only on the wiki so any of us can update is and just have a link to it from the first post. We may also find it is better to have a seperate thread for each bug after we have identifed what is is and have it ina bug tracking system and only uses this thread to identify the bug enough to get it in a bug tracking system and then split off a new thread for the bug.

What are people thoughs on this?

[nevarrie]

I need help on describing the alarm's when suspended.

What application is the alarms from?
Is this still and issue in the 2.6 kernel?

I do not have this problem since I do not have alarms on my Z so I am not the best person to descibe it but I can put the bug in if I can get more information.

[vorondil28]

I need help on describing the alarm's when suspended. 

What application is the alarms from?
Is this still and issue in the 2.6 kernel?

I do not have this problem since I do not have alarms on my Z so I am not the best person to descibe it but I can put the bug in if I can get more information.

I'm assuming you're talking about alarms not resuming the unit when they occur while the unit is suspended. I'm pretty sure that's fixed unless there's some other issue I don't know about. In the other thread, dirk siad it's fixed, and they work for me (I just tested it) on the latest image.

EDIT: By "latest image" I really mean, "latest GPE image." I don't know about Opie.

[speculatrix]

I managed to resolve the problem with ad-hoc and wep.. turned out to be a combination having once tried to use the gpe network config tool and basic stupidity. So, intel 2915abg on firewall runs in ad-hoc with wep and Z uses the following configuration to talk to it:

CODE

# Wireless interfaces
iface wlan0 inet dhcp
 wireless_type wlan-ng
       wireless_mode managed
       wireless_enc on
       wlan_ng_authtype opensystem
       wlan_ng_key0 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
       wlan_ng_key1 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
       wlan_ng_key2 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
       wlan_ng_key3 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
       wireless_essid ZZZZZZZZZZZZZZZZZZ
 pre-up modprobe ohci-hcd
 pre-up modprobe prism2_usb
 post-down rmmod prism2_usb
 post-down rmmod ohci-hcd