5 ms·

It could be worse. I had a low-end Chromebook that I bought to put Linux on it. Part of the reason for this was that I needed a wi-fi repeater and extra screen

It could be worse. I had a low-end Chromebook that I bought to put Linux on it. Part of the reason for this was that I needed a wi-fi repeater and extra screen for my dev machine. A long time later my needs changed and I switched back to running ChromeOS. This install was because I wanted to gift the Chromebook to a friend. So we tested YouTube and the Chromebook was mute. It turned out that installing Linux fried something inside and only a new motherboard would fix that. Luckily I was still on the right side of the warranty expiring, therefore, with no love for the shop I bought it from, I decided to try my luck at getting it repaired. The machine came back box fresh with superb sound. So I was able to gift a 'brand new' machine (which happens to still be on sale) rather than some hand-me down. I am still on Chromebook Pixel 2013 vintage and very happy with it, the Pixelbook was 'meh' to me even though I think I really need one. I was disappointed that they did not go 8th generation Intel with the CPU during this year's product launches for the Pixelbook. So I am now viewing my Pixel (2013) as a future classic, not that computers have this status (Apple 1, Altair excepted). I think Pixelbooks will also have this status but I don't see an 'investment opportunity' in getting one in the hope it will be worth $$$ in decades to come.

gcb0 8y ago
lol. something fried because google hardware is notoriously bad, not "because you installed linux". Hardware is not supposed to fry because the software told it to.
- Theodores 8y ago
  I wasn't clear there as I didn't want to namedrop the brand of the $300 machine, it began with the first letter of the alphabet and was a four letter name. It is not the hardware that is a problem with Google products, there is no 'you must be holding it wrong' nonsense. The problem Google have is in the support. Utterly awful. They have absolutely no idea, as if they are not able to empathise with the customer in any way whatsoever. A budgerigar is as much help. Fortunately my five year old Pixel is as good as new, not a scratch. Despite its age it still impresses people whether they know what it is or not. Few computers do that these days. The wow factor isn't quite up to 'SGI' standards but I always say it is just 'a cheap really old Chromebook'. The room filling sound from the speakers under the keyboard is something I can't believe the newer Pixelbook has to quite the same level of 'high fidelity', I would be gutted if that died due to some upgrade. This won't happen though as updates no longer happen (as of a week ago) due to the age of it. The 2560x1700 'retina plus' native screen mode is also a true delight, particularly with dev tools open. People struggle to read the text and, with them not used to having pinch-to-zoom on their Applebooks, they are amazed that the zoom works just like on a phone.
  - PascLeRasc 8y ago
    edit: mistake but too late to delete.
    - komaromy 8y ago
      I think they meant Pixelbook.
- PascLeRasc 8y ago
  Sometimes it's a little of hardware and software's fault: https://www.dell.com/support/article/us/en/04/sln186332/distorted-sound-from-notebook-speakers-when-using-vlc-media-player?lang=en https://www.dell.com/support/article/us/en/04/sln186332/dist...
  - pritambaral 8y ago
    That is 100% the hardware's fault. I'm including firmware and drivers for the audio card in "hardware".
- bryanbuckley 8y ago
  "not supposed to" is pretty idealistic, the goal. Anyone working on firmware, drivers, or other low level SW will assure you that SW can fry, shorten the lifespan of, or otherwise brick HW.
- pjmlp 8y ago
  Many of us were very careful to avoid frying our monitors while configuring X Windows on BSD/Linux back in the old days.
xrd 8y ago
I'm in the same boat. My original pixel is awesome and never had an issue with it. Of course, can't run containers in it but otherwise it's perfect.
rstuart4133 8y ago
> So we tested YouTube and the Chromebook was mute. It turned out that installing Linux fried something inside and only a new motherboard would fix that. I have a $3K Dell XPS 9550 on which I run Debian. One of the things many reviewers noted was "wow those inbuilt speakers are loud". And indeed they are loud, it turned out too loud as they burn out. The fix from Dell was new Windows drivers. As a consequence I've had my speakers replaced under warranty twice now. The second time I swear it was only seconds before I frantically turned the sound down. Alas it was too late. I can't imagine Dell replacing them for free more many few times, so now I'm paranoid about what is really a hardware bug.

gcb0 8y ago

lol. something fried because google hardware is notoriously bad, not "because you installed linux". Hardware is not supposed to fry because the software told it to.

Theodores 8y ago
I wasn't clear there as I didn't want to namedrop the brand of the $300 machine, it began with the first letter of the alphabet and was a four letter name. It is not the hardware that is a problem with Google products, there is no 'you must be holding it wrong' nonsense. The problem Google have is in the support. Utterly awful. They have absolutely no idea, as if they are not able to empathise with the customer in any way whatsoever. A budgerigar is as much help. Fortunately my five year old Pixel is as good as new, not a scratch. Despite its age it still impresses people whether they know what it is or not. Few computers do that these days. The wow factor isn't quite up to 'SGI' standards but I always say it is just 'a cheap really old Chromebook'. The room filling sound from the speakers under the keyboard is something I can't believe the newer Pixelbook has to quite the same level of 'high fidelity', I would be gutted if that died due to some upgrade. This won't happen though as updates no longer happen (as of a week ago) due to the age of it. The 2560x1700 'retina plus' native screen mode is also a true delight, particularly with dev tools open. People struggle to read the text and, with them not used to having pinch-to-zoom on their Applebooks, they are amazed that the zoom works just like on a phone.
- PascLeRasc 8y ago
  edit: mistake but too late to delete.
  - komaromy 8y ago
    I think they meant Pixelbook.
PascLeRasc 8y ago
Sometimes it's a little of hardware and software's fault: https://www.dell.com/support/article/us/en/04/sln186332/distorted-sound-from-notebook-speakers-when-using-vlc-media-player?lang=en https://www.dell.com/support/article/us/en/04/sln186332/dist...
- pritambaral 8y ago
  That is 100% the hardware's fault. I'm including firmware and drivers for the audio card in "hardware".
bryanbuckley 8y ago
"not supposed to" is pretty idealistic, the goal. Anyone working on firmware, drivers, or other low level SW will assure you that SW can fry, shorten the lifespan of, or otherwise brick HW.
pjmlp 8y ago
Many of us were very careful to avoid frying our monitors while configuring X Windows on BSD/Linux back in the old days.

xrd 8y ago

I'm in the same boat. My original pixel is awesome and never had an issue with it. Of course, can't run containers in it but otherwise it's perfect.

rstuart4133 8y ago

> So we tested YouTube and the Chromebook was mute. It turned out that installing Linux fried something inside and only a new motherboard would fix that. I have a $3K Dell XPS 9550 on which I run Debian. One of the things many reviewers noted was "wow those inbuilt speakers are loud". And indeed they are loud, it turned out too loud as they burn out. The fix from Dell was new Windows drivers. As a consequence I've had my speakers replaced under warranty twice now. The second time I swear it was only seconds before I frantically turned the sound down. Alas it was too late. I can't imagine Dell replacing them for free more many few times, so now I'm paranoid about what is really a hardware bug.