Page 11 of 12

4g modem in linux

Posted: Tue 07 Jun 2016, 05:52
by Aung
I am trying 4G Mobile broardband where I am on micko slacko64 and I would rather use Puppy than doze but as with 3G dongles linux software wont load. It makes a MobileBrServ folder in/usr/local with a empty runmbbservice file in it, none of the other files on the dongle are copied to MobileBrServ folder. When I copy the rest of the files to the MobileBrServ folder they are deleted when trying to install a second time. Stonkered, end of experiment, whats different about Puppy that stops software on dongles from loading. Same thing happens on FD64, at least this time I dont get the 'missing operand' message.

From Rxvt terminal

# ./install_linux
begin to verify ISO ...
verify the ISO succeed !
begin to copy install file...
now begin to install...
/usr/bin/xterm
Run xterm and begin to install

It then opens Xterm

install begin...
/usr/local/MobileBrServ/mbbservice '&' /usr/local/MobileBrServ/ArConfig.dat is not exist
begin to copy file...
/tmp/MobileBrServ_AutoRun/linux_mbb_install/install: line 99: /tmp/MobileBrServ_AutoRun/linux_mbb_install/7zr: No such file or directory
copy end ...
begin to install ...
cp: cannot stat ‘./*’: No such file or directory
cp: cannot stat ‘/usr/local/MobileBrServ/10-Huawei-FlashCard.rules’: No such file or directory
chmod: cannot access ‘/etc/udev/rules.d/10-Huawei-FlashCard.rules’: No such file or directory
cp: cannot stat ‘/etc/udev/rules.d/10-Huawei-FlashCard.rules’: No such file or directory
sed: can't read /usr/local/MobileBrServ/skeleton: No such file or directory
install success...
run the process...
/usr/local/MobileBrServ/mbbservice
/tmp/MobileBrServ_AutoRun/linux_mbb_install/install: line 513: /usr/local/MobileBrServ/mbbservice: No such file or directory
install end...
Press any key to exit.



In /tmp there is only a log file, no '/MobileBrServ_AutoRun/linux_mbb_install/install'

Current path = .
begin to verify ISO ...
verify the ISO succeed !
begin to copy install file...
now begin to install...
Run xterm and begin to install

install begin...
/usr/local/MobileBrServ/mbbservice '&' /usr/local/MobileBrServ/ArConfig.dat is not exist
begin to copy file...
copy end ...
begin to install ...
udevVer=208
run the process...
/usr/local/MobileBrServ/mbbservice
Press any key to exit.

Posted: Tue 07 Jun 2016, 15:28
by dejan555
Hey gcmartin, sorry for the late reply... here are the files:

https://drive.google.com/open?id=0B_Mb5 ... 3JWV2VpTkU

slacko64-6.3.0

Posted: Sat 11 Jun 2016, 20:59
by Billtoo
Manual frugal install to a 32gb flash drive, pc is an hp desktop.

video-info-glx 1.5.3 Sat 11 Jun 2016 on Slacko64 Puppy 6.3.0 Linux 4.1.11 x86_64
0.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Redwood PRO [Radeon HD 5570]
oem: ATI ATOMBIOS
product: REDWOOD 01.00

X Server: Xorg Driver: radeon
X.Org version: 1.14.3
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
OpenGL version string: 2.1 Mesa 9.1.7

AMD Phenom(tm) II X6 1045T Processor
Core 0: @800 1: @800 2: @800 3: @800 4: @1400 5: @800 MHz

Installed kdegames with PPM + Smplayer-16.60 & Smtube-16.60

It's working well.

slacko64-6.3.0

Posted: Tue 21 Jun 2016, 02:39
by Billtoo
I produced a slacko64-6.3.1.iso with woof-ce and did a manual frugal
install to a usb-3.0 hard drive, pc is a macmini.

video-info-glx 1.5.3 Mon 20 Jun 2016 on Slacko64 Puppy 6.3.1 Linux 4.1.11 x86_64
2.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
oem: Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS
product: Intel(R) Sandybridge/Ivybridge Graphics Controller Hardware Version 0.0

X Server: Xorg Driver: intel
X.Org version: 1.14.3
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.1.7

Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Core 0: @1500 1: @1300 2: @1300 3: @1300 MHz

I wanted to compile the newest VLC but some of the libs were too old so
I downloaded the latest versions from BLFS and compiled them, vlc-2.2.4
compiled without problems then.

The "set properties of X" utility is missing so couldn't turn of sreen blanking,
I downloaded a screensaver with PPM so hopefully it will work.

Slacko64-6.3.1 is working pretty well so far.

Re: slacko64-6.3.0

Posted: Tue 21 Jun 2016, 02:57
by 01micko
Billtoo wrote:The "set properties of X" utility is missing so couldn't turn of sreen blanking,
I downloaded a screensaver with PPM so hopefully it will work.

Slacko64-6.3.1 is working pretty well so far.
The pupx utility is moved to rootfs-packages - so when you get that list if stuff to check the boxes in woof/3builddistro-Z it is in there (with pmusic and friends, now frisbee too).

Posted: Tue 21 Jun 2016, 07:46
by gcmartin
Mick, open PM for a Slacko64 related item.

Re: slacko64-6.3.0

Posted: Tue 21 Jun 2016, 10:44
by Billtoo
01micko wrote: The pupx utility is moved to rootfs-packages - so when you get that list if stuff to check the boxes in woof/3builddistro-Z it is in there (with pmusic and friends, now frisbee too).
I found the pupx directory and made a pet of it, it's working now I think,
Thanks.

EDIT:
After setting up I did a remaster and burned it to a DVD+RW, I have it
running on my Acer laptop:

video-info-glx 1.5.3 Tue 21 Jun 2016 on Slacko64 Puppy 6.3.1 Linux 4.1.11 x86_64
0.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Park [Mobility Radeon HD 5430/5450/5470]
oem: ATI ATOMBIOS
product: PARK 01.00

X Server: Xorg Driver: radeon
X.Org version: 1.14.3
dimensions: 1600x900 pixels (423x238 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD CEDAR
OpenGL version string: 2.1 Mesa 9.1.7

Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz
Core 0: @1199 1: @1333 2: @1199 3: @1199 MHz

It's working well, thanks to you and the other Woof-CE people.

slacko64-6.3.0

Posted: Thu 23 Jun 2016, 12:55
by Billtoo
I re-ran the ./3builddistro-Z step in Woof-CE and selected all the
things (pupx etc) that I missed the first time, chose a different theme
too.
video-info-glx 1.5.3 Thu 23 Jun 2016 on Slacko64 Puppy 6.3.1 Linux 4.1.11 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
oem: NVIDIA
product: GF108 Board - 1071v1p1 Chip Rev

X Server: Xorg Driver: nouveau
X.Org version: 1.14.3
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVC1
OpenGL version string: 2.1 Mesa 9.1.7

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2336 1: @2336 MHz

I did a manual frugal install to a usb-3.0 SSD which is running on my
lenovo desktop pc.

It's working well.
Thanks

Posted: Fri 08 Jul 2016, 15:12
by Mike Walsh
Afternoon, all.

Got a question for those of you who might be knowledgeable about such things.

I run WINE in every one of the 10 Pups in my current 'kennels'. With the exception, that is, of Slacko 64.....because it just will not run. It'll load.....but that's it.

In Tahr 64, Phil's got the '32-bit compatability libs SFS'. It works a treat. I can't help noticing, however, that there is nothing like this for Slacko 64. Out of curiosity, I loaded the Tahr 32-bit libs. compat SFS to see what would happen. I was able to get WINE to configure itself.....but it still wouldn't install anything. This is probably because the libraries structure in Slacko is rather different to Tahr 64, so I wasn't entirely surprised.

Is there any intentions of creating something like this for Slacko.....or am I flogging a dead horse here?? I know some people in the community won't touch WINE with a bargepole.....is Mick one of them? :P

Just curious, that's all! WINE would be the 'icing on the cake' for Slacko 64, if I can get it running.....


Mike. :wink:

Posted: Fri 08 Jul 2016, 15:59
by Sailor Enceladus
Re: Wine, I was trying to do the same yesterday in Xenialpup64, downloaded every wine and wine64 things I could find in the repositories and typing wine to no avail before just rebooting into Slacko 32-bit where I already had an sfs and .wine folder ready. One thing I didn't think of was trying to type wine64 instead of wine... haha, this whole 64 concept is pretty new to me.

Posted: Fri 08 Jul 2016, 19:11
by Mike Walsh
Hi, Sailor.

Mm. You've got two advantages with Xenial, though; one, it's 'buntu-based.....and two, it's Phil developing it. He'll make it as compatibile as Tahr was.

There's no reference to anything to do with WINE in the Slacko repos at all.


Mike. :?

Posted: Fri 08 Jul 2016, 22:45
by peebee
Mike Walsh wrote: There's no reference to anything to do with WINE in the Slacko repos at all.
Mike. :?
Wine (32 & 64) for Slackware:
https://sourceforge.net/projects/wine/f ... 0Packages/

I add the wine-extra-bits and make an sfs for 32-bit....

Posted: Sat 09 Jul 2016, 00:53
by Mike Walsh
Hiya, peebee.

O-kay. Translation, please..! 'Wine-extra-bits'; what are these, exactly?


Mike. :wink:

Posted: Sat 09 Jul 2016, 06:16
by peebee
Mike Walsh wrote:Hiya, peebee.
O-kay. Translation, please..! 'Wine-extra-bits'; what are these, exactly?
Mike. :wink:
Just adds an ms-dos-executable mime type....

Posted: Sat 09 Jul 2016, 07:54
by Mike Walsh
Morning, peebee.

Mm-hm. 'Kay. I don't know if it's just me, but all that stuff you gave me the link to looks awfully like source code; 'make-files' all over the place. I've never compiled a thing in my life; wouldn't even know where to start.

(Actually, that's not strictly true; I did compile the 'gimp-gap' extension for the GIMP in Slacko 570.....but that was under CatDude's instruction. If he hadn't led me through it, literally step-by-step, I wouldn't have known what I was doing..!)

I later found out that it's in the repos of all the 'buntu-based Pups..!)

But if I'm right, and it is compiling, I'm guessing every single one of those folders has to be compiled, too. Looks like a very long and tedious business indeed..... (*sheesh*)

Do I really need WINE that badly ? I guess not..... :lol:

EDIT:- Just found out that AlienBob's done a version of WINE 1.8 for 14.1. I've downloaded it; I'll have a look at it later on...!


Mike. :wink:

Posted: Sat 09 Jul 2016, 08:11
by peebee
Mike Walsh wrote: the link to looks awfully like source code
The link sent you to .txz files - which are loadable packages....
There is source on the same site but you don't need it....the .txz are compiled ready for slackware...

1.9.13 is the latest - 1.19.4 will appear soon as the source is there now.

e.g. https://sourceforge.net/projects/wine/f ... z/download

Posted: Sun 10 Jul 2016, 10:31
by Mike Walsh
Hiya, peebee.

Well, problem sorted. I've got AlienBob's WINE 1.7.51 installed in Slacko64; I wanted to stick with the version that works so well with the two graphics apps I use so much; Mooi's 'PhotoScape', and Adobe's CS2 'Photoshop'.

The thing that threw me was the fact that the 64-bit versions have not only 'wine' in /usr/bin, but also 'wine64' Normally, you'd click on 'wine', followed by 'winecfg' to set it all up, and create the /root/.wine folder.....but in a 64-bit Pup, of course, you have to use 'wine64' instead'.....

Old habits die hard! :lol:


Mike. :wink:

Posted: Wed 13 Jul 2016, 06:17
by s243a
In the first run settings, I'm not given the option to enable the fire wall.

On another note,I'm having wierd boot issues with my windows 8.1 machine (probably not slaco related). In the case of both grub4dos and unetbootin once the kernal was mounted and boot image loaded, it was as though it could no longer read the USB drive to find the sfs file.

Strangly though, now it is working. Perhaps the complete poweroff helped. This new bios stuff is a bit of a mistory to me.

I'm not sure whether it will or will not work the next time I try. I guess we'll see. **Note I am booting from a USB drive.

Posted: Thu 14 Jul 2016, 06:11
by s243a
I'm trying to install vitualbox.

I downloaded the SUSE version because I read that early slackware was most influenced by SUSE. Also it turns out there are tools to convert rpm to tgz available through the puppy package manager.

After doing this the tgz modula appears to install virtualbox.

Now I need to build the kernal moduals or virtualbox won't load. The following link suggests:

Code: Select all

modprobe vboxdrv
https://forums.opensuse.org/showthread. ... el-upgrade


This didn't work. I remember phill explaining before how to build the kernal menu's for tahrpup. I can try to find the post. However, I don't know if these modules are included in slaco by default.

Perhaps first I should also see what sfs files I might need to load first before building the kernel modual menus.

Posted: Thu 14 Jul 2016, 21:54
by gcmartin
@S243a, on FirstRUN, there are several versions seen across the PUPPY spectrum. In the modern era of today, There is this version in Slacko/ThurPUP which is maintained by @01Micko AND there is a version from @BarryK. Further, for older PUPs with FirstRUN technology, there is @Shinobar's version which improved how PUP boots and how users have a clearer view of their startup requirements of their PUPs.

They have some similarities but are different in the scope each of these developers see as a need when starting any new PUP to support user needs. It appears that @01Micko intends that uses conscious of f/w will click the taskbar to control behavior of the firewall vs a blanket startup.

Beware, when using @BarryK's version as he has several. His most recent has a quirk which starts the firewall even when a users does not want it started because user's router provide a necessary firewall for one's network. He has acknowledged this problem and intends to fix his FirstRUN.

More info than asked.