On Jo, 16 dec 21, 23:30:37, Thomas Schmitt wrote:
> Hi,
>
> Jude DaShiell wrote:
> > [10200.545324] usb 3-1: Product: DISK
> > [10200.545329] usb 3-1: Manufacturer: Realtek
> > [10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected
> > [10200.546006] scsi host6: usb-storage 3-1:1.0
>
Jude DaShiell wrote:
> I have firmware-realtek installed for wireless devices and that's all
> debian offers.
but sometime if it is a new device on the market you may need either to wait
for the firmware to go to the package or you can download from vendor or
you can extract from the windows pack
Jude DaShiell wrote:
> hcitool and rfkill list showed nothing, according to them the device isn't
> there yet. I might be able to get this going with usb_modeswitch but need
> a product identifier and another item to do that.
based on the product name, find what is the chip inside and ask google
I have firmware-realtek installed for wireless devices and that's all
debian offers.
On Fri, 17 Dec 2021, deloptes wrote:
> Thomas Schmitt wrote:
>
> > I find its home page somehow confusing
> > https://www.draisberghof.de/usb_modeswitch/
> > But the web says that it is supposed to work automagi
hcitool and rfkill list showed nothing, according to them the device isn't
there yet. I might be able to get this going with usb_modeswitch but need
a product identifier and another item to do that.
On Fri, 17 Dec 2021, deloptes wrote:
> Jude DaShiell wrote:
>
> > Dec 16 17:10:08 taf systemd[1]
Jude DaShiell wrote:
> Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth
> service being skipped.
> Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service
> 'org.bluez': timed out (service_start_timeout=25000ms)
> Dec 16 17:20:36 taf kernel: Bluetooth: Core v
Thomas Schmitt wrote:
> I find its home page somehow confusing
> https://www.draisberghof.de/usb_modeswitch/
> But the web says that it is supposed to work automagically for known
> devices.
may be OP is needing the firmware and this mode is a fallout mode. It is
strange if it would need usb_mode
firmware-realtek has been installed a while ago. I'm probably going to
have to run usb-modeswitch against the device.
On Thu, 16 Dec 2021, Jude DaShiell wrote:
>
>
> On Thu, 16 Dec 2021, deloptes wrote:
>
> > Jude DaShiell wrote:
> >
> > > No Linux firmware came on the disk only windows files.
On Thu, 16 Dec 2021, deloptes wrote:
> Jude DaShiell wrote:
>
> > No Linux firmware came on the disk only windows files. To that extent I
> > checked. On debian does a way exist to check devices for missing
> > firmware?
> >
>
> in the log file journalctl or /var/log/syslog, after plugging in
Hi,
Jude DaShiell wrote:
> [10200.545324] usb 3-1: Product: DISK
> [10200.545329] usb 3-1: Manufacturer: Realtek
> [10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected
> [10200.546006] scsi host6: usb-storage 3-1:1.0
> [10201.560487] scsi 6:0:0:0: CD-ROMRealtek Driver
Havbing removed the device I ran dmesg| wc -l.
Inserting the device I ran dmesg| wc -l again and got a difference of 11
lines.
So dmesg >dmesg.log and tail -11 dmesg.log got me this information.
[10200.545324] usb 3-1: Product: DISK
[10200.545329] usb 3-1: Manufacturer: Realtek
[10200.545637] usb-s
Jude DaShiell wrote:
> No Linux firmware came on the disk only windows files. To that extent I
> checked. On debian does a way exist to check devices for missing
> firmware?
>
in the log file journalctl or /var/log/syslog, after plugging in the usb (I
am not sure if it is usb stick, because yo
On 2021-12-16 21:45 UTC+0100, Jude DaShiell wrote:
> No Linux firmware came on the disk only windows files. To that extent I
> checked. On debian does a way exist to check devices for missing
> firmware?
>
>
> On Thu, 16 Dec 2021, deloptes wrote:
>
>> Jude DaShiell wrote:
>>
>>> So in reali
No Linux firmware came on the disk only windows files. To that extent I
checked. On debian does a way exist to check devices for missing
firmware?
On Thu, 16 Dec 2021, deloptes wrote:
> Jude DaShiell wrote:
>
> > So in reality this may actually not be a card
> > The disk that came with this cl
Jude DaShiell wrote:
> So in reality this may actually not be a card
> The disk that came with this claimed it was an realtek-0179 device if
> memory serves.
did you check firmware if required - do you have it installed?
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
On Thu, 16 Dec 2021, Christian Britz wrote:
>
>
> On 2021-12-16 20:01 UTC+0100, Dan Ritter wrote:
> > Jude DaShiell wrote:
> >> bnep 20480 0
> >> bluetooth 483328 1 bnep
> >> ecdh_generic 16384 1 bluetooth
> >> ecc40960 1 ecdh_gene
On Thu, 16 Dec 2021, Dan Ritter wrote:
> Jude DaShiell wrote:
> > bnep 20480 0
> > bluetooth 483328 1 bnep
> > ecdh_generic 16384 1 bluetooth
> > ecc40960 1 ecdh_generic
> >
> > That's relevant output from lsmod.
> > If I run inxi
On 2021-12-16 20:01 UTC+0100, Dan Ritter wrote:
> Jude DaShiell wrote:
>> bnep 20480 0
>> bluetooth 483328 1 bnep
>> ecdh_generic 16384 1 bluetooth
>> ecc40960 1 ecdh_generic
>>
>> That's relevant output from lsmod.
>> If I run inx
Jude DaShiell wrote:
> bnep 20480 0
> bluetooth 483328 1 bnep
> ecdh_generic 16384 1 bluetooth
> ecc40960 1 ecdh_generic
>
> That's relevant output from lsmod.
> If I run inxi -E
> that returns no bluetooth data available.
> This is
bnep 20480 0
bluetooth 483328 1 bnep
ecdh_generic 16384 1 bluetooth
ecc40960 1 ecdh_generic
That's relevant output from lsmod.
If I run inxi -E
that returns no bluetooth data available.
This is supposed to be linux-compatible.
Unfortu
20 matches
Mail list logo
