Re: [D-I] Network driver question - how to recognize sunqe
Attached is prtconf output from an SS1000 system. This is from
DaveM's older vger prtconf CVS repo, which I find very useful. It
concurs "qec" would provide a root device node for a QE device.
Thanks,
E
On 3/16/06, Frans Pop <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Both Debian Installer and discover currently attempt to install the sunqe
> driver for SUNW,qfe sbus devices. From an installation report [1] it
> looks very much like this is incorrect.
>
> Current detection is based on this line in the hw-setup component of d-i:
> SUNW,qfe:SunQuad SBus Ethernet:sunqe
>
> I've taken a look at some kernel module code and it looks like the correct
> driver for the NICs themselves is sunhme. From sunhme.c:
> for_each_sbus(sbus) {
> for_each_sbusdev(sdev, sbus) {
> char *name = sdev->prom_name;
>
> if (!strcmp(name, "SUNW,hme")) {
> cards++;
> prom_getstring(sdev->prom_node, "model",
>model, sizeof(model));
> if (!strcmp(model, "SUNW,sbus-qfe"))
> happy_meal_sbus_init(sdev, 1);
> else
> happy_meal_sbus_init(sdev, 0);
> } else if (!strcmp(name, "qfe") ||
>!strcmp(name, "SUNW,qfe")) {
> cards++;
> happy_meal_sbus_init(sdev, 1);
> }
> }
> }
>
> This is supported by this comment from sunqe.c:
>/* QEC can be parent of either QuadEthernet or BigMAC
> * children. Do not confuse this with qfe/SUNW,qfe
> * which is a quad-happymeal card and handled by
> * a different driver.
> */
>
> The question that remains is: how can we recognize when the sunqe driver
> should be loaded (and do we need to at all)?
> This bit from sunqe.c suggests looking for the string "qec":
> if (strcmp(sdev->prom_name, "qec") != 0)
> return 0;
>
> Can someone confirm this?
> If someone has a system that uses the sunqe driver, please post the output
> of 'prtconf'.
>
> Cheers,
> FJP
>
> P.S. I've changed the indentation of the code snippets a bit.
>
> [1] http://bugs.debian.org/306476
>
>
>
--
E
ss1000
Description: Binary data
Re: [D-I] Network driver question - how to recognize sunqe
Here they are: Version: Linux version 2.4.27-2-sparc64-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Mon Aug 22 18:22:32 UTC 2005 cat /proc/cpuinfo cpu : TI UltraSparc I (SpitFire) fpu : UltraSparc I integrated FPU promlib : Version 3 Revision 1 prom: 3.1.5 type: sun4u ncpus probed: 2 ncpus active: 2 Cpu0Bogo: 398.95 Cpu0ClkTck : 0bebc200 Cpu1Bogo: 399.76 Cpu1ClkTck : 0bebc200 MMU Type: Spitfire State: CPU0: online CPU1: online lsmod: Module Size Used byNot tainted sunqe 10432 0 (unused) ip_nat_irc 2952 0 (unused) ip_nat_ftp 3704 0 (unused) ip_conntrack_irc3288 1 [ip_nat_irc] ip_conntrack_ftp4504 1 [ip_nat_ftp] ipt_LOG 3865 4 (autoclean) iptable_mangle 2496 0 (autoclean) (unused) iptable_filter 2024 1 (autoclean) iptable_nat19832 2 [ip_nat_irc ip_nat_ftp] ip_tables 15872 6 [ipt_LOG iptable_mangle iptable_filter iptable_nat] ip_conntrack 25444 2 [ip_nat_irc ip_nat_ftp ip_conntrack_irc ip_conntrack_ftp iptable_nat] sunhme 25992 1 crc32 3504 0 [sunqe sunhme] sr_mod 16644 0 (unused) cdrom 29184 0 [sr_mod] reiserfs 283400 2 (autoclean) sd_mod 12816 8 (autoclean) esp33312 4 (autoclean) scsi_mod 99232 3 (autoclean) [sr_mod sd_mod esp] And prtconf: System Configuration: Sun Microsystems sun4u Memory size: 512 Megabytes System Peripherals (Software Nodes): SUNW,Ultra-2 packages (driver probably installed) terminal-emulator (driver probably installed) deblocker (driver probably installed) obp-tftp (driver probably installed) disk-label (driver probably installed) chosen (driver probably installed) openprom (driver probably installed) client-services (driver probably installed) options (driver probably installed) aliases (driver probably installed) memory (driver probably installed) virtual-memory (driver probably installed) counter-timer (driver probably installed) sbus (driver probably installed) SUNW,CS4231 (driver probably installed) auxio (driver probably installed) flashprom (driver probably installed) SUNW,fdtwo (driver probably installed) eeprom (driver probably installed) zs (driver probably installed) zs (driver probably installed) sc (driver probably installed) SUNW,pll (driver probably installed) SUNW,fas (driver probably installed) sd (driver probably installed) st (driver probably installed) SUNW,hme (driver probably installed) SUNW,bpp (driver probably installed) qec (driver probably installed) qe (driver probably installed) qe (driver probably installed) qe (driver probably installed) qe (driver probably installed) qec (driver probably installed) qe (driver probably installed) qe (driver probably installed) qe (driver probably installed) qe (driver probably installed) SUNW,UltraSPARC (driver probably installed) SUNW,UltraSPARC (driver probably installed) SUNW,ffb (driver probably installed) Hope this helps Chris Brandstetter -Begin Geek Code GCS d+ s++:++ a- C U+++ L+++ P+++ E--- W+++ o K- w-- O M V PS PE Y+ PGP++ t++ 5+++ X++ R+ tv b++ DI+ D+ G e+ h++ r-- z? --End Geek Code--- To Decode:http://www.ebb.org/ungeek/
[D-I] Network driver question - how to recognize sunqe
Hi all,
Both Debian Installer and discover currently attempt to install the sunqe
driver for SUNW,qfe sbus devices. From an installation report [1] it
looks very much like this is incorrect.
Current detection is based on this line in the hw-setup component of d-i:
SUNW,qfe:SunQuad SBus Ethernet:sunqe
I've taken a look at some kernel module code and it looks like the correct
driver for the NICs themselves is sunhme. From sunhme.c:
for_each_sbus(sbus) {
for_each_sbusdev(sdev, sbus) {
char *name = sdev->prom_name;
if (!strcmp(name, "SUNW,hme")) {
cards++;
prom_getstring(sdev->prom_node, "model",
model, sizeof(model));
if (!strcmp(model, "SUNW,sbus-qfe"))
happy_meal_sbus_init(sdev, 1);
else
happy_meal_sbus_init(sdev, 0);
} else if (!strcmp(name, "qfe") ||
!strcmp(name, "SUNW,qfe")) {
cards++;
happy_meal_sbus_init(sdev, 1);
}
}
}
This is supported by this comment from sunqe.c:
/* QEC can be parent of either QuadEthernet or BigMAC
* children. Do not confuse this with qfe/SUNW,qfe
* which is a quad-happymeal card and handled by
* a different driver.
*/
The question that remains is: how can we recognize when the sunqe driver
should be loaded (and do we need to at all)?
This bit from sunqe.c suggests looking for the string "qec":
if (strcmp(sdev->prom_name, "qec") != 0)
return 0;
Can someone confirm this?
If someone has a system that uses the sunqe driver, please post the output
of 'prtconf'.
Cheers,
FJP
P.S. I've changed the indentation of the code snippets a bit.
[1] http://bugs.debian.org/306476
pgpKKqDyQSzgx.pgp
Description: PGP signature
Re: Sun Enterprise 4000 insmod problem
Chris Brandstetter wrote: Dear All, I have a Sun Enterprise 4000 (e4000, e4K) that I am trying to get Debian Sarge to run on. Now I installed debian on the hard drive using a SS2 Dual Proc so that it would install the smp kernel. I did a base install and only added a couple things like Kernel Source and Tree. It boot's fine, but won't allow me to insmod the sunhme or any net driver as it gives this error unresolved symbol in $driver crc32_le_Rsmp_92ea4ae4. It is running the generic 2.4.27-2-sparc64-smp. Version gives me "Debian 1:3.3.5-13". The config of the e4K is 6 processors (It's kinda col having six penguins at the top of the boot screen :-) ) and 3GB Ram over 3 Mainboards. There are two SBUS boards, and it is the 66MHz backplane and clockboard. I have 2 Disk boards but they are not installed. Any help would be appreciated. Try the sunlance driver. Early E4000 systems had le ether ports, later models had hme. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sun Enterprise 4000 insmod problem
Dear All, I have a Sun Enterprise 4000 (e4000, e4K) that I am trying to get Debian Sarge to run on. Now I installed debian on the hard drive using a SS2 Dual Proc so that it would install the smp kernel. I did a base install and only added a couple things like Kernel Source and Tree. It boot's fine, but won't allow me to insmod the sunhme or any net driver as it gives this error unresolved symbol in $driver crc32_le_Rsmp_92ea4ae4. It is running the generic 2.4.27-2-sparc64-smp. Version gives me "Debian 1:3.3.5-13". The config of the e4K is 6 processors (It's kinda col having six penguins at the top of the boot screen :-) ) and 3GB Ram over 3 Mainboards. There are two SBUS boards, and it is the 66MHz backplane and clockboard. I have 2 Disk boards but they are not installed. Any help would be appreciated. -- Chris Brandstetter -Begin Geek Code GCS d+ s++:++ a- C U+++ L+++ P+++ E--- W+++ o K- w-- O M V PS PE Y+ PGP++ t++ 5+++ X++ R+ tv b++ DI+ D+ G e+ h++ r-- z? --End Geek Code--- To Decode:http://www.ebb.org/ungeek/
