Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?}
- To: debian-user@lists.debian.org
- Subject: Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?}
- From: David Wright <deblis@lionunicorn.co.uk>
- Date: Sat, 3 Aug 2019 10:44:59 -0500
- Message-id: <[🔎] 20190803154459.nmvinlvmjmt6vcw7@wren.corp>
- Reply-to: debian-user@lists.debian.org
- In-reply-to: <a59ad3f2-f5eb-18f0-8bd3-4edd8187137a@cloud85.net>
- References: <3706dbf6-3b95-2458-071e-3e77581608ba@cloud85.net> <20190729081021.35b9aaec@debian9> <8c0b38b9-b810-02a9-4360-90dd0f5d069a@cloud85.net> <c5de1867-2bdb-65a0-fa1a-9b5440d6ce2e@cloud85.net> <20190729210835.ekhgsczlicewrfnt@wren.corp> <a59ad3f2-f5eb-18f0-8bd3-4edd8187137a@cloud85.net>
On Mon 29 Jul 2019 at 22:09:45 (-0500), Richard Owlett wrote:
> On 07/29/2019 04:08 PM, David Wright wrote:
> > On Mon 29 Jul 2019 at 11:56:25 (-0500), Richard Owlett wrote:
> > > On 07/29/2019 10:51 AM, Richard Owlett wrote:
> > > > On 07/29/2019 10:10 AM, Patrick Bartek wrote:
> > > > > [snip]
> > > > > Since your machines are very close together, take a look at USB to USB
> > > > > networking.
> > > >
> > > > Did ;} One of the first things I thought of as I date back days of
> > > > everyone having multiple RS-232 null modems.
> > > > Unfortunately the one I ended up with was extremely Windows-centric.
> > > > My WinXP machine recognized it with no problem. Whatever version
> > > > of Debian I was running at the time did not. The cardboard backing
> > > > of the bubblepak it came in was sticking out of my Misc
> > > > cubbyholes.
> > > >
> > > > It's website [https://plugable.com/products/usb-easy-tran/] claims:
> > > > > Linux kernels 3.0 and later support the cable as a high-speed
> > > > > virtual network interface, but offer no special file transfer support.
> > >
> > > Found cable.
> > > Plugged in to two Debian 9.8 machines with MATE DE.
> > > On both machines the Ethernet icon indicated it was attempting to connect.
> > > Both correctly reported manufacturer and model.
> > > One reported missing firmware.
> > >
> > > QUESTION:
> > > What log file(s) should I be watching for diagnostic information?
> >
> > # dmesg | grep firmware
> >
> > or
> >
> > # dmesg | less
> >
> > if you want a bit more context.
>
> Thank you. Thought I was going to be able run test this afternoon.
> Tomorrow is another day :>
So, did you find out what was missing, have you added it, and did you
manage host-host transfers and logins as you should have been able
to do?
Cheers,
David.
Reply to: