Oleg's firmware and wl500gp v2

[AnyOne]

Does oleg firmware works on a wl500gp v2?

[ph34b0t]

I tried the firmware file:
WL500gp-1.9.2.7-9.zip

but it wasnt possible to put it on thr router (msg: wrong version ....)
i read in another thread that there s a hardware difference between
gp and gp v2. so the firmware will not work...

my question is the following:
will there be an oleg firmware for the v2 of wl500gp ???...

or is there another way to make the -9 firmware work???

thx in advance

[al37919]

Firmwares for Premium v1 and v2 are incompatible.

According to Oleg, the next 10th release will contain v2 support. If you have enough courage you may test a pre-release available here:

Discussion (in Russian): http://wl500g.info/showthread.php?t=13567
Firmware: http://oleg.wl500g.info/10-pre/

Important: after flashing from another firmware reset the router to default settings.

[Wally]

I have enough courage and tested it (WL500gpv2-1.9.2.7-10-pre4.trx), but after flashing AP didnt boot-up. It jumped only to recovery mode. After flashing original fw again, everything was ok. I dont have AP connected to serial console, so I cant say more, why it didnt boot up.

[ph34b0t]

haha.. i dont have the courage :-D

but iam really looking forward to the -10 release

hope it wont take too long .....

[al37919]

I have enough courage and tested it (WL500gpv2-1.9.2.7-10-pre4.trx), but after flashing AP didnt boot-up. It jumped only to recovery mode. After flashing original fw again, everything was ok. I dont have AP connected to serial console, so I cant say more, why it didnt boot up.

I think it would be nice if you post your experience in this Russian thread. It seems that at the moment there is lack of people who own this device and have enough experience to test it. Don't worry about your English.

[Oleg]

I have enough courage and tested it (WL500gpv2-1.9.2.7-10-pre4.trx), but after flashing AP didnt boot-up. It jumped only to recovery mode. After flashing original fw again, everything was ok. I dont have AP connected to serial console, so I cant say more, why it didnt boot up.

Try flashing using firmware restoration utility or tftp. Your flash seems was incomplete, so it was in restoration mode: firmware had no chance to start at all.

[Wally]

Yes, really. File was incomplete (my was 3,5MB and right was 3,6MB). Now I had download it again but I can try it tomorrow. I flashed it via restoration utility, because web interface was not able to upload it (there was error with wrong version or something).

[Wally]

So I tried flash it again with whole file and now it seems much better. It looks like everything works ok, but I have tested it shortly yet, so I will see more in next few days.

[lamocch]

Hello, i've a WL-500G Premium V2 and install this firmware (WL500gpv2-1.9.2.7-10-USB-1.69.trx) so i can plug an huawei e220(try vodafone and Kanguru). But in the end just blinks a blue light.

Here are the system logs:

