**** BEGIN LOGGING AT Sun Mar 04 02:59:59 2012 Mar 04 03:43:12 hi I am trying to get stuff running on FriendlyARM Tiny 6410. My aim is to get a usb bluetooth dongle and usb wireless dongle running on it Mar 04 03:44:17 currently it il running the default version of linux that came with it, should I try and install ubuntu on it (if yes, how the guide asks me to run an exe, and I dont have Wndows) Mar 04 03:45:04 Will I have to hunt for drivers, can somebody help? Mar 04 17:01:40 Hello anyone here ? Mar 04 17:02:14 I ma having a problem installing Ubuntu on PandaBoard Mar 04 17:02:44 First time it boot it resizes partition, but then instead of start installer it keeps rebooting forever Mar 04 17:02:53 fwiw, tmax was having an issue w/ installer: http://pastebin.pandaboard.org/index.php/view/77105354 Mar 04 17:03:06 * robclark thought perhaps someone here would have a better idea what is going on Mar 04 17:06:09 robclark helped because i was getting through RS232 an error about kernel could not find uEnv.txt so i created it Mar 04 17:06:25 and put it inside: initrd_high=0xffffffff fdt_high=0xffffffff bootcmd=fatload mmc 0:1 0x80200000 uImage; fatload mmc 0:1 0x81600000 uInitrd; bootm 0x80200000 0x81600000 bootargs=console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait ro text earlyprintk fixrtc nocompcache loglevel=10 ip=dhcp uenvcmd=boot Mar 04 17:10:57 anyone ? Mar 04 17:16:53 hello ?? :/ Mar 04 17:27:58 that usually happens when something went wrong during the resize Mar 04 17:28:18 when regenerating the initramfs probably Mar 04 17:28:43 one thing you can do is to flash the image again, mount it at your host, edit the boot args and enable the console output Mar 04 17:28:47 if you have access to your serial Mar 04 17:29:00 then you'll get all the details about the installer and what is happening Mar 04 17:30:27 yeah i can see everything from my PC trough console Mar 04 17:30:44 i have reinstalled the image about 4 times Mar 04 17:31:14 ok i have reinstalled the image again in my SD card Mar 04 17:31:25 what should i change before put it into PandaBoard ? Mar 04 17:33:55 when i put the img inside SD card it doesnt create uEnv.txt is that normal ? Mar 04 17:34:12 I believe it's still using the boot.src file Mar 04 17:34:44 ok should i try booting again ? Mar 04 17:35:18 that's before the first boot (before resize) as it seems the resize not working properly for you Mar 04 17:35:27 or if you just want to understand why it's rebooting Mar 04 17:35:36 you can also change it to see what are the logs Mar 04 17:36:05 yes i want to understand too i want to learn :D Mar 04 17:36:17 but what i have to change ? Mar 04 17:36:24 adding console=ttyO2,115200, remove quite and replace splash with nosplash Mar 04 17:36:42 *quiet Mar 04 17:36:51 so i have to create uEnv.txt again ? Mar 04 17:37:16 dd if=boot.scr of=boot.script bs=1 skip=72 Mar 04 17:37:19 edit boot.script Mar 04 17:37:26 mkimage -A arm -T script -C none -n "Ubuntu boot script" -d boot.txt boot.scr Mar 04 17:37:32 if it's not yet using uEnv.txt Mar 04 17:38:11 yeah, still using boot.scr Mar 04 17:38:46 yeah it says it couldnt find uEnv.txt so it uses boot.scr Mar 04 17:39:15 mmm i dont have boot.script in FAT32 partition Mar 04 17:39:28 that's why you have to run the dd command first Mar 04 17:39:36 it'll remove the header and create the boot.script file Mar 04 17:39:56 so you can properly open it with any editor Mar 04 17:40:02 ok wait, so i have to put it in PandaBoard and let it resize first ? Mar 04 17:40:23 i apologise i am pretty new at this and i am lerning Mar 04 17:40:53 if you want the messages since first boot, no, you just need to add the sdcard at your host, mount first partition, generate the boot.script file, edit, and create a new boot.scr file again with mkimage Mar 04 17:41:42 ok i have mounted the first FAT32 partition on my PC Mar 04 17:41:59 now i have to create boot.script and what i have to put inside ? Mar 04 17:42:39 there will be a line similar as " setenv bootargs ro elevator=noop vram=32M mem=456M@0x80000000 mem=512M@0xA0000000 root=UUID=9d4de70e-1323-4ac9-9d3f-4ae05139f7ff fixrtc quiet splash" Mar 04 17:43:22 edit this line, removing quiet and splash, and add "console=ttyO2,115200 nosplash loglevel=8" Mar 04 17:43:30 then run mkimage as I said before Mar 04 17:43:41 mkimage -A arm -T script -C none -n "Ubuntu boot script" -d boot.sript boot.scr Mar 04 17:43:49 umount it and boot the card at your pandaboard Mar 04 17:49:02 i am getting this mkimage: Can't read boot.script: Invalid argument Mar 04 17:49:29 andres-nt@andres-nt:/tmp/mmc$ sudo mkimage -A arm -T script -C none -n "Ubuntu boot script" -d boot.script boot.scr Mar 04 17:49:33 thats what i put Mar 04 17:50:19 i have FAT32 mounted in /tmp/mmc Mar 04 17:52:17 and when i edit boot.scr gedit warns me about it can corrupt the file if i save it because there are strange caracters Mar 04 17:52:35 you first need to generate the boot.script file with dd Mar 04 17:52:40 when i save it the file becomes strange it is filled whit 0 Mar 04 17:52:45 run: dd if=boot.scr of=boot.script bs=1 skip=72 Mar 04 17:53:05 then you'll have the boot.script file to be edited and used by mkimage Mar 04 17:53:26 ok, but is normal what gedit tells me ? Mar 04 17:53:46 because i can see file is corrupted when i save it whit gedit Mar 04 17:54:06 yes, because you tried to edit the boot.scr file instead of boot.script Mar 04 17:54:15 the boot.scr file has a special header for u-boot Mar 04 17:54:37 that's why you need to run the dd command, that will just remove the header and create a text file called boot.script Mar 04 17:54:48 mkimage will then turn this file into a boot.scr, adding the header again Mar 04 17:54:53 to be valid by u-boot Mar 04 17:55:14 hooo and i have to edit the arguments from boot.script not boot.scr right ? Mar 04 17:55:21 yup Mar 04 17:55:34 hooo i am starting to understand :D Mar 04 17:56:54 ok now it worked :) Mar 04 17:57:18 now try booting Panda ? Mar 04 18:00:57 i have to have ethernet ?? it says waiting for ethernet connection Mar 04 18:02:21 http://pastebin.pandaboard.org/index.php/view/44520241 Mar 04 18:02:32 thats whatt i have it doesnt looks good :/ Mar 04 18:04:46 it says image is corrupt Mar 04 18:09:25 i reboot PandaBoard and now i get it Mar 04 18:09:28 http://pastebin.pandaboard.org/index.php/view/4026588 Mar 04 18:12:27 rsalveti ? Mar 04 18:13:53 are u there ? Mar 04 18:25:12 anyone ?? Mar 04 19:28:50 somebody online ? Mar 05 00:45:06 so, running into an... interesting issue with ubuntu-core, on an efika, i am installing, and really not doing much special, but, i'm doing it in a chroot, so i have the policy-rc.d file, but, upon reboot, once going through oem-config, when you login as the user created, it throws up 2 system errors, and it seems to be man-db and ubuntu-extras-keyring need to be re-installed. is there a way to do Mar 05 00:45:06 that before oem-config is run? Mar 05 02:43:31 steev_: I don't see how having a policy-rc.d in place would prevent man-db and ubuntu-extras-keyring from installing correctly. Mar 05 02:44:26 steev_: What are the actual errors? Mar 05 02:45:32 infinity: one sec, i'm about to reboot on a new install again Mar 05 02:50:47 infinity: ugh, for some reason it only happens *after* oem-config is run. and i'm trying to get all the different packages i want in order, before i set it to run oem-config. i'll do more research, but i definitely remember it complaining about man-db and ubuntu-extras-keyring, but when i told it to report the issue, it complained about some log being empty. Next time I will pay more attention Mar 05 02:50:47 (i haven't slept since friday night) Mar 05 02:51:38 Your man-db issue could just be that you need to manually run /etc/cron.daily/man-db (or wait for the cronjob to trigger later), but without seeing the error you're talking about, I don't know. Mar 05 02:52:05 If you mean that either of them is complaining about actually not being installed correctly period, that's a packaging bug, and not something you should be working around in installers. Mar 05 02:52:20 But, yeah. Seeing the errors would be helpful. Filing bugs, too. Mar 05 02:52:50 like i said, i hit the button to report issue, it complained about some log file being empty, next time i see it, i'll take a screenshot just to be safe Mar 05 02:53:13 for the moment though, i'm going to say this one is cooked, and prep it so i can mass install ;) **** ENDING LOGGING AT Mon Mar 05 02:59:58 2012