simple question

simple question

[Zyman, Andy]

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
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: simple question

[David Hinds]

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.

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.

-- Dave


-------------------------------------------------------
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
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: simple question

[Zyman, Andy]

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.

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=&threadidv818&hig
hlight­M811

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 default params on it. 


I played with pcmcia - no results, so now I'm here and hope to get at least
some idea where should i look next.



-------------------------------------------------------
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
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: simple question

[David Hinds]

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=&threadidv818&hig
> hlight­M811

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
> default params on it.

/etc/pcmcia/wireless.opts won't get used for Cardbus cards since they
are managed by the hotplug scripts.  Some distributions' network setup
tools are wireless-networking-aware and would allow you to set these
sorts of parameters so that when hotplug does "ifup eth0" the right
stuff gets done.

I suggest that you take your questions to a wireless networking list.

-- Dave


-------------------------------------------------------
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
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: simple question

[Joshua Schmidlkofer]

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,
  joshua





-------------------------------------------------------
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
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

simple question

[Niv]

Hay,

I read the udev HOWTO and I still dont understand why /dev/cdrom get a 
root:root permision.


I switched to RC_DEVICE_TARBALL="no" - so I guess I am a udev "pureist"


the line in /etc/udev/rules/50-udev.rules say:


# cdrom symlinks and other good cdrom naming

BUS="ide",    KERNEL="hd[a-z]", ACTION="add", IMPORT="/sbin/cdrom_id 
--export $tempnode"
BUS="scsi",    KERNEL="sr[0-9]*", ACTION="add", IMPORT="/sbin/cdrom_id 
--export $tempnode"
BUS="scsi",    KERNEL="scd[a-z]", ACTION="add", IMPORT="/sbin/cdrom_id 
--export $tempnode"
BUS="scsi",    KERNEL="sg[0-9]*", ACTION="add", DRIVER="sr", 
GROUP="cdrom"


#---  look here --


ENV{ID_CDROM}="?*",        SYMLINK+="cdrom%e", GROUP="cdrom"

ENV{ID_CDROM_CD_RW}="?*",    SYMLINK+="cdrw%e"
ENV{ID_CDROM_DVD}="?*",    SYMLINK+="dvd%e"
ENV{ID_CDROM_DVD_R}="?*",    SYMLINK+="dvdrw%e"


so I see GROUP="cdrom" - so It should be root:cdrom - right?


Niv




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: simple question

[Greg KH]

On Sun, Feb 19, 2006 at 02:12:42AM +0200, Niv wrote:
> Hay,
> 
> I read the udev HOWTO and I still dont understand why /dev/cdrom get a 
> root:root permision.
> 
> 
> I switched to RC_DEVICE_TARBALL="no" - so I guess I am a udev "pureist"

I'm guessing that you are using gentoo?

If so, please file a bug in their bugzilla, as this is a distro specific
thing.

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: simple question

[Mark Rosenstand]

On 2/19/06, Niv <nivv@cs.bgu.ac.il> wrote:
> so I see GROUP="cdrom" - so It should be root:cdrom - right?

Are you sure you have a cdrom group?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: simple question

[Niv]

$ fgrep cdrom /etc/group
cdrom:x:19:haldaemon,mythtv,niv

Mark Rosenstand wrote:

>On 2/19/06, Niv <nivv@cs.bgu.ac.il> wrote:
>  
>
>>so I see GROUP="cdrom" - so It should be root:cdrom - right?
>>    
>>
>
>Are you sure you have a cdrom group?
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd_______________________________________________
>Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
>Linux-hotplug-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel