LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 11-20-2005, 05:13 PM   #1
superbnerb
Member
 
Registered: Jul 2005
Location: about town
Distribution: Kanotix64
Posts: 71

Rep: Reputation: 15
has anyone EVER had ndiswrapper work in a 64 bit environment?


i wish there was a site dedicated to 64 bit questions only. linux questions... let's get on that one, or make it easy to find if it does exist.

all that aside, simple question:

CAN ANYONE WHO HAS EVER HAD A BROADCOM 64 BIT DRIVER WORK PLEASE POST HOW YOU DID IT!

kanotix has gotten t heir latest 64 bit OS working right. It's got all the eye candy that i wanted pre installed, with all the headers you'll ever need. I want to use them, and need my wireless connection.

Feel free to post and help brothers who are less fortunate then thou.
 
Old 11-21-2005, 10:08 AM   #2
fouldsy
Senior Member
 
Registered: Jan 2002
Location: St Louis, MO
Distribution: Ubuntu
Posts: 1,284

Rep: Reputation: 47
Not sure about your particular problem since I don't have any 64bit x86 hardware, but you could make it a suggestion under the forums Feedback & Suggestions towards at 64-bit forum if the idea has not already been raised before. There does seem to be more + more issues with 64-bit related drivers that are unique to those systems, so sounds like a good idea in principal.
 
Old 11-21-2005, 01:20 PM   #3
CrimZon
LQ Newbie
 
Registered: Aug 2003
Location: none
Distribution: none
Posts: 15

Rep: Reputation: 0
Not here.
I'm running an AMD 64 X2 dual dore 4400 and using a USB-type wireless DLink DWL-G122 (v. A2) and have had no luck on Mandriva 2005 64-bit or Mandriva 2006 64-bit.

I do not know exactly what the problem is as I can load the driver and recognize the device, but it never makes "wlan0" on the system (all this is detailed in a thread I have below).

Honestly, I have had nothing but problems in Linux since I went to a 64-bit system. Perhaps it is a Mandrake issue, so I may have to change distros.

