@TolkemI absolutely was going to delete the whole line.
This is what I was afraid of and why I piped up and put in my two cents worth!!
I'm glad you understand.
@TolkemI absolutely was going to delete the whole line.
Tolkem, I see you did tell me explicitly how to use search. I was so excited to try it I got off line before taking notes. I wanted to get back on to tell you, there was no 'Hash #' before the word 'modem', so no changes were made. You did mean remove the Hash from that line only, correct.
Should I uncomment [if that's correct, remove harsh from 'persist' or anything
So the modem is seen by the system ... I thought it wasn't. Can you please post the output of that? Open a terminal and typeyet when I put in lsusb the name and location of the modem is seen
lsusb
I'm sorry but I don't see any Device 006 on the screenshot, it goes up to 5 but no 6. Nor I see any of the details you mentioned on the device. You sure this' the right screenshot?The modem showed as Bus 003 Device 006: ID 0803::3095 ZoomTelephonics, Inc. v.92 56kn Mini External Modem Model 3095.
Ah, now I see it. Ok, let's check which driver it is using, if any. Open a terminal and typeNo you would not see it on that snapshot as the modem was not plugged in. I'm at home now on the Windows machine and I have a screenshot with the Fujitsu Linux machine with the modem plugged in.
lsusb -tv
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
ID 1d6b:0001 Linux Foundation 1.1 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
ID 1d6b:0001 Linux Foundation 1.1 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
ID 05c8:0348 Cheng Uei Precision Industry Co., Ltd (Foxlink)
|__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
ID 05c8:0348 Cheng Uei Precision Industry Co., Ltd (Foxlink)
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
ID 0951:1607 Kingston Technology DataTraveler 100
|__ Port 3: Dev 9, If 0, Class=Mass Storage, Driver=usb-storage, 480M
ID 0951:1607 Kingston Technology DataTraveler 100
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=, 480M
ID 0951:1607 Kingston Technology DataTraveler 100
@Vicktoria if a BIOS update is what you want you should go to the manufacturers web site and find the support page for your exact model of computer.Is the BIOS driver what would be updated in a BIOS update?
@Vicktoria if a BIOS update is what you want you should go to the manufacturers web site and find the support page for your exact model of computer.
. . .
Sometimes BIOS updates can fix the types of problems you are describing.
Hello Wiley One, Yes I too am disappointed about clonezilla, yet it made me suspect that the issue is with the kernel not communicating properly between the hardware and the programs. I think this is a telling clue, yet I'm not literate enough to know where the issue might be or how to remedy things. Yes I've been having BIOS issues yet have never done anything other than reset things by replacing CMOS battery.I believe this was mentioned and BIOS update was found, at the outset! (Don't recall which thread)
Am disappointed the clonezilla did not work as planned, though.
What, exactly, was the purpose of the BIOS update? In other words, what did the manufacturer say the BIOS update fixed or what new features did it enable?I downloaded the BIOS offerings from the manufacturers site specifically for my model and then OS. I just don't understand if BIOS is the same as BIOS driver, etc.
Reading here might help https://en.wikipedia.org/wiki/BIOS You need to run that command while the problematic modem is connected to check whether it is using a driver and which one.I just don't understand if BIOS is the same as BIOS driver,
and I hate to try to upload screenshots on the possible slower speed I'll get when I connect again.
Possibly. But if the USB ports and such were working before then I would not likely suspect a BIOS update.BIOS most likely needs to be flashed so that variables concerning the USB ports and optical drive may be eliminated, IMO.
In your first post you saidThe usbs never were recognized on Cinnamon 19.3. They were recognized on 18.3 Trisia [whatever Trisia's number was]
So I have to ask, which one are you currently using and having issues with? 19.3 or 18.3?I am installing another Mint version 19.3 Cinnamon