On Thu, Jul 19, 2007 at 10:58:13 +0100, Barry Samuels wrote: > I have two computers at home on a small network both of which are > connected to a router. Both computers are running Debian Testing. > > Computer A has two ethernet ports one of which is connected to the > router and one is connected to a network printer. Computer B sends its > printing jobs to the network printer via the router. > > Everything was working well until I upgraded the kernel on computer A > from 2.6.20.1 to 2.6.22. After that upgrade network printing from > computer B would no longer work with the message 'waiting for <IP > address> to come up'. The odd thing is that I could ping the ethernet > port on computer A to which the printer is connect but not the printer > itself. > > Reverting to kernel 2.20.1 on computer A cured the printing problem but > means that the sensors temperatures that have worked properly for the > first time with 2.6.22 now cannot be displayed (bother!). > > That seems to mean either a bug in kernel 2.6.22 or a new setting that > I have not set. I did copy my 2.6.20.1 config to 2.6.22 and did a make > oldconfig. > > Any comments, suggestions or revalations please?
Maybe there was a network-related change in some kernel configuration options and "make oldconfig" did not take that into account properly. For example, a missing netfilter module might make your firewall on Computer A unduly restrictive. Do you see any network or firewall related error messages in dmesg? I would simply try a stock Debian 2.6.22 kernel image (available in Sid); if that works then you know the problem is the configuration of your custom kernel. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
