[04:10] <Mahesh> was hoping if someone could provide an insight into this:
[04:10] <Mahesh> http://askubuntu.com/q/55138/45659
[07:37]  * apw gets his machine back together ...
[07:37] <smb> apw, What did you do to it?
[07:42] <ppisati> moin
[07:46] <apw> smb, heh, put it back together after a parental visit ...
[07:46] <apw> ppisati, moin
[07:47] <apw> Nahesh, done
[07:47] <smb> apw, Ah, so sort of putting the office back together. :)
[07:47] <apw> smb, that indeed
[07:47] <apw> smb, but nowadays I have so much stuff plugged into my machine I think the only empty port is the firewire one
[07:48] <smb> Can see that happen. Maybe time for a docking bay. :)
[07:52] <apw> smb, i wonder if this heap has one ... its pretty old so perhaps they are nice and cheap now
[07:55] <smb> apw, That is one of the things, that ThinkPads seemed to be good at. At least those seemed to have an additional docking connection. Most other seem to only offer a usb attachment.
[07:55] <apw> smb, yeah don't see no stinking connector on it ... sigh
[08:07]  * apw waits for his machine to update to the frozen archive
[08:07] <apw> only 89 updates
[08:08] <ppisati> 237 here...
[08:08] <apw> ppisati, you are just not trying hard enough
[08:11] <ppisati> curiosly just 76 on my panda... uhmm...
[08:11] <apw> lots of universe installed perhaps on the 237 box
[08:12] <diwic> is there a name for Q yet? 
[08:12] <apw> diwic, not that i have seen yet no?
[08:12] <diwic> ok
[08:12] <apw> i assume we really need to know before long though
[08:12] <diwic> yeah I feel so too
[08:12] <apw> diwic, its normally on markshuttleworth.com when its there
[08:14] <smb> diwic, While you are here and I remember...
[08:14] <apw> right before i get all settled in for the day i am going to reboot into todays 'fun'
[08:15] <smb> diwic, I know its probably not the main target thing... but do you know who would be interested / responsible for encoding into mp3 (from rhythmbox or other applications)
[08:15] <diwic> smb, who as in person or application?
[08:16] <diwic> smb, not understanding the question really
[08:16] <smb> diwic, In person (I sort of know its done trhough gstreamer stack)
[08:17] <smb> The problem I see is a) its not working correctly b) all visible ways of modifying the used gstreamer chain have gone
[08:17] <smb> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/945987
[08:17] <ubot2> Launchpad bug 945987 in rhythmbox "No Settings are available in "Preferred format", only preset defaults are used" [Undecided,Confirmed]
[08:18] <smb> That bug report is about b) but also (without knowing so) complains about a)
[08:18]  * diwic reads bug
[08:20] <smb> diwic, The settings dialog is purely a UI thing I guess... Not sure why it was seen as not needed anymore... The other problem seems to be that something seems wrong with the chain and I am not sure where the heck it would be found nowadays...
[08:21] <diwic> smb, hmm, can it export to ogg just fine, only mp3 is the problem?
[08:21] <smb> diwic, Right, ogg seems ok
[08:21] <smb> diwic, In essence the produced mp3 is vbr but has no xing header
[08:22] <smb> So bitrate and length displayed are way off
[08:22]  * ppisati -> reboot
[08:22] <diwic> smb, ah, so it *can* export to mp3, but the result is broken?
[08:22] <smb> diwic, right
[08:23] <smb> And without the dialog there is no way to verify or modify the way it does the encoding 
[08:23] <smb> (eg. have a different quality setting)
[08:24] <diwic> smb, I know a few gstreamer people, but not sure if any of them are into mp3
[08:25] <diwic> smb, gstreamer-devel could be a place to ask
[08:25] <smb> diwic, I think a good first step would be to get the dialog working
[08:25] <smb> apw, You cannot hear us anymore
[08:26] <diwic> apw, if your having mumble trouble, can you please pastebin me the output of "pacmd ls" 
[08:26] <smb> diwic, Ok, I will try it there then
[08:26] <apw> diwic, i am having 'not using the damn connector that is marked selected in the g
[08:26] <apw> gnome thingy' trouble at the moment
[08:27] <diwic> apw, IIRC the mumble audio wizard allows you to select a device there as well
[08:27] <diwic> apw, maybe it overrides gnome/pulseaudio's default setting?
[08:28] <apw> diwic, well it didn't before the last reboot, wtf, i hate hate hate pulse
[08:28] <apw> open letter to pulse "do what i say or get deinstalled"
[08:29] <diwic> apw, you can file a bug for it, against pulseaudio. Then I can spam you with requests to try newer versions and open bugs in upstream bug trackers. ;-) 
[08:29]  * apw cries
[08:29] <diwic> apw, seriously though, I *do* want to fix it. 
[08:30] <apw> diwic, yep i know, and i want it to work
[08:30] <apw> diwic, its just every bloody morning ... every bloody time ... its broken somehow, i hate it
[08:30] <apw> diwic, what against bugness fun
[08:30] <apw> diwic, and compared to the utter hideous complexity of pulse the kernel seems easy
[08:31] <smb> apw, At least its not you disk or raid that is not working...
[08:31] <apw> smb, heh ... at least that
[08:31] <apw> diwic, pus
[08:31]  * apw fails to use his keybaord as well ... sigh
[08:36] <diwic> apw, pulseaudio is far from perfect; but we're left with two options 1) be patient and try to resolve the bugs that still are there or 2) replace it with something else.
[08:36] <ppisati> ok, seems i've some mumble/pulse audio prob too
[08:36] <ppisati> i can hear you
[08:36] <apw> diwic, heh understood indeed... its just an ongoing torture ;)
[08:36] <ppisati> but you can only hear my music! :)
[08:36] <smb> ppisati, We only hear your music
[08:37] <diwic> ppisati, the output of "pacmd ls" please?
[08:39] <ppisati> diwic: a mumble restart fixed it :)
[08:39] <apw> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/982886
[08:39] <ubot2> Launchpad bug 982886 in pulseaudio "selected input in the gnome input selector is not the input that mumble uses" [Undecided,New]
[08:39] <apw> diwic, ^^
[08:39] <ppisati> diwic: pulse didn't pick the correct input (mic vs $somethingelse)
[08:40] <diwic> apw, thanks
[08:40] <apw> diwic, i have the 'default' selected in mumble, and its stubbonly the 'inbuilt audio' and not the usb mic
[08:42] <diwic> apw, hmm, maybe it has something with the "media-role:phone" that mumble identifies itself with
[08:44] <diwic> apw, I guess that if you run "pacmd stat" it would show the snowball mic as default source?
[08:45] <apw> Default source name: alsa_input.usb-BLUE_MICROPHONE_Blue_Snowball_201111-00-Snowball.analog-stereo
[08:45] <apw> diwic, ^^
[08:45] <diwic> apw, yep. So the analog input is either because of an media-role override or application override.
[08:46] <diwic> apw, how reproducible is this?
[08:47] <apw> diwic, its the first i've seen this i think, where its not possible to change it
[08:48] <apw> diwic, i updated today and rebooted, from fridays archive to todays
[08:48] <apw> diwic, i have tried moving mumble to the blue and that works and when i put it back to 'default' it goes back to the wrong one
[08:49] <diwic> apw, ah, interesting. Can you execute this command "pacmd set-log-level 4". Then switch back to 'default'. Then pastebin me "grep pulseaudio /var/log/syslog"
[08:55] <apw> grep pulseaudio /var/log/syslog
[08:55] <apw> diwic, http://paste.ubuntu.com/932257/
[08:58] <diwic> apw, thanks. PulseAudio says "not guilty": "Apr 16 09:55:02 dm pulseaudio[2964]: [pulseaudio] module-stream-restore.c: Not restoring device for stream source-output-by-media-role:phone, because already set"
[08:59] <diwic> apw, let me dive into the mumble source code to see how it opens the pulseaudio device. It'll take a little while so use whatever workaround you prefer if you need audio.
[09:03] <apw> diwic, ok thanks
[09:05] <apw> diwic, oh and just for completeness i have restarted mumble following those being attached and made the defaults; to be in this position.  plus audio output changes approriatly just fine ... i also have usb speaker fun
[09:06] <jorgesuarez_> hi, is there some place where is explained the removal of -server flavour for 12.04? there are no technical implications? i find the release notes too brief
[09:06] <apw> jorgesuarez_, there were no configuration differences which could not be done in userspace
[09:06] <apw> jorgesuarez_, therefore there was no point in building two identicle binaries
[09:07] <jorgesuarez_> so, preemption and timer interrupt can also be switched? didn't know
[09:07] <apw> jorgesuarez_, no but they had the same settings
[09:08] <jorgesuarez_> i thought based on https://help.ubuntu.com/10.10/serverguide/C/preparing-to-install.html#intro-kernel-diffs that preemption and timer interrupt were different on -server
[09:08] <jorgesuarez_> maybe something has changed since 10.10?
[09:08] <apw> that was back in 10.10 thats practically the jurassic :)
[09:09] <jorgesuarez_> but i can't find non-jurassic docs ;)
[09:09] <apw> decisions to change things like that are discussed at UDS and would be in theory at least documented in the write up of those
[09:09] <apw> on the blueprints for each release since
[09:10] <jorgesuarez_> the blueprints on launchpad, you mean?
[09:10] <apw> the one and only
[09:10] <jorgesuarez_> i'll take a look then, thanks!
[09:11] <jorgesuarez_> (sorry, i'll be afk now but come back later)
[09:34] <diwic> apw, it's mumble's fault. It explicitly sets the wrong device to be used. See comment #2 in your bug for some explanation.
[09:34] <apw> diwic, bad piece of junk ... did you shove it over to mumble ?
[09:35] <apw> diwic, i vote for (1) so it moves correctly
[09:42]  * cking rummages around for some old SSD H/W
[09:57]  * ppisati -> reboot again
[10:15] <ppisati> cool
[10:15] <ppisati> so now my lcd doesn't recognize the output from my motherboard anymore
[10:15] <ppisati> but works with my panda
[10:15] <ppisati> i'm officialy sad now...
[10:16] <apw> ppisati, since you did what, rebooted ?
[10:25] <ppisati> apw: nope, tested a new linaro patch
[10:25] <ppisati> apw: attached the panda to the right lcd
[10:25] <ppisati> apw: spent some time with it (kernel hanged, paniced, etcetc)
[10:26] <ppisati> apw: decided it was not worth it, reattached the lcd to the hdmi output of my desktop and now it doesn't sync anymore with it
[10:26] <ppisati> but it works with another source...
[10:26] <ppisati> uhmm
[10:29] <apw> physical problem, connector perhaps
[10:29] <apw> or the cable, slightly dammaged at the connector
[10:35] <ppisati> apw: i don't have another cable to test, but connectors look good
[10:48] <apw> ppisati, don't know what to think, as you didn't change th s/w on the desktop it has to be physical no ?
[10:52] <ppisati> apw: definitely, i'm already buying a cheap discrete graphics card
[10:52] <ppisati> apw: my video output was mobo integrated (intel dvi + vga)
[10:53] <apw> ppisati, how annoying
[11:01] <apw> ppisati, i can see that that will work soooo well :/
[11:01] <apw> ppisati, does the vga output work on it?
[11:08] <ppisati> yep
[11:08] <ppisati> IMO it's the motherboard that is dying
[11:09] <ppisati> btw, gfx card bought
[11:09] <apw> you are not having the highest luck right now are you
[11:09] <apw> what make did you get?  nvidia/radeon/?
[11:10] <ppisati> ati $something
[11:10] <ppisati> 30 bucks with 3 output
[11:10] <ppisati> vga + dvi + hdmi
[11:10] <ppisati> anyway, i hope i get by tomorrow (but i doubt it)
[11:11] <ppisati> going from dual to single screen sucks
[11:11] <ppisati> and yes, it seems i don't have so much luck with video related things lately
[11:11] <apw> yeah i bet it would ... i guess one day be livable, pretend one is travelling
[11:14] <ppisati> anyway
[11:14]  * ppisati -> lunch
[11:18] <henrix> apw: remember the fsam7400 driver thing i was looking at last week?
[11:18] <apw> henrix, yep
[11:18] <henrix> apw: the new driver does not support the bug reporter system
[11:19] <henrix> apw: bug #979253
[11:19] <ubot2> Launchpad bug 979253 in linux "BUG: unable to handle kernel paging request at c00fdd20" [Medium,Triaged] https://launchpad.net/bugs/979253
[11:19] <henrix> so, i guess we still need to keep the old driver anyway
[11:19] <apw> henrix, now lovely ... i think you said benh was maintaining the new driver ?
[11:19] <henrix> yep, he's the commiter
[11:19] <henrix> shall i ping him?
[11:19] <apw> henrix, might be worth approaching whoever is doing that and see if you can make it support it
[11:20] <henrix> apw: ack, i'll try that
[11:20] <apw> henrix, yeah i would indeed
[11:20] <henrix> apw: thanks
[12:40] <brendand> herton - hi
[12:41] <herton> brendand, hi
[12:41] <brendand> herton - any -proposed kernel news for today?
[12:42] <herton> brendand, oneiric finished verification, will go today for testing, you can start testing it. Lucid we are reverting one unverified patch, packages should be in proposed tomorrow I expect
[12:44] <tgardner> herton, which Lucid patch has failed to be verified ?
[12:44] <henrix> tgardner: the reverted patch was 73ae7483541a7e5e90cc4ce09a08763d86945486.
[12:44] <henrix> tgardner: "USB: EHCI: go back to using the system clock for QH unlinks"
[12:50] <tgardner> henrix, I think Ming Lei broke his hand and is gonna be out for a few days. Lemme see if I can reproduce and/or verify this patch before you get too crazy. Otherwise we'll have crackheads coming out of the woodwork in a few days complaining that their USB is too slow.
[12:51] <herton> tgardner, ok, the bug number: 624510, no one said anything despite several pings for testing there at least
[12:53] <tgardner> herton, yeah, I see that. gimme an hour or so....
[12:53] <herton> sure, no problem
[13:38] <desrt> i guess it's beyond hope for https://bugs.launchpad.net/bugs/956046 in precise?
[13:38] <ubot2> Launchpad bug 956046 in linux "intel driver fails to use dual-link LVDS if lid is down at boot" [Medium,Confirmed]
[13:42] <tgardner> desrt, is the patch referenced in the bug report merged in Linus' repo yet ?
[13:43] <desrt> no.  it's on the to-merge-in-next-version repo
[13:43] <desrt> intel-drm-next iirc
[13:45] <tgardner> desrt, it seems like it might qualify as  a bug fix for the 3.4 merge window, though I haven't actually looked at the code. Have you asked upstream about it ?
[13:45] <desrt> upstream has taken it
[13:46] <desrt> the freedesktop.org bug is marked FIXED
[13:46] <tgardner> desrt, no, I meant have you asked them to get it into the 3.4 merge window ?
[13:46] <desrt> oh.  i have no idea.
[13:46]  * desrt has no idea how the kernel works
[13:47] <tgardner> desrt, you don't necessarily have to know how it works. just ask them to merge that specific patch because it fixes your problem. you never know, they might listen.
[13:48] <desrt> i'd guess that drm-intel-next is what will go into the next release?
[13:48] <tgardner> yep, 3.5
[13:48] <desrt> tgardner: so i think it's already slated to be merged (along with a bunch of other things)
[13:48] <desrt> ah
[13:48] <tgardner> which is months away yet
[13:48] <desrt> so you mean a 3.4.x stable release
[13:48] <tgardner> desrt, 3.4 isn't in the can, so it could still make it as a bug fix
[13:49] <desrt> i guess i can ping on the freedesktop bug...
[13:49] <tgardner> desrt, right
[13:49] <desrt> okay.  done
[13:49] <desrt> how does that affect ubuntu?  aren't we on 3.2?
[13:50] <tgardner> desrt, our policy is that we typically only pull fixes from upstream, either 3.2 stable or Linus' repo.
[13:50] <desrt> gotcha
[13:51] <desrt> so if they're willing to land it on a stable branch then you'll take it
[13:51] <tgardner> desrt, correct, but it _first_ has to get merged in Lunus' repo
[13:51] <tgardner> Linus*
[13:53] <ogasawara> tgardner: speaking of 3.4, I've rebased q to 3.4-rc3, just gonna do a test build and boot then push
[13:53] <tgardner> ogasawara, ack
[14:10] <apw> RAOF, Sarvatt ^^ any thoughts on the dual-lane stuff above ?
[14:13]  * apw may be unreliable for a bit, some network reconfigs about to get to t
[14:13] <apw> to the 'oh crap' stage
[14:15]  * henrix can't find out how to add a release note task to a bug
[14:15] <apw> henrix, i am sure i know
[14:15] <apw> henrix, give me the bug # and i'll use it to remember ;)
[14:15] <henrix> apw: yeah, i guess i just need to add the bug to the "Release Notes for Ubuntu" proj
[14:15] <henrix> apw: but can't figure it out how :(
[14:15] <apw> yeah its something like that indeed
[14:15] <henrix> apw: the bug is 979253
[14:16] <apw> throw me the number and i'll figure it out and let you know :)
[14:16] <henrix> thanks
[14:16] <apw> bug #979253
[14:16] <ubot2> Launchpad bug 979253 in linux "BUG: unable to handle kernel paging request at c00fdd20" [Medium,Triaged] https://launchpad.net/bugs/979253
[14:16] <henrix> btw, benh replied. no plans of adding support in the amilo-rfkill
[14:16] <henrix> i may give it a try
[14:17] <apw> henrix, ok its 'also affects project', then near the top '(Choose another project)' and then ubuntu-release-notes
[14:18] <apw> henrix, if you want to write some proposed words you can add them in the top of the description
[14:18] <henrix> apw: i've looked at that, but then it asks for an URL
[14:18] <apw> seemed to work for me, it has a box for a url but higher up you can change the thing from linux to something else and it goes away
[14:18] <apw> the 'Choose another project' thing
[14:18] <apw> henrix, anyhow its on there now
[14:19] <henrix> apw: ah, got it! haven't seen the "choose another project" thing
[14:19] <henrix> apw: thanks, i'll add a small description to that
[14:22] <apw> henrix, put like "Release Notes:" at the top of the description bit, so it is nice and obvious
[14:27] <henrix> apw: ack
[14:43]  * ogasawara back in 20
[14:53] <henrix> tgardner: any luck reproducing the lucid bug?
[14:55] <tgardner> henrix, I have not observed the original bug to the extreme taht some of the reports have. dd times for a 4.6GB iso went from 18:57 to 18:42.
[14:55] <tgardner> so, at least it didn't regress.
[14:55] <henrix> tgardner: you tried with or without the patch?
[14:56] <tgardner> henrix, both. I'll add the info top the bug
[14:56] <tgardner> to*
[14:56] <henrix> tgardner: ok. so i guess we can just revert it, right?
[14:57] <tgardner> henrix, actually, I think we should leave it in for now. its not regressing as far as I can tell, plus it might help the folks that have affected HW
[14:57] <henrix> tgardner: ok, thanks. let me just ping bjf
[14:57] <bjf> henrix, i'm watching
[14:58] <bjf> lurking
[14:58] <henrix> bjf: yeah, i though so. just referred you name to make sure you would get the notifications :)
[14:59] <tgardner> henrix, bjf: one thing I should do is rerun with the generic kernel since I think it uses a different I/O scheduler in lucid.
[14:59] <bjf> tgardner: ack, i'm going to stare at the code a bit
[15:03] <tgardner> henrix, started the ISO copy with -generic. will let you know the outcome in 20 mins or so.
[15:04] <henrix> tgardner: ok, thanks
[15:10] <bjf> tgardner, henrix, this same patch has been in Oneiric since 3.0.0-8.10 (Aug. 5)
[15:31]  * apw might be sorta back
[15:57] <tgardner> henrix, bjf: bug #624510 marked verification-done-lucid. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/624510/comments/64
[15:57] <ubot2> Launchpad bug 624510 in linux "Copying To USB Is Very Slow" [Undecided,Fix committed] https://launchpad.net/bugs/624510
[15:57] <ubot2> Launchpad bug 624510 in linux "Copying To USB Is Very Slow" [Undecided,Fix committed]
[15:57] <bjf> tgardner: ack
[16:11] <apw> tgardner, any idea what 'tx aggregation enabled on ra = xxx:xxx:xxx:' means?  this is from an iwlwifi
[16:12] <tgardner> apw, I think is 'high throughput' aggregating packats.
[16:12] <apw> t
[16:12] <apw> tgardner, i am unsure if i am any the wiser
[16:13] <tgardner> apw, it seems like its just an informational blurb
[16:14] <sforshee> apw, it means acking a block of packets rather than each individual packet
[16:14] <apw> sforshee, oh so reducing the slots on the channel for ack use, interesting
[16:14] <tgardner> sforshee, what does it say when it aggregates multiple PDUs into one ?
[16:16] <sforshee> tgardner, who is "it"? iwlwifi?
[16:16] <tgardner> sforshee, that, or the mac802.1 stack. is there any indication that HT mode is in effect ?
[16:17] <sforshee> tgardner, I don't know that there's anything in dmesg, but I think you can query with iw
[16:27] <tgardner> apw, anymore feedback on your __ticket_spin_lock patch set ?
[16:36] <apw> tgardner, looks like henrix has also successfully tested it, so i'll ship 'em to the list so you can all weep
[16:37] <tgardner> apw, ack
[18:35]  * apw recons on getting fed ... see you tommorrow
[19:40] <tgardner> ogasawara, how do we target a bug for release noting ? See https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/969304/comments/29
[19:40] <ubot2> Launchpad bug 969304 in linux-firmware "Regression: Missing Firmware Files phanfw.bin and nx3fwct.bin (precise 12.04 beta)" [Undecided,Incomplete]
[19:40] <ogasawara> tgardner: nominate for precise and milestone for 12.04 final
[19:40] <tgardner> ogasawara, but its really an invalid bug
[19:40] <tgardner> the fix is to update the NIC BIOS
[19:41] <tgardner> I wanna make the solution gets in the release notes
[19:41] <ogasawara> tgardner: ah, there's a release notes team, lemme see if I can remember it
[19:41] <tgardner> ogasawara, apw was teaching henrix how to do it just this AM, but I wan't paying close attaention
[19:44] <tgardner> ogasawara, maybe skaet knows off-hand how to do it
[19:45] <henrix> ogasawara: just pick the "also affects project"
[19:45] <ogasawara> henrix: and then I thought it was ubuntu-release-notes?
[19:45] <henrix> ogasawara: yep, just "choose another project"
[19:45] <henrix> ogasawara: and use the ubuntu-release-notes
[19:46] <ogasawara> henrix: ah, thanks.  I was clicking "also affect distribution"
[19:46] <henrix> ogasawara: yeah, i spent some time trying to figure out how to do it
[19:46] <henrix> ogasawara: at the end apw did it for me :)
[19:47] <ogasawara> tgardner: ok, should be added
[19:47] <ogasawara> seems odd that it's not a subset of the Ubuntu project, but oh well
[19:48] <tgardner> ogasawara, hmm, so I should just add something to the comment block ?
[19:48] <ogasawara> tgardner: I usually update the bug description to contain the release notes text
[19:49] <tgardner> ogasawara, k, will do
[20:03] <tgardner> jsalisbury, looks like bug #908279 has a good reproducer and known good/bad kernel versions. since it appears to be a Precise regression, would you care to work with the reporter to bisect the kernel ?
[20:03] <ubot2> Launchpad bug 908279 in linux-lts-backport-oneiric "vm.dirty_bytes should be set to something sane" [Undecided,New] https://launchpad.net/bugs/908279
[20:03] <jsalisbury> tgardner, sure thing
[20:03] <tgardner> jsalisbury, wrong bug, see bug #980279
[20:03] <ubot2> Launchpad bug 980279 in linux "BUG: soft lockup - CPU#5 stuck for 22s! [xfce4-sensors-p:1873]; EIP is at generic_exec_single+0x66/0x80" [Medium,Triaged] https://launchpad.net/bugs/980279
[20:04]  * tgardner -> EOD
[20:04] <jsalisbury> tgardner, that is the same bug :-)
[20:05] <jsalisbury> tgardner, oops, nevermind
[20:28] <jcastro> jsalisbury: hey so you responded before I was able to report, but the last test kernel was working and only bailed on me last night, it just took way longer than usual.
[20:29] <jsalisbury> jcastro, ahh, ok.  thanks for the update.  I'll see if I can bisect further.
[20:29] <jcastro> ok should I try running the vanilla kernel like you asked?
[20:30] <jsalisbury> jcastro, it wouldn't hurt to test the lastest precise kernel
[21:58] <bjf> ogasawara: did pgraner get anywhere on that kernel hang he was getting on friday ?
[22:21] <Sarvatt> hmm i can only modinfo vesafb on i386, not amd64
[22:22] <apw> Sarvatt, that makes sense i think ... is vesa valid on 64bit ?
[22:25] <apw> Sarvatt, actually, i can do it on my 64bit system
[22:26] <Sarvatt> so just something borked on this one machine, sorry for the noise, thought it might explain why i get text splashes for the past few releases with the blobs :)
[23:07] <bryceh> would someone be able to roll a kernel build of http://cgit.freedesktop.org/~danvet/drm-intel/?h=drm-intel-next-queued?
[23:07] <bryceh> (I also emailed apw that this is apparently the new drm-intel-* branch of the month, that would be worth auto-building)