/srv/irclogs.ubuntu.com/2014/01/23/#ubuntu-kernel.txt

=== mwhudson is now known as zz_mwhudson
vic1Kernel Experts: 04:27
vic1Could i get the exact kernel source git tree that was used to generate: trusty-preinstalled-boot-armhf+maguro.img04:27
vic1Maguro(samsung galaxy nexus) Kernel source tree is what i am looking for Ubuntu Touch.04:29
=== zz_mwhudson is now known as mwhudson
ppisatimoin07:41
=== mwhudson is now known as zz_mwhudson
=== lag` is now known as lag
apwppisati, moin09:27
smbapw, If you ain't hearing anything your mumble is broken09:36
apwor my ear is currently remote09:36
* apw bets 10p on the latter09:36
smbor that09:36
smbapw needs ears on strings09:37
hvn3hi, I run precise on armhf (beagleboard-xm) and need to add xenomai. I tried codesourcery but that doesn't do it. Linaro people directed me here. Can someone please help me out. Thank you.09:41
brendandcking, hey - which of your ppa's has the version of fwts with the stdout-summary fix?09:44
ckinghttps://launchpad.net/~colin-king/+archive/ppa, but only a trusty build09:47
ckingbrendand, we hope to spin a 14.01.01 release to address this before the week is out09:48
brendandcking, ok09:49
apwhvn3, not sure what you are asking really?09:55
brendandcking, when will 14.01.01 be out?09:58
ckingbrendand, hopefully end of this week if it builds OK today10:00
hvn3apw: I'm asking if someone here can direct me to info on cross-compiling a xenomai-patched precise-kernel to armhf10:00
hvn3apw: it needs to run on omap310:01
hvn3apw: the tools I have found so far only cross-compile to either armel or armv6, not to armhf and armv710:02
ppisatihvn3: i'm reading the xenomai doc right now10:02
ppisatihvn3: hold on10:02
hvn3ppisati: ty10:03
ppisatihvn3: you already did the "scripts/prepare-kernel.sh --linux=..." step, right?10:03
ppisatihvn3: you just need to recompile a patched kernel, don't you?10:03
hvn3ppisati: at got stuck at that point, because it tells me the kernel is unsupported.10:04
hvn3ppisati: I used a vanilla-kernel btw, not a ubuntu kernel-source10:05
ppisatihvn3: https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile10:05
ppisatihvn3: FAQ section, point 610:06
ppisatihvn3: make ARCH=arm omap2plus_defconfig10:06
ppisatihvn3: edit .config to suit your need10:06
ppisatihvn3: (you better try it with make ARCH=arm menuconfig since - i guess - xenomai adds some menu entries and you want to select that)10:07
ppisatihvn3: and then10:07
ppisatihvn3: make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- uImage10:07
hvn3ppisate: I read that now....I stopped reading that because it mentioned omap410:07
ppisatihvn3: when you did "scripts/prepare-kernel.sh --linux=..." did you use the --arch= switch?10:08
ppisatihvn3: "3) Ok, but what about my Beagle/XM? How do i compile a kernel for an omap3 board?"10:08
hvn3ppisati: does arch=arm differ from ARCH=arm ?10:08
hvn3ppisati: I used arch=arm10:09
hvn3ppisati: not in capitals10:09
ppisatihvn3: ARCH=arm is used during the kernel compilation, --arch=arm is when you patch the kernel src tree with xenomai10:09
ppisatihvn3: ok, there's some confusion let me recap...10:09
ppisatihvn3: these are the steps that you should take to make it work:10:10
ppisatihvn3: (since you are using a vanilla kernel) checkout a vanilla tree somewhere10:11
ppisatihvn3: make ARCH=arm omap2plus_defconfig10:11
ppisatihvn3: edit .config as stated in https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile, FAQ point 6, subsection b10:12
ppisatihvn3: make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- uImage10:12
ppisatihvn3: and follow the remaining step10:12
ppisatihvn3: if it boots, then you have kernel tree and .config that you know it works with your hw and your userspace10:13
apwhvn3, arch=arm and ARCH=arm are completly different to make10:13
ppisatihvn3: after that (make a backup copy of .config)10:13
ppisatihvn3: and follow the xenomai instructions10:14
ppisatihvn3: scripts/prepare-kernel.sh --linux=$YOURKERNELTREE10:14
ppisatihvn3: sorry, add the "--arch=arm" switch at the command above10:14
ppisatihvn3: make ARCH=arm menuconfig and tweaks the config10:15
hvn3ppisati: yes, I tried that and got error, but will try again10:15
ppisatihvn3: and finally "make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- uImage" and follow the rest10:15
hvn3ppisati: thank you for helping out so far10:16
ppisatihvn3: first make sure you have a vanilla kernel AND a vanilla config working with your hw, then take the xenomai patches10:16
ppisatihvn3: because if you start patching a kernel that you never tested, you'll never know if those patches are bad, the config was already broken, the kernel didn't support your board, etcetc10:16
ppisatihvn3: baby steps10:17
hvn3ppisati: I have the 3.2.0-55-omap kernel running right now....would it be safer to get a ubuntu-kernel source ?10:17
ppisatihvn3: the kernel that you are going to use depends on xenomai (since you want to patch it with it later on), so which kernel does xenomai support?10:23
brendandcking, someones hooking me up with a test system - i'll let you know in a few hours if it works10:24
ckingbrendand, ok, thanks10:25
hvn3ppisati: as far as I see, the xenomai FAQ only mentions the hardware it supports, not kernels. So I assume it supports all recent kernels.10:26
ppisatihvn3: i wouldn't be so sure, you better find out first10:27
ppisatihvn3: and when you found out which kernel it supports, you make that version work (config and compilation wise) with your board10:28
ppisatihvn3: and only after that, you apply the xenomai patches, reconfig and recompile10:29
hvn3ppisati: ok, ty for the advise10:29
hvn3ppisati: ty for your help and time10:32
apwppisati, do we still support linux-fsl-imx51 in lucid (i presume not)10:32
ppisatiapw: nope10:42
ppisatiapw: we dropped support for all the arm topic branches in L AFAIK10:42
apwgreat10:43
ppisatiapw: cve?10:43
apwyeah, just noting we are running processing on that branch for nothing, so getting rid of it10:45
=== ricmm_ is now known as ricmm
brendandcking, the fix looks good. cheers!11:27
ckingbrendand, cool, thanks for letting me know :-)11:27
zequenceinfinity: There's a problem with the saucy -lowlatency. From what I can tell, it includes the right code, but the debian/changelog file only shows 3 master commits since 3.11.1511:54
infinityzequence: Oops.  Want to fix that up?11:59
infinityzequence: I'm in no rush to copy it over ASAP.12:00
apwzequence, you hsould be able to reset to the previous lowlatency tag and remake it12:00
zequenceapw: Ok. I'll try that12:11
zequenceinfinity: apw: I'm applying for upload rights to ubuntustudio-* packages. Also, linux-lowlatency, but I suppose that might not be necessary anymore. If anyone of you could endorse me that would be really helpful. micahg is the person who has been most active in sponsoring our packages, so he'll probably add a few words here too https://wiki.ubuntu.com/zequence/DeveloperApplication12:29
zequenceI realize you don't know that much about my packaging skills, and tbh, I need a lot more practice, but the ubuntustudio-* packages are pretty straightforward, and I do maintenance on most of them12:30
zequenceThings went better with saucy this time. I'm uploading soon12:32
zequenceinfinity: did you get the reject message too?12:39
infinityzequence: Why would I get reject messages on your uploads?12:41
infinityzequence: You didn't reuse the same version number did you?12:41
infinityzequence: You can't reuse versions, even if you delete the old one.  Just bump the build number, so it's -7.1012:43
infinity(Don't bother with a new changelog entry, just edit the top line and re-tag and rebuild the source)12:43
infinity17.10, even.12:44
zequenceinfinity: Just guessing. LP might be able to send pigeon post until I know it doesn't ;)13:03
zequenceinfinity: It's up now.13:04
infinityzequence: Great, thanks.13:07
brendanddoes anyone know what is happening with the -proposed kernels?13:08
brendandare they waiting for 12.04.4 release?13:08
apwbrendand, that is my understanding yes, that they are all holding for the point release which in and of itself was delayed13:35
* apw muses that if they hold much longer we might consider respinning them for stables throughout13:36
rtgapw, here is a 3.13 bug we ought to keep an eye on (from LKML): '[BISECTED] Linux 3.12.7 introduces page map handling regression'13:40
rtgsmb, ^^13:40
apwrtg, looking13:40
smbrtg, hm looking13:41
rtgdunno if it requires 3.13 host as well13:41
smbHm, yeah that sounds like something we had reports too and was somewhat related to anonymous pages (at least that flag seemed present most of the times)13:45
rtgapw, smb: here is another good one: 'fanotify use after free.'. Seems like 3.13 might have some gotchas for awhile.13:47
apwrtg lets be glad we ahve a few stables before release13:48
rtgoh yeah13:48
smbrtg, Uhm, well for those bad page thing... not sure how much of numa code was around then but we got a bug report unresolved for something looking reaaalyly similar for Lucid13:53
smbNeed to try that testcase there13:53
rtgapw, you (or your minion) are still planning to produce a low-latency kernel for Trusty, right ?14:03
apwrtg, yeah, the question which has been raised is as to whether to pull it into master-next14:37
rtgapw, are there no extra patches now ?14:37
rtgapw, perhaps you should add this to the sprint agenda14:38
apwthere is one patch, but that changes the default for a configuration option14:38
apwso we could carry that and it be only config them14:38
apwrtg, already on there14:38
rtgapw, ack14:38
apwi was presuming i would sort out the fat kernel and meta in a ppa, we could decide that on monday and upload them together or not14:39
rsalvetiapw: rtg: did a rebase for manta (aosp 4.4.2) based, tested and working fine with the 4.4.2 port that I'm working on: http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-trusty.git;a=shortlog;h=refs/heads/manta-kitkat16:16
rsalvetican any of you get this merged into the 'manta' branch and upload the package to the ppa? don't yet upload to the archive as we need to first switch the android code officially (like done with mako and flo)16:16
rtgrsalveti, acl16:17
rtgack*16:17
rsalvetirtg: thanks16:18
rsalvetirtg: would also be nice to have the meta package in the ppa as well16:19
rtgrsalveti, I didn't think y'all were using a meta package16:20
rsalvetirtg: it's used by our android build system to find the package name (because of the abi)16:20
rtgrsalveti, ok, can do16:20
rsalvetiawesome, thanks!16:20
* apw reboots to test a grub2 beta17:07
* apw is somewhat supprised to be back ..17:11
apwcjwatson, just installed and booted my efi system (secure boot _off_) with your new grub2 from -proposed17:12
apwcjwatson, all seems to be ok, only noticed a '*' marker on the menus, other than that it seemed the same17:12
cjwatsonI think that was deliberate17:14
apwit didn't seem like a bad thing, just noticed it17:15
cjwatsonapw: yep, http://git.savannah.gnu.org/gitweb/?p=grub.git;a=commitdiff;h=a59a9826fd56efe350933ef73cba3a42b97a52b917:16
apwcjwatson, it seems to let me select other kernels, and edit things, i have an issue with ctrl- not working in the exec screen but i seem to remember that was there before for me17:21
apwcjwatson, but worth checking next reboot if ctrl-x works ok for you17:22
cjwatsonapw: ok.  does the help screen still advise ctrl-x?17:28
apwyeah, the help is the same, and F12 or whatever it is works ok17:28
apwi think it is a bios issue, as hitting C-x gives me an X 17:28
cjwatsoneven outside grub?17:28
apwonly in grub17:29
cjwatsonbit sceptical of that being a bios issue then17:29
cjwatsonI vaguely recall some attempt to improve EFI keyboard handling but I can't find it now17:29
apwi'll downgrade and confirm its there before either way17:29
=== jono is now known as Guest52764
cjwatsonta17:30
apwcjwatson, ok confirmed ctrl- issue is there in the 2.0.22 version as well17:34
cjwatsonah ok17:34
cjwatsonso I guess that could just be crazy bios17:34
cjwatsonthanks for the testing17:34
apwyeah i suspect so, and it is a pre-release job, so i am not so concerned about it17:34
rtgrsalveti, manta -5.20 uploaded. I'll get the meta package in a bit17:34
apwand i have "or Fn" keys which work just fine17:35
rsalvetirtg: great, mind also doing the meta package for flo?17:35
rtgrsalveti, np17:35
rsalvetiawesome17:35
kirklandI'm curious if anyone here has experience using amtterm to get console output on Ubuntu?18:57
kirklandI have a couple of systems that have Intel AMT enabled;  and I can use it successfully to remotely power on/off systems18:58
kirklandbut I haven't succeeded yet with getting console output18:58
kirklandI've tried following http://manpages.ubuntu.com/manpages/trusty/en/man7/amt-howto.7.html18:58
kirklandbut that manpage talks about inittab, which, of course, doesn't exist in Ubuntu18:58
kirklandcking: you seem like my most likely candidate to have tried ^  :-)19:02
ckingkirkland, i've not used that19:02
kirklandcking: bummer19:03
mjg59I have also not tried that19:03
kirklandmjg59: wow, you either, huh?19:04
mjg59I've played with most of the other features. And cried.19:05
kirklandmjg59: it's a bit wonky, isn't it19:05
kirklandwhere would I put "T2:2345:respawn:/sbin/getty ttyS2 115200 vt100-nav", if not inittab?  I'm guessing somewhere upstarty...19:05
mjg59kirkland: /etc/init/ttyS2.conf19:06
mjg59kirkland: Compare to tty1.conf, etc19:06
kirklandmjg59: excellent, thanks19:07
* cking likes the man page section "More fun with AMT", yeah, right19:08
kirklandcking: :-P19:09
kirklandcking: self-extracting archive19:09
ckingfun as in "poking oneself in the eye with a red hot poker"19:09
kirklandheh19:09
kirklandcking: oh, btw, I encountered something very odd this week, something that gave me many hours of headache19:10
kirklandcking: realtek USB ethernet adapters19:10
kirklandcking: we had a bunch of them, all identical, some worked, some didn't19:10
kirklandcking: ie, dmesg could see some, but not others19:10
ckingkirkland, duds or something more bizarre?19:11
kirklandcking: perhaps more bizarre; not dudes19:11
kirklandcking: after poking at it for several days, we noticed that the ones that didn't show up as NICs19:11
kirklandcking: actually showed up as cdrom/optical devices19:11
kirklandcking: when running windows, you get a popup, that a cdrom exists with some drivers you need to install19:11
ckingkirkland, there is some special magic that makes them switch mode, I can't recall what it is19:11
kirklandcking: you do that, and then it clears some flag19:12
kirklandcking: after which it looks like a nic again19:12
kirklandcking: we couldn't figure out how to clear that flag in Linux (though we didn't try too hard)19:12
kirklandcking: cool, so you've encountered these before19:12
ckingkirkland, something like usb-modeswitch, I've seen this on a USB 3G modem dongle19:13
ckingisn't it something like "ZeroCD" mode?19:13
ckinghttp://en.wikipedia.org/wiki/Virtual_CD-ROM_switching_utility perchance?19:14
kirklandcking: interesting, I'll definitely try it if I get access to another one of these dongles19:25
apwkirkland, try ejecting the CD rom device, that is commonly what occurs on the 3G modems19:26
apwkirkland, you ask it to eject and that makes it go awayand the modem or whatever appear19:26
ckingthat's a nice trick19:28
kirklandapw: heh, cool :-)19:33
apwcking, it makes some sense for sure19:48
=== zz_mwhudson is now known as mwhudson
=== mwhudson is now known as zz_mwhudson
=== zz_mwhudson is now known as mwhudson

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