So far, Ubuntu seems to be the closest to working on mine, but the biggest problem is stupid ATI not being open source friendly.

The only distro i could get working (zv6005us) was Mepis 3.3.1 but no wifi and the NIC won't get a DHCP adress. I tried all the BSDs and about 20 diffrent distros and the kbd is dead or the hd or cd/dvd-rw timeout. It's always one or the other wonder if there is a *hiccup* in the kernel code somewhere? If someone could post any workaroud they did to get a distro up it would be nice for people who are having trouble with this series.
BTW: The mouse won't work under Mepis and you need to tap keys on the keyboard to get the kbd to come-up.

When the keyboard acts funny for me, I just hold the [fn] + [left shift] keys for about 5 seconds and it usually clears stuff up for me. (In case that helps)

I have a zv6007us that I installed SuSE 9.3 on.
I got it Sunday night and figured the following out by Thursday:

I downloaded the fglrx video driver from ATI: fglrx64_6_8_0-8.13.3-1.x86_64.rpm
I found it on the ATI website by searching the ATI site for XPRESS 200M IGP or XPRESS 200M.
Here:
https://support.ati.com/ics/support/...ge&folderID=27
Instructions here:
https://support.ati.com/ics/support/...asp?deptID=894
The kernel module failed to build when I installed the RPM so I have indirect Mesa 3d at the moment.
But the 2D 1280x800 is an improvement over the VESA framebuffer 1024x768.
I need to go back and see if I can't build the kernel module correctly.

I got the Broadcom wireless working using ndiswrapper and the 64 bit inf and sys files from a link at the linuxant site like someone else had posted.
BCMWL564: 64-bit generic Broadcom 54g NDIS driver for use with driverloader >= 2.20 on x86_64 (AMD64/EM64T) machines
Here:
http://ubuntuforums.org/attachment.php?attachmentid=186
This zip file has the 64 bit wireless drivers needed by ndiswapper for the broadcom chipset.
The 32 bit HP ones from the installed XP home do not work with x86_64 linux.

The last problem I had is an overly fast system clock.
The discussion boards and dmesg indicate it is an APIC problem.
Passing "noapic" to the kernel at boot time seems to fix this problem.

My HP has a broadcom 54g and It works perfectly w/ the Linuxant software. I would suggest using that. I've also heard there is another piece of software that you can use that does the same thing for free but I've had no experience with it.
I've even got WPA encryption w/ my 54g card working under Suse 9.2.

My laptop also has an ATI 345m graphics and it has 3d support under Suse 9.2.

What model of HP do you have? I couldn't get Suse 9.2 to load on my zv6000. I'm downloading 9.3 now to see if I have better luck.

I got the kernel module from ATI proprietary driver for XPRESS 200M IGP fglrx64_6_8_0-8.13.3-1.x86_64.rpm to build and install last night in SUSE 9.3 by following instructions from here:

http://www.driverheaven.net/showthread.php?t=72278

Once the 2 agp patches were applied the ATI kernel module built, but would not install, giving this error: fglrx: Unknown symbol pci_find_class

Following the advice here:
http://bhhdoa.org.au/pipermail/ck/20...er/000903.html

"Just change the pci_get_class calls in your driver to pci_find_class, or vice versa."

I edited /lib/modules/fglrx/build_mod/agpgrt_be.c to change all instances of pci_find_class to pci_get_class, but not in the #define lines.

The kernel module built and installed:
As root:
cd /lib/modules/fglrx/build_mod/
sh make.sh
cd ..
./make_install.sh

But - I still have Indirect Mesa 3D acceleration.
The problem now is DRI:

drmOpenByBusid: Searching for BusID PCI:1:5:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenByBusid: drmOpenMinor returns 5
drmOpenByBusid: drmGetBusid reports
-snip-
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmGetBusid returned ''
(II) fglrx(0): [drm] loaded kernel module for "fglrx" driver
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:5:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x00681000
(II) fglrx(0): [drm] drmMap failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0x20000000 FBMappedSize: 0x08000000
(II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,800) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) fglrx(0): Using hardware cursor (scanline 800)
(II) fglrx(0): Largest offscreen area available: 1280 x 7387

The articles about "no3D" in /usr/share/doc/fglrx/articles say that this problem is fixed in ATI Proprietary Linux Driver 3.14 and later.

But in the README for the 8.12.10 driver for ATI for SUSE 9.3-AMD64 there is a comment about a "Known Issue"
- DRI support on R200 boards is currently broken on AMD64

I wonder if this is the problem?

I got most everything working with Fedora Core 4 Test 3 with a x86_64 install on a zv6015us. The issues I still have are:

1) The above mentioned clock-speed problem. There is a patch available but I'm waiting for the actual release of Fedora Core 4 before hassling with patching the kernel source every time there's a new kernel version. They were coming out fairly frequently for a while but seem to have slowed down as FC4 gets closer ro scheduled release.