With the option GPRS:
Jan 1 00:00:04 kernel: usb.c: registered new driver usbdevfs
Jan 1 00:00:04 kernel: usb.c: registered new driver hub
Jan 1 00:00:04 kernel: usb-ohci.c: USB OHCI at membase 0xb8003000, IRQ 6
Jan 1 00:00:04 kernel: usb-ohci.c: usb-00:03.0, PCI device 14e4:471a
Jan 1 00:00:04 kernel: usb.c: new USB bus registered, assigned bus number 1
Jan 1 00:00:04 kernel: Product: USB OHCI Root Hub
Jan 1 00:00:04 kernel: SerialNumber: b8003000
Jan 1 00:00:04 kernel: hub.c: USB hub found
Jan 1 00:00:04 kernel: hub.c: 2 ports detected
Jan 1 00:00:04 kernel: ehci_hcd 00:03.1: PCI device 14e4:471a
Jan 1 00:00:04 kernel: ehci_hcd 00:03.1: irq 6, pci mem b8003800
Jan 1 00:00:04 kernel: usb.c: new USB bus registered, assigned bus number 2
Jan 1 00:00:04 kernel: ehci_hcd 00:03.1: illegal capability!
Jan 1 00:00:04 kernel: ECHI PCI device 471a14e4 found.
Jan 1 00:00:04 kernel: PCI: 00:03.1 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
Jan 1 00:00:04 kernel: ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
Jan 1 00:00:04 kernel: Manufacturer: Linux 2.4.20 ehci_hcd
Jan 1 00:00:04 kernel: Product: PCI device 14e4:471a
Jan 1 00:00:04 kernel: SerialNumber: 00:03.1
Jan 1 00:00:04 kernel: hub.c: USB hub found
Jan 1 00:00:04 kernel: hub.c: 2 ports detected
Jan 1 00:00:05 kernel: hub.c: new USB device 00:03.1-1, assigned address 2
Jan 1 00:00:05 kernel: hub.c: USB hub found
Jan 1 00:00:05 kernel: hub.c: 2 ports detected
Jan 1 00:00:06 kernel: hub.c: new USB device 00:03.1-1.2, assigned address 3
Jan 1 00:00:06 kernel: usb.c: not enough configurations
Jan 1 00:00:06 kernel: usb.c: unable to get device 3 configuration (error=-22)
Jan 1 00:00:06 kernel: hub.c: new USB device 00:03.1-1.2, assigned address 4
Jan 1 00:00:06 kernel: usb.c: not enough configurations
Jan 1 00:00:06 kernel: usb.c: unable to get device 4 configuration (error=-22)
Jan 1 00:00:07 kernel: usb.c: registered new driver usblp
Jan 1 00:00:07 kernel: printer.c: v0.13: USB Printer Device Class driver
Jan 1 00:00:08 kernel: Linux video capture interface: v1.00
Jan 1 00:00:08 kernel: SCSI subsystem driver Revision: 1.00
Jan 1 00:00:09 kernel: Initializing USB Mass Storage driver...
Jan 1 00:00:09 kernel: usb.c: registered new driver usb-storage
Jan 1 00:00:09 kernel: USB Mass Storage support registered.
Jan 1 00:00:10 kernel: usb.c: registered new driver acm
Jan 1 00:00:10 kernel: acm.c: v0.22:USB Abstract Control Model driver for USB modems and ISDN adapters (GTRAN patched)
Jan 1 00:00:10 kernel: usb.c: registered new driver serial
Jan 1 00:00:10 kernel: usbserial.c: USB Serial support registered for Generic
Jan 1 00:00:10 kernel: usbserial.c: USB Serial Driver core v1.4
Jan 1 00:00:10 kernel: usbserial.c: USB Serial support registered for Modem
Jan 1 00:00:10 kernel: modem.c: GSM/CDMA modem driver v0.1
Jan 1 00:00:10 kernel: usbserial.c: USB Serial support registered for PL-2303
Jan 1 00:00:10 kernel: pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.10.1
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for FTDI SIO
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for FTDI 8U232AM Compatible
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for FTDI FT232BM Compatible
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for FTDI FT2232C Compatible
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for FTDI FT232R Compatible
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for USB-UIRT Infrared Tranceiver
Jan 1 00:00:11 kernel: usbserial.c: USB Serial support registered for Home-Electronics TIRA-1 IR Transceiver
Jan 1 00:00:11 kernel: ftdi_sio.c: v1.3.5r1:USB FTDI Serial Converters Driver
Jan 1 00:00:17 pppd[136]: In file /tmp/ppp/peers/gprs: unrecognized option '/dev/usb/tts/0'
Jan 1 00:00:47 pppd[164]: In file /tmp/ppp/peers/gprs: unrecognized option '/dev/usb/tts/0'
Jan 1 00:01:18 pppd[191]: In file /tmp/ppp/peers/gprs: unrecognized option '/dev/usb/tts/0'
Jan 1 00:01:49 pppd[218]: In file /tmp/ppp/peers/gprs: unrecognized option '/dev/usb/tts/0'


With "user define" and a dial-up file:
Jan 1 00:00:09 kernel: usb.c: registered new driver usb-storage
Jan 1 00:00:09 kernel: USB Mass Storage support registered.
Jan 1 00:00:10 kernel: usb.c: registered new driver acm
Jan 1 00:00:10 kernel: acm.c: v0.22:USB Abstract Control Model driver for USB modems and ISDN adapters (GTRAN patched)
Jan 1 00:00:10 kernel: usb.c: registered new driver serial
Jan 1 00:00:10 kernel: usbserial.c: USB Serial support registered for Generic
Jan 1 00:00:10 kernel: usbserial.c: USB Serial Driver core v1.4
Jan 1 00:00:17 pppd[125]: In file /tmp/ppp/peers/gprs: unrecognized option '/dev/usb/tts/0'
Jan 1 00:00:47 pppd[145]: In file /tmp/ppp/peers/gprs: unrecognized option '/dev/usb/tts/0'

Tried also, some dial ups, chosing -user define- upload the dial file than the APN data, but the huawei e220 just blinks a blue light.

As anyone have installed this modem with success on a V2?

Great forum guys

Greatings from Portugal

Thanks in advance for any help or

[newbiefan]

Ask Engy, he is one of the developer of the koppel FW.
Koppel FW is based on Olegs FW and has some features for modems.
You can ask here: http://koppel.cz/cdmawifi/english/

But as first try: at the console perform a 'killall pppd' and wait some seconds.
If modem connects now, just use the script from howto.


Have fun

[AnyOne]

ive tryed to flash buf after doing the nvram stuff the 4 lan + wan lights are up and the air and power are off....

did i just bricked my router???

[newbiefan]

ive tryed to flash buf after doing the nvram stuff the 4 lan + wan lights are up and the air and power are off....

did i just bricked my router???

More information is necessary. FW, which Howto, Router Type, what have you done with nvram (stuff???) and so on.

[againmoon]

I have the same problem of lamocch, even if I use an other modem
With V1 it worked....
I would like to know if anybody tested a modem usb connection in V2.
Just to know....
Maybe power problems but in this http://koppel.cz/cdmawifi/english/
lamocch said no change with powered usb hub

[AnyOne]

More information is necessary. FW, which Howto, Router Type, what have you done with nvram (stuff???) and so on.

wl500gp v2, ive uploaded oleg firmware and it worked then i did the commands to "expand" the memory but after that they router didnt booted anymore