Kernel booting hangs in Beagleboard - xm.

Hi all,

I'm trying to compile the kernel I got from
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
for my beagleboard-xm rev C.

I did the following steps.

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
INSTALL_MOD_PATH=/media/Narcissus-rootfs/ modules_install

I copied the uImage into /media/Narcissus-rootfs/boot/ (the boot
folder in the ext3 partition of the mmc) and modified the 'uImage'
link there to point to my image. I also changed the ttyS2 in the
uEnv.txt to ttyO2.

Upon booting the kernel, I entered the u-boot prompt and did "setenv
console ttyO2,115200n8".

The kernel started booting and produced the following log. However,
once it reaches that point, it is not going any further.

what for? Get sources that work 100% and enjoy

what for? Get sources that work 100% and enjoy

Could you point me to sources that work 100%? I thought
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
was the kernel configured properly for OMAP processors.

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
On Behalf Of Haris Ibrahim K. V.
Sent: Monday, May 14, 2012 8:17 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Kernel booting hangs in Beagleboard - xm.

> what for? Get sources that work 100% and enjoy

Could you point me to sources that work 100%? I thought
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
was the kernel configured properly for OMAP processors.

I posed this yesterday, but since you are asking the same question here again, here is what I recommend. For developers who are new to Linux/BeagleBoard, I suggest that you use Angstrom to build your kernel as it takes care of everything you need. If you are planning to make changes to the kernel, then I suggest that you do the following:

Clone the GIT repository https://github.com/beagleboard/kernel as this includes a script to clone the latest mainline kernel and apply the same patches Angstrom uses when building the kernel. After you clone this repository, you need to checkout the correct tag using git checkout origin/beagleboard-3.2 –b beagleboard-3.2 for BeagleBoard or git checkout origin/beaglebone-3.2 –b beaglebone-3.2 for Beaglebone. After that, just run the script and it will clone the mainline kernel and then patch it for you. Make sure you are using the latest u-boot.bin or you may have some problems booting.

You can also build the 3.4 kernel, but I don't know how stable it is at this time.

Regards
John

I’m not sure 3.2 is stable either

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
On Behalf Of Haris Ibrahim K. V.
Sent: Monday, May 14, 2012 8:17 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Kernel booting hangs in Beagleboard - xm.

> what for? Get sources that work 100% and enjoy

Could you point me to sources that work 100%? I thought
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
was the kernel configured properly for OMAP processors.

I posed this yesterday, but since you are asking the same question here again, here is what I recommend. For developers who are new to Linux/BeagleBoard, I suggest that you use Angstrom to build your kernel as it takes care of everything you need. If you are planning to make changes to the kernel, then I suggest that you do the following:

Clone the GIT repository https://github.com/beagleboard/kernel as this includes a script to clone the latest mainline kernel and apply the same patches Angstrom uses when building the kernel. After you clone this repository, you need to checkout the correct tag using git checkout origin/beagleboard-3.2 –b beagleboard-3.2 for BeagleBoard or git checkout origin/beaglebone-3.2 –b beaglebone-3.2 for Beaglebone. After that, just run the script and it will clone the mainline kernel and then patch it for you. Make sure you are using the latest u-boot.bin or you may have some problems booting.

Thank you for helping out. It would be great if you could tell me how
I can know whether I'm using the latest u-boot.bin. And if I'm not,
where can I get the latest from?

Also, being a fresher, I'm a bit confused so as to whether I should
compile the kernel source after applying the patches just as before
itself. Like below?

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
INSTALL_MOD_PATH=/media/Narcissus-rootfs/ modules_install

I'm guessing that I might be able to run make (without copying the
configurations and passing the ARCH and CROSS_COMPILE arguments)
directly since the kernel is already configured for the beagleboard.
If that is the case would "make uImage" be sufficient?

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
On Behalf Of Haris Ibrahim K. V.
Sent: Monday, May 14, 2012 8:17 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Kernel booting hangs in Beagleboard - xm.

> what for? Get sources that work 100% and enjoy

Could you point me to sources that work 100%? I thought
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
was the kernel configured properly for OMAP processors.

I posed this yesterday, but since you are asking the same question here again, here is what I recommend. For developers who are new to Linux/BeagleBoard, I suggest that you use Angstrom to build your kernel as it takes care of everything you need. If you are planning to make changes to the kernel, then I suggest that you do the following:

Clone the GIT repository https://github.com/beagleboard/kernel as this includes a script to clone the latest mainline kernel and apply the same patches Angstrom uses when building the kernel. After you clone this repository, you need to checkout the correct tag using git checkout origin/beagleboard-3.2 –b beagleboard-3.2 for BeagleBoard or git checkout origin/beaglebone-3.2 –b beaglebone-3.2 for Beaglebone. After that, just run the script and it will clone the mainline kernel and then patch it for you. Make sure you are using the latest u-boot.bin or you may have some problems booting.

Thank you for helping out. It would be great if you could tell me how
I can know whether I'm using the latest u-boot.bin. And if I'm not,
where can I get the latest from?

Also, being a fresher, I'm a bit confused so as to whether I should
compile the kernel source after applying the patches just as before
itself. Like below?

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
INSTALL_MOD_PATH=/media/Narcissus-rootfs/ modules_install

I'm guessing that I might be able to run make (without copying the
configurations and passing the ARCH and CROSS_COMPILE arguments)
directly since the kernel is already configured for the beagleboard.
If that is the case would "make uImage" be sufficient?

I tried my older steps as follows:

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

and I got the following errors in between compilation:

arch/arm/mach-omap2/board-omap3beagle.c: In function 'omap3_beagle_init':
arch/arm/mach-omap2/board-omap3beagle.c:946:3: error: implicit
declaration of function 'wl12xx_set_platform_data'
[-Werror=implicit-function-declaration]
arch/arm/mach-omap2/board-omap3beagle.c:946:33: error:
'omap_beagle_wlan_data' undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:946:33: note: each undeclared
identifier is reported only once for each function it appears in
arch/arm/mach-omap2/board-omap3beagle.c:949:29: error: 'wl12xx_device'
undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:950:29: error:
'btwilink_device' undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:952:29: error:
'omap_vwlan_device' undeclared (first use in this function)
cc1: some warnings being treated as errors

make[1]: *** [arch/arm/mach-omap2/board-omap3beagle.o] Error 1
make: *** [arch/arm/mach-omap2] Error 2
make: *** Waiting for unfinished jobs....

Could this be because I used the omap2plus_defconfig?

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
On Behalf Of Haris Ibrahim K. V.
Sent: Monday, May 14, 2012 8:17 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Kernel booting hangs in Beagleboard - xm.

> what for? Get sources that work 100% and enjoy

Could you point me to sources that work 100%? I thought
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
was the kernel configured properly for OMAP processors.

I posed this yesterday, but since you are asking the same question here again, here is what I recommend. For developers who are new to Linux/BeagleBoard, I suggest that you use Angstrom to build your kernel as it takes care of everything you need. If you are planning to make changes to the kernel, then I suggest that you do the following:

Clone the GIT repository https://github.com/beagleboard/kernel as this includes a script to clone the latest mainline kernel and apply the same patches Angstrom uses when building the kernel. After you clone this repository, you need to checkout the correct tag using git checkout origin/beagleboard-3.2 –b beagleboard-3.2 for BeagleBoard or git checkout origin/beaglebone-3.2 –b beaglebone-3.2 for Beaglebone. After that, just run the script and it will clone the mainline kernel and then patch it for you. Make sure you are using the latest u-boot.bin or you may have some problems booting.

Thank you for helping out. It would be great if you could tell me how
I can know whether I'm using the latest u-boot.bin. And if I'm not,
where can I get the latest from?

Also, being a fresher, I'm a bit confused so as to whether I should
compile the kernel source after applying the patches just as before
itself. Like below?

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
INSTALL_MOD_PATH=/media/Narcissus-rootfs/ modules_install

I'm guessing that I might be able to run make (without copying the
configurations and passing the ARCH and CROSS_COMPILE arguments)
directly since the kernel is already configured for the beagleboard.
If that is the case would "make uImage" be sufficient?

I tried my older steps as follows:

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

and I got the following errors in between compilation:

