Re: problem with MySon Ethernet Nics

2004-03-22 Thread GiTi

   It is driver for MySon Ethernet Nics and it is in
   :"/usr/src/sys/dev/my", compiled it into kernel, that is all.
   Note: before compiling it into kernel, under file GENERIC (or modified
   file of GENERIC) finding the division of NIC and add :
   "device   my"
   rebuild the kernel now :)

   - Ná»i dung gá»c 
   Gá»i tá: "Olaf Hoyer" <[EMAIL PROTECTED]>
   Gá»i Äán: "GiTi" <[EMAIL PROTECTED]>
   Äá»ng gá»i: [EMAIL PROTECTED], "Olaf Hoyer"
   <[EMAIL PROTECTED]>
   Chá Äá»: Re: problem with MySon Ethernet Nics
   Ngà y: Mon 22/03/2004 19:21
   On Mon, 22 Mar 2004, GiTi wrote:
   >
   > Hello Olaf Hoyer and list, i want to thank you for your help. I have
   > resolved this problem. I also succeed to move server from Redhat box
   > to freeBSD too.
   Hi!
   well, just for the archives, what did you do?
   I looked around the driver source, for identifying the chipset, as it
   seems a realtek in disguise, but am a bit busy at work right now...
   cu
   Olaf

   
   www.airland.kiev.ua - Airland Network eMail
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-22 Thread Olaf Hoyer
On Mon, 22 Mar 2004, GiTi wrote:

>
>Hello Olaf Hoyer and list, i want to thank you for your help. I have
>resolved this problem. I also succeed to move server from Redhat box
>to freeBSD too.


Hi!

well, just for the archives, what did you do?

I looked around the driver source, for identifying the chipset, as it
seems a realtek in disguise, but am a bit busy at work right now...

