Trying more puppies recently I still cannot get my Huawei E160x 3G Modem
With Amaysim/Optus (Sydney,Australia) to work natively with puppy

All I need is the APN the phone number #99whatever and CHAP. that is fine

I have to revert to Mobile Partner version 11 or something.

In Precise it recognizes the modem and tells me so but even with the modem switch I cannot get, GSM connect to work for me. no ttyUSB,

Once Mobile Partner is installed, the USB_Mode_Switch Flipflopping the CD/Modem actually causes the modem to repeatedly be plugged in and then unplugged by the software a few times before Mobile Partner settles down and recognizes the modem, once connected Blinky works and I can view the info on statistics and see the Modem hardware next to etho and Lo.

I don't have any better luck with earlier puppies, Gnome network manager works fine in large distros, but I notices that Mobile Partner manages the toggle between mobile bands UMTS & HSDPA better that the Network manager

In the help file Barry mentioned that he used an E160 and wanted some more info so I add it here that it could help.

"I often don't respond to a bug report simply because I haven't got a clue how to fix it. If someone reports a "black screen", there is not much to go on.

Often the only apparent solution is to use some other puplet or even other distro that does work with that hardware."

Sorry Barry, I thought I was explicit enough re the problem of the black screen, and I am persevering with Puppy because I believe your majestic efforts have resulted in a superb compact distro.

As I said this problem affects most current distros and relates to the Nvidia "Optimus" technology for power savings on the GPU in dual display situations, usually with an integrated intel video and nvidia combination. I imagine this technology will rear it's head more and more and present ongoing problems for linux. The bumblebee project http://bumblebee-project.org/ is set up especially to solve this problem, and I have heard that a fix for the optimus problem is in place in the latest kernel version.

On Ubuntu Precise it is possible to boot into vesa mode by adding nomodeset on the command line on boot, even if the resolution is not ideal at least you can get a desktop displayed. I tried pressing F3 on Puppy live distro 5.4 beta boot and entering "puppy nomodeset pfix=vesa,ram" which should have had the same result, but to no avail the kernel did not appear to accept the command or at least did not put X into vesa mode.

If I can get nomodeset to work, then I can play around with a fix for the native video driver I assume that is nouveau being based on precise

Can anyone help with getting Puppy to boot to Vesa - I also tried vga=ask that changed the mode OK, text for boot came up in suitably small display but still went into graphics mode with the native driver active and black screen with blink.

I have uploaded an improved-but-not-yet-perfect version of the integrated Frisbee network manager, to make the pop-up messages more readable without slowing the initialization of networks. I also added the switching between versions of the network tray.

Peebee pointed out to me that the messages each delay network initialization by at least 6 seconds. And, because they all appeared at the same position on the screen, some could be obscured by others. I corrected that by placing the "announcement" messages at the bottom-left of the screen and the status messages at the bottom center. Messages will be delayed in those spots if another is being displayed. So, the messages may appear in sequence even though the processing is not delayed by them.

Previously, the network tray was selected only at boot time and only if Frisbee was the selected default "network setup tool". Now, when Frisbee is invoked through the "connect wizard", it will change to the Frisbee-network tray upon exit via the "exit" button. Canceling Frisbee by way of the "X" button does not trigger the swap. To switch back, the "woof-updates" package switches back to the normal network-tray icon if anything other than Frisbee is chosen.

However, there remains a malfunction that occurs the first time Frisbee is selected in a session. Upon exit, Frisbee appears to abort without running to the end of the script, so the swap does not occur. Subsequent selections of Frisbee seem to perform the swap. This behavior appears to cause no harm and corrects itself on an immediate second selection of Frisbee. I continue to investigate that.

For testing, be sure to have the remaining packages at the woof_updates link also installed (except for the old woof_update-20121101).
Richard

UPDATE 11/10/2012: Due to faulty testing, the greyed-out wireless tab was erroneously announced as fixed. It is not fixed. The problem was that the indications of acquired interfaces were not being set. Please replace it with the now-corrected package at the above Frisbee link. Sorry for wasting your time.

UPDATE 11/11/2012: Uploaded new versions of the packages at the above links, to improve the usability. Please try them. Thanks.

UPDATE 11/12/2012: Uploaded new versions of the woof-updates and frisbee packages at the above links, to continue improvements to the usability. Modified Frisbee to allow it to run in slacko, as well.
REdited_times_total

Ignoring bug reports because you dislike the poster simply undermines confidence in your work, as well as discouraging essential feedback.

Oh please!!!!

What nonsense.

This is one example of many that have contributed to my desire to withdraw from the "frontline" development.

You're behaving like a three year old, Barry. I spent a lot of time and effort to describe a very serious problem with Puppy 5.4, and you simply ignored my efforts and can't offer a coherent explanation. Where's the "nonsense"?

Do you really believe your selective responses are not noticed by forum readers, or that they don't discourage potential posters? Can you really think that such behaviour doesn't undermine confidence in potential Puppy adopters?

Stomping your feet and threatening to take your ball home in response to criticism is just making things worse._________________otropogo@gmail.com facebook.com/otropogo

Do you really believe your selective responses are not noticed by forum readers, or that they don't discourage potential posters? Can you really think that such behaviour doesn't undermine confidence in potential Puppy adopters?

otropogo,
please get discouraged and lose your confidence!

While doing that you may want to read this in case it helps_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Ignoring bug reports because you dislike the poster simply undermines confidence in your work, as well as discouraging essential feedback.

Oh please!!!!

What nonsense.

This is one example of many that have contributed to my desire to withdraw from the "frontline" development.

You're behaving like a three year old, Barry. I spent a lot of time and effort to describe a very serious problem with Puppy 5.4, and you simply ignored my efforts and can't offer a coherent explanation. Where's the "nonsense"?

Do you really believe your selective responses are not noticed by forum readers, or that they don't discourage potential posters? Can you really think that such behaviour doesn't undermine confidence in potential Puppy adopters?

Stomping your feet and threatening to take your ball home in response to criticism is just making things worse.

Lost cause. BTW if anyone has a real issue that o...o has already posted, you may want to go ahead and re-post it, since he has pissed off just about everyone who actually has the ability to fix issues to the point where we don't even read his posts. Sorry for the inconvenience._________________Web Programming - Pet Packaging 100 & 101

For those who may be assisted by this RE video problem with nvidia dual display with optimus on puppy precise 5.4.1. I have just been able to boot into vesa mode from live cd using F3/F3 with parameter puppy acpi=off ..... It turns out nomodeset was not necessary. However once on the desktop, the video wizard probe tells me 1920*1080 is available but hangs on the test. Bumblebee may hold the answer to using full resolution graphics.
Cheers.

I was able to get working correctly by booting on another machine, commenting out the /etc/modprobe.d/radeon.conf /modeset=1 line. Did a save then booted on to amd machine with nomodeset option install the amd-fglrx-pet. rebooted without the nomodeset option and now everything works.

If you'd been around here a few years back, you'd know that I'm not talking about myself. You might also remember when Puppy prided itself on being easy for newbies to use...

And why would anyone search the WEB to figure out how something that previously worked in Puppy is broken in the latest version, when the programmer who did the major work on both is supposedly waiting eagerly for such problem reports?

Believe it or not, I don't get any joy out of spending hours rebooting my system, making notes about all of the unintelligible error messages and nonsensical results, and then typing them up.

MY time is no less valuable to me than yours or Barry's. So yeah, when my effort gets kicked to the curb without explanation or apology, followed by vague insults, I'm put out. Any sensible person would be.

But note that I initially voiced my disappointment politely, whereas the response was vitriolic.

What happened after that is unfortunate but understandable. I have no wish to antagonize anyone, but I'm not about to respond to a totally unwarranted verbal lashing by kissing butt._________________otropogo@gmail.com facebook.com/otropogo