Fatdog64-500 final
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Hi. I'm sorry to say I have a problem with Fatdog 500.
I downloaded it yesterday and booted it up on a (64-bit) computer, and it worked fine except that about 20 minutes later I got a complaint from the centre's tech guy. The centre runs on Windows XP, and apparently my computer was using 2 IP addresses and slowing down the network.
Does anyone else know why this might be happening?
Thanks in advance,
CP.
I downloaded it yesterday and booted it up on a (64-bit) computer, and it worked fine except that about 20 minutes later I got a complaint from the centre's tech guy. The centre runs on Windows XP, and apparently my computer was using 2 IP addresses and slowing down the network.
Does anyone else know why this might be happening?
Thanks in advance,
CP.
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
LAN card questions
Please reboot the LIveCD and after getting to desktop, open a terminal window and type "ip address show". Post the results here.Colonel Panic wrote:Hi. I'm sorry to say I have a problem with Fatdog 500.
I downloaded it yesterday and booted it up on a (64-bit) computer, and it worked fine except that about 20 minutes later I got a complaint from the centre's tech guy. The centre runs on Windows XP, and apparently my computer was using 2 IP addresses and slowing down the network.
Does anyone else know why this might be happening?
Thanks in advance,
CP.
Are there any improvements to the ATI Radeon drivers in the new version?
We have an ACER Aspire that chronically overheats under moderate video stress.
We only run Puppy Fatdog64-500 on it, though we have briefly tested dpup and zpup -- with the same result, or worse.
We have an ACER Aspire that chronically overheats under moderate video stress.
We only run Puppy Fatdog64-500 on it, though we have briefly tested dpup and zpup -- with the same result, or worse.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Re: LAN card questions
Thanks for replying. I'll certainly do that although it probably won't be until next week - that's when I'm next likely to be in town.gcmartin wrote:Please reboot the LIveCD and after getting to desktop, open a terminal window and type "ip address show". Post the results here.Colonel Panic wrote:Hi. I'm sorry to say I have a problem with Fatdog 500.
I downloaded it yesterday and booted it up on a (64-bit) computer, and it worked fine except that about 20 minutes later I got a complaint from the centre's tech guy. The centre runs on Windows XP, and apparently my computer was using 2 IP addresses and slowing down the network.
Does anyone else know why this might be happening?
Thanks in advance,
CP.
Best,
CP .
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
Do you have two NIC cards? I suspect you tech guy is confused. Even if you had two IP addresses that shouldn't make much difference. To check your IP address open a terminal and type ifconfig.I downloaded it yesterday and booted it up on a (64-bit) computer, and it worked fine except that about 20 minutes later I got a complaint from the centre's tech guy. The centre runs on Windows XP, and apparently my computer was using 2 IP addresses and slowing down the network.
Well, I packaged the latest version Catalyst 10.10. Or if you mean the open source driver the whole Xorg tree has been upgraded to the latest.Are there any improvements to the ATI Radeon drivers in the new version?
I'll post an RC this weekend. Please note that the kernel has changed and I'm going to use the same repository for pet packages that 500 uses. The only problem with that is the ATI and Nvidia proprietary drivers. I'll move those two to a sub-folder labeled old. Also, Jamesbond has been on a mission and hasn't had free time lately, so there's no Nvidia pet for 510 yet. :>
ATI...Barry post..does this help?
http://bkhome.org/blog/?viewDetailed=01932
http://bkhome.org/blog/?viewDetailed=01931
Chris.
http://bkhome.org/blog/?viewDetailed=01932
http://bkhome.org/blog/?viewDetailed=01931
Chris.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Thanks for replying. He's normally very good, so I doubt he's confused but there's no harm in my trying that ifconfig anyway (as well as the ip address command mentioned earlier).kirk wrote:I downloaded it yesterday and booted it up on a (64-bit) computer, and it worked fine except that about 20 minutes later I got a complaint from the centre's tech guy. The centre runs on Windows XP, and apparently my computer was using 2 IP addresses and slowing down the network.
Do you have two NIC cards? I suspect you tech guy is confused. Even if you had two IP addresses that shouldn't make much difference. To check your IP address open a terminal and type ifconfig.
He told me he thought it was something to do with it being a Linux machine running on a networked system meant for Windows XP, but I don't know why that would be a problem.
Best,
CP .
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
Always some new progress in Puppy-world!cthisbear wrote:ATI...Barry post..does this help?
http://bkhome.org/blog/?viewDetailed=01932
http://bkhome.org/blog/?viewDetailed=01931
Chris.
If I understand correctly the RC may contain access to the new ATI drivers - we can test them then.
Thanks!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
edoc,
There is a ATI Catalyst pet package for Fatdog64-500 too. This one is version 10.5. The release notes are here:
https://a248.e.akamai.net/f/674/9206/0/ ... _linux.pdf
You need to look at the release notes before installing the pet package and make sure your card is supported. I've uploaded Fatdog64-510, so the ATI pet package for 500 has been moved to the "old" folder.
The ATI Catalyst pet package for Fatdog64-510 is version 10.10. Here's the release notes for that:
https://a248.e.akamai.net/f/674/9206/0/ ... _linux.pdf
Again make sure you check that your card is supported, the release notes will list what cards are supported. The 10.10 version is now in the pet repository.
The pet packages are kernel specific:
ati-catalyst-10.5.pet is for Fatdog64-500 only.
ati-catalyst-10.10.pet is for Fatdog64-510 only.
There is a ATI Catalyst pet package for Fatdog64-500 too. This one is version 10.5. The release notes are here:
https://a248.e.akamai.net/f/674/9206/0/ ... _linux.pdf
You need to look at the release notes before installing the pet package and make sure your card is supported. I've uploaded Fatdog64-510, so the ATI pet package for 500 has been moved to the "old" folder.
The ATI Catalyst pet package for Fatdog64-510 is version 10.10. Here's the release notes for that:
https://a248.e.akamai.net/f/674/9206/0/ ... _linux.pdf
Again make sure you check that your card is supported, the release notes will list what cards are supported. The 10.10 version is now in the pet repository.
The pet packages are kernel specific:
ati-catalyst-10.5.pet is for Fatdog64-500 only.
ati-catalyst-10.10.pet is for Fatdog64-510 only.
Update Page 1?
Hi - I am picking up with Fatdog again after six months or so. Decided to test out 510 so I needed to start with a new save file. I read through this forum thread and at 18+ pages it's easy to miss stuff.
I really like Fatdog500 for its speed on 64 bit processors.
Can you update the initial page entry with information that a new user, or someone re-setting-up should know, so that all the information needed is in one place? I'm thinking about these items:
- Apply the .pet to prevent white on yellow for PPM.
- Warning about using Alsa sound wizard (It disabled my save file)
- How to set up Firefox for use as non-spot
- Any other stuff that a first time user should be aware of.
Thanks,
B.
I really like Fatdog500 for its speed on 64 bit processors.
Can you update the initial page entry with information that a new user, or someone re-setting-up should know, so that all the information needed is in one place? I'm thinking about these items:
- Apply the .pet to prevent white on yellow for PPM.
- Warning about using Alsa sound wizard (It disabled my save file)
- How to set up Firefox for use as non-spot
- Any other stuff that a first time user should be aware of.
Thanks,
B.
[i]Laptop[/i]: Acer Aspire 5810TZ
That should be fixed in 510.- Apply the .pet to prevent white on yellow for PPM.
The Alsa sound wizard has been removed from the menu.- Warning about using Alsa sound wizard (It disabled my save file)
In 510 if you click the FAQs link and then click "Firefox won't save to xxxx." you'll find your answer.How to set up Firefox for use as non-spot
Read all of the FAQs, there's not much to read. It should be very helpful to new users.- Any other stuff that a first time user should be aware of.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Hi. Sadly I wasn't able to do this as the system is gradually being upgraded to Windows 7 this week and I didn't want to risk "rocking the boat."kirk wrote:Do you have two NIC cards? I suspect you tech guy is confused. Even if you had two IP addresses that shouldn't make much difference. To check your IP address open a terminal and type ifconfig.
He did tell me what he thought the problem was though; apparently the Fatdog system is failing to release its IP address so it's showing up as a "ghost computer" on the network.
Maybe if I'm unable to investigate this further it's better if I write this off, especially if no one else is experiencing this problem when running Fatdog (or any other Puppy) on a networked Windows XP Pro system.
Thanks for your attention anyway,
CP .
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
-
- Posts: 90
- Joined: Tue 03 Aug 2010, 15:46
System Monitor?
I was wondering if there are plans to include a System Monitor in FD500.
I boot FD500 with the .sfs for 32 bit libraries and the .sfs for 32-bit OxygenOffice works just fine.
I like gkrellm (small, efficient, and multi-functional) and I tried ttuuxxx's pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=39202
I get an xmessage "gkrellm segmentation fault: (Initializing)"
B.
I boot FD500 with the .sfs for 32 bit libraries and the .sfs for 32-bit OxygenOffice works just fine.
I like gkrellm (small, efficient, and multi-functional) and I tried ttuuxxx's pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=39202
I get an xmessage "gkrellm segmentation fault: (Initializing)"
B.
[i]Laptop[/i]: Acer Aspire 5810TZ
Can you set the network to accept a static IP?Colonel Panic wrote:Hi. Sadly I wasn't able to do this as the system is gradually being upgraded to Windows 7 this week and I didn't want to risk "rocking the boat."kirk wrote:Do you have two NIC cards? I suspect you tech guy is confused. Even if you had two IP addresses that shouldn't make much difference. To check your IP address open a terminal and type ifconfig.
He did tell me what he thought the problem was though; apparently the Fatdog system is failing to release its IP address so it's showing up as a "ghost computer" on the network.
Maybe if I'm unable to investigate this further it's better if I write this off, especially if no one else is experiencing this problem when running Fatdog (or any other Puppy) on a networked Windows XP Pro system.
Thanks for your attention anyway,
CP .
That way the DHCP lease expiring would not be an issue.
Also...
We had a similar "problem" on a LAN with two IP addresses for a box with ethernet and wifi connections, both of which were being connected to the network. If it's not the lease issue, that might well be the ticket?
Or...
To set the puppy to keep up one can set the ip to go down and back up at intervals more suitable to the msWindows LAN.
If you reconnect too quickly (ie too soon) you will get multiple IP's listed on your LAN. (Sixty seconds or more is required for most DNS records to reset.) The timeouts vary, so check with your local support.
Code: Select all
killall -HUP eth0
http://www.google.com/search?q=HUP+reload+linux
Best results to you
moB
It's not a linux vs ms thing.
All windows--ms wasn't even the first
Yes, you'll see a button for that in the network wizard. You'll want to make sure that any static address you use is available and out of the DHCP server's range.Can you set the network to accept a static IP?
That's only possible if you have a network cable connected and you configure your wireless card to connect. Your wireless card will not just connect on it's own, unless you have configured it to do so. If you open a terminal and type ifconfig you'll get something like this (probably not this long):We had a similar "problem" on a LAN with two IP addresses for a box with ethernet and wifi connections, both of which were being connected to the network. If it's not the lease issue, that might well be the ticket?
Code: Select all
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:26:B9:E0:A5:6A
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Memory:96900000-96920000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ppp0 Link encap:Point-to-Point Protocol
inet addr:75.204.58.41 P-t-P:66.174.168.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1303 errors:0 dropped:0 overruns:0 frame:0
TX packets:1438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:802841 (784.0 KiB) TX bytes:198169 (193.5 KiB)
wlan0 Link encap:Ethernet HWaddr 00:23:14:DC:48:B8
inet addr:192.168.1.220 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
#
eth0 --- This is my hard-wired lan connection. I gave it an address of 192.168.1.200.
lo --- This is the loop-back device, it should always have an address of 127.0.0.1.
ppp0 --- This is my cell phone modem. The cell carrier's DHCP assigned me an address of 75.204.58.41.
wlan0 --- This is my wifi card. I gave it an address of 192.168.1.220.
Your interface names will vary, except for lo and probably eth0. In this example I have three ip addresses and all of my interfaces are up so ifconfig shows their status. If I had not caused all of those interfaces to be active, ifconfig would have just shown the lo interface and the interface I was actually using.
I suspect that you're using Windows, and Windows gets an IP address from your DHCP server, then when you shutdown/hybernate and Windows doesn't release that address. Then you boot up Fatdog64 and it gets an IP address from your DHCP server for that same MAC address. You might try opening a terminal on Windows (Start-run-cmd) and typing ipconfig /release and then shutting down. I don't know why you IT guy cares if your MAC address has two address assigned to it unless your running out of addresses.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
OK, finally managed to grab some quiet time in the computer suite.
Here's my ipconfig (I'm posting from Fatdog 64-500 as before);
eth0 Link encap:Ethernet HWaddr 48:5B:39:C2:67:66
inet addr:192.168.1.107 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31436 errors:0 dropped:0 overruns:0 frame:0
TX packets:29078 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36993229 (35.2 MiB) TX bytes:4148922 (3.9 MiB)
Interrupt:28 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Hope someone can make sense of this!
Cheers,
CP .
Here's my ipconfig (I'm posting from Fatdog 64-500 as before);
eth0 Link encap:Ethernet HWaddr 48:5B:39:C2:67:66
inet addr:192.168.1.107 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31436 errors:0 dropped:0 overruns:0 frame:0
TX packets:29078 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36993229 (35.2 MiB) TX bytes:4148922 (3.9 MiB)
Interrupt:28 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Hope someone can make sense of this!
Cheers,
CP .
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Thanks for the info. I assume that means it's not "ghosting" on the server network any more? In any case I haven't heard any more about it from the tech people here so it may have been a one-off.kirk wrote:Colonel Panic,
That shows that you have one IP address, eth0 has an address of 192.168.1.107.
Cheers,
CP .
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.