[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#399165: marked as done (linux-source-2.6.18: hostap_cs not talking to Belkin F5D6020)

Your message dated Sat, 5 Jul 2008 12:07:33 +0200
with message-id <20080705100733.GH7212@baikonur.stro.at>
and subject line Re: Bug#399165: linux-source-2.6.18: hostap_cs not talking to Belkin F5D6020
has caused the Debian Bug report #399165,
regarding linux-source-2.6.18: hostap_cs not talking to Belkin F5D6020
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
399165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399165
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-source-2.6.18
Version: 2.6.18-5
Severity: normal


This card used to work with previous kernels.

Card insertion generates this syslog:

kernel: pccard: PCMCIA card inserted into slot 0
kernel: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xd3fff 0xe0000-0xfffff
kernel: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x600fffff
kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
kernel: pcmcia: registering new device pcmcia0.0

ie. hostap_cs is not loaded (orinoco_cs is blacklisted).

modprobe hostap_cs:

kernel: ieee80211_crypt: registered algorithm 'NULL'
kernel: hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)

and ifconfig -a indicates no new interfaces have been created. Further,
lspcmcia indicates "no driver":

# lspcmcia -v
Socket 0 Bridge:        [yenta_cardbus]         (bus ID: 0000:00:02.0)
        Configuration:  state: on       ready: yes
        Voltage: 5.0V Vcc: 5.0V Vpp: 5.0V
Socket 0 Device 0:      [-- no driver --]       (bus ID: 0.0)
        Configuration:  state: on
        Product Name:   Belkin 11Mbps Wireless Notebook Network Adapter Version 01.02
        Identification: manf_id: 0x0156 card_id: 0x0002
                        function: 6 (network)
                        prod_id(1): "Belkin" (0x3805a391)
                        prod_id(2): "11Mbps Wireless Notebook Network Adapter" (0xad4c7744)
                        prod_id(3): "Version 01.02" (0x4b74baa0)
                        prod_id(4): --- (---)

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-a21m.27
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-source-2.6.18 depends on:
ii  binutils                      2.17-3     The GNU assembler, linker and bina
ii  bzip2                         1.0.3-6    high-quality block-sorting file co

Versions of packages linux-source-2.6.18 recommends:
ii  gcc                          4:4.1.1-13  The GNU C compiler
ii  libc6-dev [libc-dev]         2.3.6.ds1-7 GNU C Library: Development Librari
ii  make                         3.81-2      The GNU version of the "make" util

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, Jul 05, 2008 at 02:54:15PM +0800, Clayton wrote:
> On Fri, 4 Jul 2008 22:27:42 +0200
> maximilian attems <max@stro.at> wrote:
> 
> > > This card used to work with previous kernels.
> > 
> > sorry for late reply.
> > could you test up to date kernels aka 2.6.25 or even better
> > 2.6.26-rc8?
> > 
> > so that we can see if that bug still exists and upstream needs
> > to be notified.
> 
> This one has definitely been overcome by events. A while back I tested
> the card on a Windows machine, where it also seemed to have stopped
> working, so I came to the conclusion that the card was broken and threw
> it out. No idea whether breakage occurred before or after I reported
> this bug.
> 
> If you have no other testers/reporters, you might as well just close
> the bug.
> 
> Clayton

right no other report, thus assuming hardware failure.
closing, thanks for the quick feedback

best regards

-- 
maks

--- End Message ---
Reply to: