You tried it with th IP port and 9101 for USB?
Tried the test firmware, but unfortunately got exactly the same problem.
Printer is an HP PSC 2210.
Below the log:
Apr 18 13:15:22 WL500g user.warn klogd: Oops in fault.c::do_page_fault, line 192:
Apr 18 13:15:22 WL500g user.warn klogd: $0 : 00000000 c00a0000 0000006e c00a77a7 c00a7f3f 00000000 ffffffff c00a7ef8
Apr 18 13:15:22 WL500g user.warn klogd: $8 : 00004366 0000000a 00000000 00000000 8019132a fffffff9 0000000a 807bdcb2
Apr 18 13:15:22 WL500g user.warn klogd: $16: 00000001 80133058 80a2cc02 00000000 807fc3b8 80ac2800 00000000 c009c460
Apr 18 13:15:22 WL500g user.warn klogd: $24: ffffffff 00000002 807bc000 807bdde0 00000000 c00a5440
Apr 18 13:15:22 WL500g user.warn klogd: Hi : 00000000
Apr 18 13:15:22 WL500g user.warn klogd: Lo : 00000042
Apr 18 13:15:22 WL500g user.warn klogd: epc : c00a53b4 Not tainted
Apr 18 13:15:22 WL500g user.warn klogd: Status: 1000fc03
Apr 18 13:15:22 WL500g user.warn klogd: Cause : 00000008
Apr 18 13:15:22 WL500g user.warn klogd: Process khubd (pid: 533, stackpage=807bc000)
Apr 18 13:15:22 WL500g user.warn klogd: Stack: c00a773c 00000000 0000009e 80a2cc02 00000001 00000000 80a2cc00
Apr 18 13:15:22 WL500g user.warn klogd: 000003ff 80ac2a00 c00a5000 c00a7844 80010fac c00a6ec8 c00a6e4c c00a79c0
Apr 18 13:15:22 WL500g user.warn klogd: 80183a64 807fc6a0 00000002 00000001 00000000 00000002 000003f0 00002911
Apr 18 13:15:22 WL500g user.warn klogd: 807fc383 0030706c 80ac49e0 c00a7df8 00000001 c00a7db4 c00a7e18 c008b484
Apr 18 13:15:22 WL500g user.warn klogd: c008bf90 00000190 c0080008 c009c5e0 80010fac 80ac2828 00000018 00000002
Apr 18 13:15:22 WL500g user.warn klogd: 80ac2800 ...
Apr 18 13:15:22 WL500g user.warn klogd: Call Trace: [<c00a773c>] [<c00a7844>] [<80010fac>] [<c00a6ec8>] [<c00a6e4c>]
Apr 18 13:15:22 WL500g user.warn klogd: [<c00a79c0>] [<c00a7df8>] [<c00a7db4>] [<c00a7e18>] [<c008b484>] [<c008bf90>]
Apr 18 13:15:22 WL500g user.warn klogd: [<c0080008>] [<c009c5e0>] [<80010fac>] [<c008b2c4>] [<c008b0f4>] [<c008b960>]
Apr 18 13:15:22 WL500g user.warn klogd: [<c0095fc4>] [<80010fac>] [<c009c4c4>] [<c008e4d4>] [<c008e460>] [<80010fac>]
Apr 18 13:15:22 WL500g user.warn klogd: [<c0090964>] [<c009a7ac>] [<c00901c4>] [<c008f2fc>] [<80010fac>] [<c00906d0>]
Apr 18 13:15:22 WL500g user.warn klogd: [<c0090ca0>] [<8000d04c>] [<8000cda8>] [<c009c4d0>] [<8000eb64>] [<8000ea80>]
Apr 18 13:15:22 WL500g user.warn klogd: [<c009c4e0>] [<c009c4d0>] [<c0090a50>] [<c0090fe4>] [<800113f4>] ...
Apr 18 13:15:22 WL500g user.warn klogd:
Apr 18 13:15:22 WL500g user.warn klogd: Code: 10a00021 00008021 24a50004 <80a30000> 2402003b 10620003 00003021 1200000c 00a01821
You tried it with th IP port and 9101 for USB?
There's no need to test it with the print daemon, because it's not starting, and the printer module crashes...
I'm wondering why All-in-One printers not working with this.
(Yeah my Borther printer also a scanner, fax, photocopy, and things like that )
Josephus
HuWiCo - Hungarian Wireless Community
http://www.huwico.hu
With the standard Asus firmware the printer is working, including the card reader.
1000 THX to OLEG
the new driver works 100% with my Epson Stylus Photo R300
THX
THX
Ok, I will try to determine the reason for that. Stay tuned, probably I will ask you for additional information.Originally posted by ebakke
With the standard Asus firmware the printer is working, including the card reader.
Finally what is needed: to whom who has kernel oopses, please perform these steps - boot with printer attached, establish the telnet/ssh session and execute these commands:
You need to have ftp server enabled in the system settings. Probably there will be an errors during the execution of the first command, but this is ok. Also, no USB drive required for this to work. You need to use latest test firmware.Code:/init/ftpdserver mount -t ramfs none /mnt/usbfs/ cp /proc/ksyms /proc/modules /etc/linuxigd/syslog.log /mnt/usbfs/ stupid-ftpd
After that you should start the ftp client and connect to wl500g via ftp. Copy 3 files named ksyms, modules & syslog.log to your local drive, compress(zip) them and attach to the reply of this message.
Guys, finally it's seems I've found an error in the ASUS stuff. Please try using this firmware. Hopefully it will fix kernel oopses. Please let me know if it's working now.
Regards, Oleg.
Tested the latest firmware (test3). Unfortunately I still have problems, although seems to recognize the printer.
Attached the log with the Oops error.
2 questions.
One question I have, related to published rootfs, do I need to update that as well? If so, how should I do this, as I cannot find any info related to that.
Other question, are the bootloader (2.2) and hardware (1.0) version also important?
Let me know if I need to do some other tests.
Erik
Ok, found another piece of shit. Try this one.
For others - no & no.