On Tuesday, September 4, 2012 7:25:09 AM UTC-5, Boudet, Xavier wrote:
> Hi there,
> A major update has been done on TI PPA. Please read the below e-mail > especially for upgrade. > If you do not have installed the TI release PPA, please refer to New > installation procedure.
> *New installation procedure:* > 1- Add TI OMAP release PPA: > $ sudo su - > # export http_proxy=<your proxy if any> > # export https_proxy=<your proxy if any> > # add-apt-repository ppa:tiomap-dev/release
> This step is failing for me with the following error:
> On Tuesday, September 4, 2012 7:25:09 AM UTC-5, Boudet, Xavier wrote:
> Hi there,
> A major update has been done on TI PPA. Please read the below
> e-mail especially for upgrade.
> If you do not have installed the TI release PPA, please refer to
> New installation procedure.
> *New installation procedure:*
> 1- Add TI OMAP release PPA:
> $ sudo su -
> # export http_proxy=<your proxy if any>
> # export https_proxy=<your proxy if any>
> # add-apt-repository ppa:tiomap-dev/release
> This step is failing for me with the following error:
> On Tuesday, September 4, 2012 7:25:09 AM UTC-5, Boudet, Xavier wrote:
>> Hi there,
>> A major update has been done on TI PPA. Please read the below e-mail >> especially for upgrade. >> If you do not have installed the TI release PPA, please refer to New >> installation procedure.
>> *New installation procedure:* >> 1- Add TI OMAP release PPA: >> $ sudo su - >> # export http_proxy=<your proxy if any> >> # export https_proxy=<your proxy if any> >> # add-apt-repository ppa:tiomap-dev/release
>> This step is failing for me with the following error:
> On Tuesday, September 4, 2012 7:25:09 AM UTC-5, Boudet, Xavier wrote:
>> Hi there,
>> A major update has been done on TI PPA. Please read the below e-mail >> especially for upgrade. >> If you do not have installed the TI release PPA, please refer to New >> installation procedure.
>> *New installation procedure:* >> 1- Add TI OMAP release PPA: >> $ sudo su - >> # export http_proxy=<your proxy if any> >> # export https_proxy=<your proxy if any> >> # add-apt-repository ppa:tiomap-dev/release
>> This step is failing for me with the following error:
Don't know if its because I'd rebooted the Pandaboard to poke around the SD card to see if I could figure out how to add the PPA manually (wan't obvious) or because whatever network issue there was fixed itself while I ate lunch.
If you have this problem try rebooting the Pandaboard and if that fails try again an hour or so later.
>> On Tuesday, September 4, 2012 7:25:09 AM UTC-5, Boudet, Xavier wrote:
>>> Hi there,
>>> A major update has been done on TI PPA. Please read the below e-mail >>> especially for upgrade. >>> If you do not have installed the TI release PPA, please refer to New >>> installation procedure.
>>> *New installation procedure:* >>> 1- Add TI OMAP release PPA: >>> $ sudo su - >>> # export http_proxy=<your proxy if any> >>> # export https_proxy=<your proxy if any> >>> # add-apt-repository ppa:tiomap-dev/release
>>> This step is failing for me with the following error:
I started from scratch again, this time grabbing the uInitrd for the boot partition and adding the bootargs you noted. On first boot there now seems to be a net installation that wants to format the rootfs and create a user, etc. This seems to no longer be "Ubuntu core" and destroys the tarball that was extracted to the rootfs and all the modifications.
Any idea what this uInitrd is? Is this the right one?
On Tuesday, November 13, 2012 11:47:26 PM UTC-8, Xavier Boudet wrote:
> Hi Jared,
> Apparently you are facing uInitrd issue. > We realized very recently that without the uInitrd, udevd was not starting > correctly and as a consequence ducati is not starting correctly: > [ 11.963928] rproc remoteproc1: failed waiting for udev -2 > [ 11.970092] rproc remoteproc0: failed waiting for udev -2 > It is still not clear why we are facing this issue, but we are > investigating.
> You just need to update your boot.scr/boot.script accordingly: > fatload mmc 0:1 0x80000000 uImage > *fatload mmc 0:1 0x81600000 uInitrd* > setenv bootargs <... your current bootargs, no change> > *bootm 0x80000000 0x81600000*
> Oh, oops. I had copied the recommended bootargs "ro elevator=noop > console=ttyO2,115200n8 mem=1G@0x80000000 root=/dev/mmcblk0p2 fixrtc splash" > from one of the other posts here. I don't want to mount the root > filesystem as read-only... I am now using these bootargs in a new boot.scr:
> - I can again login from the serial console > - The DVI display has a login prompt and I can login there as well > - The HDMI display shows nothing (monitor goes into powersaving mode)
> At the DVI display, if I login as root, startx, see omapdrm_pvr from > lsmod, and run the recommended gstreamer pipeline, I get an error and see > no output:
> root@localhost:~# ./gst.sh > Setting pipeline to PAUSED ... > PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, > /bridged_pvr_dc_glue.c] > PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, > /bridged_pvr_dc_glue.c] > libdce-x11.c:64: dce_auth_x11 info: attempting to open X11 > connection > *libdce.c:459: init error: could not get plugin ioctl base: -22* > ERROR: Pipeline doesn't want to pause. > Setting pipeline to NULL ... > PVR:(Warning): PVRDRMSetFD: DRM fd already set [57, /pvr_bridge_u.c] > Freeing pipeline ... > root@localhost:~#
> Output from dmesg is attached if that helps any... Thanks!
> Jared
> On Tuesday, November 13, 2012 10:39:38 AM UTC-8, JB wrote:
>> I plugged into the DVI port on the Pandaboard, powered on, and saw two >> penguins in the upper left corner. I then tried the HDMI port and saw the >> same thing. At this point I was unable to log in via the serial console, >> and saw no login prompt from either display - just penguins. I can ping >> the board's IP address but not SSH. I'm probably missing something obvious >> here...
>> Jared
>> On Sunday, November 11, 2012 11:40:35 PM UTC-8, Xavier Boudet wrote:
>>> Answers inline. >>> Can you clarify what is/are the remaining issue(s)? The gst pipeline?
>>> Hi Xavier. Thanks very much for the quick reply! I'm pretty new to >>> Pandaboard and I've been trying to get a minimal Ubuntu core image >>> working. All I need is for gstreamer to be able to capture from a USB >>> webcam, H.264 encode, H.264 decode, and render to X11 without a window >>> manager.
>>> With these modifications: >>> A.) Before "apt-get install ubuntu-omap4-extras --yes --force-yes" I did >>> "apt-get install u-boot-tools" >>> B.) After the "apt-get install ubuntu-omap4-extras --yes --force-yes" I >>> shut down and modified boot.scr in the boot partition to:
>>> I am still not sure why you are using omapdss.def_disp=dvi
>>> The instructions say to use "vram=32M" but I know that is no longer >>> valid, so I took that out. Also, both the DVI port and HDMI port had no >>> signal until I added omapdss.def_disp=dvi to the bootargs. Even after >>> doing that the HDMI port was activated, not the DVI one. Strange...
>>> With the TI PPA kernel, HDMI and DVI shall be auto-detected at boot and >>> you shall be able to use both connector.
>>> C.) Before doing the "apt-get install xorg", I did "apt-get install >>> --reinstall pvr-omap4-dkms" because I did not see "omapdrm_prv" from lsmod.
>>> omapdrm_prv will be triggered only after X startup in fact.
>>> D.) After doing the "apt-get install xorg" I stopped with the >>> instructions, since I don't want a window manager. I'm trying to make an >>> image as minimal as possible.
>>> To answer your questions (with my Pandaboard in the state described >>> above): >>> 1.) So you are using TI PPA, correct?
>>> 2.) Can you ensure that you perform dist-upgrade? We indeed have renamed >>> some packages so aptitude needs that you perform dist-upgrade to replace >>> existing package with new ones.
>>> Apparently I already have the latest: >>> root@localhost:~# apt-get dist-upgrade >>> Reading package lists... Done >>> Building dependency tree >>> Reading state information... Done >>> Calculating upgrade... Done >>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>> 3.) Can you check if pvr module is correctly installed? >>> After the boot perform: lsmod | grep omapdrm_prv >>> If this module is not loaded you might need to execute: >>> sudo apt-get install --reinstall pvr-omap4-dkms
>>> Even though I did "apt-get install --reinstall pvr-omap4-dkms" >>> previously, I still don't see "omapdrm_prv" now on reboot. I installed it >>> again just now and rebooted - it did not show under lsmod until after I ran >>> "startx". Apparently I will always need to startx first.
>>> Yes, omapdrm_prv is automatically loaded only after you startx, this is >>> expected.
>>> 4.) Can you ensure that you are running the last kernel? Please send >>> "uname -a" output.
>>> root@localhost:~# uname -a >>> Linux localhost.localdomain 3.4.0-1487-omap4 #6-Ubuntu SMP PREEMPT Mon >>> Oct 1 16:54:59 UTC 2012 armv7l armv7l armv7l GNU/Linux
>>> OK.
>>> 5.) Why are you using omapdss.def_disp=dvi in your bootargs?
>>> I saw this on http://omappedia.org/wiki/Bootargs_for_enabling_displayand added it since neither HDMI nor DVI were providing signal without it. >>> Maybe the situation is different because I am using a core image and not a >>> desktop one?
>>> When booting Ubuntu Core, you shall see a console on HDMI or DVI after >>> the boot. You shall not specify omapdss_def and you shall add splash to the >>> bootargs.
>>> 6.) Are you sure about your pipeline? Here is an example of pipeline >>> supposed to work: >>> Example of VTC (videoconference) e.g. V4L2 USB webcam + preview + H264 >>> encode + H264 decode + display, using V4L2, DRI2 and PVR. >>> gst-launch -v v4l2src ! "video/x-raw-yuv, framerate=(fraction)30/1" ! >>> stridetransform ! tee name=t \ >>> t. ! queue ! dri2videosink sync=false \ >>> t. ! queue ! ducatih264enc rate-preset=low-delay profile=100 ! h264parse >>> ! ducatih264dec ! queue ! pvrvideosink sync=false
>>> So I did a reboot, startx, export DISPLAY=:0, checked lsmod again for >>> "omapdrm_prv", and ran the pipeline you provided:
>>> root@localhost:~# ./gst.sh >>> Setting pipeline to PAUSED ... >>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >>> /bridged_pvr_dc_glue.c] >>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >>> /bridged_pvr_dc_glue.c] >>> libdce-x11.c:64: dce_auth_x11 info: attempting to open X11 >>> connection >>> libdce.c:459: init error: could not get plugin ioctl base: -22 >>> ERROR: Pipeline doesn't want to pause. >>> Setting pipeline to NULL ... >>> PVR:(Warning): PVRDRMSetFD: DRM fd already set [57, /pvr_bridge_u.c] >>> Freeing pipeline ...
>>> It looks correct, messages are normal ones.
>>> 7.) Why are you using root user?
>>> The Ubuntu core image drops you right into root.
>>> OK, this explains why...
>>> 8.) Which kind of image are you using, desktop one?
no, this is the wrong init ramdisk. Here is what i did: First install the ubuntu core on a SD card (without init ramdisk), then boot the pandaboard and install the TI PPA. After updating the bootloader (with "flash-kernel --update-bootloader"), the init ramdisk is being generated in the boot partition. Then, change the /boot/boot.script to load the uInitrd and update the bootloader again ("flash-kernel"). Reboot and everything will work.
On Wednesday, November 14, 2012 11:49:05 PM UTC+1, JB wrote:
> I started from scratch again, this time grabbing the uInitrd for the boot > partition and adding the bootargs you noted. On first boot there now seems > to be a net installation that wants to format the rootfs and create a user, > etc. This seems to no longer be "Ubuntu core" and destroys the tarball > that was extracted to the rootfs and all the modifications.
> Any idea what this uInitrd is? Is this the right one?
> On Tuesday, November 13, 2012 11:47:26 PM UTC-8, Xavier Boudet wrote:
>> Hi Jared,
>> Apparently you are facing uInitrd issue. >> We realized very recently that without the uInitrd, udevd was not >> starting correctly and as a consequence ducati is not starting correctly: >> [ 11.963928] rproc remoteproc1: failed waiting for udev -2 >> [ 11.970092] rproc remoteproc0: failed waiting for udev -2 >> It is still not clear why we are facing this issue, but we are >> investigating.
>> You just need to update your boot.scr/boot.script accordingly: >> fatload mmc 0:1 0x80000000 uImage >> *fatload mmc 0:1 0x81600000 uInitrd* >> setenv bootargs <... your current bootargs, no change> >> *bootm 0x80000000 0x81600000*
>> Oh, oops. I had copied the recommended bootargs "ro elevator=noop >> console=ttyO2,115200n8 mem=1G@0x80000000 root=/dev/mmcblk0p2 fixrtc splash" >> from one of the other posts here. I don't want to mount the root >> filesystem as read-only... I am now using these bootargs in a new boot.scr:
>> - I can again login from the serial console >> - The DVI display has a login prompt and I can login there as well >> - The HDMI display shows nothing (monitor goes into powersaving mode)
>> At the DVI display, if I login as root, startx, see omapdrm_pvr from >> lsmod, and run the recommended gstreamer pipeline, I get an error and see >> no output:
>> root@localhost:~# ./gst.sh >> Setting pipeline to PAUSED ... >> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >> /bridged_pvr_dc_glue.c] >> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >> /bridged_pvr_dc_glue.c] >> libdce-x11.c:64: dce_auth_x11 info: attempting to open X11 >> connection >> *libdce.c:459: init error: could not get plugin ioctl base: -22* >> ERROR: Pipeline doesn't want to pause. >> Setting pipeline to NULL ... >> PVR:(Warning): PVRDRMSetFD: DRM fd already set [57, /pvr_bridge_u.c] >> Freeing pipeline ... >> root@localhost:~#
>> Output from dmesg is attached if that helps any... Thanks!
>> Jared
>> On Tuesday, November 13, 2012 10:39:38 AM UTC-8, JB wrote:
>>> I plugged into the DVI port on the Pandaboard, powered on, and saw two >>> penguins in the upper left corner. I then tried the HDMI port and saw the >>> same thing. At this point I was unable to log in via the serial console, >>> and saw no login prompt from either display - just penguins. I can ping >>> the board's IP address but not SSH. I'm probably missing something obvious >>> here...
>>> Jared
>>> On Sunday, November 11, 2012 11:40:35 PM UTC-8, Xavier Boudet wrote:
>>>> Answers inline. >>>> Can you clarify what is/are the remaining issue(s)? The gst pipeline?
>>>> Hi Xavier. Thanks very much for the quick reply! I'm pretty new to >>>> Pandaboard and I've been trying to get a minimal Ubuntu core image >>>> working. All I need is for gstreamer to be able to capture from a USB >>>> webcam, H.264 encode, H.264 decode, and render to X11 without a window >>>> manager.
>>>> With these modifications: >>>> A.) Before "apt-get install ubuntu-omap4-extras --yes --force-yes" I >>>> did "apt-get install u-boot-tools" >>>> B.) After the "apt-get install ubuntu-omap4-extras --yes --force-yes" I >>>> shut down and modified boot.scr in the boot partition to:
>>>> I am still not sure why you are using omapdss.def_disp=dvi
>>>> The instructions say to use "vram=32M" but I know that is no longer >>>> valid, so I took that out. Also, both the DVI port and HDMI port had no >>>> signal until I added omapdss.def_disp=dvi to the bootargs. Even after >>>> doing that the HDMI port was activated, not the DVI one. Strange...
>>>> With the TI PPA kernel, HDMI and DVI shall be auto-detected at boot and >>>> you shall be able to use both connector.
>>>> C.) Before doing the "apt-get install xorg", I did "apt-get install >>>> --reinstall pvr-omap4-dkms" because I did not see "omapdrm_prv" from lsmod.
>>>> omapdrm_prv will be triggered only after X startup in fact.
>>>> D.) After doing the "apt-get install xorg" I stopped with the >>>> instructions, since I don't want a window manager. I'm trying to make an >>>> image as minimal as possible.
>>>> To answer your questions (with my Pandaboard in the state described >>>> above): >>>> 1.) So you are using TI PPA, correct?
>>>> 2.) Can you ensure that you perform dist-upgrade? We indeed have >>>> renamed some packages so aptitude needs that you perform dist-upgrade to >>>> replace existing package with new ones.
>>>> Apparently I already have the latest: >>>> root@localhost:~# apt-get dist-upgrade >>>> Reading package lists... Done >>>> Building dependency tree >>>> Reading state information... Done >>>> Calculating upgrade... Done >>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>>> 3.) Can you check if pvr module is correctly installed? >>>> After the boot perform: lsmod | grep omapdrm_prv >>>> If this module is not loaded you might need to execute: >>>> sudo apt-get install --reinstall pvr-omap4-dkms
>>>> Even though I did "apt-get install --reinstall pvr-omap4-dkms" >>>> previously, I still don't see "omapdrm_prv" now on reboot. I installed it >>>> again just now and rebooted - it did not show under lsmod until after I ran >>>> "startx". Apparently I will always need to startx first.
>>>> Yes, omapdrm_prv is automatically loaded only after you startx, this is >>>> expected.
>>>> 4.) Can you ensure that you are running the last kernel? Please send >>>> "uname -a" output.
>>>> root@localhost:~# uname -a >>>> Linux localhost.localdomain 3.4.0-1487-omap4 #6-Ubuntu SMP PREEMPT Mon >>>> Oct 1 16:54:59 UTC 2012 armv7l armv7l armv7l GNU/Linux
>>>> OK.
>>>> 5.) Why are you using omapdss.def_disp=dvi in your bootargs?
>>>> I saw this on http://omappedia.org/wiki/Bootargs_for_enabling_displayand added it since neither HDMI nor DVI were providing signal without it. >>>> Maybe the situation is different because I am using a core image and not a >>>> desktop one?
>>>> When booting Ubuntu Core, you shall see a console on HDMI or DVI after >>>> the boot. You shall not specify omapdss_def and you shall add splash to the >>>> bootargs.
>>>> 6.) Are you sure about your pipeline? Here is an example of pipeline >>>> supposed to work: >>>> Example of VTC (videoconference) e.g. V4L2 USB webcam + preview + H264 >>>> encode + H264 decode + display, using V4L2, DRI2 and PVR. >>>> gst-launch -v v4l2src ! "video/x-raw-yuv, framerate=(fraction)30/1" ! >>>> stridetransform ! tee name=t \ >>>> t. ! queue ! dri2videosink sync=false \ >>>> t. ! queue ! ducatih264enc rate-preset=low-delay profile=100 ! >>>> h264parse ! ducatih264dec ! queue ! pvrvideosink sync=false
>>>> So I did a reboot, startx, export DISPLAY=:0, checked lsmod again for >>>> "omapdrm_prv", and ran the pipeline you provided:
>>>> root@localhost:~# ./gst.sh >>>> Setting pipeline to PAUSED ... >>>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >>>> /bridged_pvr_dc_glue.c] >>>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >>>> /bridged_pvr_dc_glue.c] >>>> libdce-x11.c:64: dce_auth_x11 info: attempting to open X11 >>>> connection >>>> libdce.c:459: init error: could not get plugin ioctl base: -22 >>>> ERROR: Pipeline doesn't want to pause. >>>> Setting pipeline to NULL ... >>>> PVR:(Warning):
> no, this is the wrong init ramdisk.
> Here is what i did:
> First install the ubuntu core on a SD card (without init ramdisk), > then boot the pandaboard and install the TI PPA. After updating the > bootloader (with "flash-kernel --update-bootloader"), the init ramdisk > is being generated in the boot partition. Then, change the > /boot/boot.script to load the uInitrd and update the bootloader again > ("flash-kernel"). Reboot and everything will work.
> On Wednesday, November 14, 2012 11:49:05 PM UTC+1, JB wrote:
> I started from scratch again, this time grabbing the uInitrd for
> the boot partition and adding the bootargs you noted. On first
> boot there now seems to be a net installation that wants to format
> the rootfs and create a user, etc. This seems to no longer be
> "Ubuntu core" and destroys the tarball that was extracted to the
> rootfs and all the modifications.
> Any idea what this uInitrd is? Is this the right one?
> On Tuesday, November 13, 2012 11:47:26 PM UTC-8, Xavier Boudet wrote:
> Hi Jared,
> Apparently you are facing uInitrd issue.
> We realized very recently that without the uInitrd, udevd was
> not starting correctly and as a consequence ducati is not
> starting correctly:
> [ 11.963928] rproc remoteproc1: failed waiting for udev -2
> [ 11.970092] rproc remoteproc0: failed waiting for udev -2
> It is still not clear why we are facing this issue, but we are
> investigating.
> You just need to update your boot.scr/boot.script accordingly:
> fatload mmc 0:1 0x80000000 uImage
> *fatload mmc 0:1 0x81600000 uInitrd*
> setenv bootargs <... your current bootargs, no change>
> *bootm 0x80000000 0x81600000*
> On 11/13/2012 08:14 PM, JB wrote:
>> Oh, oops. I had copied the recommended bootargs "ro
>> elevator=noop console=ttyO2,115200n8 mem=1G@0x80000000
>> root=/dev/mmcblk0p2 fixrtc splash" from one of the other
>> posts here. I don't want to mount the root filesystem as
>> read-only... I am now using these bootargs in a new boot.scr:
>> - I can again login from the serial console
>> - The DVI display has a login prompt and I can login there as
>> well
>> - The HDMI display shows nothing (monitor goes into
>> powersaving mode)
>> At the DVI display, if I login as root, startx, see
>> omapdrm_pvr from lsmod, and run the recommended gstreamer
>> pipeline, I get an error and see no output:
>> root@localhost:~# ./gst.sh
>> Setting pipeline to PAUSED ...
>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned
>> [80, /bridged_pvr_dc_glue.c]
>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned
>> [80, /bridged_pvr_dc_glue.c]
>> libdce-x11.c:64: dce_auth_x11 info: attempting to
>> open X11 connection
>> *libdce.c:459: init error: could not get plugin ioctl
>> base: -22*
>> ERROR: Pipeline doesn't want to pause.
>> Setting pipeline to NULL ...
>> PVR:(Warning): PVRDRMSetFD: DRM fd already set [57,
>> /pvr_bridge_u.c]
>> Freeing pipeline ...
>> root@localhost:~#
>> Output from dmesg is attached if that helps any... Thanks!
>> Jared
>> On Tuesday, November 13, 2012 10:39:38 AM UTC-8, JB wrote:
>> I plugged into the DVI port on the Pandaboard, powered
>> on, and saw two penguins in the upper left corner. I
>> then tried the HDMI port and saw the same thing. At this
>> point I was unable to log in via the serial console, and
>> saw no login prompt from either display - just penguins. >> I can ping the board's IP address but not SSH. I'm
>> probably missing something obvious here...
>> Jared
>> On Sunday, November 11, 2012 11:40:35 PM UTC-8, Xavier
>> Boudet wrote:
>> Answers inline.
>> Can you clarify what is/are the remaining issue(s)?
>> The gst pipeline?
>> Regards, Xavier Boudet
>> On 11/09/2012 08:23 PM, JB wrote:
>>> Hi Xavier. Thanks very much for the quick reply! >>> I'm pretty new to Pandaboard and I've been trying to
>>> get a minimal Ubuntu core image working. All I need
>>> is for gstreamer to be able to capture from a USB
>>> webcam, H.264 encode, H.264 decode, and render to
>>> X11 without a window manager.
>>> With these modifications:
>>> A.) Before "apt-get install ubuntu-omap4-extras
>>> --yes --force-yes" I did "apt-get install u-boot-tools"
>>> B.) After the "apt-get install ubuntu-omap4-extras
>>> --yes --force-yes" I shut down and modified boot.scr
>>> in the boot partition to:
>> I am still not sure why you are using
>> omapdss.def_disp=dvi
>>> The instructions say to use "vram=32M" but I know
>>> that is no longer valid, so I took that out. Also,
>>> both the DVI port and HDMI port had no signal until
>>> I added omapdss.def_disp=dvi to the bootargs. Even
>>> after doing that the HDMI port was activated, not
>>> the DVI one. Strange...
>> With the TI PPA kernel, HDMI and DVI shall be
>> auto-detected at boot and you shall be able to use
>> both connector.
>>> C.) Before doing the "apt-get install xorg", I did
>>> "apt-get install --reinstall pvr-omap4-dkms" because
>>> I did not see "omapdrm_prv" from lsmod.
>> omapdrm_prv will be triggered only after X startup in
>> fact.
>>> D.) After doing the "apt-get install xorg" I stopped
>>> with the instructions, since I don't want a window
>>> manager. I'm trying to make an image as minimal as
>>> possible.
>>> To answer your questions (with my Pandaboard in the
>>> state described above):
>>> 1.) So you are using TI PPA, correct?
>>> 2.) Can you ensure that you perform dist-upgrade? We
>>> indeed have renamed some packages so aptitude needs
>>> that you perform dist-upgrade to replace existing
>>> package with new ones.
>>> Apparently I already have the latest:
>>> root@localhost:~# apt-get dist-upgrade
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Calculating upgrade... Done
>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not
>>> upgraded.
>>> 3.) Can you check if pvr module is correctly installed?
>>> After the boot perform: lsmod | grep omapdrm_prv
I have also been getting the black screen issues, but was able to circumvent it by powering the board with the monitor plugged into the DVI-D port and then switching to the HDMI-1080p port. I'm using an HDMI to DVI-D adapter to my monitor. Booting with the screen unplugged and plugging it in after 1 minute also seems to work sometimes.
I've been following the instructions on this discussion and this page: http://omappedia.org/wiki/Installing_Ubuntu_12.04_on_Pandaboard_with_.... After the installation procedure, when performing the command: $ sudo apt-get dist-upgrade About 30 minutes into the upgrade, everything disappears except for the wallpaper, the screen goes black, and I only get flashes of the wallpaper when I move my cursor. The Pandaboard will not reboot after this.
Am I supposed to change any bootargs first? Do I need to enable Universe and Multiverse Repositories before the update and the dist-upgrade?
The only thing I may be doing differently is that I'm writing the image to my 8 GB SDHC card using Windows and ImageWriter per the instructions here: https://wiki.ubuntu.com/ARM/OmapDesktopInstall. I have tried writing the images using a Ubuntu 12.04 VirtualBox and a USB SD Card Reader. Although the image finishes being written, the Pandaboard will not read it. I also cannot get minicom to read serial commands through the Ubuntu 12.04 VirtualBox.
If I just want to get something running, am I better off going back to Ubuntu 11.10?
> no, this is the wrong init ramdisk. > Here is what i did: > First install the ubuntu core on a SD card (without init ramdisk), then > boot the pandaboard and install the TI PPA. After updating the bootloader > (with "flash-kernel --update-bootloader"), the init ramdisk is being > generated in the boot partition. Then, change the /boot/boot.script to load > the uInitrd and update the bootloader again ("flash-kernel"). Reboot and > everything will work.
> On Wednesday, November 14, 2012 11:49:05 PM UTC+1, JB wrote:
>> I started from scratch again, this time grabbing the uInitrd for the boot >> partition and adding the bootargs you noted. On first boot there now seems >> to be a net installation that wants to format the rootfs and create a user, >> etc. This seems to no longer be "Ubuntu core" and destroys the tarball >> that was extracted to the rootfs and all the modifications.
>> Any idea what this uInitrd is? Is this the right one?
>> On Tuesday, November 13, 2012 11:47:26 PM UTC-8, Xavier Boudet wrote:
>>> Hi Jared,
>>> Apparently you are facing uInitrd issue. >>> We realized very recently that without the uInitrd, udevd was not >>> starting correctly and as a consequence ducati is not starting correctly: >>> [ 11.963928] rproc remoteproc1: failed waiting for udev -2 >>> [ 11.970092] rproc remoteproc0: failed waiting for udev -2 >>> It is still not clear why we are facing this issue, but we are >>> investigating.
>>> You just need to update your boot.scr/boot.script accordingly: >>> fatload mmc 0:1 0x80000000 uImage >>> *fatload mmc 0:1 0x81600000 uInitrd* >>> setenv bootargs <... your current bootargs, no change> >>> *bootm 0x80000000 0x81600000*
>>> Oh, oops. I had copied the recommended bootargs "ro elevator=noop >>> console=ttyO2,115200n8 mem=1G@0x80000000 root=/dev/mmcblk0p2 fixrtc splash" >>> from one of the other posts here. I don't want to mount the root >>> filesystem as read-only... I am now using these bootargs in a new boot.scr:
>>> - I can again login from the serial console >>> - The DVI display has a login prompt and I can login there as well >>> - The HDMI display shows nothing (monitor goes into powersaving mode)
>>> At the DVI display, if I login as root, startx, see omapdrm_pvr from >>> lsmod, and run the recommended gstreamer pipeline, I get an error and see >>> no output:
>>> root@localhost:~# ./gst.sh >>> Setting pipeline to PAUSED ... >>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >>> /bridged_pvr_dc_glue.c] >>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, >>> /bridged_pvr_dc_glue.c] >>> libdce-x11.c:64: dce_auth_x11 info: attempting to open X11 >>> connection >>> *libdce.c:459: init error: could not get plugin ioctl base: -22* >>> ERROR: Pipeline doesn't want to pause. >>> Setting pipeline to NULL ... >>> PVR:(Warning): PVRDRMSetFD: DRM fd already set [57, /pvr_bridge_u.c] >>> Freeing pipeline ... >>> root@localhost:~#
>>> Output from dmesg is attached if that helps any... Thanks!
>>> Jared
>>> On Tuesday, November 13, 2012 10:39:38 AM UTC-8, JB wrote:
>>>> I plugged into the DVI port on the Pandaboard, powered on, and saw two >>>> penguins in the upper left corner. I then tried the HDMI port and saw the >>>> same thing. At this point I was unable to log in via the serial console, >>>> and saw no login prompt from either display - just penguins. I can ping >>>> the board's IP address but not SSH. I'm probably missing something obvious >>>> here...
>>>> Jared
>>>> On Sunday, November 11, 2012 11:40:35 PM UTC-8, Xavier Boudet wrote:
>>>>> Answers inline. >>>>> Can you clarify what is/are the remaining issue(s)? The gst pipeline?
>>>>> Hi Xavier. Thanks very much for the quick reply! I'm pretty new to >>>>> Pandaboard and I've been trying to get a minimal Ubuntu core image >>>>> working. All I need is for gstreamer to be able to capture from a USB >>>>> webcam, H.264 encode, H.264 decode, and render to X11 without a window >>>>> manager.
>>>>> With these modifications: >>>>> A.) Before "apt-get install ubuntu-omap4-extras --yes --force-yes" I >>>>> did "apt-get install u-boot-tools" >>>>> B.) After the "apt-get install ubuntu-omap4-extras --yes --force-yes" >>>>> I shut down and modified boot.scr in the boot partition to:
>>>>> I am still not sure why you are using omapdss.def_disp=dvi
>>>>> The instructions say to use "vram=32M" but I know that is no longer >>>>> valid, so I took that out. Also, both the DVI port and HDMI port had no >>>>> signal until I added omapdss.def_disp=dvi to the bootargs. Even after >>>>> doing that the HDMI port was activated, not the DVI one. Strange...
>>>>> With the TI PPA kernel, HDMI and DVI shall be auto-detected at boot >>>>> and you shall be able to use both connector.
>>>>> C.) Before doing the "apt-get install xorg", I did "apt-get install >>>>> --reinstall pvr-omap4-dkms" because I did not see "omapdrm_prv" from lsmod.
>>>>> omapdrm_prv will be triggered only after X startup in fact.
>>>>> D.) After doing the "apt-get install xorg" I stopped with the >>>>> instructions, since I don't want a window manager. I'm trying to make an >>>>> image as minimal as possible.
>>>>> To answer your questions (with my Pandaboard in the state described >>>>> above): >>>>> 1.) So you are using TI PPA, correct?
>>>>> 2.) Can you ensure that you perform dist-upgrade? We indeed have >>>>> renamed some packages so aptitude needs that you perform dist-upgrade to >>>>> replace existing package with new ones.
>>>>> Apparently I already have the latest: >>>>> root@localhost:~# apt-get dist-upgrade >>>>> Reading package lists... Done >>>>> Building dependency tree >>>>> Reading state information... Done >>>>> Calculating upgrade... Done >>>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>>>> 3.) Can you check if pvr module is correctly installed? >>>>> After the boot perform: lsmod | grep omapdrm_prv >>>>> If this module is
First of all, I advise you to configure a console on the Panda and to perform the upgrade through the console if this is not already the case.
Then can you confirm that you are using Ubuntu 2D (unity) and not Ubuntu 3D (compiz).
Ubuntu 3D is known to be unstable with TI PPA.
Concerning bootargs, you indeed need to ensure that your bootargs are the following:
ro elevator=noop console=ttyO2,115200n8 mem=1G@0x80000000 root=<UUID or LABEL root> fixrtc splash
> I have also been getting the black screen issues, but was able to > circumvent it by powering the board with the monitor plugged into the > DVI-D port and then switching to the HDMI-1080p port. I'm using an > HDMI to DVI-D adapter to my monitor. Booting with the screen unplugged > and plugging it in after 1 minute also seems to work sometimes.
> I've been following the instructions on this discussion and this > page: http://omappedia.org/wiki/Installing_Ubuntu_12.04_on_Pandaboard_with_.... > After the installation procedure, when performing the command:
> $ sudo apt-get dist-upgrade
> About 30 minutes into the upgrade, everything disappears except for > the wallpaper, the screen goes black, and I only get flashes of the > wallpaper when I move my cursor. The Pandaboard will not reboot after > this.
> Am I supposed to change any bootargs first? Do I need to enable > Universe and Multiverse Repositories before the update and the > dist-upgrade?
> The only thing I may be doing differently is that I'm writing the > image to my 8 GB SDHC card using Windows and ImageWriter per the > instructions here: https://wiki.ubuntu.com/ARM/OmapDesktopInstall. I > have tried writing the images using a Ubuntu 12.04 VirtualBox and a > USB SD Card Reader. Although the image finishes being written, the > Pandaboard will not read it. I also cannot get minicom to read serial > commands through the Ubuntu 12.04 VirtualBox.
> If I just want to get something running, am I better off going back to > Ubuntu 11.10?
> Thanks again for your help.
> Best Regards,
> Frankie
> On Thursday, November 15, 2012 2:21:03 AM UTC-8, Xavier Boudet wrote:
> Indeed, I did not notice that.
> I will modify back the documentation to indicate to add uInitrd
> after the ubuntu-omap4-extras installation.
> Thanks for the feedback.
> Regards, Xavier Boudet
> On 11/15/2012 12:08 AM, Uli Grossek wrote:
>> no, this is the wrong init ramdisk.
>> Here is what i did:
>> First install the ubuntu core on a SD card (without init
>> ramdisk), then boot the pandaboard and install the TI PPA. After
>> updating the bootloader (with "flash-kernel
>> --update-bootloader"), the init ramdisk is being generated in the
>> boot partition. Then, change the /boot/boot.script to load the
>> uInitrd and update the bootloader again ("flash-kernel"). Reboot
>> and everything will work.
>> On Wednesday, November 14, 2012 11:49:05 PM UTC+1, JB wrote:
>> I started from scratch again, this time grabbing the uInitrd
>> for the boot partition and adding the bootargs you noted. On
>> first boot there now seems to be a net installation that
>> wants to format the rootfs and create a user, etc. This
>> seems to no longer be "Ubuntu core" and destroys the tarball
>> that was extracted to the rootfs and all the modifications.
>> Any idea what this uInitrd is? Is this the right one?
>> On Tuesday, November 13, 2012 11:47:26 PM UTC-8, Xavier
>> Boudet wrote:
>> Hi Jared,
>> Apparently you are facing uInitrd issue.
>> We realized very recently that without the uInitrd, udevd
>> was not starting correctly and as a consequence ducati is
>> not starting correctly:
>> [ 11.963928] rproc remoteproc1: failed waiting for udev -2
>> [ 11.970092] rproc remoteproc0: failed waiting for udev -2
>> It is still not clear why we are facing this issue, but
>> we are investigating.
>> You just need to update your boot.scr/boot.script
>> accordingly:
>> fatload mmc 0:1 0x80000000 uImage
>> *fatload mmc 0:1 0x81600000 uInitrd*
>> setenv bootargs <... your current bootargs, no change>
>> *bootm 0x80000000 0x81600000*
>> On 11/13/2012 08:14 PM, JB wrote:
>>> Oh, oops. I had copied the recommended bootargs "ro
>>> elevator=noop console=ttyO2,115200n8 mem=1G@0x80000000
>>> root=/dev/mmcblk0p2 fixrtc splash" from one of the other
>>> posts here. I don't want to mount the root filesystem
>>> as read-only... I am now using these bootargs in a new
>>> boot.scr:
>>> - I can again login from the serial console
>>> - The DVI display has a login prompt and I can login
>>> there as well
>>> - The HDMI display shows nothing (monitor goes into
>>> powersaving mode)
>>> At the DVI display, if I login as root, startx, see
>>> omapdrm_pvr from lsmod, and run the recommended
>>> gstreamer pipeline, I get an error and see no output:
>>> root@localhost:~# ./gst.sh
>>> Setting pipeline to PAUSED ...
>>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138
>>> returned [80, /bridged_pvr_dc_glue.c]
>>> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138
>>> returned [80, /bridged_pvr_dc_glue.c]
>>> libdce-x11.c:64: dce_auth_x11 info: attempting
>>> to open X11 connection
>>> *libdce.c:459: init error: could not get plugin ioctl
>>> base: -22*
>>> ERROR: Pipeline doesn't want to pause.
>>> Setting pipeline to NULL ...
>>> PVR:(Warning): PVRDRMSetFD: DRM fd already set [57,
>>> /pvr_bridge_u.c]
>>> Freeing pipeline ...
>>> root@localhost:~#
>>> Output from dmesg is attached if that helps any... Thanks!
>>> Jared
>>> On Tuesday, November 13, 2012 10:39:38 AM UTC-8, JB wrote:
>>> I plugged into the DVI port on the Pandaboard,
>>> powered on, and saw two penguins in the upper left
>>> corner. I then tried the HDMI port and saw the same
>>> thing. At this point I was unable to log in via the
>>> serial console, and saw no login prompt from either
>>> display - just penguins. I can ping the board's IP
>>> address but not SSH. I'm probably missing something
>>> obvious here...
>>> Jared
>>> On Sunday, November 11, 2012 11:40:35 PM UTC-8,
>>> Xavier Boudet wrote:
>>> Answers inline.
>>> Can you clarify what is/are the remaining
>>> issue(s)? The gst pipeline?
>>> Regards, Xavier Boudet
>>> On 11/09/2012 08:23 PM, JB wrote:
>>>> Hi Xavier. Thanks very much for the quick
>>>> reply! I'm pretty new to Pandaboard and I've
>>>> been trying to get a minimal Ubuntu core image
I ran into the same problem right now. Yesterday it'd worked perfectly, today it didn't. I realised that pandaboard (obviously /no battery/ :) ) looses date/time settings when unplugged. That's why it couldn't do the verification with the server. When I set the correct date, it worked fine. So probably when you went to eat lunch, ubuntu has updated the date/time from a time server ;)
On Wednesday, November 14, 2012 8:00:18 PM UTC+1, wb666...@gmail.com wrote:
> Don't know if its because I'd rebooted the Pandaboard to poke around the > SD card to see if I could figure out how to add the PPA manually (wan't > obvious) or because whatever network issue there was fixed itself while I > ate lunch.
> If you have this problem try rebooting the Pandaboard and if that fails > try again an hour or so later.
> On Wednesday, November 14, 2012 11:42:56 AM UTC-6, wb666...@gmail.comwrote:
>> I did it from the Linux Mint 13 host that is running the minicom talking >> to the Pandaboard and it added the repo and got the key.
>> Both systems are connected to the same router box. Of it does no me no >> good here.
>> On Wednesday, November 14, 2012 11:12:38 AM UTC-6, Xavier Boudet wrote:
>>> The error your are facing is typically due to bad proxy settings. >>> Are you behind a proxy? >>> Have you set correctly http_proxy and https_proxy?
>>> On Tuesday, September 4, 2012 7:25:09 AM UTC-5, Boudet, Xavier wrote:
>>>> Hi there,
>>>> A major update has been done on TI PPA. Please read the below e-mail >>>> especially for upgrade. >>>> If you do not have installed the TI release PPA, please refer to New >>>> installation procedure.
>>>> *New installation procedure:* >>>> 1- Add TI OMAP release PPA: >>>> $ sudo su - >>>> # export http_proxy=<your proxy if any> >>>> # export https_proxy=<your proxy if any> >>>> # add-apt-repository ppa:tiomap-dev/release
>>>> This step is failing for me with the following error:
