Re: Some testing notes for OS10 for the XO-1
Hi Steven - The scratch sensor board doesn't work (works with build 802) I hoped allow olpc access to ttyUSB nodes (from release notes os10) would make it work. I added an extract of /var/log/messages at the bottom of the email. - timezone can not be changed in gnome since administration menu is missing (changing the timezone in sugar control panel has no effect in gnome). And talking about time, I think the clock activity is really nice and useful. - build information OLPC release 11 (Leonidas) in sugar control panel is more confusing than helpful. What about 10 (based on Fedora 11)? Does it boot consistently into Sugar? Gnome? Worked fine here. Does sound work? Yes,no problem. Can you suspend? Does it wake up? Suspend yes, but no proper wake up as mentioned by other testers (but the shutdown with the power button is really nice and useful). Regards, Philipp Plug in Scratch Sensor board with build 10 on Fedora 11: Dec 12 07:56:16 xo-11-08-d6 kernel: [ 88.687028] usb 1-2: new full speed USB device using ohci_hcd and address 2 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 88.908698] usb 1-2: configura tion #1 chosen from 1 choice Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere d new interface driver usbserial Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] USB Serial support registered for generic Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere d new interface driver usbserial_generic Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbserial: USB Ser ial Driver core Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162673] USB Serial support registered for pl2303 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162861] pl2303 1-2:1.0: pl 2303 converter detected Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185652] usb 1-2: pl2303 co nverter now attached to ttyUSB0 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185960] usbcore: registere d new interface driver pl2303 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185982] pl2303: Prolific P L2303 USB to serial adaptor driver Dec 12 07:56:17 xo-11-08-d6 NetworkManager: info (ttyUSB0): ignori ng due to lack of mobile broadband capabilties Plug in Scratch Sensor board with build 802 on Fedora 9: Dec 13 08:48:55 localhost kernel: [ 155.465098] hub_port_wait_reset: portstatus=501 portchange=10 Dec 13 08:48:55 localhost kernel: [ 155.536006] hub_port_wait_reset: portstatus=100 portchange=1 Dec 13 08:48:55 localhost kernel: [ 155.539599] hub_port_wait_reset: device went away! Dec 13 08:48:55 localhost kernel: [ 155.549596] hub 2-0:1.0: unable to enumerate USB device on port 2 Dec 13 08:48:55 localhost kernel: [ 155.831725] hub_port_wait_reset: portstatus=103 portchange=10 Dec 13 08:48:55 localhost kernel: [ 155.904029] usb 1-2: new full speed USB device using ohci_hcd and address 4 Dec 13 08:48:55 localhost kernel: [ 155.997296] hub_port_wait_reset: portstatus=103 portchange=10 Dec 13 08:48:56 localhost kernel: [ 156.077180] usb 1-2: configuration #1 chosen from 1 choice Dec 13 08:48:56 localhost kernel: [ 156.413019] usbcore: registered new interface driver usbserial Dec 13 08:48:56 localhost kernel: [ 156.417722] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic Dec 13 08:48:56 localhost kernel: [ 156.431937] usbcore: registered new interface driver usbserial_generic Dec 13 08:48:56 localhost kernel: [ 156.439535] drivers/usb/serial/usb-serial.c: USB Serial Driver core Dec 13 08:48:56 localhost kernel: [ 156.476346] drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303 Dec 13 08:48:56 localhost kernel: [ 156.479963] pl2303 1-2:1.0: pl2303 converter detected Dec 13 08:48:56 localhost kernel: [ 156.516365] usb 1-2: pl2303 converter now attached to ttyUSB0 Dec 13 08:48:56 localhost kernel: [ 156.522309] usbcore: registered new interface driver pl2303 Dec 13 08:48:56 localhost kernel: [ 156.536892] drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Problems with build 59
On Sat, 2009-12-12 at 23:43 -0800, Caryl Bigenho wrote: Hi... Downloaded Build 59 this evening and tried to flash the XO-1.5. It appeared to work perfectly, but could not complete restart at the end. The outline of the XO man appears and dots slowly begin to surround him, but it stalls about 2/3 of the way around the circle. How long did you wait? If you press ctrl+alt+mesh you will reach a text console, perhaps you could transcribe the lowest few lines of text at this point. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
updated olpc.fth for XO-1.5
Hi Richard,
Sorry to turn around on this -- we no longer want the XO-1.5-specific
kernel parameters in olpc.fth since we are now building them into the
kernel.
For future XO-1.5 bootfw releases please replace olpc.fth with the one
included here
This isn't critical - everything still works fine even if all the
parameters are duplicated, but it's something we should clean up
Thanks
Daniel
\ OLPC boot script
[ifndef] do-firmware-update
: do-firmware-update ( img$ -- )
\ Keep .error from printing an input sream position report
\ which makes a buffer@address show up in the error message
['] noop to show-error
visible
tuck flash-buf swap move ( len )
['] ?image-valid catch ?dup if( )
visible
red-letters
. Bad firmware image file - .error
. Continuing with old firmware cr
black-letters
exit
then
true to file-loaded?
d# 12,000 wait-until \ Wait for EC to notice the battery
['] ?enough-power catch ?dup if
visible
red-letters
. Unsafe to update firmware now - .error
. Continuing with old firmware cr
black-letters
exit
then
Updating firmware ?lease-debug-cr
ec-indexed-io-off? if
visible
. Restarting to enable SPI FLASH writing. cr
d# 3000 ms
ec-ixio-reboot
security-failure
then
\ Latch alternate? flag for next startup
alternate? if [char] A h# 82 cmos! then
reflash \ Should power-off and reboot
show-x
Reflash returned, unexpectedly .security-failure
;
[then]
[ifndef] ?ofw-reflash
\ Check for new firmware.
: ?ofw-reflash ( -- )
${DN}${PN}\bootfw.zip expand$
['] (boot-read) catch if 2drop exit then
img$ firmware-up-to-date? if exit then
img$ do-firmware-update
;
[then]
: set-path-macros ( -- )
button-o game-key? if \boot-alt else \boot then pn-buf place
/chosen find-package if ( phandle )
bootpath rot get-package-property 0= if ( propval$ )
get-encoded-string ( bootpath$ )
[char] \ left-parse-string 2nip( dn$ )
dn-buf place( )
then
then
;
: olpc-fth-boot-me
set-path-macros
?ofw-reflash
console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22 expand$ to
boot-file
${DN}${PN}\vmlinuzexpand$ to boot-device
${DN}${PN}\initrd.img expand$ to ramdisk
boot
;
olpc-fth-boot-me
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: updated olpc.fth for XO-1.5
On 12/13/2009 06:54 AM, Daniel Drake wrote: Hi Richard, Sorry to turn around on this -- we no longer want the XO-1.5-specific kernel parameters in olpc.fth since we are now building them into the kernel. Ok. Great. I'm going to release a firmware tonight so I'll add this in. -- Richard A. Smith rich...@laptop.org One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Some testing notes for OS10 for the XO-1
Hi, Steven. The USB-serial cable that comes with the Scratch Sensor board needs a driver from Prolifix. That driver used to be included in the builds, but perhaps it was accidentally dropped? If you use a supported USB-serial adaptor cable, then I think the ScratchBoard will work. I just got a report that sound playback is rough on XO 1.5: http://dev.laptop.org/ticket/9375 I'm guessing this is caused by a switch from ALSA to PulseAudio. We've seen that on Ubuntu; we still working to resolve the problem. PulseAudio itself has some buffering issues, although it appears that folks are working on those. The problems tend to show up more in applications where sounds are triggered dynamically, such as Scratch, EToys, and games, vs. playing music. -- John On Dec 13, 2009, at 4:00 AM, Philipp Kocher wrote: Hi Steven - The scratch sensor board doesn't work (works with build 802) I hoped allow olpc access to ttyUSB nodes (from release notes os10) would make it work. I added an extract of /var/log/messages at the bottom of the email. - timezone can not be changed in gnome since administration menu is missing (changing the timezone in sugar control panel has no effect in gnome). And talking about time, I think the clock activity is really nice and useful. - build information OLPC release 11 (Leonidas) in sugar control panel is more confusing than helpful. What about 10 (based on Fedora 11)? Does it boot consistently into Sugar? Gnome? Worked fine here. Does sound work? Yes,no problem. Can you suspend? Does it wake up? Suspend yes, but no proper wake up as mentioned by other testers (but the shutdown with the power button is really nice and useful). Regards, Philipp Plug in Scratch Sensor board with build 10 on Fedora 11: Dec 12 07:56:16 xo-11-08-d6 kernel: [ 88.687028] usb 1-2: new full speed USB device using ohci_hcd and address 2 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 88.908698] usb 1-2: configura tion #1 chosen from 1 choice Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere d new interface driver usbserial Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] USB Serial support registered for generic Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere d new interface driver usbserial_generic Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbserial: USB Ser ial Driver core Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162673] USB Serial support registered for pl2303 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162861] pl2303 1-2:1.0: pl 2303 converter detected Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185652] usb 1-2: pl2303 co nverter now attached to ttyUSB0 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185960] usbcore: registere d new interface driver pl2303 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185982] pl2303: Prolific P L2303 USB to serial adaptor driver Dec 12 07:56:17 xo-11-08-d6 NetworkManager: info (ttyUSB0): ignori ng due to lack of mobile broadband capabilties Plug in Scratch Sensor board with build 802 on Fedora 9: Dec 13 08:48:55 localhost kernel: [ 155.465098] hub_port_wait_reset: portstatus=501 portchange=10 Dec 13 08:48:55 localhost kernel: [ 155.536006] hub_port_wait_reset: portstatus=100 portchange=1 Dec 13 08:48:55 localhost kernel: [ 155.539599] hub_port_wait_reset: device went away! Dec 13 08:48:55 localhost kernel: [ 155.549596] hub 2-0:1.0: unable to enumerate USB device on port 2 Dec 13 08:48:55 localhost kernel: [ 155.831725] hub_port_wait_reset: portstatus=103 portchange=10 Dec 13 08:48:55 localhost kernel: [ 155.904029] usb 1-2: new full speed USB device using ohci_hcd and address 4 Dec 13 08:48:55 localhost kernel: [ 155.997296] hub_port_wait_reset: portstatus=103 portchange=10 Dec 13 08:48:56 localhost kernel: [ 156.077180] usb 1-2: configuration #1 chosen from 1 choice Dec 13 08:48:56 localhost kernel: [ 156.413019] usbcore: registered new interface driver usbserial Dec 13 08:48:56 localhost kernel: [ 156.417722] drivers/usb/serial/ usb-serial.c: USB Serial support registered for generic Dec 13 08:48:56 localhost kernel: [ 156.431937] usbcore: registered new interface driver usbserial_generic Dec 13 08:48:56 localhost kernel: [ 156.439535] drivers/usb/serial/ usb-serial.c: USB Serial Driver core Dec 13 08:48:56 localhost kernel: [ 156.476346] drivers/usb/serial/ usb-serial.c: USB Serial support registered for pl2303 Dec 13 08:48:56 localhost kernel: [ 156.479963] pl2303 1-2:1.0: pl2303 converter detected Dec 13 08:48:56 localhost kernel: [ 156.516365] usb 1-2: pl2303 converter now attached to ttyUSB0 Dec 13 08:48:56 localhost kernel: [ 156.522309] usbcore: registered new interface driver pl2303 Dec 13 08:48:56 localhost kernel: [ 156.536892] drivers/usb/serial/ pl2303.c: Prolific PL2303 USB to serial adaptor driver
Re: possible progress on XO-1 camera issues
On Sat, Dec 12, 2009 at 8:16 PM, Daniel Drake d...@laptop.org wrote: Hi, Jon Corbet's been working on the XO-1.5 camera driver for us, and while doing so he found a V4L2 bug which is probably one of the reasons that we're having problems with XO-1 camera on all post-8.2 builds. The workaround is to build the sensor driver into the kernel, and the camera driver as a module. I've made the equivalent change for the kernel that has been built here: http://xs-dev.laptop.org/~dsd/repos/f11-xo1/kernel-2.6.31_xo1-20091211.1834.1.olpc.813348c.i586.rpm Untested, just wanted to get the word out. Note that you may have to load the camera driver (cafe_ccic) manually, if it doesn't automatically get loaded. Word is going round that on a SoaS build for XO (which uses something close to OLPC's 2.6.30 kernel, I think), someone recently managed to capture a photo from the command line. If someone is up for a small task, it would be good to start changing these words going round to some actual solid information. Anyone want to head up these efforts and to start http://wiki.laptop.org/go/Reviving_XO1_camera ? At the very least it would be nice to have some solid documentation on where the problem is (and isn't). Is it in ov7670, cafe_ccic, v4l2, gstreamer, xf86-video-geode, or..? How can you tell? Does the above kernel help? What's the exact command you can use on F12 SoasXO to take a photo? What's the corresponding error if you do that on F11? etc. I got it working just fine on SoaS beta 4 build for the XO using a gstreamer pipeline. I was taking .png still images with out issue. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New F11 for XO-1.5 build 60
http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os60 Compressed image size: 703.93mb (+3.12mb since build 59) Description of changes in this build: * New firmware Q3A23 * New release of manufacturing run-in tests Package changes since build 59: -bootfw-q3a20-1.unsigned.i386 +bootfw-q3a23-1.unsigned.i386 -md5deep-3.4-1.fc11.i586 -olpc-runin-tests-0.2-1.noarch +olpc-runin-tests-0.2-2.noarch +xterm-242-3.fc11.i586 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Hi SGers... I thought I might try helping test the F11 Build 10 on an XO-1. I have one that had a developer key way back in the summer of 2008. I have reflashed the machine numerous times as software updates have arrived... using the No-fail Update, which I thought was supposed to erase everything. Tonight, when I turned the machine on, I pressed the escape key just for fun to see what would happen. It went to the same ok prompt I get on the XO-1.5 O am testing. Did the developer key persist through the numerous reflashings the machine has endured in the past year or so or do I need to go pick it up again? Caryl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
TamTam Mini Quirks In Build 56
Hi... I have been playing with Tam Tam Mini in build 56. After playing for a while it will not allow the machine to go home! You can access the Journal and go to the Activities previously opened (including Tam Tam Mini) but there is no way to get back to the home screen. You have to do a force quit with the power button. I have checked to see if this was a special occurrence but I got it to happen 3 times total and have no doubt that it will happen again. Each time, I selected a drum set and instrument. Then I just kept playing with the notes and loops for several minutes. After just a minute or 2, I could still access the home page, but after I kept playing for maybe 5 minutes or so... it would no longer go to home. I tried this on an XO-1 just to see if it was an old bug. A few funny things happened there, but I was always able to get back to the home screen on the XO-1 but not on the XO-1.5. BTW, I didn't realize that Tam Tam Mini had melodic loops available on the keys that aren't assigned to specific notes. Really cool! Lots of fun! Caryl P.S. The build 59 download just finished. I'll install it now. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Problems with build 59
Hi... Downloaded Build 59 this evening and tried to flash the XO-1.5. It appeared to work perfectly, but could not complete restart at the end. The outline of the XO man appears and dots slowly begin to surround him, but it stalls about 2/3 of the way around the circle. I tried to install it twice. Same results. Maybe it is a faulty download. If you think it may be, I can download it and try again tomorrow. Caryl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: [support-gang] Problems with build 59
Hi... I waited about an hour. Then I decided to try one more time before re-doing the download. I started the process and went to bed (11:30 pm). This morning I found it had installed correctly and is now running and ready to test. No idea why the first try stalled like that. Caryl From: d...@laptop.org To: support-g...@lists.laptop.org Date: Sun, 13 Dec 2009 11:40:56 + CC: c...@laptop.org; devel@lists.laptop.org; support-g...@laptop.org Subject: Re: [support-gang] Problems with build 59 On Sat, 2009-12-12 at 23:43 -0800, Caryl Bigenho wrote: Hi... Downloaded Build 59 this evening and tried to flash the XO-1.5. It appeared to work perfectly, but could not complete restart at the end. The outline of the XO man appears and dots slowly begin to surround him, but it stalls about 2/3 of the way around the circle. How long did you wait? If you press ctrl+alt+mesh you will reach a text console, perhaps you could transcribe the lowest few lines of text at this point. Thanks, Daniel ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [olpc-nz] Testing summary - 12 December 2009 Wellington, NZ
We did not disable suspend before testing, all these observations were made on a fresh boot while plugged into AC power with no suspending. The wireless just didn't seem to activate at all. When checking 'ifconfig -a' the only device shown was the local loopback device 'lo'. -Alastair On Sat, Dec 12, 2009 at 2:11 PM, James Cameron qu...@laptop.org wrote: On Sat, Dec 12, 2009 at 01:40:04PM +1300, Tabitha Roder wrote: On all XO 1.5s we updated to OS54 wifi does not work (except on 1 of 5 machines showed wireless connections for about 20 seconds then gone) although we now realise there is OS56 so maybe we need to just update again. You probably hit the known problem described in the release candidate announcement If you have a B2 without hardware mods, you must disable suspend using Control Panel-Power-Automatic power management, else your wireless device will disconnect on suspend and not come back until the next reboot. Can you confirm that you did not disable suspend before testing wireless? -- James Cameron http://quozl.linux.org.au/ ___ olpc-nz mailing list olpc...@lists.laptop.org http://lists.laptop.org/listinfo/olpc-nz ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [olpc-nz] Testing summary - 12 December 2009 Wellington, NZ
G'day Alastair, Thanks for responding. I'd like to drill down further into the facts just to make sure we're not missing anything. On Mon, Dec 14, 2009 at 09:19:19AM +1300, Alastair Munro wrote: We did not disable suspend before testing, all these observations were made on a fresh boot while plugged into AC power with no suspending. You did not disable suspend, yet there was no suspending at all? That's surprising. The design since about build os49 is that dim screen with begin at about 15 seconds and suspend will begin at about 25 seconds of idle. The suspend doesn't turn off the screen, so you might not notice it. The power LED begins to blink at about a five second rate. Can you confirm that you keep the keyboard and touchpad active, and never idle for more than 30 seconds? It is very hard to do that, especially with other people interrupting. The wireless just didn't seem to activate at all. When checking 'ifconfig -a' the only device shown was the local loopback device 'lo'. This is quite consistent with not knowing that an automatic idle suspend has happened. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Some testing notes for OS10 for the XO-1
On Fri, Dec 11, 2009 at 7:55 PM, Steven M. Parrish smparr...@gmail.com wrote: If you are going to try out OS10 for the XO-1 here are a few things that need testing. Here are my test results on a XO-1 B4. Does it boot consistently into Sugar? Gnome? Working with Sugar. A flash on screen during booting of kernel. There is almost no gray frame when launching activities. Any strange lockups? If so what were you doing? Problem after resuming from suspend. Strange behavior on audio recording related parts. Can you upgrade packages using yum update from the command line? This time yum works great. The out-of-memory problem on OS8 seems fixed here. Does sound work? Playing works on all related activities. Recording at measure sometimes locks up. Working well in record. Can you suspend? Does it wake up? Suspend works but keyboard/mouse no response when resumed. If push power button to sleep, touching mouse and keyboard does make power LED flash. Press power button again resumes but still no keyboard/mouse. Please report any issues you have. When booting, mic LED becomes normal. (used to stay on till HAL loaded) Stop in lots of activities becomes down arrow. (insufficient space?) Power setting still not persistent. (OS8) Droid font works great on CJK web browsing. Scrolling is still broken. (OS8) Web cam video doesn't work. Browser scroll bar shows strange pattern when font-size enlarged. Chinese translations works well. Terminal font is too large. Can be fixed by setting font size in /home/olpc/.sugar/default/terminalrc (was set in OS8) Booting and (especially) shutdown speed up. GnomePowerManager can't get battery info. No firefox installed under Gnome, but default browser is set to FF. Midori is great, but need to set proper font first. Otherwise, font display will be very slow, especially for CJK contents. (same for FF3) -- Best regards, Yuan Chao ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Some testing notes for OS10 for the XO-1
The Prolific driver gets loaded (see logs at the bottom). The problem are the permissions. After plugging in the scratch board ll /dev/ttyUSB0 shows: crw-rw 1 root dialout 188, 0 2009-12-14 09:52 /dev/ttyUSB0 User olpc is not in group dialout which means it doesn't have access to ttyUSB0. After adding olpc to group dialout the scratch board works fine. Regards, Philipp On 12/13/2009 11:17 PM, John Maloney wrote: Hi, Steven. The USB-serial cable that comes with the Scratch Sensor board needs a driver from Prolifix. That driver used to be included in the builds, but perhaps it was accidentally dropped? If you use a supported USB-serial adaptor cable, then I think the ScratchBoard will work. I just got a report that sound playback is rough on XO 1.5: http://dev.laptop.org/ticket/9375 I'm guessing this is caused by a switch from ALSA to PulseAudio. We've seen that on Ubuntu; we still working to resolve the problem. PulseAudio itself has some buffering issues, although it appears that folks are working on those. The problems tend to show up more in applications where sounds are triggered dynamically, such as Scratch, EToys, and games, vs. playing music. -- John On Dec 13, 2009, at 4:00 AM, Philipp Kocher wrote: Hi Steven - The scratch sensor board doesn't work (works with build 802) I hoped allow olpc access to ttyUSB nodes (from release notes os10) would make it work. I added an extract of /var/log/messages at the bottom of the email. - timezone can not be changed in gnome since administration menu is missing (changing the timezone in sugar control panel has no effect in gnome). And talking about time, I think the clock activity is really nice and useful. - build information OLPC release 11 (Leonidas) in sugar control panel is more confusing than helpful. What about 10 (based on Fedora 11)? Does it boot consistently into Sugar? Gnome? Worked fine here. Does sound work? Yes,no problem. Can you suspend? Does it wake up? Suspend yes, but no proper wake up as mentioned by other testers (but the shutdown with the power button is really nice and useful). Regards, Philipp Plug in Scratch Sensor board with build 10 on Fedora 11: Dec 12 07:56:16 xo-11-08-d6 kernel: [ 88.687028] usb 1-2: new full speed USB device using ohci_hcd and address 2 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 88.908698] usb 1-2: configura tion #1 chosen from 1 choice Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere d new interface driver usbserial Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] USB Serial support registered for generic Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere d new interface driver usbserial_generic Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbserial: USB Ser ial Driver core Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162673] USB Serial support registered for pl2303 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162861] pl2303 1-2:1.0: pl 2303 converter detected Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185652] usb 1-2: pl2303 co nverter now attached to ttyUSB0 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185960] usbcore: registere d new interface driver pl2303 Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185982] pl2303: Prolific P L2303 USB to serial adaptor driver Dec 12 07:56:17 xo-11-08-d6 NetworkManager: info (ttyUSB0): ignori ng due to lack of mobile broadband capabilties Plug in Scratch Sensor board with build 802 on Fedora 9: Dec 13 08:48:55 localhost kernel: [ 155.465098] hub_port_wait_reset: portstatus=501 portchange=10 Dec 13 08:48:55 localhost kernel: [ 155.536006] hub_port_wait_reset: portstatus=100 portchange=1 Dec 13 08:48:55 localhost kernel: [ 155.539599] hub_port_wait_reset: device went away! Dec 13 08:48:55 localhost kernel: [ 155.549596] hub 2-0:1.0: unable to enumerate USB device on port 2 Dec 13 08:48:55 localhost kernel: [ 155.831725] hub_port_wait_reset: portstatus=103 portchange=10 Dec 13 08:48:55 localhost kernel: [ 155.904029] usb 1-2: new full speed USB device using ohci_hcd and address 4 Dec 13 08:48:55 localhost kernel: [ 155.997296] hub_port_wait_reset: portstatus=103 portchange=10 Dec 13 08:48:56 localhost kernel: [ 156.077180] usb 1-2: configuration #1 chosen from 1 choice Dec 13 08:48:56 localhost kernel: [ 156.413019] usbcore: registered new interface driver usbserial Dec 13 08:48:56 localhost kernel: [ 156.417722] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic Dec 13 08:48:56 localhost kernel: [ 156.431937] usbcore: registered new interface driver usbserial_generic Dec 13 08:48:56 localhost kernel: [ 156.439535] drivers/usb/serial/usb-serial.c: USB Serial Driver core Dec 13 08:48:56 localhost kernel: [ 156.476346] drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303 Dec 13 08:48:56 localhost kernel: [ 156.479963] pl2303 1-2:1.0: pl2303 converter detected Dec 13 08:48:56 localhost kernel: [
Re: TamTam Mini Quirks In Build 56
G'day Caryl, That problem sounded interesting, so I tested it myself. I couldn't get it to happen. I was using os60, and I don't think anything relevant was changed between os56 and os60. I wondered if I was trying to do the same thing you were. Could you tell me what action you do to go home? Do you mean pressing the Home View or F3 (single green dot in solid green circle) key above the 4 key? Or Alt/Tab? Or Ctrl/Q? Was an external keyboard attached to the laptop? Were you holding down any of the modifier keys ... the ctrl, shift, fn, alt, alt gr, or shift keys? The Home View key surprisingly doesn't work if any of those are active. If you can get it to happen again, could you tell me if any of the following fixes the symptom without having to restart: 1. Alt/Tab (which should switch to the Journal or any other running activity), 2. Ctrl/Q (which should quit the Tam Tam Mini activity), 3. clicking on the Stop icon at the top right, 4. Ctrl/Alt/Erase (which should restart Sugar only without restarting the operating system), 5. pressing each of the modifier keys once and then releasing them before you try the Home View key. (this would imply a key state is incorrectly latching, something we've seen before after a resume from idle suspend, but we thought we fixed it). -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: TamTam Mini Quirks In Build 56
Hi James, I'll fill in my responses in your message. Boy! These builds come along fast. I haven't had time to test 59 yet and 60 is here already! Is there supposed to be a firmware update along with 60? It was mentioned in the email Adam forwarded, but there was no link. Caryl Date: Mon, 14 Dec 2009 14:55:43 +1100 From: qu...@laptop.org To: cbige...@hotmail.com CC: devel@lists.laptop.org; support-g...@laptop.org Subject: Re: TamTam Mini Quirks In Build 56 G'day Caryl, That problem sounded interesting, so I tested it myself. I couldn't get it to happen. I was using os60, and I don't think anything relevant was changed between os56 and os60. I wondered if I was trying to do the same thing you were. I'll try it again. Right now I have 59 installed so I'll use it. I will also time it to see how long it takes to happen. It may be longer than I thought. Could you tell me what action you do to go home? Do you mean pressing the Home View or F3 (single green dot in solid green circle) key above the 4 key? Or Alt/Tab? Or Ctrl/Q? First I clicked on the stop sign icon. That took me to the Journal. I tried the F3 key to go home. It didn't work. From the Journal I was able to get back to TamTam and to the other Activities in the Journal, but when they were closed I ended up back in the Journal. I was locked in! Was an external keyboard attached to the laptop? No, just the laptop. I hope someday a small piano-type will be able to interface with the XO. Were you holding down any of the modifier keys ... the ctrl, shift, fn, alt, alt gr, or shift keys? The Home View key surprisingly doesn't work if any of those are active. No, just the Home View key If you can get it to happen again, could you tell me if any of the following fixes the symptom without having to restart: I'll check it out and let you know one way or another what happens. 1. Alt/Tab (which should switch to the Journal or any other running activity), 2. Ctrl/Q (which should quit the Tam Tam Mini activity), 3. clicking on the Stop icon at the top right, 4. Ctrl/Alt/Erase (which should restart Sugar only without restarting the operating system), 5. pressing each of the modifier keys once and then releasing them before you try the Home View key. (this would imply a key state is incorrectly latching, something we've seen before after a resume from idle suspend, but we thought we fixed it). -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam Mini Quirks In Build 56
On Sun, Dec 13, 2009 at 08:35:24PM -0800, Caryl Bigenho wrote: Is there supposed to be a firmware update along with 60? It was mentioned in the email Adam forwarded, but there was no link. Yes, it is included in the build now, and when you next reboot with battery and external power it will be applied. First I clicked on the stop sign icon. That took me to the Journal. I tried the F3 key to go home. It didn't work. From the Journal I was able to get back to TamTam and to the other Activities in the Journal, but when they were closed I ended up back in the Journal. I was locked in! Okay, thanks, that's a better description of the symptom. Interesting. Seems to be related only to Sugar, based on the available information. I'll check it out and let you know one way or another what happens. Thanks! -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: TamTam Mini Quirks In Build 56
OK. Tried it again with build 59. This time it was different. I played with it for about 40 mins with no problems until the sound quit! I tried it in TamTam Jam... no sound. I tried it in Speak... no sound. Rebooted... sound was fine! This is probably an interesting problem that isn't a problem. How many people are going to play with Tam Tam Mini for 40 minutes? Probably not many. And if they do manage to crash the sound, they can just reboot. So, I'll download build 60 now and see what other things I can get to crash! Caryl Date: Mon, 14 Dec 2009 15:47:43 +1100 From: qu...@laptop.org To: cbige...@hotmail.com CC: devel@lists.laptop.org; support-g...@laptop.org Subject: Re: TamTam Mini Quirks In Build 56 On Sun, Dec 13, 2009 at 08:35:24PM -0800, Caryl Bigenho wrote: Is there supposed to be a firmware update along with 60? It was mentioned in the email Adam forwarded, but there was no link. Yes, it is included in the build now, and when you next reboot with battery and external power it will be applied. First I clicked on the stop sign icon. That took me to the Journal. I tried the F3 key to go home. It didn't work. From the Journal I was able to get back to TamTam and to the other Activities in the Journal, but when they were closed I ended up back in the Journal. I was locked in! Okay, thanks, that's a better description of the symptom. Interesting. Seems to be related only to Sugar, based on the available information. I'll check it out and let you know one way or another what happens. Thanks! -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Some testing notes for OS10 for the XO-1
Switching off pm doesn't work (with control panel GUI or command): [o...@xo-11-08-d6 logs]$ sugar-control-panel -s automatic_pm off /usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha sugar-control-panel: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ohm was not provided by any .service files After starting ohmd with sudo service ohmd start (per default service ohmd is off for all runlevels) it is possible to switch off automatic_pm (at least no error anymore), but it still suspends after some time and with resume is the same problem as before. Is ohmd supposed to be on or off? On 12/12/2009 01:55 AM, Steven M. Parrish wrote: If you are going to try out OS10 for the XO-1 here are a few things that need testing. Does it boot consistently into Sugar? Gnome? Any strange lockups? If so what were you doing? Can you upgrade packages using yum update from the command line? Does sound work? Can you suspend? Does it wake up? Please report any issues you have. Steven ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Some testing notes for OS10 for the XO-1
smparrish will correct me if i'm wrong, but i believe the release you're testing runs powerd, not ohmd. the presence of the control panel, and its inability to control powerd's behavior, is a bug, or an unimplemented feature -- take your pick. (you can disable powerd if you wish, with initctl stop powerd, and move /etc/events.d/powerd elsewhere. then start ohmd as you did below.) i'm curious about the keyboard/mouse not waking things up properly, but i have zero time to look at it currently. to prevent powerd from suspending the laptop, edit /etc/powerd/powerd.conf, and adjust the timeout s to something big, like 9. paul philipp wrote: Switching off pm doesn't work (with control panel GUI or command): [o...@xo-11-08-d6 logs]$ sugar-control-panel -s automatic_pm off /usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha sugar-control-panel: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ohm was not provided by any .service files After starting ohmd with sudo service ohmd start (per default service ohmd is off for all runlevels) it is possible to switch off automatic_pm (at least no error anymore), but it still suspends after some time and with resume is the same problem as before. Is ohmd supposed to be on or off? On 12/12/2009 01:55 AM, Steven M. Parrish wrote: If you are going to try out OS10 for the XO-1 here are a few things that need testing. Does it boot consistently into Sugar? Gnome? Any strange lockups? If so what were you doing? Can you upgrade packages using yum update from the command line? Does sound work? Can you suspend? Does it wake up? Please report any issues you have. Steven ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
