Can't set-up Wifi Adhoc on my Raspberry Pi with an USB dongle
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am trying to set-up an access point (ad-hoc) for my Raspberry Pi. That means I'm trying to "share" the ethernet connection over Wi-Fi. I am doing this using my Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter. When following a tutorial (or actually every tutorial), it immediately goes wrong.
root@pinkypi:/home/pi# iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.
I already tried ifdown and not having it in the USB port at the startup.
If it helps, every action with the thing fail (or at least setting the mode). I am using Debian.
I'm sure I'm overseeing something, but I can't find out what. What is wrong?
linux wireless-networking usb debian
asked Sep 16 '12 at 12:23
WouterWouter
213
add a comment |
I am trying to set-up an access point (ad-hoc) for my Raspberry Pi. That means I'm trying to "share" the ethernet connection over Wi-Fi. I am doing this using my Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter. When following a tutorial (or actually every tutorial), it immediately goes wrong.
root@pinkypi:/home/pi# iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.
I already tried ifdown and not having it in the USB port at the startup.
If it helps, every action with the thing fail (or at least setting the mode). I am using Debian.
I'm sure I'm overseeing something, but I can't find out what. What is wrong?
linux wireless-networking usb debian
asked Sep 16 '12 at 12:23
WouterWouter
213
add a comment |
I am trying to set-up an access point (ad-hoc) for my Raspberry Pi. That means I'm trying to "share" the ethernet connection over Wi-Fi. I am doing this using my Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter. When following a tutorial (or actually every tutorial), it immediately goes wrong.
root@pinkypi:/home/pi# iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.
I already tried ifdown and not having it in the USB port at the startup.
If it helps, every action with the thing fail (or at least setting the mode). I am using Debian.
I'm sure I'm overseeing something, but I can't find out what. What is wrong?
linux wireless-networking usb debian
asked Sep 16 '12 at 12:23
WouterWouter
213
I am trying to set-up an access point (ad-hoc) for my Raspberry Pi. That means I'm trying to "share" the ethernet connection over Wi-Fi. I am doing this using my Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter. When following a tutorial (or actually every tutorial), it immediately goes wrong.
root@pinkypi:/home/pi# iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.
I already tried ifdown and not having it in the USB port at the startup.
If it helps, every action with the thing fail (or at least setting the mode). I am using Debian.
I'm sure I'm overseeing something, but I can't find out what. What is wrong?
linux wireless-networking usb debian
linux wireless-networking usb debian
asked Sep 16 '12 at 12:23
WouterWouter
213
asked Sep 16 '12 at 12:23
WouterWouter
213
edited Sep 16 '12 at 12:37
Wouter
asked Sep 16 '12 at 12:23
WouterWouter
213
asked Sep 16 '12 at 12:23
WouterWouter
213
asked Sep 16 '12 at 12:23
WouterWouter
213
213
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Have you tried running the command with admin privileges, ie prefix the command with sudo:
sudo iwconfig wlan0 mode ad-hoc
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
add a comment |
What does the kernel say? (If anything)
Have you tried to bring the interface up with 'ifconfig wlan0 up' before setting the mode?
It might also be worth checking if the device can be used in ad-hoc mode on another box, possibly with a recent distro.
answered Dec 4 '12 at 17:22
emaema
29615
add a comment |
I am having the same issue. I was able to successfully start an ad hoc network on on my raspi by first creating one in wicd and then from the command line. I get the error if I try to start ad hoc on boot. Wicd must be changing modes for me before I try to bring up ad hoc, but I need to find out what it is doing to replicate it on boot. Does anyone know how to find out what wicd is doing or any way to fix this issue. I have already tried using ifconfig wlan0 up/down and there is no difference.
answered Feb 14 '13 at 2:24
user198109user198109
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f475768%2fcant-set-up-wifi-adhoc-on-my-raspberry-pi-with-an-usb-dongle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Have you tried running the command with admin privileges, ie prefix the command with sudo:
sudo iwconfig wlan0 mode ad-hoc
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
add a comment |
Have you tried running the command with admin privileges, ie prefix the command with sudo:
sudo iwconfig wlan0 mode ad-hoc
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
add a comment |
Have you tried running the command with admin privileges, ie prefix the command with sudo:
sudo iwconfig wlan0 mode ad-hoc
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
Have you tried running the command with admin privileges, ie prefix the command with sudo:
sudo iwconfig wlan0 mode ad-hoc
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
answered Sep 17 '12 at 9:03
snowdudesnowdude
2,4451217
2,4451217
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
add a comment |
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
As you can see in the codeblock, I am doing this all with the "root" user. So, yes.
– Wouter
Sep 17 '12 at 20:26
add a comment |
What does the kernel say? (If anything)
Have you tried to bring the interface up with 'ifconfig wlan0 up' before setting the mode?
It might also be worth checking if the device can be used in ad-hoc mode on another box, possibly with a recent distro.
answered Dec 4 '12 at 17:22
emaema
29615
add a comment |
What does the kernel say? (If anything)
Have you tried to bring the interface up with 'ifconfig wlan0 up' before setting the mode?
It might also be worth checking if the device can be used in ad-hoc mode on another box, possibly with a recent distro.
answered Dec 4 '12 at 17:22
emaema
29615
add a comment |
What does the kernel say? (If anything)
Have you tried to bring the interface up with 'ifconfig wlan0 up' before setting the mode?
It might also be worth checking if the device can be used in ad-hoc mode on another box, possibly with a recent distro.
answered Dec 4 '12 at 17:22
emaema
29615
What does the kernel say? (If anything)
Have you tried to bring the interface up with 'ifconfig wlan0 up' before setting the mode?
It might also be worth checking if the device can be used in ad-hoc mode on another box, possibly with a recent distro.
answered Dec 4 '12 at 17:22
emaema
29615
answered Dec 4 '12 at 17:22
emaema
29615
answered Dec 4 '12 at 17:22
emaema
29615
answered Dec 4 '12 at 17:22
emaema
29615
29615
add a comment |
add a comment |
I am having the same issue. I was able to successfully start an ad hoc network on on my raspi by first creating one in wicd and then from the command line. I get the error if I try to start ad hoc on boot. Wicd must be changing modes for me before I try to bring up ad hoc, but I need to find out what it is doing to replicate it on boot. Does anyone know how to find out what wicd is doing or any way to fix this issue. I have already tried using ifconfig wlan0 up/down and there is no difference.
answered Feb 14 '13 at 2:24
user198109user198109
1
add a comment |
I am having the same issue. I was able to successfully start an ad hoc network on on my raspi by first creating one in wicd and then from the command line. I get the error if I try to start ad hoc on boot. Wicd must be changing modes for me before I try to bring up ad hoc, but I need to find out what it is doing to replicate it on boot. Does anyone know how to find out what wicd is doing or any way to fix this issue. I have already tried using ifconfig wlan0 up/down and there is no difference.
answered Feb 14 '13 at 2:24
user198109user198109
1
add a comment |
I am having the same issue. I was able to successfully start an ad hoc network on on my raspi by first creating one in wicd and then from the command line. I get the error if I try to start ad hoc on boot. Wicd must be changing modes for me before I try to bring up ad hoc, but I need to find out what it is doing to replicate it on boot. Does anyone know how to find out what wicd is doing or any way to fix this issue. I have already tried using ifconfig wlan0 up/down and there is no difference.
answered Feb 14 '13 at 2:24
user198109user198109
1
I am having the same issue. I was able to successfully start an ad hoc network on on my raspi by first creating one in wicd and then from the command line. I get the error if I try to start ad hoc on boot. Wicd must be changing modes for me before I try to bring up ad hoc, but I need to find out what it is doing to replicate it on boot. Does anyone know how to find out what wicd is doing or any way to fix this issue. I have already tried using ifconfig wlan0 up/down and there is no difference.
answered Feb 14 '13 at 2:24
user198109user198109
1
answered Feb 14 '13 at 2:24
user198109user198109
1
answered Feb 14 '13 at 2:24
user198109user198109
1
answered Feb 14 '13 at 2:24
user198109user198109
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f475768%2fcant-set-up-wifi-adhoc-on-my-raspberry-pi-with-an-usb-dongle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
