Mageia forum

by **ind-pc_student** » Jan 11th, '12, 12:39

hello fellow mageia users,

i have two different laptops

1st one is a 64bit laptop and naturally a 64bit mageia and both my dongles work on this device

2nd one there is a strange issue this one in particular is 32 bits laptop is that although it has the same drivers and the installed software it faild to detect both dongles.

questions are;

A. how can this be and is there any bash commands to address this issues?

B my mobile broadband is provided by a company not listed on the network manager how do i add it and its APN settings to a more permanent basis?

company name giffgaff.com in the uk and the packages are called gigabags --->> http://giffgaff.com/goodybags#data

thank you in advance for any advice you might give me.

PS the 32 bit laptop is for my mother she is interested in using mageia Linux, as i demonstrated to her the speed and composite effects on my 64 bit laptop and not being able to use mobile internet on amgeia 32 bit will be a very bad advert for a new user, so please help me to help her; so she can use mageia comfortably.

by **doktor5000** » Jan 11th, '12, 16:40

On the laptop where it's not detected, open up a terminal, and launch the following command as root:

Code: Select all: tailf /var/log/messages

then wait a few seconds, plugin the dongle, again wait a few secons, until there is no added output,
and post the whole output here, but please use a Code-block.

by **David_Batson** » Jan 12th, '12, 00:06

I don't use Network Manager in Mageia, but I do in Fedora. Try running nm-connection-editor in terminal to add your connection.

by **ind-pc_student** » Jan 13th, '12, 17:18

thank you i will have a look when arriving at home and the other laptop is present

by **ind-pc_student** » Jan 16th, '12, 19:23

tail if results:

part one connecting dongle:

Code: Select all: Jan 16 16:18:49 localhost kernel: usb 1-4: new high speed USB device using ehci_hcd and address 6 Jan 16 16:18:50 localhost kernel: usb 1-4: New USB device found, idVendor=12d1, idProduct=1c0b Jan 16 16:18:50 localhost kernel: usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Jan 16 16:18:50 localhost kernel: usb 1-4: Product: HUAWEI Mobile Jan 16 16:18:50 localhost kernel: usb 1-4: Manufacturer: HUAWEI Jan 16 16:18:50 localhost kernel: scsi9 : usb-storage 1-4:1.0 Jan 16 16:18:50 localhost kernel: scsi10 : usb-storage 1-4:1.1 Jan 16 16:18:50 localhost mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4" Jan 16 16:18:50 localhost mtp-probe: bus: 1, device: 6 was not an MTP device Jan 16 16:18:53 localhost kernel: scsi 9:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 Jan 16 16:18:53 localhost kernel: scsi 10:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2 Jan 16 16:18:53 localhost kernel: sd 10:0:0:0: Attached scsi generic sg2 type 0 Jan 16 16:18:53 localhost kernel: sr0: scsi-1 drive Jan 16 16:18:53 localhost kernel: sd 10:0:0:0: [sdc] Attached SCSI removable disk Jan 16 16:18:53 localhost kernel: sr 9:0:0:0: Attached scsi generic sg3 type 5

part two when opening network centre

