[EMAIL PROTECTED] wrote:
> Here is the code I am running (the patch Phil mentioned above) that
> alleviated my problems with syscall():
[snip]
> This has worked for me. Replace the beginning of sys_syscall() in
> arch/arm/kernel/entry-common.S with what I have above, and it should
> work.
>
Hmmm... I tried this change, however I'm getting garbage like:
^@^@^@��^EN^U^[S^]/etc/rc.d/rc: /var/run/runlevel.dir: Read-only file
system
^@^@^@��^EN^U^[S^]^@^@^@��^EN^U^[S^]^@^@^@��^EN^U^[S^]Bringing up
interface lo
^@^@^@��^EN^U^[S^]^@^@^@��^EN^U^[S^]^@^@^@��^EN^U^[S^]modprobe: can't
locate module net-pf-6
modprobe: can't locate module net-pf-4
modprobe: can't locate module net-pf-5
^@^@^@��^EN^U^[S^]modprobe: can't locate module net-pf-6
...etc.
I also tried the change as Russell gave last week,
> The code around sys_syscall should read:
> add ip, sp, #4
> ldmleib ip, {r0 - r4}
Which did not have such side effects, but the command `loglevel 1'
displays
`syslog: Invalid argument', same as before. As best as I can tell, the
command `/sbin/loglevel 1' calls (eventually, thru swi) do_syslog(type=2
buf=<NULL> len=1). This seems to be an improvement, but it still isn't
working. :/ buf and len seem to be set correctly (loglevel 3 seems to
call do_syslog(type=2, buf=<NULL>, len=3) ), but type should be 8.
Thoughts, suggestions, comments?
(Incedentally, this also appears to break xntpd's setting of the date on
bootup, though I can't guarrantee that is related. I'll try some checks
on this...)
Eli
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
