Hi Jeremy Foshee,
please note that I ran 'apport-collect -p linux 408555' on the EeePC 1000H but the problem exists also on any PC.
The procedure I used to send the 'apport-collect' data was:
- Boot without the modem
- modem attached, CD-ROM icon appear, right click it and 'eject' drive
(modem changed from 19d2:2000 to 19d2:0031)
- network manager did not 'see' the modem
- dmesg show a looping creation (or 'attachment') of ttyUSBx ports and then disconnection
To 'send' the report I had to connect with the same modem (MF636):
- modem removed
- sudo stop network-manager
- sudo killall modem-manager
- sudo pppd ttyUSB2 nodetach defaultroute noipdefault lock usepeerdns connect 'chat "" "at" "" "at" "OK"...
- from new terminal window: apport-collect -p linux 408555
and finally I followed directions to send it.
Hi Jeremy Foshee,
please note that I ran 'apport-collect -p linux 408555' on the EeePC 1000H but the problem exists also on any PC.
The procedure I used to send the 'apport-collect' data was:
- Boot without the modem
- modem attached, CD-ROM icon appear, right click it and 'eject' drive
(modem changed from 19d2:2000 to 19d2:0031)
- network manager did not 'see' the modem
- dmesg show a looping creation (or 'attachment') of ttyUSBx ports and then disconnection
To 'send' the report I had to connect with the same modem (MF636):
- modem removed
- sudo stop network-manager
- sudo killall modem-manager
- sudo pppd ttyUSB2 nodetach defaultroute noipdefault lock usepeerdns connect 'chat "" "at" "" "at" "OK"...
- from new terminal window: apport-collect -p linux 408555
and finally I followed directions to send it.
Regards,
George