Code: Select all: Jan 16 16:23:36 localhost net_applet[3775]: running: /usr/bin/draknetcenter Jan 16 16:23:36 localhost draknetcenter[6699]: ### Program is starting ### Jan 16 16:23:41 localhost kernel: ath: Failed to wakeup in 500us Jan 16 16:23:41 localhost kernel: ath: Chip reset failed Jan 16 16:23:41 localhost kernel: ath: Unable to reset channel (2412 MHz), reset status -22 Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:41 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:41 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:41 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:42 localhost kernel: ath: Chip reset failed Jan 16 16:23:42 localhost kernel: ath: Unable to reset channel (2412 MHz), reset status -22 Jan 16 16:23:42 localhost kernel: ath: Unable to set channel Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:42 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:42 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:42 localhost kernel: ath: Chip reset failed Jan 16 16:23:42 localhost kernel: ath: Unable to reset channel (2417 MHz), reset status -22 Jan 16 16:23:42 localhost kernel: ath: Unable to set channel Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:42 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:42 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:42 localhost kernel: ath: Chip reset failed Jan 16 16:23:42 localhost kernel: ath: Unable to reset channel (2422 MHz), reset status -22 Jan 16 16:23:42 localhost kernel: ath: Unable to set channel Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:42 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:42 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:42 localhost kernel: ath: Chip reset failed Jan 16 16:23:42 localhost kernel: ath: Unable to reset channel (2427 MHz), reset status -22 Jan 16 16:23:42 localhost kernel: ath: Unable to set channel Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:42 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:42 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:42 localhost kernel: ath: Chip reset failed Jan 16 16:23:42 localhost kernel: ath: Unable to reset channel (2432 MHz), reset status -22 Jan 16 16:23:42 localhost kernel: ath: Unable to set channel Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:42 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:42 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:42 localhost kernel: ath: Chip reset failed Jan 16 16:23:42 localhost kernel: ath: Unable to reset channel (2437 MHz), reset status -22 Jan 16 16:23:42 localhost kernel: ath: Unable to set channel Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:42 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:42 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:42 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:43 localhost kernel: ath: Chip reset failed Jan 16 16:23:43 localhost kernel: ath: Unable to reset channel (2442 MHz), reset status -22 Jan 16 16:23:43 localhost kernel: ath: Unable to set channel Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:43 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:43 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:43 localhost kernel: ath: Chip reset failed Jan 16 16:23:43 localhost kernel: ath: Unable to reset channel (2447 MHz), reset status -22 Jan 16 16:23:43 localhost kernel: ath: Unable to set channel Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:43 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:43 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:43 localhost kernel: ath: Chip reset failed Jan 16 16:23:43 localhost kernel: ath: Unable to reset channel (2452 MHz), reset status -22 Jan 16 16:23:43 localhost kernel: ath: Unable to set channel Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:43 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:43 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:43 localhost kernel: ath: Chip reset failed Jan 16 16:23:43 localhost kernel: ath: Unable to reset channel (2457 MHz), reset status -22 Jan 16 16:23:43 localhost kernel: ath: Unable to set channel Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:43 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:43 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:43 localhost kernel: ath: Chip reset failed Jan 16 16:23:43 localhost kernel: ath: Unable to reset channel (2462 MHz), reset status -22 Jan 16 16:23:43 localhost kernel: ath: Unable to set channel Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:43 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:43 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:43 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:44 localhost kernel: ath: Chip reset failed Jan 16 16:23:44 localhost kernel: ath: Unable to reset channel (2467 MHz), reset status -22 Jan 16 16:23:44 localhost kernel: ath: Unable to set channel Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:44 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:44 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:44 localhost kernel: ath: Chip reset failed Jan 16 16:23:44 localhost kernel: ath: Unable to reset channel (2472 MHz), reset status -22 Jan 16 16:23:44 localhost kernel: ath: Unable to set channel Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:44 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:44 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:44 localhost kernel: ath: Chip reset failed Jan 16 16:23:44 localhost kernel: ath: Unable to reset channel (2412 MHz), reset status -22 Jan 16 16:23:44 localhost kernel: ath: Unable to set channel Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA in 100 msec after killing last frame Jan 16 16:23:44 localhost kernel: ath: Failed to stop TX DMA! Jan 16 16:23:44 localhost kernel: ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jan 16 16:23:44 localhost kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Jan 16 16:23:44 localhost kernel: ath: Chip reset failed Jan 16 16:23:44 localhost kernel: ath: Unable to reset channel (2412 MHz), reset status -22 Jan 16 16:23:49 localhost draknetcenter[6699]: ### Program is exiting ##

by **doktor5000** » Jan 16th, '12, 19:59

So, the dongle is recognized as storage volume/CD drive, like in windows for driver installation. In linux, we don't need that,
normally usb_modeswitch should take over then, and send some magic bits which switch the broadband dongle to modem mode, so you can start to use it.
Seems this step is missing here. Could you please take a look at http://www.draisberghof.de/usb_modeswit ... .php?t=552
to see whether you can switch it manually?

The second output is not really helpful for the problem of the broadband dongle, it only shows error messages of your wireless chipset currently, for the reason see above.

by **ind-pc_student** » Jan 16th, '12, 22:58

thank you will get the latest 1.21 and compare with the one installed on the 32bit laptop thanks, any ideas on problem b setup a custom network profile?

by **doktor5000** » Jan 16th, '12, 23:03

ind-pc_student wrote:any ideas on problem b setup a custom network profile?

That would be another topic best discussed in a seperate thread.

by **Ken-Bergen** » Jan 17th, '12, 00:29

What kernel are you running?

The reason for asking is that I recently helped someone with a similar device.
usb_modeswitch switched the device on his laptop
Laptop: 2.6.38.8-server-6.mga
but not his netbook
netbook: 2.6.38.8-desktop-8.mga

I and others helped him write a custom udev rule

Code: Select all: SUBSYSTEM=="usb",SYSFS{idProduct}=="1446",SYSFS{idVendor}=="12d1",RUN+="usb_modeswitch -c usb_modeswitch/12d1:1446"

which didn't work.
Someone suggested including the full path to usb_modeswitch in the rule which he did and it worked.

Code: Select all: SUBSYSTEM=="usb",SYSFS{idProduct}=="1446",SYSFS{idVendor}=="12d1",RUN+="/usr/sbin/usb_modeswitch -c /usr/share/usb_modeswitch/12d1:1446"

I urged him to report the problem here and file a bug report but he said anyone can search the net and find his solution.

As I don't have any device that requires switching I couldn't test so didn't file a bug report.

by **doktor5000** » Jan 17th, '12, 10:25

Ken-Bergen wrote:I and others helped him write a custom udev rule
[...]
Code: Select all
SUBSYSTEM=="usb",SYSFS{idProduct}=="1446",SYSFS{idVendor}=="12d1",RUN+="/usr/sbin/usb_modeswitch -c /usr/share/usb_modeswitch/12d1:1446"

That should be added to usb_modeswitch-data package.

Wait, seems we already have that one:

Code: Select all: [doktor5000@mageia1 ~]$ cat /usr/share/usb_modeswitch/12d1\:1446 ######################################################## # Huawei, newer modems DefaultVendor= 0x12d1 DefaultProduct=0x1446 TargetVendor= 0x12d1 TargetProductList="1001,1406,140b,140c,1412,141b,1433,14ac" CheckSuccess=20 MessageContent="55534243123456780000000000000011062000000100000000000000000000"

So it should be reported that it's not working somehow. The above log (part one) and the manually
created rule, which is working.

by **Ken-Bergen** » Jan 17th, '12, 10:51

Yes it should be reported but by someone that has the problem and can test.

The only thing I can think of is that the entry in /lib/udev/rules.d/40-usb_modeswitch.rules

Code: Select all: # Huawei, newer modems ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN+="usb_modeswitch '%b/%k'"

doesn't use the full path to /usr/sbin/usb_modeswitch which seems to be needed with the latest "at that time" kernel but as I say I have no way of testing.

by **ind-pc_student** » Jan 30th, '12, 16:34

thank you every one will copy to usb drive and get these codes into that netbook

by **ind-pc_student** » Feb 9th, '12, 15:07

I have found a solution that worked for me as follows:

1 "kdesu dolphin" on the run command
2 created a file called "98-huawei.rules" on folder /etc/udev/rules.d
3 opened the "98-huawei.rules" file by using the kdesu kwrite
4 pasted the

Code: Select all: SUBSYSTEM=="usb",SYSFS{idProduct}=="1446",SYSFS{idVendor}=="12d1",RUN+="/usr/sbin/usb_modeswitch -c /usr/share/usb_modeswitch/12d1:1446"

to the file and saved
5 disconnected and reconnected the modem and now it works well without a issue.

i would like to take the chance to thank everyone for the short codes given to me now both dongles work effortlessly on the 32 bit netbook and my mother will not notice the issue, leaving her to just enjoy the faster mageia linux

by **Ken-Bergen** » Feb 22nd, '12, 12:42

Would you please give us the bug report number so that we can follow what is being done to fix this problem for all users?

Mageia forum

[SOLVED] mobile broadband questions - help needed

[SOLVED] mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: mobile broadband questions - help needed

Re: [SOLVED] mobile broadband questions - help needed

Who is online