headers
Zyman, Andy | 31 Jul 2003 19:53

simple question

Hello,
I'm trying to figure out why my SMC wireless card is not working.

so far this is my finding ( I should say I'm totally new to this , including
Linux ).
1. Cardbus cards are not handled by PCMCIA package ( kernel 2.4.18-14,
pcmcia 3.1.31 )
2. At the same time pcmcia is needed to be in the memory for hotplug events
to be recognized by kernel.

 Please any comment on this

3. Cardbus network cards ( ethernet and wireless ) trigger the pci.agent
with ethX parameter and <REGISTER> event.
	this basically calls ifup ethX 
	
Now why it calls ETHx, not wlan interface?

Any help even hammering my head against the wall - will help.

Thank You
 Andy

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
Permalink | Reply | 4 comments |
headers
Joshua Schmidlkofer | 31 Jul 2003 23:26

Re: simple question

On Thu, 2003-07-31 at 10:53, Zyman, Andy wrote:
> Hello,
> I'm trying to figure out why my SMC wireless card is not working.
> 
> so far this is my finding ( I should say I'm totally new to this , including
> Linux ).
> 1. Cardbus cards are not handled by PCMCIA package ( kernel 2.4.18-14,
> pcmcia 3.1.31 )
> 2. At the same time pcmcia is needed to be in the memory for hotplug events
> to be recognized by kernel.
> 
>  Please any comment on this
> 
> 3. Cardbus network cards ( ethernet and wireless ) trigger the pci.agent
> with ethX parameter and <REGISTER> event.
> 	this basically calls ifup ethX 
> 	
> Now why it calls ETHx, not wlan interface?
> 
> Any help even hammering my head against the wall - will help.
> 
> Thank You
>  Andy
> 

I had the same problem, but in my case I was using a kernel w/o the
wireless extentions enabled, thus all my wifi card were coming through
as ethX.   Don't know if that helps.

thanks,
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Hinds | 31 Jul 2003 21:14
Favicon

Re: simple question

On Thu, Jul 31, 2003 at 01:53:05PM -0400, Zyman, Andy wrote:
> Hello,
> I'm trying to figure out why my SMC wireless card is not working.

What model card, specifically?

> 1. Cardbus cards are not handled by PCMCIA package ( kernel 2.4.18-14,
> pcmcia 3.1.31 )

Cardbus cards are not managed by the kernel PCMCIA subsystem.  Some of
their setup is done by the PCMCIA subsystem, but then they are handed
off to the hotplug system.

> 2. At the same time pcmcia is needed to be in the memory for hotplug
> events to be recognized by kernel.

Err not exactly.  The PCMCIA subsystem is needed to handle setup of
the CardBus bridge device.  The hotplug subsystem is a separate and
independent part of the kernel, and generates hotplug events.  Both
are needed for a Cardbus card to be set up properly.

> 3. Cardbus network cards ( ethernet and wireless ) trigger the pci.agent
> with ethX parameter and <REGISTER> event.
> 	this basically calls ifup ethX 
> 	
> Now why it calls ETHx, not wlan interface?

Most wireless drivers call their devices ETHx too.  The "ifup" will be
for whatever the device is actually named.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Zyman, Andy | 31 Jul 2003 22:41

RE: simple question

Dave,
thank you for response.

> On Thu, Jul 31, 2003 at 01:53:05PM -0400, Zyman, Andy wrote:
> > Hello,
> > I'm trying to figure out why my SMC wireless card is not working.
> What model card, specifically?

SMC2635W. I recently got drivers for it from SMC. And now trying to figure
how to make it work.

<skip>

> > 3. Cardbus network cards ( ethernet and wireless ) trigger 
> the pci.agent
> > with ethX parameter and <REGISTER> event.
> > 	this basically calls ifup ethX 
> > 	
> > Now why it calls ETHx, not wlan interface?
> 
> Most wireless drivers call their devices ETHx too.  The "ifup" will be
> for whatever the device is actually named.

tha nkyou again for explanation. Now is it possible to create ( and store )
different profiles so, for example, on work I'll have this card with this
params and at home the same card with diff. set?

> Perhaps you should describe your problem more specifically (i.e., show
> all relevant system log messages), then we can decide if this is the
> appropriate forum for your question.
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Hinds | 31 Jul 2003 22:59
Favicon

Re: simple question

On Thu, Jul 31, 2003 at 04:41:59PM -0400, Zyman, Andy wrote:
>
> > What model card, specifically?
> 
> SMC2635W. I recently got drivers for it from SMC. And now trying to figure
> how to make it work.
> 
> thank you again for explanation. Now is it possible to create ( and
> store ) different profiles so, for example, on work I'll have this
> card with this params and at home the same card with diff. set?

This is a general network configuration question, not a hotplug
question, and is beyond the scope of this forum.  Perhaps your Linux
distribution provides tools for managing network profiles.

> the major problem for me right now is that card starting scanning
> channels are crazy and .... I'll better give you an url, so you will
> have the logs and full description.
> http://www.linuxquestions.org/questions/showthread.php?s=&threadid=76818&hig
> hlight=ADM811

This is also not a hotplug problem; the appropriate driver got loaded
(i.e. hotplug did its job).  Your problem is specific to this wireless
driver and you'll have to either report the problem to SMC since
that's where you got the driver, or try to find someone on a wireless
forum who knows more about this driver.

> So it seems that wireless parameters are default... And this is not
> what i want. So i guess i need to figure out how to change ( and
> first of all why it is not taking /etc/pcmcia/wirelss.opt ?) the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marcel Holtmann | 26 Jul 2003 18:24

