SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had no problem in slack-11 with stock 2.6 kernel off install disk nor with an install of current 2-3 months ago but I just installed 12-rc1 to see what I'll need to do on the home lan and...
It seems that while my dvb-t card is recognised and correct modules are being loaded at boot, there is no /dev/dvb/adapter0 and devices therein being created.
As it was not necessary to do anything in /etc/udev in slack-11 or the last current install, I am a bit puzzeled. I had a look around on google last night but I'm not really sure what I should be looking for.
The udev rules look the same from 11 to rc1. Im booting with vmlinuz -> vmlinuz-huge-smp-188.8.131.52-smp
Has anyone had a dvb card recognised with /dev/dvb etc. being created in rc-1?
I still have not figured out what the difference is with 184.108.40.206 and why the devices are not created. It appears udev does the job with the previous kernels on the same box.
Dumb question, but have you tried compiling a custom 220.127.116.11 kernel?
According to the documentation, the "huge" kernels are not intended for every day use. They're more for emergency situations. It is possible that they don't have the support necessary for your DVB card compiled in by default.
The huge smp from current in April (18.104.22.168) worked OK when recompiled in both slack-11 and rc-1.
I compiled 7 or 8 kernels this weekend and checked to make sure all dvb IMHO options were correct each time
Probably have to compare the configs against each other next. I could also just keep compiling kernel versions up from 22.214.171.124 until I find the next one that don't work and see what changed at that point. Seems silly though.
Fallback would be to just compile and use 126.96.36.199 when Slack-12.0 is released though it's nice to just have things work out of the box.
You asked about anyone having got the right dev parts with a dvb-t device in 12RC1 (or now RC2): Yes, without any problem. Only thing I had to do (like before, like with any distro) was to copy the firmware to /lib/firmware, then it was picked up like it should.
I tested it with kaffeine and it worked nicely.
I forgot: kernel is vmlinuz-huge-smp-188.8.131.52-smp, the same you started with. I didn't recompile it until now.
Last edited by titopoquito; 07-02-2007 at 05:37 AM.
Thanks for the input but I am a bit confused after reading your post
I have never needed to do anything with firmware. I have a dvico fusion hdtv dvb-t on this box and a winfast dtv1000 T dvb-t card on another box. Both running slack-11 and I didn't do anything to get the devices created. Udev rules/scripts do that. Both use a Conexant CX23880 chip.
In slack-10.1 I had to fiddle with compiling modules with 2.4.X kernels and with udev when I started using 2.6. kernels but I did not have to do anything special in slack-11 or in the current I downloaded in April with a 184.108.40.206 kernel.
Why do I now need to install firmware and where do I find this firmware that I never had to use before?
I have sorted this problem out on a new slack-12 install.
After booting a fresh install with the default huge kernel and the generic not huge kernel without having my devices recognised as dvb at boot and later by udev, I installed v4l-dvb from http://www.linuxtv.org/repo/ and compiled and installed it.
This has remdied the problem, dmesg indicates recognition as a dvb device, /proc/devices has a DVB 212 entry, and udev creates the requisit devices.
I still have not figured out why I have to compile and install modules on 220.127.116.11 that were already compiled with that kernel and which worked perfectly on the 18.104.22.168 and 2.6 18.8 slack kernels off the shelf.
.... but in any case, above is how I resolved the problem and I thought I'd best put it here as google was already serving up this thread when I looked for a solution.
Last edited by justwantin; 07-05-2007 at 03:16 PM.