LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Current Huge Kernel Will Not Boot With cx23885 Module (http://www.linuxquestions.org/questions/slackware-14/current-huge-kernel-will-not-boot-with-cx23885-module-727859/)

Woodsman 05-22-2009 02:49 PM

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?

Alien Bob 05-22-2009 07:17 PM

Yes. Use the generic kernel instead, as suggested in the Slackware documentation.

Eric

forum1793 05-22-2009 07:43 PM

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.

Woodsman 05-22-2009 08:17 PM

Quote:

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.

forum1793 05-23-2009 08:59 AM

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.

Woodsman 05-23-2009 12:34 PM

Quote:

And you'll feel better knowing you're helping the economy.
Ah, so you are a product of the ivory-towered pinheads and spin doctors. :D

forum1793 05-23-2009 02:37 PM

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.

Woodsman 05-29-2009 10:46 AM

Quote:

so I went with a little humor
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. :)


All times are GMT -5. The time now is 01:49 AM.