From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] m.2 nvme stick not what I was expecting at all.
Date: Tue, 25 Feb 2025 20:21:08 +0000 [thread overview]
Message-ID: <2301876.iZASKD2KPV@rogueboard> (raw)
In-Reply-To: <c1ec5b88-ef9b-4c61-a635-62c5e7da356e@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Tuesday, 25 February 2025 20:19:18 Greenwich Mean Time Wol wrote:
> On 25/02/2025 15:04, Rich Freeman wrote:
> > That said, there is nothing "wrong" with buying M.2 drives just to use
> > them exclusively USB3 enclosures. I just think you're paying a big
> > premium for something that isn't really much better than a thumb
> > drive.
>
> Until you get a TV like ours, that DEMANDS a disk drive to hang off its
> USB. I tried sticking a USB3 stick in, and it refused. Hang a bare
> laptop HDD off it, and it's quite happy.
>
> So I'm hoping a M2 in an enclosure will keep it happy ...
>
> (Of course, every other TV I've ever had is perfectly happen with just a
> USB stick!)
>
> Cheers,
> Wol
Some 'smart' TVs won't use a USB drive unless and until they've formatted it
first. I've attached a 3" drive in a USB 3.0 docking station and it worked
fine *after* it was formatted. Then it wouldn't unmount it, even after I had
shutdown the TV. I can't recall what fs format it had used.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-25 20:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:58 [gentoo-user] m.2 nvme stick not what I was expecting at all Dale
2025-02-24 19:20 ` Jack
2025-02-24 19:49 ` Dale
2025-02-24 19:40 ` Mark Knecht
2025-02-24 19:41 ` Rich Freeman
2025-02-24 19:53 ` Dale
2025-02-24 20:00 ` Rich Freeman
2025-02-24 20:34 ` Dale
2025-02-24 20:02 ` eric
2025-02-24 20:11 ` Mark Knecht
2025-02-24 20:44 ` Dale
2025-02-24 22:48 ` Frank Steinmetzger
2025-02-25 3:56 ` Dale
2025-02-25 10:08 ` Michael
2025-02-25 11:00 ` Dale
2025-02-25 11:16 ` Michael
2025-02-25 15:57 ` Dale
2025-02-25 17:05 ` Rich Freeman
2025-02-25 19:00 ` Michael
2025-02-25 19:18 ` Rich Freeman
2025-02-25 20:39 ` Michael
2025-02-25 22:16 ` Frank Steinmetzger
2025-02-25 14:48 ` Peter Humphrey
2025-02-25 17:00 ` Michael
2025-02-24 22:13 ` Frank Steinmetzger
2025-02-25 4:20 ` Dale
2025-02-25 8:18 ` Wols Lists
2025-02-25 14:07 ` [gentoo-user] " Grant Edwards
2025-02-25 8:20 ` [gentoo-user] " Wols Lists
2025-02-25 11:09 ` Dale
2025-02-25 12:26 ` Dale
2025-02-25 15:04 ` Rich Freeman
2025-02-25 15:32 ` Dale
2025-02-25 16:29 ` Rich Freeman
2025-02-25 17:26 ` Dale
2025-02-25 17:41 ` Rich Freeman
2025-02-26 14:43 ` Dale
2025-02-26 16:38 ` Michael
2025-02-26 20:34 ` Dale
2025-02-26 20:48 ` Mark Knecht
2025-02-25 20:19 ` Wol
2025-02-25 20:21 ` Michael [this message]
2025-02-25 21:34 ` Frank Steinmetzger
2025-02-26 7:52 ` Wols Lists
2025-02-26 16:44 ` Michael
2025-02-26 18:03 ` Wol
2025-02-26 18:05 ` Rich Freeman
2025-02-26 18:42 ` Wol
2025-02-26 19:26 ` Rich Freeman
2025-02-26 19:47 ` Wols Lists
2025-02-26 19:56 ` Rich Freeman
2025-02-26 21:25 ` Wol
2025-02-26 22:37 ` Michael
2025-02-26 16:41 ` Michael
2025-02-28 5:43 ` Dale
2025-02-28 16:40 ` [gentoo-user] " Grant Edwards
2025-03-02 16:01 ` Dale
2025-03-02 22:06 ` Frank Steinmetzger
2025-03-02 22:39 ` Dale
2025-03-03 3:01 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2301876.iZASKD2KPV@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox