Slacko Puppy version 5.5 - Unable to Connect

Please post any bugs you have found
Message
Author
flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

Slacko Puppy version 5.5 - Unable to Connect

#1 Post by flywire »

I get the error:
Unable to connect
Firefox can't establish a connection to the server at www.google.com.au.

The error comes up almost instantly compared to the slow page loading I normally get on a 512k broadband. When I click retry a couple of times the page eventually loads.

My system has no problems under WinXP SP3.

Any advice?

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#2 Post by ally »

hey fly

how are you trying to connect to the internet, via ethernet or wifi?

did you set up your connection using the connect icon?

:)

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#3 Post by flywire »

I am connected with an ethernet cable although other devices are using wifi. I didn't set anything up, it just worked out of the box.

Modem / Router: Netcomm NB5 / Linksys WRTP54G

Lighthouse system info: https://docs.google.com/file/d/0B0YmifA ... sp=sharing

I noted a couple of errors.
bootsysinit.log
ERROR: could not insert 'acpi_cpufreq': Input/output error
Starting HAL daemon: /usr/sbin/hald --daemon=yes
pcd[3825]: eth0: executing `/usr/libexec/dhcpcd-run-hooks', reason CARRIER

(Maybe I am running the wrong version of slacko for my hardware.)

dhcpcp.log
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
dhcpcd[3825]: eth0: reading lease `/var/db/dhcpcd-eth0.lease'

(I don't want to upload my IP address.)

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#4 Post by flywire »

Any thoughts?

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#5 Post by flywire »

OK I now realise that this system is only half-baked and not intended to be a fully functional system but rather a system that needs to be customised for individual hardware. Unfortunately this doesn't seem to be as straight forward as windows.

User avatar
Ray MK
Posts: 774
Joined: Tue 05 Feb 2008, 09:10
Location: UK

#6 Post by Ray MK »

Hi flywire

Had a look at your sys-info report - did you defrag your ntfs partition b4 using puppy? If not you should.
Another thought is with all the pets installed - save-file space is a bit low, try expanding it, or use sfs’s as you did with Office.
Better still - you’ve got loads of hdd space - after defragging, use gparted to provide a couple of ext2 partitions, one for puppy(‘ys) of choice and another for files.
I would also suggest a modest swap partition of approx. 512mb to 1gig.
With the above done. your ram and processor setup should allow any puppy you care to use, to absolutely fly.

HTH - best regards - Ray
[b]Asus[/b] 701SD. 2gig ram. 8gb SSD. [b]IBM A21m[/b] laptop. 192mb ram. PIII Coppermine proc. [b]X60[/b] T2400 1.8Ghz proc. 2gig ram. 80gb hdd. [b]T41[/b] Pentium M 1400Mhz. 512mb ram.

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#7 Post by flywire »

I appreciate you comments Ray but with respect, Puppy seems fine but there is an error in the browser re connecting to the net. It is so bad now that it is not worth running because it takes so many clicks to bring up a page. (I'm on WinXP SP3 now.)

How do I work through the process of what happens from booting Slacko to bringing up a page? Probably just a simple setting or maybe a file has run out of space.

I did do a defrag before I started and the log file should show that I increased the size of my pup_save.2fs by 50%. The whole configuration thing is not clear to me - I don't even recall being asked to configure anything.

Still, my preference is to save files where they are accessible irrespective of the operating system rather than on ext2. Can I mount the pup_save.2fs as a drive in WinXP? Seems like an easy way of saving my files.

User avatar
darkcity
Posts: 2534
Joined: Sun 23 May 2010, 19:16
Location: near here
Contact:

#8 Post by darkcity »

Your savefile may have become corrupted, especially if you use .2fs rather than .3fs

e2fsck can help restore it
http://puppylinux.org/wikka/e2fsck

Boot Puppy without loading the Savefile, so it isn't mounted

DO NOT USE ON MOUNTED FILESYSTEM

I like to use these options-
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-v Be verbose

for example-
e2fsck /mnt/home/lslackosave-flywirel.2fs -ycv

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#9 Post by greengeek »

Hi flywire,

in order to track down the reason for this issue I would recommend that you boot your PC from a CD containing the Slacko 55 iso (typing "puppy pfix=ram" at the first boot prompt).

This will help confirm whether or not the condition is caused by some other factor of the installation process.

If you get different symptoms then we can recommend some other steps as a means of re-installing. If you get the same symptoms that would indicate a bad download or some incompatibilty between Slacko55 and your hardware or router. If that is the case then you may well find a different puppy that does the job well. (As a trial I would recommend Pemasu's "Upup Raring 3.9.9.2" which seems quite stable on my hardware. Link here:http://murga-linux.com/puppy/viewtopic.php?t=87374)

Even if you don't want to run a different puppy at least it may contribute to our understanding of what works and what doesn't.

Bear in mind that puppy is a cutdown operating system and the devs don't have access to all hardware so some trial and error may be necessary. Hopefully we can help you get a good puppy running on your machine.

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#10 Post by flywire »

I appreciate your suggestions and will give it a go over the weekend as I am keen to get it working.

I will start with a fresh download of Slacko 5.6 because I know that people hate trying to sort out problems on old versions.

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

#11 Post by 666philb »

hi flywire,

if the problems persist in the newer slacko it's worth trying a different puppy to see if that has the same problems ..... try a precise..
http://ftp.nluug.nl/ibiblio/distributio ... -retro.iso
or
upup precise http://www.murga-linux.com/puppy/viewtopic.php?t=84944
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

Slacko Puppy version 5.6 - Unable to Connect

#12 Post by flywire »

I downloaded the Slacko 5.6 Non-PAE and have been running it for over a week in RAM. (It detects the old 5.5 install on my hard drive and allows any letter to be selected to run in RAM.)

I still get the unable to connect message frequently and after retrying a few times the page comes up.

(BTW The first version that I tried was precise which is why I went to Slacko.)

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#13 Post by flywire »

Interesting. When I sit in System Information - Network - Routing Table the eth0 Interface cycles through appearing then disappearing continuously. Is this normal?

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#14 Post by 01micko »

Ok, I gather that hardware is good, clean contacts and in perfect working order just so we can eliminate that.

Also, just be sure you got a good download by checking the md5sum (checksum) available from the repo where you downloaded the iso.

We need to know exactly what device ID your interface has, so run this:

Code: Select all

lspci -nn
Post the output please. If you know what your adapter is (usually it's easy to tell in the output, will say "Ethernet adapter" or similar) just post that part, or even just look for the HEX code that identifies your adapter, in the form of [vendorID:deviceID]
example: [10ec:8136]

Do a fresh boot and and post the output of dmesg. Probably the best way to do that is to run this:

Code: Select all

dmesg > my-dmesg.txt
gzip my-demsg.txt
This will make a file called my-dmesg.txt.gz which is a gzipped archive and can be uploaded to the forum. Upload it.

Without these hard facts it's difficult to offer any diagnosis.

What we are looking for is that your driver gets loaded and is stable. If it is then the problem is elsewhere. We'll look at that when we can confirm that there is either an issue or not with the kernel loading your particular module.
Puppy Linux Blog - contact me for access

flywire
Posts: 14
Joined: Wed 15 May 2013, 10:18

#15 Post by flywire »

Please note that I have downloaded 3 versions of Slacko and all have the same problem.

00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)

Files uploaded.

I ran the console from the icon on the desktop. Can I cut and paste to/from the console?
Attachments
my-dmesg.txt.gz
(14.12 KiB) Downloaded 438 times

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#16 Post by 01micko »

Ok, I'll take a look. I had an nvidia board which I was developing in but it died so this seems a little unusual to be unsupported (or flakey support to be more correct).. maybe the hardware is crap? I say that because my board was only 3 years old and was aging badly, sound died, one of the RAM slots died, overheating, especially in Windows... wasn't worth keeping.
flywire wrote:Can I cut and paste to/from the console?
Hightlight text and middle click, or if no middle button/scroll wheel click left and right buttons simultaneously.

LATER:

Hmmm.. definitely a weird problem..

Code: Select all

[  545.956313] forcedeth 0000:00:07.0: eth0: link down
[  547.795831] forcedeth 0000:00:07.0: eth0: link up
[  567.978180] forcedeth 0000:00:07.0: eth0: link down
[  569.757710] forcedeth 0000:00:07.0: eth0: link up
[  589.569048] forcedeth 0000:00:07.0: eth0: link down
[  591.401016] forcedeth 0000:00:07.0: eth0: link up
[  607.050450] forcedeth 0000:00:07.0: eth0: link down
[  608.832934] forcedeth 0000:00:07.0: eth0: link up
[  630.160157] forcedeth 0000:00:07.0: eth0: link down
[  631.930837] forcedeth 0000:00:07.0: eth0: link up
[  646.494732] forcedeth 0000:00:07.0: eth0: link down
[  648.335874] forcedeth 0000:00:07.0: eth0: link up
[  673.732904] forcedeth 0000:00:07.0: eth0: link down
[  675.518657] forcedeth 0000:00:07.0: eth0: link up
[  759.587675] forcedeth 0000:00:07.0: eth0: link down
[  761.378353] forcedeth 0000:00:07.0: eth0: link up
[  791.709145] forcedeth 0000:00:07.0: eth0: link down
[  793.474254] forcedeth 0000:00:07.0: eth0: link up
[  800.861516] forcedeth 0000:00:07.0: eth0: link down
[  802.680700] forcedeth 0000:00:07.0: eth0: link up
[  910.439567] forcedeth 0000:00:07.0: eth0: link down
[  912.284642] forcedeth 0000:00:07.0: eth0: link up
[  914.158988] forcedeth 0000:00:07.0: eth0: link down
[  915.943754] forcedeth 0000:00:07.0: eth0: link up
[  927.720709] forcedeth 0000:00:07.0: eth0: link down
[  929.564487] forcedeth 0000:00:07.0: eth0: link up
[  940.073652] forcedeth 0000:00:07.0: eth0: link down
[  941.863674] forcedeth 0000:00:07.0: eth0: link up
[  948.127715] forcedeth 0000:00:07.0: eth0: link down
[  949.916740] forcedeth 0000:00:07.0: eth0: link up
[ 1020.323734] forcedeth 0000:00:07.0: eth0: link down
[ 1021.884977] forcedeth 0000:00:07.0: eth0: link up
[ 1037.292195] forcedeth 0000:00:07.0: eth0: link down
[ 1039.084509] forcedeth 0000:00:07.0: eth0: link up
[ 1049.880478] forcedeth 0000:00:07.0: eth0: link down
[ 1051.666891] forcedeth 0000:00:07.0: eth0: link up
[ 1077.972467] forcedeth 0000:00:07.0: eth0: link down
[ 1079.751992] forcedeth 0000:00:07.0: eth0: link up
[ 1084.745300] forcedeth 0000:00:07.0: eth0: link down
[ 1086.593983] forcedeth 0000:00:07.0: eth0: link up
[ 1147.286828] forcedeth 0000:00:07.0: eth0: link down
Please check your cables as the pattern is rather erratic. Not saying it is cable related but it is very weird.
Attachments
Screenshot_2013-09-12_12-15-37.png
(4.87 KiB) Downloaded 773 times
Puppy Linux Blog - contact me for access

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#17 Post by 01micko »

flywire,

You are not alone, some others have reported this since kernel 3.2.

Here is something to try.

At terminal type this.

Code: Select all

echo  "options forcedeth msi=0 msix=0" > /etc/modprobe.d/forcedeth.conf
Reboot and see what happens.

Ref

Good luck!
Puppy Linux Blog - contact me for access

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#18 Post by James C »

For what it's worth, no troubles here in Slacko 5.5 or 5.6..... using 5.5 right now.

Code: Select all

# lspci -nn

00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)

Code: Select all

# uname -r
3.2.33-4g
#

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#19 Post by James C »

From 5.6 .....

Code: Select all

# uname -r
3.4.52
# 
Have had no problems.

Code: Select all

[   16.324237] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
[   16.324398] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 22
[   16.324406] forcedeth 0000:00:07.0: setting latency timer to 64
[   16.847318] forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:25:22:61:55:fc
[   16.847323] forcedeth 0000:00:07.0: highdma pwrctl mgmt lnktim msi desc-v3
[   16.847668] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   16.847915] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
[   16.848231] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 21
[   16.848242] nvidia 0000:00:0d.0: setting latency timer to 64
[   16.848247] vgaarb: device changed decodes: PCI:0000:00:0d.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   16.848466] NVRM: loading NVIDIA UNIX x86 Kernel Module  173.14.37  Wed Mar  6 16:56:05 PST 2013
[   17.222693] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[   17.222735] forcedeth 0000:00:07.0: eth0: MSI enabled
[   17.222991] forcedeth 0000:00:07.0: eth0: no link during initialization
[   17.234440] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[   17.234480] forcedeth 0000:00:07.0: eth0: MSI enabled
[   17.234735] forcedeth 0000:00:07.0: eth0: no link during initialization
[   17.734526] ip_tables: (C) 2000-2006 Netfilter Core Team
[   17.741448] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   18.420785] forcedeth 0000:00:07.0: eth0: link up
EDIT:

Mobo is about 1 yr old.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#20 Post by 01micko »

James C wrote:Mobo is about 1 yr old.
Apparently it is a BIOS problem and updating fixes it, I guess James yours already has the newer BIOS.
P23 bios from EVGA fixed the ethernet bug
Ref

So, flywire, the real solution is to update the BIOS, however the above work around I supplied should work.
Puppy Linux Blog - contact me for access

Post Reply