[00:23] <sbeattie> nagappan: no, I don't believe so, as plymouth acts as the I/O intermediary between the system and whatever interface (text console/graphic splash) presents it.
[00:24] <sbeattie> nagappan: are you using beta 1 or the daily iso snapshot to try your install?
=== kermiac_ is now known as kermiac
[00:27] <sbeattie> nagappan: slangasek might be able to give you more guidance about bug 552393
[00:27] <ubot4> Launchpad bug 552393 in plymouth (Ubuntu) "Installing Ubuntu 10.04 through Ilo interface doesn't seem to work (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/552393
[00:42] <nagappan> sbeattie, sorry was away, I'm using beta1
[00:44] <nagappan> sbeattie, sure, let me ping slangasek
[00:44] <nagappan> hello slangasek
[00:47] <slangasek> nagappan: hi - can you please test with a daily image?  plymouth has changed substantially since beta1, and I don't think it's going to benefit us to try to debug this failure with the beta image directly
[00:48] <nagappan> slangasek, sure, let me download the daily image now
[00:49] <slangasek> you may well run into *other* problems with the daily image that prevent you completing an install; but at least this lets us rule out plymouth
[01:27] <nagappan> ah ! slangasek left :)
[01:40] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5454959018502120402
[01:40] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5454962545741038722
[01:41] <nagappan> slangasek, still booting, for last 45 minutes
[01:41] <nagappan> slangasek, downloaded image http://cdimage.ubuntu.com/daily-live/current/lucid-desktop-amd64.iso
[01:41] <slangasek> nagappan: do you boot it with any particular kernel commandline options?
[01:44] <slangasek> nagappan: in particular, does your ilo involve setting a 'console=' option?
[01:44] <nagappan> slangasek, I just removed splash and quiet
[01:44] <nagappan> slangasek, otherwise, I haven't changed anything
[01:44] <slangasek> and the ilo is connected to the machine's VGA output?
[01:45] <nagappan> slangasek, with the same machines, I have Ubuntu 8.04 / 9.04 / 9.10 working
[01:45] <slangasek> what happens if you *don't* remove splash and quiet?
[01:46] <nagappan> slangasek, it uses IPMI technology, the VGA is connected to physical monitor, since the machine is located 200 miles away from my office, I have to use only ilo to access it remotely during installation
[01:46] <nagappan> slangasek, if I don't remove those options, the screen just stays blank, I waited last time for 2 hours
[01:47] <nagappan> slangasek, new screen - http://picasaweb.google.com/nagappan/Tmp#5454964288819800066
[01:47] <slangasek> so there's a physical monitor connected to the VGA port, and the iLO is done via a separate IPMI interface?
[01:48] <nagappan> slangasek, perfect :)
[01:48] <slangasek> are you able to send a sysrq key via the ilo?
[01:48] <slangasek> if so, please send Alt+SysRq+K
[01:49] <nagappan> slangasek, I have soft keyboard option
[01:49] <nagappan> slangasek, let me do it
[01:53] <nagappan> slangasek, I don't see SysRq in soft keyboard - just incase sharing the screenshot :) http://picasaweb.google.com/nagappan/Tmp#5454965568864614354
[01:53] <nagappan> slangasek, doing with my regular keyboard, focusing the ilo window
[01:53] <slangasek> nagappan: it may work by sending Alt+Prn+K
[01:55] <nagappan> slangasek, it logged me off from my Ubuntu host :D
[01:55] <slangasek> <cough> yes
[01:58] <slangasek> nagappan: Alt+Prn+K on the soft keyboard may do the right thing.  If not, we probably need to edit the boot options to break into the initramfs
[01:59] <nagappan> slangasek, sure
[02:03] <nagappan> slangasek, whats the expected output of this ?
[02:03] <nagappan> slangasek, I don't see anything happening with it
[02:14] <slangasek> nagappan: if it didn't immediately cause the login screen to appear, then it didn't work; so you get to break into the initramfs instead
[02:14] <slangasek> adding 'break=top' to the boot options should do the job
[02:14] <nagappan> slangasek, sure
[02:14] <nagappan> slangasek, let me do it now
[02:27] <slangasek> nagappan: any luck?
[02:27] <nagappan> slangasek, its not booting
[02:28] <slangasek> oh?
[02:28] <nagappan> slangasek, my virtual cd image seems to be not reachable
[02:28] <slangasek> ah
[02:28] <nagappan> slangasek, debugging
[02:36] <nagappan> slangasek, removing splash and quiet
[02:36] <nagappan> slangasek, adding break=top
[02:36] <nagappan> slangasek, let me boot now and see
[02:37] <nagappan> slangasek, when I press enter it stays in the initial screen for about 10 minutes, initially I thought the system got hung ! later I realized it takes time to boot !
[02:38] <nagappan> slangasek, still in initial screen, will update you once, it enters the next screen
[02:40] <nagappan> slangasek, I'm into intramfs prompt
[02:41] <slangasek> ok
[02:41] <slangasek> run '/scripts/init-top/udev'
[02:41] <nagappan> slangasek, sure
[02:42] <nagappan> slangasek, looks like its in hung state, I'm unable to type any
[02:42] <slangasek> oh. :/
[02:42] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5454978538134140082
[02:43] <slangasek> well, there's one more thing we can try
[02:43] <nagappan> slangasek, sure
[02:44] <slangasek> instead of 'break=top', try 'break=casper-bottom'
[02:45] <nagappan> slangasek, sure
[02:53] <nagappan> slangasek, I'm in initramfs prompt
[02:53] <nagappan> slangasek, and its accessible
[02:54] <slangasek> nagappan: great - please run 'cat /proc/fb' and 'ls -l /sys/class/drm' and tell me the output of each
[02:54] <nagappan> slangasek, sure
[02:55] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5454981775863160354
[02:57] <slangasek> nagappan: cat /sys/class/drm/*/status
[02:57] <nagappan> slangasek, sure
[02:58] <nagappan> slangasek, I got 2 lines of "connected" string printed
[02:59] <slangasek> nagappan: ok - at this point, my best guess is that this is an instance of bug #533135
[02:59] <ubot4> Launchpad bug 533135 in plymouth (Ubuntu) "System fails to boot with plymouth installed (nouveau driver with >1 display) (affects: 24) (dups: 12) (heat: 216)" [Medium,Triaged] https://launchpad.net/bugs/533135
[02:59] <nagappan> slangasek, ah ! ok :)
[02:59] <slangasek> but that bug has only been reported on nvidia before now; and it hasn't been diagnosed, so I don't know if it should also affect radeon
[02:59] <slangasek> have you tried booting with 'nomodeset'?
[03:01] <nagappan> slangasek, nope, shall I try now ?
[03:02] <nagappan> slangasek, added myself to the above bug
[03:02] <slangasek> yes, please try the nomodeset option
[03:02] <nagappan> slangasek, trying now
[03:13] <nagappan> slangasek, still waiting
[03:13] <slangasek> did it stop at the same place as before?
[03:14] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5454959018502120402
[03:14] <nagappan> slangasek, waiting here
[03:14] <slangasek> right - same place it stopped before, hmm
[03:14] <nagappan> slangasek, just a general question, what does this plymouth do ?
[03:14] <nagappan> slangasek, yes
[03:15] <slangasek> plymouth serializes boot-time interactions with the user; it's needed because we have a parallel boot system which could be starting multiple programs at the same time which need to interact with the user in a comprehensible manner
[03:16] <slangasek> ...it does this by taking over the console, so any bugs in it are serious bugs
[03:16] <nagappan> slangasek, ah ! ok
[03:16] <nagappan> slangasek, make sense
[03:17] <nagappan> slangasek, but it makes Ubuntu 10.04 experience harder :) Hope it will be resolved soon
[03:17] <slangasek> just to be sure... could you try booting with 'break=init'?
[03:18] <slangasek> we could still be wrong about plymouth being involved
[03:19] <nagappan> slangasek, sure, let me try now
[03:21] <nagappan> slangasek, with nomodeset ?
[03:22] <slangasek> with or without; shouldn't matter
[03:22] <nagappan> slangasek, ok
[03:22] <slangasek> as long as you see *some* text output
[03:24] <nagappan> slangasek, ok
[03:26] <nagappan> slangasek, after pressing enter in boot prompt, not sure, why it takes atleast 5 minutes to come to the next screen
[03:26] <nagappan> slangasek, maybe extracting the initram ?
[03:27] <slangasek> that's all it should be doing - is it extracting it across the network?
[03:27] <slangasek> initramfs extraction should be fast
[03:27] <slangasek> *CD* extraction is very slow, however
[03:27] <slangasek> so if it takes 5 minutes just to extract the initramfs, it's *possible* that 2h to unpack the livefs is accurate
[03:28] <slangasek> and not a bug in plymouth at all
[03:29] <nagappan> slangasek, ok
[03:29] <nagappan> slangasek, yes its across network
[03:29] <nagappan> slangasek, the ISO exist on my box
[03:30] <nagappan> slangasek, and the test machine physically 200 miles away !
[03:30] <slangasek> I don't know why 10.04 would be slower than previous releases
[03:30] <nagappan> slangasek, its in "Adding live session user...."
[03:31] <nagappan> slangasek, but 10.04 installation as a guest inside VM, it rocks !
[03:31] <nagappan> slangasek, believe me :)
[03:31] <slangasek> so if it's stopping there even with break=init, I don't see anyway that this could be a plymouth bug
[03:31] <nagappan> slangasek, we use that for our regular testing
[03:31] <nagappan> slangasek, ah ! ok
[03:32] <slangasek> is it possible that the kernel never succeeds in detecting your CD?
[03:32] <slangasek> because there are many errors about /dev/sr0 in the screenshots
[03:32] <nagappan> slangasek, Ubuntu 10.04 is high priority for our upcoming VMware Workstation release
[03:32] <nagappan> slangasek, but it has detected the virtual CD
[03:32] <nagappan> slangasek, /dev/sr1
[03:32] <slangasek> ah
[03:33] <slangasek> maybe it needs to be manually told to look at /dev/sr1
[03:33] <nagappan> slangasek, ah ! how do I do that ?
[03:34] <nagappan> slangasek, the same thing worked for other Ubuntu versions !
[03:34] <slangasek> I'm not sure; currently looking
[03:34] <nagappan> slangasek, ok
[03:37] <nagappan> slangasek, looks like configuring fstab took more time ?
[03:38] <slangasek> nagappan: sorry, what do you mean?
[03:38] <nagappan> slangasek, let me see whether I have any screenshot
[03:38] <nagappan> slangasek, that screen is now completely blank
[03:39] <nagappan> slangasek, after this http://picasaweb.google.com/nagappan/Tmp#5454959018502120402
[03:39] <nagappan> slangasek, it takes long time
[03:39] <nagappan> slangasek, and then print, something like configuring fstab
[03:39] <slangasek> nagappan: ah
[03:39] <slangasek> yes, if you look in the casper package at the files under /usr/share/initramfs-tools/scripts/casper-bottom, you'll see the series of scripts that it's trying to run
[03:40] <slangasek> there are a *lot* of them, and it seems we've only gotten up to '12fstab' in the sequence
[03:40] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5454993361718377666
[03:40] <nagappan> slangasek, ok
[03:40] <nagappan> slangasek, now in intramfs prompt :D
[03:40] <slangasek> nagappan: do you normally install from an image 200 miles away from the machine, or do you usually put the image closer to the target machine first?
[03:41] <nagappan> slangasek, this is our usual scenario and works well :)
[03:41] <slangasek> oh, if you're at an initramfs prompt, just type 'exit'
[03:41] <slangasek> and see if it continues
[03:41] <nagappan> slangasek, sure
[03:42] <nagappan> slangasek, all the host OS images are located in our corporate center, where we work and the test machines are in different state !
[03:42] <slangasek> right
[03:42] <slangasek> I don't know why this is slow, then
[03:43] <nagappan> slangasek, after I typed exit and pressed enter
[03:44] <nagappan> slangasek, it just stays there
[03:44] <slangasek> hmm
[03:44] <slangasek> well, if the root filesystem on the liveCD were not mounted, I would expect to see errors from those scripts
[03:45] <slangasek> so I believe everything up to running init is working
[03:45] <slangasek> but if there's a performance issue with the CD, it's definitely going to affect trying to chroot into the livefs and start X, as well
[03:53] <slangasek> nagappan: ok, one more idea: boot without 'quiet' 'splash', boot with 'nomodeset' and '--verbose'
[04:00] <nagappan> slangasek, sure
[04:01] <nagappan> slangasek, -- at end is required ?
[04:02] <slangasek> not required
[04:03] <nagappan> slangasek, pressed enter, let me see
[04:21] <nagappan> slangasek, http://picasaweb.google.com/nagappan/Tmp#5455004022539527410
[04:23] <slangasek> nagappan: ok - can you please link that from the bug report?
[04:23] <nagappan> slangasek, sure
[04:23] <slangasek> I've run out of ideas on this for the evening; I think it'll have to wait until someone else picks it up now and can figure out what's happening
[04:24] <slangasek> how long has it been stopped at that line?
[04:24] <nagappan> slangasek, atleast for last 15 / 20 minutes
[04:25] <slangasek> right
[04:25] <slangasek> so that's definitely hanging, I just can't see why
[04:25] <nagappan> slangasek, ah ! now its in new screen (though I have seen this earlier) - http://picasaweb.google.com/nagappan/Tmp#5454964288819800066
[04:26] <slangasek> can you try switching VTs? Alt+F1, Alt+F7?
[04:26] <nagappan> slangasek, back to this screen itself http://launchpadlibrarian.net/42744482/Screenshot-Supermicro%20Daughter%20Card%20Remote%20Console%20-%20w1-hutlab045-ilo.eng.vmware.com-4.png
[04:26] <nagappan> slangasek, sure
[04:27] <nagappan> slangasek, nothing is happening, maybe in hang state
[04:27] <slangasek> ok
[04:28] <slangasek> the screen switch should indicate either plymouth exiting, or X starting
[04:28] <nagappan> slangasek, ah ! ok
[04:28] <nagappan> slangasek, looks like X is starting
[04:28] <nagappan> slangasek, still the screen is blank
[04:29] <slangasek> so this could be a plymouth, X, or kernel bug
[04:29] <slangasek> since we're booting without 'splash', it's probably not a plymouth bug
[04:29] <slangasek> I suggest sending all this information to the bug
[04:30] <nagappan> slangasek, ok
[04:32]  * nagappan heading home from office
[04:32] <nagappan> slangasek, thanks for your kind help and debugging instructions :)
[04:32] <slangasek> sure - sorry for not figuring out the bug yet
[04:35] <nagappan> slangasek, np :) let me try tomorrow as well :)
=== kermiac is now known as kermiac_
[11:11] <davmor2> morning all
=== kermiac_ is now known as kermiac
=== kermiac is now known as kermiac_
[14:57] <davmor2> morning cr3 fader_
[14:57] <fader_> davmor2: Hey dude
[14:57] <cr3> davmor2: yo mama
[14:57] <davmor2> happy april fader_ day
[14:59] <fader_> davmor2: That hurts my feelings, as your opinion is incredibly valuable to me
[14:59] <fader_> APRIL FOOL
[14:59] <fader_> :P
[15:03] <davmor2> fader_: If I thought for one second that your skin wasn't as thick as a rhino's and you know how much we live to rag on each other then I would of swallowed that line :D
[15:03] <fader_> ;)
[15:06] <davmor2> I haven't seen so many net gags this year
[15:06] <davmor2> but then I've been too busy to look too
=== yofel_ is now known as yofel
[20:08] <gringochapin> Hi all. I have some xml files from the system testing application that we generated on a few different computers at our local jam last weekend.  Where do I go to submit these?  The application seemed to have a bug, so we were not able to submit any of the results.
[20:08] <gringochapin> That is, we weren't able to submit any of them automatically.
[20:09] <gringochapin> I believe we were hit by this bug: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/540080
[20:09] <ubot4> Launchpad bug 540080 in checkbox (Ubuntu) "System Testing failed to upload to server (affects: 6) (heat: 34)" [Undecided,Confirmed]
[21:39] <nagappan> slangasek, Hi
[21:39] <nagappan> slangasek, https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/533135
[21:39] <ubot4> Launchpad bug 533135 in plymouth (Ubuntu) "System fails to boot with plymouth installed (nouveau driver with >1 display) (affects: 26) (dups: 13) (heat: 236)" [Medium,Triaged]
[21:40] <nagappan> slangasek, I read text theme over here
[21:40] <nagappan> slangasek, how can I try that ?
[21:42] <slangasek> nagappan: if you're booting without 'splash', you're already using /a/ text theme.  You can test the ubuntu-logo text theme by booting with 'plymouth:splash=text'
[21:44] <nagappan> slangasek, ah ! ok, I guess in my case its issue due to multiple VGA card on the host system
[21:48] <slangasek> maybe