DebianThis forum is for the discussion of Debian 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'm running Debian/Testing on my HP Pavilion laptop and I've recently compiled a new kernel (2.6.8), but after that I noticed DHCPDISCOVER kept failing at boot time. After looking about and messing with all sorts of stuff, I believe I've narrowed it down; apparentely, it's not listening correctly for DHCP offers. Upon boot time it says it's listening and sending on LPF/eth0/<null>, instead of the correct address (which would be, I believe, the router's address, 192.168.1.1). The ethernet card is configured and working, but I have no idea how to set up DHCP decently =/
eth0 is my LAN card, eth1 my wireless card, lo and sit0 I have no idea >_>
As for the problematic kernel:
eth0 Link encap:UNSPEC HWaddr 3C-3F-02-00-38-0E-00-3D-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:112 errors:0 dropped:0 overruns:0 frame:0
TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:7340 (7.1 KiB) TX bytes:7340 (7.1 KiB)
This opens up a whole new world of possibilities o_O no sit0, to start, and eth0 is suddenly my wireless card. My Ethernet card is nowhere to be seen, which is definitely a problem. ifconfig eth1 up (assuming here that the two cards simply switched places) outputs
eth1: ERROR while getting interface flags: No such device
meaning the damned thing has no idea my Ethernet card exists.
There's a whole another issue at work here too; if eth0, in the new kernel, is my wireless card, it's not supposed to be working, as I haven't set up ndiswrapper or anything similar (and to the best of my knowledge Debian/Testing doesn't handle Broadcom WLAN cards all by its lonesome <_<); but if my any chance it is working, why isn't it getting dhcp offers from my wireless router (which I'm sure is working, at least with Windows :P)?
Anyway, why doesn't it detect my Ethernet card? How can I get it to?
Thanks for any help
: Oh, and David, I'm not entirely sure how to check whether DHCP is firewalled or not. How would I do that? Thanks
Ensure your ethernet driver is compile in your kernel.
If you want to start with clean config, you can try the suggestion below (try it at your own risk);
-you can backup config files from /boot (e.g. /boot/config-* )
-you can rename those config file with temporary names (e.g. add suffix .bak)
-you can rename /usr/src/linux/.config to a new name (e.g. add suffix .bak)
-you can rerun "make xconfig" or equivalent to regenerate /usr/src/linux/.config.
make xconfig usually try to build the /usr/src/linux/.config by looking at existing config file from /boot.The /usr/src/linux/.config contains instruction on how to build the kernel.
-alternatively, you can try leave a good config file in /boot so that "make xconfig" will try to use it as a default config and then you could tweak other parameters that you want.
forgox, I followed this page's instructions on how to compile the kernel seeing as the guy's laptop is so similar to mine and he's using the same distro. Everything went pretty much like he says on the page, except for not finding the 2.6.10 source (stuck with 2.6.8; I suspect it is so because he added unstable entries to his apt-get list). I even tried using his .conf file, but no >_< anyway, my point is that I never saw any compiler flags anywhere, so...
At any rate, that was one error I corrected - the first time I compiled the kernel, I included the wrong drivers for my card, but I think I've got them correctly now. I could check though...