DSL Report Speed Tests

DSL Reports speed tests from this location @ Zanesville, OH.

This is a wifi connection served by a Time / Warner / Road Runner residential back-haul connection.

Acer 5520-5912 OEM Device Driver List

PDF from Acer: http://www.acerpanam.com/synapse/forms/AcerDrivers/Aspire%205520.pdf - A PDF containing a list of drivers for the 5520-5912; these can be downloaded from Acer; the listing includes drivers for WinXP, Vista, and Vista-64; the file contains download links that may be used to retrieve the device drivers from Acer as compressed archive files, each of which in turn contain a Windows setup program, release notes, etc

The base URL for the driver archive files referenced in this file is:

http://www.acerpanam.com/synapse/data/7117/documents/

Acer 5520-5912 NVIDIA Driver Problems

• Acer 5520
• NVIDIA Ge7000M video chipset

Bob provides a fairly clear description of the problem he and others are experiencing with the NVIDIA device drivers, Windows Vista, and the Acer 5520-xxxx:

[...] currently running the machine on generic VGA without any driver installed because that is all that will work. I've tried installing everything from 84.25 to the latest 169 version. Same problem; flickering during install and then either won't work and have to restart from previous good config or it does start and is stuck in 4bit color and 640 x 480 res. I've read all the FAQs, googled til I'm blue in the face and still no joy.

Help please!

Bob

Google: acer "5520-5912" nvidia driver vista

PDF containing a list of drivers for the 5520-5912; these can be downloaded from Acer; the listing includes drivers for WinXP, Vista, and Vista-64

Ubuntu Forums: Acer 5520 -specific Atheros AR5007EG HowTo

Ubuntu Forums is hosting a some discussions about getting the Atheros WiFi card working on the Acer 5520 laptop.

Also, Bug #162251 in network-manager-applet (Ubuntu) details a bug which the post's author says may be related to the problems with

Acer Aspire 5520-5912

The Problem Space

I can't stand Vista any longer. I started looking last week for a Linux LiveCD distribution to use.

So far I have tried a good half-dozen [it seems - I will enumerate later] Linux LiveCD distros, and none of them have proven satisfactory. Again, I will try to detail the specific problems of each a bit later.

The Machine

Acer Aspire 5520–5912, AMD Turion 64x2 TL-58, 2 GB RAM, NVIDIA GeForce 700M / nForce 610M, DVD-RW, Ethernet NVIDIA nForce Networking Controller, Wireless Atheros AR5007EG

The [Working] Distro(s0

• Knoppix 5.1.1 LiveDVD

Device listing for Acer Aspire 5520-5912 w/ Windows Vista

Here is the driver list painstakingly hand-copied from a windows dialog box:

Acer Aspire 5520 5912, AMD Turion 64x2 TL-58, 
2 GB RAM, NVIDIA GeForce 700M / nForce 610M, 
DVD-RW, Ethernet NVIDIA nForce Networking Controller, 
Wireless Atheros AR5007EG

**********************************************************

Batteries: 
 Microsoft AC Adapter
 Microsoft ACPI-Compliant Control Method Battery

Computer: 
 ACPI x86-based PCv

Disk Drives: 
 TOSHIBA MK11637GSX ATA Device

Display adapters: 
 NVIDIA GeForce 700M / nForce 610M

DVD/CD-ROM drives:  
 Optiarc DVD RW AD-7560A ATA Device

Human Interface Devices: 
 ENE CIR Receiver
 HID-compliant consumer control device
 HID-compliant device [3x]
 Microsoft eHome Infrared Transceiver; USB Human Interface Device 

IDE ATA/ATAPI controllers: 
 IDE Channel [4x]
 Ricoh Memory Stick Controller
 Ricoh xD-Picture Card Controller
 Standard Dual Channel PCI IDE Controller [2x]

IEEE 1394 Bus host controllers: 
 RICOH OHCI Compliant IEEE 1394 Host Controller

Imaging Devices: 
 Acer Crystal Eye Webcam

Keyboards: 
 Microsoft eHome MCIR 109 Keyboard
 Microsoft eHome MCIR Keyboard
 Microsoft eHome Remote Control Keyboard keys
 Standard 101/102-key or Microsoft Natural PS/2 Keyboard

Mice and other pointing devices: 
 Alps Pointing-device
 HID-compliant mouse [2x]

Modems: 
 HDAUDIO Soft Data Fax Modem with SmartCP

Monitors: 
 Generic PnP Monitor

Network adapters: 
 Atheros AR5007EG Wireless Network Adapter
 isatap.{13CDFF80-1123-4C42-BFDA-CF21C68B1754}
 isatap.knowlogy.net
 isatap.shacknet.nu
 NVIDIA nForce Networking Controller
 Teredo Tunneling Pseudo-Interface
 WAN Miniport (IP)
 WAN Miniport (IPv6)
 WAN Miniport (L2TP)
 WAN Miniport (PPPEO)
 WAN Miniport (PPTP)
 
Non-Plug and Play Drivers:
 Ancillary Function Driver for Winsock
 Beep
 Common Log (CLFS)
 Crcdisk Filter Driver
 Dritek General Port I/O
 Dynamic Volume Manager 
 HTTP
 int15
 IP Network Address Translator
 ISA/EISA Class Driver 
 Kernel Mode Driver Frameworks Service
 KSecDD
 LDDM Graphics Subsystem
 Link-layer Topology Discovery Mapper I/O Driver 
 Link-layer Topology Discovery Responder
 Message-oriented TCP/IP and TCP/IPv6 Protocol (SMB session)
 Mount Point Manager
 NativeWiFi Filter
 NDIS System Driver 
 NDIS Usermode I/O Protocol
 NDProxy
 NETBT
 NetIO Legacy TDI Support Driver
 NSI proxy service 
 Null
 QoS Packet Scheduler 
 RDP Encoder Mirror Driver
 RDPCDD
 ReadyBoost Caching Driver
 Remote Access Auto Connection Driver
 Remote Access IPv6 ARP Driver
 Security Driver
 Security Processor Loader Drivr
 Storage Volumes 
 TCP/IP Protocol Driver
 TCP/IP Registry Compatibility
 VgaSave
 Windows Firewall Authorization Driver
 XAudio

Processors:
 AMD Turion(tm) 64 X2 Mobile Technology TL-58 [2x]

SD host adapters:
 SDA Standard Compliant SD Host Controller
 
Sound, video, and game controllers:
 Realtek High Definition Audio
 
Storage Controllers:
 Microsoft iSCSI Initiator
 
Storage volume shadow copies:
 Generic volume shadow copy [3x]
 
Storage Volumes:
 Generic volume [3x]
 
System Devices:
 ACPI Fixed Feature Button 
 ACPI Lid
 ACPI Power Button
 ACPI Sleep Button 
 ACPI Thermal Zone 
 AMD Address Map Configuration
 AMD DRAM and HyperTransport(tm) Trace Mode Configuration
 AMD HyperTransport(tm) Configuration
 AMD Miscellaneous Configuration
 Consumer IR Devices
 Direct memory access controller
 High Definition Audio Controller
 High precision event timer
 Microsoft ACPI-Compliant Embedded Controller
 Microsoft ACPI-Compliant System
 Microsoft Composite Battery
 Microsoft System Management BIOS Driver
 Microsoft Windows Management Interface for ACPI [3x]
 Motherboard resources [2x]
 NVDIA nForce PCI System Management 
 NVDIA nForce System Management Controller
 PCI bus
 PCI standard ISA bridge
 PCI standard PCI-to-PCI bridge [2x] 
 PCI standard RAM Controller [2x]
 Plug and Play Software Device Enumerator
 Programmable interrupt controller
 System board
 System timer
 Terminal Server Keyboard Driver
 Terminal Server Mouse Driver
 UMBus Enumerator
 Volume Manager
 
Universal Serial Bus controllers:
 Standard Enhanced PCI to USB Host Controller [2x]
 Standard OpenHCD USB Host Controller [2x]
 USB Root Hub [4x]
 
************************************************************

what worked for me was changing the monitor to a 
"acer 55s (widescreen)" using the 
system/administration/screens and graphics then running 
nvidia-settings from the command line.

Death of a Laptop/Windows Vista Review

My HP/Compaq a220n died on 13 July, 2007. It does not complete the boot process, and appears to be hanging while executing the optical drive Power On Self Test (POST) code from the system BIOS.

I have since acquired an Acer AMD 64 Dual Core machine [will post the specs later] which came from Walmart pre-loaded with Windows VIsta.

I've been using the Acer for a couple weeks now, and am finding that Windows Vista sux even harder than Windows XP - this is Win95 territory, in fact. Crappy OS, crashes regularly, and runs slower the new, better hardware (this new system has a 64-bit dual core processor w/ 2Gig of RAM) than XP did on a system with only 512M of RAM and a 2 generations older processor.

This system is so slow that the cursor hangs for seconds at a time just while trying to move it across the screen, w/ nothing in particular running in the background.

The Vista user interface is ever cluckier to use than the XP interface (e.g. the new Start Menu is just utter crap - it doesn't fit on the screen, and going to "All Programs" gets me into a mess that need the arrow key pad to get out of without doing serious collateral damage to the menu itself as the brainded trackpad driver tries to drag and drop your menu items in places that, while not specified ahead of time, appear to be more malicious than just random.

In short, this machine

1. Appears to have a malign intelligence all its own
2. Obviously and very "vocally" HATES the user.
3. Appears to be pursuing some other-motivated agenda that has to have been conceived and implemented by Microsoft Corp at the expense of anyone with the temerity to actually try to do useful or productive work with a laptop computer.

Next order of business: Install a 64-bit OS that supports full multi-tasking. [note that Vista seems to be running 32-bit code in a 32-bit emulated environment running on top of the 64-bit hardware - probably why the machine is so slow - HAL is not your friend, anymore, it seems]

So despite the gifting a brand new, higher-end-than-what-we-had replacement for the HP, we still aren't able to accomplish any non-trivial tasks with the new machine until the system software is rebuilt and properly configured. Film at eleven.

USR Ethernet / WiFi Bridge Model 5430

This article discusses the use of the US Robotics 5430 802.11g Wireless Ethernet Bridge device to connect to a Ethernet-connected PC to a "managed" WiFi network. This article does not discuss use of the 5430 as an "Ad hoc" network device/node.

By default, the USR Ethernet / WiFi bridge boots up using 192.168.1.201 as it's "Management IP Address". The IP address used can be changed by accessing the 5430's management interface via HTTP.

1. Connect a CAT5e Ethernet cable from the PC NIC to the 5430; this is a "straight thru" Ethernet patch cable, not a crossover cable, although a crossover cable might work here, don't know yet]
2. Perform a "hard reset" on the 5430; this may be acccomplished by holding down the reset switch on the back of the device while power is applied - the reset switch can be depressed using a matchstick or a paperclip - hold it down for about 30 second after power is applied in order to restore the device to its "factory default" settings [30 sec may be overkill in that some smaller amount of time may be all that is required, but 30 seconds works, and we use it here until we have a chance to refine the process.
3. At a Bash prompt [on the computer that is connected to the 5430], do something like

    sudo ifconfig eth1 192.168.1.111 up
   

   This will bring up the 2^nd Ethernet interface on the PC with an IP address in the same sub-net as the bridge's management interface, allowing access to the 5430 using a web browser [HTTP client].
4. Open e.g. Konqueror or Firefox and enter 192.168.1.201 in the Location bar; make sure Javascript is enabled for this address, since the 5430 appears to user Javascript in the web forms that make up the device's management interface. [If there is a username/password prompt/dialog box when opening the 5430 management interface pages, the default userid/password for the 5430 when set to factory defaults is admin/admin]
5. Use the Site Survey on the Tools page of the 5430 management interface to see what wireless networks are available [note that the 5430 firmware does not seem to any channel or signal strength info for the available networks - see below for firmaware version number].

Here is the firmware version info for the 5430:

 Boot Loader Firmware Version:  CFE 3.51.21.0.2
 OS Firmware Version:    Linux 3.51.21.0.3
 Firmware Date:        Mar 9 2004

Once you have the SSID of the wireless network to connect to, select it from the Site Survey popup and follow the prompts. [It may be necessary to enter the desired SSID string directly into the SSID text input element on the Wireless page of the 5430 management interface, as well].

Once the wireless network has been selected within the 5430 management interface, the 5430 will immediately attempt to retrieve a network IP address for the new wireless network association the next time the PC requests DHCP provisioning for the NIC connected to the 5430.

Use the command

 sudo ifconfig eth1 0 down

to close down the static IP configuration for the NIC [created above], and use

 sudo ifup eth1

to bring up the NIC using the default [DHCP] NIC configuration.

Note that the syntax

  sudo ifconfig eth1:1 168.192.1.123 up 

Can be used to re-establish a connection to the 5430 Management Interface once eth1 [or whatever the device name is] has been provisioned using DHCP to have the same WiFi netowkr address as the bridge (I.E. the IP address assigned to the 5430 by the selected wireless network association).

High Fructose Corn Syrup (HFCS)

[this item cross-posted to earth_food at http://blogs.earthside.org/earth_food/2007/07/high-fructose-corn-syrup-hfcs.html]

We've been hearing that "high fructose corn syrup (HFCS) is not good for you" for a couple years now, but up until now it has just been something to avoid if possible (i.e. choose the brands that don't have it in the ingredient list if and when an alternative is available, pass up certain "SALE" items because they contain it, etc), but - at least up until this point, no evidence concerning HFCS has been presented (to me), and no critical warnings have been raised about its use in human food products.

Today while moderating a discussion at slashdot.org entitled PubPat Kills Four Key Monsanto Patents, I ran across a post (#19982005 by an "anonymous" author) which - while substantially directed at the issue of genetically modified (GM) crops, mentions some of the reputed [according to the anonymous author] problems with HFCS and includes some [supporting] internet links.

We've had HFCS on a sort of "probationary" status for some time since it's lack of usefulness for human consumption was first brought to our attention a few years ago.

At the present time, HFCS seems destined for infamy on that list I carry around in my head of "poisonous items which are disguised as food and to which the U.S. FDA turns a blind eye." Items which are already on that list include, but are not limited to:

• aspartame
• fluoride

The [anonymous] author of the /. post quotes from a source at http://ezinearticles.com/?The-Dangers-of-High-Fructose-Corn-Syrup&id=28535, which quote is reproduced again, here, in part:

When high fructose corn syrup breaks down in the intestine, we once again find near equal amounts of glucose and fructose entering the bloodstream. As covered in recent newsletters, the fructose short-circuits the glycolytic pathway for glucose. This leads to all the problems associated with sucrose. In addition, HFCS seems to be generating a few of its own problems, epidemic obesity being one of them. Fructose does not stimulate insulin production and also fails to increase "leptin" production, a hormone produced by the body's fat cells. Both of these act to turn off the appetite and control body weight. Also, fructose does not suppress ghrelin, a hormone that works to increase hunger. This interesting work is being done by Peter Havel at UC Davis.

Some of the problems associated with high fructose corn syrup:

• Increased LDL's (the bad lipoprotein) leading to increased risk of heart disease.
• Altered Magnesium balance leading to increased osteoporosis.
• Increased risk of Adult Onset Diabetes Mellitus.
• Fructose has no enzymes or vitamins thus robbing the body ofprecious micro-nutrients.
• Fructose interacts with birth control pills and can elevate insulin levels in women on the pill.
• Accelerated aging.

FEMA Continues to Contribute to Katrina Death Toll

Democracy Now! is reporting that FEMA suppressed warnings of toxic gases [formaldehyde] in trailers issued for the use of persons evacuated from the destruction wreaked by Hurricane Katrina. From the Headlines page for 20 July 2007:

FEMA Suppressed Warnings on Toxic Gas in Evacuee Trailers

[…] documents show top Federal Emergency Management Agency officials have suppressed internal warnings about dangerous levels of toxic chemicals in trailers inhabited by Hurricane Katrina evacuees […] FEMA field workers warned the evacuees were living amidst levels of potentially cancerous formaldehyde gas […] seventy-five times the recommended maximum […] Hundreds have complained of health effects […] emails show FEMA officials were only concerned with avoiding any legal liability … a FEMA official wrote [that] agency lawyers had advised against carrying out tests because doing so: “would imply FEMA’s ownership of this issue.” […] FEMA lawyer Patrick Preston wrote: “Do not initiate any testing until we give the OK … Once you get results […] the clock is running on our duty to respond to them.” Eleven days later, an evacuee who had complained about the chemicals was found dead in his trailer. […] FEMA attorneys rejected calls for an independent investigation into his death […].

It is interesting to note that as of 08:21 EST Saturday 21 July 2007 [the time of this writing] the GSA auction site at http://gsaauctions.gov/gsaauctions/gsaauctions/ where these trailers are being auctioned is unavailable, returning an HTTP 503 "503 Retry request – Service will be available shortly. Please retry request" error for repeated retries.

This sort of incident brings forcefully to mind the actions of the European settlers to North America in giving blankets contaminated with smallpox to the native tribes residing in the territory upon which the Europeans wished to settle. I.E. There have been repeated allegations amongst the Katrina survivor community to the effect that the Federal government planned to use the disastrous events surrounding the hurricane to depopulate New Orleans in order that the city might be turned over to corporate interests.

The story in the Washington Post titled FEMA Announces Trailer Air Testing Plans, also dated 20 July, mentions several other FEMA-trailer-related deaths and lawsuits which have been filed.

A point which is mentioned in the Washington post article is that at least one of the lawsuits which has been filed, and which is attempting to gain class action status, is against the trailer manufacturer.

1. Why is/was FEMA concerned with liability when in fact the manufacturers who produced trailers purchased by FEMA are the ones who ultimately bear liability for their unsafe product?
2. These trailers purchased and distributed by FEMA are brand­name, commercially available "Recreational Vehicles" (RVs) – if the formaldehyde levels in them are sufficient to kill the occupants – even if the occupants killed are "infirm" or suffer from respiratory problems – how is it that the manufactures are allowed to sell these deathtraps to the public?
3. If private individuals purchase these trailers and resell them, will they be responsible for "cleanup" of the toxic materials in them, and if so, what sort of toxic materials handling and disposal certifications will be required of them?

[note that the GSA auction site is back online as of 09:24 EST today, 21 July 2007 - no explanation of the outage provided on the GSA page]