[02:36] <jk-> ogasawara: I've just registered hardware-q-defensive-software; is there any magic I need to do to get it scheduled?
[03:21] <snadge> ive tried googling for this.. and i can only seem to find idiot responses so i thought i'd ask in here
[03:21] <snadge> i have a pc with 4GB ram total.. and am running 12.04 64bit on it
[03:21] <ohsix> it depends on the chipset
[03:21] <snadge> MemTotal:        3044928 kB
[03:21] <ohsix> (/me waits for rest of question to see if he's right)
[03:22] <snadge> i have checked the onboard graphics settings.. and regardless of what i set it to.. i still have that memtotal
[03:22] <ohsix> right, some is reserved for pci devices, you need to flip an option in your bios if you can
[03:22] <snadge> i dont have any pci devices.. and my bios is retarded
[03:22] <ohsix> only devices that can do a dual address cycle can be moved out of the lower 4g of physical memory, and that is not all of them
[03:22] <snadge> its an intel motherboard
[03:23] <ohsix> all your devices are pci ... some of them, like a gpu have rather large pci areas
[03:23] <snadge> perhaps i need to buy a dedicated graphics card to free up the 1GB?
[03:23] <snadge> theres no options in the bios relating to reserving memory for pci devices
[03:23] <ohsix> the option in your bios may even be called something like "Installed OS:" and the choice is Windows or Other
[03:23] <snadge> i can only change the apeture size.. and something called dvt
[03:24] <snadge> so i have set them both to the lowest value of 128mb
[03:24] <ogasawara> jk-: looks like it's already approved for uds-q so it should be getting auto-scheduled
[03:24] <jk-> ogasawara: awesome, thanks.
[03:24] <ogasawara> jk-: lemme know if you want me to try and lock it down to a specific date, time, or room
[03:24] <ohsix> without EFI you are left with what the bios lets you do, my pc at home doesn't let me do anything, so i'm in the same situation you are :]
[03:24] <snadge> i dont remember seeing an installed os option
[03:24] <snadge> there is a UEFI option though
[03:24] <snadge> which is disabled
[03:24] <ohsix> snadge: what chipset/board is it? some boards deliberately don't allow it
[03:25] <jk-> ogasawara: no, should be fine being dynamic.
[03:25] <snadge> DG43NB
[03:25] <snadge> i think is the motherboard
[03:26] <ohsix> snadge: see if that matches cat /sys/class/dmi/id/board_name
[03:26] <snadge> yes
[03:27] <snadge> Version: AAE34877-405 (from dmidecode)
[03:27] <snadge> looks completely different to the version number that intel offers on their site
[03:27] <snadge> dated 12th jan 2011
[03:28] <snadge> NBG4310H.86A
[03:28] <snadge> ahh yes thats the one im running by the looks of it
[03:30] <snadge> although it says 0107 and im apparently running 0096.2009.0903.1845
[03:30] <snadge> which appears to be older
[03:32] <ohsix> you may have to use the uefi boot to get the devices to move ... even then some might not have DAC
[03:32] <ohsix> hah there's a bios setting for on board skull backlighting, wicked
[03:34] <snadge> Fixed issue where 64-bit operating system runs extremely slow
[03:34] <snadge> with 4 GB memory installed.
[03:34] <snadge> LOL
[03:34] <snadge> i totally need this bios update.. this pc runs like a dog
[03:34] <snadge> with its legs shot off
[03:35] <snadge> Fixed issue where BIOS Setup is inconsistent on memory.
[03:36] <snadge> *facepalm* thanks intel ;)
[03:37] <RAOF> “Fixed issue where system fails to hand off to GRUB roughly half the time” :)
[03:45] <ohsix> snadge: yea i don't see any option that stands out, except the efi thing; getting it to work on an existing install can be a real drag
[04:41] <snadge> MemTotal:        3915828 kB
[04:41] <snadge> yes!!! bios update.. :D
[04:41]  * snadge shakes fist at intel
[04:41] <snadge> i had to write freedos to a usb stick.. and flash the bios from DOS.. sigh
[04:42] <snadge> the windows flash tool didnt work
[04:42] <snadge> and the flash tool built into the bios.. also didnt work
[06:44] <ppisati> moin
=== smb` is now known as smb
[07:21] <smb> morning
[08:37] <apw> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=1a5a9906d4e8d1976b701f889d8f35d54b928f25
=== amitk is now known as vinguamit
=== vinguamit is now known as amitk
[11:50]  * cking grabs some food
[12:59] <tgardner> apw, doh
[13:00] <apw> tgardner, often indeed
[13:01] <tgardner> apw, I wacked on one of your bugs, bug #931353
[13:01] <ubot2> Launchpad bug 931353 in linux-base "package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.3" [High,In progress] https://launchpad.net/bugs/931353
[13:01] <apw> tgardner, bah i was going to do that towards my coredev
[13:02] <tgardner> apw, ah, sorry.
[13:29]  * apw wanders out to get some last minute travel bits
=== JanC_ is now known as JanC
=== kirkland` is now known as kirkland
[14:19]  * ogasawara back in 20
[14:30] <hallyn> sigh, is there a git-am flag to say "offsets are ok"?
[14:33] <tgardner> hallyn, -3 ?
[14:33] <tgardner> --3way
[14:34] <apw> hallyn, -C1 perhaps
[14:34] <apw> -C1 gives you semantics like patch
[14:35] <hallyn> tgardner: i'm an ignorant git and never looked up what a 3way really is
[14:35] <hallyn> apw: hm, -C1 isn't in git-am man page
[14:35] <tgardner> apw, apw is likely more crrect in that you want -C1
[14:36] <tgardner> hallyn, its in 'git apply'
[14:36] <tgardner>        -C<n>
[14:36] <tgardner>            Ensure at least <n> lines of surrounding context match before and after each change. When fewer lines
[14:36] <tgardner>            of surrounding context exist they all must match. By default no context is ever ignored.
[14:37] <hallyn> cool, with 130 patches in the mbox and 40 patches in it may be worth re-trying with that :)
[14:37] <tgardner> thats a lot of patches
[14:37] <hallyn> hm, -C1 sounds dangerous though :)
[14:38] <hallyn> I just want it to ignore offsets, not changed context
[14:38] <apw> hallyn, it tells you exactly what it relaxed when it did it
[14:38] <apw> hallyn, and as i say -C1 makes us only as lax as a normal patch apply
[14:39] <hallyn> but if the patch has 3 lines of context, and I say -C3, will it then still ignore offsets?  And is -C3 in that case safer than -C1?
[14:42] <hallyn> hm, 'context reduced to (1/1)', guess it did need to be C1 :)  thanks apw
[14:44] <apw> yep so you need to be wary and eyeball what happened just in case
[15:15]  * smb drops off to enjoy some outside air before leaving early tomorrow...
[15:19]  * cking goes and packs his bags
[16:13] <cking> apw, henrix, seeya at LHR terminal 5 tomorrow
[16:14] <henrix> cking: see you there!
[16:14]  * cking goes to sort out final bits and bobs
[16:14]  * henrix needs to start packing as well...
[16:15] <apw> yeah time to go pack and all that ... see you all
[17:06]  * tgardner -> pack for UDS
=== tgardner is now known as tgardner-afk
[22:23] <jjohansen> ogasawara: when is the next kernel upload for precise planned for? Oh and quantal too?