Processed: Re: Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade
Processing commands for [EMAIL PROTECTED]: > reassign 456310 hal Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade Bug reassigned from package `hal-info' to `hal'. > forcemerge 456314 456310 Bug#456314: hal exits with Rule is NULL on jump Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade Bug#456890: hal-info: hald fails to start Bug#457017: hal exits with Rule is NULL on jump Bug#457020: hal exits with Rule is NULL on jump Forcibly Merged 456310 456314 456890 457017 457020. > tag 456314 +pending Bug#456314: hal exits with Rule is NULL on jump There were no tags set. Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade Bug#456890: hal-info: hald fails to start Bug#457017: hal exits with Rule is NULL on jump Bug#457020: hal exits with Rule is NULL on jump Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade
severity 456310 important thanks On Fri, Dec 14, 2007 at 03:34:25PM +0100, Stefano Zacchiroli wrote: > Severity grave since I bet other people with the same Intel card will > have a network shortage upon installing the current package version. Downgrading to important. I've asked various people with an ipw2200 to see if they could reproduce this bug and none of them can. Which indicates it isn't a general ipw2200 issue. Could you provide the debug info Michael requested, so we can find out what's going wrong for you :) ? Sjoerd -- Your wig steers the gig. -- Lord Buckley -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade
Processing commands for [EMAIL PROTECTED]: > severity 456310 important Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#456310: [Pkg-utopia-maintainers] Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade
Stefano Zacchiroli schrieb:
> Package: hal-info
> Version: 20071212-1
> Severity: grave
>
> After the last upgrade of hal-info, network manager fails to find any
> network device only reporting the error message mentioned in the subject
> ("no network device has been found") when clicking on the ex nm-applet
> icon. (Note that this happens even with the network device not being
> mentioned in /etc/network/interfaces as required by network-manager.)
>
> Downgrading hal-info to the testing version (20071030-1) fixes the
> problem.
>
> I presume (though I haven't checked) that for finding the network
> interfaces which are not listed in /etc/network/interfaces to be
> managed, network manager does some lookup via hal, which fails due to
> some hal-info breakage. Hence, I think that the other way of using
> network-manager via /etc/network/interfaces suggested in
> /usr/share/doc/network-manager/README.Debian (namely, to list the
> desired interfaces as "auto" and with "dhcp") works, but I haven't tried
> that.
>
> My (wireless) network card is an Intel as described below by lspci:
>
> 06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network
> Connection (rev 05)
> Subsystem: Intel Corporation Unknown device 2702
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> SERR- Latency: 32 (750ns min, 6000ns max), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 20
> Region 0: Memory at b0204000 (32-bit, non-prefetchable) [size=4K]
> Capabilities:
>
> and works properly (without network-manager / hal) with the ipw2200
> kernel module.
>
> Severity grave since I bet other people with the same Intel card will
> have a network shortage upon installing the current package version.
>
Could you please attach the output of lshal, nm-tool and also
hald --daemon=no --verbose=yes
Thanks,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#456310: network manager returns "no network device has been found" after last hal-info upgrade
Package: hal-info
Version: 20071212-1
Severity: grave
After the last upgrade of hal-info, network manager fails to find any
network device only reporting the error message mentioned in the subject
("no network device has been found") when clicking on the ex nm-applet
icon. (Note that this happens even with the network device not being
mentioned in /etc/network/interfaces as required by network-manager.)
Downgrading hal-info to the testing version (20071030-1) fixes the
problem.
I presume (though I haven't checked) that for finding the network
interfaces which are not listed in /etc/network/interfaces to be
managed, network manager does some lookup via hal, which fails due to
some hal-info breakage. Hence, I think that the other way of using
network-manager via /etc/network/interfaces suggested in
/usr/share/doc/network-manager/README.Debian (namely, to list the
desired interfaces as "auto" and with "dhcp") works, but I haven't tried
that.
My (wireless) network card is an Intel as described below by lspci:
06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network
Connection (rev 05)
Subsystem: Intel Corporation Unknown device 2702
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR-
and works properly (without network-manager / hal) with the ipw2200
kernel module.
Severity grave since I bet other people with the same Intel card will
have a network shortage upon installing the current package version.
Thanks in advance,
Cheers.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
