Bug#360681: marked as done (kernel: NIC: Unknow symbol mii_*)
Your message dated Tue, 04 Apr 2006 22:37:12 +0200
with message-id <200604042237.13328.aragorn@tiscali.nl>
and subject line kernel: NIC: Unknow symbol mii_*
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.16-1-486
Tags: d-i
Hello,
On a computer where d-i works fine with 2.6.15, it doesn't work with 2.6.16.
The NIC module is not loaded.
Debian-Installer syslog says:
Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_ethtool_sset
Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_link_ok
Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_check_link
Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_nway_restart
Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_ethtool_gset
Apr 4 02:32:12 kernel: e100: Unknown symbol mii_ethtool_sset
Apr 4 02:32:12 kernel: e100: Unknown symbol mii_link_ok
Apr 4 02:32:12 kernel: e100: Unknown symbol mii_check_link
Apr 4 02:32:12 kernel: e100: Unknown symbol mii_nway_restart
Apr 4 02:32:12 kernel: e100: Unknown symbol generic_mii_ioctl
Apr 4 02:32:12 kernel: e100: Unknown symbol mii_ethtool_gset
Doing a manual `modprobe e100` in d-i syslog says:
Apr 4 02:34:06 kernel: e100: Unknown symbol mii_ethtool_sset
Apr 4 02:34:06 kernel: e100: Unknown symbol mii_link_ok
Apr 4 02:34:06 kernel: e100: Unknown symbol mii_check_link
Apr 4 02:34:06 kernel: e100: Unknown symbol mii_nway_restart
Apr 4 02:34:06 kernel: e100: Unknown symbol generic_mii_ioctl
Apr 4 02:34:06 kernel: e100: Unknown symbol mii_ethtool_gset
Cheers
Geert Stappers
--- End Message ---
--- Begin Message ---
On Tuesday 04 April 2006 21:49, Geert Stappers wrote:
> Most likely a hick-up in the build system (the error occures on a
> home made image).
Let's close the BR then.
--- End Message ---
Reply to: