Steve Kieu wrote:
Is this the correct summary of the problem
scenarios.
Assume each one starts from cold boot (power off).
* 2.6.13(skge) boot=> Good
* 2.6.13(sk98lin) boot => Good
* 2.6.13 + SK version of sk98lin => Good
* XP boot
> Is this the correct summary of the problem
> scenarios.
> Assume each one starts from cold boot (power off).
>
> * 2.6.13(skge) boot=> Good
> * 2.6.13(sk98lin) boot => Good
> * 2.6.13 + SK version of sk98lin => Good
> * XP boot
On Tue, 30 Aug 2005 12:54:31 +0100
Daniel Drake <[EMAIL PROTECTED]> wrote:
> Hi Stephen,
>
> This looks like an issue I reported previously. After you use a recent skge,
> you can't use any older drivers or the windows driver, but skge still works
> fine every time.
>
> http://marc.theai
On Wed, 31 Aug 2005 10:09:48 +1000 (EST)
Steve Kieu <[EMAIL PROTECTED]> wrote:
>
> --- Stephen Hemminger <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 31 Aug 2005 07:49:37 +1000 (EST)
>
> > >
> > > install-8_23.tar.bz2
> >
> > Just look for references to CHIP_REV_YU_LITE_A3 in
> > the driver
> >
Stephen Hemminger wrote:
You have a version of the Marvell Yukon that was affected
by a fix in 2.6.13.
skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
Both the skge and sk98lin driver were fixed to check for this.
Without the fix, the chip will be in the wrong power mode.
The version
--- Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> On Wed, 31 Aug 2005 07:49:37 +1000 (EST)
> >
> > install-8_23.tar.bz2
>
> Just look for references to CHIP_REV_YU_LITE_A3 in
> the driver
> sk98lin/skgeinit.c and sk98lin/skxmac2.c
> The comparison should always be:
Have a look but no c
On Wed, 31 Aug 2005 07:49:37 +1000 (EST)
Steve Kieu <[EMAIL PROTECTED]> wrote:
>
> --- Stephen Hemminger <[EMAIL PROTECTED]> wrote:
>
> > You have a version of the Marvell Yukon that was
> > affected
> > by a fix in 2.6.13.
> > skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
> >
> > Both
--- Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> You have a version of the Marvell Yukon that was
> affected
> by a fix in 2.6.13.
> skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
>
> Both the skge and sk98lin driver were fixed to check
> for this.
> Without the fix, the chip will be
You have a version of the Marvell Yukon that was affected
by a fix in 2.6.13.
skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
Both the skge and sk98lin driver were fixed to check for this.
Without the fix, the chip will be in the wrong power mode.
The version of sk98lin driver from SysK
Ok, I reproduce the problem and attached several lspci
log here
--- Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> On Tue, 30 Aug 2005 13:18:57 -0700
> Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
>
> > on 2.6.11/12 when it isn't working maybe you
> should send us the output
> > of lspci -vvv
>
On Tue, 30 Aug 2005 13:18:57 -0700
Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
> on 2.6.11/12 when it isn't working maybe you should send us the output
> of lspci -vvv
>
> just a hint, I'm guessing its power management related, and / or
> something to do with the pci bus code.
Also, the dmesg ou
on 2.6.11/12 when it isn't working maybe you should send us the output
of lspci -vvv
just a hint, I'm guessing its power management related, and / or
something to do with the pci bus code.
On 8/30/05, Daniel Drake <[EMAIL PROTECTED]> wrote:
> Forwarding on, please reply-to-all in future.
>
> Ste
Forwarding on, please reply-to-all in future.
Steve Kieu wrote:
Hi all,
I have "fixed" the problem in a very wierd way.Reading
your post I thought maybe when removing the driver
itself it set some bit incorrectly. Then I decided to
do:
Boot with init=/bin/bash so bypass all other things.
modp
Hi all,
I have "fixed" the problem in a very wierd way.Reading
your post I thought maybe when removing the driver
itself it set some bit incorrectly. Then I decided to
do:
Boot with init=/bin/bash so bypass all other things.
modprobe skge
run ifconfig eth0 ip_num up
ping a host
then while
Hi Stephen,
This looks like an issue I reported previously. After you use a recent skge,
you can't use any older drivers or the windows driver, but skge still works
fine every time.
http://marc.theaimsgroup.com/?l=linux-netdev&m=112268414417743&w=2
The Gentoo bug report is here:
> Can you test the new skge driver instead? If that
> one is broken then we
Tested , not broken, working now but the same problem,
that is if I reboot to winXP or 2.6.12, 2.6.11, the
NIC is unusaeble. In XP it always says link is down,
or media disconnected (from ipconfig command output in
XP)
i
Just select and doing make now, let u know very soon
thanks
--- Daniel Drake <[EMAIL PROTECTED]> wrote:
> Steve Kieu wrote:
> >>Are you using skge or sk98lin?
> >
> >
> > sk98lin
> >
> > thanks
>
> Can you test the new skge driver instead? If that
> one is broken then we
> probably have mor
Steve Kieu wrote:
Are you using skge or sk98lin?
sk98lin
thanks
Can you test the new skge driver instead? If that one is broken then we
probably have more chance of getting it fixed :)
Thanks,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
>
> Are you using skge or sk98lin?
sk98lin
thanks
>
> > It is working as normal with 2.6.12 and winXP
> before.
> > Today I did upgrade the kernel to 2.6.13 and it
> still
> > works. The problem is now I switch to the older
> kernel
> > that is 2.6.12.5 and .6 it no longer works. dmesg
> > sh
Steve Kieu wrote:
Ok it sound wierd enough to assume that the latest
kernel 2.6.13 ethernet driver has done something wrong
with the NIC and sustain the condition after reboot or
turn off the machine.
Here is my configuration.
Laptop Asus A4500d. dmesg shows:
eth0: Yukon Gigabit Ethernet 10/10
20 matches
Mail list logo
