• Re: Strange PC Video Fault

    From Java Jive@21:1/5 to All on Tue Aug 6 23:06:03 2024
    XPost: alt.os.linux, alt.windows7.general

    On 02/08/2024 15:01, NY wrote:

    On 02/08/2024 00:21, Java Jive wrote:

    As I did not dare to try to disconnect the screen end of the cable,
    because it looked complicated and was covered with "Don't touch!"
    stickers, but I did remove and replace the motherboard end, my best
    guess now is that the motherboard end of the cable, through a process
    of heating up and cooling down, had walked itself partly out of its
    connecting socket.  Supposedly this should have been prevented by it
    being held in place by sticky tape, but maybe that allows some creep
    when it warms up.

    However that may be, hopefully when the replacement plastic arrives
    I'll be able to restore the laptop to a fully working state.

    Arrived today, laptop now fixed, all seemingly well, at least for the
    moment I have 'feature'-free display.

    As for what follows, yes, I agree completely.

    Good luck with getting the screen working again. There was a time when laptops were assembled in a way that made it easy to disassemble them.
    They had little access doors, held in place with a single screw, to get
    at the RAM DIMMs, the hard drive, and to slide out the CD or DVD drive.
    If you did need to remove the whole "lid", it was held on by lots of
    very obvious screws on the underside. The battery was held in place by a couple of slide locks and could be removed and replaced with a new one
    in a few seconds. You didn't have to use a spudger to release plastic spring-clips, or have to remove the keyboard to get at screws hidden underneath.

    But nowadays everything is fitted for life, and there is no expectation
    that the owner or a repair technician can swap out defective parts as
    they could with a desktop PC. When (not if) my present laptop battery
    stops holding its charge, goodness knows how I will get to the battery
    to replace it. The underside of the laptop only has two screws at one
    corner, so unless *all* the screws are hidden under the rubber strips
    that constitute the feet, then everything is held in place by clips or
    by screws that require access from the keyboard side.

    The entirety of the bottom plate of the Dell Precision M6700s is held in
    by 2 screws + a raft of metal tongues. To remove it, you take out the
    battery, undo the two screws, and then slide the cover about 2-3 mms
    forward or backwards (I can't remember which, and they're both running
    just now, so I don't want to disturb them) which frees the tongues and
    and the entire bottom can be just lifted away, revealing 2 of the 4 RAM
    slots, the other 2 are under the keyboard, the fans, the card slots, and
    the HD mountings - a *HUGE* improvement on both this Inspiron and the
    older Precision M6300s.

    Both the Inspiron and the Precision M6300s have reasonably accessible
    RAM and HDs, and the M6300s also have easily accessible card slots, but
    there ends convenience of upgrade or repair for either.

    With the Inspiron, you have to take the palm-rest off to get at the
    card-slots, or rather, mostly, the single slot, because in that model
    Dell were so mean that they didn't actually include the second-slot
    unless you specifically ordered a model with a card-style SSD - on the
    other models, the vast majority, the circuitry seems all to be there for
    the second slot, but they decided to save a few fractions of a cent by
    not having the second slot soldered into its place on the daughterboard.
    So, even if you were willing and able to go to the trouble of a
    near-complete dismantling of the PC to upgrade it with a card SSD, you couldn't, unless you were also willing to try your hand at soldering the
    second slot into place, or else were lucky enough to be able to find a replacement daughterboard with the 2nd slot, which seem to be as rare as
    hens' teeth.

    The Precision M6300's fans tend to get very noisy when they get old, as
    do the Inspiron's single fan, though for me at least its noise was
    rather more bearable than the other, but, despite the fact that fans are
    moving parts and therefore a need to change them is absolutely
    predictable, with both a near-complete dismantling of the laptop is
    required to do so.

    The Inspiron has been particularly bad in this respect, the laptop
    equivalent of the Citroen GSA models which cost a fortune in garage fees because everything was so densely packed under the bonnet that you
    couldn't do anything without removing something else first. Hopefully
    never again will I have ever to work on either!

    I do PC repairs for a living but I won't touch laptops if it's a
    hardware problem that requires the back to be removed, because of fear
    that I will break some fragile clip. Let some other poor sod attempt
    that work!

    In the "olden days", if a laptop failed to boot, a last resort was to
    remove the HDD, connect it as a slave drive via a USB-to-SATA or
    USB-to-IDE caddy interface, and read the user files in
    c:\users\<username> once Windows had gone through the lengthy "take ownership" process - assuming the user hadn't encrypted the drive. But
    if you can't get at the HDD, you're stuffed.

    Yes, and, one of the stupidest ever defaults of most recent versions of Windows, if you get a bluescreen it's been and gone before you can
    possibly read it as the laptop goes into an endless cycle of rebooting
    - the only way you can read the details on the screen is to video it
    with a mobile phone and try, probably several times before you are
    lucky, to freeze the playback at exactly the right moment to be able to
    read it. That most stupid of defaults is always one of the first things
    I change on any new installation of Windows.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Java Jive on Tue Aug 6 19:05:01 2024
    XPost: alt.os.linux, alt.windows7.general

    On Tue, 8/6/2024 6:06 PM, Java Jive wrote:


    Yes, and, one of the stupidest ever defaults of most recent versions of Windows, if you get a bluescreen it's been and gone before you can possibly read it as the laptop goes into an endless cycle of rebooting -  the only way you can read the details
    on the screen is to video it with a mobile phone and try, probably several times before you are lucky, to freeze the playback at exactly the right moment to be able to read it.  That most stupid of defaults is always one of the first things I change on
    any new installation of Windows.

    There is a setting for that. Disable "automatic restart" or so.
    This causes the blue screen to stand still. Then you can get out
    your magnifying glass, and read that annoying five point font
    the idiots selected for the code.

    That could be in sysdm.cpl somewhere.

    [Picture]

    https://i.postimg.cc/sghZL2h2/automatically-restart.gif

    Dump files can be read with dumpchk.exe , one of the early
    tools from MSFT to read a minidump. Windbg (available
    separately as a Visual Studio sub-feature) can read dumps
    or full memory dumps, in a similar manner to dumpchk. !analyze
    Windbg has a comment, right in the interface, what to use...

    Third party tools (BlueScreenViewer) also exist, but
    occasionally they don't know where the .dmp files are.

    After you have set up your crash response. you can test it.

    https://learn.microsoft.com/en-us/sysinternals/downloads/notmyfault

    The one on the display there, that ought to do it. Close
    all your Notepads, MSWDs, Firefox, make sure anything of
    value is put away. Right after a full backup, might be
    a good time for a test. The "High IRQL fault" should
    blow a similarly named Blue Screen for you. The Reliability
    Monitor will then have an entry for NotMyFault.exe as the
    thing that dropped the system or created a .dmp. Russinovich+Co
    wrote that for us.

    If you're bored, you can have a lot of fun making minidmps
    and testing viewers and such.

    Note that, if you encourage the system to dump all memory,
    the writing of the memory to some place on C: , is
    excruciatingly slow. You will have regrets about
    some of those options. But I don't see the "mini dump"
    option in the pictured one, so I guess the system
    knows when it's supposed to make a small one.
    If you have hiberfile turned off, there's no place to store a big dump.

    powercfg /h off # Can't hibernate, also "can't take a dump"
    # Minidmp .dmp files could be 100KB.

    I am trying to remember why I do *NOT* have
    this option selected (BSOD stand still). The automatic restart
    might be "cleaner". But when you don't have hints, and the
    problem is re-producible, you might use this. If the system can
    produce a BSOD, maybe it can manage to log it. Eventvwr.msc might
    contain the code. Or reliability monitor.

    For the problems I was having with the Zen3 processor, the system just halted, and the event viewer only reported a dirty shutdown had occurred (no log).
    It felt like the BIOS was halting it (on an SMI/SMM). There
    was no MCE logged (Machine Check Error), so whatever the problem
    (Vcore?), it was not something tied to MCE. I'm not used to weirdness
    like that (the lack of documentation does not help). There is always
    something on computers, you've never seen before. The processor (so far)
    runs fine on a different mobo. Great, I guess.

    You would be surprised on computers, how many features and
    codes are not documented. The mobo makers are sloppy, because
    they're designing 30 of the stupid things in parallel every year,
    and there is no time for frippery. That's how they can have BIOS
    manuals today, that apply to a whole bunch of boards, rather than
    just one board.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Java Jive on Wed Aug 7 11:21:19 2024
    XPost: alt.os.linux, alt.windows7.general

    On 06/08/2024 23:06, Java Jive wrote:

    On 02/08/2024 00:21, Java Jive wrote:

    However that may be, hopefully when the replacement plastic arrives
    I'll be able to restore the laptop to a fully working state.

    Arrived today, laptop now fixed, all seemingly well, at least for the
    moment I have 'feature'-free display.

    Spoke too soon, there is now some sort of smudge of darker pixels in the
    centre of the screen that won't wipe off, and I'm not sure what I did
    wrong to cause it (it's much more obvious in real life than this photo suggests):

    www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Smudge.jpg

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to All on Wed Jul 31 13:22:05 2024
    XPost: alt.os.linux, alt.windows7.general

    This is a deliberate cross-post concerning a presumed hardware problem.

    This happened on turning on this laptop this morning, it's a Dell
    Inspiron 15RSE 7520:

    www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Video_Fault.jpg

    The pattern is rather unusual. In the past, nearly always I've seen
    video faults that concern one of the primary colours ...
    Dead red = cyan (turquoise) cast
    Dead green = magenta (purple) cast
    Dead blue = yellow cast
    ... but this patterning is rather different.

    And it's not constant, but changes over time, for example it changed
    somewhat as I moved the mouse, and in fact for a while now it's gone altogether. I suspect that temperature may have played a part in its appearance immediately on switching on and its subsequent disappearance
    as the PC warmed up, a loose connection possibly.

    Or the screen or the video card is dying.

    Does anyone recognise the rather unusual patterning and can be more
    specific in their diagnosis?

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From sticks@21:1/5 to Java Jive on Wed Jul 31 08:30:53 2024
    XPost: alt.os.linux, alt.windows7.general

    On 7/31/2024 7:22 AM, Java Jive wrote:
    This is a deliberate cross-post concerning a presumed hardware problem.

    This happened on turning on this laptop this morning, it's a Dell
    Inspiron 15RSE 7520:

      www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Video_Fault.jpg

    I get this


    Hmm. We’re having trouble finding that site.

    We can’t connect to the server at www.macfh.co.uk.


    --
    Stand With Israel!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Java Jive on Wed Jul 31 09:54:21 2024
    XPost: alt.os.linux, alt.windows7.general

    On Wed, 7/31/2024 8:22 AM, Java Jive wrote:
    This is a deliberate cross-post concerning a presumed hardware problem.

    This happened on turning on this laptop this morning, it's a Dell Inspiron 15RSE 7520:

      www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Video_Fault.jpg

    The pattern is rather unusual.  In the past, nearly always I've seen video faults that concern one of the primary colours ...
      Dead red = cyan (turquoise) cast
      Dead green = magenta (purple) cast
      Dead blue = yellow cast
    ... but this patterning is rather different.

    And it's not constant, but changes over time, for example it changed somewhat as I moved the mouse, and in fact for a while now it's gone altogether.  I suspect that temperature may have played a part in its appearance immediately on switching on and
    its subsequent disappearance as the PC warmed up, a loose connection possibly.

    Or the screen or the video card is dying.

    Does anyone recognise the rather unusual patterning and can be more specific in their diagnosis?


    Intel HD 4000 Integrated graphics and AMD Radeon HD 7730m

    There are various reports of issues with these specific Radeon graphics. You are not alone.

    Radeon HD 7730M April 2012 GCN 1st gen (28 nm) 512:32:16:8 2GB GDDR3 128 bit
    (Chelsea LP)

    So that could be a chip with four RAM soldered to the top, 512MB GDDR3 chips with 32 bit interfaces.
    RAM come in 8 bit, 16 bit, 32 bit versions, and can share
    a common ball pattern on the bottom. So the 8 bit RAM, 24 signals
    would be "no-connect". That sort of thing.

    The effect might stop, if you turn off the AMD graphics.

    The way the two GPU "share", is one GPU makes an image and
    dumps it into the shared system RAM the other GPU uses, and
    it displays the contents of that shared area. Only one GPU
    drives the TMDS cable (likely the Intel HD 4000), and if/when
    the AMD is running, the software changes the pointer location
    to the frame buffer the TMDS-driving GPU is using.

    Occasionally on an AMD, there is a fabrication issue with the
    mounting of RAM over top of the GPU chip.

    But your pattern is not suggestive of a recognizable pattern.
    It's not uninitialized RAM. The pattern for that is filled with
    "more rectangular constructs". Your image looks like a photograph
    previously occupied the memory, and now is being displayed in false
    colours.

    I don't know how they do scaling on panels, if at all. Maybe
    a panel with a TMDS cable, only runs native ? And everything
    else is fudged via GPU ? Regular LCD monitors can have scalers
    to support multisync (a scaler chip can fail). And panel electrical
    driver failures, make lines on the screen. Pixel rows or pixel columns.
    The pattern is not a match for a panel problem.

    I'd say the AMD GPU is croaking, and it should be switched off.
    It could be a cracked ball on the bottom of the fine pitch BGA
    AMD chip, or a problem with the solder between the AMD chip
    and the complement of RAM riding on top of it.

    All that (logically) switching it off does, is removes software
    usage of it. If the thing had an electrical problem, it could
    burn whether logically on or logically off. It could be an
    intermittent connection (cracked ball). Or even one of the
    four RAM chips on the lid, is failing (thermally induced failure
    or mechanical pressure induced failure). They have fancy ways
    of packaging silicon today, that are much more aggressive
    in terms of causing problems (HBM near some GPUs, die height).

    Some laptop GPUs are MXM style. There is a conventional GPU
    and it is surrounded by RAM chips, similar to how a PCIe card
    does it. MXM can be unplugged. But they're high power devices,
    merit a separate blower, and the laptop sucks down battery
    so bad, you leave those plugged in at your desk. That's an example
    of a laptop GPU you can repair, by replacing it. Your machine
    might need a hot air station, to fix.

    Whereas the dual-GPU mid range laptops, there can be
    a soldered down GPU chip. Does not take nearly as much X-Y space
    inside the chassis. Needs a heatpipe for cooling. And if there
    is VRAM (it does not absolutely need to have VRAM), sometimes
    the packaging method leaves a bit to be desired. Just the way it was
    soldered and underfilled at the factory, could be part
    of the (eventual) problem.

    heatpipe ---------------> heat to blower area
    RAMx4 (quadrants)
    GPU
    (underfill)
    PCB

    A laptop which only had the HD 4000 graphics, would be
    pretty useless for gaming (SIMS level), but it would
    have the benefit of being less failure prone.

    The AMD GPU is 25-28 watts (listed in Wikipedia). And that would
    be flat out, with a tail wind. Furmark thermal rating. GPUs
    from that era are not closed loop control, which is why
    the usage of Furmark had to be detected manually and
    the driver would turn down the clock :-) That's to prevent
    thermal mayhem. Both CPUs and GPUs today, have power limiters.
    We may not like the settings they used for those power limits,
    but, they have power limits. Like your desktop 4090 at 450 watts
    or 600 watts. That sort of thing.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to Java Jive on Wed Jul 31 11:18:53 2024
    XPost: alt.os.linux, alt.windows7.general

    On Wed, 31 Jul 2024 13:22:05 +0100, Java Jive <java@evij.com.invalid> wrote:

    This is a deliberate cross-post concerning a presumed hardware problem.

    This happened on turning on this laptop this morning, it's a Dell
    Inspiron 15RSE 7520:

    www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Video_Fault.jpg

    The pattern is rather unusual. In the past, nearly always I've seen
    video faults that concern one of the primary colours ...
    Dead red = cyan (turquoise) cast
    Dead green = magenta (purple) cast
    Dead blue = yellow cast
    ... but this patterning is rather different.

    And it's not constant, but changes over time, for example it changed
    somewhat as I moved the mouse, and in fact for a while now it's gone >altogether. I suspect that temperature may have played a part in its >appearance immediately on switching on and its subsequent disappearance
    as the PC warmed up, a loose connection possibly.

    Or the screen or the video card is dying.

    Does anyone recognise the rather unusual patterning and can be more
    specific in their diagnosis?

    I have the same model of laptop, in continuous 24x7 service since early 2012. No
    video issues so far.

    What would you think about temporarily connecting a second display to the laptop*, with the idea being that it may help to determine whether you have a display panel issue or a GPU issue. I would think that a panel issue is a bit more likely.

    *There should be an HDMI connector and a VGA connector on the left side. I use VGA to drive a second display, but I've used HDMI in the past and it also works fine.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Paul on Wed Jul 31 20:09:13 2024
    XPost: alt.os.linux, alt.windows7.general

    On 31/07/2024 14:54, Paul wrote:
    On Wed, 7/31/2024 8:22 AM, Java Jive wrote:
    This is a deliberate cross-post concerning a presumed hardware problem.

    This happened on turning on this laptop this morning, it's a Dell Inspiron 15RSE 7520:

      www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Video_Fault.jpg >>
    The pattern is rather unusual.  In the past, nearly always I've seen video faults that concern one of the primary colours ...
      Dead red = cyan (turquoise) cast
      Dead green = magenta (purple) cast
      Dead blue = yellow cast
    ... but this patterning is rather different.

    And it's not constant, but changes over time, for example it changed somewhat as I moved the mouse, and in fact for a while now it's gone altogether.  I suspect that temperature may have played a part in its appearance immediately on switching on and
    its subsequent disappearance as the PC warmed up, a loose connection possibly. >>
    Or the screen or the video card is dying.

    Does anyone recognise the rather unusual patterning and can be more specific in their diagnosis?


    Intel HD 4000 Integrated graphics and AMD Radeon HD 7730m

    There are various reports of issues with these specific Radeon graphics. You are not alone.

    Radeon HD 7730M April 2012 GCN 1st gen (28 nm) 512:32:16:8 2GB GDDR3 128 bit
    (Chelsea LP)

    So that could be a chip with four RAM soldered to the top, 512MB GDDR3 chips with 32 bit interfaces.
    RAM come in 8 bit, 16 bit, 32 bit versions, and can share
    a common ball pattern on the bottom. So the 8 bit RAM, 24 signals
    would be "no-connect". That sort of thing.

    The effect might stop, if you turn off the AMD graphics.

    The way the two GPU "share", is one GPU makes an image and
    dumps it into the shared system RAM the other GPU uses, and
    it displays the contents of that shared area. Only one GPU
    drives the TMDS cable (likely the Intel HD 4000), and if/when
    the AMD is running, the software changes the pointer location
    to the frame buffer the TMDS-driving GPU is using.

    Occasionally on an AMD, there is a fabrication issue with the
    mounting of RAM over top of the GPU chip.

    But your pattern is not suggestive of a recognizable pattern.
    It's not uninitialized RAM. The pattern for that is filled with
    "more rectangular constructs". Your image looks like a photograph
    previously occupied the memory, and now is being displayed in false
    colours.

    I don't know how they do scaling on panels, if at all. Maybe
    a panel with a TMDS cable, only runs native ? And everything
    else is fudged via GPU ? Regular LCD monitors can have scalers
    to support multisync (a scaler chip can fail). And panel electrical
    driver failures, make lines on the screen. Pixel rows or pixel columns.
    The pattern is not a match for a panel problem.

    I'd say the AMD GPU is croaking, and it should be switched off.
    It could be a cracked ball on the bottom of the fine pitch BGA
    AMD chip, or a problem with the solder between the AMD chip
    and the complement of RAM riding on top of it.

    All that (logically) switching it off does, is removes software
    usage of it. If the thing had an electrical problem, it could
    burn whether logically on or logically off. It could be an
    intermittent connection (cracked ball). Or even one of the
    four RAM chips on the lid, is failing (thermally induced failure
    or mechanical pressure induced failure). They have fancy ways
    of packaging silicon today, that are much more aggressive
    in terms of causing problems (HBM near some GPUs, die height).

    Some laptop GPUs are MXM style. There is a conventional GPU
    and it is surrounded by RAM chips, similar to how a PCIe card
    does it. MXM can be unplugged. But they're high power devices,
    merit a separate blower, and the laptop sucks down battery
    so bad, you leave those plugged in at your desk. That's an example
    of a laptop GPU you can repair, by replacing it. Your machine
    might need a hot air station, to fix.

    Whereas the dual-GPU mid range laptops, there can be
    a soldered down GPU chip. Does not take nearly as much X-Y space
    inside the chassis. Needs a heatpipe for cooling. And if there
    is VRAM (it does not absolutely need to have VRAM), sometimes
    the packaging method leaves a bit to be desired. Just the way it was
    soldered and underfilled at the factory, could be part
    of the (eventual) problem.

    heatpipe ---------------> heat to blower area
    RAMx4 (quadrants)
    GPU
    (underfill)
    PCB

    A laptop which only had the HD 4000 graphics, would be
    pretty useless for gaming (SIMS level), but it would
    have the benefit of being less failure prone.

    The AMD GPU is 25-28 watts (listed in Wikipedia). And that would
    be flat out, with a tail wind. Furmark thermal rating. GPUs
    from that era are not closed loop control, which is why
    the usage of Furmark had to be detected manually and
    the driver would turn down the clock :-) That's to prevent
    thermal mayhem. Both CPUs and GPUs today, have power limiters.
    We may not like the settings they used for those power limits,
    but, they have power limits. Like your desktop 4090 at 450 watts
    or 600 watts. That sort of thing.

    Thanks for your extensive research, but I'm coming down on the side of
    it being the display. See my imminent reply to Char Jackson.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Char Jackson on Wed Jul 31 21:17:47 2024
    XPost: alt.os.linux, alt.windows7.general

    On 31/07/2024 17:18, Char Jackson wrote:

    On Wed, 31 Jul 2024 13:22:05 +0100, Java Jive <java@evij.com.invalid> wrote:

    This is a deliberate cross-post concerning a presumed hardware problem.

    This happened on turning on this laptop this morning, it's a Dell
    Inspiron 15RSE 7520:

    www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Video_Fault.jpg

    The pattern is rather unusual. In the past, nearly always I've seen
    video faults that concern one of the primary colours ...
    Dead red = cyan (turquoise) cast
    Dead green = magenta (purple) cast
    Dead blue = yellow cast
    ... but this patterning is rather different.

    And it's not constant, but changes over time, for example it changed
    somewhat as I moved the mouse, and in fact for a while now it's gone
    altogether. I suspect that temperature may have played a part in its
    appearance immediately on switching on and its subsequent disappearance
    as the PC warmed up, a loose connection possibly.

    Or the screen or the video card is dying.

    Does anyone recognise the rather unusual patterning and can be more
    specific in their diagnosis?

    I have the same model of laptop, in continuous 24x7 service since early 2012. No
    video issues so far.

    What would you think about temporarily connecting a second display to the laptop*, with the idea being that it may help to determine whether you have a display panel issue or a GPU issue. I would think that a panel issue is a bit more likely.

    *There should be an HDMI connector and a VGA connector on the left side. I use
    VGA to drive a second display, but I've used HDMI in the past and it also works
    fine.

    Unfortunately I have no alternative display. My external monitor caught
    fire some years ago and I never replaced it.

    However, I think you're right, because a number of things that I've
    observed during the course of the day all seem to point to the display:

    - If I disable the AMD Radeon HD 7730M as Paul suggested, there is
    no change, the screen still shows the effect.

    - When the display has been on for a while it seems less likely to
    show the problem, but when it has been blanked by the screensaver for a
    while, it's more likely to show the problem immediately after being
    turned on by moving the mouse or typing.

    - But the killer diagnosis is this: if I alter the angle of the lid,
    all hell breaks loose until I stop moving it!

    So now I must decide whether I think it's worth trying to source
    another, probably used, display and attempting to fix it ...

    :-( Unfortunately, these clam shell laptops are a PITA to take apart
    and repair. Usually, changing a laptop display is a relatively quick
    job, because the lid will be held on by a small number of screws, and
    usually the display is connected under the keyboard and the WiFi and
    other possible aerials connect to the card(s) either also under the
    keyboard or else under an easily removable bottom cover - often the
    trickiest part is simply getting the aerial cables to feed through a
    small hole or cutout to get them beneath the motherboard - all of
    which means that you can just buy a lid/display as a unit off a used PC
    that has failed somehow else, and swap it easily with your broken one.
    However on these buggers you have to remove the palm-rest and the bottom
    of the case, lots of screws, and lots of other things to disconnect on
    the way and to forget to reconnect as you re-assemble it - that may
    even be why I now have this problem, because I went through all that to
    change the fan 10 months ago, though I rather think it's actually the
    display screen itself rather than the connector, because the hinges are
    so tight that every time you open or close the lid it flexes slightly,
    and given the events of the day, I'm now suspicious that this flexing,
    over the years I've had the PC (from new), is the root cause of the
    display giving up.

    :-( Also, it's quite a limited screen resolution, and, having had to replace already two of the Dell Precision M6300s with their lovely big
    screens within about 6 months of each other, I now have two Dell
    Precision M6700s both of which are higher spec than this, and, although
    they don't have the same height resolution as the 6300s, the better of
    the two does have a higher screen resolution than this, so I was
    planning to turn it into my principal PC anyway.

    :-( Also, the Inspiron's speakers are knackered.

    :-( Also, it can't fit into a dock as can the 6700/6800/etc series.

    So I think I might just let it go. Can't complain, if it's worth
    nothing now, it works out that it's cost me £69pa in depreciation, and
    that seems reasonable to me.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Java Jive on Wed Jul 31 21:30:17 2024
    XPost: alt.os.linux, alt.windows7.general

    Java Jive wrote:

    Usually, changing a laptop display is a relatively quick job, because
    the lid will be held on by a small number of screws, and usually the
    display is connected under the keyboard and the WiFi and other possible aerials connect to the card(s) either also under the keyboard or else
    under an easily removable bottom cover  -  often the trickiest part is simply getting the aerial cables to feed through a small hole or cutout
    to get them beneath the motherboard

    All the ones I've seen, have cables running through a "tunnel" in the
    hinge, there's usually a video on youtube for each model ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to Java Jive on Wed Jul 31 16:01:48 2024
    XPost: alt.os.linux, alt.windows7.general

    Java Jive <java@evij.com.invalid> wrote:

    - But the killer diagnosis is this: if I alter the angle of the lid,
    all hell breaks loose until I stop moving it!

    That could be a ribbon cable that has worked loose. You would have to dismantle the case to extract and reinsert the ribbon cable to ensure
    any oxide on the foils got wiped off.

    Dell Inspiron 15R SE 7520 Take Apart Complete Disassemble https://www.youtube.com/watch?v=AivcRqtS76A

    Shows more than just disassembly of the shell that you would need to get
    at the ribbon cable from mobo through hinge to display panel. Takes
    several screws to remove (better than notebooks that you need a spludge
    to pry apart the tangs used to snap together the shell halves).

    If you don't feel like doing all the work, and hoping you get it all
    back together again (without some extra parts left over afterward),
    check with a computer shop what they would charge on reseating the video
    cable in the mobo and in the PCB for the display. If the laptop is
    still viable and wanted, $120 USD might be worth having a shop do the
    repair as opposed to applying that money to a new laptop. Sometimes it
    is worth the cost savings, sometimes not.

    To check if it is the display panel or ribbon cable, don't rotate the
    lid. Get it in a position where the display looks good, and twist the
    lid in place. The connection from the lid PCB to the display could be
    just a piece of rubber with metal traces that gets sandwiched to make
    contact, and rubber, silicone, or other plastics shrink with age. That
    would require taking apart the display module at which point it might be
    worth the added effort to replace the CCFLs (cold cathode fluorescent
    lamps aka backlamps since those fade over time). Often you can find
    kits with all the parts, including butyl tape, to repair the display
    module.

    :-( Also, the Inspiron's speakers are knackered.

    Whatever that means. If you decide to repair (instead of trash), you
    could inspect the speakers when dismantling.

    https://youtu.be/cwr_rg7f02s?t=279

    That one shows replacing the speakers. Looks like you have to buy a
    custom speaker module from Dell.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to All on Wed Jul 31 22:29:36 2024
    XPost: alt.os.linux, alt.windows7.general

    T24gV2VkLCA3LzMxLzIwMjQgNDoxNyBQTSwgSmF2YSBKaXZlIHdyb3RlOg0KPiBPbiAzMS8w Ny8yMDI0IDE3OjE4LCBDaGFyIEphY2tzb24gd3JvdGU6DQo+Pg0KPj4gT24gV2VkLCAzMSBK dWwgMjAyNCAxMzoyMjowNSArMDEwMCwgSmF2YSBKaXZlIDxqYXZhQGV2aWouY29tLmludmFs aWQ+IHdyb3RlOg0KPj4+DQo+Pj4gVGhpcyBpcyBhIGRlbGliZXJhdGUgY3Jvc3MtcG9zdCBj b25jZXJuaW5nIGEgcHJlc3VtZWQgaGFyZHdhcmUgcHJvYmxlbS4NCj4+Pg0KPj4+IFRoaXMg aGFwcGVuZWQgb24gdHVybmluZyBvbiB0aGlzIGxhcHRvcCB0aGlzIG1vcm5pbmcsIGl0J3Mg YSBEZWxsDQo+Pj4gSW5zcGlyb24gMTVSU0UgNzUyMDoNCj4+Pg0KPj4+IMKgwqAgd3d3Lm1h Y2ZoLmNvLnVrL1RlbXAvMjAyNDA3MzFfRGVsbF9JbnNwaXJvbl8xNVJTRV83NTIwX1ZpZGVv X0ZhdWx0LmpwZw0KPj4+DQo+Pj4gVGhlIHBhdHRlcm4gaXMgcmF0aGVyIHVudXN1YWwuwqAg SW4gdGhlIHBhc3QsIG5lYXJseSBhbHdheXMgSSd2ZSBzZWVuDQo+Pj4gdmlkZW8gZmF1bHRz IHRoYXQgY29uY2VybiBvbmUgb2YgdGhlIHByaW1hcnkgY29sb3VycyAuLi4NCj4+PiDCoMKg IERlYWQgcmVkID0gY3lhbiAodHVycXVvaXNlKSBjYXN0DQo+Pj4gwqDCoCBEZWFkIGdyZWVu ID0gbWFnZW50YSAocHVycGxlKSBjYXN0DQo+Pj4gwqDCoCBEZWFkIGJsdWUgPSB5ZWxsb3cg Y2FzdA0KPj4+IC4uLiBidXQgdGhpcyBwYXR0ZXJuaW5nIGlzIHJhdGhlciBkaWZmZXJlbnQu DQo+Pj4NCj4+PiBBbmQgaXQncyBub3QgY29uc3RhbnQsIGJ1dCBjaGFuZ2VzIG92ZXIgdGlt ZSwgZm9yIGV4YW1wbGUgaXQgY2hhbmdlZA0KPj4+IHNvbWV3aGF0IGFzIEkgbW92ZWQgdGhl IG1vdXNlLCBhbmQgaW4gZmFjdCBmb3IgYSB3aGlsZSBub3cgaXQncyBnb25lDQo+Pj4gYWx0 b2dldGhlci7CoCBJIHN1c3BlY3QgdGhhdCB0ZW1wZXJhdHVyZSBtYXkgaGF2ZSBwbGF5ZWQg YSBwYXJ0IGluIGl0cw0KPj4+IGFwcGVhcmFuY2UgaW1tZWRpYXRlbHkgb24gc3dpdGNoaW5n IG9uIGFuZCBpdHMgc3Vic2VxdWVudCBkaXNhcHBlYXJhbmNlDQo+Pj4gYXMgdGhlIFBDIHdh cm1lZCB1cCwgYSBsb29zZSBjb25uZWN0aW9uIHBvc3NpYmx5Lg0KPj4+DQo+Pj4gT3IgdGhl IHNjcmVlbiBvciB0aGUgdmlkZW8gY2FyZCBpcyBkeWluZy4NCj4+Pg0KPj4+IERvZXMgYW55 b25lIHJlY29nbmlzZSB0aGUgcmF0aGVyIHVudXN1YWwgcGF0dGVybmluZyBhbmQgY2FuIGJl IG1vcmUNCj4+PiBzcGVjaWZpYyBpbiB0aGVpciBkaWFnbm9zaXM/DQo+Pg0KPj4gSSBoYXZl IHRoZSBzYW1lIG1vZGVsIG9mIGxhcHRvcCwgaW4gY29udGludW91cyAyNHg3IHNlcnZpY2Ug c2luY2UgZWFybHkgMjAxMi4gTm8NCj4+IHZpZGVvIGlzc3VlcyBzbyBmYXIuDQo+Pg0KPj4g V2hhdCB3b3VsZCB5b3UgdGhpbmsgYWJvdXQgdGVtcG9yYXJpbHkgY29ubmVjdGluZyBhIHNl Y29uZCBkaXNwbGF5IHRvIHRoZQ0KPj4gbGFwdG9wKiwgd2l0aCB0aGUgaWRlYSBiZWluZyB0 aGF0IGl0IG1heSBoZWxwIHRvIGRldGVybWluZSB3aGV0aGVyIHlvdSBoYXZlIGENCj4+IGRp c3BsYXkgcGFuZWwgaXNzdWUgb3IgYSBHUFUgaXNzdWUuIEkgd291bGQgdGhpbmsgdGhhdCBh IHBhbmVsIGlzc3VlIGlzIGEgYml0DQo+PiBtb3JlIGxpa2VseS4NCj4+DQo+PiAqVGhlcmUg c2hvdWxkIGJlIGFuIEhETUkgY29ubmVjdG9yIGFuZCBhIFZHQSBjb25uZWN0b3Igb24gdGhl IGxlZnQgc2lkZS4gSSB1c2UNCj4+IFZHQSB0byBkcml2ZSBhIHNlY29uZCBkaXNwbGF5LCBi dXQgSSd2ZSB1c2VkIEhETUkgaW4gdGhlIHBhc3QgYW5kIGl0IGFsc28gd29ya3MNCj4+IGZp bmUuDQo+IA0KPiBVbmZvcnR1bmF0ZWx5IEkgaGF2ZSBubyBhbHRlcm5hdGl2ZSBkaXNwbGF5 LsKgIE15IGV4dGVybmFsIG1vbml0b3IgY2F1Z2h0IGZpcmUgc29tZSB5ZWFycyBhZ28gYW5k IEkgbmV2ZXIgcmVwbGFjZWQgaXQuDQo+IA0KPiBIb3dldmVyLCBJIHRoaW5rIHlvdSdyZSBy aWdodCwgYmVjYXVzZSBhIG51bWJlciBvZiB0aGluZ3MgdGhhdCBJJ3ZlIG9ic2VydmVkIGR1 cmluZyB0aGUgY291cnNlIG9mIHRoZSBkYXkgYWxsIHNlZW0gdG8gcG9pbnQgdG8gdGhlIGRp c3BsYXk6DQo+IA0KPiDCoCAtwqAgSWYgSSBkaXNhYmxlIHRoZSBBTUQgUmFkZW9uIEhEIDc3 MzBNIGFzIFBhdWwgc3VnZ2VzdGVkLCB0aGVyZSBpcyBubyBjaGFuZ2UsIHRoZSBzY3JlZW4g c3RpbGwgc2hvd3MgdGhlIGVmZmVjdC4NCj4gDQo+IMKgIC3CoCBXaGVuIHRoZSBkaXNwbGF5 IGhhcyBiZWVuIG9uIGZvciBhIHdoaWxlIGl0IHNlZW1zIGxlc3MgbGlrZWx5IHRvIHNob3cg dGhlIHByb2JsZW0sIGJ1dCB3aGVuIGl0IGhhcyBiZWVuIGJsYW5rZWQgYnkgdGhlIHNjcmVl bnNhdmVyIGZvciBhIHdoaWxlLCBpdCdzIG1vcmUgbGlrZWx5IHRvIHNob3cgdGhlIHByb2Js ZW0gaW1tZWRpYXRlbHkgYWZ0ZXIgYmVpbmcgdHVybmVkIG9uIGJ5IG1vdmluZyB0aGUgbW91 c2Ugb3IgdHlwaW5nLg0KPiANCj4gwqAgLcKgIEJ1dCB0aGUga2lsbGVyIGRpYWdub3NpcyBp cyB0aGlzOiBpZiBJIGFsdGVyIHRoZSBhbmdsZSBvZiB0aGUgbGlkLCBhbGwgaGVsbCBicmVh a3MgbG9vc2UgdW50aWwgSSBzdG9wIG1vdmluZyBpdCENCj4gDQo+IFNvIG5vdyBJIG11c3Qg ZGVjaWRlIHdoZXRoZXIgSSB0aGluayBpdCdzIHdvcnRoIHRyeWluZyB0byBzb3VyY2UgYW5v dGhlciwgcHJvYmFibHkgdXNlZCwgZGlzcGxheSBhbmQgYXR0ZW1wdGluZyB0byBmaXggaXQg Li4uDQo+IA0KPiDCoCA6LSjCoCBVbmZvcnR1bmF0ZWx5LCB0aGVzZSBjbGFtIHNoZWxsIGxh cHRvcHMgYXJlIGEgUElUQSB0byB0YWtlIGFwYXJ0IGFuZCByZXBhaXIuwqAgVXN1YWxseSwg Y2hhbmdpbmcgYSBsYXB0b3AgZGlzcGxheSBpcyBhIHJlbGF0aXZlbHkgcXVpY2sgam9iLCBi ZWNhdXNlIHRoZSBsaWQgd2lsbCBiZSBoZWxkIG9uIGJ5IGEgc21hbGwgbnVtYmVyIG9mIHNj cmV3cywgYW5kIHVzdWFsbHkgdGhlIGRpc3BsYXkgaXMgY29ubmVjdGVkIHVuZGVyIHRoZSBr ZXlib2FyZCBhbmQgdGhlIFdpRmkgYW5kIG90aGVyIHBvc3NpYmxlIGFlcmlhbHMgY29ubmVj dCB0byB0aGUgY2FyZChzKSBlaXRoZXIgYWxzbyB1bmRlciB0aGUga2V5Ym9hcmQgb3IgZWxz ZSB1bmRlciBhbiBlYXNpbHkgcmVtb3ZhYmxlIGJvdHRvbSBjb3ZlcsKgIC3CoCBvZnRlbiB0 aGUgdHJpY2tpZXN0IHBhcnQgaXMgc2ltcGx5IGdldHRpbmcgdGhlIGFlcmlhbCBjYWJsZXMg dG8gZmVlZCB0aHJvdWdoIGEgc21hbGwgaG9sZSBvciBjdXRvdXQgdG8gZ2V0IHRoZW0gYmVu ZWF0aCB0aGUgbW90aGVyYm9hcmTCoCAtwqAgYWxsIG9mIHdoaWNoIG1lYW5zIHRoYXQgeW91 IGNhbiBqdXN0IGJ1eSBhIGxpZC9kaXNwbGF5IGFzIGEgdW5pdCBvZmYgYSB1c2VkIFBDIHRo YXQgaGFzIGZhaWxlZCBzb21laG93IGVsc2UsIGFuZCBzd2FwIGl0IGVhc2lseSB3aXRoIHlv dXIgYnJva2VuIG9uZS4gSG93ZXZlciBvbiB0aGVzZSBidWdnZXJzIHlvdSBoYXZlIHRvIHJl bW92ZSB0aGUgcGFsbS1yZXN0IGFuZCB0aGUgYm90dG9tIG9mIHRoZSBjYXNlLCBsb3RzIG9m IHNjcmV3cywgYW5kIGxvdHMgb2Ygb3RoZXIgdGhpbmdzIHRvIGRpc2Nvbm5lY3Qgb24gdGhl IHdheSBhbmQgdG8gZm9yZ2V0IHRvIHJlY29ubmVjdCBhcyB5b3UgcmUtYXNzZW1ibGUgaXTC oCAtwqAgdGhhdCBtYXkgZXZlbiBiZSB3aHkgSSBub3cgaGF2ZSB0aGlzIHByb2JsZW0sIGJl Y2F1c2UgSSB3ZW50IHRocm91Z2ggYWxsIHRoYXQgdG8NCj4gY2hhbmdlIHRoZSBmYW4gMTAg bW9udGhzIGFnbywgdGhvdWdoIEkgcmF0aGVyIHRoaW5rIGl0J3MgYWN0dWFsbHkgdGhlIGRp c3BsYXkgc2NyZWVuIGl0c2VsZiByYXRoZXIgdGhhbiB0aGUgY29ubmVjdG9yLCBiZWNhdXNl IHRoZSBoaW5nZXMgYXJlIHNvIHRpZ2h0IHRoYXQgZXZlcnkgdGltZSB5b3Ugb3BlbiBvciBj bG9zZSB0aGUgbGlkIGl0IGZsZXhlcyBzbGlnaHRseSwgYW5kIGdpdmVuIHRoZSBldmVudHMg b2YgdGhlIGRheSwgSSdtIG5vdyBzdXNwaWNpb3VzIHRoYXQgdGhpcyBmbGV4aW5nLCBvdmVy IHRoZSB5ZWFycyBJJ3ZlIGhhZCB0aGUgUEMgKGZyb20gbmV3KSwgaXMgdGhlIHJvb3QgY2F1 c2Ugb2YgdGhlIGRpc3BsYXkgZ2l2aW5nIHVwLg0KPiANCj4gwqAgOi0owqAgQWxzbywgaXQn cyBxdWl0ZSBhIGxpbWl0ZWQgc2NyZWVuIHJlc29sdXRpb24sIGFuZCwgaGF2aW5nIGhhZCB0 byByZXBsYWNlIGFscmVhZHkgdHdvIG9mIHRoZSBEZWxsIFByZWNpc2lvbiBNNjMwMHMgd2l0 aCB0aGVpciBsb3ZlbHkgYmlnIHNjcmVlbnMgd2l0aGluIGFib3V0IDYgbW9udGhzIG9mIGVh Y2ggb3RoZXIsIEkgbm93IGhhdmUgdHdvIERlbGwgUHJlY2lzaW9uIE02NzAwcyBib3RoIG9m IHdoaWNoIGFyZSBoaWdoZXIgc3BlYyB0aGFuIHRoaXMsIGFuZCwgYWx0aG91Z2ggdGhleSBk b24ndCBoYXZlIHRoZSBzYW1lIGhlaWdodCByZXNvbHV0aW9uIGFzIHRoZSA2MzAwcywgdGhl IGJldHRlciBvZiB0aGUgdHdvIGRvZXMgaGF2ZSBhIGhpZ2hlciBzY3JlZW4gcmVzb2x1dGlv biB0aGFuIHRoaXMsIHNvIEkgd2FzIHBsYW5uaW5nIHRvIHR1cm4gaXQgaW50byBteSBwcmlu Y2lwYWwgUEMgYW55d2F5Lg0KPiANCj4gwqAgOi0owqAgQWxzbywgdGhlIEluc3Bpcm9uJ3Mg c3BlYWtlcnMgYXJlIGtuYWNrZXJlZC4NCj4gDQo+IMKgIDotKMKgIEFsc28sIGl0IGNhbid0 IGZpdCBpbnRvIGEgZG9jayBhcyBjYW4gdGhlIDY3MDAvNjgwMC9ldGMgc2VyaWVzLg0KPiAN Cj4gU28gSSB0aGluayBJIG1pZ2h0IGp1c3QgbGV0IGl0IGdvLsKgIENhbid0IGNvbXBsYWlu LCBpZiBpdCdzIHdvcnRoIG5vdGhpbmcgbm93LCBpdCB3b3JrcyBvdXQgdGhhdCBpdCdzIGNv c3QgbWUgwqM2OXBhIGluIGRlcHJlY2lhdGlvbiwgYW5kIHRoYXQgc2VlbXMgcmVhc29uYWJs ZSB0byBtZS4NCj4gDQoNCldoYXQgcGFydCBvZiB0aGUgcGFuZWwgd291bGQgdGhhdCBwYXR0 ZXJuIGNvbWUgZnJvbSA/DQoNCkRpZCB5b3Ugc2hvb3QgdGhlIHBpY3R1cmUgd2l0aCBhIGhp Z2ggc3BlZWQgY2FtZXJhID8NCg0KRG9lcyB0aGUgcGF0dGVybiBzdGFuZCBzdGlsbCwgb3Ig ZG9lcyBpdCB2YXJ5IGNvbnRpbnVvdXNseSAoamlnZ2xpbmcsIGRhbmNpbmcpID8NClRoYXQn cyBub3QgZmFpbGluZyBJL08gc25vdyBJJ20gbG9va2luZyBhdC4gVGhlcmUgaXMNCmEgcGF0 dGVybiB0aGVyZS4gWW91IGNvdWxkIGJlIHNob3dpbmcgbWUgYSBzdGF0aWMgcGF0dGVybg0K b3IgYSBtb3ZpbmcgcGF0dGVybiAoc3RvcHBlZCB3aXRoIGEgaGlnaCBzaHV0dGVyIHNwZWVk KS4NCg0KSXQgaGVscHMgdG8gdW5kZXJzdGFuZCB3aGVyZSB0aGF0IHBhdHRlcm4gY29tZXMg ZnJvbSwgZm9yIHRoZQ0KbmV4dCB0aW1lLiBQYW5lbHMgaGF2ZSBkcml2ZXIgY2hpcCBmYWls dXJlcyAodGhlc2UgYXJlIGNoaXBzDQpvbiBvciBuZWFyIHRoZSBnbGFzcyBwYW5lbCksIHdo aWNoIGRyaXZlIHRoZQ0KTENEIG1hdHJpeCwgYW5kIHRoZSBvcmllbnRhdGlvbiBvZiB0aGUg ZmF1bHQgdGhlbiwgaXMgbGluZXMNCm9uIHRoZSBzY3JlZW4uIEhvcml6b250YWwgb3IgdmVy dGljYWwgbGluZXMuDQoNCkZvciBhIG5pY2UgZmFpbHVyZSBjb25kaXRpb24sIHlvdSBuZWVk IHNpbGljb24gdGhhdCBoYXMgdGhlDQpjYXBhYmlsaXR5IG9mIG1ha2luZyB0aGUgcGF0dGVy bi4gQW4gSS9PIGZhaWx1cmUgY2FuIGdpdmUgeW91DQpzbm93LiBBIGxhY2sgb2YgSERDUCBz dXBwb3J0LCBtaWdodCBnaXZlIHlvdSBlbmNyeXB0aW9uLXNub3cuDQoNCkdQVXMgY2FuIG1h a2Ugc29tZSByZWFsbHkgbmVhdCBmYWlsdXJlcy4gT25lIEdQVSBmYWlsdXJlLA0KaXQgZHJl dyBmaWxsZWQgY2lyY2xlcyBvbiB0aGUgc2NyZWVuLCBub3QgYWxsIG9mIHRoZSBzYW1lDQpz aXplLiBJdCdzIGhhcmQgdG8gaW1hZ2luZSBob3cgb3Igd2h5IHN1Y2ggYSB0aGluZyB3b3Vs ZA0KaGFwcGVuLCBidXQgb25seSB0aGUgR1BVIGhhcyBlbm91Z2ggY29tcHV0ZSB0byBkbyBz dHVmZg0KbGlrZSB0aGF0Lg0KDQpBbiBleHRlcm5hbCBtb25pdG9yIHRvIHRlc3Qgd2l0aCwg Y2FuIGNvc3QgJDEwMCBvbiBKYW51YXJ5IDE1dGgsDQpidXQgdGhlIGJhY2stdG8tc2Nob29s IG1hcmtldGluZyBpbnRlcnZhbCBzdGFydHMgbm93LCBzbyB0aGUNCnByaWNlcyB3aWxsIGJl IGphY2tlZCB0byB0YWtlIGFkdmFudGFnZSByaWdodCBub3cuIEkgdHJ5IHRvDQpjaGVjayB0 aGUgYWR2ZXJ0cyBhcm91bmQgSmFuLjE1LCB0byBhY3F1aXJlIGFuIGVtZXJnZW5jeSBtb25p dG9yDQpmb3IgbGF0ZXIuIEFuZCB0aGVuIHlvdSBoYXZlIHRvIGdldCB0aGUgcmlnaHQgY29u bmVjdG9ycyBvbiBpdCwNCnRvIG1ha2UgaXQgYSBnb29kIG1hdGNoIGZvciB5b3VyIGNvbXB1 dGVyIHJvb20uDQoNCllvdSBjYW4gdGFrZSBhIHNjcmVlbnNob3QsIHdpdGggYSBwcmludC1z Y3JlZW4gb3Igd2l0aCBhIHNuaXBwaW5ndG9vbCwNCmFuZCBzZWUgaWYgdGhlIHBhdHRlcm4g aXMgZXZpZGVudC4gSXQgc2hvdWxkIG5vdCBiZSwgYmVjYXVzZQ0KdGhlIGZhdWx0IGlzIGRv d25zdHJlYW0gb2YgdGhhdCBwb2ludC4gSWYgeW91IGNhbiBzZWUgYSBwcm9ibGVtDQphdCB0 aGF0IHBvaW50LCBpdCBjb3VsZCBiZSBhIHN5c3RlbSBtZW1vcnkgaXNzdWUgKGFuZCBvdGhl cg0Kc3R1ZmYgd291bGQgaGF2ZSBjcmFzaGVkKS4NCg0KICAgUGF1bA0K

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Java Jive on Wed Aug 7 19:20:50 2024
    XPost: alt.os.linux, alt.windows7.general

    On Wed, 8/7/2024 6:21 AM, Java Jive wrote:
    On 06/08/2024 23:06, Java Jive wrote:

    On 02/08/2024 00:21, Java Jive wrote:

    However that may be, hopefully when the replacement plastic arrives I'll be able to restore the laptop to a fully working state.

    Arrived today, laptop now fixed, all seemingly well, at least for the moment I have 'feature'-free display.

    Spoke too soon, there is now some sort of smudge of darker pixels in the centre of the screen that won't wipe off, and I'm not sure what I did wrong to cause it (it's much more obvious in real life than this photo suggests):

    www.macfh.co.uk/Temp/20240731_Dell_Inspiron_15RSE_7520_Smudge.jpg


    You must have handled something optical. Might not be CCFL related,
    but maybe some gadget that spreads the light.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Andy Burns on Thu Aug 1 13:12:07 2024
    XPost: alt.os.linux, alt.windows7.general

    On 31/07/2024 21:30, Andy Burns wrote:

    Java Jive wrote:

    Usually, changing a laptop display is a relatively quick job, because
    the lid will be held on by a small number of screws, and usually the
    display is connected under the keyboard and the WiFi and other
    possible aerials connect to the card(s) either also under the keyboard
    or else under an easily removable bottom cover  -  often the trickiest
    part is simply getting the aerial cables to feed through a small hole
    or cutout to get them beneath the motherboard

    All the ones I've seen, have cables running through a "tunnel" in the
    hinge, there's usually a video on youtube for each model ...

    Yes and no, it depends on the model, let alone the make. Dells vary considerably by model. See my other replies here.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to VanguardLH on Thu Aug 1 13:33:50 2024
    XPost: alt.os.linux, alt.windows7.general

    On 31/07/2024 22:01, VanguardLH wrote:

    Java Jive <java@evij.com.invalid> wrote:

    - But the killer diagnosis is this: if I alter the angle of the lid,
    all hell breaks loose until I stop moving it!

    That could be a ribbon cable that has worked loose. You would have to dismantle the case to extract and reinsert the ribbon cable to ensure
    any oxide on the foils got wiped off.

    Dell Inspiron 15R SE 7520 Take Apart Complete Disassemble https://www.youtube.com/watch?v=AivcRqtS76A

    Yes, I followed one of those in the past when I changed the fan, but
    it's not a ribbon rather a round cable ...

    Dell Inspiron 15R Owner’s Manual*

    p35 Removing the Display Assembly

    Prerequisites
    1 Remove the battery. See "Removing the Battery" on page 13.
    2 Remove the keyboard. See "Removing the Keyboard" on page 15.
    3 Remove the base cover. See "Removing the Base Cover" on page 17.
    4 Remove the palm rest. See "Removing the Palm Rest" on page 27.

    p27 Removing the Palm Rest

    Prerequisites
    1 Remove the battery. See "Removing the Battery" on page 13.
    2 Remove the keyboard. See "Removing the Keyboard" on page 15.
    3 Remove the base cover. See "Removing the Base Cover" on page 17.

    Procedure
    1 Remove the screws that secure the palm rest to the computer base.
    2 Turn the computer over.
    3 Lift the connector latches and pull the pull-tabs to disconnect the power-button board cable, touchpad cable, and hot-key board cable from
    the connectors on the system board.

    [11 screws and three connectors over and above what you've already
    removed to get this far, then 'spludge' - perhaps that should be
    'kludge' - the palm-rest off the base, and only then can you access
    the hinge screws and the display and WiFi connections.]

    Incidentally, this is a model where only an option made at purchase time included an extra card connector on the underside of the daughterboard
    for the card slot(s), so most daughterboards don't even have the extra connector, meaning you can't upgrade a second-hand/used machine with an
    onboard SSD unless you can somehow get hold of a daughterboard with the
    extra connector, and even then you must go through all the above and
    more just to fit an onboard SSD. By comparison, with a Precision M6700,
    you simply take off the bottom cover - just two screws. It rather
    reminds me of stories of having to take the engine out of a mini to
    change the battery, or the Citroen GSA (IMS) where everything was so
    cluttered under the bonnet that to do any significant work in there was
    an absolute bloody nightmare.

    * A Dell irritation, what effectively are Service Manuals are frequently
    called Owner's Manuals.

    :-( Also, the Inspiron's speakers are knackered.

    Whatever that means. If you decide to repair (instead of trash), you
    could inspect the speakers when dismantling.

    It means they distort the sound verging on unacceptably.

    https://youtu.be/cwr_rg7f02s?t=279

    That one shows replacing the speakers. Looks like you have to buy a
    custom speaker module from Dell.

    Not worth it, second-hand maybe, but then you don't know whether the replacements would be any better.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Folderol@21:1/5 to Java Jive on Thu Aug 1 14:35:40 2024
    XPost: alt.os.linux, alt.windows7.general

    On Thu, 1 Aug 2024 14:30:26 +0100
    Java Jive <java@evij.com.invalid> wrote:

    I've already thought of that, a screenshot taken with <PrintScreen> or ><Alt-PrintScreen> when viewed on another PC is free of the fault.


    The it's *definitely* either screen and/or screen connecting cable
    --
    Basic

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to All on Thu Aug 1 14:30:26 2024
    XPost: alt.os.linux, alt.windows7.general

    T24gMDEvMDgvMjAyNCAwMzoyOSwgUGF1bCB3cm90ZToNCj4gT24gV2VkLCA3LzMxLzIwMjQg NDoxNyBQTSwgSmF2YSBKaXZlIHdyb3RlOg0KPj4gT24gMzEvMDcvMjAyNCAxNzoxOCwgQ2hh ciBKYWNrc29uIHdyb3RlOg0KPj4+DQo+Pj4gT24gV2VkLCAzMSBKdWwgMjAyNCAxMzoyMjow NSArMDEwMCwgSmF2YSBKaXZlIDxqYXZhQGV2aWouY29tLmludmFsaWQ+IHdyb3RlOg0KPj4+ Pg0KPj4+PiBUaGlzIGlzIGEgZGVsaWJlcmF0ZSBjcm9zcy1wb3N0IGNvbmNlcm5pbmcgYSBw cmVzdW1lZCBoYXJkd2FyZSBwcm9ibGVtLg0KPj4+Pg0KPj4+PiBUaGlzIGhhcHBlbmVkIG9u IHR1cm5pbmcgb24gdGhpcyBsYXB0b3AgdGhpcyBtb3JuaW5nLCBpdCdzIGEgRGVsbA0KPj4+ PiBJbnNwaXJvbiAxNVJTRSA3NTIwOg0KPj4+Pg0KPj4+PiAgwqDCoCB3d3cubWFjZmguY28u dWsvVGVtcC8yMDI0MDczMV9EZWxsX0luc3Bpcm9uXzE1UlNFXzc1MjBfVmlkZW9fRmF1bHQu anBnDQo+Pj4+DQo+Pj4+IFRoZSBwYXR0ZXJuIGlzIHJhdGhlciB1bnVzdWFsLsKgIEluIHRo ZSBwYXN0LCBuZWFybHkgYWx3YXlzIEkndmUgc2Vlbg0KPj4+PiB2aWRlbyBmYXVsdHMgdGhh dCBjb25jZXJuIG9uZSBvZiB0aGUgcHJpbWFyeSBjb2xvdXJzIC4uLg0KPj4+PiAgwqDCoCBE ZWFkIHJlZCA9IGN5YW4gKHR1cnF1b2lzZSkgY2FzdA0KPj4+PiAgwqDCoCBEZWFkIGdyZWVu ID0gbWFnZW50YSAocHVycGxlKSBjYXN0DQo+Pj4+ICDCoMKgIERlYWQgYmx1ZSA9IHllbGxv dyBjYXN0DQo+Pj4+IC4uLiBidXQgdGhpcyBwYXR0ZXJuaW5nIGlzIHJhdGhlciBkaWZmZXJl bnQuDQo+Pj4+DQo+Pj4+IEFuZCBpdCdzIG5vdCBjb25zdGFudCwgYnV0IGNoYW5nZXMgb3Zl ciB0aW1lLCBmb3IgZXhhbXBsZSBpdCBjaGFuZ2VkDQo+Pj4+IHNvbWV3aGF0IGFzIEkgbW92 ZWQgdGhlIG1vdXNlLCBhbmQgaW4gZmFjdCBmb3IgYSB3aGlsZSBub3cgaXQncyBnb25lDQo+ Pj4+IGFsdG9nZXRoZXIuwqAgSSBzdXNwZWN0IHRoYXQgdGVtcGVyYXR1cmUgbWF5IGhhdmUg cGxheWVkIGEgcGFydCBpbiBpdHMNCj4+Pj4gYXBwZWFyYW5jZSBpbW1lZGlhdGVseSBvbiBz d2l0Y2hpbmcgb24gYW5kIGl0cyBzdWJzZXF1ZW50IGRpc2FwcGVhcmFuY2UNCj4+Pj4gYXMg dGhlIFBDIHdhcm1lZCB1cCwgYSBsb29zZSBjb25uZWN0aW9uIHBvc3NpYmx5Lg0KPj4+Pg0K Pj4+PiBPciB0aGUgc2NyZWVuIG9yIHRoZSB2aWRlbyBjYXJkIGlzIGR5aW5nLg0KPj4+Pg0K Pj4+PiBEb2VzIGFueW9uZSByZWNvZ25pc2UgdGhlIHJhdGhlciB1bnVzdWFsIHBhdHRlcm5p bmcgYW5kIGNhbiBiZSBtb3JlDQo+Pj4+IHNwZWNpZmljIGluIHRoZWlyIGRpYWdub3Npcz8N Cj4+Pg0KPj4+IEkgaGF2ZSB0aGUgc2FtZSBtb2RlbCBvZiBsYXB0b3AsIGluIGNvbnRpbnVv dXMgMjR4NyBzZXJ2aWNlIHNpbmNlIGVhcmx5IDIwMTIuIE5vDQo+Pj4gdmlkZW8gaXNzdWVz IHNvIGZhci4NCj4+Pg0KPj4+IFdoYXQgd291bGQgeW91IHRoaW5rIGFib3V0IHRlbXBvcmFy aWx5IGNvbm5lY3RpbmcgYSBzZWNvbmQgZGlzcGxheSB0byB0aGUNCj4+PiBsYXB0b3AqLCB3 aXRoIHRoZSBpZGVhIGJlaW5nIHRoYXQgaXQgbWF5IGhlbHAgdG8gZGV0ZXJtaW5lIHdoZXRo ZXIgeW91IGhhdmUgYQ0KPj4+IGRpc3BsYXkgcGFuZWwgaXNzdWUgb3IgYSBHUFUgaXNzdWUu IEkgd291bGQgdGhpbmsgdGhhdCBhIHBhbmVsIGlzc3VlIGlzIGEgYml0DQo+Pj4gbW9yZSBs aWtlbHkuDQo+Pj4NCj4+PiAqVGhlcmUgc2hvdWxkIGJlIGFuIEhETUkgY29ubmVjdG9yIGFu ZCBhIFZHQSBjb25uZWN0b3Igb24gdGhlIGxlZnQgc2lkZS4gSSB1c2UNCj4+PiBWR0EgdG8g ZHJpdmUgYSBzZWNvbmQgZGlzcGxheSwgYnV0IEkndmUgdXNlZCBIRE1JIGluIHRoZSBwYXN0 IGFuZCBpdCBhbHNvIHdvcmtzDQo+Pj4gZmluZS4NCj4+DQo+PiBVbmZvcnR1bmF0ZWx5IEkg aGF2ZSBubyBhbHRlcm5hdGl2ZSBkaXNwbGF5LsKgIE15IGV4dGVybmFsIG1vbml0b3IgY2F1 Z2h0IGZpcmUgc29tZSB5ZWFycyBhZ28gYW5kIEkgbmV2ZXIgcmVwbGFjZWQgaXQuDQo+Pg0K Pj4gSG93ZXZlciwgSSB0aGluayB5b3UncmUgcmlnaHQsIGJlY2F1c2UgYSBudW1iZXIgb2Yg dGhpbmdzIHRoYXQgSSd2ZSBvYnNlcnZlZCBkdXJpbmcgdGhlIGNvdXJzZSBvZiB0aGUgZGF5 IGFsbCBzZWVtIHRvIHBvaW50IHRvIHRoZSBkaXNwbGF5Og0KPj4NCj4+ICDCoCAtwqAgSWYg SSBkaXNhYmxlIHRoZSBBTUQgUmFkZW9uIEhEIDc3MzBNIGFzIFBhdWwgc3VnZ2VzdGVkLCB0 aGVyZSBpcyBubyBjaGFuZ2UsIHRoZSBzY3JlZW4gc3RpbGwgc2hvd3MgdGhlIGVmZmVjdC4N Cj4+DQo+PiAgwqAgLcKgIFdoZW4gdGhlIGRpc3BsYXkgaGFzIGJlZW4gb24gZm9yIGEgd2hp bGUgaXQgc2VlbXMgbGVzcyBsaWtlbHkgdG8gc2hvdyB0aGUgcHJvYmxlbSwgYnV0IHdoZW4g aXQgaGFzIGJlZW4gYmxhbmtlZCBieSB0aGUgc2NyZWVuc2F2ZXIgZm9yIGEgd2hpbGUsIGl0 J3MgbW9yZSBsaWtlbHkgdG8gc2hvdyB0aGUgcHJvYmxlbSBpbW1lZGlhdGVseSBhZnRlciBi ZWluZyB0dXJuZWQgb24gYnkgbW92aW5nIHRoZSBtb3VzZSBvciB0eXBpbmcuDQo+Pg0KPj4g IMKgIC3CoCBCdXQgdGhlIGtpbGxlciBkaWFnbm9zaXMgaXMgdGhpczogaWYgSSBhbHRlciB0 aGUgYW5nbGUgb2YgdGhlIGxpZCwgYWxsIGhlbGwgYnJlYWtzIGxvb3NlIHVudGlsIEkgc3Rv cCBtb3ZpbmcgaXQhDQo+Pg0KPj4gU28gbm93IEkgbXVzdCBkZWNpZGUgd2hldGhlciBJIHRo aW5rIGl0J3Mgd29ydGggdHJ5aW5nIHRvIHNvdXJjZSBhbm90aGVyLCBwcm9iYWJseSB1c2Vk LCBkaXNwbGF5IGFuZCBhdHRlbXB0aW5nIHRvIGZpeCBpdCAuLi4NCj4+DQo+PiAgwqAgOi0o wqAgVW5mb3J0dW5hdGVseSwgdGhlc2UgY2xhbSBzaGVsbCBsYXB0b3BzIGFyZSBhIFBJVEEg dG8gdGFrZSBhcGFydCBhbmQgcmVwYWlyLsKgIFVzdWFsbHksIGNoYW5naW5nIGEgbGFwdG9w IGRpc3BsYXkgaXMgYSByZWxhdGl2ZWx5IHF1aWNrIGpvYiwgYmVjYXVzZSB0aGUgbGlkIHdp bGwgYmUgaGVsZCBvbiBieSBhIHNtYWxsIG51bWJlciBvZiBzY3Jld3MsIGFuZCB1c3VhbGx5 IHRoZSBkaXNwbGF5IGlzIGNvbm5lY3RlZCB1bmRlciB0aGUga2V5Ym9hcmQgYW5kIHRoZSBX aUZpIGFuZCBvdGhlciBwb3NzaWJsZSBhZXJpYWxzIGNvbm5lY3QgdG8gdGhlIGNhcmQocykg ZWl0aGVyIGFsc28gdW5kZXIgdGhlIGtleWJvYXJkIG9yIGVsc2UgdW5kZXIgYW4gZWFzaWx5 IHJlbW92YWJsZSBib3R0b20gY292ZXLCoCAtwqAgb2Z0ZW4gdGhlIHRyaWNraWVzdCBwYXJ0 IGlzIHNpbXBseSBnZXR0aW5nIHRoZSBhZXJpYWwgY2FibGVzIHRvIGZlZWQgdGhyb3VnaCBh IHNtYWxsIGhvbGUgb3IgY3V0b3V0IHRvIGdldCB0aGVtIGJlbmVhdGggdGhlIG1vdGhlcmJv YXJkwqAgLcKgIGFsbCBvZiB3aGljaCBtZWFucyB0aGF0IHlvdSBjYW4ganVzdCBidXkgYSBs aWQvZGlzcGxheSBhcyBhIHVuaXQgb2ZmIGEgdXNlZCBQQyB0aGF0IGhhcyBmYWlsZWQgc29t ZWhvdyBlbHNlLCBhbmQgc3dhcCBpdCBlYXNpbHkgd2l0aCB5b3VyIGJyb2tlbiBvbmUuIEhv d2V2ZXIgb24gdGhlc2UgYnVnZ2VycyB5b3UgaGF2ZSB0byByZW1vdmUgdGhlIHBhbG0tcmVz dCBhbmQgdGhlIGJvdHRvbSBvZiB0aGUgY2FzZSwgbG90cyBvZiBzY3Jld3MsIGFuZCBsb3Rz IG9mIG90aGVyIHRoaW5ncyB0byBkaXNjb25uZWN0IG9uIHRoZSB3YXkgYW5kIHRvIGZvcmdl dCB0byByZWNvbm5lY3QgYXMgeW91IHJlLWFzc2VtYmxlIGl0wqAgLcKgIHRoYXQgbWF5IGV2 ZW4gYmUgd2h5IEkgbm93IGhhdmUgdGhpcyBwcm9ibGVtLCBiZWNhdXNlIEkgd2VudCB0aHJv dWdoIGFsbCB0aGF0IHRvDQo+PiBjaGFuZ2UgdGhlIGZhbiAxMCBtb250aHMgYWdvLCB0aG91 Z2ggSSByYXRoZXIgdGhpbmsgaXQncyBhY3R1YWxseSB0aGUgZGlzcGxheSBzY3JlZW4gaXRz ZWxmIHJhdGhlciB0aGFuIHRoZSBjb25uZWN0b3IsIGJlY2F1c2UgdGhlIGhpbmdlcyBhcmUg c28gdGlnaHQgdGhhdCBldmVyeSB0aW1lIHlvdSBvcGVuIG9yIGNsb3NlIHRoZSBsaWQgaXQg ZmxleGVzIHNsaWdodGx5LCBhbmQgZ2l2ZW4gdGhlIGV2ZW50cyBvZiB0aGUgZGF5LCBJJ20g bm93IHN1c3BpY2lvdXMgdGhhdCB0aGlzIGZsZXhpbmcsIG92ZXIgdGhlIHllYXJzIEkndmUg aGFkIHRoZSBQQyAoZnJvbSBuZXcpLCBpcyB0aGUgcm9vdCBjYXVzZSBvZiB0aGUgZGlzcGxh eSBnaXZpbmcgdXAuDQo+Pg0KPj4gIMKgIDotKMKgIEFsc28sIGl0J3MgcXVpdGUgYSBsaW1p dGVkIHNjcmVlbiByZXNvbHV0aW9uLCBhbmQsIGhhdmluZyBoYWQgdG8gcmVwbGFjZSBhbHJl YWR5IHR3byBvZiB0aGUgRGVsbCBQcmVjaXNpb24gTTYzMDBzIHdpdGggdGhlaXIgbG92ZWx5 IGJpZyBzY3JlZW5zIHdpdGhpbiBhYm91dCA2IG1vbnRocyBvZiBlYWNoIG90aGVyLCBJIG5v dyBoYXZlIHR3byBEZWxsIFByZWNpc2lvbiBNNjcwMHMgYm90aCBvZiB3aGljaCBhcmUgaGln aGVyIHNwZWMgdGhhbiB0aGlzLCBhbmQsIGFsdGhvdWdoIHRoZXkgZG9uJ3QgaGF2ZSB0aGUg c2FtZSBoZWlnaHQgcmVzb2x1dGlvbiBhcyB0aGUgNjMwMHMsIHRoZSBiZXR0ZXIgb2YgdGhl IHR3byBkb2VzIGhhdmUgYSBoaWdoZXIgc2NyZWVuIHJlc29sdXRpb24gdGhhbiB0aGlzLCBz byBJIHdhcyBwbGFubmluZyB0byB0dXJuIGl0IGludG8gbXkgcHJpbmNpcGFsIFBDIGFueXdh eS4NCj4+DQo+PiAgwqAgOi0owqAgQWxzbywgdGhlIEluc3Bpcm9uJ3Mgc3BlYWtlcnMgYXJl IGtuYWNrZXJlZC4NCj4+DQo+PiAgwqAgOi0owqAgQWxzbywgaXQgY2FuJ3QgZml0IGludG8g YSBkb2NrIGFzIGNhbiB0aGUgNjcwMC82ODAwL2V0YyBzZXJpZXMuDQo+Pg0KPj4gU28gSSB0 aGluayBJIG1pZ2h0IGp1c3QgbGV0IGl0IGdvLsKgIENhbid0IGNvbXBsYWluLCBpZiBpdCdz IHdvcnRoIG5vdGhpbmcgbm93LCBpdCB3b3JrcyBvdXQgdGhhdCBpdCdzIGNvc3QgbWUgwqM2 OXBhIGluIGRlcHJlY2lhdGlvbiwgYW5kIHRoYXQgc2VlbXMgcmVhc29uYWJsZSB0byBtZS4N Cj4gDQo+IFdoYXQgcGFydCBvZiB0aGUgcGFuZWwgd291bGQgdGhhdCBwYXR0ZXJuIGNvbWUg ZnJvbSA/DQoNCkR1bm5vLg0KDQo+IERpZCB5b3Ugc2hvb3QgdGhlIHBpY3R1cmUgd2l0aCBh IGhpZ2ggc3BlZWQgY2FtZXJhID8NCg0KQSBQaXhlbCA4YQ0KDQo+IERvZXMgdGhlIHBhdHRl cm4gc3RhbmQgc3RpbGwsIG9yIGRvZXMgaXQgdmFyeSBjb250aW51b3VzbHkgKGppZ2dsaW5n LCBkYW5jaW5nKSA/DQoNCkRlcGVuZHMsIG1vc3RseSBpdCdzIGZhaXJseSBzdGF0aWMsIGJ1 dCBpdCBoYXMgdmFyaWVkIHdoZW4gSSBtb3ZlIHRoZSANCm1vdXNlLCBhbmQgaXQgdmFyaWVz IGVub3Jtb3VzbHkgd2hlbiBJIG1vdmUgdGhlIGxpZCwgYW5kIHNvbWV0aW1lcyBJIGNhbiAN Cm1ha2UgdGVtcG9yYXJpbHkgZGlzYXBwZWFyIHRoZXJlYnksIG9ubHkgc29vbiB0byByZXR1 cm4uICBJdCBjb21lcyBhbmQgDQpnb2VzIHdoZW4gdGhlIGxpZCBpcyBzdGF0aW9uZXJ5LCBi dXQgaXMgbW9yZSBwcmV2YWxlbnQgd2hlbiB0aGUgZGlzcGxheSANCmZpcnN0IGNvbWVzIG9u IGFmdGVyIGJlaW5nIGJsYW5rZWQgZm9yIGEgd2hpbGUuICBUaGUgY29tcGxleGl0eSBvZiB0 aGUgDQpzY3JlZW5zaG90IEkgc2hhcmVkIGlzIHBhcnRseSBkdWUgdG8gdGhlIGNvbXBsZXhp dHkgb2YgdGhlIGxvZ2luIA0KYmFja2dyb3VuZCBwaWN0dXJlLiAgQWZ0ZXIgbG9nZ2luZyBp biwgdGhpbmdzIGxvb2sgc2ltcGxlciBhbmQgbW9yZSANCnJlZ3VsYXIuICBIZXJlIGlzIGEg cGhvdG8gb2YgdGhlIHNjcmVlbiB3aGlsZSBXaW5EaWZmIGlzIGNoZWNraW5nIGZvciANCmRp ZmZlcmVuY2VzIGJldHdlZW4gZHJpdmUgY29udGVudHMgb2YgdGhlIEluc3Bpcm9uIGFuZCB0 aGlzIE02NzAwIHdoaWNoIA0KSSBoYXZlIG5vdyBtb3ZlZCBvdmVyIHRvIHVzaW5nIGluc3Rl YWQsIHNvIHRoYXQgaWYgSSBkaXRjaCB0aGUgZm9ybWVyIEkgDQpjYW4gYmUgc3VyZSBvZiBu b3QgbG9zaW5nIGFueSBkYXRhICh0aGUgZGlmZmVyZW5jZXMgeW91IGNhbiBzZWUgdGhlcmUg DQphcmUgZWl0aGVyIHNwdXJpb3VzbHkgY2F1c2VkIGJ5IGFjY2VudGVkIGNoYXJhY3RlcnMg aW4gdGhlIGZpbGVuYW1lIG9yIA0KZWxzZSBnZW51aW5lbHkgZG9uJ3QgbWF0dGVyKToNCg0K d3d3Lm1hY2ZoLmNvLnVrL1RlbXAvMjAyNDA4MDFfRGVsbF9JbnNwaXJvbl8xNVJTRV83NTIw X1ZpZGVvX0ZhdWx0LmpwZw0KDQpOb3RlIHBhcnRpY3VsYXJseToNCg0KICAgLSBUaGUgJ2Nv bXBhcmluZyAuLi4nIGJhciBzaG91bGQgbm90IGNvbnRhaW4gYW55IGdyZWVuIGF0IGFsbDsN Cg0KICAgLSBUaGUgcmVndWxhciByZXBlYXRlZCBwYXR0ZXJucyBpbiB0aGUgdGl0bGUgYmFy LCBvZiB3aGljaCB0aGUgbGVhc3QgDQphbmQgbW9zdCBpbnRlbnNpdmVseSBncmVlbiBhcmUg ZmFpcmx5IHN0YWJsZSwgYnV0IHRob3NlIG1pZHdheSBiZXR3ZWVuIA0Kc29tZXRpbWUgamln Z2xlLg0KDQo+IFtzbmlwXQ0KPiANCj4gWW91IGNhbiB0YWtlIGEgc2NyZWVuc2hvdCwgd2l0 aCBhIHByaW50LXNjcmVlbiBvciB3aXRoIGEgc25pcHBpbmd0b29sLA0KPiBhbmQgc2VlIGlm IHRoZSBwYXR0ZXJuIGlzIGV2aWRlbnQuIEl0IHNob3VsZCBub3QgYmUsIGJlY2F1c2UNCj4g dGhlIGZhdWx0IGlzIGRvd25zdHJlYW0gb2YgdGhhdCBwb2ludC4gSWYgeW91IGNhbiBzZWUg YSBwcm9ibGVtDQo+IGF0IHRoYXQgcG9pbnQsIGl0IGNvdWxkIGJlIGEgc3lzdGVtIG1lbW9y eSBpc3N1ZSAoYW5kIG90aGVyDQo+IHN0dWZmIHdvdWxkIGhhdmUgY3Jhc2hlZCkuDQpJJ3Zl IGFscmVhZHkgdGhvdWdodCBvZiB0aGF0LCBhIHNjcmVlbnNob3QgdGFrZW4gd2l0aCA8UHJp bnRTY3JlZW4+IG9yIA0KPEFsdC1QcmludFNjcmVlbj4gd2hlbiB2aWV3ZWQgb24gYW5vdGhl ciBQQyBpcyBmcmVlIG9mIHRoZSBmYXVsdC4NCg0KLS0gDQoNCkZha2UgbmV3cyBraWxscyEN Cg0KSSBtYXkgYmUgY29udGFjdGVkIHZpYSB0aGUgY29udGFjdCBhZGRyZXNzIGdpdmVuIG9u IG15IHdlYnNpdGU6IA0Kd3d3Lm1hY2ZoLmNvLnVrDQoNCg==

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Folderol on Thu Aug 1 14:33:23 2024
    XPost: alt.os.linux, alt.windows7.general

    On Thu, 8/1/2024 9:35 AM, Folderol wrote:
    On Thu, 1 Aug 2024 14:30:26 +0100
    Java Jive <java@evij.com.invalid> wrote:

    I've already thought of that, a screenshot taken with <PrintScreen> or
    <Alt-PrintScreen> when viewed on another PC is free of the fault.


    The it's *definitely* either screen and/or screen connecting cable


    This could be the screen connecting cable.

    https://en.wikipedia.org/wiki/Transition-minimized_differential_signaling

    It claims the I/O is DC coupled (unlike PCI express, which is capacitively coupled).
    If a wire breaks, perhaps the output is a fixed set of symbols for that gun. Like most low amplitude diff signalling on a computer, the termination is 100 ohms
    (across each pair).

    The I/O needs four pairs (RGB Clock), three grounds for crosstalk isolation, then +12V and GND for power for the panel. If the data rate was 1650Mb/sec,
    the clock would be 165MHz. A PLL synthesizes a sampling clock (1650MHz).

    The panel needs to derive a signal called DE (Display Enable), which is a
    logic 1 for visible parts of the screen and logic 0 for the rest. If the
    panel cannot make DE, then the image should be a black screen. the 8B10B code provides opportunities (JK) for sending synchronization primitives. In its
    way, DE is the embodiment of HSYNC/VSYNC.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Paul on Fri Aug 2 00:21:48 2024
    XPost: alt.os.linux, alt.windows7.general

    On 01/08/2024 19:33, Paul wrote:

    On Thu, 8/1/2024 9:35 AM, Folderol wrote:

    On Thu, 1 Aug 2024 14:30:26 +0100
    Java Jive <java@evij.com.invalid> wrote:

    I've already thought of that, a screenshot taken with <PrintScreen> or
    <Alt-PrintScreen> when viewed on another PC is free of the fault.

    The it's *definitely* either screen and/or screen connecting cable

    This could be the screen connecting cable.

    I think it was (note the past tense) ...

    It occurred to me that I still have a spare unattached M6300 screen, so, assuming that they would have the same connectors at each end and
    therefore I could test the screen and cable separately, I started to
    dismantle the lid while it was still on the base. This was unwise,
    because too late I discovered that the lid is constructed in such a way
    as that it can only be completely dismantled when detached from the
    base, because there is a screw hidden under each hinge cover which is
    only accessible after the hinge cover has been removed, and this can
    only be done with the lid removed from the base. As a consequence, I
    broke the plastic attachment point of one of them through not realising
    this, so now I need a new lid, but have already found and ordered one
    that looks right for less than a tenner on eBay, which I was happy to do because that seems cheap by comparison with needing a new LCD which was
    what I expected to prove, but instead I ended up proving the opposite.

    When finally I got to it, the screen end of the connection cable is
    entirely different from the M6300 one, so I was forced after all to
    dismantle the main PC which I had been trying to avoid, only to find
    that the motherboard end was different as well. However, when instead
    of my planned test I just attached the Inspiron screen floating free on
    the desk back to the motherboard and switched on, there was no hint of
    green, no problem in fact, and so it remained for several hours, even
    when I tried moving the cable and the screen about on the desk.

    As I did not dare to try to disconnect the screen end of the cable,
    because it looked complicated and was covered with "Don't touch!"
    stickers, but I did remove and replace the motherboard end, my best
    guess now is that the motherboard end of the cable, through a process of heating up and cooling down, had walked itself partly out of its
    connecting socket. Supposedly this should have been prevented by it
    being held in place by sticky tape, but maybe that allows some creep
    when it warms up.

    However that may be, hopefully when the replacement plastic arrives I'll
    be able to restore the laptop to a fully working state.

    Thanks to all who've given help and advice along the way.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From NY@21:1/5 to Java Jive on Fri Aug 2 15:01:31 2024
    XPost: alt.os.linux, alt.windows7.general

    On 02/08/2024 00:21, Java Jive wrote:
    As I did not dare to try to disconnect the screen end of the cable,
    because it looked complicated and was covered with "Don't touch!"
    stickers, but I did remove and replace the motherboard end, my best
    guess now is that the motherboard end of the cable, through a process of heating up and cooling down, had walked itself partly out of its
    connecting socket.  Supposedly this should have been prevented by it
    being held in place by sticky tape, but maybe that allows some creep
    when it warms up.

    However that may be, hopefully when the replacement plastic arrives I'll
    be able to restore the laptop to a fully working state.

    Thanks to all who've given help and advice along the way.


    Good luck with getting the screen working again. There was a time when
    laptops were assembled in a way that made it easy to disassemble them.
    They had little access doors, held in place with a single screw, to get
    at the RAM DIMMs, the hard drive, and to slide out the CD or DVD drive.
    If you did need to remove the whole "lid", it was held on by lots of
    very obvious screws on the underside. The battery was held in place by a
    couple of slide locks and could be removed and replaced with a new one
    in a few seconds. You didn't have to use a spudger to release plastic spring-clips, or have to remove the keyboard to get at screws hidden underneath.

    But nowadays everything is fitted for life, and there is no expectation
    that the owner or a repair technician can swap out defective parts as
    they could with a desktop PC. When (not if) my present laptop battery
    stops holding its charge, goodness knows how I will get to the battery
    to replace it. The underside of the laptop only has two screws at one
    corner, so unless *all* the screws are hidden under the rubber strips
    that constitute the feet, then everything is held in place by clips or
    by screws that require access from the keyboard side.

    I do PC repairs for a living but I won't touch laptops if it's a
    hardware problem that requires the back to be removed, because of fear
    that I will break some fragile clip. Let some other poor sod attempt
    that work!

    In the "olden days", if a laptop failed to boot, a last resort was to
    remove the HDD, connect it as a slave drive via a USB-to-SATA or
    USB-to-IDE caddy interface, and read the user files in
    c:\users\<username> once Windows had gone through the lengthy "take
    ownership" process - assuming the user hadn't encrypted the drive. But
    if you can't get at the HDD, you're stuffed.


    I did once *try* to replace the backlight on one of my laptops. The
    screen worked perfectly but the backlight stopped working. I tried
    replacing the control circuit, which was comparatively easy to get to,
    but that didn't fix the problem so I had to remove the light itself - a
    narrow tube that was taped to the end of the glass of the screen without
    any location lugs that forced it to be in the correct alignment. I got
    it to work perfectly but try as I might I couldn't get the tube aligned sufficiently accurately to give vaguely even illumination across the
    width of the screen. I ended up using that laptop as a desktop - with a
    duff screen but always connected to an external monitor.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From NY@21:1/5 to Paul on Fri Aug 9 22:40:14 2024
    XPost: alt.os.linux, alt.windows7.general

    On 07/08/2024 00:05, Paul wrote:
    On Tue, 8/6/2024 6:06 PM, Java Jive wrote:


    Yes, and, one of the stupidest ever defaults of most recent versions of Windows, if you get a bluescreen it's been and gone before you can possibly read it as the laptop goes into an endless cycle of rebooting -  the only way you can read the details
    on the screen is to video it with a mobile phone and try, probably several times before you are lucky, to freeze the playback at exactly the right moment to be able to read it.  That most stupid of defaults is always one of the first things I change on
    any new installation of Windows.

    There is a setting for that. Disable "automatic restart" or so.
    This causes the blue screen to stand still. Then you can get out
    your magnifying glass, and read that annoying five point font
    the idiots selected for the code.

    That could be in sysdm.cpl somewhere.

    [Picture]

    https://i.postimg.cc/sghZL2h2/automatically-restart.gif

    For Windows 10, it's a slightly different route to the same option:

    https://i.postimg.cc/XqHSNgGk/Image1.png

    It was already turned off - and I don't remember doing it, so evidently
    Win 10's default it more sensible than Win 11's.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)