If Ndiswrapper is not working for you, you may have to find what chips your wireless card is using and load and configure that way (then again, you're probably posting about ndiswrapper because they may not have worked).

As I said, I've had no luck here, but I figure if this doesn't help, at least you'll know that you're not the only one out there that can't get ndiswrapper to work.

Best of luck. :|
 
Old 11-21-2005, 07:35 PM   #4
superbnerb
Member
 
Registered: Jul 2005
Location: about town
Distribution: Kanotix64
Posts: 71

Original Poster
Rep: Reputation: 15
you hit the penguin on the head, dude. i wanted to see if someone else had the same problem.

i mean, ndiswrapper works for my 32 bit environment. but the world is, and should be, shifting to a 64 bit enviro. I want to be there. Kanotix64 is exactly what i wanted in a distro. I have a AMD turion chipset (i know i spelled it wrong) and i want to use it. i just want to work. finding 64 bit information that you don't LUCK across is like winning the lottery, mate.

was this posting a bitch session... yes, but I needed to know i wasn't alone. Now we can find a solution to the problem.
 
Old 11-27-2005, 11:29 PM   #5
CrimZon
LQ Newbie
 
Registered: Aug 2003
Location: none
Distribution: none
Posts: 15

Rep: Reputation: 0
Just a hypothesis or two but:

It may be that NDISWRAPPER is not compiled for 64-bit.

Perhaps although WinXP-32 will run on a 64-bit CPU (AMD), NDISWRAPPER may need 64-bit Windows drivers, just as WinXP-64 needs it's own 64-bit drivers.

It may be something within the Kernel that does not allow either NDISWRAPPER to operate with 32-bit Win drivers in 64-bit Linux distros.

And finally, it might be something tied to how some 64-bit Linuxes initialize thier devices..(on one level or another)...

The last one has a bit of thought because I think that Linux, in general, will list devices even if they are not there. For example, you may find "eth0" on your system even if you don't have an ethernet connection. We find "sd0" (I may have the device name off, just going off memory here) even though we don't have a SCSI device, board, or controller on the system. Likewise, we should find "wlan0" whether or not there is a wireless device attached, installed, or whatnot. I have had no luck with finding "wlan0" at all in 64-bit Mandriva 2005 or 2006.

This problem might be a bit larger than I thought, namely: Is there a major problem with wireless devices in 64-bit Linuxes?

Last edited by CrimZon; 11-27-2005 at 11:31 PM.
 
Old 11-28-2005, 07:03 AM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,785
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally posted by CrimZon


Perhaps although WinXP-32 will run on a 64-bit CPU (AMD), NDISWRAPPER may need 64-bit Windows drivers, just as WinXP-64 needs it's own 64-bit drivers.

It may be something within the Kernel that does not allow either NDISWRAPPER to operate with 32-bit Win drivers in 64-bit Linux distros.

From what I understand, and what I've read on the ndiswrapper FAQ, mixing 32 bit Windows drivers in a 64 bit environment is a big no-no. It simply doesn't work. You absolutely, positively MUST be using a 64 bit windows driver.
 
Old 11-28-2005, 09:25 PM   #7
ShatteredArm
LQ Newbie
 
Registered: Aug 2005
Location: AZ
Distribution: FC4, Gentoo
Posts: 22

Rep: Reputation: 15
I'm using ndiswrapper in a 64-bit environment.. I'm pretty inexperienced, so don't ask me how I did it... I do recall that I ended up using a different driver than the one suggested though. I believe they say to use bcmw1564, but I think it was netbc564 that ended up working for me. If I remember correctly, that's the 64-bit one.
 
Old 12-14-2005, 07:56 PM   #8
superbnerb
Member
 
Registered: Jul 2005
Location: about town
Distribution: Kanotix64
Posts: 71

Original Poster
Rep: Reputation: 15
linuxant

dear dudes who read this in the future...

if you have a 64 bit OS, like kanotix64 http://www.kanotix.comyou must use a 64 bit driver. I found a site, that found a driver for our card. i am using a Presario V2310CA machine and it has a built in broadcom chipset. the driver files come from ACER at this URL

and i used linuxant's driverloader and signed up for the free 30 day trial. http://www.linuxant.com/driverloader/

here is the driver

once the free trial ends, then maybe i'll try again. The thing is now I can't make the machine connect with the AP. i use kwifi and i can see my access point. I input my wep and essid and stuff i used to do on the 32 bit system, but it won't connect. It's like Valhala... i'm close and i can see it, but it won't let me in.
 
Old 12-14-2005, 08:36 PM   #9
Lenard
Senior Member
 
Registered: Dec 2005
Location: Indiana
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790

Rep: Reputation: 56
Doing so right now. running a 2.6.14.3 kernel and using ndiswrapper-1.7 on my Acer Aspire 5002 laptop;

00:0b.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

With the Windows 64-bit driver (see ndiswrapper wiki list card # 36 for where to get the driver)

$ ndiswrapper -l
Installed ndis drivers:
bcmwl5 driver present, hardware present

$ uname -a
Linux Aspire5000 2.6.14.3 #1 Sun Dec 11 19:02:03 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
 
Old 12-14-2005, 09:38 PM   #10
superbnerb
Member
 
Registered: Jul 2005
Location: about town
Distribution: Kanotix64
Posts: 71

Original Poster
Rep: Reputation: 15
thanks man, now, can u tell me the process on how to connect to the AP? access point...

i used to do the following

Code:
iwconfig eth1 essid WHATEVERTHEFCK
iwconfig eth1 key restricted 34092309ri23049i23049(thewepkey!)
dhclient eth1
NOW IN my kanotix 64 OS, that shtuff don't work. i get this gay message, and yes i said gay!

DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database.

Sleeping.

so dude, how do u do it?
 
Old 12-15-2005, 08:41 PM   #11
Lenard
Senior Member
 
Registered: Dec 2005
Location: Indiana
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790

Rep: Reputation: 56
Try replacing eth1 with wlan0 in your code, what I did the first time with no encryption enabled (make things a bit easier);

iwlist wlan0 scan
iwconfig wlan0 essid 'ESSID RESULTS HERE' <-- notice the single quotemarks
dhclient wlan0
 
Old 12-15-2005, 09:59 PM   #12
superbnerb
Member
 
Registered: Jul 2005
Location: about town
Distribution: Kanotix64
Posts: 71

Original Poster
Rep: Reputation: 15
my wireless adapter/integrated chipset is on eth1. wlan0 doesn't work because it isn't on wlan0. i have tried. thanks though.

what i will try is the single quotes just to see if that sh!t works.
 
Old 12-17-2005, 02:59 PM   #13
Lenard
Senior Member
 
Registered: Dec 2005
Location: Indiana
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790

Rep: Reputation: 56
Just re-read the thread, looking for a possible common solution......

You need to use the 64-bit Windows drivers if you build ndiswrapper in 64-bit, the 32-bit drivers don't work with ndiswrapper 64-bit.

For me, it was downloading the 64-bit drivers as listed in the ndiswrapper working cards list (Broadcom card # 36).
 
Old 12-31-2005, 05:22 PM   #14
superbnerb
Member
 
Registered: Jul 2005
Location: about town
Distribution: Kanotix64
Posts: 71

Original Poster
Rep: Reputation: 15
i explain the steps that i used to make my 64 bit machine run. I'm excited and hope it saves everyone some fricking hair pulling.

Use this link if you know your ndiswrapper configured and compiled your driver properly... i.e. your lights are on, or kwifimanager says it can see your AP, however, you can't connect to it for some reason.

http://www.linuxquestions.org/questi...34#post2023634 hope it helps... it helped me. Read my post towards the bottom... at time of writing.
 
Old 01-08-2006, 11:49 AM   #15
Jules82
LQ Newbie
 
Registered: Jan 2006
Posts: 3

Rep: Reputation: 0
Lenard,

I have the same laptop than you.
But when i tried to scan which wireless network are available, i got an error : interface doesn't support the scanning.

Do you have an idea???
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ndiswrapper on 64 bit KasperLotus Linux - Wireless Networking 0 09-30-2005 08:12 PM
Mandriva 64-bit Wireless w\ ndiswrapper Avi Linux - Wireless Networking 0 08-19-2005 10:25 PM
Broadcom 802.11b/g setup under 64 bit SUSE 9.2 with ndiswrapper tavisor Linux - Wireless Networking 6 04-19-2005 11:29 PM
Compiling an AMD64 kernel from a 32-bit environment justinmc Linux - General 3 01-16-2005 06:47 PM
Compiling 32-bit binary in a 64-bit environment Kaj Linux - Software 1 12-13-2004 09:43 AM


All times are GMT -5. The time now is 03:44 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration