Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: JohnJS on September 12, 2009, 10:55:41 AM
-
Using 2.3 final, unable to get appbrowser to connect.
Error= "connection error, check network or mirror".
Cpanel indicates DHCP active.
Had no problem with 1.2RC1. (on older computer PIII)
Edit: Tried from Term. result:
"wget: bad address 'distro.ibiblio.org'
Xlib: extension "Generic Event Extension" missing on display "0.0".
Note: This is the first version that seems to work with my video card. (Intel 82845G/GL Brookdale -G") on P4 computer without 915resolution which I failed to get to work.
-
Does your connection otherwise work? Ping google, browsing?
edit: Seems your DNS is not working properly. What's in /etc/resolv.conf? Does nslookup work?
-
Hi Curaga,
Cannot test with base 2.3. Needed appbrowser to obtain browser apps.
My eth0 works with Puppy which I am using until I can get TC to work with this P4 computer with the Intel 82845g video board.
Had to switch from DSL and TC as I could not get 915resolution or Xorg to work. (Relative newbie to Linux).
This 2.3 ver seems to work with the Intel card.
-
Cannot test with base 2.3. Needed appbrowser to obtain browser apps.
How about this from a terminal window: $ wget -c http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/tce/opera.tce
-
Hi Juanito,
From TC Term I get "bad address".
However downloaded opera from Puppy and am using it from Tc now.. Colors are off again though resolution seems okay.
-
Ping, nslookup and wget are available in the base. Open a terminal, and try for example:
ping www.google.com
nslookup google.com
cat /etc/resolv.conf
-
Hi Curaga,
ping www.google.com = bad address
nslookup google.com = server 192.168.1.254 address 1: 192.168.1.254
nslookup can't resolve google.com
cat /etc/resolv.conf = nameserver 192.168.1.254.
-
Indeed your DNS is not working. What is in /etc/resolv.conf in puppy?
-
It's using the local nameserver instead of the router's DNS. I think someone else noted that problem in a former thread
http://forum.tinycorelinux.net/index.php?topic=753.0
-
Hi Curaga,
/etc/resolv.conf is the address for my provider ATT/Yahoo
Edit
FYI Appbrowser works on my P3 with DSL4.4.10 TC1.2RC1 and Puppy.
Only have problem with TC 2.3. Won't work on either P3 or P4.
-
Did you edit /etc/resolv.conf with the router's DNS as suggested in the linked thread?
-
Hi jpeters,
Did not change anything in /etc/resolv.conf.
Did not have to change when using 1.2rc1 or DSL 4.4.10.
Is this something new with 2.3?
-
Hi jpeters,
Did not change anything in /etc/resolv.conf.
Did not have to change when using 1.2rc1 or DSL 4.4.10.
Is this something new with 2.3?
Maybe you could post more about your connection setup. TC's use of udhcpc is different than DSL. TC 2 updated glibc. Note the reference below.
MikeLockmoore had a similar problem, and found:
Ulrich also seemed to ignore the a particularly cognizant observation that the poor DNS behavior started when glibc was changed to send essentially simultaneous IPv6 and IPv4 type DNS lookup requests out of the same originating IP port
His solution:
nameserver 192.168.{... the rest of my WAP/router's local IP addr ...}
.......
thought it may not be forwarding DNS requests and/or replies very well, so I logged into my WAP/router's admin page, found the DNS number provided by my ISP, then edited my /etc/resolv.conf file to now point to the ISP's DNS server address:
...
nameserver {my ISP-issued DNS IP address}
After this, AppBrowser and wget started working lightning quick again! Cheesy
-
Hi jpeters,
Success.
I edited /etc/resolve.conf to dns supplied by provider and appbrowser now working correctly.
Many thanks to all who replied.