[10:39] <Kano> hi, could somebody merge 2.6.30-rc6
[12:25] <Loco> Hi. I just upgraded to Ubuntu 9.04. Now my MP3's play verry fast most of the time. It does not matter what app I use to play them or what size or bitrate they were made at..Any help would be apreciated.
[12:26] <Nafallo> mode +c would be appreciated as well :-)
[16:03] <vertix> i am having a hard time with booting 8.10 because of mixed drive configuration. I have IDE and SCSI (sata) drive. BIOS is set for IDE to be 1st drive. But when I boot from livecd, it becomes 2nd drive and when i regenerate grub and put it on MBR, it thinks it is 2nd drive (hd1) for grub. So, when you boot from grub and escape to commmand line, you are seeing that / partition as drive 1, not 2
[16:04] <vertix> and so all other partitions are on the wrong drive and fsck exits with error, because it is trying to check the wrong partition type, because what it is checking is not on the right drive
[16:08] <vertix> basically, what it boils down to is this: looks like you need to change the drive order in bios before you boot from livecd. then, do grub>find /boot/grub/stage1, specify kernel and do a setup, but before you start booting it, you need to go to bios and change drive order, else you won't be able to boot because what grub/kernel think of drive/partition order when you were generating grub, is not the same as when you BOOT
[16:10] <vertix> btw, i am talking about the case when you already had 8.10 installed and are trying to fix the MBR that was wiped out by windows install after ubuntu, in which cause you already have your system, except your MBR needs fixing
[16:11] <vertix> and interesting thing is that even if you refer to drives via guid (in grub's menu.lst), it still does not help
[16:11] <mjg59> I suspect you're misdiagnosing this
[16:12] <mjg59> The kernel ignores bios drive order
[16:12] <vertix> could be
[16:12] <mjg59> Whereas grub pays attention to nothing other than bios drive order
[16:12] <mjg59> So either you don't get a kernel or you don't get a root filesystem
[16:12] <vertix> unfortunately that is not what i am seeing
[16:13] <mjg59> If you get a kernel then grub works fine and it's not a bios drive order issue
[16:13] <vertix> what i see is grub seeing the same drive order as in bios ONLY when you get a grub> prompt. after that, at some point, the drives are swapped and if you manage to boot, your drive order is going to be different than what bios says
[16:13] <mjg59> The kernel doesn't care about bios order
[16:14] <mjg59> If you see any output from Linux then your issue has nothing to do with that
[16:14] <vertix> well, but the thing is, i get an error at the point when root partition is attempted to be mounted
[16:14] <mjg59> The kernel sees all disks and will use the appropriate uuid
[16:15] <vertix> yes, i saw some of that, except in my case, my ide drive was addressed not as guid because it had old grub from old redhat and i don't recall it being addressed as guid, but lemme see here
[16:19] <vertix> well, what i am seeing is menu.lst is not addressing the ide drive as guid. i don't remember exactly now, but it could be that i just copied the grub sections from ide drive (where redhat is installed) to the sata drive (where ubuntu is installed, just to be able to boot any one of them. could this cause some problem?
[16:20] <mjg59> menu.ls tis only parsed by grub
[16:20] <vertix> btw, do you know at what exact point in the boot sequence the grub's device.map goes into effect?
[16:20] <mjg59> In grub
[16:20] <mjg59> If grub can see your kernel then device.map is fine
[16:21] <vertix> grub CAN see my kernel, but it is on the wrong drive. becasue when that grub was generated, the drive order was different. What i am seeing is this:
[16:22] <vertix> when you boot and escape from grub, the drive order is the same as bios
[16:22] <vertix> but at some point in booting sequence, drive order is swapped, and if you manage to boot, then what bios says as drive 1, actually becomes drive 2
[16:22] <vertix> so, at some point, the drive switching happens
[16:23] <vertix> the question is exactly when and why?
[16:23] <mjg59> I have no idea what you mean
[16:23] <mjg59> The kernel doesn't use the BIOS drive order
[16:23] <mjg59> There's no swapping
[16:24] <mjg59> Kernel drive order has never had anything to do with BIOS drive order
[16:24] <vertix> well, but this is not what i am seeing
[16:24] <mjg59> So 0x80 may end up has hdc
[16:24] <vertix> there IS swapping and it is even discussed in GNU's grub documentation somewhere
[16:24] <mjg59> Or sdb
[16:24] <mjg59> Or whatever
[16:25] <mjg59> But if grub is reading the kernel then BIOS drive order is entirely not what you are having a problem with
[16:25] <vertix> you see, grub comes up from MBR of the drive that is set to be drive 1 in bios, doesn't it?
[16:25] <mjg59> Either grub is reading the wrong configuration file or your uuid entry in the grub config is wrong
[16:25] <mjg59> No
[16:25] <vertix> or "active partition"
[16:25] <mjg59> grub is launched from whatever partition the BIOS boots
[16:25] <vertix> correct
[16:25] <mjg59> The rules for that depend on the BIOS
[16:26] <vertix> yep
[16:26] <mjg59> grub then reads stage 1.5 and stage 2 off the disk
[16:26] <mjg59> If that works then grub and the bios agree on drive ordering
[16:26] <mjg59> Which means devices.map is correct
[16:27] <vertix> yep, i am asking about that device.map. at what point that device.map is being looked upon or takes effect in boot sequence?
[16:28] <mjg59> Neve
[16:28] <mjg59> r
[16:28] <mjg59> It's only read when grub is being installed into the boot sector
[16:28] <vertix> assume my 1st drive (in bios is ide), 2nd drive is sata. after kernel comes up, the sata drive shows as sda, not sdb, and ide shows as sdb. why?
[16:28] <vertix> oh, i see
[16:28] <mjg59> Because the kernel enumerates in PCI order, not BIOS order
[16:29] <vertix> so, i need to change the drive order in .map file and THEN regenerate the grub?
[16:29] <mjg59> No
[16:29] <vertix> cause what i am seeing is drives swapping around
[16:29] <mjg59> If grub is running then devices.map is correct
[16:29] <mjg59> The drives are *not* swapping
[16:29] <mjg59> BIOS order has nothing to do with kernel order
[16:30] <mjg59> You can't make them consistent
[16:30] <vertix> then i don't follow it? why do i see different drive order when just starting to boot and when i am booted?
[16:30] <mjg59> You don't
[16:30] <soren> Well, that's exactly *because* BIOS and kernel disk ordering are completely unrelated.
[16:31] <mjg59> Right
[16:31] <mjg59> You can't change the BIOS order
[16:31] <mjg59> And you can't change the kernel order
[16:31] <mjg59> devices.map exists just to tell grub how to get from kernel order (which it can read) to BIOS order (which it can't)
[16:33] <vertix> ok, assume i start booting. i escape from grub and do grub> find /boot/grub/stage1
[16:33] <Nafallo> ehrm. my laptop have two devices in their... I must have installed with the external plugged in :-P
[16:33] <Nafallo> s/eir/ere/
[16:33] <vertix> what I am seeing is stage 1 is not on the same drive as when i was booted from live cd and generated the mbr
[16:34] <mjg59> That's not what you were saying
[16:34] <mjg59> It's helpful if you explain your problem rather than what you think your problem is
[16:34] <mjg59> So grub is reading the wrong config file?
[16:35] <vertix> mjg59, basically, my question is simple: how do i make it boot? are you saying that when i generated grub, i should have done something different?
[16:35] <mjg59> You're not saying what's going wrong
[16:35] <vertix> kernel can not mount root partition because it is on the wrong drive
[16:36] <vertix> and when it does fsck, it says one of partitions is bad, because again, it is looking at the wrong drive
[16:36] <vertix> could it be because of initrd?
[16:36] <mjg59> If the kernel is booting then your problem is unrelated to grub
[16:36] <vertix> you see, i was able to get it booting at some point
[16:36] <mjg59> It could be the initrd
[16:36] <vertix> kernel is not booting. it can not, because it can not mount the / 
[16:37] <mjg59> If you manage to end up with an initrd that doesn't contain drivers for your filesystem then you'll see that
[16:37] <mjg59> If the kernel didn't boot then you wouldn't get that message
[16:37] <mjg59> The kernel has loaded. It's executed. The initrd has then failed.
[16:38] <mjg59> eAnyway. 1:40AM here, so I'm sleeping.
[16:39] <vertix> well, the boot sequence started. because grub was told the actual correct root partition, but when boot process tried to mount /, it complained. it could be that driver for sata was not loaded. i don't argue that
[16:39] <vertix> k, thanx for your time
[17:00] <pong> Hi
[22:16] <vertix> my box got infected with rootkit and it looks like it progressed pretty far and now my cdrom drive does not work as advertised
[22:17] <vertix> looks like bios is infected and when i insert the rw+ disk into it, it starts doing something with the disk and, after a while, reboots the box
[22:18] <vertix> but when i insert the blank CD, then I see the message from ubuntu saying: blank disk is inserted
[22:18] <ikonia> how is this anything to do with a kernal ?
[22:18] <vertix> I am not sure it is a good idea to write anything to that disk, cause there is no guarantee that it is not going to add some viruses to the image
[22:19] <ikonia> this is a.) nothing to do with ubuntu-kernel b.) interesting to hear as you said you couldn't boot ubuntu 
[22:19] <vertix> well, I am curious if someone knows that in case bios is infected, will it percolate to kernel?
[22:19] <ikonia> nothing to do with ubuntu-kernel
[22:19] <vertix> ikonia, why are you following me around and provoking some ugly stuff?
[22:19] <vertix> what does it have to do with YOU?
[22:19] <vertix> what is YOUR problem?
[22:19] <ikonia> I'm not following you, I was here in this channel when you joined, please read the /topic
[22:20] <vertix> and I know enough about kernel level issue to see what does it have to do with what
[22:20] <vertix> Yes, you ARE following me
[22:20] <vertix> here, than on #linux
[22:20] <vertix> what is that you want froim me?
[22:20] <ikonia> I was in this channel before you joined as I was in ##linux before you joined also 
[22:20] <vertix> What is this ugly spying trip you are involved in?
[22:21] <ikonia> vertix: if your bios is infected with a virus is nothing to do with #ubuntu-kernel, plus I can't see how this is anything to do with ubuntu as you explained you can't boot ubuntu 
[22:21] <vertix> ikonia, I am not interested in your opinions
[22:21] <ikonia> vertix: the topic is "ubuntu kernel development only" 
[22:21] <vertix> you can just do all other exciting things you normally do
[22:21] <ikonia> please check the /topic
[22:22] <vertix> ikonia, one more time: I am not interested in YOUR opinion? Is that clear enough?
[22:22] <vertix> I have seen one of your opinions and it is totally off the wall
[22:22] <ikonia> vertix: one more time - respect the channels topic
[22:22] <LjL> vertix: please stay on topic.
[22:22] <vertix> I never had a single chance to work
[22:22] <vertix> and I would have to spend half a day doing the most stupid thing in the world
[22:23] <vertix> so, could you stay away from me and mind your own business?
[22:23] <ikonia> thats not our problem, follow the channels topic, please. 
[22:23] <vertix> the topic is this:
[22:23] <ikonia> the topic is displayed in /topic 
[22:23] <vertix> can virus potentially affect the cdrom drivers
[22:23] <vertix> kernel level
[22:23] <LjL> No, the topic is: "KERNEL BUG DAY 12-May-2009 | Ubuntu kernel development discussion ONLY | Kernel Wiki: https://wiki.ubuntu.com/KernelTeam | Latest news: Released 2.6.28 kernel for Jaunty/9.04. | Kernel git trees: http://kernel.ubuntu.com/git | Latest kernel upload: 2.6.28-12.43 based on 2.6.28.10 final"
[22:24] <vertix> k, I see, thanx anyway, I guess you have better things to do in your life
[22:24] <ikonia> thanks,