I tried again with an N900 and that worked. Maybe something changed in RS232
handling? With an RS232 modem on atmel_usart the modem is no longer
detected.
2011/2/3 toabctl
> Hi,
>
> i tried the latest git version of modemmanager
> (8f223f45f9e0c81fc9267b830c7c05b9aa731f2a) on debian squeeze (i38
Hi,
I recently got my hands on a MOSCHIP MCS7832 NIC (USB, fast
ethernet) and NM (0.8.1) immediately starts connecting through it - even
when there's no cable attached!
My question is - whose job is it to watch/detect link state changes when a
cable is (dis-)connected? ethtool and mii-tool both
Hi,
i tried the latest git version of modemmanager
(8f223f45f9e0c81fc9267b830c7c05b9aa731f2a) on debian squeeze (i386 and
armel) but modemmanager does nothing more than loading plugins. Here's the
debug output:
modem-manager --debug
modem-manager[28478]: [1296750276.586230] [main.c:167] main():
Hello.
I am using NetworkManager 0.8.1-10.git20100831 in Fedora 14.
I had a problem: the dhcp client in NM does not send FQDN updates to the
server, so I could not use mine over the network.
I saw that many other people are complaining about this on the web, so I
made a patch that fixed up things.
Hi,
I have bug reports about some inconsistencies caused by the state file and
rfkill
interactions like when the user kills the radio and then re-enables it, the
WLAN can't be enabled
unless the state file is edited manually as root, etc.
I think that when the system is booted, NM should ignore
Hello
nm uses dnsmasq as dhcp and dns server for attached clients, handled
via nm-dnsmasq-manager[1].
it uses hard coded parameters which proved to be problematic in the
past (i stumbled upon the stand alone dnsmasq vs. nm-dnsmasq conflict
before).
my problem/use case is a lan, where i want to us
