Thanks for replying so quickly. I have tried your way with the icon in the bottom right hand corner. Unfortunately, it does not work for me. I think this is because the network has a hidden ESSID. I enter its name and the PSK/Password but it does not respond to it. When I plug in the usb dongle there is now two wireless interfaces and I am not sure which one the right hand corner system works with.

If I try the Network Manager from the Control Panel, I can select the wireless interface. I cannot connect with the R8180 pci but I can with the usb dongle.

It seems that the driver for the r8180 card doesn't save the network settings or something like that.

Lately I've been using a 3g usb stick for internet access. However FatDog doesn't seem to know anything about these devices - er, to be precise the system knows the thing is there and mounts the fake Windows CD, but doesn't seem to have any gui tool for simpletons to actually get internet access. Have I missed something, or what needs to be added to the FatDog base system to use 3g? I'm afraid I haven't spent many happy hours under the hood working out what are the relevant config files and so on. Mainly NetworkManager just does it for me in other distros. In fact this seems to be a bit of a Puppy gap if I dare say so, no Puppy I have struck seems to do 3g usb modems out of the box. I await enlightenment, thanks in advance.

Fatdog doesn't support 3g usb dongle because kirk and me don't use one; we don't have the devices for testing; and there have been no volunteers that step up and make that happen, sorry.

Hi! I've managed to compile usb_modeswitch from sources in Fatdog 610 (a total achievement for me since it is my second compiling.. ). Then I could manually modeswitched my USB dongle (a Huawei E1756) and get a succesfull connection to Internet whith pupdial, from which I'm writing this words. I'm pretty happy about this 'cause now I finally can make Fatdog my primary OS, and I have to say I'm loving it, is faster than anything and everything works OOTB!!
But right now I have no automatic recognition of the device as a modem when I plug it (no automatic modeswitching). I guess it could be something regarding udev but have no clue where to look. Perhaps whith a little help (or more than little I presume) I could make a pet from this, any help would be apprecieted

Another issue: I'm from a spanish speaking country and although I'm used to having english as the system language, half of my files have accents or the "ñ" character. Then half of my files appear in red as no valid filename.. Is any way I can solve this (without renaming the files of course! ).

Anyway, a lot of thanks for this great distro!!!!

Barbol

UPDATE: one problem solved! I was linking the wrong file in /usr/libexec (the binary instead of the usb_modeswitch script). I have it working automatically now, just plug in the dongle and udev takes care of it.
Now I'll go for the next challenge.. making the pet!!

I'm running the FD 610 version now and it runs well , still have to make a few more tweaks and install it on a hard drive .
I tested FD 611 , the Firefox iso and checked the md5sum file before burn it on a rewritable DVD .
First , I could see for the first time Zarfy from Display properties in the Control Panel but only inside Virtual Box as in the attachment below ...
I never saw it while booting directly on PC .
I also noticed Seamonkey in the Menu even it was a Firefox version... JWM did not restart and did not make any change to the tray height option... The Menu with Seamonkey and the JWM issue were while running on PC from DVD .
Then I wanted to run xorgwizard so I inserted pfix=xorgwizard from the bootline , it gave me a window with options , but after choosing a driver : error , no changes . The same thing running xorgwizard from Terminal only that after choosing an option I got the message seen in the attachment .
if this happens only on my machine then is not a big issue , but if not then maybe this post would help...
I did't find the missing closing parethesis ( I guess it was that ) in the redirected file .

new xorgwizard.png

Description

xorgwizard in terminal

Filesize

153.52 KB

Viewed

1297 Time(s)

Last edited by Gobbi on Thu 20 Dec 2012, 20:32; edited 2 times in total

Another issue: I'm from a spanish speaking country and although I'm used to having english as the system language, half of my files have accents or the "ñ" character. Then half of my files appear in red as no valid filename.. Is any way I can solve this (without renaming the files of course! ).

I think this problem depends on the format of the hard disk.

If it is a hard disk format that linux likes like EXT2 EXT3 EXT4
then you won't have this problem.

The reason why I believe this is true --> I had a USB stick
(formated as FAT32) and it contained files with 'red' filenames.
It was caused by going to French language websites
and then saving the website to the USB disk.

