Sponsored Content
Operating Systems Linux Ubuntu Does /dev/ttyUSB* causing my usb 3G Dongle doesn't work when plug-in Post 302505364 by jao_madn on Wednesday 16th of March 2011 06:59:33 PM
Old 03-16-2011
Sorry i already created the topic about this one..i forget since no one address my problem and also i wait for any responce maybe someone knows or solved the problem. Just now i decided to tacke this issue not like before im afraid i will lose my internet connection in the process since this is the only way i can connect to the internet.

By the way i just solved my problem by installing the package usb-modeswitch

Some add info

My USB dongle is HUAWEI E169u, Asus Laptop, and Lucyd lynx. kernel linux 2.6.32-30-generic

Thanks for the reply..
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

USB Hot Plug Mandrake 9.0

I recently installed Mandrake Linux 9.0 on my intel machine, with a view to migrating completely from Windows within the next few months. First I need to get things working. My modem, sound card, scanner and printer all fail to work. This isn't going to put me off because I love the interface... (1 Reply)
Discussion started by: saabir
1 Replies

2. Shell Programming and Scripting

Some env setting is causing the script not to work ?

Not sure what has changed in the Unix environment. The following script which was working is now not working. #!/usr/bin/ksh # ----------------------------------------------------------------------------- # File: monitor_db.sh # #... (1 Reply)
Discussion started by: uuser
1 Replies

3. UNIX for Dummies Questions & Answers

Script doesn't work, but commands inside work

Howdie everyone... I have a shell script RemoveFiles.sh Inside this file, it only has two commands as below: rm -f ../../reportToday/temp/* rm -f ../../report/* My problem is that when i execute this script, nothing happened. Files remained unremoved. I don't see any error message as it... (2 Replies)
Discussion started by: cheongww
2 Replies

4. Filesystems, Disks and Memory

Cant' mount usb drive, /dev/sda1 not showing up

Hi, I'm trying to mount a usb drive but the path /dev/sda1 does not show up under /dev when I plug in the usb device. In fact I see no differences under /dev before and after I plugin my usb drive. Any ideas why the system is not recognizing the usb drive and how to fix? This is on a... (3 Replies)
Discussion started by: orahi001
3 Replies

5. UNIX for Advanced & Expert Users

/dev not updated on usb device removal

Hello all :-) i'm not sure if its a beginner or advanced question but i have the following problem - now for some months after building a kernel from source (2.6.36 and now 2.6.38) the /dev/sd* entries are not removed if a remove the corresponding usb disk, sd card, what ever. i'm pretty sure... (0 Replies)
Discussion started by: apfelkuchen
0 Replies

6. UNIX for Advanced & Expert Users

Disk /dev/sdb doesn't contain a valid partition table

Hello, I have rebooted the RHEL VM but after rebooting the vm it not showing all the partition mounted on OS level, if i'll execute the fdisk -l command, then i'm able to see the same disk. below is the fdisk output : # fdisk -l Disk /dev/sda: 107.6 GB, 107639996416 bytes 255 heads, 63... (1 Reply)
Discussion started by: purushottamaher
1 Replies

7. UNIX for Beginners Questions & Answers

CONFIG_HID=y and logitech usb mouse B185 doesn't work in 5.3.0-RC2

trying to make the best for me with 5.3.0-RC2, everthing's fine, the dell vostro 3558 does what it should - but - and here's the question: how do I get a logitech m185 (wireless mouse) to work; I googled around but couldn't fiind anything usefull; the best I get when using solaar (depreciated?) is:... (2 Replies)
Discussion started by: vanbreukelingen
2 Replies
apport-bug(1)						      General Commands Manual						     apport-bug(1)

NAME
apport-bug, apport-collect - file a bug report using Apport, or update an existing report SYNOPSIS
apport-bug apport-bug symptom | pid | package | program path | .apport/.crash file apport-collect report-number DESCRIPTION
apport-bug reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your sys- tem to help the developers to fix the problem and avoid unnecessary question/answer turnarounds. You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most useful bug reports. If there is no matching symptom, you need to determine the affected program or package yourself. You can provide a package name or program name to apport-bug, e. g.: apport-bug firefox apport-bug /usr/bin/unzip In order to add more information to the bug report that could help the developers to fix the problem, you can also specify a process ID instead: $ pidof gnome-terminal 5139 $ apport-bug 5139 As a special case, to report a bug against the Linux kernel, you do not need to use the full package name (such as linux- image-2.6.28-4-generic); you can just use apport-bug linux to report a bug against the currently running kernel. Finally, you can use this program to report a previously stored crash or bug report: apport-bug /var/crash/_bin_bash.1000.crash apport-bug /tmp/apport.firefox.332G9t.apport Bug reports can be written to a file by using the --save option or by using apport-cli. apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the session does not run under X11, it calls apport-cli for a command-line client. UPDATING EXISTING REPORTS
apport-collect collects the same information as apport-bug, but adds it to an already reported problem you have submitted. This is useful if the report was not originally filed through Apport, and the developers ask you to attach information from your system. OPTIONS
Please see the apport-cli(1) manpage for possible options. ENVIRONMENT
APPORT_IGNORE_OBSOLETE_PACKAGES Apport refuses to create bug reports if the package or any dependency is not current. If this environment variable is set, this check is waived. Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or temporarily on the command line when calling apport-bug. SEE ALSO
apport-cli(1) AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>. Martin Pitt September 08, 2009 apport-bug(1)
All times are GMT -4. The time now is 09:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy