[05:42] *** tellnes has quit IRC (Ping timeout: 258 seconds)
[05:43] *** meingtsla has quit IRC (Ping timeout: 258 seconds)
[05:44] *** meingtsla has joined #arpnetworks
[05:51] *** tellnes has joined #arpnetworks
[05:57] *** dj_goku has quit IRC (Ping timeout: 272 seconds)
[06:22] *** dj_goku has joined #arpnetworks
[06:26] *** dj_goku has quit IRC (Read error: No route to host)
[06:27] *** dj_goku has joined #arpnetworks
[06:27] *** dj_goku has quit IRC (Changing host)
[06:27] *** dj_goku has joined #arpnetworks
[10:05] <mnathani> how does one diagnose and repair a case that is short circuting with the motherboard?
[10:14] <m0unds> is it shorting the board because of clearance w/standoffs and the board or something?
[10:16] <m0unds> like..does the board work if you try and run it w/cpu + ram outside the case?
[10:34] <JC_Denton> check for missing standoffs too
[10:34] <m0unds> ^
[10:34] <m0unds> yeah, that's what i was getting at
[10:35] <m0unds> it's an easy thing to overlook when assembling
[11:20] <mercutio> how do you know it's short circuiting anyawy?
[11:23] <mnathani> m0unds: works fine outside the case
[11:23] <mnathani> JC_Denton: standoffs came pre-attached to the case
[11:24] <mnathani> mercutio: its a guess - as the machine turns off right after you hit the power button to turn it on
[11:26] <mercutio> oh
[11:26] <mercutio> \that could be bad psu too
[11:26] <mercutio> with an existitng computer i'd guess it was the powersupply first
[11:26] <mercutio> as motherboard problems aer'nt usually fixable easily :)
[11:28] <mercutio> oh
[11:28] <mercutio> missing plugging in the extra cpu power can do that too mnathani
[11:28] <mercutio> if it's a new build
[11:36] <mercutio> i forgot to plug in extra power to video card once and had nothing on screen but i'm pretty sure it didn't power off straight away.
[11:42] <mnathani> it is a new build
[11:43] <m0unds> yeah
[11:43] <m0unds> i think the power off thing sounds like a signalling issue
[11:44] <m0unds> could be psu or mobo - if it powers off correctly with the board not seated in the case, but using the power button from the case it could be that something is contacting the tray under the board
[11:44] <m0unds> maybe a standoff in the wrong place or something
[12:25] *** medum has quit IRC (Ping timeout: 265 seconds)
[14:55] <mnathani> I just installed Ubuntu 14.10 Server on a Dual CPU Quad core AMD box with 32 gigs of RAM
[14:55] <mnathani> trying to get Xen working now
[14:56] <mnathani> not sure what the whole Dom0 / DomU is about
[14:56] <mnathani> and networking seems to be acting really wierd
[14:57] <mnathani> after rebooting once Xen was installed, I get an ip : 172.16.100.x but my local Lan is 10.10.x.y
[14:57] <mnathani> is there a transparent NAT?
[15:54] <brycec> "trying to get Xen working now" "not sure what the whole Dom0 / DomU is about" -- I gather this is your first time with Xen?
[15:57] <mercutio> mnathani: i don't use the bridging
[15:58] <mercutio> mnathani: but it's how most setups are done
[17:09] *** awyeah has quit IRC (Ping timeout: 240 seconds)
[17:09] *** awyeah has joined #arpnetworks
[18:43] *** mhoran has quit IRC (Quit: WeeChat 1.0.1)
[18:43] *** mhoran has joined #arpnetworks
[18:43] *** ChanServ sets mode: +o mhoran
[18:46] <mnathani> brycec: yup my first time experimenting with Xen
[18:47] <mnathani> mercutio: turned out I had selected setup this host for virtualization maybe kvm during setup so the nat came from there
[19:27] <mercutio> weird
[19:27] <mercutio> i use normal xen rather than ubuntu's stuff
[19:28] <mercutio> to me virtualisation is one of those areas i don't like weid random "intelligent" decisions
[23:20] *** dj_goku has quit IRC (Ping timeout: 244 seconds)
[23:35] *** dj_goku has joined #arpnetworks