cu
Olaf
-- 
Olaf Hoyer[EMAIL PROTECTED]
Fuerchterliche Erlebniss geben zu raten,
ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist.
(Nietzsche, Jenseits von Gut und Boese)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-22 Thread GiTi

   Hello Olaf Hoyer and list, i want to thank you for your help. I have
   resolved this problem. I also succeed to move server from Redhat box
   to freeBSD too.
   Good luck to you
   
   www.airland.kiev.ua - Airland Network eMail
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-20 Thread GiTi
> > yes, my Nic has own driver but ... only for Freebsd 2.x and 3.x. And
this is
> > its instruction
>
> Ok, so there are sources, but the driver structure from 4.x and 5.x
> differs a lot from 3.x, so they cannot work.
>
> > pcib2:  at device 30.0 on pci0
> > pci3:  on pcib2
> > pci3:  at device 4.0 (no driver attached)
>
> ok, these were the lines that were important.
>
> >
> > when i run command pciconf, i also met such error:
> > Operation is not permitted
>
> Probably you weren't root, pciconf -lv needs root riviliges.
>
>
> With a 4.9-stable, it looks like this:
>
> pris 14:03 >pciconf -lv
> pciconf: /dev/pci: Permission denied
> pris 14:03 >su -
> Password:
> pris# pciconf -lv
>
> [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x1a318086 rev=0x04
> hdr=0x01
> vendor   = 'Intel Corporation'
> device   = '82845/E/MP/MZ Brookdale CPU to AGP Bridge'
> class= bridge
> subclass = PCI-PCI
>
>
> In the case above, the entries of:
> pcib2 and pci3  are important, could you post them?
>
> Also please post a uname -a string of your system.

Olaf Hoyer, thank you again

i knows Nic's driver is for 2.x and 3.x, i have compiled its driver because
i can not probe it

i was root when using pciconf. I was confused and ... And I have just
reinstall my freebsd 5.2, now i can run pciconf
And this is the result:
---begin---
[EMAIL PROTECTED]:0:0:  class=0x06 card=0x chip=0x1a308086 rev=0x11
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82845/E/MP/MZ Brookdale CPU to I/O Bridge'
class= bridge
subclass = HOST-PCI
[EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x1a318086 rev=0x11
hdr=0x01
vendor   = 'Intel Corporation'
device   = '82845/E/MP/MZ Brookdale CPU to AGP Bridge'
class= bridge
subclass = PCI-PCI
[EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x56611462 chip=0x24c28086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB/DBM (ICH4/M) USB UHCI Controller #1'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x56611462 chip=0x24c48086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB/DBM (ICH4/M) USB UHCI Controller #2'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x56611462 chip=0x24c78086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB/DBM (ICH4/M) USB UHCI Controller #3'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x39801462 chip=0x24cd8086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB/DBM (ICH4/M) USB EHCI Controller'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:30:0:class=0x060400 card=0x chip=0x244e8086
rev=0x82
hdr=0x01
vendor   = 'Intel Corporation'
device   = '82801BA/CA/DB/EB/ER (ICH2/3/4/5/5R) Hub Interface to PCI Bridge'
class= bridge
subclass = PCI-PCI
[EMAIL PROTECTED]:31:0:class=0x060100 card=0x chip=0x24c08086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB (ICH4) LPC Interface Bridge'
class= bridge
subclass = PCI-ISA
[EMAIL PROTECTED]:31:1:  class=0x01018a card=0x56611462 chip=0x24cb8086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB (ICH4) UltraATA/100 EIDE Controller'
class= mass storage
subclass = ATA
[EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x56611462 chip=0x24c38086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB/DBM (ICH4/M) SMBus Controller'
class= serial bus
subclass = SMBus
[EMAIL PROTECTED]:31:5:class=0x040100 card=0x56611462 chip=0x24c58086
rev=0x02
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82801DB/DBM (ICH4/M) AC'97 Audio Controller'
class= multimedia
subclass = audio
[EMAIL PROTECTED]:0:0: class=0x03 card=0x000510de chip=0x002810de rev=0x15
hdr=0x00
vendor   = 'NVIDIA Corporation'
device   = 'NV5 TNT2 / TNT2 Pro'
class= display
subclass = VGA
[EMAIL PROTECTED]:4:0: class=0x02 card=0x132010bd chip=0x08031516 rev=0x00
hdr=0x00
vendor   = 'Myson Technology Inc'
device   = '803 series PCI Ethernet controller'
class= network
subclass = ethernet
end---
afterthat i run
# ifconfig -a
-begin---
plip0: flags=8810 mtu 1500
lo0: flags=8049 mtu 16384
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
end--
I will post the uname -a string of system if needed but it looks like :
FreeBSd 5.2 ... i386 ... GENERIC
I have not rebuilt my kernel yet.
any suggestions? Thanks in advanced



www.airland.kiev.ua - Airland Network eMail
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-20 Thread Olaf Hoyer
On Sat, 20 Mar 2004, GiTi wrote:

> Olaf Hoyer wrote:
> > Well, do you mean with "compiled its driver" that they provide some own
> > driver?
>
> yes, my Nic has own driver but ... only for Freebsd 2.x and 3.x. And this is
> its instruction

Hi!

Ok, so there are sources, but the driver structure from 4.x and 5.x
differs a lot from 3.x, so they cannot work.


> pcib2:  at device 30.0 on pci0
> pci3:  on pcib2
> pci3:  at device 4.0 (no driver attached)

ok, these were the lines that were important.

>
> when i run command pciconf, i also met such error:
> Operation is not permitted

Probably you weren't root, pciconf -lv needs root riviliges.


With a 4.9-stable, it looks like this:

pris 14:03 >pciconf -lv
pciconf: /dev/pci: Permission denied
pris 14:03 >su -
Password:
pris# pciconf -lv

[EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x1a318086 rev=0x04
hdr=0x01
vendor   = 'Intel Corporation'
device   = '82845/E/MP/MZ Brookdale CPU to AGP Bridge'
class= bridge
subclass = PCI-PCI




In the case above, the entries of:
pcib2 and pci3  are important, could you post them?

Also please post a uname -a string of your system.

HTH
Olaf

-- 
Olaf Hoyer[EMAIL PROTECTED]
Fuerchterliche Erlebniss geben zu raten,
ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist.
(Nietzsche, Jenseits von Gut und Boese)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-20 Thread GiTi
Olaf Hoyer wrote:
> Well, do you mean with "compiled its driver" that they provide some own
> driver?

yes, my Nic has own driver but ... only for Freebsd 2.x and 3.x. And this is
its instruction
begin-

Installation:

1. copy the source codes if_fet.c and if_fetreg.h to /sys/pci directory,

#cp if_fet.c /sys/pci
#cp if_fetreg.h /sys/pci

2. modify /sys/conf/files, add the following line

pci/if_fet.c optional   fet  device-driver

3. modify /usr/src/sys/i386/conf/GENERIC, add the following line

device  fet0

4. compile the kernel,

#cd /usr/src/sys/i386/conf
#cp GENERIC MYKERNEL
#/usr/sbin/config MYKERNEL
#cd /usr/src/sys/compile/MYKERNEL
#make depend
#make
#make install

5. reboot the system,

#reboot

6. bind your card to an IP address

#ifconfig fet0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}

7. now, you should be able to ping local network.

--end---


> Ok, in order to be able to help you, we  need at least a dmesg with the
> card, and the _exact_ message, and also a pciconf -lv will be helpful.
> Because of rebranding of network chips one can never be sure what
> chip-revision you get with those relabelled products.
>
> Please boot a kernel.GENERIC and post that dmesg.

thank you, Olaf Hoyer
this is my dmesg.today:
begin-
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.2-RELEASE #0: Sun Jan 11 04:21:45 GMT 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a33000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a3326c.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(R) CPU 1.80GHz (1804.10-MHz 686-class CPU)
Origin = "GenuineIntel"  Id = 0xf13  Stepping = 3
Features=0x3febfbff
real memory  = 268369920 (255 MB)
avail memory = 251047936 (239 MB)
ACPI APIC Table: 
ioapic0  irqs 0-23 on motherboard
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 10 entries at 0xc00f7a60
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.MDET] (Node
0xc16b2ba0), AE_AML_REGION_LIMIT
ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0._CRS] (Node
0xc16b2ae0), AE_AML_REGION_LIMIT
ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0._CRS] (Node
0xc16b2ae0), AE_AML_REGION_LIMIT
can't fetch resources for \_SB_.PCI0 - AE_AML_REGION_LIMIT
ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.MDET] (Node
0xc16b2ba0), AE_AML_REGION_LIMIT
ACPI-1287: *** Error: Method execution failed [\_SB_.MEM_._CRS] (Node
0xc16bd840), AE_AML_REGION_LIMIT
ACPI-0175: *** Error: Method execution failed [\_SB_.MEM_._CRS] (Node
0xc16bd840), AE_AML_REGION_LIMIT
can't fetch resources for \_SB_.MEM_ - AE_AML_REGION_LIMIT
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_cpu0:  on acpi0
acpi_cpu1:  on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
acpi_button0:  on acpi0
pcib0:  on acpi0
pci0:  on pcib0
agp0:  mem 0xe000-0xe3ff at device
0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pcib1: slot 0 INTA is routed to irq 16
pci1:  at device 0.0 (no driver attached)
uhci0:  port 0xd400-0xd41f irq 16
at device 29.0 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xd800-0xd81f irq 19
at device 29.1 on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xdc00-0xdc1f irq 18
at device 29.2 on pci0
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pci0:  at device 29.7 (no driver attached)
pcib2:  at device 30.0 on pci0
pci3:  on pcib2
pci3:  at device 4.0 (no driver attached)
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port
0xfc00-0xfc0f,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
pci0:  at device 31.3 (no driver attached)
pci0:  at device 31.5 (no driver attached)
acpi_button1:  on acpi0
atkbdc0:  port 0x64,0x60 irq 1 on acpi0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
fdc0: cmd 3 failed at out byte 1 of 3
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0:  on ppc0
pli

Re: problem with MySon Ethernet Nics

2004-03-19 Thread Olaf Hoyer
On Fri, 19 Mar 2004, GiTi wrote:

> On Thursday 18 March 2004 18:09, Olaf Hoyer wrote:
>
> > Ok, do you have any Information about the chipset used on these?
> >
> > What is needed, is the dmesg output, at least those lines where the nic
> > is probed.
> >
> > should read something like:
> >
> > pci2:  foo bar
>
> dmesg print out something like:
>
> pci2:
>
>
> My Nics is:
> SURECOM EP-320X-S 100/10M Ethernet PCI Adapter
>
> i have tried to rebuilded the kernel and compiled its driver (basing on the
> instruction) into kernel several times but I have not succeeded
>
> It is said that freebsd 5.2 supported MySon Ethernet Nics and ... i am
> surprized . Maybe I have missed somthing?
> Please help me to solve this problem
>

Hi!

Well, do you mean with "compiled its driver" that they provide some own
driver?

Ok, in order to be able to help you, we  need at least a dmesg with the
card, and the _exact_ message, and also a pciconf -lv will be helpful.
Because of rebranding of network chips one can never be sure what
chip-revision you get with those relabelled products.

Please boot a kernel.GENERIC and post that dmesg.

HTH
Olaf



-- 
Olaf Hoyer[EMAIL PROTECTED]
Fuerchterliche Erlebniss geben zu raten,
ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist.
(Nietzsche, Jenseits von Gut und Boese)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-19 Thread GiTi
On Thursday 18 March 2004 18:09, Olaf Hoyer wrote:

> Ok, do you have any Information about the chipset used on these?
>
> What is needed, is the dmesg output, at least those lines where the nic
> is probed.
>
> should read something like:
>
> pci2:  foo bar

dmesg print out something like:

pci2:


My Nics is:
SURECOM EP-320X-S 100/10M Ethernet PCI Adapter

i have tried to rebuilded the kernel and compiled its driver (basing on the
instruction) into kernel several times but I have not succeeded

It is said that freebsd 5.2 supported MySon Ethernet Nics and ... i am
surprized . Maybe I have missed somthing?
Please help me to solve this problem


www.airland.kiev.ua - Airland Network eMail
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problem with MySon Ethernet Nics

2004-03-18 Thread Olaf Hoyer
On Fri, 19 Mar 2004, GiTi wrote:

> hello list
>
> I have just upgradated to freeBSD 5.2 but My freebsd box does not recognize
> Nic (Myson Ethernet Nic). Please help me to solve this problem
>
Ok, do you have any Information about the chipset used on these?

What is needed, is the dmesg output, at least those lines where the nic
is probed.

should read something like:

pci2:  foo bar

and the output from pciconf -lv regarding that device will be helpful in
identifying that thing, and perhaps, when its only a matter of some PCI
IDs, to add them to the driver...

HTH
Olaf



-- 
Olaf Hoyer[EMAIL PROTECTED]
Fuerchterliche Erlebniss geben zu raten,
ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist.
(Nietzsche, Jenseits von Gut und Boese)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"