[yocto] Kernel does not emit any boot-up messages
Hi All, A newbie question: After creating a new bsp for an Overo using the yocto-bsp script and modifying some kernel config's using menuconfig, I successfully created and loaded the image (core-image-minimal) onto an SD card and booted it. However, I do not see the kernel emitting any boot messages. Am I forgetting to include some recipes? > OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz > OMAP3 Beagle board + LPDDR/NAND > I2C: ready > DRAM: 512 MiB > NAND: 512 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - bad CRC, using default environment > > In:serial > Out: serial > Err: serial > Beagle Rev Ax/Bx > No EEPROM on expansion board > Die ID #36be00029ff8016071640201b009 > Hit any key to stop autoboot: 0 > SD/MMC found on device 0 > reading uEnv.txt > > ** Unable to read "uEnv.txt" from mmc 0:1 ** > reading uImage > > 3356520 bytes read > Booting from mmc ... > ## Booting kernel from Legacy Image at 8200 ... >Image Name: Linux-3.2.18-rt16-yocto-preempt- >Image Type: ARM Linux Kernel Image (uncompressed) >Data Size:3356456 Bytes = 3.2 MiB >Load Address: 80008000 >Entry Point: 80008000 >Verifying Checksum ... OK >Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > Yocto (Built by Poky 7.0) 1.2+snapshot-20120828 > ttyO2 > > overo login: root > root@overo:~# uname -a > Linux overo 3.2.18-rt16-yocto-preempt-rt #4 PREEMPT RT Tue Aug 28 22:36:26 > SAST 2012 armv7l GNU/Linux > > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel does not emit any boot-up messages
On 2012-08-29 05:04, Hartmut Behrens wrote: Hi All, A newbie question: After creating a new bsp for an Overo using the yocto-bsp script and modifying some kernel config's using menuconfig, I successfully created and loaded the image (core-image-minimal) onto an SD card and booted it. However, I do not see the kernel emitting any boot messages. Am I forgetting to include some recipes? OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 512 MiB MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Beagle Rev Ax/Bx No EEPROM on expansion board Die ID #36be00029ff8016071640201b009 Hit any key to stop autoboot: 0 SD/MMC found on device 0 reading uEnv.txt ** Unable to read "uEnv.txt" from mmc 0:1 ** reading uImage 3356520 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 8200 ... Image Name: Linux-3.2.18-rt16-yocto-preempt- Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3356456 Bytes = 3.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Yocto (Built by Poky 7.0) 1.2+snapshot-20120828 ttyO2 overo login: root root@overo:~# uname -a Linux overo 3.2.18-rt16-yocto-preempt-rt #4 PREEMPT RT Tue Aug 28 22:36:26 SAST 2012 armv7l GNU/Linux Make sure your [U-Boot] bootargs contain 'console=ttyO2,115200' -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] configuring WiFi in Yocto
On 24 August 2012 19:36, Jim Abernathy wrote: > On 08/24/2012 02:23 PM, Ross Burton wrote: > See the linux-firmware packages. There are a few split out sub packages, and > then linux-firmware contains the rest. > > I see the rtl8192 firmware included in the linux-firmware recipe, but not > sure if there is a step to force a load of the firmware. Whoops, accidentally took this off-list by using my phone. If this is still broken, can you attach the output of dmesg, ifconfig and iwconfig on a fresh boot? Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [SPAM] - Re: Ubuntu PPA usage in Yocto - Email found in subject
Indeed, that does make sense ... Thanks for the reply, Kind regards, Tim -Original Message- From: Khem Raj [mailto:raj.k...@gmail.com] Sent: dinsdag 28 augustus 2012 19:04 To: Tim Verstraete Cc: yocto@yoctoproject.org Subject: [SPAM] - Re: [yocto] Ubuntu PPA usage in Yocto - Email found in subject On Tue, Aug 28, 2012 at 2:50 AM, Tim Verstraete wrote: > Hi everybody, > > > > I keep on seeing some interesting software packages into the PPA for > Ubuntu ... now I was wondering is there a way within Yocto to reuse > those PPA package (not from the machine with apt-get) but with a recipe? > > > > Take for example the TI OMAP4 … on the TI Launchpad I see: > https://launchpad.net/~tiomap-dev/+archive/release pvr-omap4-dkms and > i would like to use this. How should I add such thing in yocto. > > well you would start by using PACKAGE_CLASSES = " package_deb" in your local.conf that should generate you an image with dpkg as packaging backend IMAGE_FEATURES += "package-management" that will add online package management component to your image build your image and it should have knobs for hooking in feeds if you know how its done for apt bigger problems start here where the packages in that PPA may require different versions of package dependencies than what you get from yocto image and even worse they might use a different ABI etc. > > Thank in advance, > > > > Kind regards, > > > > Tim > > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel does not emit any boot-up messages
What does your. Overo machine.conf looks like ? -Khem On Aug 29, 2012, at 4:04 AM, Hartmut Behrens wrote: > Hi All, > > A newbie question: > > After creating a new bsp for an Overo using the yocto-bsp script and > modifying some kernel config's using menuconfig, I successfully created and > loaded the image (core-image-minimal) onto an SD card and booted it. > > However, I do not see the kernel emitting any boot messages. Am I forgetting > to include some recipes? > > > > OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz > OMAP3 Beagle board + LPDDR/NAND > I2C: ready > DRAM: 512 MiB > NAND: 512 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - bad CRC, using default environment > > In:serial > Out: serial > Err: serial > Beagle Rev Ax/Bx > No EEPROM on expansion board > Die ID #36be00029ff8016071640201b009 > Hit any key to stop autoboot: 0 > SD/MMC found on device 0 > reading uEnv.txt > > ** Unable to read "uEnv.txt" from mmc 0:1 ** > reading uImage > > 3356520 bytes read > Booting from mmc ... > ## Booting kernel from Legacy Image at 8200 ... >Image Name: Linux-3.2.18-rt16-yocto-preempt- >Image Type: ARM Linux Kernel Image (uncompressed) >Data Size:3356456 Bytes = 3.2 MiB >Load Address: 80008000 >Entry Point: 80008000 >Verifying Checksum ... OK >Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > Yocto (Built by Poky 7.0) 1.2+snapshot-20120828 > ttyO2 > > overo login: root > root@overo:~# uname -a > Linux overo 3.2.18-rt16-yocto-preempt-rt #4 PREEMPT RT Tue Aug 28 22:36:26 > SAST 2012 armv7l GNU/Linux > > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?
On 08/27/2012 08:18 PM, Bruce Ashfield wrote: > On 12-08-27 8:14 PM, Saxena, Rahul wrote: >> Hi, >> >> I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky. >> >> When I try to boot a image such as core-image-sato, I get kernel panic >> and errors such as: >> >> VFS: Cannot open root device “ram0” or unkown-block(0,0) >> >> Please append a correct “root=” boot option; here are the available >> >> partitions: >> >> VFS: unable to mount root fs on unknown block(0,0) >> >> User configuration error – no valid rootfilesystem found >> >> I do see that the root file system exists in >> cedartrail-poky-linux/core-image-sato-1.0-r0/rootfs dir.. >> >> I did not see this problem when I uses a earlier commit of the Poky >> master branch. >> >> It seems like something broke with 1.3 M3 branch that prevents a proper >> build with 3.0 kernel. I do need to build my BSP with 3.0 kernel. >> >> (I was also told by Laurentiu Serban that 1.3 M3 Full Pass testing does >> not include testing with the 3.0 kernel) >> >> Any suggestions would be most welcome. I do need to build my BSP with >> the 3.0 kernel. > > Hmm. It should work, I booted one not that long ago. Can you force > qemux86 to prefer the 3.0 kernel and see if that boots ? That would > at least start to isolate the potential problem areas. However, won't 3.0 be removed for the 1.3 release? Keeping with 3.4 and 3.2? -- Darren > > Bruce > >> >> Thanks >> >> Rahul >> > -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?
On Tue, Aug 28, 2012 at 3:34 PM, Darren Hart wrote: > On 08/27/2012 08:18 PM, Bruce Ashfield wrote: >> On 12-08-27 8:14 PM, Saxena, Rahul wrote: >>> Hi, >>> >>> I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky. >>> >>> When I try to boot a image such as core-image-sato, I get kernel panic >>> and errors such as: >>> >>> VFS: Cannot open root device “ram0” or unkown-block(0,0) >>> >>> Please append a correct “root=” boot option; here are the available >>> >>> partitions: >>> >>> VFS: unable to mount root fs on unknown block(0,0) >>> >>> User configuration error – no valid rootfilesystem found >>> >>> I do see that the root file system exists in >>> cedartrail-poky-linux/core-image-sato-1.0-r0/rootfs dir.. >>> >>> I did not see this problem when I uses a earlier commit of the Poky >>> master branch. >>> >>> It seems like something broke with 1.3 M3 branch that prevents a proper >>> build with 3.0 kernel. I do need to build my BSP with 3.0 kernel. >>> >>> (I was also told by Laurentiu Serban that 1.3 M3 Full Pass testing does >>> not include testing with the 3.0 kernel) >>> >>> Any suggestions would be most welcome. I do need to build my BSP with >>> the 3.0 kernel. >> >> Hmm. It should work, I booted one not that long ago. Can you force >> qemux86 to prefer the 3.0 kernel and see if that boots ? That would >> at least start to isolate the potential problem areas. > > However, won't 3.0 be removed for the 1.3 release? Keeping with 3.4 and 3.2? For 1.3 the 3 kernel sliding window plan was 3.4, 3.2 and 3.0 with 2.6.37 being voted off the island. Or did you mean 1.4 ? Regardless, anything using 3.0 needs to be updated since it's time is running short! :) Cheers, Bruce > > -- > Darren > >> >> Bruce >> >>> >>> Thanks >>> >>> Rahul >>> >> > > > -- > Darren Hart > Intel Open Source Technology Center > Yocto Project - Linux Kernel > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?
>-Original Message- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Bruce Ashfield >Sent: Wednesday, August 29, 2012 10:47 AM >To: Hart, Darren >Cc: yocto@yoctoproject.org >Subject: Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 >kernel ? > >On Tue, Aug 28, 2012 at 3:34 PM, Darren Hart wrote: >> On 08/27/2012 08:18 PM, Bruce Ashfield wrote: >>> On 12-08-27 8:14 PM, Saxena, Rahul wrote: Hi, I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky. When I try to boot a image such as core-image-sato, I get kernel panic and errors such as: VFS: Cannot open root device "ram0" or unkown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: VFS: unable to mount root fs on unknown block(0,0) User configuration error - no valid rootfilesystem found I do see that the root file system exists in cedartrail-poky-linux/core-image-sato-1.0-r0/rootfs dir.. I did not see this problem when I uses a earlier commit of the Poky master branch. It seems like something broke with 1.3 M3 branch that prevents a proper build with 3.0 kernel. I do need to build my BSP with 3.0 kernel. (I was also told by Laurentiu Serban that 1.3 M3 Full Pass testing does not include testing with the 3.0 kernel) Any suggestions would be most welcome. I do need to build my BSP with the 3.0 kernel. >>> >>> Hmm. It should work, I booted one not that long ago. Can you force >>> qemux86 to prefer the 3.0 kernel and see if that boots ? That would >>> at least start to isolate the potential problem areas. >> >> However, won't 3.0 be removed for the 1.3 release? Keeping with 3.4 and >3.2? > >For 1.3 the 3 kernel sliding window plan was 3.4, 3.2 and 3.0 with 2.6.37 being >voted off the island. Or did you mean 1.4 ? Regardless, anything using 3.0 >needs >to be updated since it's time is running short! :) > Cedartrail BSP has PVR Graphics drivers which works only with 3.0 Kernel. Thanks Kishore. >Cheers, > >Bruce > >> >> -- >> Darren >> >>> >>> Bruce >>> Thanks Rahul >>> >> >> >> -- >> Darren Hart >> Intel Open Source Technology Center >> Yocto Project - Linux Kernel >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > > >-- >"Thou shalt not follow the NULL pointer, for chaos and madness await >thee at its end" >___ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Upgrade recipes name list
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version is unstable" You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason ccache3.1.7 3.1.8 Wenzong Fan xdg-utils 1.0.2 1.1.0 Valentin Popa liberation-fonts 1.04 2.00.0 Valentin Popa qemu 0.15.11.2.0 Valentin Popa matchbox-panel-2 0.0+git1+cdf7a22716b8746 2.0 Valentin Popa evolution-data-server 2.30+git1+3ca578d968d097 6.0 Valentin Popa puzzles r9561 9606 Valentin Popa lttng-viewer 0.12.38 0.12.38.21032011 Valentin Popa shadow4.1.4.3 4.1.5.1 Scott Garman blktool 4-6 4 Scott Garman apmd 3.2.2-14 3.2.2 Scott Garman openssh 6.0p1 6.1p1 Scott Garman createrepo0.4.110.9.9 Saul WoldVersions after 0.9.* use YUM,... apt 0.7.140.9.7.4 Saul Wold pkgconfig 0.25 0.27.1 Saul Wold0.26 removes glib-conf, adds ... build-appliance-image 1.0 3.2.1 Saul Wold util-linux2.21.22.22 Saul Wold libxml2 2.8.0 2.9.0 Saul Wold dhcp 4.2.4-P1 4.2.4 Saul Wold ftp://ftp.isc.org/isc/dhcp/4.2.4-P1/dhcp-4.2.4-P1.tar.gz logrotate 3.8.1 3.8.2 Robert Yang curl 7.26.07.27.0 Radu Moisan liburcu 0.6.7 0.7.4 Radu Moisan js1.7.0+1.8.0rc11.60 Radu Moisan u-boot-mkimage2011.06 2012.07 Radu Moisan valgrind 3.7.0 3.8.0 Radu Moisan babeltrace0.12+git1+0d8f8c2ea27df0 1.0.0 Radu Moisan udev 164 182 Radu Moisan mobile-broadband-provider-info1.0.0+gitr1+d9995ef693cb 20090309 Radu Moisan man-pages 3.41 3.42 No Maintainer information nativesdk-bdwgc 20110107 7.2alpha5 No Maintainer information nativesdk-curl7.26.07.27.0 No Maintainer information nativesdk-qemu0.15.11.2.0 No Maintainer information kconfig-frontends 3.5.0 3.5.0.0 No Maintainer information nativesdk-automake1.12.11.12.3 No Maintainer information nativesdk-pkgconf
[yocto] [Package Report System]Manual check recipes name list
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason lsb 1.4 1.4 133 day Yi Zhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?
-Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Bodke, Kishore K Sent: Wednesday, August 29, 2012 11:08 AM To: Bruce Ashfield; Hart, Darren Cc: yocto@yoctoproject.org Subject: Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ? >-Original Message- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Bruce Ashfield >Sent: Wednesday, August 29, 2012 10:47 AM >To: Hart, Darren >Cc: yocto@yoctoproject.org >Subject: Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto >3.0 kernel ? > >On Tue, Aug 28, 2012 at 3:34 PM, Darren Hart wrote: >> On 08/27/2012 08:18 PM, Bruce Ashfield wrote: >>> On 12-08-27 8:14 PM, Saxena, Rahul wrote: Hi, I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky. When I try to boot a image such as core-image-sato, I get kernel panic and errors such as: VFS: Cannot open root device "ram0" or unkown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: VFS: unable to mount root fs on unknown block(0,0) User configuration error - no valid rootfilesystem found I do see that the root file system exists in cedartrail-poky-linux/core-image-sato-1.0-r0/rootfs dir.. I did not see this problem when I uses a earlier commit of the Poky master branch. It seems like something broke with 1.3 M3 branch that prevents a proper build with 3.0 kernel. I do need to build my BSP with 3.0 kernel. (I was also told by Laurentiu Serban that 1.3 M3 Full Pass testing does not include testing with the 3.0 kernel) Any suggestions would be most welcome. I do need to build my BSP with the 3.0 kernel. >>> >>> Hmm. It should work, I booted one not that long ago. Can you force >>> qemux86 to prefer the 3.0 kernel and see if that boots ? That would >>> at least start to isolate the potential problem areas. >> >> However, won't 3.0 be removed for the 1.3 release? Keeping with 3.4 >> and >3.2? > >For 1.3 the 3 kernel sliding window plan was 3.4, 3.2 and 3.0 with >2.6.37 being voted off the island. Or did you mean 1.4 ? Regardless, >anything using 3.0 needs to be updated since it's time is running >short! :) > Cedartrail BSP has PVR Graphics drivers which works only with 3.0 Kernel. Thanks Kishore. I am mainly interested in ensuring 3.0 Kernel works with the next Yocto release (i.e. Yocto 1.3) since the CedarTrail BSP will work only with 3.0 Kernel due to a graphics driver dependency. We will not port the Cedartrail BSP beyond Yocto 1.3. Thanks Rahul >Cheers, > >Bruce > >> >> -- >> Darren >> >>> >>> Bruce >>> Thanks Rahul >>> >> >> >> -- >> Darren Hart >> Intel Open Source Technology Center >> Yocto Project - Linux Kernel >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > > >-- >"Thou shalt not follow the NULL pointer, for chaos and madness await >thee at its end" >___ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
