Hi... Would anyone happen to know how to enable iptables support for the 2.6.16-ck3 kernel? Firestarter won't start without it...
Printable View
Hi... Would anyone happen to know how to enable iptables support for the 2.6.16-ck3 kernel? Firestarter won't start without it...
Thats not a link to the patchset thats a link to the folder that the kernel is in before you compile it.
how do I do that?Quote:
That's weird...check if it's hidden. Also, after upgrading up to this kernel, my sound works and it never did before !
Iptables starts but firestarter doesn't reconize it. Youb don't need firestarter anyway.Quote:
Originally Posted by Thios
K well that completely drove me away from kernal compilation....
I dont know what I messed up but when I booted into the kernel it started in Failsafe. I logged in and when I went to start X it panicked. I booted my old kernel (2.6.12 ancient!) and THAT started in failsafe but X started at least. I uninstalled the package and now everything is back to normal. Think I'll wait till Dapper is released then do a fresh install of that so I have the latest kernel.
Very well, I would try and get comfortable with compiling kernels, once you compile your first one, the rest are simple. I origionally broke my system when I tried to install the 2.14.2 kernel but I got it the second time. I also tried to compile this kernel but it didn't work. I then compiled it again and it works great.Quote:
Originally Posted by R3linquish3r
It's time to start my first community :)
I have followed all steps and the Kernel is building..
If something goes wrong, what must I do to rebuild the deb package?
What must I do for "make clean"?
I have build the Kernel in the past but not on the Debian based system, and I haven't try to rebuild the same kernel.
*new to linux*
Well, things were going along smoothly until step 11. Since I downloaded the kernel and patch to my desktop, I had to put that into the path. Apparently, I must have forgotten to type in the pipe and everything after, because nothing happened. Then when I got to step 15, I got an error (but I don't know what it was, because it scrolled off the terminal). So after realizing I missed some things after the pipe, I tried re-typing it and I got launched into some program that wanted me to verify every little element of the patch (I think). This wasn't in your instructions, so I'm panicking. A snippet from the program that started up is below. If anyone can get me out of whatever hole I've dug myself into.
can't find file to patch at input line 7819
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.16-ck3/arch/x86_64/Makefile
|================================================= ==================
|--- linux-2.6.16-ck3.orig/arch/x86_64/Makefile 2006-04-02 13:04:38.000000000 +1000
|+++ linux-2.6.16-ck3/arch/x86_64/Makefile 2006-04-02 13:05:11.000000000 +1000
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 7834
Perhaps you used the wrong -p or --strip option?
etc, etc, etc....
For future reference, you can copy and paste things into Konsole or Yakuake ;)
****+ins
The new kernel works fine
The problem I have is with the motherboard
I don't know why, but it can't show the name of cards, or show other names
I have tested my tvcard on Athlon PC, and it works, but no on Intel PC the same tvcard.
I have upgraded my kernel beliving that it can recognize my motherboard
I don't know what goes wrong (and sorry if this is not the thread for that :)), but if somebody had the same problem and can help...
I have seen the names from lspci
-----------------------------------------------
0000:00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0259
0000:00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1259
0000:00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2259
0000:00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3259
0000:00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4259
0000:00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7259
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:09.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
0000:00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78 )
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown device 3118 (rev 02)
-----------------------------------------
Thanks