Jump to content


Photo

Wifi adapter met RT5370 chipset drivers

wifi usb chipset drivers RT5370

  • Please log in to reply
6 replies to this topic

#1 Glacier

  • Member
  • 24 posts

0
Neutral

Posted 18 July 2013 - 14:48

Ik ben sinds kort in het bezit van een Xtrend ET4000. Ik heb een Golden Media usb wifi adapter met RT5370 chipset die ik wil gaan gebruiken. Maar ik kan nergens drivers vinden, niet op google, dit forum en niet in openpli zelf.

Heeft iemand de gouden tip voor mij hoe ik deze wifi usb stick aan de praat kan krijgen? Ik gebruik openpli van 3 dagen geleden.

 

Even een usb gerelateerde vraag: is het mogelijk om mijn (via aparte voeding gepowerde) externe harddisk en het wifi usb adaptertje via een usb hubje aan de ET4000 te hangen? Dan hoef ik niet steeds de klep aan de voorkant open te hebben :)



Re: Wifi adapter met RT5370 chipset drivers #2 WTE

  • Senior Member
  • 702 posts

+31
Good

Posted 18 July 2013 - 18:42

Ik ben sinds kort in het bezit van een Xtrend ET4000. Ik heb een Golden Media usb wifi adapter met RT5370 chipset die ik wil gaan gebruiken. Maar ik kan nergens drivers vinden, niet op google, dit forum en niet in openpli zelf.

Heeft iemand de gouden tip voor mij hoe ik deze wifi usb stick aan de praat kan krijgen? Ik gebruik openpli van 3 dagen geleden.

 

Even een usb gerelateerde vraag: is het mogelijk om mijn (via aparte voeding gepowerde) externe harddisk en het wifi usb adaptertje via een usb hubje aan de ET4000 te hangen? Dan hoef ik niet steeds de klep aan de voorkant open te hebben :)

 

Je kan gewoon een hub gebruiken.

 

RT5370 zou gewoon moeten werken.

Om te kijken waarom het niet werkt zal je via putty/hyperterminal de dmesg en lsusb log hier moeten neerzetten.


Mut@nt HD51 STB 4K

   :rolleyes:                :rolleyes:


Re: Wifi adapter met RT5370 chipset drivers #3 Glacier

  • Member
  • 24 posts

0
Neutral

Posted 19 July 2013 - 07:43

Ik zie in de driver lijst alleen maar dvb-t drivers staan (stuk of 10) en verder niets. Of bedoel je dat het out of the box zou moeten werken?



Re: Wifi adapter met RT5370 chipset drivers #4 WTE

  • Senior Member
  • 702 posts

+31
Good

Posted 19 July 2013 - 12:13

Ik zie in de driver lijst alleen maar dvb-t drivers staan (stuk of 10) en verder niets. Of bedoel je dat het out of the box zou moeten werken?

 

Wifi drivers worden automatisch geladen maar dan moet wel de device ID bekend zijn in de linux kernel.

Met dmesg kan je zien als er iets geladen wordt en lsusb laat de fabrikant en product ID zien.


Mut@nt HD51 STB 4K

   :rolleyes:                :rolleyes:


Re: Wifi adapter met RT5370 chipset drivers #5 Glacier

  • Member
  • 24 posts

0
Neutral

Posted 19 July 2013 - 15:00

Dit is de output van dmesg:

Linux version 3.8.7 (build@buildserver) (gcc version 4.6.4 20120
 (GCC) ) #1 Wed Jun 5 11:57:49 CEST 2013
Fetching vars from bootloader... found 7 vars.
Options: enet_en=1 enet0_mii=0 enet_no_mdio=0 enet1_en=0 moca=0
         sata=0 docsis=0 pci=0 pcie=0 smp=0 usb=1
Using 512 MB + 0 MB RAM (from CFE)
MEMC0 split: 256 MB -> Linux; 256 MB -> extra bmem
CPU revision is: 00029032 (Broadcom BMIPS3300)
Determined physical RAM map:
 memory: 10000000 @ 00000000 (usable)
bmem: adding 232 MB LINUX region at 7 MB (0x0e8a6000@0x0075a000)
bmem: adding 16 MB RESERVED region at 240 MB (0x01000000@0x0f000
Zone ranges:
  Normal   [mem 0x00000000-0x0fffffff]
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00000000-0x0fffffff]
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat 80701ab0, node_mem_map 810000
  Normal zone: 512 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 65024 pages, LIFO batch:15
Primary instruction cache 32kB, VIPT, 4-way, linesize 16 bytes.
Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pa
Kernel command line:  ubi.mtd=rootfs rootfstype=ubifs root=ubi0:
@512M bmem=16M console=null consoleblank=0
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
__ex_table already sorted, skipping sort
Memory: 235940k/262144k available (5771k kernel code, 26204k res
a, 244k init, 0k highmem)
NR_IRQS:160
Measuring MIPS counter frequency...
Detected MIPS clock frequency: 501 MHz (250.502 MHz counter)
Console: colour dummy device 80x25
Calibrating delay loop... 497.66 BogoMIPS (lpj=248832)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
devtmpfs: initialized
bmem: adding extra 256 MB RESERVED region at 512 MB (0x10000000@
NET: Registered protocol family 16
USB0: power enable is active low; overcurrent is active low
bio: create slab <bio-0> at 0
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Linux video capture interface: v2.00
Advanced Linux Sound Architecture Driver Initialized.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource wktmr
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
fuse init (API version 7.20)
msgmni has been set to 460
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10406800 (irq = 62) is a 16550A
serial8250.0: ttyS1 at MMIO 0x10406840 (irq = 63) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10406880 (irq = 64) is a 16550A
loop: module loaded
brcmstb_nand: NAND controller driver is loaded
__clk_enable: network [1]
__clk_enable: enet [1]
bcm7552_pm_genet_enable 00
Config internal EPHY through MDIO
__clk_disable: enet [0]
bcm7552_pm_genet_disable 00
__clk_disable: network [0]
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
__clk_enable: usb [1]
bcm7552_pm_usb_enable 00
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus numb
ehci-brcm ehci-brcm.0: irq 66, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus numb
ohci-brcm ohci-brcm.0: irq 67, io mem 0x10480400
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
Key type dns_resolver registered
EBI CS1: setting up NAND flash (primary)
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND
t), 128MiB, page size: 2048, OOB size: 64
brcmnand brcmnand.0: 128MiB total, 128KiB blocks, 2KiB pages, 16
H-4

Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
Creating 3 MTD partitions on "brcmnand.0":
0x000000000000-0x000008000000 : "complete"
0x000000000000-0x000000600000 : "kernel"
0x000000600000-0x000008000000 : "rootfs"
PM: CP0 COUNT/COMPARE frequency depends on divisor
UBI: attaching mtd2 to ubi0
usb 1-1: new high-speed USB device number 2 using ehci-brcm
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.2: new full-speed USB device number 3 using ehci-brcm
UBI: scanning is finished
UBI: attached mtd2 (name "rootfs", size 122 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 972, bad PEBs: 4, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 12
UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequ
3008110
UBI: available PEBs: 0, total reserved PEBs: 972, PEBs reserved
ling: 16
ALSA device list:
  No soundcards found.
Warning: unable to open an initial console.
UBI: background thread "ubi_bgt0d" started, PID 41
UBIFS: background thread "ubifs_bgt0_0" started, PID 42
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"(null)
UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit size
48 bytes
UBIFS: FS size: 119484416 bytes (113 MiB, 941 LEBs), journal siz
(8 MiB, 72 LEBs)
UBIFS: reserved for root: 0 bytes (0 KiB)
UBIFS: media format: w4/r0 (latest is w4/r0), UUID BCBE035E-C5AC
3136AA8, small LPT model
VFS: Mounted root (ubifs filesystem) on device 0:10.
devtmpfs: mounted
Freeing unused kernel memory: 244k freed
Algorithmics/MIPS FPU Emulator v1.5
usbcore: registered new interface driver tpm
dvb: module_layout: kernel tainted.
Disabling lock debugging due to kernel taint
Console: switching to colour frame buffer device 160x45
input: dreambox remote control (native) as /devices/virtual/inpu
input: dreambox advanced remote control (native) as /devices/vir
1
DVB: registering new adapter (dvb0)
platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2).
input: front panel as /devices/virtual/input/input2
NET: Registered protocol family 10
Console: switching to colour dummy device 80x25
__clk_enable: network [1]
__clk_enable: enet [1]
bcm7552_pm_genet_enable 00
eth0 Link DOWN.
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0 Link UP.
Auto config phy
eth0: Link is up, 100 Mbps Full Duplex
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
usb 1-1.1: new high-speed USB device number 4 using ehci-brcm
usb 1-1.1: reset high-speed USB device number 4 using ehci-brcm
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
usbcore: registered new interface driver rt2800usb
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
usb 1-1.1: USB disconnect, device number 4
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)

 

En dit die van lsusb:

Bus 001 Device 002: ID 1a40:0101
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 003: ID dead:beef


Re: Wifi adapter met RT5370 chipset drivers #6 WTE

  • Senior Member
  • 702 posts

+31
Good

Posted 20 July 2013 - 08:29

Het lijkt erop dat je externe hub of je wifi stick niet goed functioneert.

 

usbcore: registered new interface driver rt2800usb
dvb_demux_feed_del
: feed not in list (type=0 state=0 pid=ffff)
usb 1-1.1: USB disconnect, device number 4
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)

 

De stick wordt (even) herkend (rt2800usb) en daarna verdwijnt het.

Kan je nog kijken wat lsmod zegt. Ik heb het idee dat je vanalles hebt geinstalleerd.

Werkt de stick wel goed in een ander apparaat?


Mut@nt HD51 STB 4K

   :rolleyes:                :rolleyes:


Re: Wifi adapter met RT5370 chipset drivers #7 Glacier

  • Member
  • 24 posts

0
Neutral

Posted 23 July 2013 - 15:51

Ik weet niet precies wat er gebeurd is, maar hij werkt nu dus wel..had de ET een paar dagen niet aan gehad en na het opstarten stond het nu wel bij network..

Het enige wat ik geinstalleerd heb, is EPG Import..hoe kom je erbij dat ik vanalles heb geinstalleerd?







Also tagged with one or more of these keywords: wifi, usb, chipset, drivers, RT5370

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users