VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: October 29, 2016, 04:10:22 am 
Started by vector - Last post by vincent2
There is a FCC problem with Channel 13 & 14:

http://kernelmag.dailydot.com/features/report/8051/the-mystery-of-wifi-channel-14/

You could use this approach:

https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA

Hope that helps,

Bigpaws

need iw pkg  and  libnl pkg  from slackware 64 cuurent repo,
  current libnl on vl7.2 test repo is old version
crda pkg can be found from slack repo..

 22 
 on: October 27, 2016, 11:11:54 am 
Started by Rytz - Last post by rbistolfi
What about this?

Code: [Select]
# setserial /dev/<tty_name> low_latency
Worth the try :)

 23 
 on: October 27, 2016, 11:06:09 am 
Started by Rytz - Last post by rbistolfi
Nop, we are just reading on the serial port as data from the station arrives.
I agree about the cables, it would be weird if all 4 cables were bad.
Did you try disabling power saving on usb ports?

 24 
 on: October 26, 2016, 11:14:21 am 
Started by Rytz - Last post by Rytz
Hi Rytz,

I would try the easiest first. USB devices are not great for latency, event a long cable can cause a lot of problems. Did you try a different cable? Are you using an USB hub? I recently experienced a lot of problems installing a weather station and it turned out to be the USB hub.

HTH, Rodrigo
Hi Rodrigo - thanks for the response.

There are four USB joysticks, and all four have been hit with this delay (I have logs that record the process).  Which device is affected when this occurs seems random.  I could swap out the cables, but I doubt all four cables are bad. 

I'm not using a USB hub.  I do think that I am using all USB ports on the machine, though (8-10 ports).

Are you reprogramming your weather station dynamically in a similar fashion?

 25 
 on: October 25, 2016, 06:14:48 pm 
Started by vector - Last post by bigpaws
There is a FCC problem with Channel 13 & 14:

http://kernelmag.dailydot.com/features/report/8051/the-mystery-of-wifi-channel-14/

You could use this approach:

https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA

Hope that helps,

Bigpaws

 26 
 on: October 25, 2016, 05:32:45 pm 
Started by vector - Last post by vincent2
we need channel 14  for wifi @japan!!!
expect new  kernel supporting chnanel 14!!!

 27 
 on: October 25, 2016, 08:39:23 am 
Started by Rytz - Last post by rbistolfi
Hi Rytz,

I would try the easiest first. USB devices are not great for latency, event a long cable can cause a lot of problems. Did you try a different cable? Are you using an USB hub? I recently experienced a lot of problems installing a weather station and it turned out to be the USB hub.

HTH, Rodrigo

 28 
 on: October 19, 2016, 11:13:52 am 
Started by Rytz - Last post by Rytz
VL Version: VL64-7.1 Standard
Kernel: 3.8.16 #2

Preface: I've been poking around the internet looking for more information on ioctl connect delays but haven't really found much.  Any suggestions or feedback appreciated.

I have a C program that calibrates joysticks using ioctl calls.  The code in question looks like below:

Code: [Select]
usb_ioctl.ioctl_code = USBDEVFS_DISCONNECT;
ioctl(fd, USBDEVFS_IOCTL, &usb_ioctl);

usb_ioctl.ioctl_code = USBDEVFS_CONNECT;
ioctl(fd, USBDEVFS_IOCTL, &usb_ioctl);

The 2nd ioctl call with USBDEVFS_CONNECT is the culprit.  I'd say 90% of the time, this call takes about 5ms.  The other 10% of the calls can take anywhere up to 10 seconds.  The delay time is random, so sometimes it is less.

What I have tried so far is to put the calibrator in a loop and force it to retry if execution time goes past 50ms.  So far this doesn't seem to help, as the newly spawn calibrators just keep delaying as well.

I have some code to manually reset the USB ports (to simulate a physical reconnect) but haven't tried it out yet.  I was trying to avoid the resetting of ports just in case that leads to other problems.  Other than these random delays in the ioctl call, I haven't experienced any other hardware related problems.

Any info or help on debugging the problem or fixing it would be great.  Thanks!

 29 
 on: October 18, 2016, 06:49:42 pm 
Started by vector - Last post by vincent2
already installled and boot with kernel 4.4.24, wifi still doesn't work on channel14, 13 yet so far...

modem 4G e3276 also doesn't work as well!

 30 
 on: October 18, 2016, 06:47:49 pm 
Started by vector - Last post by vincent2
Can you post which ralink chip does not work for you?  Maybe we just need to enable support for it on our build.  And are you using the 32bit or 64bit build?


ralink 3370 ...

also we need channel 13 and 14, this  is japn, not north america  canada!!!

Pages: 1 2 [3] 4 5 ... 10