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