≡
[02:11:37] <isthatme> at boot
[10:31:23] <rds100> Hello
[10:31:26] <rds100> anyone from Olimex here?
[10:33:03] <tkoskine> Tsvetan looks to be offline, so probably not.
[10:33:30] <rds100> thanks :) will try to catch him up some other time then
[10:35:48] <rds100> gttodorov what about you, do you work for Olimex?
[10:41:27] <HeHoPMaJIeH> rds100: you can reach them by email
[10:41:54] <rds100> HeHoPMaJIeH i could also call them since i am also from Bulgaria, but i would like to chat with someone to discuss something first :)
[12:37:49] <olimexa13> Hi
[12:38:05] <olimexa13> I need help building a kernel image for the olinuxino a13
[12:38:27] <olimexa13> the command apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essentials git
[12:38:31] <olimexa13> doesn't work
[12:38:40] <olimexa13> it does'nt find the packet
[12:42:44] <rds100> which packet ?
[14:25:31] <remco_> Hi all
[14:26:39] <remco_> I'm using the A20-OLinuXino with success, but the only thing is that the file system gets currupted on powerloss
[14:27:02] <remco_> IS there a way to use the filesystem of the image as read-only, or something?
[14:28:50] <tkoskine> It is possible, but fully read-only filesystem requires quite lot of tweaking.
[14:30:03] <remco_> Maybe its better to recompile a read-only linux dist the the olimex kernel?
[14:30:16] <tkoskine> You get some ideas by looking how Raspberry Pi folks do it, for example http://thebeezspeaks.blogspot.fi/2013/10/hardening-your-raspberry-pi.html
[14:30:28] <tkoskine> Or http://raspberrypi.stackexchange.com/questions/5112/running-on-read-only-sd-card
[14:31:32] <remco_> But mounting as read-only on system boot wouldn't be too difficult? Why does it requires a lots of tweaking?
[14:31:45] <remco_> From the fstab
[14:33:24] <tkoskine> Depending on your distribution, various system daemons and other programs might expect that certain areas of your filesystems are writable.
[14:34:12] <tkoskine> And if they fail to write to the disk, they might stop working, and if some needed daemon stops working, then you have unusable system.
[14:34:18] <remco_> Ah, yes...
[14:34:20] <remco_> Hmz
[14:35:44] <remco_> Problem is that my board is the engine of a big robot which should run forever, but i cant use a filesystem that gets corrupted on every power loss :)
[15:18:50] <olimexa13> I'm folowing the manual from: http://olimex.wordpress.com/2014/01/15/building-debian-linux-bootable-sd-card-with-hardware-accelerated-video-decoding-and-kernel-3-4-for-a13-olinuxino/
[15:21:54] <olimexa13> and I get a error makefile:479 system not configured
[15:22:21] <olimexa13> when I wrote the command make A13-OLinuXino CROSS_COMPILE=arm-linux-gnueabihf-
[15:22:28] <olimexa13> What I'm doing wrong?
[15:44:16] <weigon> olimexa13: you missed the "make config " step?
[15:44:42] <olimexa13> I did that now
[15:46:20] <olimexa13> but it gave an error www.pastie.org/9070308
[15:46:55] <olimexa13> it says arm-linux-gnueabihf-gcc: not found
[15:47:04] <olimexa13> I'm on a 64 machine
[15:48:54] <olimexa13> maybe it is not in my PATH?
[15:49:26] <olimexa13> it says: /bin/sh: 1: arm-linux-gnueabihf-gcc: not found
[15:58:36] <olimexa13> weigon can you help me?
[16:16:32] <olimexa13> It's working now I had to do:
[16:17:11] <olimexa13> a symlink with ln
[16:17:31] <olimexa13> in case any of you have the same problem :)
[16:19:08] <weigon> olimexa13: did you isntall the arm-...gcc-4.7 package without the arm-...-gcc package?
[16:19:18] <weigon> usually the -gcc package provides those symlinks
[16:19:31] <weigon> at least on Ubuntu and I assume also debian
[16:19:56] <olimexa13> i installed this one:
[16:20:00] <olimexa13> apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git
[16:20:24] <olimexa13> it dones't provide the symlinks
[16:21:07] <olimexa13> I have one question
[16:22:09] <olimexa13> Do I need to download the .config file before doing make ARCH=arm menuconfig right?
[16:22:21] <olimexa13> I want a image with cdc drivers
[16:28:21] <weigon> olimexa13: the .config? or the defconfig?
[16:28:46] <olimexa13> sorry i mean the defconfig
[16:29:04] <weigon> yep, you use the defconfig to generate the .config
[16:29:38] <olimexa13> and then I do ARCH=arm menuconfig to customize the kernel right?
[16:34:23] <weigon> olimexa13: that's all documented in the page there
[17:01:24] <olimexa13> ok than you
[18:01:13] <remco_> Is it possible to redirect the kernel output to a different port when booting the image for the A20?
[18:01:49] <remco_> Maybe with recompiling
[18:05:06] <ccaione> remco_: console bootarg?
[18:05:47] <remco_> Is it called that way?
[18:06:42] <ccaione> what
[18:07:57] <remco_> What i need to look for when i want to redirect or disable the console output?
[18:09:15] <ccaione> assuming that your kernel has support for that, you can use the consol= bootarg to define where the kernel is going to output the boot printout
[18:10:08] <remco_> I dont know if it has. I'm using the standard one provided by the board
[18:13:44] <remco_> Can this be changed on a compiled image, or do i have to recompile the kernel with it's new value?
[23:53:01] <WarheadsSE> remco_: the standard kernel, or uboot
IRC #olimex 2014-04-10
[02:07:17] <isthatme> the default image for the LIME supplied at the wiki page should default to HDMI @ 720p60Hz right?[02:11:37] <isthatme> at boot
[10:31:23] <rds100> Hello
[10:31:26] <rds100> anyone from Olimex here?
[10:33:03] <tkoskine> Tsvetan looks to be offline, so probably not.
[10:33:30] <rds100> thanks :) will try to catch him up some other time then
[10:35:48] <rds100> gttodorov what about you, do you work for Olimex?
[10:41:27] <HeHoPMaJIeH> rds100: you can reach them by email
[10:41:54] <rds100> HeHoPMaJIeH i could also call them since i am also from Bulgaria, but i would like to chat with someone to discuss something first :)
[12:37:49] <olimexa13> Hi
[12:38:05] <olimexa13> I need help building a kernel image for the olinuxino a13
[12:38:27] <olimexa13> the command apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essentials git
[12:38:31] <olimexa13> doesn't work
[12:38:40] <olimexa13> it does'nt find the packet
[12:42:44] <rds100> which packet ?
[14:25:31] <remco_> Hi all
[14:26:39] <remco_> I'm using the A20-OLinuXino with success, but the only thing is that the file system gets currupted on powerloss
[14:27:02] <remco_> IS there a way to use the filesystem of the image as read-only, or something?
[14:28:50] <tkoskine> It is possible, but fully read-only filesystem requires quite lot of tweaking.
[14:30:03] <remco_> Maybe its better to recompile a read-only linux dist the the olimex kernel?
[14:30:16] <tkoskine> You get some ideas by looking how Raspberry Pi folks do it, for example http://thebeezspeaks.blogspot.fi/2013/10/hardening-your-raspberry-pi.html
[14:30:28] <tkoskine> Or http://raspberrypi.stackexchange.com/questions/5112/running-on-read-only-sd-card
[14:31:32] <remco_> But mounting as read-only on system boot wouldn't be too difficult? Why does it requires a lots of tweaking?
[14:31:45] <remco_> From the fstab
[14:33:24] <tkoskine> Depending on your distribution, various system daemons and other programs might expect that certain areas of your filesystems are writable.
[14:34:12] <tkoskine> And if they fail to write to the disk, they might stop working, and if some needed daemon stops working, then you have unusable system.
[14:34:18] <remco_> Ah, yes...
[14:34:20] <remco_> Hmz
[14:35:44] <remco_> Problem is that my board is the engine of a big robot which should run forever, but i cant use a filesystem that gets corrupted on every power loss :)
[15:18:50] <olimexa13> I'm folowing the manual from: http://olimex.wordpress.com/2014/01/15/building-debian-linux-bootable-sd-card-with-hardware-accelerated-video-decoding-and-kernel-3-4-for-a13-olinuxino/
[15:21:54] <olimexa13> and I get a error makefile:479 system not configured
[15:22:21] <olimexa13> when I wrote the command make A13-OLinuXino CROSS_COMPILE=arm-linux-gnueabihf-
[15:22:28] <olimexa13> What I'm doing wrong?
[15:44:16] <weigon> olimexa13: you missed the "make config " step?
[15:44:42] <olimexa13> I did that now
[15:46:20] <olimexa13> but it gave an error www.pastie.org/9070308
[15:46:55] <olimexa13> it says arm-linux-gnueabihf-gcc: not found
[15:47:04] <olimexa13> I'm on a 64 machine
[15:48:54] <olimexa13> maybe it is not in my PATH?
[15:49:26] <olimexa13> it says: /bin/sh: 1: arm-linux-gnueabihf-gcc: not found
[15:58:36] <olimexa13> weigon can you help me?
[16:16:32] <olimexa13> It's working now I had to do:
[16:17:11] <olimexa13> a symlink with ln
[16:17:31] <olimexa13> in case any of you have the same problem :)
[16:19:08] <weigon> olimexa13: did you isntall the arm-...gcc-4.7 package without the arm-...-gcc package?
[16:19:18] <weigon> usually the -gcc package provides those symlinks
[16:19:31] <weigon> at least on Ubuntu and I assume also debian
[16:19:56] <olimexa13> i installed this one:
[16:20:00] <olimexa13> apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git
[16:20:24] <olimexa13> it dones't provide the symlinks
[16:21:07] <olimexa13> I have one question
[16:22:09] <olimexa13> Do I need to download the .config file before doing make ARCH=arm menuconfig right?
[16:22:21] <olimexa13> I want a image with cdc drivers
[16:28:21] <weigon> olimexa13: the .config? or the defconfig?
[16:28:46] <olimexa13> sorry i mean the defconfig
[16:29:04] <weigon> yep, you use the defconfig to generate the .config
[16:29:38] <olimexa13> and then I do ARCH=arm menuconfig to customize the kernel right?
[16:34:23] <weigon> olimexa13: that's all documented in the page there
[17:01:24] <olimexa13> ok than you
[18:01:13] <remco_> Is it possible to redirect the kernel output to a different port when booting the image for the A20?
[18:01:49] <remco_> Maybe with recompiling
[18:05:06] <ccaione> remco_: console bootarg?
[18:05:47] <remco_> Is it called that way?
[18:06:42] <ccaione> what
[18:07:57] <remco_> What i need to look for when i want to redirect or disable the console output?
[18:09:15] <ccaione> assuming that your kernel has support for that, you can use the consol= bootarg to define where the kernel is going to output the boot printout
[18:10:08] <remco_> I dont know if it has. I'm using the standard one provided by the board
[18:13:44] <remco_> Can this be changed on a compiled image, or do i have to recompile the kernel with it's new value?
[23:53:01] <WarheadsSE> remco_: the standard kernel, or uboot
