/srv/irclogs.ubuntu.com/2008/08/27/#ubuntu-kernel.txt

Zettosmb_tp, NP, i saw a lot of critical bugs assigned to Ubuntu-Kernel-Team, i know that they are working hard 00:00
smb_tpZetto, speaking of: guess I have to go shopping to get some food... ;-)00:02
Zettosmb_tp, hehehehe00:04
Zettosmb_tp, do you have a job ?00:04
smb_tpZetto, Well, look at your report ;-)00:06
Zettosmb_tp, ok :D00:07
smb_tpZetto, Gotta run. CU :)00:07
Zettosmb_tp, i and my girlfriend wanna travel to Canada someday00:10
Zettobut we still don't have enough money ^^00:11
hyperairhello there. in which kernel does intel 5100 support come in?05:45
hyperairuh whoops dc05:45
=== emma_ is now known as emma
fabbioneBenC: pull request in your inbox for gfs1 for .2709:45
lagaBenC: what's the status on aufs? :)10:03
=== n0u_ is now known as n0u
cjwatsonhey - I'm trying to figure out bug 251593, which is part of the complex of things hosing PS3 right now13:19
cjwatsonthe spufs module seems to be present in that kernel (2.6.25-1-powerpc64-smp), and as far as I was aware sys_mount ultimately ended up telling kmod to load missing modules as necessary. Nevertheless, all this seems to fail and mount says "unknown filesystem type: spufs". Does anyone know what's up?13:20
=== asac_ is now known as asac
pgranercjwatson: BenC is prob best to ask. I know he has the box in question.13:44
cjwatsonBenC: ^-13:44
hyperairdoes anyone know when iwlwifi with support for 5100 is coming?14:00
BenCcjwatson: I'll check in a bit14:05
BenChyperair: check linux-backports-modules in hardy, or latest kernel in intrepid (2.6.27, but may be a day before it's ready)14:06
hyperairi see14:06
hyperairokay14:06
hyperairBenC, linux-backports-modules contain the iwlwifi-5000-1-lbm.ucode, but not the driver that uses the ucode14:37
hyperairunless i'm mistaken about the driver name14:38
rtghyperair: at the time compat-wireless was snap shotted, I'm not sure support for the iwl 5K device was fully implemented.14:39
rtgI didn't have one to test.14:39
hyperairi see14:40
hyperairwhat's the driver name supposed to be anyway?14:40
hyperairi see an iwl4965, iwl3945, and iwlcore14:40
hyperairi don't see any other iwls14:40
hyperairbrb i'm gonna restart and see how the iwl4965 driver in lbm works14:41
hyperaircurrently my led's not working =\14:41
hyperairby the way can someone look into backporting alsa 1.0.17 to hardy? or will hardy users who have HDA intel sound cards that require the new alsa drivers just suffer until intrepid appears?14:42
rtgI'm working on a proposal to get the Intrepid kernel available in Hardy, but its gonna take awhile.14:44
hyperair_ah. iwl4965 still has the awesome kernel-panic-upon-rmmod bug14:50
hyperair_in lbm that is14:50
rtghyperair_: welcome to 2.6.26 wireless bugs14:50
hyperair_lol14:50
hyperair_will 2.6.27's modules get backported via lbm anytime soon?14:51
hyperair_i think it might be worht mentioning that the leds still don't work in lbm14:52
rtghyperair_: I doubt it. there are significant backporting difficulties. thats why I'm proposing backporting the whole kernel.14:52
rtgI'm aware of the led issues.14:52
hyperair_that'll be nice14:52
hyperair_i've noticed that my leds work in 2.6.2714:52
hyperair_the rc3 kernel that is built in kernel.ubuntu.com14:53
hyperair_however, upon resume, iwlagn causes the keyboard to lock up14:53
hyperair_only happens when there's some problem associating with an AP14:53
hyperair_something about a timeout14:53
hyperair_then the keyboard locks up and theo nly way to bring it back is to turn the HW RF Kill switch on14:53
rtghyperair_: there are still a bunch more iwlwifi fixes bubbling up, though there seems to be some flame wars in LKML about what is a fix and what is a feature wrt to iwlwifi pull requests.14:57
hyperair_lol that's interesting to see14:58
hyperair_i'll go look in the archives or something14:58
hyperair_what's the thread name?14:58
rtgRe: pull request: wireless-2.6 2008-08-2615:00
hyperair_thanks, found it15:00
=== lamont` is now known as lamont
BenCrtg, smb_tp, cking, pgraner: ping for IRC meeting17:01
pgranerBenC: ack17:02
smb_tpBenC, ack17:02
ckingBenC: ack too17:02
BenCpgraner: do you have a quick link to the contingency plan you sent earlier?17:02
pgranerBenC: Nope, still in email, I guess I can throw it up quick17:03
BenCThanks17:03
BenCzul, soren: We're discussing the 2.6.27 move and contingency plan if you're interested17:03
zulsure17:03
BenCI'm waiting to see if mdz and slangesek are interested in joining17:04
cjwatsonI noticed that we seemed to have already moved in intrepid17:04
pgranerBenC: wiki is sloooooow saving17:04
cjwatsonI've been holding off on changing the installer until we are all agreed on a plan17:05
pgraner[LINK] https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan17:05
BenCcjwatson: we have, because in order to make the move, we need to do it now...what we are discussing is the contingency and criteria for reverting back to 2.6.2617:05
cjwatsonthere's no mention of certification in the plan, which I think will be valuable input17:06
BenCcjwatson: should we get cr3 in on this now, or is there someone else that can better represent that?17:07
pgranercjwatson: good point17:07
cjwatsonI would suggest that all certification regressions need to be considered as 2.6.27 blockers unless explicitly declared to be minor17:07
cjwatsonthey're one of our best sources of hard data17:07
cjwatsonBenC: cr3 or heno could speak to it17:07
* pgraner just edited wiki for better formatting17:07
pgranerogasawara: ping, can you sit in on this meeting?17:08
ogasawarapgraner: sure17:08
cr3hi folks17:09
cjwatsonBenC: I suggest phoning mdz - he's likely to be in meetings with the LP folks today17:09
pgranercjwatson: he is in a meeting for the next 90min I just talked to him17:09
BenCI'll be sure to post the log to him afterwards17:09
pgranercr3: can you read  [LINK] https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan17:10
BenCcr3: Thanks...we're interested on what can be done to speed up certification/regression testing with a 2.6.27 based intrepid image?17:10
pgranercr3: we need to cover cert in this plan17:10
BenCcr3: This is quite important since cert is the most reliable testing for us right now17:11
cr3BenC: I spoke with heno this morning and I could start delivering more comprehensive testing as of next week17:11
cjwatsoncr3: I've been assuming that you'll need stock ISOs built with 2.6.27 (i.e. installer and linux-meta switched over) before you can realistically do a certification pass; is this true?17:11
BenCcjwatson: When's the soonest we could get ISO's with 2.6.27 on them if I upload linux-meta today?17:11
* BenC converges on cjwatson's thoughts17:12
cr3cjwatson: if the kernel is available somewhere, it might be possible to have it installed outside the iso17:13
BenCcjwatson: note that lrm for 2.6.27 is built and needs to be NEW'd17:13
cr3I would really want to perform the extensive testing from next week on .26 and then on .27, just to compare the results. I should have results for both ltp and autotest17:14
cjwatsonBenC: tomorrow17:14
cr3Ideally, I should do that today, but my code is just not ready :(17:14
cjwatsoncr3: can you do testing without an installer image?17:14
cjwatsonit's going to be a little difficult to get parallel images with .26 and .2717:15
cr3cjwatson: I could use a prior installer image and perform post-installation steps if necessary, to install .27 for example17:16
cr3cjwatson: right, I wouldn't expect parallel images with .26 and .27 either17:16
cjwatsonyou wouldn't get verification of whether the installer still works, but you'd get some of it17:16
BenCI'd like to see installer images17:16
BenCcompcache+aufs+squashfs testing is important to me17:17
cjwatsoncould we just compare alpha 4 to alpha 5?17:17
BenCMainly because of some VFS changes I had to port them for17:17
cr3cjwatson: where alpha 5 would use .27, right?17:17
BenCcjwatson: Yeah, that's fine with me17:17
cjwatsonon the assumption that we will be able to identify userspace regressions17:17
BenCcr3 is smart enough to separate installer/userspace bugs from kernel ones17:17
cjwatsoncr3: right - or preferably an earlier milestone if we can identify one that works17:17
cr3cjwatson: my intention is to run the full suite from next week on alpha 4 again in order to have data to compare against 5, so I should be able to identify regressions that way17:18
cjwatsonthat sounds good17:18
BenCcr3: Can we have a hard date from you for results?17:18
BenCI know it may be difficult to estimate, but we have some serious time constaints17:19
cjwatsonBenC: lrm 2.6.27 processed17:19
cr3BenC: one of heno's concern is my reporting, which is not very strong right now. worst case, you might have to query a database dump17:19
BenCcjwatson: Thanks, meta coming up then17:19
cr3BenC: results for alpha 5? at least some should be made available 24 hours after release17:20
BenCcr3: as long as we have some discernible data to look at17:20
pgranercr3: define query a db dump?17:20
cr3BenC: yeah, the data is all there, just getting reports out of it is lagging behind17:20
pgranercr3: do we see pass/fail by subsystem? component level? a mix?17:21
cr3pgraner: if the reports on the web site are not sufficient, I might have to pg_dump my database and make it available for running sql queries against it. that's assuming the reports aren't sufficient and can't be improved in reasonable time17:21
cjwatsonBenC: once we upgrade -meta, if we have to go back to .26, how will we get the newer kernel off testers' systems so that we don't end up with divided testing effort17:21
cr3pgraner: you at least see pass/fail per build and per system17:21
BenCcr3: basically we just need to compare pass/fail from one set to the next and verify that it was caused by a kernel issue17:22
pgranercr3: ack ... do you have a pointer to the web page as an example that would go along way to knowing what to expect17:22
cr3pgraner: someone is working full time on improving the reports but he's on vacation right now17:22
pgranercr3: can you show us what you have today?17:23
BenCcjwatson: linux-meta uploaded17:23
cr3pgraner: sure, I'll send you an invitation to access the site17:24
pgranercr3: great thx17:24
BenCOk, as far as known regressions...17:24
BenCSubject: 2.6.27-rc4-git1: Reported regressions from 2.6.2617:24
BenCthat's on lkml...I've been going through the list...it's very tedious17:25
BenCSo far I have identified ~8 regressions that may pertain to us17:25
cr3BenC: regarding comparing pass/fail from one "set" to the next, "set" being a build?17:25
BenCthe rest of the bugs are either on non-x86, outside the scope of our configs (we don't enable things that cause the bugs) or they were present in 2.6.26 as well17:26
pgranerBenC: is that this list? http://bugzilla.kernel.org/showdependencytree.cgi?id=11167&hide_resolved=117:26
BenCcr3: set being a system17:26
BenCpgraner: looks very similar17:26
BenCpgraner: that list may be more up-to-date as well, so I'll cross check against it17:26
pgranerBenC: I went thru that yesterday and most were not critical as you say due to config options and the like17:27
BenCThe ones I've payed attention to aren't critical, but I want to investigate them further to make sure we get full descriptions of what we may have to handle17:27
BenCor things we can look into fixing ourselves17:28
BenCpgraner: Are you adding that link to the wiki?17:28
cr3BenC: ideally, you would probably want to see that for a bunch of systems at once, right?17:28
pgranerBenC: ACK done17:28
BenCcr3: right17:28
BenCpgraner: thanks...that's much easier than the email thread I was looking at17:29
cr3BenC: what would the columns and rows look like? I'm imagining the first column would contain the system name, where each row would be an individual system. not sure about the subsequent columns though17:29
BenCcr3: each row would be a system with columns being doubled for each test (with pass/fail for alpha4/alpha5 shown for each test)17:30
BenCcr3: mainly we only want to see the ones where there is a pass for alpha4 and a fail for alpha517:30
cr3BenC: ok, I would like to follow up after this discussion by email with you and pgraner to make sure we at least have that kind of report straight17:30
pgranercr3: ack17:31
BenCcr3: knowing which ones are fail/pass for alpha4/alpha5 would be nice to, so we can see what we're fixing :)17:31
BenCcr3: thanks17:31
cr3BenC: well, I can't make a report specific just for this corner case of a new kernel but hopefully something generic which could be reused across releases17:31
cr3pgraner: problem?17:31
pgranercr3: nope17:32
BenCcr3: I would have thought that comparing fail/pass between test runs was a normal reporting output17:32
BenCcr3: ACK == "ok, noted"17:32
BenCcr3: but we can discuss this more through email17:33
cr3BenC: the problem is that not all systems necessarily have a test run each day, and some systems might have multiple runs the same day. the problem is that when you display multiple systems at once, it doesn't always make sense to have columns per date but perhaps per build or milestone might make sense.17:33
cr3BenC: or phone17:33
BenCcjwatson: There are some things that need to be contended with from userspace....one of the main ones is alsa userspace and pulseaudio to get the benefits of 1.0.17 alsa drivers17:34
cr3per build or per milestone would be awesome actually, I could finally determine which systems have been neglected!17:34
BenCcjwatson: it's not required mind you, but the benefits will be lost without syncing those17:34
cr3BenC: actually, I think I have a good idea for the report now. I'll build something this week and ping you when done17:35
devfil_hi to all, there is a chance to include compcache (http://code.google.com/p/compcache/) to ubuntu kernel? it seems to be good (but I don't know nothing about how a kernel work, so at your choice :))17:35
BenCcr3: great thanks17:35
BenCdevfil_: already there, thanks17:35
BenCcjwatson: do you forsee any issues in syncing alsa/pulseaudio?17:35
devfil_BenC: in what kernel version?17:35
BenCdevfil_: intrepid17:36
devfil_BenC: wow, really good thing :)17:36
shenkianother reason to not run .26, no more compat wireless backports: http://marc.info/?l=linux-wireless&m=121977672215224&w=217:37
BenCshenki: nice point, but sucks for hardy :/17:38
BenCrtg: you can add that to your reasons for trying to get 2.6.27 into hardy though :)17:38
shenkiyeah, poor hardy. no 80211n for you17:38
pgranerBenC: rtg's proposal look more attractive huh?17:38
lukehasnonameHardy doesn't have wireless N support?17:39
BenCpgraner: definitely17:39
lukehasnonameyou learn something every day17:39
* BenC wonders if cjwatson caught the underground home already17:39
shenkilukehasnoname: not with intel atleast17:39
BenClukehasnoname: it's supports 11n chipsets, but not 11n itself17:39
cjwatsonBenC: I'm at home17:39
BenCcjwatson: ah :)17:40
lukehasnoname:( Well then... looks like I have one more reason to move to Intrepid17:40
cjwatsonBenC: I believe new pulseaudio still needs a bit of TLC before we add it, though folks in the know seem generally keen17:40
cjwatson00:43 <TheMuso> As now 2.6.27 is in/going into the archive, I now have to get alsa 1.0.17 in before FF.17:40
cjwatson00:49 <cjwatson> TheMuso: I don't think 2.6.27 is settled yet17:40
cjwatson00:49 <TheMuso> cjwatson: oh ok.17:40
cjwatson00:51 <TheMuso> then I'll hold off on my uploads then...17:40
cjwatson00:54 <cjwatson> hmm, though it does look like linux is at 2.6.27 now17:40
cjwatson00:54 <cjwatson> but the discussion with mdz on ubuntu-devel didn't seem to reach a clear conclusion17:40
cjwatson00:54 <cjwatson> I'd say put the alsa (and pulseaudio?) packages in a PPA for now so that we can try them out with 2.6.2717:40
BenCcjwatson: I noticed before we did this there were a lot of complaints about not having 1.017 alsa so that pulseaudio could be updated to fix a lot of bugs17:40
cjwatson00:54 <TheMuso> Yeah I gathered. I'll wait.17:41
cjwatson00:55 <TheMuso> Yep I'll do that once my dmraid work is done.17:41
BenCcjwatson: It's important to note that even if we revert back to 2.6.26, unless the regressions are because of alsa 1.0.17, we'll be moving 2.6.26 to alsa-1.0.17 anyway17:42
BenCcjwatson: so moving to new alsa userspace and pulseaudio should be done regardless17:42
cjwatsonhow intrusive is that?17:42
BenCcjwatson: we'll be taking 2.6.27's entire sound/ and include/sound/ directories into 2.6.2617:42
cjwatsonit's reassuring that we wouldn't have to roll back alsa, since rolling back libraries is always fraught with pain17:42
BenCcjwatson: that was our plan before moving to 2.6.26 anyway17:43
BenC*2.6.2717:43
pgranerBenC: Can you summarize where we are for the record with AI's17:43
BenCcjwatson: I went to the trouble of doing this before we switched to 2.6.27, and the compile and build of it went fine17:43
BenCpgraner: AI's?17:43
pgranerBenC: Action Items17:44
BenCACTION: TheMuso: move to alsa 1.0.17, new pulseaudio17:44
BenCACTION: BenC: summarize known regressions in 2.6.27/2.6.26 move17:44
BenCACTION: cr3: Setup call/email thread with BenC and pgraner to discuss cert testing and reporting between alpha4/alpha517:45
smb_tpOn email cc: kernel-team?17:45
pgranersmb_tp: good point17:46
BenCessentially, if there are regressions in 1.0.17 alsa, we will have to work to fix them, because reverting to 2.6.26 will cause more pain17:46
BenCpgraner: that's probably worth noting on the plan17:46
BenCwhich shouldn't be much trouble because we have all kinds of hardware to reproduce and fix bugs in alsa (IOW, snd-hda)17:47
pgranerBenC: Have you talked to davej at Fedora to see where they currently sit with 2.6.27 and see if we could attack different problems so we don't duplicate effort?17:47
BenCpgraner: No, but that's a good idea...opensuse and fedora are both going with 2.6.27, so would be good to coordinate17:47
pgranerBenC: do yo know davej? If not I could do an into for you17:48
BenCACTION: BenC to contact opensuse and fedora kernel devs to improve efforts17:48
BenCpgraner: I believe davej introduced himself quite rudely on my blog :)17:48
cr3pgraner: invitation sent and follow up email17:48
cr3BenC: ^^^ copied you to give an idea of my report17:48
BenCbut I may be thinking of another dave*17:49
cr3you can both expect a ping from me this week17:49
BenCcr3: thanks17:49
pgranerpgraner: I'll send an into email, and no your correct same davej17:49
pgraners/pgraner/BenC/17:49
* pgraner needs food17:49
BenCpgraner: I knew it was only a matter of time before this job drove you mad17:49
* pgraner is talking to myslef17:49
BenCpgraner: file an expense report for the psych visits and meds :)17:50
pgranerHas everyone read the page and agree in principal to the plan? Do we need to tweak dates?17:50
pgranerBenC: I can see mdz looking at the now... hehe17:50
ogasawarapgraner: we might want to change the first call for testing date - it'll likely happen before the 2nd17:51
BenCYeah, I plan sending out a CFT today as a matter of fact17:51
pgranerogasawara: just edit and set when you think is appropriate 17:51
BenCto -devel-announce, -devel and blog17:51
pgranerBenC: Coordinate that with ogasawara so we don't send multiple msgs17:51
lukehasnonamewhat's CFT?17:51
pgranerlukehasnoname: Call For Testing17:52
lukehasnonamethanks.17:52
ogasawaraBenC: I'll wait for the announcement to hit the ml, then spam the bug report17:52
BenCogasawara: Ok17:52
zulpgraner: yep read it17:52
BenCACTION: BenC to send out CFT17:54
BenCACTION: ogasawara to follow up with bug report requests to update to 2.6.27-1 and test17:54
pgranerBenC: Also grab this log and link to the page as well for background and reference17:55
BenCACTION: BenC to grab IRC log and link wiki plan to it17:56
pgranerBenC: I have to jump off, I'll check to log and will circle back with you in and hour or so.17:56
BenCpgraner: Ok, I think we are pretty much done17:57
=== pgraner is now known as pgraner_afk
BenCAnyone have anything to add?17:57
zulwhat about pending patches for 2.6.27?17:58
BenCzul: we'll try to get those in before alpha5...I want to try to keep the tree is pristine as possible though so we don't mix regressions we introduced with ones that came from external patching17:59
BenCI'd hate to revert to 2.6.26 just because a xen64 patch fubar'd everything :)18:00
zulBenC: heh it should only affect xen when its enabled18:00
zulbut thats fine18:00
BenCOk, then let's call this done, and get to work :)18:02
ubunubiis compiling the kernel from linux-source package broken? every machine I've tried it on errors with *** No rule to make target `arch/x86/kernel/asm-offsets.c', needed by `arch/x86/kernel/asm-offsets.s'.  Stop.18:15
rtgubunubi: https://wiki.ubuntu.com/KernelMaintenance18:22
ubunubirtg: why is the linux-source package still put in the repos if it's no longer maintained for building kernels?18:25
rtgubunubi: if course it is maintained. in fact, its generated from the sources in the git repo. Once you have 'apt-get source ...' then run 'debuild -b' to generate the binary packages.18:27
rtgalternatively, chewckout the sources using git, then build the same way.18:27
ubunubirtg: sorry i meant kernel-package18:27
ubunubirtg: i just want to recompile my current (2.6.24-19-generic) with PAE enabled. all the guides I can find online are using (apprently the old fakeroot make-kpkg way)18:28
rtgubunubi: now that I couldn't tell you. I've never used kernel-package.18:29
ubunubirtg: do you know of a decent tutorial using your method, for compiling with pae? all kernel compiling howto's are super old (7.10 and older)18:31
mdzBenC,pgraner: I just got off my last call of the day. what did I miss?18:31
rtgubunubi: I beg to differ. the instructions in  https://wiki.ubuntu.com/KernelMaintenance are current as of 2.6.2618:32
ubunubirtg: that's hardly a tutortial. doesn't show how to adjust any individual build options etc, like enabling/disabling custom options (like pae) ...like  make menuconfig did for the old method18:34
rtgubunubi: try 'debian/rules editconfigs'18:35
ubunubirtg: k thanks will give it a try18:35
BenCmdz: I'll have a log posted soon18:36
BenCmdz: we have a complete plan in place with some action items...cr3 and cjwatson were in the meeting18:36
BenCmdz: rookery:~bcollins/kernel-team-irc-log.txt if you want a quick look18:37
BenCmdz: you can "grep ACTION" as well18:38
mdzBenC: thanks, will review18:39
=== pgraner_afk is now known as pgraner
tormodbenc, I think our beloved prism2 drivers need some patching for 2.6.2719:17
=== emma_ is now known as emma
=== emgent` is now known as emgent
BenCtormod: they seem to compile fine...is there a runtime problem?19:38
tormodBenC:  I haven't tested, but this is in upstream git: http://git.shaftnet.org/git/gitweb.cgi?p=linux-wlan-ng.git;a=commitdiff;h=0b9426b9e7bfdd838b1f0a3e2a4ed8a8fc95ebf719:40
tormodand this: http://lists.linux-wlan.com/pipermail/linux-wlan-devel/2008-August/003861.html19:40
tormodBenC: I can test it if I get some i386 builds but I guess it will take some time before it's out?19:42
BenCtormod: I already have that done in our tree (else it wouldn't have compiled :)19:50
tormodBenC: good. you updated BOM then? :)19:51
BenCtormod: doubtful, but I did update the commit log19:54
tormodBenC: I can not see that from http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=history;f=ubuntu/misc/wireless;hb=HEAD ?19:56
BenCtormod: it's not a separate commit...check the actual code, it's there20:04
lagaBenC: can i pretty please get a status update on aufs?20:07
BenClaga: basically while moving to 2.6.27 I don't want to introduce anything yet that wasn't in the last 2.6.26 upload so we can more easily track regressions20:12
BenClaga: once alpha5 is out I'll include your aufs update20:12
lagaBenC: thanks. consider yourself hugged. 20:12
tormodBenC: I am just nitpicking about this because last time we updated the drivers from upstream it was not clear that the Ubuntu code had some needed changes of its own. And this commit log looks like a copy of an older commit although you changed a few things... But as long as you keep track of it yourself, it's not my business :)20:13
BenCtormod: I should have updated the BOM...I'll make sure to add the notes in later20:14
BenClaga: consider yourself thanked for doing the work :)20:14
* BenC => rebooting20:47
nixternalok kernel freaks, gotta a good one for you...found it once via google weeks back, but now I can't21:23
nixternalsetting up hot-swap (SATA) on a server I have21:23
nixternalcurrent setup is /dev/sda /dev/sdb /dev/sdc /dev/sdd21:24
nixternalif I pull out /dev/sdc the kernel does what it is supposed to do and performs a check every 5 seconds for drive insertion21:24
nixternalso, if I insert the same drive or a new drive back in the same slot, it doesn't come back as /dev/sdc, it comes back as /dev/sde21:24
nixternal2.6.24 kernel21:25
nixternalI thought I read about a fix somewhere a few months ago, but I do not remember21:25
CarlFKtrying to install .27 - "nvidia (177.68): Installing module.  Kernel source for 2.6.27-1-generic not installed.  Cannot install this module. [fail]"  http://dpaste.com/74302/21:37
CarlFKshould I file that on lp?21:37
CarlFKhow do I turn off # defoptions=quiet splash 21:39
CarlFKI tried ##, and I get "file has been modifed... [x] use maintiners version  [ ]merge?  [ ]leave alone.." which seems to revert it back to one #21:40
pwnguinits a config file22:07
pwnguindebconf will notice it's been changed when upgrades, and notifies you22:07
CarlFKpwnguin: so how should I answer the "what you want to do?" 22:18
pwnguinnot sure22:18
pwnguinI'd do a merge22:18
CarlFKill try that next time 22:18
pwnguinbut that means you'd have to know whether changes are relevant22:18
cr3lspci question: why does lspci -vvv return nvidiafb as value for Kernel modules whereas this value does not appear in lsmod nor in /var/log/Xorg.0.log22:23

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