Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The firmware should be in /lib/firmware/rtlwifi/, but appears to be missing. As expected for a distro that excludes non-free blobs. If you want to use that card you need to acquire and install the firmware for it.
Then reboot and the driver should load the now existing firmware and hopefully work. You could also modprobe -r and modprobe the rtl8192ce module to avoid rebooting. Things like this is why I like to install linux in linux with stuff like arch-chroot or debootstrap. It lets you get all the quirky networking stuff worked out before you have to actually use the network on a fresh install.
Most times I have ethernet options to other devices that handle wifi. In days of old my asus rt-n12 handled this ($40 at frys). But I gave my asus rt-n16 to my dad so now I only have the rt-n12 for the ISP side of wifi. So I ethernet to another laptop that bridges to the wifi. Someday I'll get a raspberry pi 3 or better and it'll handle that task.
@#31: oh! I'm -learning-, in VBox, so I'm -not- aware of the whole concept of firmware *.bin
So, my post #29 probably won't work (fully anyway). I'm confused/lost (what will happen?):
`modinfo rtl8192ce` on Trisquel doesn't list the "firmware: ... .bin" (but has the .ko !)
@#31: oh! I'm -learning-, in VBox, so I'm -not- aware of the whole concept of firmware *.bin
So, my post #29 probably won't work (fully anyway). I'm confused/lost (what will happen?):
`modinfo rtl8192ce` on Trisquel doesn't list the "firmware: ... .bin" (but has the .ko !)
Normally when it's missing it'll show up in dmesg. It'll also show up when it isn't missing.
$ dmesg | grep -i firmware
If you examine the source or use strings on the binary that is the kernel module (.ko), you'll see it there too.
For debian jessie on a 64 bit system. For other drivers it tends to end in .fw. Like my ethernet one for a device I actually have on the system I'm posting from.
Which firmware gets used depends on the hardware, so there will be more listed there than will get used by your system and your hardware. Replace 3.16.0-4-amd64 with $(uname -r) if you're not using debian. Although without the actual name, tab completion doesn't aid you in long path names.
p.s. this [note different rtl18##!] is 'expected'
# modinfo rtl8188ce
modinfo: ERROR: Module rtl8188ce not found.
Look for a net device *if&after* those modprobe rtl8192ce -work-, with:
ip a
ifconfig -a
The/my idea/guess is that: the rtl8192ce driver [might/probably] -work ok- for your rtl8188ce: http://wiki.debian.org/rtl819x web-search: RTL8188CE RTL8192CE linux
I can't even take specific parts of this post to respond, because I don't even get what part is what!
Jjanel, I think you just graduated from Chinese to Minoan!
Is this even legal?
Anybody wanna help??
Last edited by Vexon; 02-08-2017 at 03:48 PM.
Reason: Add Smiley!
... if you could somehow install the Atheros card, ...
I don't think that'll be happening. Unless, again, someone can suggest a way of doing that.
Quote:
there is a good chance that it [the Atheros card] will have exactly the same problem as the Realtek one and require additional software in order to enabled in Linux.
I am glad you said that, because I think I will have to switch that machine to GNU at some point too. A question though: Don't most Atheros cards have free drivers? I certainly saw some of them being advertised as precisely for being free/libre.
Quote:
Most Linux users have a special drawer containing several of these "tricky"/useless wireless adapters.
The firmware should be in /lib/firmware/rtlwifi/, but appears to be missing. As expected for a distro that excludes non-free blobs. If you want to use that card you need to acquire and install the firmware for it.
Then reboot and the driver should load the now existing firmware and hopefully work.
What's the difference between the firmware and the driver? I think this is important, because if firmware is the software already present in the physical chip, and if I would be changing that, I would like to back it up first!
Again:
Quote:
the driver should load the now existing firmware
Anybody can provide some information please!
P.S.: By the way, the rest of the post went into a secondary language again for me (though I understood quite a bit, so it's not Chinese!).
Quote:
You could also modprobe -r and modprobe the rtl8192ce module to avoid rebooting. Things like this is why I like to install linux in linux with stuff like arch-chroot or debootstrap. It lets you get all the quirky networking stuff worked out before you have to actually use the network on a fresh install.
Most times I have ethernet options to other devices that handle wifi. In days of old my asus rt-n12 handled this ($40 at frys). But I gave my asus rt-n16 to my dad so now I only have the rt-n12 for the ISP side of wifi. So I ethernet to another laptop that bridges to the wifi. Someday I'll get a raspberry pi 3 or better and it'll handle that task.
Last edited by Vexon; 02-08-2017 at 04:07 PM.
Reason: Change Wording!
@#31: oh! I'm -learning-, in VBox, so I'm -not- aware of the whole concept of firmware *.bin
So, my post #29 probably won't work (fully anyway). I'm confused/lost (what will happen?):
`modinfo rtl8192ce` on Trisquel doesn't list the "firmware: ... .bin" (but has the .ko !)
The first compromise is to ditch Trisquel and use another distro, ...
Again, beachboy2, why would I need to do that? Can I not install this freak'n driver (free or non-free, doesn't matter) and be done with it? I mean, is this really this difficult?
For debian jessie on a 64 bit system. For other drivers it tends to end in .fw. Like my ethernet one for a device I actually have on the system I'm posting from.
Which firmware gets used depends on the hardware, so there will be more listed there than will get used by your system and your hardware. Replace 3.16.0-4-amd64 with $(uname -r) if you're not using debian. Although without the actual name, tab completion doesn't aid you in long path names.
I thought I owned this thread, but... Maybe not.
I let you two lads chat in your language I guess...
I think he was following up on Shadow_7's idea (I think) of making sure that you have the driver module installed along with the firmware, otherwise just installing the firmware will do no good. Using the command "modinfo" and then the driver name would be a way of verifying that.
Regards...
Last edited by ardvark71; 02-08-2017 at 04:46 PM.
Reason: Added information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.