Hotplug script firmware.agent

Hi Folks,

here is my firmware.agent script and it would be nice, if you include it
into the next release of the hotplug scripts.

Regards

Marcel
Attachment (firmware.agent): text/x-sh, 1128 bytes
Permalink | Reply | 0 comments |
headers
Greg KH | 25 Jul 2003 23:47
Gravatar

[ANNOUNCE] udev 0.2 release

Hi,

I've released the 0.2 version of udev into the wild, after surviving a
live demo at the 2003 Ottawa Linux Symposium during a presentation.  It
can be found at:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-0.2.tar.gz

udev is a implementation of devfs in userspace using sysfs and
/sbin/hotplug.  It requires a 2.5/2.6 kernel to run properly.  The major
changes since the last release is that persistent device naming schemes
are now implemented.  Yeah, it's pretty rough, but it does prove that
the concept is sane and will end up working well for users.

There's a BitKeeper tree of the latest stuff available at:
	bk://kernel.bkbits.net/gregkh/udev/

I've also placed the slides from my OLS talk up at:
	http://www.kroah.com/linux/talks/ols_2003_udev_talk/

The paper which attempts to explain the background of udev, what it
does, and where it is going is at:
	http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Kroah-Hartman-OLS2003.pdf

Due to the rush of the development of udev in this past week (hacking at
it during the conference in an attempt to have something to show) there
are still a number of very rough corners present, a few known memory
leaks, and at least one hard coded path to my home directory for a
config file...  Please feel free to take it for a spin to see how well
things are progressing.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guo, Min | 31 Jul 2003 09:47
Picon
Favicon

RE: [ANNOUNCE] udev 0.2 release

Simple patch for udev mknod.

Thanks
Guo Min 
The content of this email message solely contains my own personal views,
and not those of my employer.

-----------------------------------------------------------------------------------------------------------------
--- /root/udev-0.2/udev-add.c	2003-07-24 23:54:49.000000000 +0800
+++ udev/udev-add.c	2003-07-31 16:35:14.277998152 +0800
 <at>  <at>  -81,35 +81,26  <at>  <at> 
  */
 static int create_node(char *name, char type, int major, int minor, int mode)
 {
-	char *argv[7];
-	char mode_string[100];
-	char type_string[3];
-	char major_string[20];
-	char minor_string[20];
 	char filename[255];
 	int retval = 0;

 	strncpy(filename, UDEV_ROOT, sizeof(filename));
 	strncat(filename, name, sizeof(filename));
+	if (type == 'b') {
+	       mode |= S_IFBLK;
+    	} else if ((type == 'c') || (type == 'u')){
+	        mode |= S_IFCHR;
+    	} else if ( type == 'p') {
+       		 mode |= S_IFIFO;
(Continue reading)

Permalink | Reply | 1 comment |
headers
Guo, Min | 31 Jul 2003 09:46
Picon
Favicon

RE: [ANNOUNCE] udev 0.2 release

Simple patch for udev mknod.

Thanks
Guo Min 
The content of this email message solely contains my own personal views,
and not those of my employer.

-----------------------------------------------------------------------------------------------------------------
--- /root/udev-0.2/udev-add.c	2003-07-24 23:54:49.000000000 +0800
+++ udev/udev-add.c	2003-07-31 16:35:14.277998152 +0800
 <at>  <at>  -81,35 +81,26  <at>  <at> 
  */
 static int create_node(char *name, char type, int major, int minor, int mode)
 {
-	char *argv[7];
-	char mode_string[100];
-	char type_string[3];
-	char major_string[20];
-	char minor_string[20];
 	char filename[255];
 	int retval = 0;

 	strncpy(filename, UDEV_ROOT, sizeof(filename));
 	strncat(filename, name, sizeof(filename));
+	if (type == 'b') {
+	       mode |= S_IFBLK;
+    	} else if ((type == 'c') || (type == 'u')){
+	        mode |= S_IFCHR;
+    	} else if ( type == 'p') {
+       		 mode |= S_IFIFO;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joshua Schmidlkofer | 26 Jul 2003 02:18

Re: [ANNOUNCE] udev 0.2 release

On Fri, 2003-07-25 at 14:47, Greg KH wrote:
> Hi,
> 
> I've released the 0.2 version of udev into the wild, after surviving a
> live demo at the 2003 Ottawa Linux Symposium during a presentation.  It
> can be found at:
> 	kernel.org/pub/linux/utils/kernel/hotplug/udev-0.2.tar.gz
> 
> udev is a implementation of devfs in userspace using sysfs and
> /sbin/hotplug.  It requires a 2.5/2.6 kernel to run properly.  The major
> changes since the last release is that persistent device naming schemes
> are now implemented.  Yeah, it's pretty rough, but it does prove that
> the concept is sane and will end up working well for users.
> 
> There's a BitKeeper tree of the latest stuff available at:
> 	bk://kernel.bkbits.net/gregkh/udev/
> 
> I've also placed the slides from my OLS talk up at:
> 	http://www.kroah.com/linux/talks/ols_2003_udev_talk/
> 
> The paper which attempts to explain the background of udev, what it
> does, and where it is going is at:
> 	http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Kroah-Hartman-OLS2003.pdf
> 
> 
> Due to the rush of the development of udev in this past week (hacking at
> it during the conference in an attempt to have something to show) there
> are still a number of very rough corners present, a few known memory
> leaks, and at least one hard coded path to my home directory for a
> config file...  Please feel free to take it for a spin to see how well
(Continue reading)

Permalink | Reply | 1 comment |

Gmane