arch/arm/mach-omap2/board-omap3beagle.c: In function 'omap3_beagle_init':
arch/arm/mach-omap2/board-omap3beagle.c:946:3: error: implicit
declaration of function 'wl12xx_set_platform_data'
[-Werror=implicit-function-declaration]
arch/arm/mach-omap2/board-omap3beagle.c:946:33: error:
'omap_beagle_wlan_data' undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:946:33: note: each undeclared
identifier is reported only once for each function it appears in
arch/arm/mach-omap2/board-omap3beagle.c:949:29: error: 'wl12xx_device'
undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:950:29: error:
'btwilink_device' undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:952:29: error:
'omap_vwlan_device' undeclared (first use in this function)
cc1: some warnings being treated as errors

make[1]: *** [arch/arm/mach-omap2/board-omap3beagle.o] Error 1
make: *** [arch/arm/mach-omap2] Error 2
make: *** Waiting for unfinished jobs....

Could this be because I used the omap2plus_defconfig?

I changed the wl12xx drivers to be built into the image rather than
them being modules. The compilation proceeded successfully and I got
the uImage. I built the modules, installed them and did the necessary
copying as I had mentioned in my first mail.

The kernel booted up, but got stuck at four steps before than the
earlier stuck. Earlier it was:

usb-ehci-omap.0-2.1, smsc95xx USB 28
[ 5.597290] udevd (557): /proc/557/oom_adj is deprecated, please
use /proc/557/oom_score_adj ins.
[ 15.784301] alignment: ignoring faults is unsafe on this CPU.
Defaulting to fixup mode.
[ 42.251464] netlink: 12 bytes leftover after parsing attributes.
[ 42.257904] netlink: 12 bytes leftover after parsing attributes.
k ֢&r&f��6F] netlink: 12 bytes leftover after parsing attributes.
[ 52.847290] netlink: 33 bytes leftover after parsing attributes.
[ 52.853820] netlink: 33 bytes leftover after parsing attributes.
[ 52.860778] netlink: 33 bytes leftover after parsing attributes.
[ 52.886199] zeroconf calls setitimer() with new_value NULL pointer.
Misfeature support will be rd

Now it is:

[ 14.318054] kjournald starting. Commit interval 5 seconds
[ 14.324462] EXT3-fs (mmcblk0p2): warning: maximal mount count
reached, running e2fsck is recommed
[ 14.965209] EXT3-fs (mmcblk0p2): using internal journal
[ 14.970642] EXT3-fs (mmcblk0p2): recovery complete
[ 14.984283] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
[ 14.991821] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 14.998535] Freeing init memory: 308K
[ 15.870666] udevd (592): /proc/592/oom_adj is deprecated, please
use /proc/592/oom_score_adj ins.
[ 25.219238] alignment: ignoring faults is unsafe on this CPU.
Defaulting to fixup mode.

What could be the problem here? I had cloned the kernel that you
mentioned and had run the patch script successfully.

Thanks for helping out.

omap2plus_config is not for the Beagleboard as far as I know

It's a generic basis for all omap2+ devices including the beagleboard
and should boot to a console prompt on all omap2+ devices.. Beyond
that you may have to enable config options not currently selected by
default for more features..

Regards,

hi,

just go through the make file you will get…

omap2plus_config is not for the Beagleboard as far as I know

It's a generic basis for all omap2+ devices including the beagleboard
and should boot to a console prompt on all omap2+ devices.. Beyond
that you may have to enable config options not currently selected by
default for more features..

In the older kernels, there was a config specially for beagleboard.
But from 2.6.35+ or so, it was made as omap2plus_defconfig.

I'm not actually looking to add more features. I'd like to just get
the kernel up and running with minimal features. But I'm getting stuck
when trying to do that.

Thanks for taking time to reply. I'd be grateful for any leads that
you could give me to get the kernel up and running. :slight_smile:

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

-- To join: http://beagleboard.org/discuss
To unsubscribe from this group, send email to:
beagleboard+unsubscribe@googlegroups.com
Frequently asked questions: http://beagleboard.org/faq

Regards,

Well your building from tmlind's master tree right as they getting
ready for the v3.5-rc0 merge... Build something else not in as much
flux, such as 3.4-rc7/mainline, and here's a patchset to achieve the
minimal features on top of that..

https://github.com/beagleboard/kernel/tree/beagleboard-3.4

Regards,

omap2plus_config is not for the Beagleboard as far as I know

It's a generic basis for all omap2+ devices including the beagleboard
and should boot to a console prompt on all omap2+ devices.. Beyond
that you may have to enable config options not currently selected by
default for more features..

In the older kernels, there was a config specially for beagleboard.
But from 2.6.35+ or so, it was made as omap2plus_defconfig.

I'm not actually looking to add more features. I'd like to just get
the kernel up and running with minimal features. But I'm getting stuck
when trying to do that.

Thanks for taking time to reply. I'd be grateful for any leads that
you could give me to get the kernel up and running. :slight_smile:

Well your building from tmlind's master tree right as they getting
ready for the v3.5-rc0 merge... Build something else not in as much
flux, such as 3.4-rc7/mainline, and here's a patchset to achieve the
minimal features on top of that..

https://github.com/beagleboard/kernel/tree/beagleboard-3.4

I already am on the 3.4 branch in the repo that you have mentioned.

haris@asylum:~/source/kernel$ git br -a
  beagleboard-3.2
* beagleboard-3.4
  master
  remotes/origin/HEAD -> origin/master
  remotes/origin/beagleboard-3.0
  remotes/origin/beagleboard-3.2
  remotes/origin/beagleboard-3.4
  remotes/origin/beaglebone-3.2
  remotes/origin/master
haris@asylum:~/source/kernel$ git log
commit 1a869d36436d9b7f95f8f6a58b9cbd1503e34e4d
Author: Robert Nelson <robertcnelson@gmail.com>

    beagleboard-3.4: update to 3.4-rc7

    Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

After checking that branch out, I had run ./patch.sh and after that
successfully completed, I compiled the kernel and tried to boot from
it. And that's when it got stuck at the point that I mentioned
earlier.

I hope running ./patch.sh after checking out to the 3.4 branch is what
you meant by "here's a patchset to achieve the minimal features on top
of that."

Are there any other options I could try in order to get this working?

Regards,

Did you use the config under the patches/beagleboard directory?

https://github.com/beagleboard/kernel/blob/beagleboard-3.4/patches/beagleboard/defconfig

Regards,

omap2plus_config is not for the Beagleboard as far as I know

It's a generic basis for all omap2+ devices including the beagleboard
and should boot to a console prompt on all omap2+ devices.. Beyond
that you may have to enable config options not currently selected by
default for more features..

In the older kernels, there was a config specially for beagleboard.
But from 2.6.35+ or so, it was made as omap2plus_defconfig.

I'm not actually looking to add more features. I'd like to just get
the kernel up and running with minimal features. But I'm getting stuck
when trying to do that.

Thanks for taking time to reply. I'd be grateful for any leads that
you could give me to get the kernel up and running. :slight_smile:

Well your building from tmlind's master tree right as they getting
ready for the v3.5-rc0 merge... Build something else not in as much
flux, such as 3.4-rc7/mainline, and here's a patchset to achieve the
minimal features on top of that..

https://github.com/beagleboard/kernel/tree/beagleboard-3.4

I already am on the 3.4 branch in the repo that you have mentioned.

haris@asylum:~/source/kernel$ git br -a
beagleboard-3.2
* beagleboard-3.4
master
remotes/origin/HEAD -> origin/master
remotes/origin/beagleboard-3.0
remotes/origin/beagleboard-3.2
remotes/origin/beagleboard-3.4
remotes/origin/beaglebone-3.2
remotes/origin/master
haris@asylum:~/source/kernel$ git log
commit 1a869d36436d9b7f95f8f6a58b9cbd1503e34e4d
Author: Robert Nelson <robertcnelson@gmail.com>
Date: Mon May 14 12:06:28 2012 -0500

beagleboard-3.4: update to 3.4-rc7

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

After checking that branch out, I had run ./patch.sh and after that
successfully completed, I compiled the kernel and tried to boot from
it. And that's when it got stuck at the point that I mentioned
earlier.

I hope running ./patch.sh after checking out to the 3.4 branch is what
you meant by "here's a patchset to achieve the minimal features on top
of that."

