irclog2html for #openzaurus on 20060325

00:15.13*** join/#openzaurus darkschneider (n=gab@213-140-6-96.ip.fastwebnet.it)
00:30.38Radiancei'm going to try a totally different AP, just to see if it is really related
00:31.31webmindsounds odd... can't say I've tested my tosa with wireless on 3.5.4 yet
00:31.53webmindhm
00:32.00webmindwell a little last weekend
00:32.05webmindworked ok then
00:35.01Radiancewebmind, longer than 10 to 15 min ?
00:35.12Radiancewithout having it suspend all by itself ? hehe
00:42.59webmindI'm not sure for how long
00:43.04webmindhmm
00:43.13webmindyes definatly longer
00:43.39webmindquite a while.. I remember doing some tweaking over ssh over wireless on it
00:44.29webmindbut I have noticed apm problems.. but those could in theory be cause due a broken SD card.. or a bug in the sdio
00:44.32webmindnot sure
00:44.45webmindor just actual apm bugs but I doubt that kinda
00:44.52Radiancemight be the AP
00:45.00Radiancebut i'll test this one first
00:46.05webmindthe AP putting your tosa on standby ?
00:46.17webmindthat would be odd and a bug I think?
00:47.46Radiancewell, i dunno, just gonna test if it makes any difference
00:47.51Radiancewill use a linksys ap now
00:56.00*** join/#openzaurus angom_h (n=angom@red-corp-200.79.145.199.telnor.net)
00:56.51*** part/#openzaurus angom_h (n=angom@red-corp-200.79.145.199.telnor.net)
01:02.25webmindok
01:29.38webminddarn.. my cradle doesn't seem to be working
01:29.49webmindawell tomorrow yet another day
01:30.43Radiancedidn't touch that part yet :)
01:31.00Radiancehad to dig up another ap linksys since i couldn't reconfigure the current one
01:40.04webmindawell.. gnite
01:54.56Radiancenight mate hehe
02:15.40Radiancebtw, any one noticed that backspace/del or ctrl-h is not working on the console ? (only if the virtual keyboard is used it works ofcourse)
02:17.01*** join/#openzaurus Necronom (n=jack@ice.mudshark.org)
02:20.04*** join/#openzaurus Ironnads (n=Ironnads@host86-135-182-193.range86-135.btcentralplus.com)
02:42.04*** join/#openzaurus Timelord (n=TL@4.78.4.43)
02:43.22*** join/#openzaurus REdOG (n=REdOG@66.0.161.218)
02:53.52*** join/#openzaurus Cyorxamp (n=Cyorxamp@82-47-144-216.cable.ubr11.brad.blueyonder.co.uk)
02:56.34Radianceguys, i noticed after working a while in the console that the keyboard locks up
02:56.42Radiancei can only use the virtual keyboard
02:57.05Radiancebut the hardware keyboard freezes totally in the console and any app
02:57.22Radiancethis is 3.5.4 on a sl-6000
03:00.13CyorxampAnyone in here have a broken SL-5500?  (maybe the screen is broke)... I need a replacement main (PCB) board
03:01.53Radianceanother note, keyboard doesn't respond after suspend/resume, when defining a second wifi alias then it comes up but dhcp doesn't work for it, have to enter it manually
03:02.35Radianceshutdown works only with using usbctl off 1 in the above scenario
03:03.05Radiancegotta go get some sleep now
03:07.47*** join/#openzaurus s0ciopath (n=user@net34-155.netkaster.ca)
03:21.37*** join/#openzaurus mithro (n=tim@lester.mithis.com)
04:06.02*** join/#openzaurus dtx (n=chatzill@adsl-69-150-135-188.dsl.okcyok.swbell.net)
04:13.08*** join/#openzaurus mithro (n=tim@lester.mithis.com)
04:27.21*** join/#openzaurus mithro (n=tim@lester.mithis.com)
04:41.09*** join/#openzaurus mithro (n=tim@lester.mithis.com)
04:56.50*** join/#openzaurus mithro (n=tim@lester.mithis.com)
05:02.15*** join/#openzaurus mithro (n=tim@lester.mithis.com)
05:20.43*** join/#openzaurus mithro (n=tim@lester.mithis.com)
06:06.16*** join/#openzaurus mithro (n=tim@lester.mithis.com)
06:18.55*** join/#openzaurus mithro (n=tim@lester.mithis.com)
06:26.36*** join/#openzaurus yath[tm] (n=yath@p5495E6BB.dip.t-dialin.net)
06:34.43*** join/#openzaurus mithro (n=tim@lester.mithis.com)
06:42.15*** join/#openzaurus s0ciopath (n=user@net34-155.netkaster.ca)
07:19.02*** join/#openzaurus mithro (n=tim@lester.mithis.com)
07:27.20*** join/#openzaurus mithro (n=tim@lester.mithis.com)
07:43.15*** join/#openzaurus mithro (n=tim@lester.mithis.com)
08:05.32webmindRadiance, did it lock up after pressing Fn + /
08:05.34webmind?
08:21.31*** join/#openzaurus mithro (n=tim@lester.mithis.com)
08:31.32*** join/#openzaurus JiniDog (n=jini@V9e76.v.pppool.de)
09:02.24*** join/#openzaurus mithro (n=tim@lester.mithis.com)
09:36.10*** join/#openzaurus ProfessorOhki (n=professo@user-11fa4e5.dsl.mindspring.com)
09:37.06ProfessorOhkiI just installed Opie on my 6000L, trying to get wellenreiter to run, i need to use a .patch to update stuff, how does one use a .patch file?
09:39.54*** join/#openzaurus mithro (n=tim@lester.mithis.com)
09:43.21Radiancewebmind, it locks up at random moments
09:45.59*** join/#openzaurus pleemans (n=peter@d5152D12D.access.telenet.be)
09:52.50webmindodd
09:53.50webmindRadiance, are you using gpe or opie ?
10:18.48*** join/#openzaurus polyonymous (i=hacker@pD953877B.dip0.t-ipconnect.de)
10:28.50*** join/#openzaurus Bompo (n=Bompo@V3c93.v.pppool.de)
10:30.10*** join/#openzaurus pleemans (n=peter@d5152D12D.access.telenet.be)
11:22.32*** join/#openzaurus frdy (n=opera@orange-ipfw.gni.pl)
11:24.14*** join/#openzaurus incinerator (n=incinera@82-41-24-164.cable.ubr04.edin.blueyonder.co.uk)
11:33.46*** join/#openzaurus Bompo (n=Bompo@V3c93.v.pppool.de)
11:44.35CoreDump|homemorning
11:49.16*** join/#openzaurus darkschneider (n=gab@213-140-6-96.ip.fastwebnet.it)
11:52.28*** join/#openzaurus mithro (n=tim@lester.mithis.com)
12:36.12*** join/#openzaurus mithro (n=tim@lester.mithis.com)
13:04.01*** join/#openzaurus alan|home (n=alan@ARouen-152-1-16-251.w83-115.abo.wanadoo.fr)
13:06.30alan|homemorning averyone
13:08.46CoreDump|homehello alan|home
13:11.19alan|homehello CoreDump|home
13:13.49*** part/#openzaurus frdy (n=opera@orange-ipfw.gni.pl)
13:24.28neil_manyone use OpenBSD on their C3000
13:32.29alan|homeneil_m: excuse me, but i don't think you'll find such a person on this chan... mainly for OZ users...
13:32.51alan|homehave a try at #zaurus
13:34.07neil_mdoh
13:34.08neil_mthanks
13:34.09neil_m:D
14:02.33*** part/#openzaurus neil_m (n=voldemor@neilmathers.co.uk)
14:10.59*** join/#openzaurus ajolk (n=alex@5.40.100-84.rev.gaoland.net)
15:06.44*** join/#openzaurus s0ciopath (n=user@net34-155.netkaster.ca)
15:07.10Radiancewebmind, it's opie
15:44.03*** join/#openzaurus s0ciopath (n=user@net34-155.netkaster.ca)
16:10.06Radiancethink i'll try gpe cause without a reliable keyboard it's not really useful
16:13.36Radiancejust for the record, with the previous release i had never this problem hehe
16:28.31*** join/#openzaurus s0ciopath (n=user@net34-155.netkaster.ca)
17:07.25*** join/#openzaurus Cyorxamp (n=Cyorxamp@82-47-144-216.cable.ubr11.brad.blueyonder.co.uk)
17:09.28Radianceflashing to gpe now :)
17:11.09*** join/#openzaurus DataBeaver (i=tdb@YZMDCCCXXXV.dsl.saunalahti.fi)
17:14.14Radianceis it normal that the gpe 2.7 splash screen stays for a long time there ? loading ?
17:15.02CoreDump|homeyes
17:15.18Radianceah ok
17:15.19CoreDump|homeit is configuring your apps in the background on first boot
17:15.25Radiancei see it proceeds now ...
17:19.59Radiancelooks promising ;0
17:20.00Radiance:)
17:20.13Radianceany known issues with gpe 3.5.4 currently ?
17:23.21CoreDump|homenever tried the 3.5.4 images sorry
17:30.13Radianceah ok
17:30.17Radiancetrying gpe now heh
17:30.34Radiancefeels familiar compared to opie
17:40.55*** join/#openzaurus darkschneider (n=gab@213-140-6-96.ip.fastwebnet.it)
17:42.33kadosanyone using the opie calendar as a part of an enterprise calendaring system?
17:42.58kadosI'm wondering whether you can sync it with any of the web-based open-source group calendar systems
18:14.34Radiancehm, if i set an alarm, should it work while the unit is suspended ?
18:17.02CoreDump|homeit should yes
18:19.58Radiancewell, it didn't hehe
18:20.12Radiancethe alarm went off only after i unsuspended the unit
18:21.43Radiancei'll try again just to be sure
18:27.20Radiancenope didn't work
18:27.32Radianceonly after i unsuspend the unit then the alarm goes off
18:28.46Radiancemy 50 bucks cellphone when shutdown even has this functionality lol
18:42.33Radiancewell, to summarize it: opie: keyboard locks at random time, need full reboot/shutdown to make it work again, wifi setup doesn't work (only through manual setup in console). GPE(maybe also opie), same wifi issue, alarm doesn't work when unit is suspended, unit sleep config doesn't work when set to sleep at x time, manual suspend needed. That's currently what i discovered for release 3.5.4 on a 6000.
18:46.16kadosRadiance: I can confirm that
18:46.23kadosRadiance: on my sl-6000 it's the same
18:46.33kadosRadiance: consider donating some $$ to one of the core developers
18:46.44kadosRadiance: i did that recently to get something I wanted fixed done
18:47.11pgasis this with 2.4 kernel?
18:48.43pgasthere is a kernel patch for resume on alarm for 6000 in this thread http://www.oesf.org/forums/index.php?showtopic=16617
18:48.56pgasdon't know if this applies to oz
19:00.02Radiancekados, i donated like 400 $ a while back
19:00.17Radianceso i think that's more than the average joe who doesn't donate shit
19:01.26Radiancespecifically for the 6000 development, so it can be used in a business environment, so the least which can be done is to fix these stupid things like the alarm, wifi menu :-)
19:02.45Radiancewithout the basic functionality of the average pda this is one expensive brick, which is only useful for ppl who have seas of time to play with it instead of using it
19:04.12Radianceyou know how old the wifi issue is ? it's like a year or 2 years and it still has not been fixed
19:05.00Radianceso why should i donate more if i simply can't use it normally after all this time of development ? hehe
19:06.40Radiancei really like the 3.5.4 release compared to the previous ones, but the key is basic pda functions should work perfect like the alarm, suspend, wifi, if some app doesn't work well that's no biggy, but the basic functions must work before it can be used. hehe
19:07.38Radiancemaybe it would be interesting to setup a forum where all current issue's for 3.5.4 are put after being checked, then let ppl donate to get them all fixed :)
19:08.11Radiancemake it a stable and reliable release so whatever happens in newer releases, ppl can always fall back to this release
19:33.56kadosthat's a good idea
19:34.14kadosI've been 'waiting' for OZ to stabalize enough to be usable for years too
19:34.24kadosI pretty much just gave up
19:34.47kadosthe biggest problem IMO is there isn't a large enough user base
19:42.58Radianceelse it has no use to keep releasing new versions but not one single of them is usable in a serious environment
19:45.36*** join/#openzaurus s0ciopath (n=user@net34-155.netkaster.ca)
20:01.47*** join/#openzaurus kolla (n=kolla@82.84-48-52.nextgentel.com)
20:10.27Radianceso lets start with 100 $, any one who can fix the above problems gets it. A partner of mine has also a 6000, and we both together give 100 $ to get those fixed :)
20:11.34kadosheh
20:11.40kadoshrw|gone: you around?
20:11.53kadoshrw|gone: dev work for hire :-)
20:17.30ljpthats only 6 hours work :)
20:18.22kados$100 in poland goes a long way :-)
20:19.13ljphehe
20:23.18Radianceso if any one can, just msg me in private, i will spend more if more issue's come up, need either this thing to work as it was meant or sell it and get some other thing hehe
20:23.19Radiancebrb
21:18.19*** join/#openzaurus Mudhoney (n=Bryan@12-219-31-219.client.mchsi.com)
21:35.29CoreDump|homewhat's the trick to unmute alsa in 3.5.4.1?
21:42.13NA|GoneCoreDump|home: Run alsamixer, then unmute left mixer/right mixer
21:42.30NA|GoneCoreDump|home: Also, if you're using headphones, you'll probably want to turn Out1 down to about 70.
21:42.36CoreDump|homewell, it won't let me
21:42.47NA|GoneHm, what happens?
21:43.24CoreDump|homei can unmute left+right mixer but can raisethe setting from 00
21:43.50NAbyssYeah, l/r mixer are only mute/unmute
21:44.01NAbyssLook for a different setting, left output 1 or something
21:44.09NAbyssShould be about 5-7 items to the right of left mixer
21:44.33CoreDump|homedoh, checking
21:46.49NAbyssSame goes for the right channel
21:55.27*** join/#openzaurus TMM1 (n=aman@residents-liberty-potomac-129-174-185-149.residents.gmu.edu)
22:10.10*** join/#openzaurus Cyor (n=Cyorxamp@82-47-144-216.cable.ubr11.brad.blueyonder.co.uk)
22:28.45dhrnaive question: if the 6000 alarm fix is as reported in http://www.oesf.org/forums/index.php?showtopic=16617 in mid December, how come it isn't in 3.5.4?
22:29.58dhrAh.  Perhaps because that is a pdaXrom forum.  How should this be communicated to the OZ developers?
22:32.34dhrI guess someone should report this in http://bugs.openembedded.org .  I'll go look.  Hmmm.  OZ 3.5.4 isn't a possible version according to this bugzilla -- stops at 3.5.3
22:53.01dhrHmm.  Now I see a 2006 Feb 20 report.  I wonder why my previous search failed.  I will add the pdaXrom forum link.
22:54.40Radiancewhat's this pdaXrom btw ?
22:54.46Radianceis it any better ? heh
22:55.38dhrYou try it and tell me :-).  I've not actually used my 6000 for a long time.  Waiting and hoping for reasonable software but too lazy to make it happen.
22:56.02dhrBTW, the bug report is here: http://bugs.openembedded.org/show_bug.cgi?id=711
22:57.46dhrRadiance: I've just updated it, based on what you said in this channel.  See if you agree.
22:58.57dhrHmm. my comment does not show up.  I wonder why.  Not like other bugzillas I've used.
22:59.53dhrOh, now it does.  This system seems to want to make a liar out of me :-)
22:59.57Radiancemaybe a delay hehe
23:00.01Radiancelol
23:00.45dhryou will also want to look at http://bugs.openembedded.org/show_bug.cgi?id=698
23:01.34dhrIf things are working the way they should, this is a good way for you to report problems to developers.
23:02.06dhrYour experience with wireless on 6000 with the released 3.5.4 should be added to this bug report.
23:02.25Radiancehttp://www.oesf.org/forums/index.php?showtopic=16617  it says something about a solution for the alarm, reading further..
23:03.06dhryes, I said that in my addition to 711
23:03.15Radianceyeah i got it from there
23:03.16Radiance:)
23:05.03dhrI got it from the IRC log,  pgas said so, to you about 30 hours ago (13:48 EST).
23:06.08dhrI cannot tell if the fix directly applies to OZ.  But it should be a strong hint towards a solution.
23:08.28Radianceyeah the code is clear but it's not for oz
23:08.59Radiancei'm going to read up on this pdaXrom or so
23:09.34dhrI'd say "please report back" but I guess that this is the wrong channel :-(
23:11.43dhrmaybe #zaurus is better.  #pdaxrom has one person (other than me -- I just joined to test).
23:32.24*** join/#openzaurus TMM1 (n=aman@129.174.184.3)
23:37.21Radiancelooks like the keyboard lock up bug is already reported here: http://bugs.openembedded.org/show_bug.cgi?id=763
23:37.55Radianceso the keyboard lockup bug, alarm bug, wifi on suspend/unsuspend bug are already reported
23:38.16Radiancei guess it's now waiting for a solution

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.