Skip Navigation

Posts
14
Comments
506
Joined
2 yr. ago

  • Oh one other idea is your local electronics recycling centre. Our one frequently has battered Chromebooks. One by the same brand might do you. The folks in our one are friendly and would definitely give it to you for free so you might get lucky there too. Maybe leave your phone number with them also.

    On your question about the loose power - I'd say that's a dry or loose solder joint. If you're comfortable with a soldering iron it should be easily fixed. Occasionally a heavily used connector just loses grip and if that's the case a gentle squeeze with a pliers will do you.

  • Good luck! If you can't find one for sale it might be worth posting up in a local Facebook group or equivalent asking if anyone has one. Folks frequently don't think of selling broken kit.

  • Must be. I'd call them an egg slice or fish slice like yourself. Spatula to me is silicone. Western Europe.

  • I would probably search local online markets for a broken one of your current Chromebook. The battery will likely do what you want and you'll have it for other spares too.

  • Love this one!

  • Deleted

    Permanently Deleted

    Jump
  • My kids always struggle to get presents for me because I have everything I want. I'm a simple man.

    Have you asked him if there's anything he'd like? He might have something in mind.

    When asked I always say socks. I love the Nike dri-fit socks. Black. I now have a lot of them because I've been saying "Socks. No I really mean it" for ages.

    It's such a simple joy to grab any two socks from my drawer and know that they'll match and be very comfy.

    Edit: other than that I'd suggest something that he'll use frequently and think of you. Another poster suggested tools which is a good one. A good coffee mug or nice glass is good too.

  • The ice cream truck stopped coming to our estate about 5 years ago though there are plenty of kids about.

    I do see them parked near playgrounds etc. quite a bit but not doing the rounds like they used to.

  • Yeah if you're happy to post I'm happy to see posts.

  • Incredible summary. 10/10.

  • You're not going to believe this but someone else commented above that it might be the HDMI cable or monitor and unbelievably they were correct. Ping immediately restored once I unplugged it then went bad again when I replugged.

    I've rotated the deck 90 degrees and it's a lot better.

  • Holy. Fucking. Shit.

    This was it.

    Here's my ping output. You can see where I unplugged and replugged the HDMI cable. Absolutely not in my wildest dreams would I have thought of this. Thank you so much.

     
        
    (1)(deck@steamdeck ~)$ ping google.ie
    PING google.ie (74.125.193.94) 56(84) bytes of data.
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=1 ttl=108 time=818 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=2 ttl=108 time=674 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=3 ttl=108 time=308 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=4 ttl=108 time=289 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=5 ttl=108 time=404 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=6 ttl=108 time=25.7 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=7 ttl=108 time=17.2 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=8 ttl=108 time=19.6 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=9 ttl=108 time=18.6 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=10 ttl=108 time=19.4 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=11 ttl=108 time=17.0 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=12 ttl=108 time=16.0 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=13 ttl=108 time=17.0 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=14 ttl=108 time=17.5 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=15 ttl=108 time=25.2 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=16 ttl=108 time=17.1 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=17 ttl=108 time=15.2 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=18 ttl=108 time=19.7 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=19 ttl=108 time=14.0 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=20 ttl=108 time=21.2 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=21 ttl=108 time=20.3 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=22 ttl=108 time=18.8 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=23 ttl=108 time=13.9 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=24 ttl=108 time=18.1 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=25 ttl=108 time=12.9 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=26 ttl=108 time=17.9 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=27 ttl=108 time=16.1 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=28 ttl=108 time=19.1 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=29 ttl=108 time=15.1 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=30 ttl=108 time=16.2 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=31 ttl=108 time=16.4 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=32 ttl=108 time=18.1 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=33 ttl=108 time=21.7 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=34 ttl=108 time=23.2 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=35 ttl=108 time=411 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=36 ttl=108 time=287 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=37 ttl=108 time=412 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=38 ttl=108 time=2445 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=39 ttl=108 time=1679 ms
    64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=40 ttl=108 time=666 ms
    ^C
    --- google.ie ping statistics ---
    41 packets transmitted, 40 received, 2.43902% packet loss, time 40064ms
    rtt min/avg/max/mdev = 12.890/223.052/2445.465/478.256 ms, pipe 3
    
    
      
  • Thanks. I can't see it in the KDE settings but will give that a whirl.

  • It's WiFi, 3rd party dock (but deck WiFi), ISP router which is unaffected on other devices, OS is right up to date.

    I did reboot the ISP router just before posting and the issue still persisted until I rebooted the deck at which point it was gone.

    edit: It's gone to shit again. I got a network analyzer on my phone and ping is clean as a whistle on it while the deck is averaging 400ms.

  • My wife had a favourite song when she was pregnant and it was very useful for calming after the birth. It was quite a chill tune.

  • Depends how many you're shopping for. My nearest supermarket is about a kilometre away and if I'm going there I'll always walk. That's a grand distance even with a heavy shop.

    I'd do 3 if I was just buying for myself but it's at the upper limit depending on weight, especially in 30C (I presume dry heat because fuck that shit otherwise).

  • I dunno. I was never gonna reply to her but that Facebook game sounds pretty mega.

  • Ah I eventually discovered that it was a scheduled signal message. Cheers though.

  • This was going to be my next port of call but another comment caused me to figure out that if was a scheduled signal message.

  • Thanks. I was about to do this but another comment caused me to check scheduled messages. It was signal.

    Edit: I went in here to look anyway and this would have definitely caught it. Thanks for the suggestion.

  • Just updated the comment above yours. It was a scheduled message in signal. Thanks!