Are there any other options I could try in order to get this working?

Did you use the config under the patches/beagleboard directory?

https://github.com/beagleboard/kernel/blob/beagleboard-3.4/patches/beagleboard/defconfig

No. I had used the omap2plus defconfig. What should I do in order to
use the defconfig that you have mentioned. My directory is as follows:

haris@asylum:~/source/kernel$ ls
export kernel patches patch_script.sh patch.sh README.md src-uri.txt

I have my sources in the 'kernel' directory there. So is the following
line correct?

haris@asylum:~/source/kernel/kernel$ make -j2 ARCH=arm
CROSS_COMPILE=arm-none-linux-gnueabi- ../patches/beagleboard/defconfig

Or should I copy that 'defconfig' file to the arch/arm/configs/ folder
of my kernel source and then use it?

I'd just copy as "cp ./patches/beagleboard/defconfig ./kernel/.config"
then cd in ./kernel and

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

Regards,

omap2plus_config is not for the Beagleboard as far as I know

It's a generic basis for all omap2+ devices including the beagleboard
and should boot to a console prompt on all omap2+ devices.. Beyond
that you may have to enable config options not currently selected by
default for more features..

In the older kernels, there was a config specially for beagleboard.
But from 2.6.35+ or so, it was made as omap2plus_defconfig.

I'm not actually looking to add more features. I'd like to just get
the kernel up and running with minimal features. But I'm getting stuck
when trying to do that.

Thanks for taking time to reply. I'd be grateful for any leads that
you could give me to get the kernel up and running. :slight_smile:

Well your building from tmlind's master tree right as they getting
ready for the v3.5-rc0 merge... Build something else not in as much
flux, such as 3.4-rc7/mainline, and here's a patchset to achieve the
minimal features on top of that..

https://github.com/beagleboard/kernel/tree/beagleboard-3.4

I already am on the 3.4 branch in the repo that you have mentioned.

haris@asylum:~/source/kernel$ git br -a
beagleboard-3.2
* beagleboard-3.4
master
remotes/origin/HEAD -> origin/master
remotes/origin/beagleboard-3.0
remotes/origin/beagleboard-3.2
remotes/origin/beagleboard-3.4
remotes/origin/beaglebone-3.2
remotes/origin/master
haris@asylum:~/source/kernel$ git log
commit 1a869d36436d9b7f95f8f6a58b9cbd1503e34e4d
Author: Robert Nelson <robertcnelson@gmail.com>
Date: Mon May 14 12:06:28 2012 -0500

beagleboard-3.4: update to 3.4-rc7

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

After checking that branch out, I had run ./patch.sh and after that
successfully completed, I compiled the kernel and tried to boot from
it. And that's when it got stuck at the point that I mentioned
earlier.

I hope running ./patch.sh after checking out to the 3.4 branch is what
you meant by "here's a patchset to achieve the minimal features on top
of that."

Are there any other options I could try in order to get this working?

Did you use the config under the patches/beagleboard directory?

https://github.com/beagleboard/kernel/blob/beagleboard-3.4/patches/beagleboard/defconfig

No. I had used the omap2plus defconfig. What should I do in order to
use the defconfig that you have mentioned. My directory is as follows:

haris@asylum:~/source/kernel$ ls
export kernel patches patch_script.sh patch.sh README.md src-uri.txt

I have my sources in the 'kernel' directory there. So is the following
line correct?

haris@asylum:~/source/kernel/kernel$ make -j2 ARCH=arm
CROSS_COMPILE=arm-none-linux-gnueabi- ../patches/beagleboard/defconfig

Or should I copy that 'defconfig' file to the arch/arm/configs/ folder
of my kernel source and then use it?

I'd just copy as "cp ./patches/beagleboard/defconfig ./kernel/.config"
then cd in ./kernel and

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

Thank you for bearing with me. I've done as you suggested and the
compilation is underway. Let's hope we get a positive result. :slight_smile: I'll
get back with whatever the result is.

Regards,

With that config, it's booting fine on my Beagle/Panda in the lab, the
biggest change with that version is the switch to using kms/omapdrm by
default, so you don't need the old "vram=${vram}
omapfb.mode=${defaultdisplay}:${dvimode}
omapdss.def_disp=${defaultdisplay}" stuff in uEnv.txt any more and it
should auto detect your dvi monitor's resolution..

