=== lilstevie|ZNC is now known as lilstevie [05:03] I've configured and built a new custom kernel for Ubuntu, but am having difficulty getting it to boot. There is at least one error in the rebuild scrpt in the tools directory - it doesn't pass the correct kernel version (of the new kernel) to the commands. I'm unable to use a keyboard attacked to the Beagle-xM to get more info. [05:04] Kernel drops me to an (initfs) prompt, but I can't enter anything to get more info. [05:08] This is under Maverick 10.10 === JaMa|Off is now known as JaMa === hrw|gone is now known as hrw [08:48] hi === JamieBen1ett is now known as JamieBennett === ian_brasil__ is now known as ian_brasil [10:47] hi all [10:47] i have troubles getting PowerVR SGX driver to work on blaze (omap4 ES1.0). [10:47] can somebody confirm that? [10:48] PVR_K: (FAIL) SGXInit: Incompatible HW core rev (10100) and SW core rev (10200). [10:50] whole dmesg output : http://pastebin.com/raw.php?i=ZzhF7Lzy [10:52] var/log/Xorg.0.log : http://pastebin.com/raw.php?i=w58UUAkU === ian_brasil__ is now known as ian_brasil === arun__ is now known as arun === kmargar is now known as markos_ [13:01] rsalveti: so, i couldn't reproduce the sd card corruption today, which is somewhat mysterious. [13:01] i swear it happened repeatedly on monday, but maybe i was on something good. [13:02] on an unrelated note, could this patch be incorporated into the ubuntu omap4 kernel? [13:02] http://marc.info/?l=linux-omap&m=128744421925804&w=2 [13:02] it's upstreamed and in 2.6.37-rc1 [13:03] * hrw wants it [13:03] how would that affect systems where users set the MAC from u-boot already ? [13:04] anyway my dhcp server forces same ip for device which asks as panda [13:04] in theory it shouldn't affect that at all. [13:04] it just allows you to override it after boot. [13:04] does the ubuntu omap4 kernel have a different patch for setting the mac address? [13:04] nope [13:05] file a bug and ask for SRU [13:05] should be possible to pull it into maverick === hrw is now known as hrw|afk [13:07] so it seems that the "linux" source package is collecting omap kernel bugs too. is that right? [13:08] for omap3, yes [13:08] and only in maverick [13:08] what about omap4? [13:08] for panda you want linux-ti-omap4 [13:09] ah, cheers. [13:09] mind you, the beagle has the same ethernet chip. [13:10] which is fine given we have two different kernel trees [13:11] for natty omap3 will use upstream [13:11] so should i file a bug on the linux package too? [13:11] for maverick if you want to [13:11] ah k [13:11] natty will get it qutomatically [13:11] where does the SRU tag go? subject? or is there a magic setting? [13:12] https://wiki.ubuntu.com/StableReleaseUpdates [13:26] wow. i couldn't even get two consecutive bug numbers within a couple of minutes. that's a disturbing bug rate :/ [13:26] but done. thanks! [13:28] well, we have many users ;) [13:30] many happy users too, i'm sure :) [13:30] hopefully :) [13:31] * bernard_ loves having a native ARM build environment where apt-get just works. [13:32] bernard_: what happen when you set the mac address at the cmdline? [13:32] does it works as expected and never reset it again? [13:33] rsalveti: cmdline as in kernel cmdline? [13:33] bernard_: yup, the current supported method [13:35] the patch seems fine, but it's something that you can already work with if you set it up at the kernel cmdline [13:42] okay, to save me the 15 minutes to download the kernel source, what's the kernel parameter? :) [13:43] 1 sec, changing git branch :-) [13:44] macaddr=01:23:45:67:89:AB [13:44] for example [13:45] so, I agree it makes sense to apply your patch, but the reason would be more to avoid recreating the mac address on every ifdown/ifup [13:45] because we already have a way to stick with only one mac address [13:45] cat /proc/cmdline [13:45] vram=16M,omapfb.vram=0:5M,1:5M mem=460M@0x80000000 mem=256M@0xA0000000 root=/dev/sda1 fixrtc console=ttyO2,115200n8 rootwait macaddr=00:80:c8:40:8a:de [13:45] but: % ip link list usb0 [13:45] 2: usb0: mtu 1492 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 7a:ea:e9:22:5a:4b brd ff:ff:ff:ff:ff:ff [13:47] uname -a: Linux cachehit 2.6.35-903-omap4 #14-Ubuntu SMP PREEMPT Wed Oct 6 17:23:24 UTC 2010 armv7l GNU/Linux [13:47] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commitdiff;h=10f38b455e75b85f72e98786e5518cf7b0324634;hp=f62e143182cc123fdfdf9bb88952a938af7d86e8 [13:47] rsalveti: another reason for using that patch is that it's what's in upstream, and consistent with other drivers. it also shouldn't break people who set it with current methods. [13:48] bernard_: sure [13:48] ahh. i think it needs smsc95xx.macaddr then [13:48] sure, you're right [13:49] ok, will build a new kernel with your patch, and will put this comment at the bug [13:49] thanks for reporting it [13:49] np. thank you! [13:52] ack. the smsc95xx.macaddr= indeed works too. [13:52] cool [14:05] rsalveti, bernard_: just reconnecting to irc right now and see your chat:) [14:05] I have already commented on the launchad bug [14:05] sebjan_: after posting my comment I saw that you also commented on it :-) [14:06] snap! [14:06] sebjan_: I'm now creating a new deb file to be tested [14:07] there is also bug 673509 for omap3 [14:07] Launchpad bug 673509 in linux (Ubuntu) "Beagleboard-xm chooses a new IP address on each boot (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/673509 [14:07] true, this would affect both [14:08] (sorry to make you do more work! know that it's all greatly appreciated!) [14:08] one more to the pipeline [14:08] :-) [14:08] np at all === hrw|afk is now known as hrw [14:23] NCommander, so i traced down the image build issues we have atm with cjwatson [14:23] NCommander, seems we have a dpkg bug [14:23] (telling you that because you wanted to work out why images fail) [14:40] * rsalveti lunch === zyga is now known as zyga-lunch [16:25] ogra_ac: any chance to fix the current alsa-utils issue? [16:25] rsalveti, not yet, i discussed several solutions and have to pick one [16:25] generally we need a script that removes itself after first boot and calls the alsactl init [16:26] s/boot/reboot/ [16:26] i'm just still pondering about the implementation details since all solutions are butt ugly [16:26] ogra_ac: but we still need to explicit call alsactl init? [16:26] yes [16:26] once [16:26] and you need to call it after reboot [16:27] since the kernel we get at the same upgrade needs to be running first [16:27] but the init is already calling when the file /var/lib/alsa/asound.state is not there [16:28] but I didn't check if this file is created even with the wrong configuration [16:28] that file is always there [16:28] just not on brandnew installs [16:28] it gets created on every shutdown [16:29] so the code you look at is for new installs [16:29] it doesnt help on upgrades [16:29] ok, it worked for me because at the first boot I just installed the new kernel and the patched alsa-utils that avoid calling alsactl init [16:29] then at the next boot everything was working fine [16:29] race condition [16:29] no [16:29] what about systems like mine when upgrade of kernel != reboot? [16:29] no race condition, expected behavior [16:30] hrw, then a script has to be in place taking care for that [16:30] I sometimes do few kernel updates before reboot [16:30] thats what i was talking about above [16:30] thats fine [16:30] the script will check for the right kernel running on boot [16:31] if it sees the right one, it will call alsactl init [16:31] and renove itself [16:31] *move [16:31] don't know if removing itself is the best choice [16:31] maybe creating some kind of stamp somewhere [16:31] so situation is: kernel has proper alsa setup, but users have wrong one so we need to grab kernel one before alsa will use inproper one? [16:31] rsalveti, that would mean you check for the stamp on every boot [16:32] ogra_ac: sure, something like what is already happening at [ -f /var/lib/alsa/asound.state ] || alsactl init [16:32] rsalveti, right, we shouldnt add another one [16:33] just because I don't like stuff being removed from my system without any package removal [16:33] better have a link somewhere that executes it and remove that link once it was run once [16:33] as i said, its just about implementation details atm, i discussed all that at UDS with the audio guys [16:33] hrw: users need to update the kernel and then call alsactl init to initialize the correct config [16:34] so to make the sound work you need to reboot anyway [16:34] right [16:34] the kernel has the name changes to the alsa devices we require [16:34] without the new names the alsa-utils changes cant work [16:34] thats the catch22 [16:35] no more "SDP4430 Media"? [16:35] rsalveti, persia's suggestion was a here document from postinst, so it wont be handled by any package at all, neither the putting in place nor the removal [16:35] ogra_ac: sorry If I already asked this question, but why alsactl init is not called on every boot anymore? [16:35] because thats resetting the mixers [16:36] rsalveti: what if you setup volume? [16:36] hrw, no, no more SDP4430 Media [16:36] ok, the restore should be called, not init [16:36] omap4 mixer is not small beast [16:37] and restore also calls init when it fails [16:37] rsalveti, right, thats the core bug [16:37] restore should call init but it doesnt with our sound driver [16:37] that will be investigated for natty [16:37] hm, ok [16:38] hrw, SDP4430 is used in more boards and all of them require different mixer setups so we added names pre board for the device [16:38] *per [16:38] that way tha alsa init scripts can adjust them on a per board base [16:39] ogra_ac: I remember that discussions [16:39] *Hopefully* UCM will handle this in the future. [16:39] hrw: http://paste.ubuntu.com/529441/ current result for panda [16:40] GrueMaster, it will, you really should have been at plumbers [16:40] rsalveti: which ver of kernel? [16:40] previously was just SDP4430 - SDP4430 for all boards [16:40] Yea, I figured as much. [16:40] * hrw needs to revert to natty on panda [16:40] hrw: 2.6.35-903-omap4 #17-Ubuntu [16:40] revert ? [16:40] latest one available at maverick [16:41] ogra_ac: yes. today was linaro 10.11 testing day which is maverick. yesterday it was running natty [16:41] ah [16:41] I do not have maverick on devices [16:42] * ogra_ac has only maverick on all systems here [16:42] but will reinstall smartbook to maverick to check kde4/armel status [16:48] * hrw reboots to #17 kernel [16:51] got panda [16:53] now installinf alsa-utils should get you working sound [16:54] I did 'alsactl init' by hand [16:54] that wont give you the right setup if you dont have the proper alsa-utils [16:55] ok [16:59] ogra_ac: who calls /sbin/alsa-utils start? [16:59] rsalveti, udev iirc [16:59] hm, ok [17:00] yeah, through an additionl script [17:00] from /lib/udev/rules.d/80-alsa.rules [17:00] yup, saw it here now [17:01] i have a skeleton for the postinst stuff, i'll finish that tomorrow during work hours [17:01] so it calls when it add controlC [17:01] right [17:01] ogra_ac: sure, np, I'm just trying to understand now why restore is not following init [17:01] i think its in alsactl itself [17:02] look at the source there [17:02] yeah, doing that right now [17:02] but generally init shouldnt be needed at all === zyga is now known as zyga-gone [17:02] the driver should properly init and will hopefully do in natty [17:03] sure [17:04] btw, what happened to the backtrace GrueMaster wanted to supply [17:04] don't know [17:04] would be intresting to see the offending function [17:04] but it's probably something that the compiler optimized for neon [17:04] as neon is used for everything [17:04] yeah [17:04] and not just neon capable files === hrw is now known as hrw|gone [17:23] hi all,how create cross toolchain for ARM from scratch on ubuntu 10 [17:24] aju: "apt-get install arm-linux-gnueabi-gcc" is not enough? [17:24] ;d [17:26] hrw|gone, want to know complete process for creating toolchain on ubuntu 10 [17:27] aju: apt-get source armel-cross-toolchain-base + build it + install results + apt-get source gcc-4.5-armel-cross + build it + install it + apt-get source gcc-4.4-armel-cross + build it + install it [17:27] * hrw|gone out [17:46] How do I replace the kernel in Ubuntu? I've built a 2.6.36 kernel and I want to install it. [17:47] Ubuntu 10.10 built from an image. [17:47] dpkg -i [17:47] RobotGuy, using dpkg -i [17:47] \pkg name [17:47] I am talking building the kernel from sources, not installing from a binary. [17:47] https://wiki.ubuntu.com/KernelTeam/GitKernelBuild === robbiew is now known as robbiew-lunch [17:51] I think you are not understanding my question.. I have configured and built a 2.6.36 kernel from sources. I want to install the new kernel and boot it. How do I do that? [17:51] RobotGuy, now you have .deb package of newly compiled binary? [17:52] i mean for kernel 2.6.36 ? [17:52] aju: NO I do not have a .deb package for the kernel. [17:52] RobotGuy, you should build a deb [17:52] if you know *ecxactly* wht your specific board needs for kernel and initrd treatment you can do that by hand indeed [17:53] but i would refer to the board documentation for that [17:53] As I said, I built a kernel from sources - 2.6.36 I want to install my new kernel and boot it. [17:54] RobotGuy, yes either you can create .deb using make-kpkg and then use chroot and install it in target board or using ssh [17:55] You are making this way over complicated. [17:55] RobotGuy, then look at your board docs what your board needs exactly [17:55] i.e. a u-boot booting board needs a uImage made from vmlinuz [17:56] I have already built a kernel for my hardware. Now I want to install it and boot it. What is so difficult here? [17:56] a redboot based board needs special treatment to dd the kernel into right place [17:56] RobotGuy: the ubuntu way would be to have a package for it [17:56] that you didnt tell us anything about your hardware yet [17:56] if you already built your own kernel you can just give make deb-pkg [17:56] the upstream kernel also has a way to build a deb from the sources [17:56] and it works quite well with ubuntu too [17:56] How is this going to help me install my new kernel? [17:57] what hardware do you have there ? [17:57] Hardware is a BeagleBoard-xM [17:57] it's easier because if you're installing it on a running board, the initrd will be generated when installing it [17:57] so you need to run the right mkimage command [17:57] and create a uImage [17:57] then put it in the right place [17:57] I already have a uImage [17:57] RobotGuy: if you just want to use a new uImage, just put it at the right place at the first partition [17:57] and make sure your modules are located at /lib/modules [17:57] generate a corresponding uInitrd and put that in place as well [17:58] rsalveti: That does not work. [17:58] then your mkimage parameters were likely worng [17:58] where/how does it stop ? [17:58] RobotGuy: it should work fine, if you put the modules in place and call depmod -a [17:59] a deb cares for all that [17:59] Is there a .deb package that matches a kernel 2.6.35.7-16, including config?? [17:59] RobotGuy: having the deb file is easier, you just need to install it [17:59] and then making sure you're booting with the new uImage and uInitrd [17:59] rsalveti: You do not understand. I need sources to match the running kernel for development purposes. [18:00] flash-kernel will care in this case [18:00] RobotGuy: so just use the new uImage, copy the modules to /lib/modules, update the modules cache with depmod and generate a new initrd [18:00] that should also work [18:01] rsalveti: I have already tried that and it does not work. [18:01] which emulator or IDE is available for ubuntu armel [18:01] qemu [18:01] RobotGuy: it should work fine, probably something when wrong [18:01] i mean i like test my app [18:01] RobotGuy, well, if you dont give us any more info we cant help [18:02] ogra_ac, for qemu need to boot complete os ? [18:02] what does happen exactly or what doesnt ? [18:02] or just application ? [18:02] aju, both [18:03] What more info do you need? [18:03] you can install qemu-arm-static and run qemu-debootstrap --arch armel to cerate an arm chroot [18:03] or you can use qemu-system, grab a versatile kernel and run a full VM [18:03] RobotGuy: did you give make modules_install INSTALL_MOD_PATH=/somewhere and then copied the modules to the correct directory? [18:04] rsalveti: That does not work. [18:04] then your mkimage parameters were likely worng [18:04] where/how does it stop ? [18:04] rsalveti: I know how to build kernels. I've been doing it for years. [18:05] RobotGuy: so please post the exact error you're getting [18:05] rsalveti: My problem does not have to do with building the kernel. There is no error to post. [18:06] RobotGuy: you say it didn't work for you, but didn't say what went wrong [18:07] First of all, I never said anything went wrong. Secondly, I came here asking how to do something, not how to correct an error. [18:08] RobotGuy: well, I gave you two working methods, and you said you don't want to use deb and the other one simply doesn't work for you, for some unknown reason [18:09] so I don't know how to help you more, unless you post us what went wrong with one of these options [18:09] rsalveti: I told everyone what I need to do at the start. Nobody has told me how to accomplish what I want to do. [18:10] RobotGuy: I told you 2 solutions, one is to build a deb and another is to produce a new uImage, install the modules by hand, generate the initrd and then reboot [18:10] as you asked how to replace ubuntu's kernel with your own sources [18:13] I asked how to replace Ubuntu's kernel with my own kernel that I built from sources. [18:14] This should not be rocket science. [18:15] and I gave you two working solutions for that [18:15] RobotGuy: Let's start over. Are you using our pre-installed image? Is that the kernel you wish to replace? Do you want to replace it before or after first boot? [18:16] I started out from here ---> http://elinux.org/BeagleBoardUbuntu [18:17] * GrueMaster looks. [18:18] I installed the Ubuntu image from there - 10.10 [18:18] Ok, that lists several images, both Ubuntu supported and some that someone created from ubuntu repos and posted as tarballs. It also lists different versions (Maverick, lucid). [18:18] I want to replace the kernel. [18:18] maverick [18:19] Please be more specific. We have a pre-installed image that https://wiki.ubuntu.com/ARM/OMAPMaverickInstall points to, and there is a tarball on the link you posted as well. [18:20] Two entirely different beasts. [18:22] The "Demo Image" is not built or supported by Ubuntu other than at the package level. The ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz that can be downloaded from http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/ is supported. [18:22] All I want to do is have sources matched to the kernel my beagleboard is running. I need this for development. [18:23] Either way, we need to know exactly which one because they are completely different and require different approaches to replace the kernel. [18:23] Which what?? [18:23] Which image. [18:23] I already gave the info on where I got the image. [18:24] http://elinux.org/BeagleBoardUbuntu [18:24] Maverick 10.10 [18:24] I am looking at that link. There is Maverick 10.10 preinstalled (linked through https://wiki.ubuntu.com/ARM/OMAPMaverickInstall), and below it is the Demo Image based on Maverick 10.10. [18:25] So again, which image are you using? [18:25] Demo Image, Maverick 10.10 [18:25] Ok. Thank you. Now we have a starting point. [18:27] Unfortunately, I have know knowledge of that image at this time, but I think rsalveti's point of building a kernel deb package and installing that is the best bet. [18:28] WHY do I want to build a kernel deb. That is an unnecessary complication to what I need to do. [18:28] If you already have a vmlinuz & initrd.img, then you can alternatively use mkimage to make a uImage and uInitrd to boot from. [18:29] i have a basic question why uImage , u boot image x loader need to copy in Fat partition why not in ext ? [18:29] I already have a uImage. I need to create the matching uInitrd. [18:29] If you scroll down the web link you posted, it has how to create a uInitrd from initrd.img. [18:30] My basic question remains though: How do I get the sources that match the kernel that is installed with the image I am using?? [18:31] By installing the deb packages created when building the binaries. Or copying the kernel source to /usr/src. [18:31] The whole reason I went to build my own kernel is that I could not get sources to match the kernel on the image. [18:31] RobotGuy, ask the person that created the image you used [18:31] you are obviously not using an ubuntu image [18:32] I'm using an image with ubuntu on it. [18:32] right [18:32] but not an image created by any ubuntu developer or in the ubuntu infrastructure [18:32] As I said, we can support it at the *package* level (i.e. if there is an ubuntu package in it that is having issues). [18:32] we can give you advise for ubuntu images [18:33] or for ubuntu packages [18:33] How do I know what images are or are not supported? [18:33] If the images come from *.ubuntu.com. [18:34] RobotGuy, GrueMaster just pointed you to some urls [18:34] (or authorized mirrors). [18:35] Our officially supported omap image for maverick is http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/release/ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz [18:36] Will that work on a BeagleBoard? [18:36] Installation instructions are at https://wiki.ubuntu.com/ARM/OMAPMaverickInstall [18:36] Yes. [18:36] Tested on Beagle C4 & Beagle XM. [18:36] OK, thanks. I guess I need to switch images then. I have a C3 and an xM. [18:37] It should also work fine on the C3. On the XM, be aware that there is a workaround for DVI on XM rev A3 or later. [18:37] My xM is an A2 [18:37] Then it should just work. [18:38] ogra_ac, i have a basic question why uImage , u boot image x loader need to copy in Fat partition why not in ext ? [18:38] A3 moved the DVI enable line to a gpio after 10.10 release. It has been fixed in a kernel update, but is tricky on first boot. [18:38] But as you have A2, no worries. [18:38] I'm glad. :D All this time I didn't know I was using an unsupported image of Ubuntu. [18:38] aju, thats a u-boot limitation we had with the omap u-boot [18:41] RobotGuy: No problem. There are a lot of images and even full distributions based on Ubuntu (i.e. Mint) packages. But we can only support the ones *we* create. [18:42] and indeed, instead of switching images you can just talk to the creator of the image you use [18:42] i.e. for a bug in mint you would talk to the mint devs [18:44] ogra_ac, can uboot read kernel from ext3 ? [18:44] ext2 [18:44] ok ext2 ? [18:44] but not all revisions [18:45] I don't know who created it apparently. I know you guys didn't make it now. [18:45] because as convention it is required to copy uboot xloader and kernel in fat [18:45] I'll just switch images. That seems to be the easist path. :) [18:45] will it work just copy uboot in fat and other in ext2? [18:45] something i want to test and run differently [18:46] you will have to rebuild u-boot with ext2 support [18:46] it rpovided to be unstable when we tested it [18:53] GrueMaster: I understand the whole support thing. ;D [19:00] I just created an sd card with that image but it says it doesn't have a valid partition table. [19:01] I forgot to gunzip it [19:01] you shouldnt gunzip [19:02] https://wiki.ubuntu.com/ARM/OMAPMaverickInstall has the proper instructions, use zcat [19:25] That ubuntu supported image just freezed my beagleboard up on kernel boot. [19:27] Do you see anything on the monitor? [19:56] Yeah. It appears there is a wait, reboot, wait cycle for this image to boot. [19:58] Ahhh, x-image and I don't have keyboard/mouse connected yet. [19:59] The first boot resizes the rootfs to fill the SD card. The second one should boot into X with oem-config running so that you can setup keyboard locale, timezone, and user login info. [19:59] It does. My misunderstanding. [19:59] I don't need X for the project I am working on though. [20:01] RobotGuy: you can boot with "text" at the cmd argument and you'll not get X [20:02] I would prefer to not have X on the SDcard at all. [20:03] I need dev stuff like gcc, etc. [20:03] dev libraries. [20:04] A console only dev image would be what I need/ [20:04] RobotGuy: The other thing you could do is build your own image with rootstock. [20:05] I may have to do that. [20:05] yep, unfortunately we don't have a minimal image for maverick [20:05] rootstock is the way to go [20:05] at least for natty we'll have it [20:05] That's too bad. [20:07] We lose the serial console. [20:08] At least if there were a minimal image, we could build up exactly what we need. [20:09] One other (untested) solution is to download the netboot image and use it to install from the pool. [20:09] RobotGuy, once you have my image it's easy to transition to ubuntu's kernel. ;) [20:10] rcn-ee_at_work: What image is that? [20:10] i was catching up on the irc log, 'my' image. ;) [20:11] Would that be the one I am using now? [20:11] Yeap it is.. from reading the backlog, you build a uImage and modules right? just dump the uImage in the fatfs and untar the modules to the rootfs.. the boot.. [20:12] after you build, there's a script under /boot/uboot/tools to rebuild the uInird, then reboot with all new.. [20:12] It can't find the linux partition [20:12] Yeah, I know the script. It doesn't do the right thing - uses the wrong kernel version. [20:13] it uses the 'kernel' version from "uname -m or -r" [20:13] so you need to boot with uImage for it to work.. [20:13] It always uses the version of the running kernel, which is wrong if I just created a new kernel. It needs to use the version of the new kernel. [20:13] I know that [20:13] yeah, so copy the 'new' uImage to the boot, then reboot with the new uImage... [20:14] You are not listening to me. [20:14] as long as your modules are populate to /lib/modules/new_image/ [20:14] I know how to deal with kernels, but what you are saying does not work. [20:14] Yeah i am.. So your running an old kernel.. You build a new one.. Take that new uImage and copy it to the fatfs dir.. then reboot your beagle, it'll run the new uImage.. [20:15] It does not find the rootfs partition. [20:15] I don't know why. [20:15] sounds like a config problem... can you pastebin your .config [20:24] ogra_ac: back to the alsa-utils issue [20:24] alsa-utils is calling alsactl restore with -I [20:25] -I,--no-init-fallback [20:25] it calls with no init fallback, gets the error, tries to sanify it and then calls restore again [20:26] rcn-ee_at_work: http://pastebin.com/87rjwxWm [20:26] Thanks RobotGuy [20:27] If it's the config, I don't know what the problem is. [20:31] most of the obvious things are right, but "CONFIG_GPIO_TWL4030=m" should be builtin, i belive it sets the power to mmc card... [20:31] diff'd mine and ubuntu's config we both got it as "=y" [20:32]