oops soz, I missed out the last code LOL. Sorry for that
oops soz, I missed out the last code LOL. Sorry for that
just in case you missed my edit's
here are my updated facts
compile went fine (several times)
i have no internet-connection, only "ping" works
i changed nothing in the .config,
i don't use NDIS with 2.6.17.11 (lsmod | grep ndis >results in "")
i tried:
to compile ndiswrapper from source #29 went fine but won't help
to delete everything like maciu did above #117 except my eth0 entries which didn't help
any advice for me ?
I've compiled the kernel but how do I reinstall the nvidia drivers if I already tried to boot into the new kernel and it failed..... so now I rebooted so How do I reinstall the nvidia drivers for the new kernel?
juve, disable Firestarter if you have it? Or any kind of Firewall?
I've tried a few times and with different kernels but I just can't make the module package! The last message looks like this:
I can't seem to find any error message here. To me it's just a damn script, any ideas?Code:dpkg-deb: bygger paketet "linux-headers-2.6.20-ck1" i "../linux-headers-2.6.20-ck1_2.6.20-ck1-10.00.Custom_i386.deb". tar: -: file name read contains nul character cp -pf debian/control.dist debian/control make[1]: Leaving directory `/usr/src/linux-2.6.20' ====== making target stamp-kernel-headers [new prereqs: linux-headers-2.6.20-ck1 linux-headers-2.6.20-ck1]====== This is kernel package version 10.049ubuntu5. echo done > stamp-kernel-headers ====== making target kernel_headers [new prereqs: stamp-configure stamp-prepare stamp-kernel-headers]====== This is kernel package version 10.049ubuntu5. for module in ; do \ if test -d $module; then \ (cd $module; \ if ./debian/rules KVERS="2.6.20-ck1" KSRC="/usr/src/linux-2.6.20" \ KMAINT="Unknown Kernel Package Maintainer" KEMAIL="unknown@unconfigured.in.etc.kernel-pkg.conf" \ KPKG_DEST_DIR="/usr/src/linux-2.6.20/.." \ KPKG_MAINTAINER="Unknown Kernel Package Maintainer" \ KPKG_EXTRAV_ARG="" \ ARCH="i386" \ KDREV="2.6.20-ck1-10.00.Custom" kdist_image; then \ echo "Module $module processed fine"; \ else \ echo "Module $module failed."; \ if [ "X" != "X" ]; then \ echo "Perhaps $module does not understand --rootcmd?"; \ echo "If you see messages that indicate that it is not"; \ echo "in fact being built as root, please file a bug "; \ echo "against $module."; \ fi; \ echo "Hit return to Continue"; \ read ans; \ fi; \ ); \ else \ echo "Module $module does not exist"; \ echo "Hit return to Continue?"; \ fi; \ done
I'm looking forward to basically using this new kernel in conjunction with MythTV myself, so I have to make sure I'm doing this right. I'm using Edgy Eft, for right now. I understand that MythTV usually DOES require the latest kernel in order to do anything. According to this link: http://ubuntuforums.org/showthread.php?t=333523 from what I see, this is what I should be doing. However, if the newest kernel can't be booted successfully, then what good is this to use the TV Tuner that I got here? I'm somewhat considering my options more than carefully, but it's just too much of a pain in the butt to even, I mean... wow...
Now that I'm thinking about it, could the upcoming Feisty Fawn distro have this new kernel built into the new version and ready to go for MythTV right out of the box using the newest kernel?
Last edited by Robert A. Morin; February 20th, 2007 at 12:37 AM. Reason: About upcoming Feisty Fawn distribution...
Envy can't install on new custom kernel unless modules are built in to the kernel, the problem is that with plain vanilla kernel, the make modules keep failing with riva fb sanity check error.
Bookmarks