[09:56] <chih__> i upgraded my jaunty image to karmic through "update-manger -d" on an i.mx51 based system.  now the system would always get stuck while loading gdm. could anyone give me some pointers regarding how to go about debugging it?
[10:02] <lool> chih__: That's with a custom kernel and no initrd right?
[10:02] <lool> chih__: Can you setup a serial console and change the cmdline to log to serial console to see what's going on?
[10:03] <chih__> chih__,  i tried "single" to get to the console mode and manually run "/usr/sbin/gdm" gets me the same result.
[10:03] <chih__> lool,  already did that.
[10:03] <chih__> lool,  right. custom kernel + noinitrd. that's right
[10:04] <lool> chih__: So what's the actual problem you're seeing when starting gdm?
[10:04] <lool> It hangs the system or it doesn't come up or...?
[10:04] <chih__> lool,  i did get "gdm-binary: WARNING: Unable to find users: no seat-id found" while system is hanging...
[10:05] <lool> Don't start "/usr/sbin/gdm"; use "sudo start gdm"
[10:05] <chih__> lool,  the x swirling cursor is running...
[10:05] <lool> In which case?  "sudo start gdm"?
[10:06] <chih__> lool,  and disk status light is still flashing. but i never got to the gdm login window.
[10:06] <chih__> lool,  whether it is through upstart or /usr/sbin/gdm
[10:07] <lool> chih__: Can you upload /var/log/gdm/* somewhere?
[10:07] <chih__> lool,  sure. hold on.
[10:09] <chih__> lool,  are you looking for any specific logs there or everything?
[10:10] <lool> chih__: All might be relevant, I dont know yet
[10:11] <chih__> lool,  ok. do you have an email address i can send it to?
[10:11] <lool> Cant you just upload it to a pastebin or something?
[10:11] <lool> Or people.c.c
[10:12] <chih__> lool,  ok
[10:14] <lool> chih__: start with gdm.log
[10:14] <lool> chih__: You know ubuntu-paste?
[10:14] <lool> chih__: apt-get install pastebinit
[10:14] <lool> alias ubuntu-paste='pastebinit -b http://paste.ubuntu.com'
[10:24] <lool> chih__: do you see xsplash during boot?
[10:24] <chih__> lool,  yes
[10:25] <lool> chih__: Do you see it when the session starts?
[10:25] <chih__> lool,  i don't quite get your question
[10:26] <lool> chih__: Can you paste the list of processesw
[10:26] <chih__> lool,  ok
[10:26] <lool> chih__: also .xsession-errors from the autologin user
[10:31] <chih__> lool,  .xsession-errors at http://paste.ubuntu.com/293009/
[10:31] <lool> chih__: Aha
[10:31] <chih__> lool,  :-)
[10:31] <lool> chih__: So your log shows UNR starting, that's not standard ubuntu at all
[10:32] <lool> chih__: Not only is it UNR, but it's not ubuntu's UNR; it's an enlightenment UNR
[10:32] <chih__> lool,  ah. ok. i didn't mean to have it running.
[10:33] <lool> chih__: and Xfce?!!
[10:33] <chih__> lool,  yep
[10:33] <lool> WTF is this setup??
[10:33] <ogra> lool, APM
[10:33] <lool> chih__: Is this xfce or unr or...?
[10:33] <chih__> lool,  the image happens to use xfce for some reason
[10:33] <lool> OMG
[10:33] <chih__> lool,  it is a unr launcher on top of xfce desktop
[10:33] <chih__> lool,  don't be
[10:33] <ogra> lool, it's an xfce desktop and the 2D efl thingie :)
[10:34] <chih__> lool,  :) i know it sounds like a mess...
[10:34] <chih__> lool,  should i remove unr and try again?
[10:34] <lool> chih__: Ok so disable autologin from gdm
[10:34] <lool> chih__: Use a recovery session (just starts an xterm) and launch things manually
[10:34] <chih__> lool,  ok. need your help here
[10:35] <lool> chih__: You could launch "xfce-session &" in that xterm for instance
[10:35] <lool> chih__: sudo vi /etc/gdm/*.conf
[10:35] <lool> chih__: Look for autologin
[10:35] <ogra> funny that the launcher defines itself as <unknown> :)
[10:35] <chih__> lool,  like running xinit directly?
[10:35] <lool> ogra: How do you know it's the launcher?
[10:35] <ogra> lool, because of the error messages
[10:36] <ogra> well, warnings rather
[10:36] <lool> ogra: Yeah, How do you know it's the launcher?
[10:36] <ogra> (<unknown>:1175): liblauncher-DEBUG: launcher-menu.c:361
[10:36] <lool> chih__: Or run startx if you like, but I'd recommend a gdm session instead
[10:36] <ogra> and the icon names sound very much like launcher icos as well
[10:36] <ogra> *icons
[10:37] <ogra> i suspect the fl libs got updated during the upgrade as well ?
[10:37] <ogra> *efl
[10:37] <chih__> lool,  ok. autologin disabled.
[10:38] <lool> chih__: Now you should get the gdm login screen and can select a xterm session and type in your username + password
[10:38] <ogra> EDJE: Error loading image collection "images/20" from file "/usr/share/netbook-launcher-efl/data/themes/default.edj". Missing EET Evas loader module?
[10:38] <lool> ogra: that's what I think as well
[10:39] <lool> chih__: So what's your goal exactly?  Running the same stuff as you ran on jaunty or running karmic xfce or karmic gnome?
[10:39] <ogra> karmic w3m ! minimalism FTW !! :)
[10:40] <chih__> lool,  oh. i am trying to help someone verify some packages that only seem to be available in karmic's arm port
[10:40] <lool> chih__: Could you be more precise?
[10:40] <lool> lots of packages in karmic
[10:42] <chih__> lool,  qt development tools/libraries to be exact
[10:45] <lool> chih__: Did you get to that xterm?
[10:45] <lool> chih__: So the issue seems pretty clearly related to the UNR 2D + Xfce stuff not starting in karmic anymore; it's likely this stuff needs to be rebased if you want to use it
[10:45] <lool> That's not in karmic though, so cant help much there
[10:46] <lool> chih__: What you can do is start other session types and test the qt libs from there
[10:46] <chih__> lool,  tried startx and failed
[10:46] <lool> chih__: startx will start the same session by default
[10:47] <chih__> lool,  so, can you show me how to start gdm-session alternatively?
[10:47] <lool> chih__: As I said, just select the other session from the gdm start screen
[10:47] <lool> chih__: You dont see the session type drop down on your gdm greeter?
[10:48] <chih__> lool,  ok. i haven't got to the greeter window yet
[10:48] <lool> chih__: You have a password set for your user?
[10:48] <chih__> lool,  yes.
[10:49] <chih__> lool,  i am still in console mode
[10:49] <lool> chih__: If yes, just "sudo stop gdm" and "sudo start gdm"
[10:49] <chih__> lool,  ok. trying...
[10:49] <lool> That should get you to the gdm greeter now that you turned off autologin
[10:50] <chih__> lool,  i got "gdm start/running, process XXXX" and nothing happened...
[10:50] <lool> chih__: Switch VT
[10:51] <chih__> lool,  negative. tried all the VT's. tty1~tty6
[10:51] <lool> chih__: It's on 7
[10:51] <lool> try alt + left arrow
[10:52] <chih__> lool,  uh. no tty7 for me
[10:52] <lool> chih__: just reboot, it should get gdm up on the greeter
[10:52] <lool> chih__: how did you diable autologin exactly>
[10:52] <lool> chih__: I need to drop off now
[10:52] <lool> ogra: ^ can you plesae pick it up
[10:52] <chih__> lool,  it is in /etc/gdm/gdm-cdd.conf
[10:52] <chih__> lool,  thanks for your help!
[11:02] <chih__> ogra,  there is another seemingly important message while booting up: "gdm spawning too fast, stop..."
[11:02] <ogra> ChanServ, sounds like your xserver cant start
[11:02] <ogra> err chih__ :)
[11:03] <chih__> ogra,  yeah?
[11:07] <ogra> chih__, so check /var/log/Xorg.0.log
[11:07] <chih__> ogra,  ok.
[11:07] <ogra> or dump it on the pastebin
[11:20] <chih__> ogra,  http://paste.ubuntu.com/293031/
[11:20] <chih__> ogra,  sorry for being a bit slow. network is on and off on this board... :(
[11:21] <ogra> mxc_ts The /dev/input/event* device nodes seem to be missing
[11:21] <ogra> hmm
[11:22] <ogra> that shouldnt stop X from coming up though
[11:22] <ogra> but it looks like udev issues
[11:22] <chih__> ogra,  x has been rock solid in jaunty though...
[11:22] <chih__> ogra,  ok...
[11:23] <ogra> likely caused by your kernel missing bits or pieces
[11:23] <ogra> gdm still didnt come up after reboot, right ?
[11:24] <chih__> ogra,  right. only got to see the xsplash and a running cursor
[11:24] <ogra> well, but that means X comes up
[11:24] <ogra> weird that gdm doesnt
[11:24] <chih__> ogra,  right!
[11:25] <chih__> ogra,  mmmm
[11:25] <ogra> do the following:
[11:25] <chih__> ok
[11:25] <ogra> echo xterm >~/.xsession
[11:25] <ogra> then try with startx
[11:25] <ogra> should get you at least an xterm up
[11:26] <chih__> i am in
[11:26] <chih__> ogra,  then...
[11:27] <ogra> ok, that proves it's not X at fault
[11:27] <chih__> yeah!
[11:28] <ogra> try running xfce4-session from  your xterm
[11:28] <chih__> ok....
[11:30] <chih__> Gconf error...
[11:31] <chih__> initializing gdu failed
[11:31] <ogra> but the session comes up ?
[11:32] <chih__> not completely. i saw the desktop background coming up
[11:32] <ogra> panels etc ?
[11:33] <chih__> ogra,  nope. still only xterm is there
[11:33] <ogra> no WM either ?
[11:33] <chih__> nope
[11:33] <chih__> xfce4 in karmic is seriously screwed?
[11:36] <ogra> nope
[11:36] <ogra> but i have no clue what the actual name of the xfce session has to be
[11:36] <chih__> ok...
[11:39] <ogra> NCommander, ^^^ wha do you need to run to get an xfce desktop ?
[11:40] <ogra> *what
[11:43] <ogra> chih__, ah, it's startxfce4 not xfce4-session
[11:43] <ogra> stop the process in the xterm and run startxfce4 instead
[11:44] <chih__> ok...
[11:47] <chih__> exactly the same as running xfce4-session
[11:48] <ogra> thats weird
[11:48] <ogra> can you paste your .xsession-errors again ?
[11:48] <chih__> sure
[11:50] <chih__> strangely. whenever system hangs for a considerable amount of time, i start to see "I/O error, dev sda, sector XXXXXXXX" "EXT3-fs error ..."
[11:50] <ogra> oh, that sounds like a kernel bug
[11:51] <chih__> ogra,  right. never had that in jaunty...
[11:51] <chih__> ogra,  oh oh. i am still using the jaunty kernel by the way
[11:51] <ogra> well, you are still using the same kernel, no ?
[11:51] <chih__> ogra,  yes. only upgraded the FS
[11:52] <chih__> ogra,  kernel is in SD card separate from FS
[11:52] <ogra> kernel is on SD ?
[11:52] <chih__> ogra,  which is in an external USB disk
[11:52] <ogra> ah
[11:52] <chih__> ogra,  right. the board only supports booting from kernel in SD
[11:52] <chih__> ogra,  ah?
[11:53] <ogra> i was about to ask about where the rootfs lives ... you answered that faster than i could ask ... thus "ah" :)
[11:53] <chih__> ogra,  oh actually...
[11:54] <chih__> ogra,  i was trying to upgrade to karmic by manually adding a "karmic" repo in sources.list and gradually went through "apt-get upgrade"...
[11:55] <chih__> ogra,  the system was fine during the first couple batches of updates
[11:55] <ogra> ugh
[11:55] <ogra> use update-manager for such things in the future
[11:55] <chih__> ogra,  i was able to enjoy all the rich packages in karmic that way
[11:55] <ogra> it has a cmdline tool as well
[11:55] <chih__> ogra,  till i updates some "core" stuff and then system wouldn't boot into x any more
[11:56] <chih__> ogra,  i think it was upstart related among other things...
[11:57] <chih__> ogra,  anyway, it is ok that i can't make it work completely
[11:57] <ogra> i heard rumours that upstart has issues when you run it without initramfs
[11:58] <ogra> since i'd never do that i cant verify
[11:58] <chih__> ogra,  after all, all i need are those karmic packages...
[11:58] <chih__> ogra,  i see
[11:58] <ogra> do you still see upstart errors on bootup ?
[11:58] <chih__> ogra,  i would go back to jaunty and only grab those packages as i usually did before
[11:58] <chih__> ogra,  yes. like "gdm spawning too fast..."
[11:59] <ogra> beyond that i mean
[11:59] <chih__> ogra,  nope.
[12:00] <chih__> ogra,  the system would hang trying to get to greeter window/gdm
[12:00] <chih__> ogra,  or i shouldn't say "hang", the disk was actually busy reading...
[12:01] <chih__> ogra,  until the "I/O error message" i mentioned earlier finally came out.
[12:02] <ogra> well, do you have an .xsession-errors excerpt for the test from xterm ?
[12:02] <chih__> ogra,  oh. hold on. i have to reboot the system...
[12:03]  * ogra has to run out for 30min or so
[12:05] <chih__> http://paste.ubuntu.com/293058/
[12:06] <chih__> by the way, i have since removed all netbook-launcher related packages....
[12:32] <NCommander> chih__, ogra, intsall xubuntu-desktop, then select Xfce from th eSessions list at GDM.
[12:32] <NCommander> argh
[14:10] <whazilla> hi how do i prepare and boot ubuntu on arm mmc bageleboard ?
[14:11] <whazilla> i got mini projector as hdmi screen
[14:23] <lool> whazilla: http://elinux.org/BeagleBoardUbuntu
[16:43] <Martyn1> Hmmm.
[16:44]  * armin76 checks his mail :)
[16:44] <Martyn1> armin76: Didn't send it.   I had an argument with the CEO yesterday about remote access
[16:44] <Martyn1> "Is it a partner, or company we are doing business with?"
[16:45] <Martyn1> it's going to take a bit for him to cool down, and for me to explain what a 'community developer' is
[16:45] <armin76> :(
[16:45] <Martyn1> he's a good guy, it's just that he is in the middle of Round A financing talks, and so he's touchy about IP, remote access, NDA's, etc.
[16:46] <armin76> np, thanks for trying though
[16:46] <Martyn1> now, to the business of getting Karmic Koala working
[16:46] <Martyn1> I have a serious problem with php5 .. we didn't build it with zlib enabled!
[16:47] <Martyn1> Downloading update from http://downloads.wordpress.org/plugin/wordpress-automatic-upgrade.1.2.5.zip. Unpacking the update. Abort class-pclzip.php : Missing zlib extensions
[16:47] <Martyn1> I was testing out wordpress on my BeagleServer, and ran into this problem.   turns out it's a can of worms
[16:47]  * armin76 blames NCommander 
[16:47] <Martyn1> zlib, as a whole, is missing.  PHP5 does seem to have been compiled with zlib support, but there is no php5-zlib plugin, nor is zlib.so part of the distribution
[17:12] <NCommander> armin76, what did I do O_O;
[17:12] <armin76> NCommander: you don't let me play with armv7!
[17:12] <NCommander> armin76, I gave you a shell over IPv6!
[17:13] <armin76> NCommander: but for only one day!
[17:21] <Martyn1> *groan*
[17:22] <Martyn1> NCommander: Speaking of v7, do you have 20 minutes or so to give me a helping hand?  I need to understand the PPA process of creating an arch
[17:23] <NCommander> Martyn, public PPAs are x86/x86_64 only
[17:23] <NCommander> Sorry :-/
[17:23] <NCommander> No way around that
[17:23] <Martyn1> I need to find a reliable way to build for v7, with NEON optimizations, for our A9
[17:24] <Martyn1> and that means finding a better way to recompile all of karmic.  I'm abandoning the launchpad system, because it's 1) baroque and 2) broken as all hell for me now
[17:24] <Martyn1> even though I had it working for a while
[17:25] <NCommander> Martyn, probably abuse wanna-build/buildd
[17:25] <NCommander> Martyn, hold on
[17:26] <NCommander> Martyn1, http://www.wzdftpd.net/trac/wiki/Debian/Buildd
[17:26] <NCommander> Martyn1, thats part of the Debian build systme, but its compatible with Ubuntu
[17:27] <Martyn1> sure, but only compatible.
[17:27] <Martyn1> Can I point buildd to the ubuntu repositories, and actually end up with a real karmic build?
[17:27] <NCommander> Martyn, yes
[17:28] <NCommander> Martyn, back in the days before Soyuz, I believe Ubuntu even used the same build infrastructure as Debian
[17:34] <Martyn1> Hmm
[17:34] <Martyn1> Worth a try, at least
[17:39] <lool> maen: I just reviewed the two patches from NCommander and will send them your way ASAP; one fixes the e2fsck issue
[17:40] <NCommander> lool, er, no, that one just fixes a conditional
[17:40] <NCommander> lool, the e2fsck one probably a more indepth fix :-/
[17:40] <lool> Ah
[17:40] <lool> Ok
[17:40] <NCommander> lool, I can try and run that one down if you want though
[17:40]  * NCommander isn't sure if upstream u-boot is affected or not
[17:40] <lool> No; maen's on it already
[17:41] <NCommander> maen, you mind trying to help me with UART booting again? I'd *really* like to get it to work
[17:53] <Martyn1> UART booting?
[17:53] <Martyn1> Is that broken?
[17:54] <Martyn1> We have it working here, but on our PBX system
[17:54] <Martyn1> (we're working on getting PXE support shoehorned into u-boot)
[17:54] <Martyn1> then pushed upstream
[17:55] <NCommander> Martyn, I just can't get it to work
[17:55] <NCommander> Martyn1, probably user error on my end, but damned if I can find the error
[21:04] <NCommander> maen, do you know if there are any known issues with the kernel on the Y0 locking up hard?