On Tue, Jul 08, 2008 at 11:09:58PM +0900, NAGATA Shinya wrote:
> > Thanks! This is good information. It seems that newer 810x PCIe
> > controllers seems to use different descriptor format such that
> > checksum offload didn't work on these controllers.
> > Backout previous patch and try attache
> Thanks! This is good information. It seems that newer 810x PCIe
> controllers seems to use different descriptor format such that
> checksum offload didn't work on these controllers.
> Backout previous patch and try attached patch.
I can connect via SSH. It seems work fine. Thank you!
--
NAGAT
On Tue, Jul 08, 2008 at 08:44:46PM +0900, To NAGATA Shinya wrote:
> On Tue, Jul 08, 2008 at 06:52:20PM +0900, NAGATA Shinya wrote:
> > > > re0: MAC rev. 0x0020
> > > > re0: Unknown H/W revision: 0x2480
> > > > device_attach: re0 attach returned 6
> > > >
> > >
> > > Apply a
On Tue, Jul 08, 2008 at 06:52:20PM +0900, NAGATA Shinya wrote:
> > > re0: MAC rev. 0x0020
> > > re0: Unknown H/W revision: 0x2480
> > > device_attach: re0 attach returned 6
> > >
> >
> > Apply attached one and let me know how it goes.
>
> Thank you for your patch.
>
> It doe
> > re0: MAC rev. 0x0020
> > re0: Unknown H/W revision: 0x2480
> > device_attach: re0 attach returned 6
> >
>
> Apply attached one and let me know how it goes.
Thank you for your patch.
It doesn't work on 6.3-p2.
> pci1: on pcib1
> pci1: at device 0.0 (no driver attached)
It can fi
On Tue, Jul 08, 2008 at 10:42:17AM +0400, Andrey V. Elsukov wrote:
> Pyun YongHyeon wrote:
> > > re0: port 0x2000-0x20ff mem
> > > 0x4820-0x48200
> > > fff,0x4800-0x4800 irq 16 at device 0.0 on pci1
> > > re0: Chip rev. 0x2480
> > ^^
>
> Hi, Pyun
Pyun YongHyeon wrote:
> re0: port 0x2000-0x20ff mem
> 0x4820-0x48200
> fff,0x4800-0x4800 irq 16 at device 0.0 on pci1
> re0: Chip rev. 0x2480
^^
Hi, Pyun
Did you look to the last vendors driver? It seems it has
different probe code and supports n
On Tue, Jul 08, 2008 at 10:14:15AM +0900, Tadashi Takahashi wrote:
> I have same motherboard and I tried re patch as follows.
> The result is still failed.
>
> http://people.freebsd.org/~yongari/re/re.HEAD.20080624
>
>
> re0: port 0x2000-0x20ff mem
> 0x4820-0x48200
> fff,0x480
I have same motherboard and I tried re patch as follows.
The result is still failed.
http://people.freebsd.org/~yongari/re/re.HEAD.20080624
re0: port 0x2000-0x20ff mem 0x4820-0x48200
fff,0x4800-0x4800 irq 16 at device 0.0 on pci1
re0: Chip rev. 0x2480
re0: MAC rev. 0x0020
r
On Tue, Jul 08, 2008 at 07:35:30AM +0900, NAGATA Shinya wrote:
> > Could you please try 'boot -v' and see if there is some error messages?
>
> 're0' is displayed. But it seems like kernel couldn't find a driver.
> | re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x2000
> | pci1: at device
> Could you please try 'boot -v' and see if there is some error messages?
're0' is displayed. But it seems like kernel couldn't find a driver.
| re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x2000
| pci1: at device 0.0 (no driver attached)
--
NAGATA Shinya
Consoles: internal video/keyboard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NAGATA Shinya wrote:
| I got Intel D945GCLF and it has Realtek 8102EL chip.
| But it is not found by kernel. dmesg does not display as 're' or 'rl'.
|
| How to find hwrev (revision code) to add if_rlreg.h and if_re.c ?
| I'm using 6.3-R and added this
12 matches
Mail list logo
