Bug#363490: marked as done (module sk98lin cannot be assigned to eth0)
Your message dated Fri, 28 Apr 2006 23:12:45 +0200
with message-id <200604282312.46117.aragorn@tiscali.nl>
and subject line Bug#363490: module sk98lin cannot be assigned to eth0
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: installation-reports
Boot method: CD
Image version: 06-04-17
from //cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 06-04-19 13:20CET
Machine: Self made tower pc
Processor: Intel(R) EM64T Pentium(R) 4 CPU 3.20GHz
Memory: 1 GB DDR RAM
Partitions:
Filesystem 1k-blocks Used Available Use% Mounted on
tmpfs 102400 30404 71996 30% /
tmpfs 512844 444 512400 0% /dev
tmpfs 512844 444 512400 0% /dev
tmpfs 512844 444 512400 0% /.dev
/dev/cdroms/cdrom0 97938 97938 0 100% /cdrom
/dev/sda3 76896348 11664016 61326128 16% /mnt
Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Processor to
I/O Controller (rev 04)
0000:00:01.0 PCI bridge: Intel Corporation 915G/P/GV/GL/PL/910GL PCI Express
Root Port (rev 04)
0000:00:1b.0 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High
Definition Audio Controller (rev 03)
0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
PCI Express Port 1 (rev 03)
0000:00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
PCI Express Port 2 (rev 03)
0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 03)
0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 03)
0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
0000:00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC
Interface Bridge (rev 03)
0000:00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) IDE Controller (rev 03)
0000:00:1f.2 IDE interface: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA
Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
SMBus Controller (rev 03)
0000:01:04.0 Mass storage controller: Integrated Technology Express, Inc.
IT/ITE8212 Dual channel ATA RAID controller (PCI version seems to be IT8212,
embedded seems (rev 13)
0000:01:0a.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless
Interface
0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053
Gigabit Ethernet Controller (rev 19)
0000:04:00.0 VGA compatible controller: ATI Technologies Inc R423 UK [Radeon
X800SE (PCIE)]
0000:04:00.1 Display controller: ATI Technologies Inc Radeon R423 UK (PCIE)
[X800 SE] (Secondary)
0000:00:00.0 0600: 8086:2580 (rev 04)
0000:00:01.0 0604: 8086:2581 (rev 04)
0000:00:1b.0 0403: 8086:2668 (rev 03)
0000:00:1c.0 0604: 8086:2660 (rev 03)
0000:00:1c.1 0604: 8086:2662 (rev 03)
0000:00:1d.0 0c03: 8086:2658 (rev 03)
0000:00:1d.1 0c03: 8086:2659 (rev 03)
0000:00:1d.2 0c03: 8086:265a (rev 03)
0000:00:1d.3 0c03: 8086:265b (rev 03)
0000:00:1d.7 0c03: 8086:265c (rev 03)
0000:00:1e.0 0604: 8086:244e (rev d3)
0000:00:1f.0 0601: 8086:2640 (rev 03)
0000:00:1f.1 0101: 8086:266f (rev 03)
0000:00:1f.2 0101: 8086:2652 (rev 03)
0000:00:1f.3 0c05: 8086:266a (rev 03)
0000:01:04.0 0180: 1283:8212 (rev 13)
0000:01:0a.0 0280: 104c:9066
0000:02:00.0 0200: 11ab:4362 (rev 19)
0000:04:00.0 0300: 1002:554b
0000:04:00.1 0380: 1002:556b
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [E]
Config network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
The module sk98lin needed by the network HW was not loaded automatically.
Choosing it from the list that showed after the automatic loading failure had
no effect.
Changing to the VT2, inserting ist manally by "modprobe sk98lin" and
inspecting the list put out by lsmod showed that ist was loaded.
But in /proc/net/sk98lin/ there was not the expected Document "eth0" - there
was nothing at all.
I guess that the driver module could not be assigned correctly to the lan
interface.
As I found out trying to install the i386 daily-build-image (loaded down on
April 17 at 10:11pm), there is a working sk98lin module loading
automatically.
Perhaps it is worth while taking its source code and compiling it in an amd64
environment?
Greetings,
Georg
--- End Message ---
--- Begin Message ---
On Sunday 23 April 2006 11:59, Georg Colle wrote:
> {1} cat /proc/version (i386; sk98lin working)
> {2} cat /proc/version (i386 after installation & reboot; sk98lin no
> longer working)
> {3} cat /proc/version (amd64; sk98lin not working)
OK, so it looks as if you really need a 2.6.16 kernel for the driver to
work. Unfortunately, we are slowly moving from 2.6.15 to 2.6.16 ATM.
2.6.16 is not yet in testing, which explains the problem after the reboot,
but you should be able to install the 2.6.16 kernel from unstable without
problems.
Partly because of the archive integration for amd64, it does not yet have
the 2.6.16 for the installer, so I'm afraid a bit of patience is required
for that.
I'm closing your report as it seems we've identified the issue and it is
solved with 2.6.16 kernels. You can still reply to this message though.
Cheers,
FJP
--- End Message ---
Reply to: