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

Bug#581554: marked as done (firmware-realtek: Incorrect firmware)

Your message dated Sun, 18 Jul 2010 17:51:47 +0100
with message-id <1279471907.4883.120.camel@localhost>
and subject line Re: Bug#581554: Firmware or driver
has caused the Debian Bug report #581554,
regarding firmware-realtek: Incorrect firmware
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.)


-- 
581554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581554
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-realtek
Version: 0.24
Severity: important

Firmware provided with the package does not allow wireless connection
on Belkin "F5D8053 N Wireless USB Adapter v6000". The right firmware
that does do have a md5sum of 68533bf8078a9e00966a78c9f2da4b9b . This
is the one included in rtl8192su_linux_2.6.0002.0708.2009.tar.gz from
Realtek.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34-rc7-mjj-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Sun, 2010-07-18 at 17:40 +0100, John Talbut wrote:
> Mainly because that is where people seem to be looking for a solution!  
> Also because the firmware with 0.26 is identical with earlier firmware 
> that I have downloaded and opinion seems to be that different firmware 
> is needed for a 64bit kernel.

This is nonsense.  The firmware is independent of the kernel
architecture.

> And because the messages I am getting are 
> similar to those reported above:

They are similar in so far as the initialisation messages from this
driver are always similar

[...]
> How  can I check whether the problem is with the firmware or the driver?

You can't.  You should accept my judgement that the firmware is now
correct.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: