Can't install usb-serial application

[capke]

Hey everyone,

I am a very new user trying to feel my way through using PiCore for the first time, and I have hit a rather annoying roadblock. I'm trying to install the usb-serial-4.8.17-tinycore.tcz to my Pi3, but when I use the command tce-load -wi usb-serial-4.8.17-tinycore.tcz, I get the following message:

tc@box:~$ tce-load -wi usb-serial-4.8.17-tinycore.tcz
Downloading: usb-serial-4.8.17-tinycore.tcz
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: usb-serial-4.8.17-tinycore.tcz.md5.txt: No such file or directory
Error on usb-serial-4.8.17-tinycore.tcz

I can see the usb-serial driver in the tcz repository (http://distro.ibiblio.org/tinycorelinux/8.x/x86/tcz/), but maybe I am using the wrong one? I took this one directly from the Core website. I'm hoping this driver will let me use my USB to serial device I have, but without being able to download, I'm not able to find out. Any advice would be greatly appreciated!

[Rich]

Hi capke
That's the x86 repository, the one for Pi is here:
http://tinycorelinux.net/8.x/armv6/tcz/

[capke]

Ah, I see where I went wrong!

I attempted the new command with the proper usb-serial driver in your link, but I had the same error. I did a little investigating and found the 9.x repo, which I'm guessing is where the tce-load command dives into on the 9.0.3 piCore, and there is no usb-serial driver. Any chance this will be updated soon, or better yet, are there instructions on how to load from an old repo?

Thank you very much for your help! I like being able to see how this is supposed to work!

[Rich]

Hi capke
I doubt you could use one from the old repo. The numbers you see in the extension name (4.8.17) refer to the kernel
version it was compiled against. Since the version numbers don't match I think might even refuse to load.

[Juanito]

usb-serial extensions posted to piCore 9.x repos.

Note that you might be better off to download the extension like this:

Code: [Select]

$ tce-load -w usb-serial-KERNEL..which will download the correct extension for the version of piCore you are using.

[capke]

Thanks Juanito, I was able to install the driver. Unfortunately, I still can't find a ttyUSB connection. When I search using lsusb, it recognizes the usb device, but not that it is a serial port (I'm using 'dmesg | grep tty' to check for the converter). I have a XS885 from usconverters, and it uses the ftdi chipset. I made sure to download the libftdi, and after reboot, still no luck. Any advice would be greatly appreciated. Thanks again for your fast replies!

[patrikg]

Have you tried to monitor the udev ??
Try to run this command to see what the udev manager does to the sub event.

Code: (bash) [Select]

udevadm monitor

[flixxi]

I think I have the same problem here.

My Kernel version is 4.9.35-pcpCore (armv6l GNU/Linux), and from what I understood I should install something like  "usb-serial-4.9.35-pcpCore".
Is that assumption correct?

There is, of course, only "usb-serial-4.4.39-piCore+.tcz" available - I tried to install it but it didn't help.

What can I do to use my CH340 usb2serial interface? Were you able to solve the issue, capke?

[Greg Erskine]

Hi flixxi,

When you see "pcpCore" rather than "piCore" you know you are not using the standard release of piCore. You can not ask questions about piCorePlayer here, as the piCore developers will get upset. Better to ask at the squeezebox forum.

piCorePlayer doesn't always use the same kernel versions as piCore.

So, you need to go to the [Main Page] > [Extensions] web page, change the "Current repository" to "piCorePlayer sourceforge repository", then select the appropriate extension.

Sorry for going off topic piCore developers.

regards
Greg

[flixxi]

Hi Greg,

prior to my experiments with piCorePlayer I've never been in contact with piCore, and I assumed my system was standard piCore with only a few extra packages/scripts on top.
Sorry! And thank you for your help; I haven't tried yet but I strongly suspect that this is the clue that I needed to resolve the issue.
Best regards
Walter