Suchergebnisse

What happens when you eject the usb device(s) using the avm web front-end?

Unfortunately, I have only very limited resources at the moment... It would be interesting to see the log produced during umount and detachment. How did you unmount the partitions/stick? I have noticed that some usb hubs require an active power supply: it seems as if the internal power of...

Erledigt;)

Check out this ip-forum thread. There's a freetz patch here, though it hasn't been tested with the all-in-one.

Arbitrarily setting STD_PRINTK does not work either... I did the following: echo STD_PRINTK >/dev/debug press the dial (green) button on the handset after several seconds (up to 30s) the handset says system not available or something simular press the hangup (red) button on the handset...

Yep, http://trac.freetz.org/changeset/2538/trunk/patches/180-printk.sh?old=1994&old_path=trunk%2Fpatches%2F180-printk.sh was the problem. Although it's odd, reverting this patch lets the MC-T reconnect to the 7270. The patch seems harmless enough, I wonder why exactly AVM requires this in...

Looking at the changset 2531:2561, there are only two I can see that may adversely effect dect registration: http://trac.freetz.org/changeset/2538/trunk/patches/180-printk.sh?old=1994&old_path=trunk%2Fpatches%2F180-printk.sh http://trac.freetz.org/changeset/2561 dos endline convention for...

Backing down to r2531 seems to be working;) Tomorrow (do I mean today?) or maybe sunday I try to follow the changes sets till it stops working...

I rebooted the 7270 and restored the factory defaults in the handset and recycled the power, subsequently preformed the registration to no avial As instructed, I created the nodes eeprom[12] /dev # ls -l /dev/eeprom* crw-rw-rw- 1 root root 239, 0 Jan 1 2000 /dev/eeprom...

It used to be that the my AVM MC-T DECT handset would automatically reregister itself with the 7270 after flashing. Since 2531 or so (I'm not sure) this no longer happens. In fact I can't register the handset at all. I've done the following to no avail: reset the handset reset the handset...

I'm having problems manually loading the module Piglet_noemif using modprobe. During boot I drop into ashecho 'kernel_args init=/bin/ash' >/sys/kernel/urlader/environment Mount all virtual filesystems/lib/mdev/misc/virtual_fs mount Load the piglet as in usbroot...

Although it shouldn't much matter, I'm logging to a file1544 root 1176 S syslogd -L -O /var/log/messages -b 3 -s 100

Yes, the complete mdev configuration is conceptually a re-entrant. There are, however two places where different process groups could converge: 1) handling of devmap (reporting to avm web pages, in /lib/mdev/interface) 2) sessions when more than one partition is linked with a concurrent...

olistudent had written these effects to me just after I released the last version (now unavailable). I had noticed the process groups always end with 'logger'. It would be interesting if olistudent could dispatch any logger command successfully on the command line. @olistudent I wonder do you...

Version 0.6.2 released. retracted olistudent was kind enough to warn about a few discrepancies, to fast for my own good:-Ö

As I have stated, the patches were generated against r2524. The second patching error may be solved by turning up the fuzz factor (-F) in patch (w/o guaranty).

After looking at the freetz timeline, it's seems as if r2525 introduces a change to fstab that adversely effects the patches/cond/mdev_fstab.patch. Will be fixed in the next mdev version...

I think it best to wait until it plays nicely with usbroot;)

Did you apply all the patches in the very first posting? I think you forgot one...

Could you be a little more informative? Which freetz version are you using? This seems to work fine against 2524...