Page 11 of 48 FirstFirst ... 91011121321 ... LastLast
Results 151 to 165 of 714

Thread: New oleg firmware version

  1. #151
    At the other hand, there're good news upcoming 'bout 2.6 kernel and broadcom native wl driver
    http://wl500g.info/showpost.php?p=136257&postcount=789

  2. #152
    Join Date
    Nov 2006
    Location
    Russia, Moscow
    Posts
    3,640
    Quote Originally Posted by theMIROn View Post
    At the other hand, there're good news upcoming 'bout 2.6 kernel and broadcom native wl driver
    http://wl500g.info/showpost.php?p=136257&postcount=789
    New drivers probably can omit support for old cards

  3. #153
    Quote Originally Posted by lly View Post
    New drivers probably can omit support for old cards
    Yep, it's possible... We'll see, holding our fingers crossed.

  4. #154
    Quote Originally Posted by wpte View Post
    would it be possible to set the default regulatory mode in the wireless advanced tab (for wl-500w routers) to 802.11h?
    AFAIK 802.11h disables connectivity for Intel 2200BG and similar wireless cards (by setting the spectrum management flag to ON), so it's probably a good idea to keep regulatory mode "off" by default.

    Alternatively wlconf can be patched to keep spectrum management off even if regulatory is set to "h" - but I don't know if this change may have any other implications...

  5. #155
    Join Date
    Dec 2007
    Location
    The Netherlands - Eindhoven
    Posts
    1,767
    Quote Originally Posted by teddy_bear View Post
    AFAIK 802.11h disables connectivity for Intel 2200BG and similar wireless cards (by setting the spectrum management flag to ON), so it's probably a good idea to keep regulatory mode "off" by default.

    Alternatively wlconf can be patched to keep spectrum management off even if regulatory is set to "h" - but I don't know if this change may have any other implications...
    well yes, spectrum management is one of the key good features of 802.11h... less intefierence

    but by default the regulatory mode is set to 802.11d, wich isn't that great imo
    I didn't have any problems with B/G cards with 802.11h tho

  6. #156
    Quote Originally Posted by wpte View Post
    I didn't have any problems with B/G cards with 802.11h tho
    Not sure... I don't have any Intel 2200BG card to test it myself, so this info is mostly based on this OpenWRT ticket, and this Tomato thread. Also, Oleg recommended to set mode to "d" when he releazed 1.9.2.7-8 - specifically to "solve some problems with Intel WiFi cards".

    But what I know for a fact, is that the Atheros wl card in my notebook works better when regulatory mode is "off" - otherwise it keeps reconnecting all the time...

    I'd vote for "off" as a default value, since according to the above and what I could google out, it causes less problems with various wifi clients than "d" or "h" modes. Anyway - not a big deal, the option is still available and can be set to "h" if that works better for you .

  7. #157
    Quote Originally Posted by teddy_bear View Post
    I'd vote for "off" as a default value
    +1, completely agree

  8. #158
    Join Date
    Dec 2007
    Location
    The Netherlands - Eindhoven
    Posts
    1,767
    a bit offtopic, but:
    I completed my own firmware compiles successfully thanks to the wiki on googlecode

    Now can I use "export PATH=$PATH:/opt/brcm/hndtools-mipsel-uclibc/bin" for other projects to cross compile?

    since I'm trying to get the master make file to work... but the openwrt svn is offline so it wont complete

  9. #159
    Join Date
    Nov 2006
    Location
    Russia, Moscow
    Posts
    3,640
    Quote Originally Posted by wpte View Post
    Now can I use "export PATH=$PATH:/opt/brcm/hndtools-mipsel-uclibc/bin" for other projects to cross compile?
    Yes, you may. But toolchain from wl500g.googlecode.com is incompatible with optware since it uses different uClibc (0.9.29 vs. 0.9.28.2).

  10. #160
    Join Date
    Dec 2007
    Location
    The Netherlands - Eindhoven
    Posts
    1,767
    Quote Originally Posted by lly View Post
    Yes, you may. But toolchain from wl500g.googlecode.com is incompatible with optware since it uses different uClibc (0.9.29 vs. 0.9.28.2).
    but it uses the uclibc in oleg firmware right?
    or won't I be able to run it on the router?

    btw, I get as build system when I do a configure: i686 architecture... that's not right I guess? :P

  11. #161
    Join Date
    Nov 2006
    Location
    Russia, Moscow
    Posts
    3,640
    Quote Originally Posted by wpte View Post
    but it uses the uclibc in oleg firmware right?
    or won't I be able to run it on the router?
    Old "Classic" Oleg firmwares uses uClibc 0.9.19, we upgrade it to 0.9.29. Some old binaries can run new libc, but mostly not. optware seeks for /opt/lib/libc.so.0 by default, this allows usage of two versions of uClibc simultaneously.

    btw, I get as build system when I do a configure: i686 architecture... that's not right I guess? :P
    Typically, you should issue:
    Code:
    ./configure --host=mipsel-linux
    for cross-compilation.

  12. #162
    Join Date
    Dec 2007
    Location
    The Netherlands - Eindhoven
    Posts
    1,767
    thanks lly, works great
    way better than the optware cross compiler imo

  13. #163
    Join Date
    Dec 2007
    Location
    The Netherlands - Eindhoven
    Posts
    1,767
    Hey, I found out this morning that r273 has a non working webcam

    I have a logitech quickcam 4000
    and when connecting it acts normal:
    May 3 00:13:31 kernel: hub.c: new USB device 01:03.0-2, assigned address 2
    May 3 00:13:31 kernel: usb.c: USB device 2 (vend/prod 0x46d/0x8b2) is not claimed by any active driver.
    May 3 00:13:31 USB webcam: attached
    May 3 00:14:14 kernel: pwc Philips webcam module version 9.0.2 loaded.
    May 3 00:14:14 kernel: pwc Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
    May 3 00:14:14 kernel: pwc Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
    May 3 00:14:14 kernel: pwc the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
    May 3 00:14:14 kernel: pwc Default image size set to vga [640x480].
    May 3 00:14:14 kernel: usb.c: registered new driver Philips webcam
    May 3 00:14:14 kernel: pwc Logitech QuickCam 4000 Pro USB webcam detected.
    May 3 00:14:14 kernel: pwc Registered as /dev/video0.
    May 3 00:14:14 kernel: pwc Philips webcam decompressor routines version 9.0-BETA-2
    May 3 00:14:14 kernel: pwc Supports all cameras supported by the main module (pwc).
    May 3 00:14:15 kernel: pwc Failed to set LED on/off time.
    like any other time...

    because in the changelog there is something about a fix for webcams on usb-hubs, I tought of trying to connect it to the usb-hub wich resulted in this:
    May 3 10:49:48 kernel: hub.c: new USB device 01:03.2-1.4, assigned address 5
    May 3 10:49:48 kernel: usb.c: unable to get device descriptor (error=-32)
    May 3 10:49:48 kernel: hub.c: new USB device 01:03.2-1.4, assigned address 6
    May 3 10:49:48 kernel: usb.c: unable to get descriptor
    May 3 10:49:48 kernel: usb.c: unable to get device 6 configuration (error=-32)
    I have a full 2.0 usb hub and all my hdd work on it

    well, the only thing I can see is a grey image with the time displayed on right bottom...
    kinda weird, because rcamdmain and rcamd are started

  14. #164
    lly firmware makes me interested in studing wl-500gx again!!

    After one day i installed r273 firmwareon wl-500gx, it shows below error message, and it seemed to occure in Oleg firmware as well. any idea to resolve it, please. Or it's a known bug in both firmware of oleg and lly?

    With making a google for possible rooted cause, it looks like one non-proper interface configuration in lo. So I try to re-config lo by "ifup lo", there seems no this commend by error message shown "-sh: ifup: not found"

    Thanks a lot!

    smbd[296]: [2009/05/08 02:24:01, 0] lib/util_sock.cpen_socket_in(826)
    smbd[296]: Get_Hostbyname: Unknown host wl-500gx@RR
    smbd[296]: [2009/05/08 02:24:01, 0] smbd/oplock.cpen_oplock_ipc(93)
    smbd[296]: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was No such file or directory
    smbd[297]: [2009/05/08 02:24:01, 0] lib/util_sock.cpen_socket_in(826)
    smbd[297]: Get_Hostbyname: Unknown host wl-500gx@RR
    smbd[297]: [2009/05/08 02:24:01, 0] smbd/oplock.cpen_oplock_ipc(93)
    smbd[297]: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was No such file or directory
    smbd[298]: [2009/05/08 02:24:02, 0] lib/util_sock.cpen_socket_in(826)
    smbd[298]: Get_Hostbyname: Unknown host wl-500gx@RR
    smbd[298]: [2009/05/08 02:24:02, 0] smbd/oplock.cpen_oplock_ipc(93)
    smbd[298]: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was No such file or directory

  15. #165
    i get he answer for no ifup, becasue there's no ifup in busybox of lly firmware. It currently defined functions:

    [, [[, arping, ash, awk, basename, busybox_httpd, cat, chgrp, chmod, chown, chroot, cmp, cp, crond, crontab, cut, date, dd, df, dirname, dmesg, du, e2fsck, echo, env, ether-wake, expr, false, fdisk, free, fsck.ext2, fsck.ext3, fuser, grep, gunzip, gzip, head, hexdump, hostname, hwclock, ifconfig, insmod, ipcalc, kill, killall, klogd, ln, logger, login, ls, lsmod, md5sum, mkdir, mke2fs, mkfifo, mkfs.ext2, mkfs.ext3, mknod, mkswap, modprobe, more, mount, mv, netstat, nice, nohup, nslookup, od, passwd, pidof, ping, pivot_root, printf, ps, pwd, realpath, renice, rm, rmdir, rmmod, route, sed, seq, sh, sleep, sort, strings, stty, su, swapoff, swapon, sync, syslogd, tail, tar, tee, telnet, telnetd, test, tftp, time, top, touch, tr, traceroute, true, tty, udhcpc, umount, uname, uniq, uptime, usleep, uuencode, vconfig, vi, watch, wc, wget, yes, zcat


    Quote Originally Posted by purpleray View Post
    lly firmware makes me interested in studing wl-500gx again!!

    After one day i installed r273 firmwareon wl-500gx, it shows below error message, and it seemed to occure in Oleg firmware as well. any idea to resolve it, please. Or it's a known bug in both firmware of oleg and lly?

    With making a google for possible rooted cause, it looks like one non-proper interface configuration in lo. So I try to re-config lo by "ifup lo", there seems no this commend by error message shown "-sh: ifup: not found"

    Thanks a lot!

    smbd[296]: [2009/05/08 02:24:01, 0] lib/util_sock.cpen_socket_in(826)
    smbd[296]: Get_Hostbyname: Unknown host wl-500gx@RR
    smbd[296]: [2009/05/08 02:24:01, 0] smbd/oplock.cpen_oplock_ipc(93)
    smbd[296]: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was No such file or directory
    smbd[297]: [2009/05/08 02:24:01, 0] lib/util_sock.cpen_socket_in(826)
    smbd[297]: Get_Hostbyname: Unknown host wl-500gx@RR
    smbd[297]: [2009/05/08 02:24:01, 0] smbd/oplock.cpen_oplock_ipc(93)
    smbd[297]: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was No such file or directory
    smbd[298]: [2009/05/08 02:24:02, 0] lib/util_sock.cpen_socket_in(826)
    smbd[298]: Get_Hostbyname: Unknown host wl-500gx@RR
    smbd[298]: [2009/05/08 02:24:02, 0] smbd/oplock.cpen_oplock_ipc(93)
    smbd[298]: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was No such file or directory

Page 11 of 48 FirstFirst ... 91011121321 ... LastLast

Similar Threads

  1. Probleme mit der Oleg firmware
    By errox in forum German Discussion - Deutsch (DE)
    Replies: 15
    Last Post: 14-06-2008, 22:26
  2. new firmware 1.9.2.7-8 by oleg
    By alien433 in forum WL-500gP Firmware Discussion
    Replies: 31
    Last Post: 24-01-2008, 20:31
  3. Oleg firmware not working.
    By wpte in forum WL-500gP Q&A
    Replies: 6
    Last Post: 07-01-2008, 12:48
  4. C Compiler voor de oleg firmware
    By wouzs in forum Dutch Discussion - Nederlands
    Replies: 1
    Last Post: 28-10-2007, 15:57

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •