next »

[mavrothal]

I've set up a project page only to discover  that google code allows a maximum file size of 100M. My tarball is 272mb. What shall I ever do.

james

use http://www.sendspace.com/ (300MB limit)
Upload the file and post the download link here. It will expire but till then...
Also post some instructions. eg if its for an SD card or USB stick, how should it be formated, how to untar (if a tar.gz(2) the file etc.

Alternatively make it a torrent and post it in a public tracker and seed from your machine. You'll need to have some upload bandwidth for the original seeding but after that I guess things are going to be easier (assuming recipients will keep seeding. But even with 15kb/s it will only  take ~5 hours for a complete copy...

[metal.lunchbox]

See this new thread about the project. I can't wait to hear what you guys think. There is certainly room for improvement. If you don't feel skilled enough to make the improvements, complaints are also useful.

[gmschroeder]

sorry, new thread.

[mavrothal]

DebXO is back to life
Experienced Debian users/developers look HERE for more

[fang2415]

Hmm, well, I just installed the new official 0.6 (LXDE) release after months of eager anticipation, and have hit several snags that hadn't shown up in 0.5:

• Wifi network scanning is very erratic.  I'm sitting practically on top of my wifi router and it only shows up in the list about 10% of the time.  When it does show up, the signal is at 100%, but usually it's just not there.  Problem happens both for wicd and for iwlist scanning.
• wicd connects successfully to my WPA network, but doesn't seem to realize it. The progress bar just keeps going back and forth forever and says "Connecting"; right below that is a message that says "[network name]: Done connecting...".  Mousing over the wicd icon in the taskbar shows "Not connected", and the signal strength doesn't show up anywhere.  Internet works fine during all of this, and iwconfig correctly shows an established connection.
• F11 (the OLPC volume down key) usually makes the active window fullscreen; when I do this with a terminal window, the window goes to fullscreen, then the screen fades to white around the edges and the whole system crashes hard (needs a power-off).
• The title bar on the terminal window is sometimes invisible.  Still works fine (aside from the F11 problem), but I have to guess where the bar and the close/maximize/minimize buttons are.  If I use the bar to move the window, the bar keeps the image that used to be under it.
• Had a few other keyboard problems, but upgrading firmware sorted it.  What's the trick to knowing that Q2E45 is *newer* than Q2F01 (other than this obscure Mavrothal post )?
• mplayer runs much slower than in 0.5.  I watch videos with mplayer all the time and it hardly ever lags except with very high-res video; now the video lags way behind the audio on all but a couple videos I've tried (all of which previously worked fine).  This persists whether the video is on a USB or saved on the NAND.

Is anybody else having similar troubles?  Does anybody know of a good way to report bugs without joining the entire OLPC devel mailing list?  Does dilinger ever put out updates between major releases?

The new release doesn't really seem to add much for me (as long as I resintall 0.5 every once in a while to keep disk seeks snappy, and keep the backports up to date) and so far has broken quite a bit, so unfortunately it looks like I'll be moving back to 0.5 for the time being.  If anyone has any suggestions, I'd appreciate it.

(I should also mention that despite dilinger's listed known bug, the battery meter seems to work more or less like it used to: that is, "cat /sys/devices/platform/olpc-battery.0/power_supply/olpc-battery/capacity" works fine!)

[mavrothal]

 What's the trick to knowing that Q2E45 is *newer* than Q2F01

http://wiki.laptop.org/go/Firmware   
OLPC wiki does have a wealth of info BTW, on pretty much everything

Regarding DebXO 0.6 indeed is less functional than 0.5.
However from what I understand, 0.6 rather a testbed to install Debian on the XO without any customization! Eg use only what is in Debian or Kernel, maybe with some pending patches that hopefully will go upstream and get incorporated to their distributions.
This will be pretty major. Not even Fedora is doing that.

[dilinger]

Hmm, well, I just installed the new official 0.6 (LXDE) release after months of eager anticipation, and have hit several snags that hadn't shown up in 0.5:

• Wifi network scanning is very erratic.  I'm sitting practically on top of my wifi router and it only shows up in the list about 10% of the time.  When it does show up, the signal is at 100%, but usually it's just not there.  Problem happens both for wicd and for iwlist scanning.
• wicd connects successfully to my WPA network, but doesn't seem to realize it. The progress bar just keeps going back and forth forever and says "Connecting"; right below that is a message that says "[network name]: Done connecting...".  Mousing over the wicd icon in the taskbar shows "Not connected", and the signal strength doesn't show up anywhere.  Internet works fine during all of this, and iwconfig correctly shows an established connection.
• F11 (the OLPC volume down key) usually makes the active window fullscreen; when I do this with a terminal window, the window goes to fullscreen, then the screen fades to white around the edges and the whole system crashes hard (needs a power-off).
• The title bar on the terminal window is sometimes invisible.  Still works fine (aside from the F11 problem), but I have to guess where the bar and the close/maximize/minimize buttons are.  If I use the bar to move the window, the bar keeps the image that used to be under it.
• Had a few other keyboard problems, but upgrading firmware sorted it.  What's the trick to knowing that Q2E45 is *newer* than Q2F01 (other than this obscure Mavrothal post )?
• mplayer runs much slower than in 0.5.  I watch videos with mplayer all the time and it hardly ever lags except with very high-res video; now the video lags way behind the audio on all but a couple videos I've tried (all of which previously worked fine).  This persists whether the video is on a USB or saved on the NAND.

Is anybody else having similar troubles?  Does anybody know of a good way to report bugs without joining the entire OLPC devel mailing list?  Does dilinger ever put out updates between major releases?

The new release doesn't really seem to add much for me (as long as I resintall 0.5 every once in a while to keep disk seeks snappy, and keep the backports up to date) and so far has broken quite a bit, so unfortunately it looks like I'll be moving back to 0.5 for the time being.  If anyone has any suggestions, I'd appreciate it.

(I should also mention that despite dilinger's listed known bug, the battery meter seems to work more or less like it used to: that is, "cat /sys/devices/platform/olpc-battery.0/power_supply/olpc-battery/capacity" works fine!)

Thanks for the feedback!  I'm reachable via email ([email protected]), and occasionally I'll read forums (but not that often).


Regarding your bugs:

 

• Sounds like problems with the wireless driver.  Please report this to the OLPC and/or kernel folks!
• I've seen that as well, but haven't attempted to debug it yet.  It looked like a bug in wicd, but doesn't break any functionality, so I'm concentrating on the stuff that does for now.
• Yikes, that's bad!  I hadn't seen that before.  I'm working on the gamekeys now, which includes making sure the volume keys do the right thing.  I'm planning to do a 0.7 release in a month or two, with a bunch of bugfixes.
• I've seen that as well.  I assumed an Lxterminal or Lxwm4 bug, but it's not high priority for me.
• I don't know what the deal is with Q2F01; I wasn't even aware that it existed.
• This is the first I've heard of video problems.  Unfortunately, the xorg geode driver isn't really maintained or supported at the moment (and I have no desire to deal with it), so as new versions of xorg get released, we've been seeing regressions.  My long term plans include moving a bunch of the xorg geode hardware driver code into the kernel, which should allow us to delete lots of code and make it more.. sane.  I'm hoping that doing so fixes a lot of problems that the driver has historically had.

[fang2415]

Thanks for the feedback!  I'm reachable via email ([email protected]), and occasionally I'll read forums (but not that often).

Great, so glad you saw this!  If I spot more in the future I'll drop you an email (maybe after asking around here just to make sure I'm not missing something stupid).

• Sounds like problems with the wireless driver.  Please report this to the OLPC and/or kernel folks!
• I've seen that as well, but haven't attempted to debug it yet.  It looked like a bug in wicd, but doesn't break any functionality, so I'm concentrating on the stuff that does for now.

Crazily, after leaving the machine on overnight, both of these seem bugs seem to have gone away(!), at least for now...  How weird.  I'll try rebooting and see if I can figure out how to break it again and post back (and see about where to post a driver bug).  Otherwise I'll... just remain cautiously satisfied?

Yikes, that's bad!  I hadn't seen that before.  I'm working on the gamekeys now, which includes making sure the volume keys do the right thing.

Gamekeys are all working great for me as is; it would be cool if the volume and brightness keys worked as printed, and as F9-F12 when combined with "fn".

I'm planning to do a 0.7 release in a month or two, with a bunch of bugfixes.

That's fantastic news!  If I can work around these, I'll stick with 0.6 until then; otherwise I may switch back down to 0.5 as my everyday OS until something more polished is ready.  The goal of pushing stuff upstream sounds great either way.

• I've seen that as well.  I assumed an Lxterminal or Lxwm4 bug, but it's not high priority for me.

I am wondering if this is related to the F11 bug -- if Lxterminal is behaving badly anyway, maybe that's what's causing it to totally freak out in fullscreen mode?

• I don't know what the deal is with Q2F01; I wasn't even aware that it existed.

Yeah, mavrothal, this is what really threw me for a loop -- I searched the wiki for ages and couldn't find any info on why there's a release numbered ahead of the current one.  No idea how I got it in the first place, either.

• This is the first I've heard of video problems.  Unfortunately, the xorg geode driver isn't really maintained or supported at the moment (and I have no desire to deal with it), so as new versions of xorg get released, we've been seeing regressions.  My long term plans include moving a bunch of the xorg geode hardware driver code into the kernel, which should allow us to delete lots of code and make it more.. sane.  I'm hoping that doing so fixes a lot of problems that the driver has historically had.

Sounds great to me.  Upon further inspection, some of the problems seem less severe than I previously thought -- for example, one movie only lagged for the first few minutes and then caught up.  There certainly is some regression though, which is a shame: hope your solution will work out without too much grunt work on your end.


Not sure if you saw my comment on the laptop.org blog, but it can't hurt to reiterate it here: thanks a million for your work on this.  DebXO has made the XO into a real live laptop for me, and without all the cruft that too many distros toss in these days.  Please rest assured that at least one user *really* appreciates all the work you're doing for this project.  Great stuff.

[fang2415]

mplayer runs much slower than in 0.5.  I watch videos with mplayer all the time and it hardly ever lags except with very high-res video; now the video lags way behind the audio on all but a couple videos I've tried (all of which previously worked fine).  This persists whether the video is on a USB or saved on the NAND.

Uhh... and now this bug also seems to have resolved itself?  So maybe 0.6 just needs a day to warm up?

Restarting has restored the network-list bug, but both mplayer and wicd's "connected" messages are now running fine and dandy.  All the other bugs seem to persist, but I didn't check them all before restarting -- I guess I'll give it another day and try again?

Now leaving the Twilight Zone...  Anybody have any idea what would cause this kind of behavior?