I have Slackware64 14.2, KDE and 52.6.0. I call play .mp4 videos in web pages. I get "No video with supported format and MIME type found." I can view this same video with firefox in Windows. Web searches have turned up comments for other distros involving missing codecs, but I've found nothing for Slackware. Solution?

You might need a new firefox build.

You need ffmpeg with opus, h264, aac, libvpx, & vorbis at least (from looking at the codec from youtube videos): https://slackbuilds.org/repository/1...imedia/ffmpeg/

Install ffmpeg.

That worked! Thanks!

Hello, in what forum and how can I ask you a question about wi-fi, broadcom / BCM4312, I do not know if it's any good to tell you brand of the pc, I find it stupid when they put up what color are the wires of your pc, hp mini-110, please indicate me the appropriate channel and media to ask you this question and if you need any specific information that I have to put in the question to make things easier so you can help me kill my stupidity and ignorance

shukraan | شكرا

If this is your first posts after three years of idling, then you could have expected this answer:
Please open your own thread in the forum which is appropriate for the Linux distribution you are using. Or else, if you have a generic question which has no relation to the Linux distro you are using, then please create your own new thread in the "Linux - General" forum.
Just ask your question, be as specific as possible, don't leave out the details because anything can be relevant. Do not think you are stupid or ignorant if you need to ask a question - you learn most and best if you did your own thinking first, did not find the answer and then come here to ask help. People here are gentle and friendly.

1 members found this post helpful.

do you think that for three years now this post is published?
I remember that that's why I did not ask for things here, because their system is inefficient, slow, and if you add that you have to wait for someone to deign to authorize your post, you end up getting out of here,
by the way., I did not know that you're an alien bob, I've always wanted to ask you why you have a wiki that does not use https: //, honestly and without encouragement to offend you, today I no longer risk using that kind of connections ,

And to be precise and not be angry, you could tell me if you have a post here that talks about it, I've been reading these forums for 45 days and there is too much spam, nobody deigns to make a compilation of solutions or to clean up the unnecessary comments like this that I've been doing in the thread

or you could guide me to the correct readings, take into account that my level is almost intermediate but not beyond that

possible solutions to my problem
- activate the module that controls wi-fi in the kernel
- compile a new kernel with the integrated module
-
things that I already did

- read here many similar post but none deals with this subject with precision
- Google search and document collection
- review slackware completely and I only found very superficial things to the topic
- I tried to create modules with slackbuilds and install them, but I did not succeed

I do not have a cable connection to a modem, I live in a remote area, I use a cell phone as a link to the network and mobile data to navigate, my English is not good when writing, my native language is Arabic

shukraan: wifi is tricky. Alien Bob is right that this should probably be a new post in the Slackware forum, but here's some quickie info that might help.

First of all, I found that NetworkManager sucked https://www.linuxquestions.org/quest...on-4175597478/, so I disabled it:
In your /etc/rc.d/inet1.conf uncomment the following:
All the rest of the wireless settings in that file are for the older, unsecure WEP protocol.

Then create /etc/wpa_supplicant:
If this is a laptop (i.e. mobile) you can add more network{} definitions with additional passwords.

My permissions on this file are:
Note that all must be done as root and you must know how to use some text editor. Or, you can log into your desktop as root and use a text edit like Kate.

Reboot. You should be able to see the system requesting an IP address from the wireless. If there are problems, run the following as root:
and see what it says.

This has always works for me!

Good link: https://docs.slackware.com/slackbook:wifi

Posts here on LQ do not have to be authorized, all you need is a login account here and you can post whatever you want.
Both https://wiki.alienbase.nl/ and https://docs.slackware.com/ are using HTTPS by default, so I do not know what you are talking about. I do not run any other Wiki's.

If you just had created a new post all of your own, with these questions, I am certain that you would have gotten a useful response.
Your english is good by the way, better than many others.

Please contact a moderator of this forum, and ask him to remove your posts from this thread and add them to a new thread all of your own. That way, you will not have to type and post your questions again.

Actually if one google-searches "Slackware wireless", the 2nd link that comes up is https://wiki.alienbase.nl/doku.php?id=slackware:network, which gives a "Your connection is not secure" message (Firefox).

Well, do your research then and read the actual message beyond the generic "connection is not secure" message. It will tell you what you are missing.
Then read https://alien.slackbook.org/blog/add...our-slackware/ and implement what you read there.

Personally, I just accept the exception. As far as I'm concerned, it's a trusted site and accepting the exception is a lot simpler than following the procedure in your link.

I'm just saying people like shukraan aren't going to think about researching a "connection is not secure" message. No big deal.