News:

Registered a URL and setup a forum as the IPCam stuff really needed its own site vs my irregular blog posts about IPCam hacking at http://www.computersolutions.cn/blog

Author Topic: ifconfig: socket: Operation not permitted  (Read 8973 times)

June 04, 2011, 02:22:10 am
I decided to get the linux.bin from original software and rom.bin from Lawrence.
Flashed both of them and run. The BusyBox run OK but the network services are not. Seems like I didn't set some permissions.

Here is the log from console:

Quote
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
init started:  BusyBox v0.60.4 (2011.02.13-21:55+0000) multi-call binary
new USB device :80783004-7e8740
hub.c: new USB device 1, assigned address 2
detect_sensor: mi360
ifconfig: socket: Operation not permitted
Jan  1 00:00:08 1970 dhcpcd[25]: dhcpStart: socket: Operation not permitted

ifconfig: socket: Operation not permitted
socket: Operation not permitted
can't find service
Unable to create socket
close on exec: : Bad file descriptor
setsockopt: : Bad file descriptor
Unable to bind server socket: : Bad file descriptor
Unable to listen to socket
Unable to create socket
close on exec: : Bad file descriptor
setsockopt: : Bad file descriptor
Unable to bind server socket: : Bad file descriptor
Unable to listen to socket
Unhandled fault: external abort on linefetch (F4) at 0x00000001
fault-common.c(97): start_code=0x8040, start_stack=0x11f6c)
28: EMT trap
dvm cmos successfully initialized
dvm camera registered as video0
socket: Operation not permitted


BusyBox v0.60.4 (2011.02.13-22:34+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

Could any one help me to resolve that issue?

  • No avatar
  • *****
June 04, 2011, 02:12:51 pm
It means that it didn't get a network driver installed correctly.

You need the right drivers in the kernel for your hardware. 

June 04, 2011, 05:15:20 pm
I got this linux.bin from official software. I thought, all the drivers should be there. A I understood rom.bin consits only applications not drivers.

  • No avatar
  • *****
June 04, 2011, 06:30:47 pm
Paste the boot log

  • No avatar
  • *****
June 12, 2011, 08:02:37 pm
Oops, should have noted you said original linux bin.

They don't initialise the drivers in their firmware, so if you want to use network, you either need to run the camera app, or initialize usb (for wifi), then load the relevant module init code.

Don't forget their way is to statically compile drivers into the kernel, so no insmod..
Need to call the module_init() code to load them I think (I need to check on that though), might also be register_netdev()

This seems to make sense -
http://books.google.com/books?id=yy7tihZLgGYC&pg=PT154&lpg=PT154&dq=module_init+statically&source=bl&ots=ND5jifCjd0&sig=BGRYHtp5UO7yjeumfARuRuKOwe0&hl=en&ei=0U71TZz9HYi-vgPy_Zy5Bg&sa=X&oi=book_result&ct=result&resnum=1&ved=0CBQQ6AEwADgU#v=onepage&q=module_init%20statically&f=false

Perhaps someone with better linux experience than me can add some more clarity..