Installation propose to configure FireWire Ethernet while there is no FireWire controller present

Bug #25033 reported by Etienne Goyer
6
Affects Status Importance Assigned to Milestone
hw-detect (Ubuntu)
Fix Released
Medium
Colin Watson

Bug Description

On a Toshiba Tecra 8000, a rather old laptop (Pentium II 233), the Ubuntu
installer propose to configure a FireWire Ethernet device after scanning for
network device. It claim that no network interface where found (which is
correct, this laptop does not have built-in Ethernet), but that a FireWire
controller was and that it is possible to configure it for FireWire Ethernet. I
am sorry that I can't give the exact text of the dialog, but I (obviously) could
not paste it from the installer.

Checking with lsmod and dmesg, I can't find any reference to a FireWire
controller. Which is correct, there is none anyway.

This is not a serious bug as it does not stop the installer from completing its
task. But I guess it could be confusing to the uninitiated.

Revision history for this message
Evan Clarke (evanclarke) wrote :
Download full text (10.1 KiB)

I too have observed this bug on my desktop machine. Output of lspci -vv is:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 81)
        Subsystem: Asustek Computer, Inc.: Unknown device 8041
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
        Latency: 40
        Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [a0] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans-
64bit- FW- AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
(prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR+
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: eb000000-ebefffff
        Prefetchable memory behind bridge: eff00000-f7ffffff
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
        Subsystem: Asustek Computer, Inc.: Unknown device 80e7
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a
[Master SecP PriP])
        Subsystem: Asustek Computer, Inc.: Unknown device 80e7
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Region 4: I/O ports at d800 [size=16]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16) (prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Control...

Revision history for this message
Colin Watson (cjwatson) wrote :

Yes, it looks like ethdetect wrongly asks this question if there are no network
interfaces present. Should be an easy fix, given time (and a suitably hacked-up
setup) for testing.

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

I just wanted to add to I still experience this bug, on the same machine, using the Dapper alternate (text-based) installation CD.

Revision history for this message
Colin Watson (cjwatson) wrote :

I've merged the following change from Debian into Edgy, fixing this bug:

hw-detect (1.39) unstable; urgency=low

  [ Frans Pop ]
  * Only ask FireWire question if a FireWire interface is actually present.

  [ Colin Watson ]
  * Fix disk_found to return 1 (no disks found) if it falls off the end of
    its loop.
  * If /proc/sys/kernel/hotplug is empty or /sbin/udevsend, then
    HOTPLUG_TYPE is always udev even if /etc/hotplug is present (closes:
    https://launchpad.net/bugs/53400).

  [ Otavio Salvador ]
  * Install pbbuttonsd if /sys/class/misc/pmu/ is found. Closes: #379197

  [ Updated translations ]
  * Estonian (et.po) by Siim Põder
  * Gujarati (gu.po) by Kartik Mistry
  * Hungarian (hu.po) by SZERVÁC Attila
  * Dutch (nl.po) by Bart Cornelis
  * Panjabi (pa.po) by A S Alam

 -- Frans Pop <email address hidden> Tue, 25 Jul 2006 13:04:38 +0200

Changed in hw-detect:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.