* Randall R Schulz [Oct 15. 2006 18:18]: [...]

By poking around http://www.kernel.org/ I discovered a very simple change to sky2.c in Linux kernel 2.6.19 (-rc2) that enables support for the 88E8056 as it is identified in current Asus P5B mainboards (and, probably, others, as well):

[...]

+ { PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x4364) },

If its just an additional PCI id, this can be passed to the driver at runtime. IIRC, there is even a YaST dialog for this. Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

* Randall R Schulz [2006-10-16 15:18]:

...

this can be passed to the driver at runtime.

How is that done? I haven't been able to find a comprehensive specification or list of kernel command-line options. Or do you mean it can be done even after the system is running?

If the driver isn't specially prepared (i.e. module paremeters), it cannot. Even if it is, the driver needs to be loaded manually.

...

IIRC, there is even a YaST dialog for this.

Really? Do you know how or where this is done? I thought I'd been through the whole thing (at least everything relevant to networking), but I must have overlooked that one.

I think there's no YaST dialog. It would be a driver specific issue. Bernhard -- "Was wir wissen, ist ein Tropfen; was wir nicht wissen, ein Ozean." -- Isaac Newton

Hello, * Carl-Daniel Hailfinger [2006-10-16 16:33]:

Bernhard Walle wrote:

...

* Randall R Schulz [2006-10-16 15:18]:

...

...

this can be passed to the driver at runtime. How is that done? I haven't been able to find a comprehensive specification or list of kernel command-line options. Or do you mean it can be done even after the system is running?

If the driver isn't specially prepared (i.e. module paremeters), it cannot.

No. See new_id in sysfs once the driver is loaded.

Which kerenl introduced this? On 2.6.16 it's not present. Bernhard -- "Bei der Eroberung des Weltraums sind zwei Probleme zu lösen: die Schwerkraft und der Papierkrieg. Mit der Schwerkraft wären wir fertig geworden." -- Wernher von Braun

* Carl-Daniel Hailfinger [2006-10-16 17:03]:

Bernhard Walle wrote:

...

Hello,

* Carl-Daniel Hailfinger [2006-10-16 16:33]:

...

Bernhard Walle wrote:

...

* Randall R Schulz [2006-10-16 15:18]:

...

...

this can be passed to the driver at runtime. How is that done? I haven't been able to find a comprehensive specification or list of kernel command-line options. Or do you mean it can be done even after the system is running? If the driver isn't specially prepared (i.e. module paremeters), it cannot. No. See new_id in sysfs once the driver is loaded.

Which kerenl introduced this? On 2.6.16 it's not present.

For your enlightenment: # find /sys/ -name new_id

Oh, sorry, I only searched in the /sys/devices tree.

The feature is in all kernels since at least 2.6.8 (SUSE Linux 9.2), maybe even before that.

Thanks. Bernhard -- F: Wie viele Microsoft-Leute braucht man um eine Glühbirne zu wechseln? A: Vier. Der erste ersetzt die Birne, der zweite ändert die Fassung, so dass Netscape-Glübirnen nicht reinpassen. Der dritte baut eine Kurzschlussautomatik ein, die ausgelöst wird, wenn jemand eine Glühbirne von Sun einsetzen will. Und der vierte überzeugt das amerikanische Justizministerium, dass das alles fairer Wettbewerb ist.

Juan, On Monday 16 October 2006 10:09, Juan Erbes wrote:

You has the Ethernet controller enabled in the bios? ...

I have much more than that... Now. I just applied the patch to the sky2.c driver code and rebuilt my kernel modules. Now I have two active Ethernet controllers, one for the wild Internet and one for my internal network. However, I have not been able to find the details of how to use the new_id files in /sys/bus/... If anyone can point me to that, I'd like to possess the knowledge. Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Monday 16 October 2006 10:27, Juan Erbes wrote:

2006/10/16, Randall R Schulz :

...

Juan,

On Monday 16 October 2006 10:09, Juan Erbes wrote:

...

You has the Ethernet controller enabled in the bios? ...

I have much more than that... Now.

I just applied the patch to the sky2.c driver code and rebuilt my kernel modules. Now I have two active Ethernet controllers, one for the wild Internet and one for my internal network.

...

My ethernet module driver is sk98lin. My ethernet chip is 3com3C940

sk98lin is blacklisted! Check in "/etc/modprobe.d/blacklist". But upon initial installation, that's the driver that was selected for my other Ethernet controller, a Marvell 88E8001, which rendered it inoperable.

It appears that You has other chip.

Yes. The subject of this thread does make it explicit... RRS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org