Regards,

omap2plus_config is not for the Beagleboard as far as I know

It's a generic basis for all omap2+ devices including the beagleboard
and should boot to a console prompt on all omap2+ devices.. Beyond
that you may have to enable config options not currently selected by
default for more features..

In the older kernels, there was a config specially for beagleboard.
But from 2.6.35+ or so, it was made as omap2plus_defconfig.

I'm not actually looking to add more features. I'd like to just get
the kernel up and running with minimal features. But I'm getting stuck
when trying to do that.

Thanks for taking time to reply. I'd be grateful for any leads that
you could give me to get the kernel up and running. :slight_smile:

Well your building from tmlind's master tree right as they getting
ready for the v3.5-rc0 merge... Build something else not in as much
flux, such as 3.4-rc7/mainline, and here's a patchset to achieve the
minimal features on top of that..

https://github.com/beagleboard/kernel/tree/beagleboard-3.4

I already am on the 3.4 branch in the repo that you have mentioned.

haris@asylum:~/source/kernel$ git br -a
beagleboard-3.2
* beagleboard-3.4
master
remotes/origin/HEAD -> origin/master
remotes/origin/beagleboard-3.0
remotes/origin/beagleboard-3.2
remotes/origin/beagleboard-3.4
remotes/origin/beaglebone-3.2
remotes/origin/master
haris@asylum:~/source/kernel$ git log
commit 1a869d36436d9b7f95f8f6a58b9cbd1503e34e4d
Author: Robert Nelson <robertcnelson@gmail.com>
Date: Mon May 14 12:06:28 2012 -0500

beagleboard-3.4: update to 3.4-rc7

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

After checking that branch out, I had run ./patch.sh and after that
successfully completed, I compiled the kernel and tried to boot from
it. And that's when it got stuck at the point that I mentioned
earlier.

I hope running ./patch.sh after checking out to the 3.4 branch is what
you meant by "here's a patchset to achieve the minimal features on top
of that."

Are there any other options I could try in order to get this working?

Did you use the config under the patches/beagleboard directory?

https://github.com/beagleboard/kernel/blob/beagleboard-3.4/patches/beagleboard/defconfig

No. I had used the omap2plus defconfig. What should I do in order to
use the defconfig that you have mentioned. My directory is as follows:

haris@asylum:~/source/kernel$ ls
export kernel patches patch_script.sh patch.sh README.md src-uri.txt

I have my sources in the 'kernel' directory there. So is the following
line correct?

haris@asylum:~/source/kernel/kernel$ make -j2 ARCH=arm
CROSS_COMPILE=arm-none-linux-gnueabi- ../patches/beagleboard/defconfig

Or should I copy that 'defconfig' file to the arch/arm/configs/ folder
of my kernel source and then use it?

I'd just copy as "cp ./patches/beagleboard/defconfig ./kernel/.config"
then cd in ./kernel and

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

Thank you for bearing with me. I've done as you suggested and the
compilation is underway. Let's hope we get a positive result. :slight_smile: I'll
get back with whatever the result is.

With that config, it's booting fine on my Beagle/Panda in the lab, the
biggest change with that version is the switch to using kms/omapdrm by
default, so you don't need the old "vram=${vram}
omapfb.mode=${defaultdisplay}:${dvimode}
omapdss.def_disp=${defaultdisplay}" stuff in uEnv.txt any more and it
should auto detect your dvi monitor's resolution..

I still am in my infancy regarding the changes that you have just
said. As such, I find it hard to understand what kms/omapdrm is.

A little about what I'm trying to do. I'm trying to learn to write a
driver. So right now my aim is to make the beagleboard behave as a
sound card. After plugging in the microphone, when you speak into it,
a small application program on the beagleboard will read from the
driver (the ALSA mixer I believe it is) and write to the USB gadget
driver that I'm going to write by modifying the existing f_audio.c
driver in the kernel. Once that is done, after plugging in the board,
I should be able to use some music application to play the sound that
we spoke into the microphone.

Easier said than done. :slight_smile: