TuxMobil
site map · index a-z · search   





Resources


Linux on the ASUS A4764KLP Laptop

Specs

  • CPU: AMD Athlon64 3000+ (1 MB L2-Cache)
  • Chipset: nVidia nForce3
  • Graphics: ATI Mobility Radeon 9700
  • Display: 15.4" TFT @ WSXGA+ resolution (1280x768)
  • RAM: 512 MB DDR
  • Harddisk: Hitachi IC25N080ATMR04-0 Travelstar 80GN 2,5", 80,00 GB, 4200 RPM, 12 ms, UDMA100, 8 MB Cache
  • Optical: built-in DVD-RW drive TSSTcorpCD/DVDW TS-L532A
  • Network: 1 GBit/s LAN (Yukon Gigabit Ethernet 10/100/1000Base-T Adapter), 802.11g WLAN (SIS162u)
  • Modem: nVidia nForce3
  • Audio: nVidia nForce3 AC97, Head-Out, Mic- and Line-In
  • IrDA
  • Parallel + serial port
  • VGA and TV-Out
  • Firewire: 1 small port (1394a)
  • USB: 4 ports (2.0)
  • PC-Card: 1 slot
  • Weight (including battery): 3.8 kg
  • Useable as CD player without booting an Operating System
  • See the ASUS product page


BIOS

You can reach the BIOS via F2. Hitting <ESC> on startup lets you choose between several boot devices (hard disk, cd, removable).

Installation

The machine is installed with Novell/SuSE Linux 9.2 64-bit which worked quite well without any serious problems. Afterwards, kernel 2.6.9 with the latest ACPI-patch was installed. Strange enough, when calling LILO while running the self-made kernel, it fails to write the new configuration to the bootblock. Workaruond is to boot the original SuSE-kernel, which was wisely kept bootable as a fallback. It seems, not all binaries in the 64bit-distribution are natively 64bit.

Screen

x.org

Due to licence-issues, the standard X-server for SuSE 9.2 (and most other distributions) is now x.org. As expected, x.org runs out of the box for the codebase of XFree86 and x.org is still quite the same. Because of the display-dimensions, the default-resolution inside /etc/X11/xorg.conf should be changed to something like 1280x768 to avoid blurs.

TouchPad

The synaptics touchpad worked absolutely fine out of the box. No additional steps were needed to use full functionality.

Console

Framebuffer works fine and no other problems were experienced.

TV-Out

You may switch the TV display type between NTSC and PAL in the BIOS. I don't know, if it is useable with linux.

VGA-Out

It shows the same content as the internal display. An annoyance could be, that it uses the same resolution as the TFT-display. According to the ASUS support-hotline, it should be possible to define a different resolution for the external VGA in a sort of "extended mode". I guess, this is done via TwinView. I might try this at a later point.

Cards

PC Cards

PCMCIA does not work correctly. Adding the following lines to /etc/pcmcia/config.opts at least enabled the kernel to map the card-memory:

include memory 0xf8a00000-0xfeafffff
include port 0x0000b000-0x0000dfff

Now, devices are recognized correctly, but claim to have IRQ-conflicts although all used IRQs (according to /proc/interrupts) are excluded.

SD/MMC CardReader

Does not work. According to lspci, it seems to be produced by Ricoh.

Network

LAN

The network-interface works fine with sk98lin.

WLAN

Currently, it is impossible to use that chip in 64-bit mode. Here is an excerpt from the ndiswrapper FAQ: "Can I use ndiswrapper in 64-bit mode (for AMD64)?

No. There are two problems. NDIS (Windows) drivers don't work in 64-bit mode. It is not possible to run 32-bit NDIS drivers in 64-bit mode (we run the Windows drivers natively on the processor, no binary emulation). Second problem is that ndiswrapper itself assumes 32-bit word lengths. This problem can be fixed easily once 64-bit NDIS drivers are available.

upposedly, 64 bit Broadcom drivers are available in 64 bit edition of Windows XP. According to Windows XP migration documentation, NDIS API itself hasn't changed (there are a few extra functions to be implemented). So it shouldn't be hard to port ndiswrapper to 64 bit kernel. However, none of the developers have AMD64 processor, so it would be easier for someone with this processor to port ndiswrapper and submit patches."

Linuxant has released DriverLoader 2.20 and this new version adds support for the x86_64 architecture. A x86_64 Microsoft-Windows driver is required for x86_64 support. Not all chipsets have a x86_64 Windows XP drivers and only the Broadcom BCMWL564 WLAN chipset is officially supported under x86_64 for now. I had no time to check out this driver yet.

Power and Configuration Management

ACPI

ACPI seems to work, did not experience any direct problems yet. Values given in the files in /proc/acpi seem reasonable, although wakeup, alarm and so on have not been tested.

Standby

S1 has only been tested briefly and it does not seem to work. The machine gets to sleep but does not wake up. It is necessary to pull out the battery and put it back in to get the machine to boot afterwards.

Suspend-To-RAM

S3 has only been tested briefly as well and it does not seem to work, too. The kernel prints an oops and then requires a cold start.

Suspend-To-Disk

SWSUSP2 does not compile on 64bit-architecture and initiating S4 with SWSUSP does not have any effect on the system, the request seems to be ignored.

CPUFreq

The module powernow-k8 should be chosen. The user-space daemon cpufreqd runs fine with it.

Hotkeys

The command

modprobe asus_acpi

brings the play-/pause-/prev-/next-keys to work.

Sound

Sound works with Advanced Linux Sound Architecture - ALSA driver snd-intel8x0, although it is an nVidia chipset.

Modem

The driver slmodem (slamr) from SmartLink, some later version than 2.9.11 could work. 2.9.11 is not useable in 64-bit mode, it even fails to compile.

IrDA

Not tested yet.

DVD-RW

The drive works well on /dev/hdc for both, reading and writing DVD-RWs.

USB

No problems were experienced here besides the SuSE-typical issues, that at least USB storage-devices should not be attached at boottime but when the system is up.

FireWire

The ohci1394 module loads fine, though FireWire was not really tested due to the lack of a proper device.

Survey PCI Devices

Output from lspci:

0000:00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
0000:00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev f6)
0000:00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
0000:00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2)
0000:00:06.1 Modem: nVidia Corporation: Unknown device 00d9 (rev a2)
0000:00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
0000:00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
0000:00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology[..]
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base[..]
0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
0000:02:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08)
0000:02:01.2 Class 0805: Ricoh Co Ltd: Unknown device 0822 (rev 17)
0000:02:01.3 System peripheral: Ricoh Co Ltd: Unknown device 0592 (rev 08)

Resources

Credits

  • Created by Sven Grounsell







print · i-mode · WAP · PDA
contact · imprint · privacy (P3P) · sponsors · RSS

© Werner Heuser 1997-2014 · http://tuxmobil.org/asus_a4764klp.html · last change Sat Oct 4 2008