slacko 6.3.2: Huawei E173 doesn't connect, 6.3.0 does

Please post any bugs you have found
Post Reply
Message
Author
User avatar
puppycub
Posts: 37
Joined: Wed 15 Aug 2007, 09:14

slacko 6.3.2: Huawei E173 doesn't connect, 6.3.0 does

#1 Post by puppycub »

Hi,

with slacko64 6.3.0 I get a good internet connection with my wireless USB Huawei E173 Modem (Aldi/MedionMobile). I use Network > PGPRS Setup/PGPRS Connect.

Doing the same with slacko64 6.3.2 is not successful, try as I might :cry:

Details with slacko64 6.3.2
*************************
Network > PGPRS Connect
I fill in the required infos

Code: Select all

Attempting connection through /dev/ttyUSB0 to APN internet.eplus.de...

Exit status is 1
DISCONNECTED
> Button <Disconnect>

Trying again:

Network > PGPRS Connect

Code: Select all

Attempting connection through /dev/ttyUSB0 to APN internet.eplus.de...

Exit status is 1
DISCONNECTED
Network Icon in upper task bar
Choose <Wireless GPRS modem>

Code: Select all

Attempting connection through /dev/ttyUSB0 to APN internet.eplus.de...

Exit status is 1
DISCONNECTED

Please note that I handle the modem in exactly the same way and fill in exactly same the required infos into exactly the same fields both with slacko64 6.3.2 and slacko64 6.3.0.

What is going on in slacko64 6.3.2?

Thanks,

puppycub

User avatar
puppycub
Posts: 37
Joined: Wed 15 Aug 2007, 09:14

#2 Post by puppycub »

Sorry, I had to re-edit my previous post from tharpup to slacko, using boldface for clarity. My head was so dizzy from puppy-ing to and fro for a few days that I made this mistake :oops:

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#3 Post by Karl Godt »

I cannot say more than what man pppd manual page says:

Code: Select all

EXIT STATUS
       The  exit  status  of  pppd  is  set  to indicate whether any error was
       detected, or the reason for the link being terminated.  The values used
       are:
..
       1      An immediately fatal error of some kind  occurred,  such  as  an
              essential system call failing, or running out of virtual memory.
..
System call may be related to kernel version headers differences,
slackware 14.y likely uses a different kernel version than current Slacko-Puppy
and has compiled pppd with its kernel headers, not with the headers of Slacko-Puppy.
And there may be a real change in the functions of the kernel drivers.
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P

User avatar
puppycub
Posts: 37
Joined: Wed 15 Aug 2007, 09:14

#4 Post by puppycub »

Thank you, so I have to stick with the older Slacko 6.3.0 to connect to the internet whenever I have my Huawei USB modem :evil:

And do I understand you correctly that Puppy distros use or "borrow" parts of apps, or programs, or whatever, from other distros even if they will not work alongside their own system? ;-)

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#5 Post by Karl Godt »

Yes, woof builds are a mix of some own kernel patched with a non-standard unionfs
like aufs or unionfs to be able to merge read-only and read-write layers of different
sources.

And then there are the approx. 200-300 scripts that boot the Puppy and
connect and manage the X desktop environment,
with few non-system related apps like pdict.
And the huge rest consists of mainly downloaded pre-compiled binaries from a major linux distro.
Slacko from slackware, Lupu, Precise, Tahr from Ubuntu, D-Pups from Debian .

If you want a Puppy that is using binaries compiled from source, you could
try Wary-5.x or Racy-5.y .

Nevertheless, you could try to get the pppd source tarball, load the devx and re-compile it, to see if that would work better - at least that would be the way I would try it first.
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P

User avatar
puppycub
Posts: 37
Joined: Wed 15 Aug 2007, 09:14

#6 Post by puppycub »

Thank you! Now I know.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#7 Post by bigpup »

Keep in mind, all the bugs in a Puppy version, never get completely found and fixed, until it gets released and people use it and find them.

Usually, one or maybe two people developed the Puppy version and we, the users, are their testers.
You maybe found a bug that needs to get looked at.

Also, it really depends on the person who developed the Puppy version and his willingness to put fixes into it.
Some Puppy versions I do not support, because they get released and the person controlling it just seems to walk away.
I guess they think it is good enough.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
puppycub
Posts: 37
Joined: Wed 15 Aug 2007, 09:14

#8 Post by puppycub »

Karl Godt wrote:...
If you want a Puppy that is using binaries compiled from source, you could
try Wary-5.x or Racy-5.y ....
I cannot boot either wary-5.5 nor racy-5.5 from a Live USB stick on my amd64 notebook :(
slacko64-6.3.0 and tharpub-6.0.5 were no problem!

Are Wary-5.x or Racy-5.y too old to boot on my notebook :?:

User avatar
puppycub
Posts: 37
Joined: Wed 15 Aug 2007, 09:14

#9 Post by puppycub »


Post Reply