CONFIG_PACKET should be "y" on lpia; breaks DHCP in alternate installer?

[Colin Watson]

I haven't reproduced this myself, and this is not on my machine (so this bug is intentionally not reported using ubuntu-bug), but in https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/347122/comments/7 I happened to notice this:

Mar 30 15:05:12 dhclient: socket: Address family not supported by protocol - make sure
Mar 30 15:05:12 dhclient: CONFIG_PACKET (Packet socket) and CONFIG_FILTER
Mar 30 15:05:12 dhclient: (Socket Filtering) are enabled in your kernel
Mar 30 15:05:12 dhclient: configuration!

CONFIG_FILTER doesn't exist any more as far as I can see, but CONFIG_PACKET does. On all other architectures, we set CONFIG_PACKET=y; on lpia, we set CONFIG_PACKET=m, and don't deliver the resulting module in any udeb so that debian-installer can make use of it. Although I don't have direct proof, I suspect this breaks the ability to use DHCP in the alternate installer.

I think we should set CONFIG_PACKET=y on lpia too, for consistency if nothing else.

[Loïc Minier (lool)]

I can confirm that I was lacking network in a recent alternate lpia install, but got network in the installed system -- I thought the network modules used ford KVM had been ommitted.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 2.6.28-11.42

---------------
linux (2.6.28-11.42) jaunty; urgency=low

  [ Tim Gardner ]

  * Enabled LPIA CONFIG_PACKET=y
    - LP: #362071

  [ Upstream Kernel Changes ]

  * ext4: fix bb_prealloc_list corruption due to wrong group locking
    - LP: #348836

 -- Stefan Bader <email address hidden> Thu, 16 Apr 2009 08:10:55 +0200