Re: Kernel Upgrade Problems - IBM T23
You were. In this context, a fully-configured kernel source tree means one for which "make config|menuconfig|xconfig" and "make dep" have been run. > installation of my wireless Cisco Aironet card which claimed I needed to > have a working kernel source tree, I assumed this meant I needed to have > compiled my kernel from the source, but my assumptions have been wrong > so far so it wouldn't surprise me if I was wrong once again.
Re: Kernel Upgrade Problems - IBM T23
You were. In this context, a fully-configured kernel source tree means one for which "make config|menuconfig|xconfig" and "make dep" have been run. > installation of my wireless Cisco Aironet card which claimed I needed to > have a working kernel source tree, I assumed this meant I needed to have > compiled my kernel from the source, but my assumptions have been wrong > so far so it wouldn't surprise me if I was wrong once again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Kernel Upgrade Problems - IBM T23
DHCP issues were resolved w/ CONFIG_FILTER=y, too bad I had to recompile the kernel to get this to work. The initial issue that spurred me to rebuild the kernel was the installation of my wireless Cisco Aironet card which claimed I needed to have a working kernel source tree, I assumed this meant I needed to have compiled my kernel from the source, but my assumptions have been wrong so far so it wouldn't surprise me if I was wrong once again. Beyond that, I need to support a Sony DSC-S50 digital camera which uses the memory stick, haven't found much in regards to drivers/support for this, anyone have experience with this? Additionally, how can I determine if it simply uses the USB Mass Storage or whatever type method, which I assume would allow greater compatibility w/ linux flavors. If all this can be done w/o rebuilding the kernel then I may fall back to a kernel image, I just wanted to get some knowledge of the process but I'd have more faith in a pre-built image. Thanks for your help Zane, anyone else have any comments? Thanks, Zach -Original Message- From: Zane Dodson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 17, 2002 12:21 AM To: Zach Bower Subject: Re: Kernel Upgrade Problems - IBM T23 On Sun, Sep 15, 2002 at 07:13:50PM -0400, Zach Bower wrote: | So I had sometime to finish the re-install of Debian, went fine w/ the | ide-pci disks. | | Just went through the kernel rebuild process for 2.4.18 and I'm | experiencing the same issues. | | CONFIG_PACKET=y is set | | but | | CONFIG_FILTER=n so this is incorrect. | | I just did a make oldconfig this time because I knew the config that | was used to build the kernel w/ the minimal install seemed to work | fine, but obviously that's not it. The interface is up, but still not | DHCPing an addres. Also check your system log for messages. If you are using dhclient from the dhcp-client package, there should be an error logged in your system log if there was a problem opening the socket. | | Can I set CONFIG_FILTER=y w/o rebuilding again and additionally are | there any other parameteres I should set under CONFIG_PACKET=y some of | the others are not set. No, you'll need to rebuild again after setting CONFIG_FILTER=y. Others depend on your exact hardware, module preferences, etc. Unless you have specific needs which require that you build a custom kernel, you'll probably find the prebuilt Debian kernels much easier to work with. I'd recommend you use one of those instead of building your own, if possible. | Let me know when you get a chance, thanks a lot. Please post to the mailing list rather than reply to me personally. Best regards, -- Zane Dodson [EMAIL PROTECTED] | | Zach | | -Original Message- | From: Zane Dodson [mailto:[EMAIL PROTECTED] | Sent: Friday, September 13, 2002 12:49 AM | To: Zach Bower | Cc: [email protected] | Subject: Re: Kernel Upgrade Problems - IBM T23 | | | On Fri, Sep 13, 2002 at 12:18:23AM -0400, Zach Bower wrote: | | It is the built-in Ethernet interface, I believe Intel EtherPro 100 | | or | | | some variation. Seems to DHCP fine based off the initial ide-pci | | minimal install. | | | | Which specific config files should I copy when I upgrade my kernel | | to | | 2.4.8 and I assume I'll have to recompile the module for 2.4.8 as | | well? | | | | I did try to configure it in interfaces but it seems to not want to | | dhcp an address so I thought I was missing something. | | | When compiling your own kernel, make sure to set | CONFIG_PACKET=y | CONFIG_FILTER=y | in your kernel's .config. This enables a raw socket that a dhcp | client needs to open. | | See | socket (2) (PF_PACK and SOCK_PACK) | packet (7) | | See also /usr/share/doc/dhcp-client/README.gz, section 5.1.2 - | PROTOCOL NOT CONFIGURED. | | I think that will get your DHCP working. | | Best regards, | | -- | Zane Dodson | [EMAIL PROTECTED]
Re: Kernel Upgrade Problems - IBM T23
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 12 September 2002 09:49 pm, Zane Dodson wrote: > On Fri, Sep 13, 2002 at 12:18:23AM -0400, Zach Bower wrote: > > > | It is the built-in Ethernet interface, I believe Intel EtherPro 100 or > | some variation. Seems to DHCP fine based off the initial ide-pci > | minimal install. > | > | Which specific config files should I copy when I upgrade my kernel to > | 2.4.8 and I assume I'll have to recompile the module for 2.4.8 as well? > | > | I did try to configure it in interfaces but it seems to not want to dhcp > | an address so I thought I was missing something. > > > > When compiling your own kernel, make sure to set > CONFIG_PACKET=y > CONFIG_FILTER=y > in your kernel's .config. This enables a raw socket that a dhcp > client needs to open. > > See > socket (2) (PF_PACK and SOCK_PACK) > packet (7) > > See also /usr/share/doc/dhcp-client/README.gz, section 5.1.2 - PROTOCOL > NOT CONFIGURED. > > I think that will get your DHCP working. > > Best regards, Greetings Zach: Please let us (debian-laptop) know if this latter reply solved the dhcp problem for you since I am interested in the outcome. I had a similar experience with a new Woody install on a desktop using DHCP. I have never solved the failure but did manage to get it fully functional in a more manual way. The problem was that I initially used a static IP during install. Later, I installed 'dhcpd' on my gateway and changed the desktop box to dhcp but it would never get an ip. It had dhcp-client installed, yet it would only work if I manually invoked it. Finally I installed pump and removed dhcp-client and it would work during boot (as I wanted it too). Tnx Zach. gl tatah - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9gm3XZHBxKsta6kMRAjOFAJ4/qGTcBdsRoUn0hSBC2VnE6M7BJwCfSgG8 lZZIXcWp8D44kmbvXmHR1g8= =f67Q -END PGP SIGNATURE-
Re: Kernel Upgrade Problems - IBM T23
On Fri, Sep 13, 2002 at 12:18:23AM -0400, Zach Bower wrote: | It is the built-in Ethernet interface, I believe Intel EtherPro 100 or | some variation. Seems to DHCP fine based off the initial ide-pci | minimal install. | | Which specific config files should I copy when I upgrade my kernel to | 2.4.8 and I assume I'll have to recompile the module for 2.4.8 as well? | | I did try to configure it in interfaces but it seems to not want to dhcp | an address so I thought I was missing something. When compiling your own kernel, make sure to set CONFIG_PACKET=y CONFIG_FILTER=y in your kernel's .config. This enables a raw socket that a dhcp client needs to open. See socket (2) (PF_PACK and SOCK_PACK) packet (7) See also /usr/share/doc/dhcp-client/README.gz, section 5.1.2 - PROTOCOL NOT CONFIGURED. I think that will get your DHCP working. Best regards, -- Zane Dodson [EMAIL PROTECTED]
RE: Kernel Upgrade Problems - IBM T23
Zane It is the built-in Ethernet interface, I believe Intel EtherPro 100 or some variation. Seems to DHCP fine based off the initial ide-pci minimal install. Which specific config files should I copy when I upgrade my kernel to 2.4.8 and I assume I'll have to recompile the module for 2.4.8 as well? I did try to configure it in interfaces but it seems to not want to dhcp an address so I thought I was missing something. Sorry for the newbie questions, I'm actually pretty good when it comes to routing/switching if you ever need any help there... :) Zach -Original Message- From: Zane Dodson [mailto:[EMAIL PROTECTED] Sent: Friday, September 13, 2002 12:08 AM To: Zach Bower Cc: [email protected] Subject: Re: Kernel Upgrade Problems - IBM T23 On Thu, Sep 12, 2002 at 11:56:14PM -0400, Zach Bower wrote: | I'm not sure if I'm missing something during the make config ( or | actually, I used make xconfig), but it seems as though everything | compiles fine and I specified to load the network drivers as modules | but upon reboot, I can't manage to get my eth0 interface to DHCP an | address. When I configure an IP address on it manually, I can ping | local devices so obviously there must be more configuration I need to | do when manually specifying an IP. My question is, why am I unable to | use DHCP? Do I need pump or something like that? I thought dhcpd | would take care of it. Is eth0 builtin? If so, you can configure it for DHCP via /etc/network/interfaces. See the man page on interfaces(5): % man interfaces If eth0 is a PC card, then you can specify to use DHCP when the card is configured by setting DHCP="y" in /etc/pcmcia/network.opts. Hope that helps. Best regards, -- Zane Dodson [EMAIL PROTECTED]
Re: Kernel Upgrade Problems - IBM T23
On Thu, Sep 12, 2002 at 11:56:14PM -0400, Zach Bower wrote: | I'm not sure if I'm missing something during the make config ( or | actually, I used make xconfig), but it seems as though everything | compiles fine and I specified to load the network drivers as modules but | upon reboot, I can't manage to get my eth0 interface to DHCP an address. | When I configure an IP address on it manually, I can ping local devices | so obviously there must be more configuration I need to do when manually | specifying an IP. My question is, why am I unable to use DHCP? Do I | need pump or something like that? I thought dhcpd would take care of | it. Is eth0 builtin? If so, you can configure it for DHCP via /etc/network/interfaces. See the man page on interfaces(5): % man interfaces If eth0 is a PC card, then you can specify to use DHCP when the card is configured by setting DHCP="y" in /etc/pcmcia/network.opts. Hope that helps. Best regards, -- Zane Dodson [EMAIL PROTECTED]
