Le samedi 9 septembre 2006 13:24, vous avez écrit :
> Corentin CHARY <[EMAIL PROTECTED]> :
> [...]
>
> > J'ai vu après qu'il y'avais des patchs plus à jour ici
> > http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.18-rc5/r8169/ , mais pour
> > 2.6.18.
> >
> > Je me demande donc si il y'a un moyen de faire marcher le driver r8169.c
> > pour ma r8168 sur le kernel 2.6.17. Sinon, j'attendrais le 2.6.18 :).
>
> Vous appliquez les patchs pour 2.6.8-rc5 a la derniere version 2.6.18-rc
> disponible, vous modifiez la ligne qui comprend une directive 'request_irq'
> pour qu'elle soit identique a celle du pilote du noyau 2.6.17 et le pilote
> obtenu devrait compiler avec votre noyau 2.6.17.
>
> Si le lien ne se negocie pas bien, forcez une autonegotiation avec
> l'utilitaire mii-tool (ne s'applique qu'au pilote apres bricolage).
>
> Dans tous les cas un 'lspci -vvx' de votre machine sera le bienvenu.
>
> En cas de probleme, il serait preferable de poursuivre la discussion
> en anglais en mettant la liste de diffusion 'netdev@vger.kernel.org'
> en copie.

Small summary (for the mailing list) :
--
I have a Asus Laptop A6JC, and a r8168 network card. r1000 driver from realtek 
works, but I want to use r8169.c.
I first tried with 
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.17-rc6/r8169/ patchs, but it 
doesn't Work (eth0 is here, I can use ifconfig and route, but ping or dhcpcd 
doesn't work) 
--

Now I tried with http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.18-rc5/r8169/ 
I changed :
line 1751
- request_irq(dev->irq, rtl8169_interrupt, IRQF_SHARED, dev->name, dev);
+ request_irq(dev->irq, rtl8169_interrupt, SA_SHIRQ, dev->name, dev);
line 2224
- u32 mss = skb_shinfo(skb)->gso_size;
+ u32 mss = skb_shinfo(skb)->tso_size;
to get it compile on 2.6.17

I can load the module, eth0 is here, I can play with ifconfig. But i can't 
ping other machines on my network. dhcpd doesn't work too.

dmesg output :
r8169 Gigabit Ethernet driver 2.2LK loaded
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: RTL8168b/8111b at 0xf0fe6000, 00:17:31:c1:8d:ee, IRQ 16
r8169: eth0: link down
r8169: eth0: link down
r8169: eth0: link up

lspci :
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI 
Express Gigabit Ethernet controller (rev 01)
        Subsystem: ASUSTeK Computer Inc. Unknown device 11f5
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at c800 [size=256]
        Region 2: Memory at fe0ff000 (64-bit, non-prefetchable) [size=4K]
        Expansion ROM at fe0e0000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA 
PME(D0-,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Vital Product Data
        Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/1 
Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [60] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 1024 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
                Device: AtnBtn+ AtnInd+ PwrInd+
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
                Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s L1, Port 0
                Link: Latency L0s unlimited, L1 unlimited
                Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x4
        Capabilities: [84] Vendor Specific Information
00: ec 10 68 81 03 00 10 00 01 00 00 02 08 00 00 00
10: 01 c8 00 00 00 00 00 00 04 f0 0f fe 00 00 00 00
20: 00 00 00 00 00 00 00 00 02 01 00 00 43 10 f5 11
30: 00 00 0e fe 40 00 00 00 00 00 00 00 0b 01 00 00


I tried mii-tool (and mii-diag) but I get that :
SCIOCGMIIPHY on eth0 failed: Operation not supported

Thanks
-- 
CHARY 'Iksaif' Corentin
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://xf.iksaif.net
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to