With much learning and some hours could finish the usb_modeswitch package. I tried it on three different computers and is working well, in all cases got a successful Internet connection with pupdial. I'm uploading the pet package for testing.. Hope it works fine!!
Made one for fatdog 500 series too..

If it is a hard disk format that linux likes like EXT2 EXT3 EXT4
then you won't have this problem.

don570, thanks for the answer!
After your comments I look closely which files had wrong filenames, and I think the problem are files saved in windows (XP particularly). I never had this trouble when I was using ubuntu, or racy whith the spanish langpack.. But I remember this happened too in puppy431. Could it be something regarding to the character encoding?
Thanks again.

Thanks for the modeswitch pet. I hope it is useful for those who need to use that 3G dongles.

As for encoding thing, try to use "pkeys=es" on the boot command line and see if it helps. Make sure you have a font that can display Spanish characters. This should help if you access FAT partition. It has the side-effect that your console keyboard mapping is changed to spanish keyboard too.

I have just got around to trying Fatdog64 611 on my new laptop. Thanks guys.

I could not resist the urge to try creating a 64bit version of Opera SFS for it. On a quick test using the firefox version it seems OK. However, there is one problem. For the flashplugin to work Opera needs these Mozilla libraries and looks for them in /usr/lib64 ( in 64 bit version):

Most symlinks are present but Fatdog64_611 firefox does not have these symlinks in /usr/lib64 pointing to /usr/lib64/firefox:

libnssutil3.so
lbsll3.so

It is necessary to create these symlinks manually for Opera. Having made these changes Opera now finds the Flash plugin and it works as expected. However, there are 32 bit and 64 bit versions of libflashplayer.so in Fatdog64.

Opera Tools>Advanced>Plug-ins shows:

32 bit version at /usr/lib/mozilla/plugins/libflashplayer.so
and
64 bit version at /usr/lib64/mozilla/plugins/libflashplayer.so

This does not appear to cause a problem but anyway I chose to disable the 32 bit version in Opera Plugins settings.

I have not checked the Seamonkey version but I assume a similar problem may exist there.

My modem shows up twice, but on probing ttyUSB0 it dont show up and didnt connect.
I coppied pupdial from Slacko and was able to force it to use ttyUSB2 and it connects.
But then dies when I open a browser.

As for encoding thing, try to use "pkeys=es" on the boot command line and see if it helps. Make sure you have a font that can display Spanish characters. This should help if you access FAT partition. It has the side-effect that your console keyboard mapping is changed to spanish keyboard too.

jamesbond,

Thanks for the answer, I've tried booting whit "pkeys=es" but the "wrong" filenames still appeared in red, besides my laptop's has an english keyboard so it was pretty unconfortable.. I guess I could live with some red files in Rox's windows..

Aung,

Sorry, I don't know what could be happening with pupdial, I'm not an expert on the area, just a regular and curious user..
But here is something you could try:
I found that the CLI function of sakis3g works on fatdog if you have the fd64-devx_610.sfs installed (it is a script for 3G connections with many dependencies and most of them are provided with the devx sfs, but sadly the interactive GUI didn't work).
You can download it from here (just the binary free version, the full one is not required if you already have installed the usb_modeswitch pet):
http://www.sakis3g.org/

Once unpacked it's a single file script, which I moved to /root/my-applications/bin so it be in the executable PATH.
Before it is useful there is still one thing more to do: you have to rename or remove the file /bin/chat (which is a symlink to busybox) so that the full version of chat in the sfs can be invoked by sakis3g:

Code:

mv /bin/chat /bin/chat_old

(you can restore it later if you unload the devx.sfs)

Now it should be functioning, in my case I get succesfull connection with the line:

where you have to replace "internet" for your own ISP's requirements and the xxxx:xxxx number with the corresponding one to your dongle (can get it with lsusb after the device is switched). The "--pppd" option is for using pppd instead of wvdial, which in my case was vital, and "-d" is just for debugging. It will output some "expr: syntax error" but still works.
For what I red sakis3g has very good reviews and a lot of options, so I think it worth a try.
Hope it works this time!

Merry Christmas!!

BarbolLast edited by Barbol on Mon 24 Dec 2012, 19:36; edited 1 time in total

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum