[00:12] <dtchen> sorry about the bug spam, folks. I can't really prevent people from filing bugs clearly caused by the grub configuration not being properly updated.
[02:40] <EbolaVirus> !ops
[02:40] <ubot3> Help! lamont, zul, T-Bone, mdz, or jdub
[02:41] <EbolaVirus> !ops
[02:41] <ubot3> Help! lamont, zul, T-Bone, mdz, or jdub
[02:42] <dtchen> um, what do you need?
[02:42] <EbolaVirus> ban me 
[02:42] <dtchen> why don't you just /part ?
[02:42] <EbolaVirus> why not ban me
[02:42] <dtchen> sigh, /ignore
[03:16] <eggonlea_> hi guys, I read https://help.ubuntu.com/community/Kernel/Compile but am still a bit confused about how to update config files. After "make menuconfig", how to merge what I changed in .config to debian/config? I saw /debian/config/config.common and debian/config/ARCH/config.xxx. Should I manually modify all files in /debian/config or replace them with the new .config?
[03:17] <eggonlea_> which way is recommended to change them? Thanks!
[03:43] <eggonlea_> [answer my own question] found it. just copy .config to either debian/config/xxx and run debian/rules updateconfigs and then Mr. Proper.
[03:44] <eggonlea_> maybe the wiki need update a little bit to clarify this "copy" step. I saw lots of guys asking the same question in LP and other maillist. :)
[03:45] <lifeless> eggonlea_: its a wiki, you can do that
[08:55] <apw> smb, did we get any testing feedback on the -virtual kernel issues?
[08:55] <smb> apw, Yes, luckily even good ones
[08:57] <smb> I guess the plan is to prepare and push everything for upload and then plan for it being up Thursday
[08:57] <smb> apw, ^
[09:04] <apw> smb, yeah sounds about right.  we should consider the m586_tsc thing too
[09:05] <smb> apw, Oh, ok. So I probably should delay the finalizing commit to the kernel to get that in as well
[09:05] <apw> i guess it could go in with the stables ... as noone has yet mentioned it
[09:08] <smb> apw, Right. it would be slightly more preferable to stay with the current finalized version. At least for non-lava issues
[09:08] <apw> smb, then that sounds like a plan
[09:09] <smb> apw, ack
[09:10] <indus> hei all 
[09:10] <amitk> hehe, I like that term: non-lava issue. (assuming it wasn't a typo)
[09:10] <indus> hi i need some help, can someone oblige
[09:11] <smb> amitk, no I meant anything that is not melting and very hot
[09:11] <indus> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/425756
[09:11] <ubot3> Malone bug 425756 in linux "[regression karmic] cd/dvd drive not detected" [Medium,Triaged] 
[09:12] <amitk> smb: yeah, thats what I thought. I propose we change our bugs from critical to lava and non-lava
[09:12] <amitk> :)
[09:13] <smb> amitk, It would be a nice change :)
[09:15] <smb> indus, I am not sure there is any advice that can be quickly given. The report seems to cover potentially various issues. I believe to remember something about detection in CDs but it might be different too. apw, do you have more recollection there?
[09:16] <apw> smb, i was just reading same, and i concur there is nothing easy to follow in there.  i thought some cd stuff was improved generally but clearly not fixing this person
[09:16] <indus> smb: hmm, sorry i dont quite understand 
[09:16] <apw> indus, what are your symptoms?
[09:16] <smb> indus, And in your case since when (Jaunty, or before)?
[09:17] <apw> yep, when did it last work
[09:17] <indus> ok once i put in the live cd, the cd reaches menu for booting ubuntu etc , then when i select 'try ubuntu without change to your computer' it starts looking at HDD instead of cd drive and later fails with initramfs
[09:17] <indus> it last worked in Hardy heron
[09:18] <indus> once i used some boot options pci=nomsi, rootdelay bla bla etcand it worked once to twice but no idea what it does
[09:18] <indus> works in hardy nicely
[09:18] <apw> i am not sure if that is the same bug or not, the bug referenced implies a normal boot without cd
[09:18] <smb> I'd suspect something with libata, as that was one of the major changes after hardy
[09:19] <apw> so ... i would recommend getting a new personal bug filed with the machine info on it
[09:19] <apw> and try and get a picture of the failure into initramfs
[09:19] <indus> apw: yeah the bug is normal boot, but live cd also doesnt work, i instaleld it with usb
[09:19] <apw> and a dmesg output from there if you can get it
[09:19] <apw> ...
[09:19] <indus> wait i give you another live cd bug
[09:19] <indus> i have one for casper intrepid
[09:19] <apw> ok if you have a normal boot without CD then what is in the dmesg when it fails
[09:20] <indus> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/425756
[09:20] <ubot3> Malone bug 425756 in linux "[regression karmic] cd/dvd drive not detected" [Medium,Triaged] 
[09:20] <indus> no no sorry
[09:20] <indus> wait'
[09:20] <indus> https://bugs.launchpad.net/ubuntu/+source/casper/+bug/303654
[09:20] <ubot3> Malone bug 303654 in casper "[intrepid] Live CD cannot mount - panic Unable to find a medium containing a live file system" [High,Triaged] 
[09:21] <indus> apw: dmesg says, and also at boot i have a message , libata1 soft reset failed , expecting a reference package element, device not ready
[09:22] <smb> one problem might be related to rootdelay, I remember there had been issues with waiting long enough for the root fs in some cases. But together with the other behaviour it might be ata related
[09:22] <apw> so we need to get that log element into the bug so we can see its exact form
[09:22] <smb> right
[09:22] <apw> also we need to know the exact hardware you have both mobo / disk interface / drive
[09:22] <indus> dmesg 3.972516] ata1: softreset failed (device not ready)
[09:22] <indus> [    3.972519] ata1: failed due to HW bug, retry pmp=0
[09:23] <indus> asus M2A VM motherboard amd 690 g chipset / sata HDD /IDE samsung combo drive
[09:23] <smb> I would say booting with an usb-cdrom and replacing "quiet splash" with "debug" on the grub line, and then posting the whole dmesg (maybe try to access the internal drive too)
[09:23] <indus> smb: i dont have usb cd rom :)
[09:24] <indus> if i couldget some kernel parameters to boot , i could try 
[09:24] <indus> rootdelay , so many things i had tried
[09:24] <indus> but its a hit and miss mostly
[09:24] <smb> indus, was something with all_generic_ide amongst those
[09:24] <indus> smb: of course , but it doesnt work always
[09:25] <indus> i tried it too
[09:25] <indus> its like, instead of reading the cd drive, it reads from HDD 
[09:25] <indus> hdd light stays on after cd boots from menu
[09:25] <smb> indus, How did you say you secceeded booting? From a usb stick?
[09:25] <indus> smb: yeah 
[09:26] <indus> flash 
[09:26] <apw> if the cd is missing then its not unlikely it falls back to the hdd
[09:26] <indus> no , cd is present when live cd boot i use
[09:26] <indus> it boots from cd, but once i press menu options, it starts reading HDD
[09:26] <apw> not to the kernel its not is it ... else you'd not be reportng a missing cd dirve
[09:26] <smb> Ok, if you do that again and get up (with using the debug line), then gather dmesg, cat /proc/interrupts
[09:26] <indus> ya ok
[09:27] <indus> kernel cant see or tries to look in wrong location i believe
[09:27] <indus> smb: hmm what do i need to do?
[09:27] <indus> smb: you saw that bug report, i have dmesg in there
[09:27] <indus> its with the live cd , also have casper.log
[09:28] <smb> indus, you boot from the usb stick, then on the boot menu you would go to advanced options and edit the line to remove splash and quiet and put debug there instead
[09:28] <smb> then boot the live image
[09:28] <indus> smb: ok and ? but with usb it boots fine.
[09:28] <apw> indus, ok where is your dmesg, the one in the bug you first referenced does not have your message in it
[09:29] <indus> apw: wait which dmesg you need, normal boot or live cd?
[09:29] <smb> indus, still it would try to access your cd and hdd and the errors should be there
[09:29] <indus> smb: here is dmesg from live cd intrepid http://launchpadlibrarian.net/34279545/dmesg.txt
[09:29] <apw> as the problem is likely the same i am not sure it matters.  debugging on your booted system is probabally easier i'd assume
[09:30] <indus> http://launchpadlibrarian.net/34279424/casper.log  this is casper
[09:30] <apw> indus, that dmesg is from a .27 kernel
[09:31] <indus> apw: yeah have had the problem since 
[09:31] <indus> apw: ill give you karmic dmesg then
[09:32] <indus> apw: http://launchpadlibrarian.net/31444487/BootDmesg.txt
[09:32] <smb> which is also a bit outdated
[09:33] <indus> aah ok
[09:33] <indus> so you need the current kernel
[09:33] <smb> indus, Have you tried with the release version?
[09:33] <indus> smb: of course, iam fully updated to release
[09:34] <indus> basically, as i stated earrlier, hasnt worked in any kernel after hardy 8.04
[09:34] <smb> indus, Just the log you had was from 2.6.31-9. And at the current point, when looking at the problem it helps to start of as recent as possible
[09:34] <indus> aah damn it, iam at work now
[09:34] <indus> diff system
[09:35] <indus> ill give you dmesg with latest one in evening then
[09:35] <indus> anyother way i could get cd rom to be read?
[09:35] <indus> temporary solutions
[09:36] <indus> secondly, i have a general question about multi threaded applications
[09:36] <indus> nvm
[09:37] <apw> oh so this sm600 system isn't the right one
[09:37] <indus> apw: ?
[09:38] <apw> nothing springs to mind without knowing more about it.  a current dmesg can't hurt and if you have a dmesg from hardy that might be useful to se ehow it was recognised in that kernel
[09:38] <smb> indus, Sure. And with those kind of problems, it also helps when we have a good summary on how things are connected (should the drives be on the sata port, or ata, are the sata ports set to ahci or ide) all that stuff. Thought info can be found in the dmesg it is slower to gather it manually.
[09:38] <indus> smb: in bios its set to ide controller
[09:39] <apw> i interepreted what you suggested there as saying the second dmesg is not from the system
[09:39] <indus> smb: HDD is on sata port
[09:39] <indus> apw: no no all were filed from my system, iam just chatting with you from work system
[09:39] <smb> indus, from the log it seems ahci is firing up
[09:39] <indus> smb: hmm i must have fiddled iwth bios settings that time
[09:40] <indus> smb: but itsdefault on ide controller,there are 2 other options raid and ihce
[09:40] <indus> but i use ide 
[09:40] <indus> also, the cd drive is connected with this wide and thin cable , which ironically says 'asus HDD cable'
[09:40] <indus> i believe its ide cable
[09:41] <smb> indus, Ok, so this is all stuff that we should have in the bug report. The better we know how things should be, the better one can spot differences.
[09:42] <indus> smb: hmm where do i add it
[09:42] <indus> smb: apw ill try to give you a 8.04 dmesg, and ill attach it today
[09:42] <smb> indus, You either edit the description section of you bug or add a comment with it
[09:42] <indus> smb: ok
[09:43] <indus> but is that really necessary? 8.04, man ill have to install it and all that
[09:43] <indus> just reinstalled 9.04 a few days ago
[09:43] <apw> indus, you could boot the livecd for 8.04 and take it from there
[09:43] <indus> wait let me get an old bug with hardy then
[09:43] <apw> as the cd works in 8.04
[09:43] <indus> apw: hmm , from live cd when it boots into desktop?
[09:44] <apw> yep ... it must have detected and used the CD
[09:44] <indus> yes ok ill surely do that today, 
[09:44] <indus> apw: so from a terminal i type dmesg and paste it there in report?
[09:45] <indus> i mean, no need to install right?
[09:45] <smb> indus, you actually should have network from the live cd and could add it to the bug report
[09:45] <smb> indus, No need to install
[09:45] <indus> smb: ya i know, i have network, ill add it
[09:45] <smb> Its just to get a dmesg from a working case as compared to a non-working
[09:45] <indus> let me see if i can do this in an hour or so
[09:46] <indus> so i have a question,is the kernel in C?
[09:48] <apw> the majority of the kernel is in C yes
[09:49] <indus> apw: smb i have an ubuntu 8.04.1 cd , is that ok?
[09:49] <apw> if the cd works yes
[09:50] <smb> what apw says
[09:50] <indus> also one more important thing here, some peopel had this problem befoer hardy and some patch fixed it, so it fixed for some and broke for me
[09:50] <indus> not sure if its related though
[09:51] <indus> nvm
[09:51] <indus> ill brb and upload dmesg
[09:51] <indus> 5 min
[09:52] <apw> indus, i note that your karmic kernel is an old one 2.6.31-9.29 ... the current one is -14.28 or so
[09:54] <smb> apw, Not sure about the .28 but certainly -14
[09:55] <smb> -14.48 I would guess
[09:55] <apw> doh ... typo
[10:21] <indus> ok got the dmesg
[10:22] <indus> apw: i attached the kernel
[10:27] <indus> its ATAPI cd drive , is that different from ide
[10:27] <indus> guys are you there? smb apw
[10:28] <smb> indus, yes. not so much difference that it should not work
[10:29] <indus> so now what :)
[10:29] <smb> indus, you happen to know whether the cd driver is specifically set to master or slave?
[10:30] <indus> smb: ooh dont remember, wait i came back to office now, :)
[10:30] <indus> smb: slave i think though
[10:30] <indus> smb: isnt it in the bios post screen?
[10:30] <smb> and exactly where has the dmesg gone?
[10:30] <indus> smb: dmesg i attached to bug report
[10:30] <smb> indus, you added to the first or second bug
[10:31] <indus> smb: hmm karmic bug report
[10:31] <smb> indus, ok
[10:31] <smb> indus, And the drive definitely should be set to master
[10:31] <indus> smb: hmm ok how do i do that
[10:31] <smb> it is the only drive on the pata bus
[10:32] <smb> I would not know except by opening the case and look at the drive
[10:32] <smb> in theory there should be a selector
[10:33] <apw> sometimes its cable select, so it depends which connector on the cable its connected to
[10:33] <apw> smb, how did you tell it was a slave from the dmesg?
[10:33] <smb> apw, No I am working on indus statement atm
[10:34] <smb> I have not got to the dmesg itself yet
[10:34] <apw> i had the feeling it was a slave too, and am wondering what i saw to trigger that
[10:34] <smb> if that is visible there anyways
[10:35]  * smb wonders whether it would be visible in the bios. maybe, depending on how good/bad that is
[10:36]  * apw shakes his head at all the 'sb600' needs workaround messages in the karmic dmesg ... a lemon of a machine i recon
[10:36] <indus> i think its visible in my bios , i remember the words
[10:37] <indus> its a beautiful chipset actually :) onboard graphics are really good
[10:37] <indus> in the first post messages, it mentions HDD first ,then cd drive is probably slave , ugh i dont really remember
[10:38] <indus> apw: its a 1 mm thin 5 cm wide cable connected to mobo
[10:38] <smb> Well, as your hdd is sata that would be different worlds
[10:38] <indus> ya hdd is sata sure, so no master slave business
[10:39] <smb> the cable might provide cable select ability but this needs to be supported by the drive
[10:39] <indus> cable select, its a simple cable,a wire
[10:39] <apw> [    1.000067] ata5.01: NODEV after polling detection
[10:40] <apw> smb, looking at other messages i think that that can be .00 and .01 and .01 is slave
[10:40] <apw> (this is from karmic dmesg)
[10:40] <smb> indus, its one of the cables deliberatly broken after one of the connectors
[10:40] <indus> smb: sorry i dont know this one
[10:41] <apw> there were some changes in the final karmic kernel to handle better selection of speeds for pata disks ... speed of the io over the cable. which might be related to the issue
[10:41] <smb> So there might be disagreement between controller, cable and drive what should be master and slave
[10:41] <indus> aah internal fighting :)
[10:42] <apw> i wish they documented what these damn messages really are meant to mean for humans
[10:43] <smb> apw, Also the dmesg of hardy shows the cdrom as hdb (which would be another indicator of it being slave)
[10:43] <indus> yeah hdb 
[10:43] <indus> i noticed
[10:43] <apw> yeah smb i think thats pretty definative... though that means it can work
[10:43] <apw> and i think the .01 failure indicates it found something on the cable and rejected it as a broken thing
[10:44] <indus> where is this .01? in 8.04 dmesg? or new one
[10:44] <smb> indus, yes that was in the new dmesgs
[10:45] <indus> hmm which line is this? lots of .01, just interested in knowing
[10:45] <apw> [    1.000067] ata5.01: NODEV after polling detection 
[10:45] <apw> pretty sure ata1-4 are your sata ports and ata5-6 are your pata ports
[10:45] <apw> i think the .01 can be .00 and .01 and i think they are master and slave indicators in this context
[10:46] <apw> not yet confirmed that but it seems more than conincidental that is emmitted
[10:46] <apw> and that message means 'i talked to it and it was junk so i am ignoring it'
[10:47] <smb> indus, What I would suggest, when you get home. Try taking out the drive and check, whether it can be manually set to master or slave. I would suspect it can, as you said you use the hdd cable and probably the last connector (leaving the middle one free) and I believe those are wired to set cable select capable drives to master
[10:47] <indus> smb: i think it can be
[10:47] <indus> smb: some jumper settings which iam a little scaredof
[10:48] <apw> i note that the bios is setting the drive to pio mode in the hardy dump, and the NODEV message in karmic is sometihng which can only be emitted in ATA PIO mode:
[10:48] <smb> hopefully documented on the drive and not in the documentation one usually discards quite soon
[10:48] <apw>                                         /* If diagnostic failed and this is
[10:48] <apw>                                          * IDENTIFY, it's likely a phantom
[10:48] <apw>                                          * device.  Mark hint.
[10:49] <apw> so its very likely that line indicates that the drive is being dropped as it failed to respond appropriatly
[10:49] <apw> for some definition of appropriatly
[10:50] <indus> smb: hmm there is a connector in the middle of cable you mean? hmm i will check this 
[10:51] <indus> smb: http://www.cksinfo.com/clipart/electronics/computers/cables/ide-cable.png 
[10:51] <indus> this one?
[10:51] <smb> indus, those ata flat cable connectors I know usually have three connectors...
[10:51] <indus> whats the middle one for
[10:52] <smb> indus, yep, iirc blue goes into the board side and black and gray would be master and slave drives
[10:52] <jk-> middle is generally slave, IIRC
[10:52] <smb> jk-, Yeah, so do I 
[10:53] <indus> http://www.novell.com/coolsolutions/img/16837_ide-cable.gif
[10:53] <indus> make up your minds
[10:53] <indus> :)
[10:53] <indus> *joke*
[10:54] <indus> ok let me get this right, i set cd drive to master, but connect the cables as it were? 
[10:54] <smb> indus, Well doesn't that prove us. :)
[10:54] <indus> yeah heh
[10:54] <indus> what if i let cd drive remain slave and connect that middle grey one? just wondering
[10:54] <smb> indus, yes, I believe there had been issue running  slave only setups like this
[10:55] <smb> as a general rule, if there is only one drive on the cable it should run as master
[10:55] <indus> smb: hmm but ther is only 1 drive
[10:56] <indus> smb: i hada floppy, on another port which i removed after karmic got stuck with floppy mesages
[10:56] <smb> indus, soooo? ;-)
[10:56] <indus> smb: i mean, since ther is only 1 drive, shouldnt it run as master
[10:56] <indus> bah nvm , iam speculating
[10:56] <smb> I thought thats what I said :)
[10:57] <indus> smb: anyways ill set it to master manually
[10:57] <indus> smb: will you guys be around here in a few hours?
[10:57] <smb> indus, Chances are good
[10:57] <indus> excellen
[10:57] <indus> t
[10:57] <indus> now,i have a general question for you guys/ladies
[10:58] <indus> i have this game called quake4 which has an executable called quake4-smp which takes use of dual cores
[10:58] <indus> ever since karmic alpha 4 it crashes now, is this a kernel thing or an application thing
[10:59] <indus> i guess this is too little information for you , but i wonder what the problem could be
[11:00] <smb> indus, An application crashing is certainly an application thing. 
[11:00] <indus> i get a segmentation fault 
[11:00] <indus> was wine since dapper drake 
[11:01] <indus> fine
[11:01] <indus> funny thing is , if i run the regular non smp file and enable smp in console it runs fine
[11:02] <indus> ok  but can this qualify for a regression?
[11:02] <apw> you could try stracing the -smp version and see what it does just before
[11:02] <apw> its likely its something that the app is running to find out how many cpus there are or something
[11:02] <apw> something which is likely allowed to change, and something userspace is meant to cope with
[11:03] <apw> coredumping would clearly be a fail on the applications behalf
[11:04] <apw> s/clearly/very highly likely/ ... if i am totally fair about it
[11:04] <indus> apw: ok , but if this application worked fine for 2 years, and started crashing in the newer karmic os, what is the solution
[11:04] <indus> i wrote to id software, but unlikely they will do anything now
[11:05] <apw> newer karmic kernel and user space ... well if the app is broken in some way which is now exposed by karmic thats not likely something we can fix for them
[11:05] <indus> hmm
[11:05] <apw> if its breakage in the kernel/userspace then we can address that
[11:05] <apw> figureing out which with a closed source app would be very hard
[11:06] <apw> though i would start by stracing it and seeing what it did last
[11:06] <indus> apw: ok ,hmm  iam going to try running this gaem with hardy today again to make sure its not a corrupt data file
[11:06] <indus> apw: running strace <gulp> ill try reading more on that
[11:07] <indus> apw: could you explain userspace 
[11:07] <indus> apw: also, what is it i could do for you to address the kernel/userspace issue in relation to this application?
[11:07] <indus> if any*
[11:08] <apw> userspace == everything thats not the kernel and not your application in this case
[11:09] <apw> so libraries and the like... they could have had a bug fixed which the app is relying on for instance
[11:36] <indus> oops sorry
[11:36] <indus> i got disconnected
[11:41] <indus> apw smb hello again
[11:41] <apw> hi
[11:43] <indus> any further comments on my bug?
[11:45] <indus> apw: setting jumper will involve physically dismounting the drive isnt it?
[11:46] <apw> i would expect so, the jumper docs are bnormally on the bottom of the drive
[11:47] <apw> i am building a test kernel with some additional diagnostics information to try and find out which of three cases are triggering the drive reject ... which may help understanding
[11:48] <indus> the three cases would be?
[11:48] <indus> this is all so interesting, i should learn some C i guess
[11:50] <indus> also, would you like me to test this kernel you are building?
[11:59] <apw> the three cases are a controller diagnostic failure, an HSM violation, and a stuck register check
[12:00] <apw> when the kernel is built and pushed up i'll add some instructions and commenty to the bug with the details
[12:26] <indus> bye now and thanks
[12:26] <indus> ill drop in later in 3 hours or so
[14:31] <indus> apw smb hooray it works when i changed it to master 
[14:31] <indus> so now what
[14:31] <indus> :)
[14:32] <indus> i want to thank you for this help
[14:32] <apw> indus, heh well thats good new.  first thing is to report that in the bug
[14:32] <apw> did you boot my kernel at all? before that?  might be interesting to have that data
[14:32] <indus> ya cool isnt it, and i finally found out what a jumper is
[14:32] <apw> but with the drive as slave
[14:32] <indus> which kernel? havent checked the report
[14:32] <indus> you added ?
[14:32] <indus> i just came home
[14:33] <apw> i pushed a kernel to try and find out why it errored there
[14:33]  * indus is happily browsing through the 8.04 cd  
[14:33] <apw> very nice
[14:33] <indus> iam really greatful (i hope i spelled that right)
[14:33] <indus> finally iam gonna rent some dvd's 
[14:34] <smb> Im not very positive having a single drive forced to slave is a use case which would be thought of supported
[14:34] <apw> heh well please do write up that you change it to master and it started working
[14:34] <smb> It might have worked with the old driver but ...
[14:34] <indus> smb, hmm?
[14:34]  * apw isn't at all convinced there is any techinical reason that the slave should not work on its own
[14:34] <apw> but ... its good to know how to make it work
[14:34] <apw> its possible that the error from the master failing is getting in the way of the slave identify
[14:35]  * cking is bemused by thus too
[14:35] <apw> its possible its an obvious thing to upstream
[14:35] <smb> If I recall that correctly there is some relationship between detection sequence and used ports
[14:35] <indus> apw yeah, not all people will be able to drop in here and do the master slave thing
[14:36] <indus> lucky i had  a screwdriver
[14:36] <apw> indus, if you have the energy to put it back as slave then test my kernel it may help us in deciding what if anything to report upstream.  if not not the end of the world
[14:36] <apw> but do report your success either way
[14:36] <indus> apw, what is the size of kernel?
[14:36] <apw> 25MB or so
[14:36] <indus> hmm
[14:36] <smb> So they go somewhat master, then slave. But when no master is found they might stop. Maybe even the drive keeps silent unless it "heard" his master
[14:37] <indus> ok so just download and install the kernel?
[14:37] <apw> i think in this case we get a controller level error on the master and then that is still pending when the slave error occurs and that moves that drive to bust
[14:38] <apw> possibly incorrectly.  though i am cirtian that master is the preferred place for a dive
[14:38] <apw> drive
[14:38] <apw> indus, is only worth doing that kernel if the drive moves back to slave ... else it'll report nothing new
[14:38] <indus> ya ill move it back to slave
[14:39] <indus> but which kernel exaactly? i see a few 
[14:39] <indus> oops sorry headers  and image, so i need 64 bit and all.deb?
[14:39] <apw> if you don't have any binary drivers then just the kernel image is enough
[14:40] <indus> i have nvidia
[14:40] <indus> actually iam not sure what you mean
[14:40] <apw> so you need the headers too and the all
[14:41] <indus> so headers amd64,image amd64 and all.deb
[14:41] <indus> downloading
[14:41] <apw> indeed so
[14:41] <apw> thanks for testing
[14:41] <indus> no problem at all
[14:42] <indus> so i install it now? or move slave and then?
[14:42] <indus> yikes i already installed
[14:42] <indus> aah boot time i guess
[14:42] <indus> will this appear in grub?
[14:46] <indus> brb 
[15:24] <root> hi
[15:24] <root> smb: help
[15:24] <smb> indus, what's up?
[15:25] <indus> i installed those kernel and now my screen flickers , but i dont see that kernel in grub
[15:26] <indus> wher is apw
[15:26] <indus> man
[15:26] <apw> ?
[15:26] <smb> indus, it would be a bit strange when a kernel, you not even see in grub would affect your system. sure there was no looseing of cables while switching back to slave
[15:26] <apw> what kernels do you see
[15:27] <apw> the kernel should have been a -15 right?
[15:27] <apw> which should be separate from your real kernels
[15:28] <apw> hmm he is gone
[15:29] <smb> Loose power cable?
[15:34] <indus> smb: just do me  a favour, please go to that bug report and tell me name of kernel which andy gave
[15:34] <indus> i have to remove it
[15:35] <indus> x wont start for me now
[15:35] <smb> indus, So nvidia module does not get rebuild correctly... a sec
[15:36] <indus> yeah but i cant see  that kernel in grub either, i booted normal kernel, i guess x starts after that doh !
[15:37] <smb> should be linux-image-2.6.31-15-generic_2.6.31-15.49~lp425756apw1
[15:37] <smb> as the package name
[15:38] <indus> how come i dont see it in grub?
[15:39] <smb> indus, Its a bit strange as the nvidia modules should get rebuild when you install that. All the kernels before were -14. And it should be in grub as well
[15:39] <indus> hmm i have a 15, but it doesnt say fullk name
[15:40] <indus> but i booted 14 and that too wotn get to x
[15:40] <smb> The latest release kernel was -14.48, so everything saying -15 is new
[15:40] <indus> anyways ill brb
[15:44] <indus> ok solved
[15:44] <indus> smb, but when i did apt-get remove and pressed tab, it only showed upto 15 , not the full name
[15:44] <indus> phew
[15:45] <smb> Glad, to hear. Though I cannot see how installing a -15 kernel would kill your -14 version... 
[15:45] <apw> indus, so what happened there?
[15:45] <indus> smb, i swear it killled 14 too
[15:46] <indus> apw, display trouble
[15:46] <apw> yeah installing -15 would not normally have any way to touch -14
[15:46] <indus> apw, well , it happened i swear
[15:46] <Darkness> question: to enable bluetooth on my laptop, i need to load a module. the problem is i have to do it everytime i reboot. is there anyway to load it automaticly?
[15:46] <apw> indus, well lets call it day on testing, and just get you to report 'moving to master fixed it for me' to the bug
[15:47] <indus> apw, :)
[15:47] <apw> we can let the others play with -15 if they can't move to master
[15:47] <smb> Darkness, Tried to add it to /etc/modules?
[15:47] <indus> apw, iam willing to try it 
[15:47] <apw> Darkness, what smb said
[15:47] <indus> apw what about your kernel then, you make new one?
[15:47] <Darkness> ok ill try, thanks
[15:48] <indus> also,what do i mark the bug report as? 
[15:48] <indus> this will need to be addressed isnt it?
[15:48] <apw> indus, i'll try booting it on my other laptop, it would be unexpected if there was anything wrong with it
[15:48] <indus> apw did i mention , i didnt get display, i have nvidia 
[15:48] <apw> indus, as for the bug, we'll need someone to be able to run the debugging kernels if we are going to get a s/w fix for them
[15:49] <smb> indus, The status likely stays on whatever it is now. We just need to get that info in as a comment to help others
[15:49] <indus> ok i do it now then
[15:49] <apw> indus, your info is a good work around so we don't need to change the status at this juncture
[15:49] <apw> smb, if this is an nvidia interaction its likely in your pre-proposed kernel too ... 
[15:49] <indus> so i suppose, this bug is not amd specific then, and could happen to anyone?
[15:49] <apw> got any nvidia stuff to test on
[15:49] <smb> indus, and you installed linux-image and linux-header-generic and linux-headers*all for the -15 kernel?
[15:50] <indus> wait
[15:50] <smb> apw, I would expect it to behave the same way. Only adding the ppa offers all required packages in one without need of dpkg -i
[15:51] <apw> smb, yeah so if indus installed all three and its not working then we may have an issue on the horizon
[15:52] <smb> indus, It still might depend on amd (as in the controller of the sata/pata)
[15:52] <smb> apw, If, maybe but somehow it seems very odd. Let me boot my desktop with nvidia and update
[15:52]  * apw is suspicious its related to the combination thereof ... the kit in that machine has many a brokenness qurked around
[15:53] <Darkness> another question: shutdown and reboot through gnome gui doesnt work. it logs me out, the screen turns off, and then the pc just get stuck. any idea why?
[15:53] <indus> yes i installed 3 things , http://people.canonical.com/~apw/lp425756-karmic/linux-image-2.6.31-15-generic_2.6.31-15.49~lp425756apw1_amd64.deb
[15:53] <indus> http://people.canonical.com/~apw/lp425756-karmic/linux-headers-2.6.31-15_2.6.31-15.49~lp425756apw1_all.deb
[15:53] <indus> http://people.canonical.com/~apw/lp425756-karmic/linux-headers-2.6.31-15-generic_2.6.31-15.49~lp425756apw1_amd64.deb
[15:54] <indus> correct ?
[15:54] <apw> looks correct to me ...
[15:54] <indus> shall i install it again to double check? 
[15:54] <smb> yep
[15:54] <apw> indus, be nice to see the output of those commands if you are willing to install them
[15:54] <indus> also, why would it only show 2.6.  15 and not the full name of the deb file
[15:54] <apw> put them in pastebin or something
[15:55] <indus> apw which commands
[15:55] <apw> indus, the output fromt he install commands, as we should see dkms doing things for nvidia etc as it goes
[15:55] <smb> indus, That might be because the grup lines do not show the release numbers, only the -15-generic part
[15:55]  * indus updated the bug report and thanked 2 people
[15:55] <indus> smb, no no ,also when i wanted to remove with apt-get, it didnt show full name
[15:55]  * apw installs the kernel on a misc  machine
[15:56] <apw> indus, right you remove by package name, not version
[15:56] <apw> the package name happens to contain the 2.6.31-15 part of the version as well as being in the version
[15:56]  * indus scratches head
[15:56] <apw> that is how we let you have more than one kernel install
[15:56] <apw> look at a simple package like upstart ... its just called upstart
[15:56] <indus> aaah ook the 3 packages together make the kernel?
[15:56] <apw> and you can only have one of it installed
[15:57] <apw> yep those three packages are the kernel, and there can be more than one set installed
[15:57] <apw> so you can boot back when it fails
[15:57] <indus> wait stay online
[15:58] <apw> so you'l find 3 lots of -14 and 3 lots of -15 installed
[15:58] <indus> aah crap wrong channel
[15:58] <indus> lol
[15:58] <indus> ok iam too tired now, all over my head
[15:58] <apw> indus, all you need to remember is the names of the kerenl are complex and confusing ... and its necessary :)
[16:02] <indus> apw, so can i do this tomorrow now?
[16:03] <indus> smb, did you try the kernel?
[16:03] <smb> Shoot, seems I haven't booted that for a while... no its first 550MB of other stuff that needs to go on
[16:04] <apw> indus, whenever
[16:04] <indus> ok its 9 30 pm here, need to shower etc :)
[16:04] <indus> apw, jusst tell me, which commands were you talking about?
[16:04] <apw> i would be interested to see all of the output that the dpkg -i commands produce when you install the three packages of mine ...
[16:05] <apw> that should include some install information for the the nvidia stuff which would be handy if there is an issue there
[16:05] <indus> apw hmm from a terminal 
[16:05] <apw> yeah from a terminal ...
[16:06] <apw> you can use 'script' to record the output
[16:06] <indus> sorry dont know anything about script
[16:07] <smb> indus, you could also the old fashioned way and add "2>&1 |tee logfile.txt" to the dpkg command
[16:07] <indus> iam a noob really
[16:07] <indus> give me full syntax please
[16:09] <smb> indus, just to be safe, you were amd64 or i386?
[16:09] <indus> smb dpkg -i filename 2>&1 |tee logfile.txt ?
[16:09] <indus> amd 64
[16:10] <smb> dpkg -i linux-headers-2.6.31-15-generic_2.6.31-15.49~lp425756apw1_amd64.deb linux-headers-2.6.31-15_2.6.31-15.49~lp425756apw1_all.deb linux-image-2.6.31-15-generic_2.6.31-15.49~lp425756apw1_amd64.deb 2>&1|tee logfile.txt 
[16:10] <indus> smb, so all individually ?
[16:10] <smb> indus, all 3 files in one go
[16:11] <indus> smb, so shall i copy paste those commands ?
[16:11] <smb> indus, if line break does not get messed up that should work
[16:11] <smb> indus, it is just one command
[16:11] <smb> with the 3 packages as agruments
[16:11] <indus> smb, ok wait
[16:12] <indus> i have a 15 min window befoer all shops close here :)
[16:12] <indus> then iam doomed
[16:12] <smb> indus, then I would propose to do that first and then come back
[16:12] <indus> np
[16:13] <smb> We don't want to be responsible for someone starving
[16:13] <indus> lol dont worry
[16:13] <indus> its not food but cigarettes
[16:14] <indus> also a phone recharge
[16:14] <indus> oh no
[16:14] <indus> wrong commands
[16:15] <indus> my mistake
[16:15] <indus> got it
[16:15] <indus> how do i give it to you?
[16:15] <smb> attach it to the bug
[16:17] <indus> done
[16:17] <indus> check it out
[16:17] <indus> ill see you in 15 min
[16:17] <smb> k
[16:20] <indus> ok smb it works
[16:20] <indus> Linux rajeev-desktop 2.6.31-15-generic #49~lp425756apw1 SMP Mon Nov 2 11:44:42 UTC 2009 x86_64 GNU/Linux
[16:21] <indus> i probably missed a package
[16:21] <indus> or maybe was some other problem 
[16:21] <smb> Seems 15mins are quicker in other places. :)
[16:21] <smb> But good
[16:22] <smb> Still it should have not effected the -14 part
[16:23] <smb> indus, Now it will be interesting to get your new full dmesg attached to the bug as wel
[16:25] <indus> i changed it to master though :)
[16:25] <smb> indus, the drive?
[16:25] <smb> that would make the dmesg useless
[16:26] <smb> We'd need one with the drive failing 
[16:32] <indus> smb, ya ok ill set it to slave again
[16:32] <indus> damn
[16:34] <indus> smb, what changes are there in this new kernel that will make you fix the issue?
[16:35] <smb> indus, not fixing, apw put in debug messages to see which of the three things will fail
[16:35] <indus> aah ok ok
[16:35] <indus> ill brb
[17:03] <bdmurray> Why are apport-kerneloops still being reported about karmic?
[17:10] <Ng> bdmurray: possibly /usr/share/apport/kernel_oops needs to check /etc/default/apport ?
[17:56] <indus> smb, apw hi i attached dmesg
[17:57] <apw> indus, damn lost the link to the bug, can you remind me of the number
[17:57] <indus> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/425756
[17:57] <ubot3> Malone bug 425756 in linux "[regression karmic] cd/dvd drive not detected" [Medium,Incomplete] 
[18:00] <apw> kd
[18:00] <apw> indus, i take it your video worked this time round on my kernel?
[18:00] <indus> apw yeah
[18:01] <apw> smb, good news on the nvidia video with -15 ...
[18:01] <indus> probably messed up installation
[18:01] <indus> apw, yeah he knows already 
[18:01] <indus> so  does dmesg say anything noteworthy
[18:02] <smb> apw, indeed :)
[18:02] <apw> it says this is an 'HSM violation' ... and the drive is rejected
[18:06] <indus> ok
[18:06] <indus> now?
[18:06] <apw> now one needs to know what the heck it mean
[18:06] <indus> lol
[18:06] <apw> stupid acronymus
[18:07]  * indus googles it
[18:11] <indus> apw i go now
[18:16] <apw> indus, ok
[18:16] <indus> apw, smb bye bye, ill keep checking the bug report
[18:16] <smb> bye
[18:16] <indus> apw, anything else you need?
[18:16] <apw> not till i know what it means ... thanks
[18:17] <indus> ok bye and thanks a million,i will set this to master till you have any new things
[21:11] <Kano> hi, is there a reason why the -15 kernel was not updated to 2.6.31.5? 
[23:11] <dtchen> bjf: hi, received your e-mail and will follow up. Traveling a bunch this week, so apologies in advance.
[23:12] <bjf> dtchen, understood