From: Wide Link PC <infos@widelinkpc.be>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 12228] New: D-Link 530 TX Rev. C2 not working
Date: Tue, 23 Dec 2008 08:46:19 +0100 [thread overview]
Message-ID: <4950974B.9000207@widelinkpc.be> (raw)
In-Reply-To: <20081215001816.79f1332b.akpm@linux-foundation.org>
Good morning,
Ahah, Santa Claus is in the place !!! Fixed with the last kernel update
of Ubuntu 8.10.
I was right, it was from kernel.
Thanks for your answer.
Merry Chrismas and happy new year 2009.
Oliver.
Andrew Morton a écrit :
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Mon, 15 Dec 2008 00:00:56 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
>
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=12228
>>
>> Summary: D-Link 530 TX Rev. C2 not working
>> Product: Drivers
>> Version: 2.5
>> KernelVersion: 2.6.27.X
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Network
>> AssignedTo: jgarzik@pobox.com
>> ReportedBy: infos@widelinkpc.be
>>
>>
>> Latest working kernel version: 2.6.24 and 2.6.25
>> Earliest failing kernel version: 2.6.27.X
>> Distribution: Actually Ubuntu 8.10 Deskstop (32 bit) and Fedora 10 Deskstop (32
>> bit)
>> Hardware Environment: Always the same since many years to test different
>> distributions: Asus P4P800 SE, GeForce 7800 GS in AGP, 2 x 1 GB DDR 1 Kingmax.
>> Software Environment: just TeamSpeak Server on Ubuntu 8.10 and CCSM (Compiz
>> Configurator). Fedora nothing more than original package. Just update from
>> Fedora repositories.
>> Problem Description: in the past this hardware working fine with previous
>> version of distribution. Since the last version, my nertwork card doesn't work.
>> I'm not a hacker, just want help you.
>>
>> Steps to reproduce: I have tested 2 distributions with install on my hardrive.
>> Not working. I change hardrive to see on Windows (whith drivers of course) and
>> my card working fine. The hardware working fine, but I think there is a problem
>> with Linux driver. I haven't problem to connect internet with the onboard chip
>> Marvell Yukon.
>>
>> I hope it's not a bug from Network Manager, but I think no.
>>
>>
>
> ok, I give up ;) Which device driver does that card use?
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature database 3691 (20081214) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
prev parent reply other threads:[~2008-12-23 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12228-10286@http.bugzilla.kernel.org/>
2008-12-15 8:18 ` [Bugme-new] [Bug 12228] New: D-Link 530 TX Rev. C2 not working Andrew Morton
2008-12-23 7:46 ` Wide Link PC [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4950974B.9000207@widelinkpc.be \
--to=infos@widelinkpc.be \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).