pcnet32-based HomePNA card loaded incorrectly in d-i

[Ilkka Tuohela]

A HomePNA card is recognized as such by debian installer, when it asks for
network device to configure (says HomePNA in the end of line),
but the driver, pcnet32, is not loaded with driver parameter homepna=1 and the
card really does not work as expected.

Of course this driver is for ethernet cards as well, so option homepna=1 can't
be made default value either. If it's possible to add a question about the
driver's mode when it is selected, and then reload the driver with correct
option, this would be the perfect solution: because d-i already recognized the
type as HomePNA it could even default to this driver option.

Solved this personally by not configuring network and running following commands
after install:
echo 'options pcnet32 homepna=1' > /etc/modprobe.d/pcnet32
echo 'iface eth0 inet dhcp' > /etc/network/interfaces && rmmod pcnet32 &&
modprobe pcnet32

Sorry, can't probably further test this, this happened when installing a
friend's system quite far away, I don't have any homepna cards
or networks available myself.

[Jouni Mettala (jouni-mettala)]

Using expert installation, after Detect the network hardware cards link light
goes off. Trying execute a shell and modprobe -rv pcnet32 and modprobe pcnet32
homepna=1. Link light goes on again. Then network is configured correctly after
configure network. This works also with live-cd.

[Colin Watson (cjwatson)]

I haven't checked if this has since been fixed in the kernel, but if it hasn't, IMO the fix really belongs there.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks, Markus

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.