Re: Request for help

Re: Request for help

[Eric W. Biederman]

I am CC'ing linux-kernel as that is the general kernel list.  There
may be something even more focused on IDE issues but I am
not aware of it.

"ganesh_borse" <ganesh_borse@indiatimes.com> writes:

> Hi,
> 
> 
> I would like to request for a little help related to IDE controllers.
> 
> 
> I am trying to develop a device drive code for listing the devices connected to
> a ide controller at the time of kernel booting.
> 
> 
> 
> Is there any way to get which channels on ide controller has got devices and
> which devices? 

Yes.  But it is baroque.

> This I am trying to get even before the normal ide device driver
> has been setup. Are there ide controller commands to get this info? 

Not exactly.  The method is essentially you ping the drives to see
if they are there.

> Or is this
> info stored in registers of ide-controllers? 

Nope this information is not stored in registers.

> For this do we need to write
> assembly instructions on linux?

No.

But there is also nothing that allows you to force the module
order within the kernel.  So there are no guarantees you will
come before a normal IDE driver.  I assume from the questions
you intend to have this working in the linux kernel.

Eric

Re: Request for help

[Andy Pfiffer]

[-- Attachment #1: Type: text/plain, Size: 2802 bytes --]

On Mon, 2003-06-02 at 10:49, Eric W. Biederman wrote:
> "ganesh_borse" <ganesh_borse@indiatimes.com> writes:
...
> > I am trying to develop a device drive code for listing the devices connected to
> > a ide controller at the time of kernel booting.
...
> > Is there any way to get which channels on ide controller has got devices and
> > which devices? 
> 
> Yes.  But it is baroque.
> 
> > This I am trying to get even before the normal ide device driver
> > has been setup. Are there ide controller commands to get this info?

If you can wait until *after* the system has booted, there are lots of
ways to derive what is out there.  Grab the sources for "hdparm" and
have a look at it for examples of hardcore access methods.

A simple way to derive some information can be found by walking the
sysfs hierarchy.

Here's a dirt-simple script I use that somewhat-pretty-prints items
hanging off busses in the sysfs hierarchy.  Sysfs must be mounted for
the script to work.

Sample output:
% lsbus
ide:
  pci0/00:1f.1/ide1/1.0 [ IDE Drive ]
  pci0/00:1f.1/ide0/0.1 [ IDE Drive ]
  pci0/00:1f.1/ide0/0.0 [ IDE Drive ]

ide-scsi:

pci:
  pci0/00:1e.0/04:04.0 [ Intel Corp. 82557/8/9 [Ethernet  ]
  pci0/00:02.0/02:1f.0/03:00.0 [ Intel Corp. 82806AA PCI64 Hub Ad ]
  pci0/00:02.0/02:1f.0 [ Intel Corp. 82806AA PCI64 Hub PC ]
  pci0/00:01.0/01:00.0 [ Matrox Graphics, Inc MGA G400 AGP ]
  pci0/00:1f.5 [ Intel Corp. 82801BA/BAM AC'97 Au ]
  pci0/00:1f.3 [ Intel Corp. 82801BA/BAM SMBus ]
  pci0/00:1f.2 [ Intel Corp. 82801BA/BAM USB (Hub ]
  pci0/00:1f.1 [ Intel Corp. 82801BA IDE U100 ]
  pci0/00:1f.0 [ Intel Corp. 82801BA ISA Bridge ( ]
  pci0/00:1e.0 [ Intel Corp. 82801BA/CA/DB PCI Br ]
  pci0/00:02.0 [ Intel Corp. 82860 860 (Wombat) C ]
  pci0/00:01.0 [ Intel Corp. 82850 850 (Tehama) C ]
  pci0/00:00.0 [ Intel Corp. 82860 860 (Wombat) C ]

platform:
  legacy/floppy0 [ Floppy Drive ]

pnp:
  pnp0/00:10 [ 16550A-compatible COM port ]
  pnp0/00:0f [ ECP printer port ]
  pnp0/00:0d [ PC standard floppy disk controller ]
  pnp0/00:0c [ 16550A-compatible COM port ]
  pnp0/00:0b [ PS/2 Port for PS/2-style Mice ]
  pnp0/00:0a [ PCI Bus ]
  pnp0/00:09 [ Reserved Motherboard Resources ]
  pnp0/00:08 [ System Board ]
  pnp0/00:07 [  ]
  pnp0/00:06 [ Math Coprocessor ]
  pnp0/00:05 [ AT-style speaker sound ]
  pnp0/00:04 [ IBM Enhanced (101/102-key, PS/2 mouse support) ]
  pnp0/00:03 [ AT Real-Time Clock ]
  pnp0/00:02 [ AT Timer ]
  pnp0/00:01 [ AT DMA Controller ]
  pnp0/00:00 [ AT Interrupt Controller ]

scsi:

system:
  sys/rtc0 [ i8253 Real Time Clock ]
  sys/timer0 [ timer ]
  sys/pic0 [ i8259A PIC ]
  sys/cpu1 [ CPU 1 ]
  sys/cpu0 [ CPU 0 ]

usb:
  pci0/00:1f.2/usb1/1-0:0 [ Hub ]
  pci0/00:1f.2/usb1 [ Intel Corp. 82801BA/BAM USB (Hub (Linux 2.5.70 uh
]
%

The script is attached...




[-- Attachment #2: Type: text/x-sh, Size: 729 bytes --]

#!/bin/sh

#
#	$Id$
#
#	andyp@osdl.org
#

mnt=`grep sysfs /proc/mounts | awk '{print $2}'`
cd $mnt

if [ $# = 0 ]; then
	cd ./bus
	buslist=`echo *`
	cd ..
else
	buslist="$*"
	cd ./bus
	for bus in $buslist; do
		if [ ! -d $bus ]; then
			echo "$bus: unknown bus"
			exit 1
		fi
	done
	cd ..
fi

for bus in $buslist; do
	cd ./bus
	if [ -d $bus ]; then
		echo "$bus:"
		cd $bus
		if [ -d ./devices ]; then
			cd ./devices
			devs=`find . -type l -printf "%l\n"`
			for dev in $devs; do
				name=""
				if [ -d $dev ]; then
					if [ -f $dev/name ]; then
						name=`cat $dev/name`
					fi
				fi
				terse=`echo $dev|sed -e 's/\.\.\/.*devices\///'`
				echo "  $terse [ $name ]"
			done
			cd ..
		fi
		cd ..
		echo
	fi
	cd ..
done

request for help

[shashi dhara bhat]

[-- Attachment #1: Type: text/plain, Size: 639 bytes --]

  

 Hellow sir,

        I have downloaded ur xen-2.0 source code and tried to compile
  it in my system. But i received many errors. First the macros in the
  .s files in xen-2.0/xen/arch/x86/boot/x86_32.s are not expanded.Thus it gave the error.
 The same thing happened in xen-2.0/xen/arch/x86/x86_32/entry.s file.
 Then this gave the errors like "undefined reference to do_divide_error" etc. Will u please help me by sending the details of how to solve the problem?

My system configuration is,
   Pentium-4 2.4GHz
   256 MB RAM
 I am waiting for ur mail. Please help me sir.

Thanking you,
Shashidhara Bhat 
      

[-- Attachment #2: Type: text/html, Size: 1012 bytes --]

Request for help...

[Axj]

Hi, I'm alex....

I have a notebook Acer Aspire 5920G, with an intel 4965 wireless, system is a Slackware 12 and kernel is my personal recompiled version of 2.6.21.5. 

Usually I use the drivers of the version 0.0.* with macsubsystem version 8.0.2, but I've tried to compile the version 0.1.2... a lot of compilation problem. So I think to use  mac9.0.2..... 
after the make modules of these it's arrived this message.... 


net/mac80211/wme.c: In function 'ieee80211_ht_agg_queue_add':
net/mac80211/wme.c:759: error: dereferencing pointer to incomplete type
net/mac80211/wme.c: In function 'ieee80211_ht_agg_queue_remove':
net/mac80211/wme.c:784: error: dereferencing pointer to incomplete type
make[2]: *** [net/mac80211/wme.o] Error 1
make[1]: *** [net/mac80211] Error 2
make: *** [net] Error 2


so I can't compile the new version, but, even if the compilation is not finished, when I retried to compile iwl version 0.1.2, it works. Now for me is impossible to  understand, and I'm tring the way to make mac802 subsys work. Can anyone help me....

Another little question... exist a way for make work the wireless led that is always off, even if the wireless works.

Sorry for the request and for the the bad english... it's a lot of time that I don't wrote to a english mailing list (the last was alsa).

Tank you 
Alex

----------------------------------------------------------------------
Get a free email account with anti spam protection.
http://www.bluebottle.com/tag/2

Re: Request for help...

[John W. Linville]

Since Intel continues to develop their mac80211 fork
on their own, you will have to seek support from them at
ipw3945-devel@lists.sourceforge.net.

I keep hearing that Intel intends to come back to working with the
community on mac80211.  Alas, that has yet to happen.  I want to
believe that it will soon...?

John

On Tue, Jul 24, 2007 at 08:02:12AM -0700, Axj wrote:
> Hi, I'm alex....
> 
> I have a notebook Acer Aspire 5920G, with an intel 4965 wireless, system is a Slackware 12 and kernel is my personal recompiled version of 2.6.21.5. 
> 
> Usually I use the drivers of the version 0.0.* with macsubsystem version 8.0.2, but I've tried to compile the version 0.1.2... a lot of compilation problem. So I think to use  mac9.0.2..... 
> after the make modules of these it's arrived this message.... 
> 
> 
> net/mac80211/wme.c: In function 'ieee80211_ht_agg_queue_add':
> net/mac80211/wme.c:759: error: dereferencing pointer to incomplete type
> net/mac80211/wme.c: In function 'ieee80211_ht_agg_queue_remove':
> net/mac80211/wme.c:784: error: dereferencing pointer to incomplete type
> make[2]: *** [net/mac80211/wme.o] Error 1
> make[1]: *** [net/mac80211] Error 2
> make: *** [net] Error 2
> 
> 
> so I can't compile the new version, but, even if the compilation is not finished, when I retried to compile iwl version 0.1.2, it works. Now for me is impossible to  understand, and I'm tring the way to make mac802 subsys work. Can anyone help me....
> 
> Another little question... exist a way for make work the wireless led that is always off, even if the wireless works.
> 
> Sorry for the request and for the the bad english... it's a lot of time that I don't wrote to a english mailing list (the last was alsa).
> 
> Tank you 
> Alex
> 
> ----------------------------------------------------------------------
> Get a free email account with anti spam protection.
> http://www.bluebottle.com/tag/2
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
John W. Linville
linville@tuxdriver.com

Re: Request for help...

[Zhu Yi]

On Tue, 2007-07-24 at 08:02 -0700, Axj wrote:
> so I can't compile the new version, but, even if the compilation is
> not finished, when I retried to compile iwl version 0.1.2, it works.
> Now for me is impossible to  understand, and I'm tring the way to make
> mac802 subsys work. Can anyone help me....

iwlwifi-0.1.3 fixed this problem.

Thanks,
-yi

Re: Request for help...

[Axj]

Quoting Zhu Yi <yi.zhu@intel.com>:

> On Tue, 2007-07-24 at 08:02 -0700, Axj wrote:
> > so I can't compile the new version, but, even if the compilation
> is
> > not finished, when I retried to compile iwl version 0.1.2, it
> works.
> > Now for me is impossible to  understand, and I'm tring the way to
> make
> > mac802 subsys work. Can anyone help me....
> 
> iwlwifi-0.1.3 fixed this problem.
> 
> Thanks,
> -yi
> 

I tried, but peraphs I do someting wrong.... In fact without mac80211-9.0.x is impossibile to compile iwlwifi-0.1.3. But for me I'ts impossible to compile mac-802-9.0.2... give me 2 compile errors when I do "make modules", in the wmc.c. Now, if use the "make patch_kernel" of version of 9.0.2 and compile iwlwifi-0.1.3 it copilke perfect but at the moment to load the module, search a Object that doesn't exist (because if I don't compile the 9.0.2 I have to use 8.0.2). So, if I undestood good, the only way to use the driver version 0.1.x and not the version 0.0.x, is to make work the mac80211 version 9.0.2, and to resolve the compilation problem. It's no so simply like seems to be.

I  saw onother exit of thje driver, 1.0.0, but I don't trust so much (at the momente the compination of mac80211 ver 8.0.2 and iwlwifi-0.0.42 work, even if the led doesn't work ad It's impossible to set an "Ad-Hoc" connection. ) so I would like try a CVS or GIT version of the Mac80211 or newer.... I know that a lot of person think that I have to "learn to fish", but I'm a better systemist, but not a excellent programmer (expecially in kernel space). 

I would like to tel You tank you for the help.... 
I hope that one day I will give you as better answer....

----------------------------------------------------------------------
Finally - A spam blocker that actually works.
http://www.bluebottle.com/tag/4

Re: Request for help...

[Pavel Roskin]

On Thu, 2007-07-26 at 08:10 -0700, Axj wrote:

> I  saw onother exit of thje driver, 1.0.0, but I don't trust so much
> (at the momente the compination of mac80211 ver 8.0.2 and
> iwlwifi-0.0.42 work, even if the led doesn't work ad It's impossible
> to set an "Ad-Hoc" connection. )

Actually, it's direct continuation of the 0.0.x series.  It's
unfortunate that the complexity of the build system makes you mistrust
the recent code, although I can relate.  I hope it will be remedied
quickly.

It's possible to compile the 1.0.x driver against recent unpatched
kernels, even against the standard Fedora 7 kernel, by stripping support
for Intel's rate control algorithm:

diff --git a/origin/Makefile b/origin/Makefile
index 8c0bdc7..c5d966f 100644
--- a/origin/Makefile
+++ b/origin/Makefile
@@ -10,7 +10,7 @@
 # -jpk
 
 obj-$(CONFIG_IWL3945)	+= iwl3945.o
-iwl3945-objs		= base-3945.o iwl-3945.o iwl-3945-rs.o
+iwl3945-objs		= base-3945.o iwl-3945.o
 CFLAGS_iwl-3945.o	= -DIWL=3945
 CFLAGS_iwl-3945-rs.o	= -DIWL=3945
 CFLAGS_base-3945.o	= -DIWL=3945 -D"KBUILD_MODNAME=KBUILD_STR(iwl3945)"
@@ -19,7 +19,7 @@ $(obj)/base-3945.o: $(src)/base.c FORCE
 	$(call if_changed_rule,cc_o_c)
 
 obj-$(CONFIG_IWL4965)	+= iwl4965.o
-iwl4965-objs		= base-4965.o iwl-4965.o iwl-4965-rs.o
+iwl4965-objs		= base-4965.o iwl-4965.o
 CFLAGS_iwl-4965.o	= -DIWL=4965
 CFLAGS_iwl-4965-rs.o	= -DIWL=4965
 CFLAGS_base-4965.o	= -DIWL=4965 -D"KBUILD_MODNAME=KBUILD_STR(iwl4965)"
diff --git a/origin/base.c b/origin/base.c
index eda467e..ee6ac8f 100644
--- a/origin/base.c
+++ b/origin/base.c
@@ -6284,7 +6284,6 @@ static void iwl_alive_start(struct iwl_priv *priv)
 		/* Unlock so any user space entry points can call back into
 		 * the driver without a deadlock... */
 		mutex_unlock(&priv->mutex);
-		iwl_rate_control_register();
 		rc = ieee80211_register_hw(priv->hw);
 		priv->hw->conf.beacon_int = 100;
 		mutex_lock(&priv->mutex);
@@ -6950,7 +6949,6 @@ static void iwl_bg_post_associate(struct work_struct *data)
 				  (priv->phymode == MODE_ATHEROS_TURBO)) ?
 				 IWL_RATE_6M_PLCP : IWL_RATE_1M_PLCP,
 				 CMD_ASYNC);
-		iwl_rate_scale_init(priv->hw, IWL_AP_ID);
 
 		break;
 
@@ -6967,7 +6965,6 @@ static void iwl_bg_post_associate(struct work_struct *data)
 				  (priv->phymode == MODE_ATHEROS_TURBO)) ?
 				 IWL_RATE_6M_PLCP : IWL_RATE_1M_PLCP,
 				 CMD_ASYNC);
-		iwl_rate_scale_init(priv->hw, IWL_STA_ID);
 		iwl_send_beacon_cmd(priv);
 
 		break;
@@ -7915,8 +7912,7 @@ static ssize_t show_rs_window(struct device *d,
 			      struct device_attribute *attr,
 			      char *buf)
 {
-	struct iwl_priv *priv = d->driver_data;
-	return iwl_fill_rs_info(priv->hw, buf, IWL_AP_ID);
+	return 0;
 }
 static DEVICE_ATTR(rs_window, S_IRUGO, show_rs_window, NULL);
 
@@ -8851,7 +8847,6 @@ static void iwl_pci_remove(struct pci_dev *pdev)
 
 	if (priv->mac80211_registered) {
 		ieee80211_unregister_hw(priv->hw);
-		iwl_rate_control_unregister();
 	}
 
 	/* ieee80211_unregister_hw calls d_stop, which flushes


-- 
Regards,
Pavel Roskin

Re: Request for help...

[Axj]

I've tried the driver 0.1.4 with the new (not so new) linux kernel 2.6.22.1 (against the 2.6.21.5 installed on Slackware 12, and it work without any patch. In fact,  at the moment of compiling kernel the mac80211 subsystem is already in..... now it works (even if no led and no Ad-Hoc). I really don't try 1.0.0. I will do it. Maybe the fact of the led in only because I don't pass the right option to the modprobe (in ipw2200 was "modprobe ipw2200 led=1") but here is not. For the Ad-Hoc, i try to take a look in source, but maybe isn't present this part or I don't find. 

By the way, thank you for the advice and suggestions  


Quoting Pavel Roskin <proski@gnu.org>:

I


> On Thu, 2007-07-26 at 08:10 -0700, Axj wrote:
> 
> > I  saw onother exit of thje driver, 1.0.0, but I don't trust so
> much
> > (at the momente the compination of mac80211 ver 8.0.2 and
> > iwlwifi-0.0.42 work, even if the led doesn't work ad It's
> impossible
> > to set an "Ad-Hoc" connection. )
> 
> Actually, it's direct continuation of the 0.0.x series.  It's
> unfortunate that the complexity of the build system makes you
> mistrust
> the recent code, although I can relate.  I hope it will be
> remedied
> quickly.
> 
> It's possible to compile the 1.0.x driver against recent unpatched
> kernels, even against the standard Fedora 7 kernel, by stripping
> support
> for Intel's rate control algorithm:
> 
> diff --git a/origin/Makefile b/origin/Makefile
> index 8c0bdc7..c5d966f 100644
> --- a/origin/Makefile
> +++ b/origin/Makefile
> @@ -10,7 +10,7 @@
>  # -jpk
>  
>  obj-$(CONFIG_IWL3945)	+= iwl3945.o
> -iwl3945-objs		= base-3945.o iwl-3945.o iwl-3945-rs.o
> +iwl3945-objs		= base-3945.o iwl-3945.o
>  CFLAGS_iwl-3945.o	= -DIWL=3945
>  CFLAGS_iwl-3945-rs.o	= -DIWL=3945
>  CFLAGS_base-3945.o	= -DIWL=3945
> -D"KBUILD_MODNAME=KBUILD_STR(iwl3945)"
> @@ -19,7 +19,7 @@ $(obj)/base-3945.o: $(src)/base.c FORCE
>  	$(call if_changed_rule,cc_o_c)
>  
>  obj-$(CONFIG_IWL4965)	+= iwl4965.o
> -iwl4965-objs		= base-4965.o iwl-4965.o iwl-4965-rs.o
> +iwl4965-objs		= base-4965.o iwl-4965.o
>  CFLAGS_iwl-4965.o	= -DIWL=4965
>  CFLAGS_iwl-4965-rs.o	= -DIWL=4965
>  CFLAGS_base-4965.o	= -DIWL=4965
> -D"KBUILD_MODNAME=KBUILD_STR(iwl4965)"
> diff --git a/origin/base.c b/origin/base.c
> index eda467e..ee6ac8f 100644
> --- a/origin/base.c
> +++ b/origin/base.c
> @@ -6284,7 +6284,6 @@ static void iwl_alive_start(struct iwl_priv
> *priv)
>  		/* Unlock so any user space entry points can call back into
>  		 * the driver without a deadlock... */
>  		mutex_unlock(&priv->mutex);
> -		iwl_rate_control_register();
>  		rc = ieee80211_register_hw(priv->hw);
>  		priv->hw->conf.beacon_int = 100;
>  		mutex_lock(&priv->mutex);
> @@ -6950,7 +6949,6 @@ static void iwl_bg_post_associate(struct
> work_struct *data)
>  				  (priv->phymode == MODE_ATHEROS_TURBO)) ?
>  				 IWL_RATE_6M_PLCP : IWL_RATE_1M_PLCP,
>  				 CMD_ASYNC);
> -		iwl_rate_scale_init(priv->hw, IWL_AP_ID);
>  
>  		break;
>  
> @@ -6967,7 +6965,6 @@ static void iwl_bg_post_associate(struct
> work_struct *data)
>  				  (priv->phymode == MODE_ATHEROS_TURBO)) ?
>  				 IWL_RATE_6M_PLCP : IWL_RATE_1M_PLCP,
>  				 CMD_ASYNC);
> -		iwl_rate_scale_init(priv->hw, IWL_STA_ID);
>  		iwl_send_beacon_cmd(priv);
>  
>  		break;
> @@ -7915,8 +7912,7 @@ static ssize_t show_rs_window(struct device
> *d,
>  			      struct device_attribute *attr,
>  			      char *buf)
>  {
> -	struct iwl_priv *priv = d->driver_data;
> -	return iwl_fill_rs_info(priv->hw, buf, IWL_AP_ID);
> +	return 0;
>  }
>  static DEVICE_ATTR(rs_window, S_IRUGO, show_rs_window, NULL);
>  
> @@ -8851,7 +8847,6 @@ static void iwl_pci_remove(struct pci_dev
> *pdev)
>  
>  	if (priv->mac80211_registered) {
>  		ieee80211_unregister_hw(priv->hw);
> -		iwl_rate_control_unregister();
>  	}
>  
>  	/* ieee80211_unregister_hw calls d_stop, which flushes
> 
> 
> -- 
> Regards,
> Pavel Roskin
> 
>

----------------------------------------------------------------------
Finally - A spam blocker that actually works.
http://www.bluebottle.com/tag/4

Re: Request for help...

[Zhu Yi]

On Thu, 2007-07-26 at 23:34 -0700, Axj wrote:
> 
> I've tried the driver 0.1.4 with the new (not so new) linux kernel
> 2.6.22.1 (against the 2.6.21.5 installed on Slackware 12, and it work
> without any patch. In fact,  at the moment of compiling kernel the
> mac80211 subsystem is already in..... now it works (even if no led and
> no Ad-Hoc).

No, there is ad-hoc support in 0.1.4.

Thanks,
-yi

Re: Request for help...

[Axj]

Quoting Zhu Yi <yi.zhu@intel.com>:

> On Thu, 2007-07-26 at 23:34 -0700, Axj wrote:
> > 
> > I've tried the driver 0.1.4 with the new (not so new) linux
> kernel
> > 2.6.22.1 (against the 2.6.21.5 installed on Slackware 12, and it
> work
> > without any patch. In fact,  at the moment of compiling kernel
> the
> > mac80211 subsystem is already in..... now it works (even if no
> led and
> > no Ad-Hoc).
> 
> No, there is ad-hoc support in 0.1.4.
> 
> Thanks,
> -yi
> 


Maybe.... but don't work... from the version 0.0.36 to no tell me 

Impossible to set ...etc etc.... at the first occasion I will post up the error code that give me...

----------------------------------------------------------------------
Get a free email account with anti spam protection.
http://www.bluebottle.com/tag/2

Re: Request for help...

[Zhu Yi]

On Fri, 2007-07-27 at 01:48 -0700, Axj wrote:
> Maybe.... but don't work... from the version 0.0.36 to no tell me 
> 
> Impossible to set ...etc etc.... at the first occasion I will post up the error code that give me...

With mac80211 you need to change wireless mode only when the interface
is down.

$ ifconfig wlan0 down
$ iwconfig wlan0 mode ad-hoc
$ ifconfig wlan0 up

Thanks,
-yi

Re: Request for help...

[Axj]

Quoting Zhu Yi <yi.zhu@intel.com>:

> On Fri, 2007-07-27 at 01:48 -0700, Axj wrote:
> > Maybe.... but don't work... from the version 0.0.36 to no tell me
> 
> > 
> > Impossible to set ...etc etc.... at the first occasion I will
> post up the error code that give me...
> 
> With mac80211 you need to change wireless mode only when the
> interface
> is down.
> 
> $ ifconfig wlan0 down
> $ iwconfig wlan0 mode ad-hoc
> $ ifconfig wlan0 up
> 
> Thanks,
> -yi
> 
Yes I know.....

I tryed 

iwconfig wlan0 essid "lago" mode Ad-Hoc 
and then give me error....

----------------------------------------------------------------------
Get a free email account with anti spam protection.
http://www.bluebottle.com/tag/2

Re: Request for help...

[Zhu Yi]

On Fri, 2007-07-27 at 02:10 -0700, Axj wrote:
> iwconfig wlan0 essid "lago" mode Ad-Hoc 
> and then give me error.... 

What's the error?

-yi

Re: Request for help...

[Axj]

Quoting Zhu Yi <yi.zhu@intel.com>:

> On Fri, 2007-07-27 at 02:10 -0700, Axj wrote:
> > iwconfig wlan0 essid "lago" mode Ad-Hoc 
> > and then give me error.... 
> 
> What's the error?
> 
> -yi
> 

When I try the command 
 iwconfig wlan0 essid "lago" mode Ad-Hoc 

show me 

Error for wireless request Set Mode (8B06) :
    SET failed on device wlan0 ; Device or resource busy.

But if I connect with for example 

iwconfig wlan0 essid "dip-open" #my university wireless connection it works, and very well.

For this I have no explanation

----------------------------------------------------------------------
Free pop3 email with a spam filter.
http://www.bluebottle.com/tag/5

Request for help

[Lev R. Oshvang .]

Hi people.
Today I've sent my first patch - Add file suffix selector as an IMA policy rule
My apologies for the possible errors I made fighting with mutt.
I deleted FROM line of the format patch because I thought it is wrong,
here the line:
From b84152f969c6d0555486f3c78e1dd374f05bbe18 Mo Sep 17 00:00:00 2001

Please advise me whether this line is necessary.

Re: request for help

[devicetree]

Hi there,
We have never met before but I am Doctor Halilovic from Australia 
currently in South Gaza. Please may I kindly know your name and 
where you are from? I know it can be annoying getting emails from 
people you do not know. Still, I am getting in touch because I 
wanted to discuss an opportunity for us to connect and 
collaborate. I can be reached via my email address: 
dr.halilovicnedim@hotmail.com

Yours faithfully
Halilovic