| 03:37.35 | *** join/#debianppc Bor_Ed (~ari@adsl-065-013-147-133.sip.msy.bellsouth.net) |
| 04:22.19 | *** join/#debianppc _Trinity_ (~jircii@pc-72-94-160-190.cm.vtr.net) |
| 04:22.22 | _Trinity_ | hi |
| 04:22.26 | _Trinity_ | anyone home? |
| 04:23.22 | pahartik | Hello _Trinity_ |
| 05:45.47 | _Trinity_ | Debian boots and just prior to starting gdm, the CRT screen goes black on my iMac DV |
| 05:46.08 | _Trinity_ | light is on throughout this |
| 05:46.46 | _Trinity_ | reset pram and disconnected peripherals to no avail |
| 05:49.40 | _Trinity_ | I'm thinking it's ether over heating or there is bad ram, despite that the hd is sluggish on start up. hd according to smartctl |
| 05:55.30 | pahartik | _Trinity_: Can you switch back to another virtual terminal from X11 server? |
| 05:56.50 | pahartik | _Trinity_: Try to toggle selection whether X11 server should use kernel framebuffer interface to set display mode |
| 06:01.06 | _Trinity_ | I can't get into any console. The keyboard doesn't veen respond to anything. The caps lock button doesn't even light up the corresponding light. |
| 06:01.43 | _Trinity_ | on the keyboard |
| 06:02.56 | _Trinity_ | RAM, overheating or faulty battery,is what I'm thinking. I thought it was a faulty video car at one point but that doesn't explain the unresponsiive keyboard |
| 06:04.42 | _Trinity_ | It should not be bad ram though, as these mac beeped when there was bad ram or RAM slots --still I've read that bad ram got through that safeguard |
| 06:06.14 | _Trinity_ | of course it could be hte flyback but thhose were aproblem on hte first generation iMacs and mine came in 1999/2000 --so it shouldn't be that either. |
| 06:42.16 | pahartik | _Trinity_: Start without running X11 server to investigate |
| 06:45.42 | pahartik | _Trinity_: On my experimental PowerMacintosh workstation, <CapsLock> LED is not active when toggling state of <CapsLock> on console without X11 server |
| 06:53.13 | *** join/#debianppc vaidy (~sv@59.92.203.120) |
| 07:27.05 | _Trinity_ | can't get it bootednow. Sounds like a broken record trying to get started but doesn't and it just shuts itself off with a quiet boom sound |
| 07:27.29 | _Trinity_ | I'll see if I can clear the pram again in the morning |
| 07:33.40 | _Trinity_ | which leads me to believe it's not an X thing if it barely makes it past the chime now, and it isn't overheating considering that it ressted for hours before trying to boot again. That leaves battery and RAM as culprits |
| 07:34.25 | _Trinity_ | assuming the gdm not showing is related to it barely making it past the chime |
| 07:36.39 | _Trinity_ | and het date command reported the correct time after subsequent boots so that leaves RAM --and not a faulty board is the vga external owrks, according to one reading |
| 09:43.44 | *** join/#debianppc simonrvn (simon@209.62-ppp.3menatwork.com) |
| 09:44.16 | *** join/#debianppc ravenbird (simon@unaffiliated/simonrvn/bot/ravenbird) |
| 15:41.21 | *** join/#debianppc vaidy (~sv@59.92.203.120) |
| 16:13.05 | *** join/#debianppc simonrvn (simon@209.62-ppp.3menatwork.com) |
| 16:13.36 | *** join/#debianppc ravenbird (simon@unaffiliated/simonrvn/bot/ravenbird) |
| 16:43.46 | *** join/#debianppc hramrach (debian-tor@gateway/tor-sasl/hramrach) |
| 17:49.31 | *** join/#debianppc tilmann (~tilmann@p5B2F7671.dip.t-dialin.net) |
| 18:56.09 | *** join/#debianppc hramrach (debian-tor@gateway/tor-sasl/hramrach) |
| 20:27.47 | *** part/#debianppc hramrach (debian-tor@gateway/tor-sasl/hramrach) |