[17:04] Does someone know how to send Ctrl-Alt-Fx under virtualbox? [17:07] plars, GrueMaster: Poke, I have a hang before the timezone selection screen in ubiquity under moblin remix if I chose anything else than English [17:07] Can you guys confirm? [17:07] (this is under virtualbox) [17:08] Which snapshot? Today's? [17:08] Yes [17:08] Downloading now. Will check when it finishes. [17:09] lool: no, I got past there with today's snapshot just fine [17:10] lool: also under virtual box [17:11] lool: Ctrl-Alt-Fx> Fx, where here defaults to [17:12] lool: is the battery in your b2.5 good? [17:13] plars: I installed on 2.0 for now; need to test 2.5 now [17:13] lool: if your battery is good, can you see if it still preserves the clock? [17:13] sbeattie: thanks! [17:14] plars: yes [17:14] lool: mine is not, but could be just that my battery has recently died [17:14] An ARM person told me ethernet wasn't working with babbage 2.0 :-( [17:14] and I don't have my voltmeter handy at the moment [17:14] plars: moblin > had you tried with non-english? [17:15] plars: Just rebooting into the installed system, I have date/time issues on 2.0 [17:15] lool: no, only english sorry [17:17] lool: let me try non-english real quick [17:18] Ouch I see moblin-remix pulls langpacks during install even when one selects english [17:23] Fuck, system date expired my password and I cant login [17:25] I did a ctrl-alt-del shutdown of Babbage 2.0 and it doesn't come up anymore... [17:28] lool: I tried it in French also, and I also get past the tz select screen [17:28] plars: Ok cool thanks [17:28] plars: in vbox still? [17:28] lool: yep [18:08] NCommander: awake? === playya__ is now known as playya [18:15] plars, GrueMaster: Do you guys see output on the serial console when booting babbage boards? [18:16] Briefly. [18:16] Default doesn't put much out. [18:16] lool: when I redirect to the console, yes [18:17] plars: I mean bootloader [18:17] bootloader, yes. [18:17] why? [18:17] I dont see anything [18:18] Only booting SDHC0 [18:18] And not even always [18:18] Hmm you guys have 2.0 [18:18] JamieBennett: what about you [18:18] err 2.5 [18:18] lool: I only have 2.5 [18:18] Jamie has 2.0 [18:19] GRAH [18:19] serial cable had simply moved out [18:19] lool: you don't even get output from redboot? [18:19] ah [18:20] wow, I was going to say you probably cooked your board or something :) [18:20] Sorry, just back I do have a 2.0 [18:20] I hate you real world [18:20] * JamieBennett reads backchat [18:20] JamieBennett: dont bother [18:20] I wasn't going to suggest that you plug it in. "P [18:20] :P [18:21] funny that you got as far as the first message, then nothing after that [18:21] Now Xorg wont come up anymore for me on Babbage 2.0 [18:21] Hmm probably a date issue [18:24] lool: :) just read the back chat, if in doubt always blame the hardware first [18:24] Eh if you use init=/bin/sh you have to ctrl-alt-f7 to talk to the shell [18:28] JamieBennett: How do you reset the time after install of a babbage 2.0? [18:29] After the time resets you have to drop to the console and use date (if you can boot to X that is) [18:30] JamieBennett: I cant boot to X and I dont have sudo either [18:30] It fails due to the time skew [18:30] lool: I haven't experienced that. Even though the time resets I've always been able to boot to X [18:30] I can give todays image a try though [18:31] please do [18:31] lool: OK [18:31] downloading now [18:32] are you at home? [18:32] lool: yes, why? [18:32] JamieBennett: Ok just wondering [18:32] :) [18:32] JamieBennett: I mean you're expected to be doing RC testing anyway :) [18:33] Not at 6:30pm :P [18:33] Farming the kids off to bed in 30 minutes so I'll devote some more time tonight to testing [18:33] Eh right [18:34] lool: normally the time skew doesn't cause *that* bad of problems for me... just that it makes me change my password every time I login, or use sudo [18:35] plars: exactly what I was getting (last tested a couple of days ago) [18:35] Perhaps sudo -i would work [18:36] plars: password reset every login until you set the date then its fine until you take the power away [18:37] JamieBennett: right, that bug is supposed to be fixed though :( [18:37] plars: I'm going to test in T minus 10 minutes :) [18:37] (download time) [18:40] Oh it kept the date once [18:40] Ah no [18:40] it ntped [18:40] lool: I reopened it [18:40] lool: also I looked at the kernel from yesterday, and it still seems to contain the fixes that were in that changeset [18:42] GrueMaster: are you able to make it through the dove install? [18:42] I'm dying with InstallStepError in configure_bootloader() [18:43] could be related to NCommander stuff he did on partman? maybe? [18:43] Haven't gotten to that platform yet. Just finishing up unr & imx51 install testing. [18:44] If I use startx, the server comes up fine [18:46] and if I start gdm it doesn't [18:52] Ok got it [18:53] my 2.5 doesn't boot if I pull too much power with too many devices up [18:54] lool: ? Does that mean you solved your problem ? (installing todays image now) [18:56] JamieBennett: No :-( [18:56] I gave up on babbage 2.0 to see how a 2.5 behaves for me [18:57] I saw /var/log/gdm/(null).log files and thought it was looking bad [18:58] lool: OK leave it with me. I'll see what my board does [19:03] lool: live cd has pulled up the right time, I presume from the last install and the battery backup [19:03] installing a full system now [19:04] (and its been unplugged for at least 2 days) [19:04] JamieBennett: If you have network plugged in, it ntp-ed it [19:09] lool: confirmed. Removed eth cable, unplugged, rebooted live cd, back to Jan 1st 1970. [19:11] Also why is it so hard to click on London in Ubiquity? [19:17] :-( [19:17] JamieBennett: Do you get gdm to startup on an installed system? [19:17] JamieBennett: Also could you check ls /var/log/gdm for funny names like mine [19:28] lool: still installing but I'll check === asac_ is now known as asac [20:40] plars: I had a successful time keep on 2.5 [20:40] plars: I only unplugged for 10 seconds [20:40] But I unplugged everything [20:40] and booted without network and time/date was kept [20:46] lool: booted the installed image, saw GDM briefly then blank screen :( [20:46] Oh you did see it [20:46] JamieBennett: I personally suspect the depth changes [20:47] JamieBennett: I think I'll try with mxcfb on the cmdline [20:47] JamieBennett: Did you manage to login etc.? [20:47] lool: saw the image but no text i.e. the box, backdrop but nothing else then flickered out [20:47] no, saw it for 1/2 second or so [20:48] JamieBennett: Sorry, I mean can you fix the time/date frm console? [20:48] Cause I found it quite hard to workaround the date/time issues [20:50] can't even login in at the moment (from another console). Its not accepting the password I set it to [20:51] lool: so are you thinking that all of our batteries are just failing? [20:57] lool, date from the console worked fine [20:58] (with a sudo and a password change again) [21:02] plars: So you lost hte date? [21:03] lool: yes, that's what I was saying this morning [21:03] plars: I kept my 2.5 off for 10 minutes or so and it kept time/date [21:03] plars: Who else has the issue? [21:04] plars: We see the issue JamieBennett and I on 2.0, but I kind of expected that it would be poorly supported [21:04] plars: Might be good to test your voltage [21:04] lool: ah, this morning it sounded like you were also having the clock issue [21:04] So we have failing batteries again? Was is ever fixed? [21:04] plars: One thing you might want to try is booting the board without network and DVI and plugging them after some 5 seconds [21:04] plars: I had it ... on 2.0 [21:04] plars: But 2.0 is so broken, you can't imagine [21:04] plars: And I think I found my problem with 2.5 [21:05] plars: What I thought were corruptions aren't [21:05] What was happening was a heisenbug which resolved itself after I rewrote my SD card [21:05] ok, really hoping this is just my battery [21:05] But actually it didn't change anything [21:05] * JamieBennett waits for a 2.5 next week [21:05] I just had luck booting the second time [21:05] Now I can consistenly boot my 2.5 fine IF I unplug network and DVI [21:06] If I keep them both, it often fails [21:06] lool: what about if you just keep one of them? [21:07] lool: did you ever solder those connections for the ground issue? could be the same thing we saw before on the network [21:07] plars: I need to try; I had the impression network was a worse offender and it's brought up by redboot [21:07] oh, so you're getting power on, just failing later [21:08] I'm pretty sure redboot doens't touch dvi so I would blame the network powe consumption, unless power is misconfigured on shutdown and the config is preserved across power off [21:08] I never soldered the grounding stuff [21:08] True [21:08] I wonder whether I should be soldering by 2.0 now [21:09] I'm a software guy! I'll try mxcfb= first :-P [21:09] God it's 10pm and I didn't manage to test UNR and Dove yet [21:10] lool: I just managed to finish installing dove, hit a ubiquity issue [21:11] I was wondering if it was due to the new stuff michael worked on, but the second time through it worked for me [21:11] we'll see if it boots now [21:14] plars: I could boot 2.5 with just network unplugged; not a 100% test but it looks like it's the main issue [21:15] JamieBennett: are you using a USB hub? [21:15] for keyboard and mouse only [21:15] thumb drive is plugged directly in [21:16] I wonder whether it's causing the excessive power pull [21:17] I reproduced the IO errors on SATA port with the new cables [21:17] Cursor spins, then if I try to switch to console it hangs and I can't SSH [21:19] * lool hugs his 2.5 [22:19] hmm. io errors with sata cabels? i'm fighting with this error, too [22:19] already ran a fsck for days without a result [22:20] lool, do you think i should exchange my cables? [22:28] playya: You have a Babbage 2.x? [22:28] playya: We have a very specific issue with Babbage boards; it doesn't relate to the cables but we need special cables to use its SATA port [22:28] The port works fine most of the time, except when opening a GNOME session [22:35] lool, ah ok. i have a problem with a MyBook disk on my PC :(