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