[00:23] <bge0> Hello Everyone, I recently got a donate board from TI. It's the LogicPD OmapL138EVM board. Would anyone happen to know if this board supports ubuntu11arm?
[00:35] <GrueMaster> what processor is it?  Arm11?
[00:36] <GrueMaster> We only support Armv7 (Cortex A8 & Cortex A9).
[00:37] <An-iSociaL> howdy how GrueMaster
[00:37] <GrueMaster> An-iSociaL: Hey.  Get your kernel up?
[00:37] <twb> GrueMaster: internet says ARM926 core
[00:37] <An-iSociaL> negative :(
[00:38] <An-iSociaL> not down yet though, still trudging
[00:38] <GrueMaster> Aww, sad face.   Good luck.
[00:39] <GrueMaster> I'm EOD.  Time for Skyrim.
[00:39] <An-iSociaL> laters
[00:40] <bge0> I think OmapL138--> A8, i believe
[00:41] <bge0> Oh whoops it has an ARM926EJ-S + C6748 VLIW DSP
[00:42] <bge0> any chance of seeing ubuntu on this system? i miss aptitude :(
[00:42] <twb> bge0: debian armel then
[00:43] <bge0> ty! ill look into it
[00:43] <An-iSociaL> and howdy to you too twb, sorry i didnt see you there
[00:43] <twb> An-iSociaL: whatever
[00:43] <An-iSociaL> lol
[00:43] <An-iSociaL> hmph
[00:47] <An-iSociaL> whatre you upto?
[01:13] <bge0> twb: I'm looking up debian armtel, but there seems to only be support for iop32x, ixp4xx, kirkwood and orion5x
[01:15] <twb> http://wiki.debian.org/ArmEabiPort
[01:16] <twb> You're not going to get turnkey installation, but it certainly seems to support OMAP1/2/3 boards
[01:16] <bge0> yea I figured it wouldn't be quite that easy
[01:18] <twb> But if you aren't attached to the board I would suggest getting something armv7 flavoured, since everybody is switching to those
[01:20] <bge0> Well it's a pretty nice board though. i would feel bad scrapping it. It has a good onboard dsp too
[01:22] <twb> Shrug
[01:26] <bge0> Well, I guess I might just stick with the linux port that the board came with
[01:26] <bge0> ty though
[01:34] <lilstevie> An-iSociaL: that unable to open /dev/fb0 is indicating that the fb patch from the chromeos code review didn't take
[01:35] <An-iSociaL> aha
[01:37] <An-iSociaL> well im not ready to give in just yet
[01:39] <lilstevie> An-iSociaL: http://www.cactuar.net/uploads/Xoom_Debian/xoomkernel-gnu.patch over https://github.com/Tiamat%E2%80%93AOSP/Tiamat-Xoom
[01:40] <An-iSociaL> ah
[01:40] <An-iSociaL> ill have to manually patch that in
[01:41] <An-iSociaL> the AOSP tiamat is old
[01:41] <An-iSociaL> but im using his latest version
[01:41] <An-iSociaL> the only kernel i could get to ocmpile properly
[01:41] <An-iSociaL> compile*
[01:45] <An-iSociaL> right now i cant seem to generate another working initrd
[01:51] <An-iSociaL> :/
[01:51] <An-iSociaL> i keep ending up with the installer
[01:56] <An-iSociaL> there..
[01:57] <lilstevie> An-iSociaL: you want that installer "oem-config" so you can set up a user and shit
[01:59] <An-iSociaL> yea i got it, i think i was doing something ignorant by trying to use relative path for initrd output from mkinitramfs
[01:59] <An-iSociaL> did the initrd installer steps manually, format, extract, write fstab, touch oem-config so itll run
[02:00] <An-iSociaL> got a nice bootup, only kernel module to fail was btfrs with unknown symbol _global_offset_table_ which is caused by my cross compiler
[02:01] <An-iSociaL> video failed, as if im shocked, it flashed a couple times trying to switch but never did
[02:01] <An-iSociaL> so, on to the patch
[02:14] <An-iSociaL> did you already update this patch lilstevie ?
[02:25] <lilstevie> not my patch
[02:27] <int_ua> Sorry for interrupting but are there any team that works with Nokia N900? apachelogger, mpoirier, rbelem, someone else?
[02:54] <An-iSociaL> ok all patched up
[02:54] <An-iSociaL> booting
[02:56] <An-iSociaL> whatup! ubuntu is booted with xdesktop on my Motorola Xoom!
[02:57] <An-iSociaL> tyvm lilstevie
[02:59] <An-iSociaL> now next problem
[02:59] <An-iSociaL> there's no touch lol
[03:00] <int_ua> An-iSociaL: What is the touchscreen hardware?
[03:01] <An-iSociaL> err, i actually dont know
[03:01] <int_ua> Can you execute lsusb? :)
[03:03] <An-iSociaL> i would love to
[03:03] <An-iSociaL> but
[03:03] <An-iSociaL> no keyboard
[03:03] <An-iSociaL> lol
[03:03] <An-iSociaL> let me get adbd installed onto it, then i can use a usb terminal
[03:03] <An-iSociaL> the only touchscreen enabled in a default config is CONFIG_TOUCHSCREEN_QUANTUM_OBP
[03:04] <An-iSociaL> one sec on the lsusb
[03:07] <An-iSociaL> http://pastebin.com/iRgkqPnF
[03:07] <An-iSociaL> if youre the nerdy type like me, theres my dmesg log
[03:09] <int_ua> Offtopic: Why 2.6.36? (I just started reading IRC)
[03:12] <lilstevie> An-iSociaL: ok, now that patch had my touchscreen patch
[03:12] <An-iSociaL> its just what was available
[03:12] <lilstevie> int_ua: because thats what exists
[03:12] <An-iSociaL> hm lilstevie...
[03:12] <An-iSociaL> i did all the sections, and reverted one change cuz it broke something
[03:12] <lilstevie> which one?
[03:12] <An-iSociaL> so, it should work then
[03:13] <An-iSociaL> the one you linked
[03:13] <An-iSociaL> http://www.cactuar.net/uploads/Xoom_Debian/xoomkernel-gnu.patch
[03:13] <lilstevie> yeah, which change did you revert
[03:13] <int_ua> lilstevie: I asked because the only kernel I can boot on N900 is 2.6.35. And I don't know the reason yet.
[03:13] <An-iSociaL> just a define in fb_tegra which was being used by dc.c
[03:13] <lilstevie> also, YMMV with the touch patch
[03:14] <lilstevie> revert it
[03:14] <An-iSociaL> mmk lemme figure out where that is in here...
[03:14] <lilstevie> ubuntu from natty on, includes handling in evdev for what my patch does, that patch was done because debian doesn't have the same evdev handling
[03:15] <lilstevie> although it should just be ignored
[03:15] <An-iSociaL> touchscreen/qtouch_obp_ts.c
[03:15] <An-iSociaL> ?
[03:15] <lilstevie> yep
[03:15] <An-iSociaL> ok and away i go
[03:17] <lilstevie> bbs
[03:17] <lilstevie> lunch
[03:17] <An-iSociaL> k ttyiab
[03:18] <An-iSociaL> unpatched, compiled, flashed and now we're booting
[03:20] <An-iSociaL> ugh
[03:21] <An-iSociaL> still no touch and adbd didnt start
[03:21] <An-iSociaL> lets try this again
[03:24] <An-iSociaL> attempted fix on adbd
[03:24] <An-iSociaL> and im gonna have a smoke
[03:27] <An-iSociaL> i have touch...
[03:27] <An-iSociaL> its just... not quite right
[03:29] <An-iSociaL> and adbd didnt start again :/
[03:29] <An-iSociaL> is there another way to get a shell over usb?
[03:37] <An-iSociaL> ok the touch device doesnt seem to register clicks
[03:37] <An-iSociaL> it thinks theyre mouseovers
[03:38] <An-iSociaL> and still no adbd
[03:38] <An-iSociaL> this is going to be difficult
[03:40] <lilstevie> ok, let me eat
[03:40] <lilstevie> I will gen a patch of it
[03:40] <An-iSociaL> oh cool
[03:41] <An-iSociaL> dont choke cuz you think im waiting tho.. enjoy it
[03:41] <An-iSociaL> ive been working on this for a solid week and this is the furthest ive been able to get
[03:42] <lilstevie> heh
[03:42] <lilstevie> ask twb I don't rush for anyone
[03:42] <An-iSociaL> lol cool
[03:42] <lilstevie> btw twb known bug exists on 32GB tfs with u-boot
[03:43] <twb> sad face
[03:43] <lilstevie> twb: for some reason it will only rawread, and not read the partition
[03:43] <twb> I haven't tried your latest .38 with asus bl yet either, because all these 360 games came out last week
[03:43] <lilstevie> even though it can locate it
[03:44] <lilstevie> hah
[03:44] <lilstevie> I want a 360 so i can play fable3
[03:44] <lilstevie> and new games
[03:45] <lilstevie> cause my ps3 is 3.55-MFW
[03:45] <twb> I have a 360 because 1) I've given up on the games industry getting FOSSilized anytime this decade; and 2) it's turn-key.  I don't need to give a shit about h/w drivers or windows licensing or so on
[03:46] <lilstevie> lol
[03:46] <lilstevie> I also want to get a slim, and glitch attack it
[03:46] <lilstevie> linux + games on the 360
[03:46] <twb> if slim is the new black ones, they have really noisy PSU fans
[03:47] <An-iSociaL> indeed twb, you can just turn it on and play, no thinking about shit
[03:47] <An-iSociaL> i enjoy systems like that
[03:47] <lilstevie> twb: and the old ones were really loud with the exhaust fans
[03:47] <twb> I would like to play online but then I have to give MS money, and the menus inside teh 360 become much more annoying
[03:47] <twb> lilstevie: it's a fan inside the power brick
[03:47] <twb> lilstevie: smaller than the one inside the main case on the white units, i.e. noisier
[03:48] <twb> lilstevie: I have both units
[03:48] <lilstevie> heh
[03:48] <lilstevie> I don't really care
[03:48] <twb> I guess if you have the volume of the game up it's not noticable
[03:49] <twb> I usually mute it and read a book via synthesizer
[03:49] <twb> I would be a lot happier with steam, I think, if ICBF dealing with the non-turn-key-ness
[03:51] <lilstevie> lol
[03:53] <twb> Having to shuffle CDs is a pain, and I don't enjoy dealing with the monkeys at the game store
[03:57] <An-iSociaL> wow finally
[03:57] <An-iSociaL> http://pastebin.com/CuwfZqxW
[03:57] <An-iSociaL> lsusb
[03:57] <An-iSociaL> very short list
[03:58] <An-iSociaL> i somehow am pretty sure thats wrong
[03:58] <An-iSociaL> asin incorrect, not misreported
[04:00] <int_ua> hm
[04:00] <int_ua> corresponds with dmesg. So it must be connected somewhere else. lspci? lshw?
[04:01] <An-iSociaL> lemme run those out
[04:01] <An-iSociaL> im cheating and putting in startup scripts since i cant type lol
[04:02] <lilstevie> yeah, they don't connect via usb
[04:04] <An-iSociaL> if i dont get something workable tonight ill go buy a usb adapter tomorrow so i can plugin a keyboard+mouse
[04:04] <An-iSociaL> just for testing
[04:16] <An-iSociaL> lspci is empty
[04:16] <lilstevie> ofc
[04:16] <An-iSociaL> heres a neat empty lshw
[04:16] <lilstevie> nothing connects via pci
[04:16] <An-iSociaL> near*
[04:17] <An-iSociaL> http://pastebin.com/qJxwEgNf
[04:17] <lilstevie> yeah, arm connectivity doesn't really show up
[04:17] <An-iSociaL> seems like nearly nothing is working
[04:17] <An-iSociaL> ah
[04:17] <An-iSociaL> mmk
[04:17] <lilstevie> most things connect via i2c and i2s
[04:20] <An-iSociaL> ive got alot of work ahead of me here
[04:20] <An-iSociaL> milestone 1 has passed
[04:20] <lilstevie> heh
[04:20] <lilstevie> it doesn't go any quicker either
[04:21] <lilstevie> I have been working on the tf101 for months
[04:23] <An-iSociaL> hehehe
[04:23] <An-iSociaL> well anything gained too easily we esteem too lightly
[04:23] <An-iSociaL> or somethin like that
[04:26] <An-iSociaL> once i get this done my next goal is adual kernel
[04:28] <An-iSociaL> do a pendrive type linux, put it on my evo, run it side by side with android and use the hdmi out for a full desktop
[04:28] <An-iSociaL> then use a bluetooth keyboard n mouse
[04:28] <An-iSociaL> tiny pc
[04:30] <lilstevie> heh good luck with the hdmi part
[04:31] <An-iSociaL> shouldnt be so difficult, the hdmi under normal linux just shows up as fb1
[04:31] <An-iSociaL> normal android*
[04:31] <An-iSociaL> there's just no virtual terminal devices to hook into
[04:36] <lilstevie> yeah, you would think so
[04:36] <lilstevie> but at least on my tegra device, it doesn;t really work
[04:36] <lilstevie> doesn't*
[04:38] <An-iSociaL> hehe
[04:38] <An-iSociaL> well its gonna be awhile off before i embark on that
[04:38] <An-iSociaL> right now im aiming at full ubuntu
[04:38] <An-iSociaL> then xbmc media center
[04:42] <lilstevie> you will need accel for that
[04:42] <lilstevie> and that isn't going to happen with the kernel you are running
[04:42] <An-iSociaL> yea need to get the nvidia tegra drivers to function
[04:43] <An-iSociaL> likely try out the android 4.0 kernel for the xbmc build
[04:43] <An-iSociaL> it should be much more updated
[04:45] <lilstevie> still may not help
[04:45] <lilstevie> the android driver interface is different to the L4T interface
[04:47] <An-iSociaL> hmm
[04:47] <An-iSociaL> only problem is the damn stingray stuff
[04:47] <An-iSociaL> as i recall when i was on kernel.org, they have ventana in 3.0
[04:48] <lilstevie> that doesn't mean anything really
[04:48] <An-iSociaL> itll help alot
[04:48] <lilstevie> nearly every device has a different pinmux
[05:00] <An-iSociaL> hmm
[05:00] <An-iSociaL> i think its crashing
[05:11] <An-iSociaL> yes! i have adb shell!
[05:11] <An-iSociaL> now i can do somehting
[05:12] <lilstevie> heh
[05:24] <An-iSociaL> so uhm, hows that lunch there?
[05:26] <lilstevie> eaten
[05:26] <lilstevie> got a link to the kernel you use
[05:26] <lilstevie> like its git
[05:26] <An-iSociaL> http://code.tiamat-dev.com/tegra2/tiamat-xoom/commits/tiamat
[05:27] <An-iSociaL> git://code.tiamat-dev.com/tegra2/tiamat-xoom.git
[05:27] <An-iSociaL> thats the one i cloned
[05:34] <lilstevie> yeah looking at the touch driver now
[05:35] <lilstevie> patch out input_set_capability(ts->input_dev, EV_KEY, BTN_2); and                 input_set_abs_params(ts->input_dev, ABS_HAT0X,
[05:36] <lilstevie> and any other HAT*
[05:36] <lilstevie> which is                 input_set_abs_params(ts->input_dev, ABS_HAT0Y,
[05:36] <An-iSociaL> mmk
[05:36] <lilstevie> and that should do it
[05:39] <An-iSociaL> sweet
[05:39] <An-iSociaL> thanks
[05:39] <An-iSociaL> we'll know in a couple mins
[05:41] <lilstevie> fingers crossed
[05:47] <An-iSociaL> and we're booting...
[05:48] <An-iSociaL> switched cross compilers too, the newer one was playing tricks with my kernel modules
[05:48] <An-iSociaL> thats a fail
[05:48] <lilstevie> heh yeah
[05:48] <lilstevie> awh damn
[05:48] <lilstevie> ok, have your brought up wifi yet?
[05:48] <An-iSociaL> cant get it to come up
[05:49] <An-iSociaL> unable to mount rootfs on unknown block
[05:49] <lilstevie> ok, insmod <name of wifi mod> firmware_path=/path/to/firmware.bin nvram_path=/path/to/nvram.txt iface_name=wlan0
[05:49] <An-iSociaL> wth
[05:49] <lilstevie> and use wpa_supplicant
[05:49] <An-iSociaL> kernel panic
[05:57] <lilstevie> ok, well you have adb
[05:57] <lilstevie> so you can transfer a file
[05:57] <lilstevie> find the evtest deb
[05:57] <An-iSociaL> just got the wireless module loaded...
[05:58] <An-iSociaL> its not coming up anyway
[05:58] <lilstevie> yeah, you need to use wpa_supplicant
[05:58] <An-iSociaL> https://launchpad.net/ubuntu/oneiric/armel/evtest
[05:58] <An-iSociaL> that?
[05:58] <lilstevie> yep
[05:59] <lilstevie> figure out which input event is the touchscreen
[05:59] <lilstevie> (it will be in the dmesg and the Xorg log
[05:59] <lilstevie> )
[06:00] <An-iSociaL> ok cool
[06:01] <An-iSociaL> im goping nuts over here, this thing isnt really setup all that well
[06:01] <An-iSociaL> going*
[06:01] <An-iSociaL> can i paste here?
[06:01] <An-iSociaL> like 2 long lines
[06:02] <lilstevie> k
[06:02] <An-iSociaL> dpkg: error: parsing file '/var/lib/dpkg/available' near line 3214 package 'language-pack-es':
[06:02] <An-iSociaL>  `Pre-Depends' field, invalid package name `d`kg': character ``' not allowed (only letters, digits and characters `-+._')
[06:02] <An-iSociaL> its jacked
[06:02] <lilstevie> hm
[06:02] <lilstevie> odd
[06:02] <lilstevie> you can always manually extract anyway
[06:03] <lilstevie> it is an ar archive
[06:06] <An-iSociaL> Event: time 172.655713, type 1 (Key), code 330 (Touch), value 0
[06:06] <An-iSociaL> thats me picking my finger up
[06:06] <lilstevie> ok touch the screen a few times
[06:07] <lilstevie> move it around a little
[06:07] <lilstevie> do a two finger touch
[06:07] <lilstevie> then pastie the result
[06:08] <An-iSociaL> http://pastebin.com/6236hXgC
[06:09] <lilstevie> hmm
[06:09] <lilstevie> the X/Y seem out of bounds
[06:09] <lilstevie> one finger center of screen on then off
[06:11] <An-iSociaL> http://pastebin.com/9tx9b2BZ
[06:11] <An-iSociaL> bout as close as i can guess
[06:14] <lilstevie> you still have btn_2 and the hat stuff in the driver
[06:15] <An-iSociaL> its there, just commented
[06:15] <lilstevie> it isn't :)
[06:15] <An-iSociaL> not in what im using atm
[06:15] <lilstevie> if the set_abs_params and set_bit was out it wouldn't show up
[06:15] <An-iSociaL> the compile from the changes somehow caused a kernel panic
[06:16] <An-iSociaL> so i reflashed an older kernel image
[06:16] <An-iSociaL> maybe something went sideways, lemme try again
[06:18] <lilstevie> with set_bit for those parts evdev generally tries to treat the tsp as a touchpad
[06:19] <An-iSociaL> attempting to boot
[06:20] <An-iSociaL> panic
[06:20] <lilstevie> try going back to that other toolchain
[06:20] <An-iSociaL> k
[06:20] <lilstevie> it may be the change in toolchain that screwed it
[06:21] <An-iSociaL> recompiling
[06:22] <An-iSociaL> hey i really appreciate the help
[06:23] <lilstevie> np, I don't mind
[06:24] <An-iSociaL> rebooting
[06:25] <An-iSociaL> and panic
[06:25] <An-iSociaL> thats so weird
[06:25] <lilstevie> hm
[06:26] <An-iSociaL> let me try something else
[06:26] <lilstevie> I helped liv2 with debian too :p
[06:26] <An-iSociaL> aha
[06:26] <An-iSociaL> mr smart guy
[06:27] <An-iSociaL> i still dont know how he did it
[06:27] <An-iSociaL> my xoom no matter what kernel panics if i try to boot from normal boot partition
[06:28] <An-iSociaL> if i try to use the sdcard
[06:28] <An-iSociaL> i have to go through recovery to get access to it
[06:29] <An-iSociaL> im trying your changes with a modded config, compiling it now, gonna take a bit longer as a lot more things are enabled
[06:29] <lilstevie> yeah he had to go through recoveery too
[06:29] <lilstevie> kk
[06:29] <An-iSociaL> ah, see now in every tutorial i found recovery was never mentioned
[06:30] <An-iSociaL> it was like ooh magic it works
[06:31] <lilstevie> heh
[06:34] <An-iSociaL> building new initrd
[06:34] <lilstevie> hehk
[06:36] <An-iSociaL> and we're booting again
[06:37] <lilstevie> cool
[06:37] <lilstevie> with the patch?
[06:37] <An-iSociaL> aha no panic
[06:37] <An-iSociaL> need to stick with this config...
[06:37] <An-iSociaL> yep w/patch
[06:37] <lilstevie> ok cool
[06:38] <An-iSociaL> im gonna need to put this somewhere
[06:38] <An-iSociaL> like for people to use
[06:38] <lilstevie> heh
[06:38] <lilstevie> git it
[06:39] <lilstevie> now how is the touch going, or no x yet
[06:39] <An-iSociaL> sounds like a plan, i would like to host a kernel binary too for people like me who go nuts
[06:39] <lilstevie> yeah
[06:39] <An-iSociaL> ok i just tried to click continue
[06:39] <lilstevie> well thats what I do
[06:39] <An-iSociaL> it registered a down but not an up
[06:39] <lilstevie> http://forum.xda-developers.com/showthread.php?t=1191141
[06:40] <An-iSociaL> ah youre a member too :)
[06:42] <An-iSociaL> nice work
[06:45] <An-iSociaL> ugh i lost adb
[06:46] <lilstevie> hm, don't know how you lost adb
[06:46] <lilstevie> for me it is something I just cannot kill
[06:48] <An-iSociaL> its hacked in...
[06:48] <An-iSociaL> comes up n says cannot bind tcp:5037
[06:49] <An-iSociaL> hmm
[06:49] <An-iSociaL> and you dont have qtouch in your kernel tree
[06:49] <An-iSociaL> must be specific
[06:49] <lilstevie> no, I have a different panel
[06:49] <lilstevie> my devices have atmel mxt touch panels
[06:50] <lilstevie> and there isn't a "universal arm tree" so to speak
[06:51] <An-iSociaL> hm
[06:51] <An-iSociaL> https://github.com/LIV2/LIV2-Xoom-GNU/blob/tiamat_stock_gpu/drivers/input/touchscreen/qtouch_obp_ts.c
[06:51] <An-iSociaL> liv2's kernel still has those HAT0X/Y
[06:52] <An-iSociaL> wonder if he did any fixes to his
[06:52] <lilstevie> no I left them behind
[06:53] <lilstevie> main thing is getting rid of btn2
[06:53] <lilstevie> but I see no point in keeping hat0x/y
[06:54] <An-iSociaL> yea neither do it, its made no difference
[06:55] <An-iSociaL> could this be as simple as a config in ubunbtu itself/
[06:55] <An-iSociaL> ?
[06:55] <lilstevie> nah it really shouldn't make a difference at this point
[06:55] <An-iSociaL> mmk
[06:56] <lilstevie> everything left are valid touch coords
[06:56] <lilstevie> and evdev ignores those that it doesn't use
[06:56] <lilstevie> actually can you evtest again
[06:57] <An-iSociaL> no adb
[06:57] <lilstevie> bleh
[06:57] <An-iSociaL> yea, quite the pickle
[06:58] <An-iSociaL> can i put adbd into the initrd?
[06:58] <lilstevie> possibly, not tested it myself
[06:58] <lilstevie> and really, that shouldn't affect anything
[06:58] <An-iSociaL> must be a usb thing then
[07:03] <lilstevie> probably
[07:11] <An-iSociaL> alright, well im stumped and rather tired
[07:11] <An-iSociaL> so im going to take a break for tonight
[07:16] <lilstevie> k
[08:15] <punxos> Hi
[09:44] <S0NiC> hi
[09:48] <S0NiC> can anyone give me a good howto to crosscompile for arm7 technology? thanks in advance
[09:55] <brendand> guys, whenever i finish the oem-config for the 11.10 desktop image on the pandaboard i briefly see lightdm and then the screen flickers and switches off
[09:55] <brendand> anyone seen this
[09:55] <brendand> ?
[09:55] <brendand> i've tried a few times
[09:56] <ogra_> not here
[09:56] <ogra_> what kind of panda is that ? 4430 or 4460 ?
[09:56] <ogra_> i know the 4460 still hat temperature issues with the 11.10 kernel
[09:57] <brendand> well, it's Rev A1 if that says anything
[09:59] <ruudt> thats 4430 says google
[09:59] <ogra_> well, that should definitely work
[10:03] <brendand> maybe it's my damn monitor
[10:03] <ruudt> what would be the easiest way to develop programs for a minimal ubuntu installation? Given that I need internet and show images
[10:03] <ogra_> got the chance to try another ?
[10:03] <brendand> ogra - i can try my TV :)
[10:03] <ogra_> yeah, do that
[10:04] <ruudt> brendand: what happens if you wait a few minutes? Just to rule out temperature issues?
[10:04] <ogra_> might be an issue in the EDID parsing
[10:04] <ogra_> ruudt, the 4430 shouldnt have any temp issues
[10:04] <ogra_> for the 4460 i know it for sure that we have them though
[10:04] <ruudt> ow ok, sorry, I was guessing
[10:05] <ruudt> has any of you any programming experience for linux?
[10:05] <ogra_> ruudt, we have the ubuntu-core images that you can use as a base for rolling specific minimal rootfses
[10:05] <ruudt> I mean, I just installed quickly, but it is not really what I need
[10:06] <ruudt> orgra_ I have an installation. But need to build a custom app
[10:06] <ogra_> ah
[10:06] <ogra_> well, quickly would be a good start if you actually want gtk and python apps
[10:06] <ruudt> getting a working installation took several days of trying though :(
[10:06] <ogra_> not sure where it stands with things like C
[10:06] <ogra_> ouch
[10:06] <ogra_> what board is that ?
[10:06] <ogra_> something we support ?
[10:07] <ruudt> beagleboard xm rev c
[10:07] <ogra_> ah, yeah, revC is a constant headdache
[10:07] <ruudt> damn, is it that bad?
[10:07] <ogra_> will hopefully be better in 12.04
[10:08] <ruudt> won't help me now
[10:08] <ogra_> well, we didnt have one in the team to test on it until very recently before release
[10:08] <ogra_> and it came out after kernel freeze and feature freeze
[10:08] <ruudt> Can I, with quickly then also develop programs that don't rely on X to display the images?
[10:08] <ogra_> you might, i have never used quickly to be honest
[10:09] <ruudt> What do you use?
[10:09] <ogra_> shell, C, whatever else suits the usecase
[10:09] <brendand> ogra - yeah, TV works perfectly
[10:09] <brendand> bl**dy pos samsung monitor :/
[10:09] <ogra_> (for quick GUI apps i usually take python/gtk and later re-implem,ent in C/gtk)
[10:10] <ogra_> brendand, yeah, blame the monitor ...
[10:10] <brendand> although - TV doesn't have DVI so it was a HDMI -> HDMI connection
[10:10] <brendand> whereas monitor doesn't have HDMI so it's HDMI -> DVI
[10:10] <brendand> so it might be that and not EDID
[10:10] <ogra_> that shouldnt make it break though
[10:11] <brendand> well, i don't know. also the v-alignment is off on the monitor
[10:11] <brendand> there is about 4 inches on the LHS with just static in it
[10:11] <ogra_> did you try the auto adjustment of the monitor ?
[10:11] <brendand> but not on the TV
[10:11] <brendand> ogra - yeah
[10:11] <ogra_> also look if there is an overscan setting in the menu
[10:12] <ogra_> and switch that off
[10:12] <ogra_> though that shouldnt lead to no pic at all
[10:12] <ogra_> only to a cut off pic
[10:14] <brendand> no overscan setting i can see
[10:14] <brendand> i'll just have to commandeer the telly for now
[10:15] <ogra_> well, you could wait for robclark to get up, he might know the monitor models that still have EDID issues
[10:15] <ogra_> (i thought they were solved, but apparently they arent)
[10:15] <brendand> ogra_ - i'm pretty sure i had EDID issues with this one before
[10:15] <ogra_> how about using hdmi on the monitor
[10:15] <brendand> doesn't have it
[10:17] <infinity> brendand: When you were connecting to the DVI monitor, did you use the other HDMI port? (The one marked hdmi-dvi)
[10:17] <infinity> Or DVI-D, on some boards.  Whatever.  The one on the right. :P
[10:19] <brendand> infinity - ah. i'm using the one that worked for me before. the one on the left
[10:20] <infinity> brendand: The one on the left is HDMI, the one on the right is HDMI-DVI.  In theory.  I don't use the one on the right, cause everything here is straight HDMI.
[10:21] <brendand> infinity - well. i no longer have a problem
[10:21] <brendand> that works perfectly
[10:21] <ogra_> hah
[10:22] <ruudt> so to sum up, you must use the right one if you connect to a dvi monitor
[10:22] <brendand> pebkac
[10:22] <ogra_> the one that is labeled DVI, yes :)
[10:22] <brendand> ruudt - since oneiric, yes
[10:22] <infinity> ogra_: Pfft, like anyone reads silscreening (except me, apparently).
[10:23] <ogra_> heh
[10:23] <infinity> s/sil/silk/
[10:23] <brendand> in fact i never even looked at the labels
[10:23] <brendand> just used the one that worked
[10:23] <ruudt> When infinity asked which connector I was looking that up, because on beagleboard you'd best connect to dvi as well :P
[10:24] <brendand> yeah, my beagleboard just has a DVI-D connector
[10:24] <ruudt> But I'm still learning about everything here. My next hurdle; which development environemnt to use. But despite the advices I have not yet found one
[10:25] <ogra_> didnt you say you wanted to do web development ?
[10:26] <ruudt> ogra_: nope, but I do need to access the internet
[10:26] <ogra_> ah, i thought you wanted to serve images through the net
[10:27] <ruudt> Yes, but that is not web development? To me that is anything that runs from a server and is accessed by clients
[10:28] <ruudt> I already did the web development part; I have a server ready that will supply all data my application will need
[10:29] <ruudt> Did that while waiting for the BB to ship
[10:32] <ruudt> Hmm, the minimal install that I got running doesn't even have man...
[10:33] <infinity> apt-get install man-db manpages
[10:33] <ogra_> and watch your system get slow on upgrades :P
[10:33] <infinity> And manpages-dev, if you're doing C programming.
[10:34] <ruudt> well, at least I can read up on the things that ARE installed.
[10:35] <infinity> http://manpages.ubuntu.com/ also works, if you prefer not to grind dpkg runs to a halt with man-db triggers. :P
[10:36] <ogra_> ++
[10:37] <infinity> (But I'm with you, all my machines have man-db installed... Not being able to use man confuses me)
[10:41] <ruudt> well, I'll just continue installing man-db and then figuring out what to develop the programs with. Just wish it where more clear what to use...
[10:58] <S0NiC> re
[11:08] <brendand> i guess it's well known that suspending a pandaboard doesn't really compute?
[12:23] <desrt> hi all
[12:23] <desrt> it's early in the morning and i haven't had my coffee yet, so please excuse what may be a very stupid question
[12:24] <desrt> the kernel package that comes on the i.mx53 install image is called linux-linaro-lt-mx5
[12:24] <desrt> but that package doesn't appear to be in the archive
[12:25] <desrt> it's not like i strictly need a kernel since boot is handled slightly specially here anyway, but i'd like to have some modules (installed properly) at least
[12:30] <ogra_> it is in universe
[12:30] <desrt> see?  no coffee.
[12:30] <desrt> ogra_: thanks :)
[12:30] <ogra_> yw :)
[12:31]  * desrt blames debootstrap for that
[12:32] <ogra_> it is one of the "community supported" images
[12:32] <ogra_> like the ac100 one
[12:32] <desrt> seems to be working quite nicely, fwiw
[12:32] <desrt> the userspace on the image leaves me a bit confused though
[12:32] <ogra_> well, the installation is quite slow
[12:32] <desrt> it appears to have an installer that installs to itself, or something
[12:32] <desrt> and then leaves the system in a somewhat broken state after
[12:33] <ogra_> that would be a bug
[12:33] <desrt> ogra_: it's the microsd that's slow.  i just plugged in an intel sata drive and it's about 5-10x faster now
[12:33] <ogra_> it is a preinstalled image, on first boot it expands the rootfs partition to the full size of the SD
[12:33] <desrt> ah
[12:33] <ogra_> then it reboots into oem-config to set up user, hostname, kbd etc etcd
[12:34] <desrt> ya.  i did all that and now i boot to an empty desktop
[12:34] <ogra_> (which on the desktop images requires X, so make sure to have a monitor attached)
[12:34] <desrt> in any case, it's all a bit much
[12:34]  * desrt just wants something he can ssh to
[12:34] <ogra_> did it properly finish actually ?
[12:34] <desrt> i read about this bug with the window disappearing...
[12:34] <desrt> to be honest, i don't know if it did or not
[12:35] <ogra_> you should get an aptd/dpkg UI that shows you the removal of all unneeded packages
[12:35] <desrt> i was careful not to select autologin
[12:35] <desrt> well, i'm just debootstrapping onto this sata drive now
[12:35] <ogra_> if you didnt have that (and if ubiquity is still installed) you know that oem-config failed
[12:35] <ogra_> use ubuntu-core ;)
[12:36] <desrt> i couldn't find an imx image for ubuntu core/server
[12:36] <ogra_> tar xvfz is faster than debootstrap ;)
[12:36] <desrt> seemed to only have omap
[12:36] <desrt> ohhh
[12:36] <desrt> for that
[12:36] <ogra_> there are no board specific ubuntu-core images
[12:36] <desrt> meh.  already done :)
[12:36] <ogra_> its all userspace
[12:36] <ogra_> completely unconfigured
[12:36] <ogra_> (but largely the same you get from debootstrap)
[12:37] <desrt> any board-specific userspace config i should know about before i try to boot back into this thing?
[12:38] <ogra_> no idea, ask janimo, he owns the mx5 images
[12:38] <desrt> janimo: sup? :)
[12:38] <ogra_> i dont actually know what bootloader config is usually done there
[12:39] <desrt> the image seems to have a fat partition on it with the kernel, initramfs and some sort of boot description file
[12:39] <desrt> (text)
[12:39] <desrt> looks pretty straight-forward
[12:40] <desrt> probably it needs the microsd to load the kernel image at least, then i can use the sata as the rootfs
[12:40] <ogra_> likely a u-boot script file, thats not text
[12:40] <ogra_> (boot.scr)
[12:40] <ogra_> it has a header
[12:40]  * desrt takes a peek
[12:40] <ogra_> you shoudl eb able to get away with a vfat for booting
[12:40]  * desrt notes that the SD card is hilariously slow
[12:41] <ogra_> and then switch to rootfs on sata by root=UUID=.... on cmdline
[12:41] <desrt> so there is a boot.scr here
[12:42] <desrt> but boot.txt is the one i was looking at earlier
[12:42] <ogra_> right, that should have a 64byte hearder
[12:42] <ogra_> and is generated using mkimage
[12:42] <ogra_> likely from boot.txt
[12:42] <desrt> it appears to be plain text...
[12:42] <ogra_> .scr ?
[12:42] <desrt> .txt
[12:42] <ogra_> yeah
[12:42] <desrt> oh.  i see what you're saying
[12:42] <ogra_> thats the input file
[12:42] <desrt> .txt gets compiled into .scr
[12:42] <ogra_> right
[12:43] <ogra_> mkimage adds a header
[12:43] <desrt> and somehow the .scr is 'blessed'?
[12:43] <ogra_> yep
[12:43] <ogra_> u-boot looks for it on boot
[12:43] <desrt> cool
[12:43] <desrt> lemme guess -- this 4MB /dev/mmcblk0p1 partition is uboot
[12:43] <ogra_> not sure, thats where janimo comes into play
[12:44] <ogra_> i dont have such a board and never had one in my hands
[12:44] <desrt> it's gotta be -- the kernel doesn't seem to fancy mounting it
[12:44] <ogra_> so i dont know exactly how it boots
[12:44] <desrt> i think you've helped me put together a pretty clear image for myself
[12:44] <ogra_> yeah, we tag the boot partitions with a label that udev ignores
[12:44] <ogra_> so you dont have it mounted on your desktop install ;)
[12:45] <desrt> it has dos partition type 0xfa ("Non-FS Data")
[12:45] <ogra_> (the kernel should see it in dmesg though, it should just nott be automounted)
[12:45] <desrt> 0xda, rather
[12:45] <ogra_> ah, yeah, that coudl eb raw u-boot
[12:45] <ogra_> *be
[12:47]  * desrt wonders why this uboot wasn't given ext4 support
[12:47] <ogra_> ask  upstream :)
[12:47] <desrt> oh.  srsly?
[12:47] <ogra_> it has ext2
[12:47] <desrt> that's a pretty good reason, then :)
[12:48] <ogra_> ext4 would rock though, you wouldnt need a separate boot partition
[12:48] <janimo> desrt, the mx53 ubuntu image is very slow indeed. No idea why yet, something to fix for 12.04
[12:48] <ogra_> but i think it bloats the codee to much or something
[12:48] <janimo> desrt, the linaro image for same board was much snappier iirc
[12:48] <janimo> and not only because if does not do an install
[12:48] <ogra_> lies !
[12:48] <ogra_> :P
[12:49] <desrt> janimo: it seems to be mostly the IO that is slow -- and only to the SD card
[12:49] <janimo> we use the same kernel as linaro so I am puzzled why this happens, but all of us who tested mx53 late in the oneiric cycle
[12:49] <janimo> saw it was very slow
[12:50] <janimo> ogra_, shouldn't an ext2 driver see an ext4 partition especially in read only mode as uboot is?
[12:50] <janimo> just ignoring the extra features
[12:50] <ogra_> no, i think you need ext3 support to see ext4
[12:51] <janimo> ok
[12:51] <ogra_> not sure though
[12:51] <janimo> maybe it is only vice versa then
[12:54] <ogra_> you can definitely see ext3 from an ext2 driver
[12:54] <ogra_> there the only difference should be the journal
[12:55] <ogra_> ndec, so you are sure about the model ? (you didnt say anything in the mail)
[12:56] <ndec> ogra_: sorry. i forgot that ... do you have a serial number or any other number on the board?
[12:56] <ndec> to be honest i haven't even seen such a board myself ;-)
[12:56] <ogra_> on the board or on the shell ?
[12:56] <ndec> whatever...
[12:56] <ndec> anything...
[12:56] <ogra_> there is a barcode glued underneath the sd slot
[12:57] <ogra_> T0000001266
[12:57] <ogra_> seems to be the serial # ... its on the box too
[12:58]  * desrt discovers flash-kernel.conf
[12:58] <ogra_> ndec, then i also have TEVM4460G-22-20-01
[12:58] <ndec> sounds a useful discovery...
[12:58] <ogra_> not really
[12:58] <ndec> ogra_: that one looks useful!
[12:58] <ogra_> once we switch to flash-kernel-ng there wont be a config file anymore
[12:58] <ndec> my first comment was for desrt ;-)
[12:58] <ogra_> yeah
[12:59] <ndec> argh...
[12:59] <ogra_> argh ? because of new flash-kernel ?
[12:59] <desrt> the failure situation for that file missing is a bit sad
[12:59] <ogra_> flash-kernel is all in all a bit sad :P
[12:59] <ndec> yes, because we are doing tricky things with flash-kernel.conf ;-)
[13:00] <ogra_> it makes you cry like onions if you look to long at the code
[13:00] <ogra_> in fact i would recommend rubbing onions in your eyes instead of looking at the code :) ... if you have the choice
[13:00] <ogra_> hurts less
[13:00] <ogra_> :)
[13:01] <desrt> looking at the code led me to discover UBOOT_PART
[13:01] <desrt> since it does something like this:
[13:01] <ogra_> yeah, thats an ugly wart
[13:01] <desrt> mount ${UBOOT_PART} ${tmpfile}
[13:01] <desrt> and doesn't consider that ${UBOOT_PART} may be unset :p
[13:01] <ogra_> the new flash-kernel has a proper DB wiht an entry per board arch
[13:01] <desrt> neat
[13:01] <ogra_> that will be way cleaner
[13:01] <ogra_> still hackish but lots better
[13:02] <ndec> ogra_: i am amazed, but we do have an internal DB where I could find your reference that you gave me ... TEVM4460G-22-20-01  -> OMAP ES1.1 GP,    1.5GHz, PWR ES2.0, AUD ES1.1 
[13:02] <ogra_> ndec, to be honest the device doesnt look much different from the one i already have ...
[13:02] <ogra_> chrome metal frame etc
[13:03] <ogra_> NIC built in the wrong way round again :) (which i only discovered after i had the cable attached indeed)
[13:03] <ogra_> etc etc
[13:03] <desrt> gonna try a reboot now
[13:03] <ogra_> good luck :)
[13:05] <desrt> WIN
[13:05] <desrt> works on first try
[13:05] <desrt> failed to set root password or add self to sudoers file
[13:06]  * desrt hands head in shame
[13:06] <lilstevie> ogra_: haha I had a look at flash kernel, proceeded to rip my eyes out, then think about doing my own platform specific hack till flash-kernel-ng
[13:07] <desrt> janimo: know offhand what serial parameters you configured uboot for?
[13:30] <S0NiCaw> re
[14:04] <ogra_> ndec, see pm :)
[14:05] <ogra_> An-iSociaL, if you need help with ac100 md5sum mangling, i'm around now
[14:09] <S0NiCaw> hmm can anybody help me with my ubuntu-arm and crosscompiling? ;)
[14:09] <ogra_> better try #linaro
[14:09] <S0NiCaw> ok thx
[14:20] <brendand> do all armv7l platforms follow the same layout for /proc/cpuinfo?
[14:21] <ogra_> the kernel does
[14:23] <ppisati> GrueMaster: http://people.canonical.com/~ppisati/linux-image-2.6.35-903-omap4_2.6.35-903.27~mlockfix_armel.deb
[14:23] <ppisati> GrueMaster: this should fix the
[14:23] <ppisati> GrueMaster: "Make sure the stack guard page does not split the stack on mlock ... FAIL"
[14:24] <ppisati> GrueMaster: you saw in test-kernel.py
[14:24] <ppisati> GrueMaster: can you verify it?
[14:56] <ppisati> GrueMaster: and while here
[14:56] <ppisati> GrueMaster: https://launchpadlibrarian.net/85419190/test-kernel-security.log
[14:56] <ppisati> GrueMaster: on one line it says: "PR_SET_SECCOMP works ... FAIL" but below that
[14:57] <ppisati> GrueMaster: "CONFIG_SECCOMP enabled ...  (skipped: not available on ARM) ok"
[15:59] <An-iSociaL> afternoon all
[16:00] <An-iSociaL> ogra_, if you mean the tarball installer, thanks but i figured it out
[16:00] <ogra_> well, you hacked it to be broken afterwards i guess
[16:00] <ogra_> :)
[16:01] <An-iSociaL> hm?
[16:01] <ogra_> the proper way is to roll a cpio.gz archive with a file carrying the tarball md5 of your modified tarball
[16:01] <ogra_> and then cat'ing that to the end of the initrd
[16:01] <An-iSociaL> ahhh
[16:01] <ogra_> if you hack the script you might get unexpected results
[16:02] <ogra_> and unlike GrueMaster claims we dont do "werid things" with the md5 at build time :)
[16:02] <An-iSociaL> i actually performed the role of the installer script myself, did the formatting, extracting, getting uuid, purging intaller
[16:02] <ogra_> we just put the file in place before rolling the initrd
[16:03] <An-iSociaL> and the fstab
[16:03] <ogra_> well, that will miss a bunch of configuration
[16:03] <ogra_> unless you also made oem-config work
[16:03] <ogra_> (which does the actual configuration in a proper way)
[16:03] <An-iSociaL> im pretty sure i did, oem-config did run after touching it
[16:03] <ogra_> ah, cool
[16:03] <ogra_> then you shoudl be fine
[16:04] <ogra_> the code we use to add the md5 is in the livecd-rootfs source btw
[16:04] <ogra_> for future reference
[16:04] <An-iSociaL> will have to go back to the installer if i intend to distribute
[16:04] <An-iSociaL> nice
[16:07] <An-iSociaL> noted it
[16:23] <lilstevie> heh
[16:23] <lilstevie> the way I do it is with the omap image
[16:24] <An-iSociaL> sup lilstevie
[16:24] <lilstevie> not much just working on my app
[16:24] <An-iSociaL> oh cool. whatcha building?
[16:25] <lilstevie> an app for the tf101 ubuntu/android system
[16:25] <lilstevie> android app for managing it
[16:25] <An-iSociaL> nice
[16:26] <An-iSociaL> im just watchin tv trying to get in the mood to do something
[16:33] <hallyn> If I just want to run an arm precise image in qemu-arm to verify a bugfix, what's the quickest way to create an image?  Do I download one of the preinstalled images from cdimages.u.c?  Is there a disk image i can wget?
[16:35] <An-iSociaL> uhm
[16:35] <An-iSociaL> the only image i currently know of is for the ac100
[16:35] <An-iSociaL> likely wouldnt do what you want
[16:36] <An-iSociaL> fastest way otherwise would be debootstrap
[16:37] <hallyn> and then d/l a kernel from somewhere?
[16:38] <ogra_> hallyn, use ubuntu-core and look in the linaro docs about vexpress with qemu
[16:39] <ogra_> or just use an arm chroot, if you dont need a full VM
[16:40] <hallyn> ok, thx.  (i don't think a chroot'll work as it's ecryptfs-related, but will try)
[16:41] <ogra_> ah, yeah
[16:41] <ogra_> wiki.ubuntu.com/Core
[16:41] <An-iSociaL> could be difficult working with lower level stuff like filesystems in a chroot
[16:41] <ogra_> note that there isnt a user/pw or any configuration
[16:41] <ogra_> you will need to do that yourself
[16:42] <An-iSociaL> qq ogra_, what cross compiler do you use?
[16:42] <hallyn> ok, thanks guys
[16:42] <ogra_> An-iSociaL, i compile native
[16:42] <An-iSociaL> ahh
[16:43] <An-iSociaL> obviously that would be better but how much better?
[16:43] <ogra_> depends what you compile really :)
[16:43] <An-iSociaL> specifically for kernel builds
[16:44] <ogra_> i usually build packages ... for that native is always better
[16:44] <ogra_> though there are already a bunch you can actually cross build nowadays
[16:44] <ogra_> for kernel test builds i would actually recommend cross
[16:44] <ogra_> and use the gcc-cross in the archive
[16:45] <An-iSociaL> aha
[16:45] <An-iSociaL> sweet
[16:45] <An-iSociaL> i think using the android cross compiler's been jacking my stuff up
[16:46] <An-iSociaL> kernel modules for sure
[16:46] <An-iSociaL> makes me wonder if its jacked up kernel modules wth has it done to the kernel itself
[16:47] <ogra_> there should be a package gcc-armel-cross or some such
[16:48] <ogra_> (ask hrw, he maintains it, i can never remember the actual name)
[16:48] <An-iSociaL> i saw it when i was extracting
[16:51] <hrw> gcc-arm-linux-gnueabi
[16:53] <ogra_> bah, not even remotely a -cross in the name :P
[16:53] <An-iSociaL> hehe
[16:55] <An-iSociaL> cool cool thanks
[16:55] <An-iSociaL> grabbin it now
[16:55] <An-iSociaL> perhaps this will solve a couple little bugs
[16:56] <An-iSociaL> getting closer to being in the mood to do something... yay...
[17:00] <S0NiCaw> cu
[18:33] <MrCurious> anyone have any experience getting python 2.7 to compile on a arm platform? (gumstix)
[21:35] <RoAkSoAx> hey guys
[21:35] <RoAkSoAx> any reason why unity run very slow on a pandaboard
[21:35] <RoAkSoAx> might it be because im not using a swap?