Re: firmware-realtek (0.29) can't work at amd64

On Thu, 19 May 2011 11:29:35 +0800, spp mg wrote:

2011/5/17 Camaleón <noelamac@xxxxxxxxx>

(...)

sorry,I am too late to reply.

(no problem, but don't make use of html formatted messages and better
yet if you reply at bottom or inline and don't cross-post ;-))

Ok, like this?

Much better, thanks :-)

wicd scan function is ok, but when I connect net,it will connect a
long time,and display "password error".But I'm sure password is
right.(The config can use in kernel 2.6.26.)

Make wicd to be more verbose if possible, there must be an option in
the program settings you can toggle on.

Oh,I used "wicd-curses".I will try to use "wicd-cli" or find logs.

Hopefully logs will help you to understand why it cannot be associated to
the AP.

Also, compare both "/var/log/syslog" files from the computer where it
works and from the one that fails.

On the i386,I just use apt install firmware-realtek (0.29).

And it works fine? Then it can be a bug within the amd64 port package.

Yes,it's works fine.
When I go back hometown (less then 1 month), I will use live cd of i386
and amd64 to test again. Because I just use other computer to test i386.

If it's bug,how to report?

If you followed the steps given at the wiki:

http://wiki.debian.org/rtl819x#Wheezy

And you are still experiencing problems within the amd64 system, you can
open a bug report against "wireless-tools" because the package of
firmware itself is architecture-independent.

There is a very useful tool (reportbug) you can use to open the report at
Debian BTS, just follow the on-screen wizard.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Archive: http://lists.debian.org/pan.2011.05.19.11.26.13@xxxxxxxxx

Relevant Pages

  • Re: [current tinderbox] failure on i386/i386
    ... I'm seeing similar, but slightly different, under amd64 current (have ... been for the past several days, but didn't report it in the hopes it ... *** Error code 1 ... >> To unsubscribe, send any mail to ...
    (freebsd-current)
  • Re: Spam from National Semiconductor
    ... I can't seem to unsubscribe ... I now read my email by logging on to my ISP's site and going to Mail. ... I can report incoming mail as SPAM and have sources blocked. ...
    (sci.electronics.design)
  • =?windows-1256?Q?RE:_Tripwi?= =?windows-1256?Q?re_cant_s?= =?windows-1256?Q?end_report?=
    ... I don't have much to offer on your problem with tripwire, ... This may be happening to other subscribers ot debian-user. ... With the following command I can read the report. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Rogue Filename - Cant Do A Thing With It
    ... directory was "report" but I changed it to "reportX" and moved all the ... filesystem corruption. ... Have you tried running fsck over that device? ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: usb harddrive problem
    ... You can try by reloading the usb module: ... modprobe -r usb_storage ... Maybe is time to report it... ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)