2) The wireless NIC seems to be configured correctly with ndiswrapper and the 64-bit driver. Everything looks right as reported by iwconfig/ifconfig but I can't connect to my base station nor scan a couple of other neighborhood APs. It acts like the power to the radio is off and, unfortunately, the switch above the keyboard appears to need some Windows software to be loaded to actuate the radio. The built-in Broadcom wireless NIC isn't supported by the Linux wireless LAN radio switch project (http://rfswitch.sourceforge.net/). Any suggestions on this problem would be appreciated. If nothing else, I'll re-install XP when FC4 ships since Red Hat usually recommends doing a clean install after you've had a test version installed turn the stupid thing "on" under XP and then install FC4 final.

I'll have to give the Radeon drivers a try but the current configuration allows me to run 1289x800 which is more than adequate.

(Just realized how out of date my sig was so this should bring in the edits)

DaveAtFraud,

What version of ndiswrapper are you using with FC3?
I didn't see an RPM at the Fedora download site.
I believe I read somewhere you need 1.0 or greater.
I used ndiswrapper-1.1-4.x86_64.rpm from SuSE 9.3 distro.

There is a wireless lan on/off setting in my zv6007us bios.
If this is on, I suspect the radio is on.
The light flickers when there is network traffic with Linux.

Here's a good link for howto reading on compiling the source against your installation:
http://www.suseforums.net/index.php?...pic=4327&st=40
------------------
At the bottom of this post:
http://ndiswrapper.sourceforge.net/p...9.1%2064%20bit
there is a comment about:
On 32 bit Suse, I could just run 'ifup wlan0' and the wireless would get setup okay. This doesn't seem to work reliably on 64 bit Suse. I needed to run the following commands in various combinations to persuade the wifi card to accept the parameters:

$ iwconfig wlan0 mode managed
$ iwconfig wlan0 key restricted 1234567890
$ iwconfig wlan0 essid "babwifi"

$ ifconfig wlan0 up

-------------------
I manually edited the network script ifcfg-wlan0 to include the mac address of the wireless access point and the ESSID as well as the encryption key.

I downloaded the ndiswrapper source from sourceforge (current, stable) so it's definitely the current version. I got the 64-bit Broadcom drivers that were posted to one of the Ubuntu Linux discussion threads. I'm actually running FC4, not FC3 and I'm trying to get everything working with the x86_64 version.

I found both the Suse how-to write-up and a few other resources but all I ever see from the wireless NIC is:
The button/status for the wireless NIC stays dark. Unfortunately, I turned it off while the system was still running Windows and it was off when I installed FC4. I'm guessing that there is a iwconfig or similar (iwpriv) command that would let me turn on the radio but I have yet to find it. Doing a "iwconfig eth1 txpower on" doesn't seem to do anything and I don't see a corresponding event from iwevent.

Edit 15 June 2005:

I finally got the wireless NIC to respond but it required reinstalling Windoze. I decided to just setup dual boot when I installed FC4-final in-case there were any other similar issues. Once I got windows installed, there were a number of levels of configuration screens I had to go through before I got to one that actually re-enabled the wireless LAN. The keyboard button was also dead under windows and the radio disabled until then. The wireless LAN now works great with basically a standard ndiswrapper install.

OK.
I think your radio is off, too.
But tonight I booted into XP and shut off the wireless using the button.
Then I powered off and powered on booting into Linux.
The wireless connection failed to initialize and no amount of command line coaxing could make it work.
Then I pressed the button and typed ifup wlan0 as root and the wireless came up.
I can't magine there's much hardware difference between my zv607us and your zv6015us other than processor speed.
I'm using DHCP to set the IP and netmask, and I put the access point MAC address in the network script for the wireless card.
ifcfg-wlan0:
BOOTPROTO='dhcp'
MTU=''
NAME='Ethernet Network Card'
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='yes'
WIRELESS_AP='00-30-bd-f1-a1-db'
WIRELESS_AUTH_MODE='sharedkey'
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL='11'
WIRELESS_DEFAULT_KEY='0'
WIRELESS_ESSID='belkin54g'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0='ae981c9be8e99a352ea0a8611f'
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
WIRELESS_WPA_PSK=''
_nm_name='static-0'

Hope this helps.

I'm beginning to wonder if it has something to do with the version of iwconfig that ships with FC4 x86_64. I went down the items in your ifcfg-wlan0 and matched them up with both my corresponding entries in ifcfg-eth1 and what is set by ifup-wireless (the script basically identifies the settings from ifcfg-ethX where type=wireless that can be set with iwconfig and sets them with invocations of iwconfig). Some oddities are:

iwconfig eth1nwid foo - gives a device not found error for eth.1 Setting other wireles settings with iwconfig don't give such an error.

iwconfig eth1 txpower on - gives no error but there is no corresponding output from iwevent.
ditto for iwconfig power.

iwconfig eth1 essid foo - generates the expected output from iwevent but iwconfig shows the default value (any/none).

iwevent displays the expected output for setting things like essid (but iwconfig reports it as none/any), the key/encryption settings, etc.

Changing the channel through iwconfig behaves completely as expected with both iwevent showing the change and iwconfig showing the changed value.

Regardless of what I do, my WAP shows no recieved packets. The WAP works as expected since a friend of mine just came by for a visit and I was able to set him up with wireless access with no problems.

Edit: Tried pulling down a more recent SuSE version of wireless tools and installing it. Once I coerced it into installing, I got the same results as described above. No doubt that I was getting the SuSE versions since they install to /usr/sbin instead of /sbin like the fedora version.

Here's a link I hadn't seen before:
http://fedoranews.org/contributors/e_a_graham_jr/ndis/

And another, maybe not germane:
http://www.ces.clemson.edu/linux/fc2-ipw2200.shtml

How did u get fedora to get past the installation. It hangs up on the installation screen in graphics install. I have FC Core 4 beta 3 x64.

Thanks,

Never mind...got it!