I met one strange error on sis900 ethernet driver. I'm using cvs freebios on 6 Oct, 2002 , kernel 2.4.17, mainboard is winfast6300. After booting using linuxbios stored in DOC, I boot my host linux system using normal bios. the host linux is the same system as in DOC. I test pings, the result is ( after linuxbios booting): ping -s 2592 192.12.11.1 ( remote ip addr ) 0% lost ping -s 2593 192.12.11.1 ( remote ip addr ) no response, 100% lost I can't make the mainboard work correctly until I have booted windows98. Then I use my host linux system to boot, the thing is ok. (after windows98 booting ) ping -s 2592 192.12.11.1 0% lost ping -s 2593 192.12.11.1 0% lost
What's the problem, maybe something wrong with pci ,or sis900 init code. thanks zhu
__________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com
On Mon, 2002-10-14 at 22:30, zhu shi song wrote:
I met one strange error on sis900 ethernet driver. I'm using cvs freebios on 6 Oct, 2002 , kernel 2.4.17, mainboard is winfast6300. After booting using linuxbios stored in DOC, I boot my host linux system using normal bios. the host linux is the same system as in DOC. I test pings, the result is ( after linuxbios booting): ping -s 2592 192.12.11.1 ( remote ip addr ) 0% lost ping -s 2593 192.12.11.1 ( remote ip addr ) no response, 100% lost
Why are your using a packet size of 259x bytes ?? It just makes no sense since the MTU of ethernet is about 1500.
I can't make the mainboard work correctly until I have booted windows98. Then I use my host linux system to boot, the thing is ok. (after windows98 booting ) ping -s 2592 192.12.11.1 0% lost ping -s 2593 192.12.11.1 0% lost
What's the problem, maybe something wrong with pci ,or sis900 init code.
Some early 630A/E chips has some kind of bugs due to semiconductor fab process. Probably you are just unlucky to get a bad one.
Ollie
(1) IP has the fragmentation function, ip should support it correctly (2) why windows98 can handle the matter correctly, but linux can't , maybe linux pci or sis900 ehternet driver has some bug (3) maybe linuxbios init sis900 so unusual that linux can't handle it correctly. thanks zhu ollie lho ollie@sis.com.tw wrote:On Mon, 2002-10-14 at 22:30, zhu shi song wrote:
I met one strange error on sis900 ethernet driver. I'm using cvs freebios on 6 Oct, 2002 , kernel 2.4.17, mainboard is winfast6300. After booting using linuxbios stored in DOC, I boot my host linux system using normal bios. the host linux is the same system as in DOC. I test pings, the result is ( after linuxbios booting): ping -s 2592 192.12.11.1 ( remote ip addr ) 0% lost ping -s 2593 192.12.11.1 ( remote ip addr ) no response, 100% lost
Why are your using a packet size of 259x bytes ?? It just makes no sense since the MTU of ethernet is about 1500.
I can't make the mainboard work correctly until I have booted windows98. Then I use my host linux system to boot, the thing is ok. (after windows98 booting ) ping -s 2592 192.12.11.1 0% lost ping -s 2593 192.12.11.1 0% lost
What's the problem, maybe something wrong with pci ,or sis900 init code.
Some early 630A/E chips has some kind of bugs due to semiconductor fab process. Probably you are just unlucky to get a bad one.
Ollie
_______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
--------------------------------- Do you Yahoo!? Faith Hill - Exclusive Performances, Videos, & more faith.yahoo.com
And also I have tested different packet size , I found odd len packet can't response, even can. for example: ping -s 122 192.12.11.1 0% lost ping -s 123 192.12.11.1 100% lost thanks zhu ollie lho ollie@sis.com.tw wrote:On Mon, 2002-10-14 at 22:30, zhu shi song wrote:
I met one strange error on sis900 ethernet driver. I'm using cvs freebios on 6 Oct, 2002 , kernel 2.4.17, mainboard is winfast6300. After booting using linuxbios stored in DOC, I boot my host linux system using normal bios. the host linux is the same system as in DOC. I test pings, the result is ( after linuxbios booting): ping -s 2592 192.12.11.1 ( remote ip addr ) 0% lost ping -s 2593 192.12.11.1 ( remote ip addr ) no response, 100% lost
Why are your using a packet size of 259x bytes ?? It just makes no sense since the MTU of ethernet is about 1500.
I can't make the mainboard work correctly until I have booted windows98. Then I use my host linux system to boot, the thing is ok. (after windows98 booting ) ping -s 2592 192.12.11.1 0% lost ping -s 2593 192.12.11.1 0% lost
What's the problem, maybe something wrong with pci ,or sis900 init code.
Some early 630A/E chips has some kind of bugs due to semiconductor fab process. Probably you are just unlucky to get a bad one.
Ollie
_______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
--------------------------------- Do you Yahoo!? Faith Hill - Exclusive Performances, Videos, & more faith.yahoo.com
-
ollie lho -
zhu shi song