=== asac_ is now known as asac === robclark_ is now known as robclark === velory is now known as may_null [14:32] rsalveti: I'm getting "no such device" when I'm trying to modprobe the omaplfb.ko driver (from the SGX drivers). Are you familiar with this error? [14:57] sveinse: hm, no, never had this error [15:06] rsalveti: OK. I will investigate. I suspect some kernel setting as the board (&kernel) is new to me and I have not tested SGX on it yet. I'm using the Gumstix Overo Fire board now [15:06] hm, ok [15:07] there are some boards who uses TI's linux repo, while others are using the official linux repo [15:08] Not that I really have understood the relationship between them, i.e. why TI cant work on the official one instead [15:13] rsalveti: devmem2 is used solely for identification, not for setup/configuration, right? [15:13] sveinse: just identification [15:13] In the new driver, devmem2, isn't installed and isn't used from the rc.pvr init script [15:13] the pvrsrvinit is the one who initialize the sgx [15:14] Love your upstart adaptation BTW ;) [15:15] :-) [15:27] bö [16:19] In the package ffcall, configure hangs indefinitely on armel in Ubuntu, but works fine in Debian. The problematic check is http://paste.ubuntu.com/544914/. I was wondering if someone might have a suggestion as to what the problem is. === njpatel_ is now known as njpatel [16:41] rsalveti: I found all headers I needed inside the SGX driver now [16:41] sveinse: cool [16:41] I think they have started to do so with the 4.0 driver [16:42] You have to search though.. But in that world nothing is logical [16:42] haha, true [16:46] Can one preload a library in armel? === njpatel_ is now known as njpatel [17:31] rsalveti, hmm the board crashed, last thing in ssh tail -f /var/log/messages [17:31] Dec 17 15:32:58 gcc44 kernel: [41654.445434] ptrace of non-child pid 4443 was attempted by: gdb (pid 4446) [17:31] power cycling now [17:31] ouch [17:34] rsalveti, it's back online, if you want to see /var/log/messages [17:34] guerby: sure, thanks [17:34] guerby: did you have any serial access? [17:34] rsalveti, the board did not answer ping, the usually blinking LED near the SD card was not blinking, the network LED were on [17:34] sometimes we get just the kernel trace without any messages at the logs [17:35] ok, kernel probably crashed [17:35] rsalveti, I think I have a USB serial cable somewhere if you think it's useful [17:35] guerby: it's good to have it connected at uart for cases like this one [17:36] rsalveti, ok will try to get serial over the weekend [17:36] and I'll try to debug the mem issue this weekend too [17:36] many other issues around these days [17:37] rsalveti, :) [17:37] rsalveti, munin graph: http://gcc12.fsffrance.org/munin/fsffrance.org/gcc44.fsffrance.org.html [17:38] cool [17:39] rsalveti, bigger iron here :) http://gcc12.fsffrance.org/munin/fsffrance.org/gcc10.fsffrance.org-cpu.html [17:39] http://gcc12.fsffrance.org/munin/fsffrance.org/gcc10.fsffrance.org-memory.html [17:39] thanks AMD :) [17:39] wow :-) [17:40] rsalveti, no RAM issues :) [17:41] for sure! [22:20] hello [22:20] it's a good channel for linux on pda ?? [22:47] As long as the pda is armv7 capable, maybe.