ieee1394 port not recognized

Bug #329277 reported by darkblue_b
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Jaunty a4 on an Acer ASE 380-UD440A
64bit AMD 4400+ Brisbane CPU

also, all the hardware ports are listed in Gnome Desktop
(I dont know if that is expected or not)

see attachments

ProblemType: Bug
Architecture: amd64
Date: Fri Feb 13 17:54:20 2009
Dependencies:

DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta
Uname: Linux 2.6.24-23-generic x86_64

Revision history for this message
darkblue_b (maplabs) wrote :
Revision history for this message
Stefan Richter (stefan-r-ubz) wrote :

How does "lspci -v" show the controller? The PCI IDs look like from the Texas Instruments TSB43AB** family.

The messages
        ohci1394: fw-host0: Get PHY Reg timeout [0x00000000/0x00000000/100]
indicate that the drivers were unable to perform the last steps of initialization. For now I don't know why.

What if you load the new alternative drivers instead of the old ones? According to your lspci, the new ones are installed in parallel already. The new drivers were quite buggy in kernel 2.6.24 though.
# modprobe -r ohci1394
# modprobe firewire-ohci

Revision history for this message
darkblue_b (maplabs) wrote : Re: [Bug 329277] Re: ieee1394 port not recognized

Hi Stefan-

thank you for your attention on this.. I am not sure what your
conclusion is...
I would very much like this to be addressed for Jaunty.. new release
this week, yes?
I can do any reasonable set of tests, if you specify
please make sure this is in the official bug queue

thanks
   -Brian

On Feb 19, 2009, at 1:37 PM, Stefan Richter wrote:

> How does "lspci -v" show the controller? The PCI IDs look like from
> the
> Texas Instruments TSB43AB** family.
>
> The messages
> ohci1394: fw-host0: Get PHY Reg timeout
> [0x00000000/0x00000000/100]
> indicate that the drivers were unable to perform the last steps of
> initialization. For now I don't know why.
>
> What if you load the new alternative drivers instead of the old ones?
> According to your lspci, the new ones are installed in parallel
> already. The new drivers were quite buggy in kernel 2.6.24 though.
> # modprobe -r ohci1394
> # modprobe firewire-ohci
>
> --
> ieee1394 port not recognized
> https://bugs.launchpad.net/bugs/329277
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux-meta” source package in Ubuntu: New
>
> Bug description:
> Jaunty a4 on an Acer ASE 380-UD440A
> 64bit AMD 4400+ Brisbane CPU
>
> also, all the hardware ports are listed in Gnome Desktop
> (I dont know if that is expected or not)
>
> see attachments
>
> ProblemType: Bug
> Architecture: amd64
> Date: Fri Feb 13 17:54:20 2009
> Dependencies:
>
> DistroRelease: Ubuntu 8.04
> NonfreeKernelModules: nvidia
> Package: linux None [modified: /var/lib/dpkg/info/linux.list]
> PackageArchitecture: amd64
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/
> usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: linux-meta
> Uname: Linux 2.6.24-23-generic x86_64

Revision history for this message
darkblue_b (maplabs) wrote :

On Feb 19, 2009, at 1:37 PM, Stefan Richter wrote:

> How does "lspci -v" show the controller? The PCI IDs look like from
> the
> Texas Instruments TSB43AB** family.
>

01:09.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23
IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
         Subsystem: Elitegroup Computer Systems Unknown device 8056
         Flags: bus master, medium devsel, latency 64, IRQ 19
         Memory at fdfff000 (32-bit, non-prefetchable) [size=2K]
         Memory at fdff8000 (32-bit, non-prefetchable) [size=16K]
         Capabilities: [44] Power Management version 2

> The messages
> ohci1394: fw-host0: Get PHY Reg timeout
> [0x00000000/0x00000000/100]
> indicate that the drivers were unable to perform the last steps of
> initialization. For now I don't know why.
>
> What if you load the new alternative drivers instead of the old ones?
> According to your lspci, the new ones are installed in parallel
> already. The new drivers were quite buggy in kernel 2.6.24 though.
> # modprobe -r ohci1394
> # modprobe firewire-ohci
>
> --
> ieee1394 port not recognized
> https://bugs.launchpad.net/bugs/329277
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux-meta” source package in Ubuntu: New
>
> Bug description:
> Jaunty a4 on an Acer ASE 380-UD440A
> 64bit AMD 4400+ Brisbane CPU
>
> also, all the hardware ports are listed in Gnome Desktop
> (I dont know if that is expected or not)
>
> see attachments
>
> ProblemType: Bug
> Architecture: amd64
> Date: Fri Feb 13 17:54:20 2009
> Dependencies:
>
> DistroRelease: Ubuntu 8.04
> NonfreeKernelModules: nvidia
> Package: linux None [modified: /var/lib/dpkg/info/linux.list]
> PackageArchitecture: amd64
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/
> usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: linux-meta
> Uname: Linux 2.6.24-23-generic x86_64

Revision history for this message
darkblue_b (maplabs) wrote :
Download full text (55.6 KiB)

jaunty a5 listings
have not tested the port yet.. tips welcome
===================================
ubuntu@ubuntu:~$ dmesg
[ 0.000000] BIOS EBDA/lowmem at: 0009f000/0009f000
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.28-8-generic (buildd@yellow) (gcc
version 4.3.3 (Ubuntu 4.3.3-3ubuntu5) ) #26-Ubuntu SMP Wed Feb 25
04:27:53 UTC 2009 (Ubuntu 2.6.28-8.26-generic)
[ 0.000000] Command line: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.gz
quiet splash --
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000
(reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000
(reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfff0000 (usable)
[ 0.000000] BIOS-e820: 00000000cfff0000 - 00000000cfff3000 (ACPI
NVS)
[ 0.000000] BIOS-e820: 00000000cfff3000 - 00000000d0000000 (ACPI
data)
[ 0.000000] BIOS-e820: 00000000d0000000 - 00000000e0000000
(reserved)
[ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000
(reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000
(reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
[ 0.000000] DMI 2.3 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working
it around.
[ 0.000000] last_pfn = 0x120000 max_arch_pfn = 0x3ffffffff
[ 0.000000] last_pfn = 0xcfff0 max_arch_pfn = 0x3ffffffff
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009f400 (usable)
[ 0.000000] modified: 000000000009f400 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 00000000cfff0000 (usable)
[ 0.000000] modified: 00000000cfff0000 - 00000000cfff3000 (ACPI NVS)
[ 0.000000] modified: 00000000cfff3000 - 00000000d0000000 (ACPI
data)
[ 0.000000] modified: 00000000d0000000 - 00000000e0000000 (reserved)
[ 0.000000] modified: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] modified: 0000000100000000 - 0000000120000000 (usable)
[ 0.000000] init_memory_mapping: 0000000000000000-00000000cfff0000
[ 0.000000] 0000000000 - 00cfe00000 page 2M
[ 0.000000] 00cfe00000 - 00cfff0000 page 4k
[ 0.000000] kernel direct mapping tables up to cfff0000 @ 10000-16000
[ 0.000000] last_map_addr: cfff0000 end: cfff0000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000120000000
[ 0.000000] 0100000000 - 0120000000 page 2M
[ 0.000000] kernel direct mapping tables up to 120000000 @
14000-1a000
[ 0.000000] last_map_addr: 1...

Revision history for this message
Andy Whitcroft (apw) wrote :

This is not a bug in the linux-meta package, moving to the linux package.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi darkblue_b,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 329277

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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