Recommended Posts

Well CRAP! Was installing the OS for my main set up tonight, smelled burning components. NOOOOOOO!!!!!!! Power light burned up on the board. Now I get to set up an RMA for exchange tomorrow.

Anyone know if there are still issues with obtaining a Pi given their history of slow orders? From what I understand - this one took a heck of a long time to get in November. Was purchased through Element 14 so hopefully that makes a difference.

I was running off of the usb port on my laptop which worked perfectly last night. The laptop was also powered by the mains so not off of battery. Not that it bugs me really having the bright red light off, but it does in a way knowing that it just isn't working now.

UPDATE: After waiting well over a week for Element 14 to get back to me on the unit, am now getting the RMA set up. They have to now have yet another department email the RMA info to me.

One thing I learned about them though, is with them, if you do an RMA - it isn't a standard RMA like most companies AFAIK work it. RMA is issued (Normal), once they get your return, they refund your credit card for purchase, no exchange unless you ask for one. But irregardless - you exchange the Pi, they still refund your card and then charge it again for price of new one.

Normally, this isn't such an issue, however when it comes to a gift being given to someone - (in my case), then you have to go through the hassle of contacting gift giver, to let them know you are RMA'ing the device (Signals bad product purchase to them and possible hurt feelings), then let them know that their card will be refunded. Can be a tad uncomfortable.

Anyway, advice for those who use a Pi - was told that to never run off of computer USB by them (Element 14) and sort of by Raspberry Pi's site as well:

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=27066&p=242583#p242583

This topic is now closed to further replies.
  • Posts

    • Lego Batman 2026 hahahaha. You thought I couldn't reply back???
    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      82
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!