 |
 |
 |
 |
| Hardware & Laptops Help with your hardware, including laptop issues |

7th December 2009, 02:11 PM
|
 |
Registered User
|
|
Join Date: Nov 2009
Location: Minas Gerais - Brazil
Posts: 12

|
|
|
wlan driver
Recently I have acquired a microboard computer, ultimate black one ( http://www.microboard.com.br/ultimate-black/ ) and installed fodora 12 on it.
It has a wlan card assembled by 3DSP ( http://www.3dsp.com.cn/).
I've found some drivers to download on the manufacturer website, but the drivers are for ubuntu, then I tryed to install it manually and got just error messages. I don't know if I am doing this by the right way.
Clound anyone help me, It could be a tutorial or a rpm package.
|

7th December 2009, 02:21 PM
|
|
Registered User
|
|
Join Date: Jun 2006
Posts: 7,551

|
|
Hello wregis,
Well, if the wireless device is known to work in Ubuntu, then it probably can be made to work in Fedora, too. I don't know anything about the hardware you described, but maybe the wireless card uses a common chipset. That's what determines the driver anyway. Take a moment to run these commands in a Fedora terminal and post the results. It may help someone think of something to tell you to do.
Code:
lspci -nn | grep -i -e network -e wireless
lsusb
|

7th December 2009, 02:27 PM
|
 |
Retired Community Manager -- Banned from Texas by popular demand.
|
|
Join Date: Sep 2007
Location: NYC
Posts: 8,142

|
|
A couple of things. You may need to install
(hopefully you have a wired connection)
yum install gcc gcc-c++ make automake kernel-devel
(If it's not a 64 bit chipset, than possibly kernel-PAE-devel, depending upon the results of
uname -r
If there's a PAE in there, then grab kernel-PAE-devel
That should be enough for the moment.
That's usually what causes the errors. The other thing is to post at least some of the error messages so we can see what the problem is. (My suggestion about installing things such as gcc is a guess, based on what frequently happens on these forums)
__________________
--
http://home.roadrunner.com/~computertaijutsu
Do NOT PM forum members with requests for technical support. Ask your questions on the forum.
"I don't know why there is the constant push to break any semblance of compatibility" --anon
|

8th December 2009, 02:47 AM
|
 |
Registered User
|
|
Join Date: Nov 2009
Location: Minas Gerais - Brazil
Posts: 12

|
|
Eh, right now I'm not with the problematic computer. Later I'll be with it, and then I will post what I've got.
---------- Post added at 12:47 AM CST ---------- Previous post was Yesterday at 02:30 PM CST ----------
Eh, sorry to be too late, but here is the result:
Code:
[root@icarus ~]# lspci -nn | grep -i -e network -e wireless
[root@icarus ~]# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
Bus 001 Device 002: ID 0cf2:6230 ENE Technology, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0951:1607 Kingston Technology Data Traveler 2.0
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e1:0100 Syntek Semiconductor Co., Ltd
|

8th December 2009, 03:17 PM
|
|
Registered User
|
|
Join Date: Apr 2009
Posts: 134

|
|
|
I think stoat meant
lspci -nn|grep -i -e ethernet -e network
I have never seen a PCI class of 'wireless'. Wireless PCI adapters normally either appear as Network class or Ethernet class.
|

8th December 2009, 06:34 PM
|
|
Registered User
|
|
Join Date: Jun 2006
Posts: 7,551

|
|
Quote:
|
Originally Posted by Robert2
I think stoat meant
lspci -nn|grep -i -e ethernet -e network
I have never seen a PCI class of 'wireless'. Wireless PCI adapters normally either appear as Network class or Ethernet class.
|
Actually I did mean it the way I wrote it. I didn't want returns for "-e ethernet" because they are usually wired NIC cards. But the few wireless cards that show up in lspci as "Ethernet" usually have the word "wireless" in the line, too. So to me, those two words are just the easiest way to catch more of the wireless cards in a one line report.
Quote:
|
Originally Posted by wregis
Code:
[root@icarus ~]# lspci -nn | grep -i -e network -e wireless
[root@icarus ~]# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
Bus 001 Device 002: ID 0cf2:6230 ENE Technology, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0951:1607 Kingston Technology Data Traveler 2.0
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e1:0100 Syntek Semiconductor Co., Ltd
|
I think that is the wireless device. At the moment, I don't know anything about it or what to do with it. Maybe someone else does.
Last edited by stoat; 8th December 2009 at 07:12 PM.
|

8th December 2009, 09:45 PM
|
|
Registered User
|
|
Join Date: Apr 2009
Posts: 134

|
|
Quote:
Originally Posted by stoat
Actually I did mean it the way I wrote it. I didn't want returns for "-e ethernet" because they are usually wired NIC cards. But the few wireless cards that show up in lspci as "Ethernet" usually have the word "wireless" in the line, too. So to me, those two words are just the easiest way to catch more of the wireless cards in a one line report.
Maybe someone else does.
|
Really....
Code:
[robert@t60 ~]$ lspci -nn|grep -i -e network -e wireless
[robert@t60 ~]$ lspci -nn|grep -i -e network -e ethernet
02:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a]
03:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212 802.11abg NIC [168c:1014] (rev 01)
I see no mention of wireless
|

8th December 2009, 11:52 PM
|
|
Registered User
|
|
Join Date: Jun 2006
Posts: 7,551

|
|
Quote:
|
Originally Posted by Robert2
Really....
|
You know, that was just a command that I like to do because it's has often worked in the past. I didn't mean (or say, actually) that you couldn't drag up some example where my pathetic idea would miserably fail. In lieu of further arguing over this infinitesimal and essentially irrelevant point since the wireless card has been identified anyway, I know what you need. Here. You're right. I was wrong. I grovel in mortification at your feet.
|

9th December 2009, 12:24 AM
|
|
Registered User
|
|
Join Date: Jun 2005
Location: UK
Posts: 4,345

|
|
|
You know Stoat, I like the way you put that!
|

9th December 2009, 08:23 AM
|
|
Registered User
|
|
Join Date: Apr 2009
Posts: 134

|
|
Quote:
Originally Posted by stoat
You know, that was just a command that I like to do because it's has often worked in the past. I didn't mean (or say, actually) that you couldn't drag up some example where my pathetic idea would miserably fail. In lieu of further arguing over this infinitesimal and essentially irrelevant point since the wireless card has been identified anyway, I know what you need. Here. You're right. I was wrong. I grovel in mortification at your feet.
|
Someone needs to take his meds.
All I was pointing out that grabbing for wireless on a PCI listing is no guarantee of actually finding a wireless card, since your relying on a text description field, which may even be blanc.
Wireless cards in my experience are either classified as Network class, or Ethernet class, so grabbing for those should find it. Of course it will also create false-positives since it will find your Ethernet adapter also.
|

9th December 2009, 11:36 AM
|
 |
Registered User
|
|
Join Date: Nov 2009
Location: Minas Gerais - Brazil
Posts: 12

|
|
Take a look at http://www.stk.com.tw/, I think I could be my camera, not my wireless card.
Code:
[wanderson@icarus ~]$ lspci -nn | grep -i -e network -e ethernet
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
Thanks anyway.
|

9th December 2009, 11:46 AM
|
|
Registered User
|
|
Join Date: Apr 2009
Posts: 134

|
|
Quote:
Originally Posted by wregis
Take a look at http://www.stk.com.tw/, I think I could be my camera, not my wireless card.
Code:
[wanderson@icarus ~]$ lspci -nn | grep -i -e network -e ethernet
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
Thanks anyway.
|
That is your Ethernet controller.
Your Camera would be this USB device:
Bus 001 Device 003: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
|

9th December 2009, 11:59 AM
|
|
Registered User
|
|
Join Date: Jun 2005
Location: UK
Posts: 4,345

|
|
Theres a thread here:
http://translate.google.co.uk/transl...%3Den%26sa%3DG
that identifies this device:
Code:
Bus 002 Device 002: ID 05e1:0100 Syntek Semiconductor Co., Ltd
as:
Quote:
|
Device 002: ID 05e1: 0100 is a USB dongle that makes two types of connections to the bluetooth and wifi
|
Don't see anybody having much luck with it though.
|

10th December 2009, 11:35 AM
|
 |
Registered User
|
|
Join Date: Nov 2009
Location: Minas Gerais - Brazil
Posts: 12

|
|
Hi all. At http://www.stk.com.tw/product-01.asp?Product_Type=58 I downloaded http://www.stk.com.tw/driver/Wireles...thotkey.tar.gz and then run tar xvzf on it, followed to driver folder as root, changed perissions to 744 and copied to /lib/modules/2.6.31.6-162.fc12.x86_64/kernel/net/wireless/, then I run depmod and then
Code:
[root@icarus wireless]# modprobe 3dspusbwlan
WARNING: Error inserting 3dspusbwlanpriv (/lib/modules/2.6.31.6-162.fc12.x86_64/kernel/net/wireless/3dspusbwlanpriv.ko): Invalid module format
FATAL: Error inserting 3dspusbwlan (/lib/modules/2.6.31.6-162.fc12.x86_64/kernel/net/wireless/3dspusbwlan.ko): Invalid module format
I folowed this tutorial: http://www.madeira.eng.br/wiki/index...m+no+Fedora+12, actually just the final part of it. What is wrong?
|

30th March 2011, 10:30 AM
|
|
Registered User
|
|
Join Date: Feb 2011
Posts: 2

|
|
|
3dsp source code
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 01:17 (Sunday, 26-05-2013)
|
|
 |
 |
 |
 |
|
|