/srv/irclogs.ubuntu.com/2010/11/13/#ubuntu-arm.txt

RobotGuyIs there a way to get gcc 4.3 instead of 4.4 or 4.5?00:21
RobotGuyIs there a way I can tell rootstock to use gcc 4.3 instead of the later compilers?01:20
rcn-eeRobotGuy, are building stuff in roostock? otherwise select the 'gcc-4.3' package..01:21
RobotGuyYes, rootstock.  I tried selecting gcc-4.3 but it doesn't seem to work.01:22
rcn-eewhat do you mean it doesn't work?01:22
RobotGuyIt still takes gcc 4.501:23
RobotGuyOr maybe it is 4.4, but not 4.301:23
rcn-eewhen you call "gcc" in your image? gcc-default does that, either call "gcc-4.3" in your build script or change the setting in ubuntu..01:23
RobotGuyI already told you I did that - selected "gcc-4.3" and it doesn't get me gcc 4.301:24
rcn-eewhich distro?01:24
RobotGuyUbuntu built with rootstock.01:25
rcn-eeRobotGuy, lucid/maverick?01:25
RobotGuy10.10 Maverick01:25
rcn-eeit exists.. http://packages.ubuntu.com/maverick/gcc-4.3 package name "gcc-4.3" to your seed or "sudo apt-get install gcc-4.3" will instal it later..01:26
rcn-eebut you 'unverise' enabled in rootstock..01:26
RobotGuyI haven't done anything to rootstock - it is as it was installed.01:27
rcn-eeRobotGuy, so you added "gcc-4.3" to the seed and you say it doesn't work..  what doesn't work about it in your mind?01:28
RobotGuyI still see it pulling "gcc-4.5-base"01:40
cwillu_at_workRobotGuy, adding a package won't generally remove a package01:40
cwillu_at_workI believe there's an option to remove a package from the seed though01:40
cwillu_at_work(not sure, my rootstock is thoroughly hacked up, and I promised to write up my changes and upstream them some day :p)01:40
RobotGuyThis is not intuitive at all.01:41
rcn-eeit's not really suppost to be.. just a quick way to make a base image... add the extra's later...01:41
cwillu_at_workRobotGuy, adding a package shouldn't remove packages.01:41
RobotGuyI want to replace a package.01:42
cwillu_at_workRobotGuy, if you want to replace a desk, how do you go about doing that?01:42
RobotGuyThere is also apparently a problem with Ubuntu recognizing the ethernet on the Beagle-xM.01:43
ScottKRobotGuy: Having GCC 4.5 installed doesn't preclude you from building with 4.3 if it's also installed.  4.5 is part of the build-essential metapackage for 10.10 so it's assume to be there for building.01:43
cwillu_at_workunrelated :p01:43
RobotGuycwillu_at_work: I'm not a first grader01:43
rcn-eeRobotGuy, pulling in 'gcc-4.5-base' happens.. you want "gcc-4.3" that depends on "libc6" which depends on "libgcc1" which depends on "gcc-4.5-base" ... ;)01:44
rcn-eejust a big circle..01:44
cwillu_at_workRobotGuy, I didn't say that you were, and supplying an analogous example was recognition of intelligence01:44
cwillu_at_workthere's that bit, too :)01:45
RobotGuygcc 4.4 and 4.5 just seem to be big problems.01:45
cwillu_at_workwhat problems are you seeing?01:46
RobotGuyInternal compiler errors01:46
cwillu_at_workI suspect you're doing something wrong somewhere;  what's your build setup like?01:46
RobotGuyI'm just trying to build a kernel.01:47
cwillu_at_workhow?01:47
cwillu_at_worknative builds?  cross compiling?  qemu?01:47
RobotGuyOn beagleboard01:47
cwillu_at_workc4?01:48
RobotGuyNo, Beagle-xM A201:48
cwillu_at_workokay;  xm is a different beast from the other beagles01:49
cwillu_at_workand one which I don't own  :(01:49
* cwillu_at_work accepts donations :p01:49
cwillu_at_workwhich distro and version?01:50
cwillu_at_workany oddities on how things were installed?01:50
cwillu_at_workhell, is the xm even stable in general?  :)01:50
RobotGuyUbuntu 10.10 built from rootstock.01:51
rcn-eethe most important thing is 'what' kernel and 'what' clockspeed only angstrom's can handle the full 1Ghz, mine limited to 800mhz otherwise it's unstable..01:52
cwillu_at_worknot even rcn-ee is perfect :)01:53
rcn-eespecially with zippy's... i think it esd'd it today, everything but the ks8851 works on it..01:53
RobotGuyIt's a 2.6.35 kernel.01:53
rcn-eeubuntu's?01:54
cwillu_at_workRobotGuy, the included patches matter01:54
RobotGuyYes01:54
RobotGuyI don't have any idea what patches - it comes with linux-image-omap01:54
rcn-eeit should work, never tested itmy self.. can you "dmesg | grep mpurate|core"01:54
RobotGuyrcn-ee: I haven't changed the clock rate01:55
rcn-eethen it should be the default 500ish.. no idea why your board is iceing in gcc, it shouldn't..01:55
RobotGuy500? Mine says 80001:56
rcn-eeoh great...01:56
rcn-eeyour running an image with my install script with ubuntu's kernel and pushing 800... no idea if that's stable, nor have tested it..01:56
RobotGuyI didn't change anything.01:57
rcn-eecan you pastebin the boot.scr in the fatfs?01:57
RobotGuyYou're telling me that to use Ubuntu, I have to run at half the speed of my board?01:58
cwillu_at_workrcn-ee, your kernel brings up the network on that, no?01:58
RobotGuyI've never been  able to get networking to work.01:59
cwillu_at_workRobotGuy, you're not using rcn's kernel01:59
rcn-eeit should, it does on all my xM boards..01:59
cwillu_at_workRobotGuy, rerun rootstock with one of his kernel's (which iirc is how rootstock is intended to be used anyway)02:00
rcn-eeRobotGuy, the ubuntu guys didn't get a working xM board till a week before freeze... my timelines are much more relaxed.. 'aka oh crap, lets upload a fix now'02:00
RobotGuyYou're not listening to me.02:00
cwillu_at_workRobotGuy, no, you're not listening to us.02:00
RobotGuyI have not changed anything in rootstock.02:00
cwillu_at_workyou're doing things wrong, and expecting it not to matter.02:00
RobotGuyHow am I doing things wrong?02:01
RobotGuyWhat am I doing wrong?02:02
cwillu_at_work<rcn-ee> then it should be the default 500ish.. no idea why your board is iceing in gcc, it shouldn't..02:02
cwillu_at_workbecause02:02
cwillu_at_work<rcn-ee> RobotGuy, the ubuntu guys didn't get a working xM board till a week before freeze02:02
cwillu_at_worktherefore02:02
cwillu_at_work<rcn-ee> the most important thing is 'what' kernel and 'what' clockspeed only angstrom's can handle the full 1Ghz, mine limited to 800mhz otherwise it's unstable..02:02
RobotGuyWe seem to be going round in circles and I am getting quite dizzy.02:03
cwillu_at_work:)02:03
cwillu_at_workRobotGuy, if you want to use rootstock, and you want to run at 800mhz, then you need to supply rcn's kernel.  You can probably do this without remaking the image, although it's a bit finicky02:03
cwillu_at_workIf you use rcn's kernel, the network will also Just Work.02:04
RobotGuyI keep telling you people that I did not change the clockrate.02:04
cwillu_at_work(incidently, I can has preempt_voluntary kernel now rcn-ee?)   :)02:04
cwillu_at_workRobotGuy, and we keep telling you that the ubuntu kernel isn't stable at the default clockrate02:04
cwillu_at_workthere are required patches which weren't available when ubuntu's kernel was frozen for release02:05
cwillu_at_workonly angstrom's kernel has all the patches (because that's where they get developed for the most part)02:05
cwillu_at_workeventually everybody will have them, but the hardware only came out a couple months ago.02:05
rcn-eeRobotGuy, if it's running 800Mhz, more then likely you used my "setup_sdcard.sh" script.. a "cat boot.scr | pastebinit" would prove it..02:05
RobotGuyObviously, trying to use Ubuntu was not a good idea for me.  Bummer.  I thought it would be better.02:05
rcn-eeit's that boot.scr script that changes it to 80002:06
cwillu_at_workRobotGuy, don't be that way.  Every mainline distro will be weird at this point.02:06
cwillu_at_worker, major02:06
cwillu_at_workYou need to substitute one piece, and everything will work fine.02:06
RobotGuyWhat piece?02:07
cwillu_at_workrcn-ee, 2.6.36-dl13?02:07
cwillu_at_workhttp://rcn-ee.net/deb/maverick/v2.6.36-dl3/02:07
cwillu_at_workRobotGuy, as it stands, you're mixing and matching pieces which assume you're doing it this way anyway02:07
cwillu_at_workit's an honest mistake, especially common with new hardware02:08
cwillu_at_workbut it's not our fault any more than it's your fault.02:08
RobotGuyThis is not making sense to me. :(02:08
cwillu_at_workRobotGuy, can you run the command rcn-ee gave you please?02:09
RobotGuyI need to be able to use the full speed of my Beagle-xM. If Ubuntu can't do that, then I can't use Ubuntu right now.02:09
cwillu_at_workpastebinit boot.scr02:09
rcn-eeRobotGuy, 'full' speed is only one option right now and it's angstrom, and it's on TI's 2.6.32 kernel.. The rest of us will have that hopefully in 2.6.37...02:10
cwillu_at_workRobotGuy, so you run a different kernel, which is already packaged at the address I gave you above.02:10
RobotGuyWhich is it? Ubuntu can or can not run at full speed on a Beagle-xM?02:11
cwillu_at_worknone of this has anything to do with networking, nor gcc-4.4/4.502:11
cwillu_at_workRobotGuy, ubuntu with rcn's kernel will run at 800mhz right now, and will run at 1ghz in january02:11
RobotGuyOK, that answers my question.  I'll try Ubuntu again in January or Feb then.02:12
RobotGuyWe can't hold up development that long.02:12
cwillu_at_workhow does this hold up development?02:12
rcn-eei was thinking next week.. ;) but git rebase of dvfs-pm was a huge mess. ;)02:12
cwillu_at_workrcn-ee, I was being conservative :p02:12
RobotGuyI told you - we need the full speed of the Beagle-xM now.02:12
cwillu_at_workhow could you possibly know that?02:13
rcn-eeyeah stable for everyone else..  january.. ;)02:13
rcn-eecwillu_at_work, does btrfs seem to bog down for you in git tree's?02:13
RobotGuyThe nature of our project requires top speed.02:13
cwillu_at_workrcn-ee, heh, complicated question :p02:13
cwillu_at_workRobotGuy, this is probably a good time to mention that ti's hardware isn't intended for prototyping of actual products, or actual deployment02:14
cwillu_at_worker, the beagle's02:14
rcn-eegit checkout's seem to bog when going from Head to a older branch... i think i really need to enable the new 2.6.37 mount opiton..02:14
rcn-eeRobotGuy, optomize more.. ;)02:14
RobotGuyI am well aware of that.  We are developing, not producing.02:15
cwillu_at_workRobotGuy, if you're developing, then the product speed doesn't matter.  multiply your benchmarks by 20% :p02:15
RobotGuySpeed does matter, but I am not here to argue.02:15
cwillu_at_workrcn-ee, you mean the git commands themselves?02:16
rcn-eeyeah, like a git fetch; git checkout HEAD; git checkout an old branch..02:16
cwillu_at_workI haven't noticed anything, but02:17
cwillu_at_workmight try running a defrag02:17
cwillu_at_workwhich mount options are you using currently?  (or have used in the past, some are sticky)02:17
cwillu_at_work(note that defrag operates on specific folders and files;  it's not enough to specify the root)02:17
rcn-eecould be, i build a lot of kernels on this machine.. or one of the two enabled but not 'advertised' cores is failing on this fake x4..02:17
rcn-eejust 'btrfs defaults' in /etc/fstab...02:18
cwillu_at_worknochecksum,nocow might help matters, at least for things like builds and so forth02:18
cwillu_at_workyou'd have to do a separate btrfs filesystem though, as those currently can't be set separately on subvolumes02:18
rcn-eeokay, i'll try that..02:19
cwillu_at_workbah, he left02:19
cwillu_at_workI was going to mention that pandaboard might be more useful02:19
rcn-eehe's been stuck on that issue since like tuesday night...02:20
cwillu_at_workyeah, I'm pretty sure he's been told 3 different build approaches that would give him the end result he wants02:20
cwillu_at_workand he's consistently refused to follow any one of them :p02:20
rcn-eeyeap, it's a receipe for disaster..02:21
cwillu_at_workI feel like I was getting overly crotchety, but...02:21
cwillu_at_workanyways02:22
cwillu_at_workrcn-ee, so, I see you're at home now  :)02:22
rcn-eeyeah... 8ish to 5ish.. ;)02:23
cwillu_at_workdo you know what that means?  :)02:23
rcn-eei can never be found...02:23
cwillu_at_workhint:  it involves a kernel :)02:23
rcn-eecwillu_at_work, here they are: http://rcn-ee.homeip.net:81/testing/2.6.36-something/  (forgot what i enabled, but it was that one thing)02:24
cwillu_at_work\o/02:25
cwillu_at_workthanks02:25
cwillu_at_workpreempt_voluntary I believe02:25
rcn-eeyeah that.. i knew it was 'something'02:26
cwillu_at_workrcn-ee, without ck?02:28
rcn-eeyeah, without ck...02:28
enthDoes ubuntu ARM work on StrongARM / PXA27xx processors?02:38
rcn-eeenth, not really, that stuff is too old... debian or angstrom is really your only options...02:39
enth\: Ok thanks.02:42
cwillu_at_workdownload complete02:44
rcn-eeyay i get my bandwidth back. ;)02:44
cwillu_at_workI was going to apologize for your untimely responses :)02:45
rcn-eei'm just drinking a beer, waiting for stuff to build.. ;)02:45
cwillu_at_workwhile you wait:  http://www.fanfiction.net/s/4068153/1/02:46
cwillu_at_work:p02:46
cwillu_at_workbooting02:48
cwillu_at_work(with the network plugged in, no less!)02:48
cwillu_at_workthat was quick02:49
rcn-eequick hard lock?02:49
cwillu_at_workyep02:50
cwillu_at_workand again02:52
cwillu_at_workokay, it's not my full preempt sillyness triggering this then02:53
cwillu_at_workrcn-ee, incidently, you mentioned that ks8851 was troublesome at 1ghz;  it isn't troublesome in the same way is it?02:53
rcn-eeno, it's the omap part, needs a voltage bump to the next level thru smartreflex02:54
cwillu_at_workokay02:55
cwillu_at_worktempted to get one just to reproduce this :p02:55
=== lilstevie is now known as lilstevie|ZNC
=== lilstevie|ZNC is now known as lilstevie
=== lilstevie is now known as lilstevie|ZNC
=== Tscheesy_ is now known as Tscheesy
=== lilstevie|ZNC is now known as lilstevie
sveinseI understand that a lot of you is running Ubuntu off a (micro) SD card, right?12:56
sveinseYesterday I purchased a new Class 4 Kingston 8GB micro SD. However, this card is something of the slowest I've ever seen running Ubuntu on12:57
sveinseMy old 2GB Trancend (which was bundled with a HTC phone) is *much* faster12:58
sveinseHave any of you experienced differences and difficulties in respect of memory cards?12:58
sveinseI.e. how can I find one with is fast?..12:58
ogra_actake class 1013:15
sveinseBut the class is related to read/write speeds.13:18
sveinseI did a bonnie++ comparison between the two cards. Suprisingly the read/write rates were comparible13:18
sveinseHowever the latency on IO were 4-5 times higher on the newest card.  Example. latency on random create read were 3174 us on the new, while 184 us on the old13:20
sveinseSo obviously there is some other parameter here which is not covered by the class concept13:21
ogra_acwell, i get nearly USB results with class 10 cards here13:24
sveinseYeah, I'll see if I can get my hands on one. Which brand?13:24
ogra_aci had good results with panasonic gold cards13:25
sveinsePanasonic. Interesting13:25
sveinseI not surprised though. I've had previous experiences that the off-the-radio-shack-shelf cards can be cheap (i.e. poor quality)13:27
=== Willie_ is now known as Guest49620
Neko__hey guys, anyone have any official view or a wiki or something on how to version packages based on git repos?17:06
Neko__mainly for kernel packages17:10
Neko__git commit ids aren't debian standards compliant so I can't make the debian --revision thing the tag17:10
=== Neko__ is now known as Neko
ScottKNeko: Debian package versioning has to be monotonically increasing so using git ids is out.  I usually use the date, i.e. 2010113, instead.18:18
Nekobut some packages have stuff like +gitblahblah or ~gitsomething or ~something at least18:18
NekoI never found anything which tells me what these really mean or what is recommended18:18
Nekonow I check I can't even find a package with that versioning but I know there are some :D18:18
ScottKI'm familiar with it.18:22
ScottKIn Debian versionin "~" is somewhat magical in that it's less than anything else.18:22
ScottKSo 1.0~git20101113 is less than 1.0.  You'd use this to indicate some pre-1.0 snapshot.18:23
ScottKIf you're packaging something that's a bit beyond 1.0, you'd use 1.0+git20101113 since that's higher than 1.0.18:23
ScottKNeko: Does that clarify it?18:24
Nekooh-ho! I see :)18:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!