Re: possible progress on XO-1 camera issues
On Wed, Dec 16, 2009 at 7:36 PM, César D. Rodas wrote: > Hi, > > The problem with the camera seems to be the xf86-video-geode package. > The cafe_ccic module is loaded automatically. Cheese and recordactivity > crashed right before show any picture. Then I tested remotely with ssh > -X and it worked for olpc and root user and it works. > > This test was done with: > > * XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0 > * os10 > > Even if it works remotely, there are a lots of warning messages on > the /var/log/messages: The gstreamer pipeline i used on the command line to take a photo is: gst-launch-0.10 v4l2src ! ffmpegcolorspace ! pngenc ! filesink location=foo.png It basically takes png file. Regards, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
Hello Peter, On Thu, 2009-12-17 at 08:45 +, Peter Robinson wrote: > On Wed, Dec 16, 2009 at 7:36 PM, César D. Rodas > wrote: > > Hi, > > > > The problem with the camera seems to be the xf86-video-geode package. > > The cafe_ccic module is loaded automatically. Cheese and recordactivity > > crashed right before show any picture. Then I tested remotely with ssh > > -X and it worked for olpc and root user and it works. > > > > This test was done with: > > > > * XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0 > > * os10 > > > > Even if it works remotely, there are a lots of warning messages on > > the /var/log/messages: > > The gstreamer pipeline i used on the command line to take a photo is: > > gst-launch-0.10 v4l2src ! ffmpegcolorspace ! pngenc ! filesink > location=foo.png It works perfectly fine, thanks for your help. It seems to be that X is having a hard time displaying the video feed for some reason I can't discover (yet). I took a look at the /var/log/Xorg.0.log file (while attempting to run cheese) and it said: "Could not allocate memory for the video" That's why it worked remotely before (apparently). I also tried loading extra modules in xorg.conf (the ones that are loaded in the XO-1.5 config) but no go. I'm looking forward to read clues about how to fix it. Regards, > > It basically takes png file. > > Regards, > Peter > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
secure boot- Can't mount root filesystem. Was: Problem with dracut-modules-olpc-0.2.4
Hi Daniel, I'm testing secure boot in F11-XO1 (os10). When XO boots in secure boot the lease file doesn't read from USB key. I disabled the activation in dracut and I reinstalled dracut-olpc-modules and kernel and I signed them. This log is displayed when I turn on the XO: [2.907314] brd: module loaded [2.920838] NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit) [2.931270] 2 NAND chips detected [2.947938] cmdlinepart partition parsing not available [2.954239] Searching for RedBoot partition table in NAND 512MiB 3,3V 8-bit at offset 0x0 [2.970343] No RedBoot partition table detected in NAND 512MiB 3,3V 8-bit [2.996908] serio: i8042 KBD port at 0x60,0x64 irq 1 [3.002587] serio: i8042 AUX port at 0x60,0x64 irq 12 [3.015428] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [3.023061] rtc0: alarms up to one year, y3k, 242 bytes nvram [3.042876] olpc-dcon: Discovered DCON version 2 [3.063808] Linux video capture interface: v2.00 [3.153404] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 [3.176771] geode-mfgpt: Registered timer 1 [3.196556] cpuidle: using governor ladder [3.214714] cpuidle: using governor menu [3.233455] sdhci: Secure Digital Host Controller Interface driver [3.254585] sdhci: Copyright(c) Pierre Ossman [3.274389] sdhci-pci :00:0c.1: SDHCI controller found [11ab:4101] (rev 10) [3.298023] sdhci-pci :00:0c.1: enabling device ( -> 0002) [3.320869] sdhci-pci :00:0c.1: Invalid iomem size. You may experience problems. [3.347109] Registered led device: mmc0:: [3.369713] sdhci_set_ios: power off for mmc0 from c05edf11 [3.393872] mmc0: SDHCI controller on PCI [:00:0c.1] using DMA [3.419604] sdhci_set_power: new power value = 14 [3.451202] Error allocating fallback algo aes [3.475808] alg: cipher: Failed to load transform for geode-aes: -2 [3.506283] sdhci_set_ios: power off for mmc0 from c05edf11 [3.512867] sdhci_set_power: new power value = 0 [3.573197] Error allocating fallback algo ecb(aes) [3.599878] alg: skcipher: Failed to load transform for ecb-aes-geode: -2 [3.628861] geode-aes: GEODE AES engine enabled. [3.658194] Advanced Linux Sound Architecture Driver Version 1.0.20. [3.691906] Failure reading codec reg 0x7e,Last value=0x7e805368 [3.720509] Failure reading codec reg 0x7e,Last value=0x7e805368 [3.760685] ALSA device list: [3.785201] #0: CS5535 Audio cs5535audio at 0x1480, irq 5 [3.813040] TCP bic registered [3.836955] Initializing XFRM netlink socket [3.862716] NET: Registered protocol family 10 [3.889465] lo: Disabled Privacy Extensions [3.914247] Mobile IPv6 [3.936307] NET: Registered protocol family 17 [3.967423] Freeing unused kernel memory: 236k freed [3.993617] Write protecting the kernel text: 2748k [4.018837] Write protecting the kernel read-only data: 860k [4.304065] udev: starting version 141 [5.249895] usbcore: registered new interface driver usbfs [5.329162] usbcore: registered new interface driver hub [5.482006] usbcore: registered new device driver usb [5.640157] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [5.792094] ehci_hcd :00:0f.5: EHCI Host Controller [5.831828] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [5.985996] ehci_hcd :00:0f.5: new USB bus registered, assigned bus number 1 [6.190320] ehci_hcd :00:0f.5: irq 10, io mem 0xfe01b000 [6.310419] ehci_hcd :00:0f.5: USB 2.0 started, EHCI 1.00 [6.470063] usb usb1: configuration #1 chosen from 1 choice [6.477142] hub 1-0:1.0: USB hub found [6.477296] hub 1-0:1.0: 4 ports detected [6.478027] ohci_hcd :00:0f.4: OHCI Host Controller [6.478143] ohci_hcd :00:0f.4: new USB bus registered, assigned bus number 2 [6.478281] ohci_hcd :00:0f.4: irq 10, io mem 0xfe01a000 [6.479896] modprobe used greatest stack depth: 2580 bytes left [6.761140] usb usb2: configuration #1 chosen from 1 choice [6.762237] hub 2-0:1.0: USB hub found [6.762333] hub 2-0:1.0: 4 ports detected [7.050043] usb 1-1: new high speed USB device using ehci_hcd and address 2 [7.099360] mount used greatest stack depth: 2492 bytes left [7.266896] usb 1-1: configuration #1 chosen from 1 choice [7.320473] lib80211: common routines for IEEE802.11 drivers [7.440085] usb 1-1: firmware: requesting usb8388.bin [8.213968] usb8xxx: Firmware ready event received [8.235737] libertas: 00:17:c4:0c:d8:34, fw 5.110.22p23, cap 0x03a3 [8.279072] libertas: eth0: Marvell WLAN 802.11 adapter [8.281592] libertas: PREP_CMD: command 0x0074 failed: 2 [8.281613] usb8xxx: Firmware does not seem to support PS mode [8.287666] usbcore: registered new interface driver usb8xxx mount: you must specify the filesystem type Can't mount root filesystem
Re: secure boot- Can't mount root filesystem. Was: Problem with dracut-modules-olpc-0.2.4
On Thu, 2009-12-17 at 11:40 -0200, Esteban Bordón wrote: > Hi Daniel, > > I'm testing secure boot in F11-XO1 (os10). > > When XO boots in secure boot the lease file doesn't read from USB key. > I disabled the activation in dracut and I reinstalled > dracut-olpc-modules and kernel and I signed them. You'll need the latest version of dracut-modules-olpc for activation to work. > [8.281613] usb8xxx: Firmware does not seem to support PS mode > [8.287666] usbcore: registered new interface driver usb8xxx > > mount: you must specify the filesystem type > > Can't mount root filesystem > > Boot has failed, sleepeng forever I'll need your help debugging/fixing this. At the moment my work time is fully occupied by XO-1.5 and I don't have any spare time to dedicate. My first suggestion would be to insert echo debug statements throughout the initramfs code so that you can understand what is going on. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: secure boot- Can't mount root filesystem. Was: Problem with dracut-modules-olpc-0.2.4
I forgot tell you, I'm working with the latest version of dracut-olpc-modules (0.3.2). I'll try do something with this. Regards. 2009/12/17 Daniel Drake > On Thu, 2009-12-17 at 11:40 -0200, Esteban Bordón wrote: > > Hi Daniel, > > > > I'm testing secure boot in F11-XO1 (os10). > > > > When XO boots in secure boot the lease file doesn't read from USB key. > > I disabled the activation in dracut and I reinstalled > > dracut-olpc-modules and kernel and I signed them. > > You'll need the latest version of dracut-modules-olpc for activation to > work. > > > [8.281613] usb8xxx: Firmware does not seem to support PS mode > > [8.287666] usbcore: registered new interface driver usb8xxx > > > > mount: you must specify the filesystem type > > > > Can't mount root filesystem > > > > Boot has failed, sleepeng forever > > I'll need your help debugging/fixing this. At the moment my work time is > fully occupied by XO-1.5 and I don't have any spare time to dedicate. My > first suggestion would be to insert echo debug statements throughout the > initramfs code so that you can understand what is going on. > > Daniel > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
Hi César, >> > The problem with the camera seems to be the xf86-video-geode package. >> > The cafe_ccic module is loaded automatically. Cheese and recordactivity >> > crashed right before show any picture. Then I tested remotely with ssh >> > -X and it worked for olpc and root user and it works. >> > >> > This test was done with: >> > >> > * XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0 >> > * os10 >> > >> > Even if it works remotely, there are a lots of warning messages on >> > the /var/log/messages: >> >> The gstreamer pipeline i used on the command line to take a photo is: >> >> gst-launch-0.10 v4l2src ! ffmpegcolorspace ! pngenc ! filesink >> location=foo.png > It works perfectly fine, thanks for your help. > > It seems to be that X is having a hard time displaying the video feed > for some reason I can't discover (yet). I took a look at > the /var/log/Xorg.0.log file (while attempting to run cheese) and it > said: > > "Could not allocate memory for the video" > > That's why it worked remotely before (apparently). I also tried loading > extra modules in xorg.conf (the ones that are loaded in the XO-1.5 > config) but no go. > > I'm looking forward to read clues about how to fix it. It sounds suspiciously like a Xv issue. That could be anything from a missing kernel module to a X driver bug. Out of interest can you play video using totem? Possibly record a video using a XO-1 with the working 802 build and see if it will play on one with the F11 build. That would rule out that issue, or possibly we could craft up a gstreamer pipeline that takes the output of the camera and displays it on the screen. Let me know how you go with the totem test and then we'll see where we can take it from there, if that works I can work out what the pipeline would need to be to test that raw. Regards, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
Hi Peter, On Thu, 2009-12-17 at 14:18 +, Peter Robinson wrote: > Hi César, > > >> > The problem with the camera seems to be the xf86-video-geode package. > >> > The cafe_ccic module is loaded automatically. Cheese and recordactivity > >> > crashed right before show any picture. Then I tested remotely with ssh > >> > -X and it worked for olpc and root user and it works. > >> > > >> > This test was done with: > >> > > >> > * XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0 > >> > * os10 > >> > > >> > Even if it works remotely, there are a lots of warning messages on > >> > the /var/log/messages: > >> > >> The gstreamer pipeline i used on the command line to take a photo is: > >> > >> gst-launch-0.10 v4l2src ! ffmpegcolorspace ! pngenc ! filesink > >> location=foo.png > > It works perfectly fine, thanks for your help. > > > > It seems to be that X is having a hard time displaying the video feed > > for some reason I can't discover (yet). I took a look at > > the /var/log/Xorg.0.log file (while attempting to run cheese) and it > > said: > > > > "Could not allocate memory for the video" > > > > That's why it worked remotely before (apparently). I also tried loading > > extra modules in xorg.conf (the ones that are loaded in the XO-1.5 > > config) but no go. > > > > I'm looking forward to read clues about how to fix it. > > It sounds suspiciously like a Xv issue. That could be anything from a > missing kernel module to a X driver bug. Out of interest can you play > video using totem? Possibly record a video using a XO-1 with the > working 802 build and see if it will play on one with the F11 build. > That would rule out that issue, or possibly we could craft up a > gstreamer pipeline that takes the output of the camera and displays it > on the screen. Let me know how you go with the totem test and then > we'll see where we can take it from there, if that works I can work > out what the pipeline would need to be to test that raw. Well, I've tried what you've suggested me, and it has the same problem. $ totem /media/34F7-79FD/11-Music-Painter\ \(medium\).ogg Gdk-ERROR **: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 101 error_code 11 request_code 131 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... aborted Is this output helping somehow? Is there a way I can help out to fix it? Regards, > > Regards, > Peter > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
On Thu, Dec 17, 2009 at 2:47 PM, César D. Rodas wrote: > Hi Peter, > On Thu, 2009-12-17 at 14:18 +, Peter Robinson wrote: >> Hi César, >> >> >> > The problem with the camera seems to be the xf86-video-geode package. >> >> > The cafe_ccic module is loaded automatically. Cheese and recordactivity >> >> > crashed right before show any picture. Then I tested remotely with ssh >> >> > -X and it worked for olpc and root user and it works. >> >> > >> >> > This test was done with: >> >> > >> >> > * XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0 >> >> > * os10 >> >> > >> >> > Even if it works remotely, there are a lots of warning messages on >> >> > the /var/log/messages: >> >> >> >> The gstreamer pipeline i used on the command line to take a photo is: >> >> >> >> gst-launch-0.10 v4l2src ! ffmpegcolorspace ! pngenc ! filesink >> >> location=foo.png >> > It works perfectly fine, thanks for your help. >> > >> > It seems to be that X is having a hard time displaying the video feed >> > for some reason I can't discover (yet). I took a look at >> > the /var/log/Xorg.0.log file (while attempting to run cheese) and it >> > said: >> > >> > "Could not allocate memory for the video" >> > >> > That's why it worked remotely before (apparently). I also tried loading >> > extra modules in xorg.conf (the ones that are loaded in the XO-1.5 >> > config) but no go. >> > >> > I'm looking forward to read clues about how to fix it. >> >> It sounds suspiciously like a Xv issue. That could be anything from a >> missing kernel module to a X driver bug. Out of interest can you play >> video using totem? Possibly record a video using a XO-1 with the >> working 802 build and see if it will play on one with the F11 build. >> That would rule out that issue, or possibly we could craft up a >> gstreamer pipeline that takes the output of the camera and displays it >> on the screen. Let me know how you go with the totem test and then >> we'll see where we can take it from there, if that works I can work >> out what the pipeline would need to be to test that raw. > > Well, I've tried what you've suggested me, and it has the same problem. > > $ totem /media/34F7-79FD/11-Music-Painter\ \(medium\).ogg > > Gdk-ERROR **: The program 'totem' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadAlloc (insufficient resources for operation)'. > (Details: serial 101 error_code 11 request_code 131 minor_code 19) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() > function.) > aborting... > aborted > > > Is this output helping somehow? Is there a way I can help out to fix it? Yes, it looks like an X bug. I had a similar issue previously with another X driver. To get a proper backtrace using GDB can you do the following, this will then allow us to file a bug. Run gdb and then from the gdb prompt run the following commands. If gdb isn't installed you'll need to do a 'yum install -y gdb'. You'll probably need to install quite a few debuginfo packages to ensure we get a useful backtrace but if you post the backtrace first we can work out what we need. (gdb) exec-file totem --sync (gdb) break gdk_x_error() (gdb) r You'll then get totem come up. Try and play the video as before and you'll have it crash. The run the following with gdb (gdb) thread apply all bt and paste the complete output into a file and put it somewhere I can see it (it might be somewhat large). You can see a sample one from an issue I had with the nouveau driver previously here https://bugzilla.redhat.com/attachment.cgi?id=369702 And we'll see where we need to go from there. Cheers, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
Hello, On Thu, 2009-12-17 at 15:11 +, Peter Robinson wrote: > On Thu, Dec 17, 2009 at 2:47 PM, César D. Rodas > wrote: > > Hi Peter, > > On Thu, 2009-12-17 at 14:18 +, Peter Robinson wrote: > >> Hi César, > >> > >> >> > The problem with the camera seems to be the xf86-video-geode package. > >> >> > The cafe_ccic module is loaded automatically. Cheese and > >> >> > recordactivity > >> >> > crashed right before show any picture. Then I tested remotely with ssh > >> >> > -X and it worked for olpc and root user and it works. > >> >> > > >> >> > This test was done with: > >> >> > > >> >> > * XO-1 kernel: 2.6.31_xo1-20091214.1334.1.olpc.49c30d0 > >> >> > * os10 > >> >> > > >> >> > Even if it works remotely, there are a lots of warning messages on > >> >> > the /var/log/messages: > >> >> > >> >> The gstreamer pipeline i used on the command line to take a photo is: > >> >> > >> >> gst-launch-0.10 v4l2src ! ffmpegcolorspace ! pngenc ! filesink > >> >> location=foo.png > >> > It works perfectly fine, thanks for your help. > >> > > >> > It seems to be that X is having a hard time displaying the video feed > >> > for some reason I can't discover (yet). I took a look at > >> > the /var/log/Xorg.0.log file (while attempting to run cheese) and it > >> > said: > >> > > >> > "Could not allocate memory for the video" > >> > > >> > That's why it worked remotely before (apparently). I also tried loading > >> > extra modules in xorg.conf (the ones that are loaded in the XO-1.5 > >> > config) but no go. > >> > > >> > I'm looking forward to read clues about how to fix it. > >> > >> It sounds suspiciously like a Xv issue. That could be anything from a > >> missing kernel module to a X driver bug. Out of interest can you play > >> video using totem? Possibly record a video using a XO-1 with the > >> working 802 build and see if it will play on one with the F11 build. > >> That would rule out that issue, or possibly we could craft up a > >> gstreamer pipeline that takes the output of the camera and displays it > >> on the screen. Let me know how you go with the totem test and then > >> we'll see where we can take it from there, if that works I can work > >> out what the pipeline would need to be to test that raw. > > > > Well, I've tried what you've suggested me, and it has the same problem. > > > > $ totem /media/34F7-79FD/11-Music-Painter\ \(medium\).ogg > > > > Gdk-ERROR **: The program 'totem' received an X Window System error. > > This probably reflects a bug in the program. > > The error was 'BadAlloc (insufficient resources for operation)'. > > (Details: serial 101 error_code 11 request_code 131 minor_code 19) > > (Note to programmers: normally, X errors are reported asynchronously; > > that is, you will receive the error a while after causing it. > > To debug your program, run it with the --sync command line > > option to change this behavior. You can then get a meaningful > > backtrace from your debugger if you break on the gdk_x_error() > > function.) > > aborting... > > aborted > > > > > > Is this output helping somehow? Is there a way I can help out to fix it? > > Yes, it looks like an X bug. I had a similar issue previously with > another X driver. To get a proper backtrace using GDB can you do the > following, this will then allow us to file a bug. > > Run gdb and then from the gdb prompt run the following commands. If > gdb isn't installed you'll need to do a 'yum install -y gdb'. You'll > probably need to install quite a few debuginfo packages to ensure we > get a useful backtrace but if you post the backtrace first we can work > out what we need. > > (gdb) exec-file totem --sync > (gdb) break gdk_x_error() > (gdb) r > > You'll then get totem come up. Try and play the video as before and > you'll have it crash. The run the following with gdb > > (gdb) thread apply all bt > > and paste the complete output into a file and put it somewhere I can > see it (it might be somewhat large). You can see a sample one from an > issue I had with the nouveau driver previously here > https://bugzilla.redhat.com/attachment.cgi?id=369702 > GDB complained saying it was missing some packages such as debuginfo-install totem-2.26.5-1.fc11.i586, but I think it will have not side effect since I don't want to debug Totem, I want to debug X through it. The output file is here http://oficina.paraguayeduca.org/~crodas/X-totem-debug.log Is it useful? What else can we do in order to hunt this bug? Regards, > And we'll see where we need to go from there. > > Cheers, > Peter > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
On Thu, 2009-12-17 at 15:11 +, Peter Robinson wrote: > And we'll see where we need to go from there. If the problem appears to be in the geode driver, one thing you might consider doing is going back to the version that was shipped in 8.2. After 8.2, a new release was made with various improvements and new functionality but this isn't the first time that I've suspected regressions caused from that work. Going back to the old version of the driver is not trivial -- it will likely require adapting the old code to the new X.org internal graphics drivers APIs -- but probably an easy job for any experienced programmer. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
>> >> > I'm looking forward to read clues about how to fix it. >> >> >> >> It sounds suspiciously like a Xv issue. That could be anything from a >> >> missing kernel module to a X driver bug. Out of interest can you play >> >> video using totem? Possibly record a video using a XO-1 with the >> >> working 802 build and see if it will play on one with the F11 build. >> >> That would rule out that issue, or possibly we could craft up a >> >> gstreamer pipeline that takes the output of the camera and displays it >> >> on the screen. Let me know how you go with the totem test and then >> >> we'll see where we can take it from there, if that works I can work >> >> out what the pipeline would need to be to test that raw. >> > >> > Well, I've tried what you've suggested me, and it has the same problem. >> > >> > $ totem /media/34F7-79FD/11-Music-Painter\ \(medium\).ogg >> > >> > Gdk-ERROR **: The program 'totem' received an X Window System error. >> > This probably reflects a bug in the program. >> > The error was 'BadAlloc (insufficient resources for operation)'. >> > (Details: serial 101 error_code 11 request_code 131 minor_code 19) >> > (Note to programmers: normally, X errors are reported asynchronously; >> > that is, you will receive the error a while after causing it. >> > To debug your program, run it with the --sync command line >> > option to change this behavior. You can then get a meaningful >> > backtrace from your debugger if you break on the gdk_x_error() >> > function.) >> > aborting... >> > aborted >> > >> > >> > Is this output helping somehow? Is there a way I can help out to fix it? >> >> Yes, it looks like an X bug. I had a similar issue previously with >> another X driver. To get a proper backtrace using GDB can you do the >> following, this will then allow us to file a bug. >> >> Run gdb and then from the gdb prompt run the following commands. If >> gdb isn't installed you'll need to do a 'yum install -y gdb'. You'll >> probably need to install quite a few debuginfo packages to ensure we >> get a useful backtrace but if you post the backtrace first we can work >> out what we need. >> >> (gdb) exec-file totem --sync >> (gdb) break gdk_x_error() >> (gdb) r >> >> You'll then get totem come up. Try and play the video as before and >> you'll have it crash. The run the following with gdb >> >> (gdb) thread apply all bt >> >> and paste the complete output into a file and put it somewhere I can >> see it (it might be somewhat large). You can see a sample one from an >> issue I had with the nouveau driver previously here >> https://bugzilla.redhat.com/attachment.cgi?id=369702 >> > GDB complained saying it was missing some packages such as > debuginfo-install totem-2.26.5-1.fc11.i586, but I think it will have not > side effect since I don't want to debug Totem, I want to debug X through > it. > > The output file is here > http://oficina.paraguayeduca.org/~crodas/X-totem-debug.log > > Is it useful? What else can we do in order to hunt this bug? Its a start. We need (at least) also the following debuginfo packages. So a 'yum install -y gstreamer-debuginfo gstreamer-plugins-base-debuginfo gstreamer-debuginfo glib2-debuginfo totem-pl-parser-debuginfo glibc-debuginfo gtk2-debuginfo libX11-debuginfo xorg-x11-server-debuginfo' That should fill out the rest of the debuginfo to make the back trace more useful. Regards, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
On Thu, Dec 17, 2009 at 3:40 PM, Daniel Drake wrote: > On Thu, 2009-12-17 at 15:11 +, Peter Robinson wrote: >> And we'll see where we need to go from there. > > If the problem appears to be in the geode driver, one thing you might > consider doing is going back to the version that was shipped in 8.2. > > After 8.2, a new release was made with various improvements and new > functionality but this isn't the first time that I've suspected > regressions caused from that work. > > Going back to the old version of the driver is not trivial -- it will > likely require adapting the old code to the new X.org internal graphics > drivers APIs -- but probably an easy job for any experienced programmer. Yes I was aware of the changes. I would hope it might be easier for someone to fix the bug :-) Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F11 for XO-1.5 build 62
On Mon, 2009-12-14 at 19:54 -0500, Chris Ball wrote: > (Not sure why this build lost 3MB compared to the last one without > any package changes -- we should diff the tarball to find out.) Uncompressed, os61.tree.tar has identical size to os62.tree.tar So this is just a LZMA compression thing, no actual increase in size. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Little issue with Midore
Hello All, In the FC-11, The Midore Browser comes as the default browser. It looks good so far, but it has a little bug, well it is not a proper bug, the font-size is too big displaying messages. As I said before, it is not a proper bug, and I fixed it by setting the default font size to 6px, in the ~/.config/midori/config, and it looks better. Is there a way to set this configuration by default?, I think it could be done in the RPM itself, in a %post stage. I might be wrong. If I'm not wrong, who is takes care of Midore (or perhaps Gnome) packaging? Even though Sugar is our target desktop we want everything to (sort of) work if some kid chooses to try out Gnome. Best regards ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
Hi Peter, On Thu, 2009-12-17 at 16:33 +, Peter Robinson wrote: > >> >> > I'm looking forward to read clues about how to fix it. > >> >> > >> >> It sounds suspiciously like a Xv issue. That could be anything from a > >> >> missing kernel module to a X driver bug. Out of interest can you play > >> >> video using totem? Possibly record a video using a XO-1 with the > >> >> working 802 build and see if it will play on one with the F11 build. > >> >> That would rule out that issue, or possibly we could craft up a > >> >> gstreamer pipeline that takes the output of the camera and displays it > >> >> on the screen. Let me know how you go with the totem test and then > >> >> we'll see where we can take it from there, if that works I can work > >> >> out what the pipeline would need to be to test that raw. > >> > > >> > Well, I've tried what you've suggested me, and it has the same problem. > >> > > >> > $ totem /media/34F7-79FD/11-Music-Painter\ \(medium\).ogg > >> > > >> > Gdk-ERROR **: The program 'totem' received an X Window System error. > >> > This probably reflects a bug in the program. > >> > The error was 'BadAlloc (insufficient resources for operation)'. > >> > (Details: serial 101 error_code 11 request_code 131 minor_code 19) > >> > (Note to programmers: normally, X errors are reported asynchronously; > >> > that is, you will receive the error a while after causing it. > >> > To debug your program, run it with the --sync command line > >> > option to change this behavior. You can then get a meaningful > >> > backtrace from your debugger if you break on the gdk_x_error() > >> > function.) > >> > aborting... > >> > aborted > >> > > >> > > >> > Is this output helping somehow? Is there a way I can help out to fix it? > >> > >> Yes, it looks like an X bug. I had a similar issue previously with > >> another X driver. To get a proper backtrace using GDB can you do the > >> following, this will then allow us to file a bug. > >> > >> Run gdb and then from the gdb prompt run the following commands. If > >> gdb isn't installed you'll need to do a 'yum install -y gdb'. You'll > >> probably need to install quite a few debuginfo packages to ensure we > >> get a useful backtrace but if you post the backtrace first we can work > >> out what we need. > >> > >> (gdb) exec-file totem --sync > >> (gdb) break gdk_x_error() > >> (gdb) r > >> > >> You'll then get totem come up. Try and play the video as before and > >> you'll have it crash. The run the following with gdb > >> > >> (gdb) thread apply all bt > >> > >> and paste the complete output into a file and put it somewhere I can > >> see it (it might be somewhat large). You can see a sample one from an > >> issue I had with the nouveau driver previously here > >> https://bugzilla.redhat.com/attachment.cgi?id=369702 > >> > > GDB complained saying it was missing some packages such as > > debuginfo-install totem-2.26.5-1.fc11.i586, but I think it will have not > > side effect since I don't want to debug Totem, I want to debug X through > > it. > > > > The output file is here > > http://oficina.paraguayeduca.org/~crodas/X-totem-debug.log > > > > Is it useful? What else can we do in order to hunt this bug? > > Its a start. We need (at least) also the following debuginfo packages. > So a 'yum install -y gstreamer-debuginfo > gstreamer-plugins-base-debuginfo gstreamer-debuginfo glib2-debuginfo > totem-pl-parser-debuginfo glibc-debuginfo gtk2-debuginfo > libX11-debuginfo xorg-x11-server-debuginfo' Thanks for the clue, I've installed those missing packages and I re-run the debugger, http://oficina.paraguayeduca.org/~crodas/X-totem-debug-1.log Please let me know if I need to do something else to debug better. > > That should fill out the rest of the debuginfo to make the back trace > more useful. > > Regards, > Peter > Regards, ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
F11 for XO-1.5 Release Candidate 3
http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os64 Compressed image size: 700.19mb (-2.29mb since build 63) This is the third release candidate (RC3) for the XO-1.5 F11 release! We expect this build to become the first release build (10.1.0) for the 1.5 machines after it passes final testing. B2 compatibility note: * 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. Changes from previous build os63: * Add Q3A25 firmware * Fix collaboration on ad-hoc networks (#9669) * Remove GNOME Cheese app, which isn't working with our camera (#9841) Package changes since build 63: -bootfw-q3a24-1.unsigned.i386 +bootfw-q3a25-1.unsigned.i386 -cheese-2.26.3-1.fc11.i586 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: a trac milestone for F11-for-XO1 work
On Tue, Dec 15, 2009 at 02:08:39PM -0300, C?sar D. Rodas wrote: > I'm Cesar Rodas from Paraguay, as you might notice I'm new here, please > be nice if I say something wrong :-) Welcome! > I was talking to Raul and he told me we could help adding tickets for > the XO1 (from the mailing list, and if we find some bugs). Also, we can > help trying (as hard as we can) to hunt down those bugs. Great, good, I'm pleased. If you have any questions about trac please post them to the mailing list, and if you still don't get a response mail me directly or talk to me in IRC. I work Australia business hours. http://wiki.laptop.org/go/Reporting_bugs shows you how to report bugs in different ways. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F11 for XO-1.5 build 62
On Thu, Dec 17, 2009 at 06:16:05PM +, Daniel Drake wrote: > On Mon, 2009-12-14 at 19:54 -0500, Chris Ball wrote: > > (Not sure why this build lost 3MB compared to the last one without > > any package changes -- we should diff the tarball to find out.) > > Uncompressed, os61.tree.tar has identical size to os62.tree.tar > So this is just a LZMA compression thing, no actual increase in size. I also looked into it briefly ... by comparing only the file names, and found the ordering of the files is changed, I had to sort the tar list. Changing the order of the bytes certainly changes the resulting compressed stream, and 3Mb seems not unreasonable over that total length. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
On Thu, 2009-12-17 at 11:47 -0300, César D. Rodas wrote: > This probably reflects a bug in the program. > The error was 'BadAlloc (insufficient resources for operation)'. I'm doing some work that uses xv on the XO. I found that this occurred for me when running X in 24bit, but 16bit was ok. I'm assuming that it's not actually running out of ram because free reports that I have 223M totoal memory, I certainly hope that means that 32 meg has been given to the display driver. If not I'd like some of it back please :-) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
On Fri, Dec 18, 2009 at 6:32 AM, Neil Graham wrote: > On Thu, 2009-12-17 at 11:47 -0300, César D. Rodas wrote: >> This probably reflects a bug in the program. >> The error was 'BadAlloc (insufficient resources for operation)'. > > I'm doing some work that uses xv on the XO. > > I found that this occurred for me when running X in 24bit, but 16bit > was ok. > > I'm assuming that it's not actually running out of ram because free > reports that I have 223M totoal memory, I certainly hope that means that > 32 meg has been given to the display driver. If not I'd like some of it > back please :-) See RHBZ https://bugzilla.redhat.com/show_bug.cgi?id=487601 on that particular issue. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
