Current Huge Kernel Will Not Boot With cx23885 Module
SlackwareThis Forum is for the discussion of Slackware 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.
Current Huge Kernel Will Not Boot With cx23885 Module
When I updated to 12.2 from 12.1, I could not boot with the huge kernel. Same thing happens when trying to boot Current with the 2.6.29.2 kernel. As I reported previously, the solution once again seems to be the same: blacklist the cx23885 driver in /etc/modprobe.d/blacklist. The driver supports my HVR-1250 TV capture card.
With 12.2 I solved the problem by recompiling the kernel to load the cx23885 driver as a module. Looks like eventually I'll have to do the same with 2.6.29.2.
I wish I knew why this happens. Anybody have some ideas?
What do you mean by can't boot? Does it hang? Give panic? Or just not see the tv card?
I have a Haup 1600 and the huge kernel from current boots OK. I may have still had to add the firmware for the 1600 to work. The generic works fine. I've since did custom for 2.6.29.3 and all is working fairly well.
Yes. Use the generic kernel instead, as suggested in the Slackware documentation.
Well, no, that is not what I meant. After I update 12.2 to Current, and then reboot, the only kernel available at that moment is the huge kernel. Sure, I always eventually compile my own kernel, but for a handful of reboots the huge kernel is being used. I'm just curious why the huge kernel freezes and a recompiled kernel that loads the driver as a module does not. My guess is that something in the udev loading order causes this. Blacklisting the driver allows the huge kernel to boot.
Quote:
What do you mean by can't boot? Does it hang? Give panic? Or just not see the tv card?
Freeze. Hard. Always when the udev script is being run.
Very puzzling. Sure, you have figured a good work around, but, I would use this situation as an excuse for buying new hardware. And you'll feel better knowing you're helping the economy.
I felt I needed to respond since I posted a question but I didn't have any good answer other than the obvious, "it's the kernel, it's your hardware, or bios settings" so I went with a little humor. But seriously, have you seen the prices for hardware? Graphics cards? Memory? It's incredible. To think I blew $2500+ ten years ago but can now replace that for around $500. Amazing.
And I responded in manner, hence the big smiley. Sure, new hardware might resolve the issue, but an additional card sucks more electricity and adds more heat to the case. I like integrated components for my type of usage.
I know how to work around the problem, but the problem should not exist. A driver should not freeze the boot process.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.