You are not logged in.

#101 2008-01-07 03:57:56

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

I have uploaded PKGBUILD's and tarballs for 2.6.23-ARCH kernel modules. This includes the atl2 ethernet module, the madwifi wireless modules, the acpi module and the video camera module. members.shaw.ca/dkite

Available also is a PKGBUILD and package for acpi routines. These include the /etc/acpi routines called by acpid, and asusosd, a daemon that you run as user that pops up the various indicator thingy's when you adjust volume or brightness.

The acpi scripts work for the power button, wlan on and off (doesn't reconnect however), sleep when the lid is closed. I haven't done the internal/external monitor stuff yet. I started with the asus scripts and changed some things to fit the arch setup.

Some instructions are on the site. Let me know if there are any issues.

Derek

Offline

#102 2008-01-07 09:19:46

zodmaner
Member
Registered: 2007-07-11
Posts: 653

Re: Arch on Eee PC

dkite wrote:

I have uploaded PKGBUILD's and tarballs for 2.6.23-ARCH kernel modules. This includes the atl2 ethernet module, the madwifi wireless modules, the acpi module and the video camera module. members.shaw.ca/dkite

Available also is a PKGBUILD and package for acpi routines. These include the /etc/acpi routines called by acpid, and asusosd, a daemon that you run as user that pops up the various indicator thingy's when you adjust volume or brightness.

The acpi scripts work for the power button, wlan on and off (doesn't reconnect however), sleep when the lid is closed. I haven't done the internal/external monitor stuff yet. I started with the asus scripts and changed some things to fit the arch setup.

Some instructions are on the site. Let me know if there are any issues.

Derek

Nice. Thank you for your time and effort. Will try it out and see how it goes. smile

UPDATE: I've tried both eeemodules & acpid_eee PKGBUILD it on my Eee PC with kernel 2.6.23-ARCH and I'm glad to say that everything works flawlessly. big_smile

Wifi, suspend, power button and even webcam works! I'm so glad. The Wifi on-off button works, as well as suspend using the hot key and suspend when the lid is closed (and it seems that the suspend/wake up feels faster using the patched kernel than on the original Eee kernel it self! big_smile ). Also the asusosd graphic indicators works fine on GNOME (just placing it in GNOME's Sessions and you're set).

Now my Eee PC is fully functional with Arch Linux! big_smile Thank you dkite, you're my hero. smile

UPDATE2: acpid_eee won't build correctly if Xorg is not installed. It will built but some parts, such as asusosd file, won't compile. Perhaps you should add it in as dependency?

Last edited by zodmaner (2008-01-07 17:27:10)

Offline

#103 2008-01-07 20:07:11

thursdayknights
Member
Registered: 2007-08-25
Posts: 28

Re: Arch on Eee PC

filoktetes, is the p4-clockmod in the kernel26eee you put into community? Because I can't modprobe it using your kernel, but I can on the ordinary Arch one. Otherwise, everything so far seems to be working well -- the boot is lightning fast. smile

Last edited by thursdayknights (2008-01-07 20:12:23)

Offline

#104 2008-01-07 20:30:45

filoktetes
Member
From: Skien, Norway
Registered: 2003-12-29
Posts: 287

Re: Arch on Eee PC

thursdayknights wrote:

filoktetes, is the p4-clockmod in the kernel26eee you put into community? Because I can't modprobe it using your kernel, but I can on the ordinary Arch one. Otherwise, everything so far seems to be working well -- the boot is lightning fast. smile

No, it seems I managed to leave it out... I'll include it in the next build. I'll probably compile it in, so you'll not need to modprobe it.

Offline

#105 2008-01-07 21:26:54

thursdayknights
Member
Registered: 2007-08-25
Posts: 28

Re: Arch on Eee PC

thanks.

Offline

#106 2008-01-08 00:26:18

zodmaner
Member
Registered: 2007-07-11
Posts: 653

Re: Arch on Eee PC

Hm... guys, how do you get wireless to work again after suspend? I've experienced the problem with both NetworkManager and Wicd, so I think the problem is with either the wireless driver/module or the acpi one (but I might be wrong here...).

Did anyone else also have this problem? How do you fix it? I've tried restarting hal daemon, wicd daemon, all to no avail. sad

Last edited by zodmaner (2008-01-08 00:28:48)

Offline

#107 2008-01-08 00:41:42

filoktetes
Member
From: Skien, Norway
Registered: 2003-12-29
Posts: 287

Re: Arch on Eee PC

I'm using the standard kde KLaptop to suspend and wlassistant for wireless. I just tried suspending (for the first time, actually). Wireless reconnects at once for me (I had quit wlassistant, so the driver seems to "remember" the connection. I only needed to touch the brightness controll to get the lcd on.

Offline

#108 2008-01-08 00:51:41

zodmaner
Member
Registered: 2007-07-11
Posts: 653

Re: Arch on Eee PC

Thank you filoktetes, I'll try wlassistant and see if it's works for me too (I currently use Wicd). smile

UPDATE: Hm... after reading out from dmesg it seems that the problem is with the madwifi and hal. I've attached the dmesg's output, can anyone please confirm if my suspicion is correct?

Linux version 2.6.23-ARCH (root@T-POWA-LX) (gcc version 4.2.2) #1 SMP PREEMPT Fri Dec 21 19:39:35 UTC 2007
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001f780000 (usable)
 BIOS-e820: 000000001f780000 - 000000001f790000 (ACPI data)
 BIOS-e820: 000000001f790000 - 000000001f7d0000 (ACPI NVS)
 BIOS-e820: 000000001f7d0000 - 000000001f7de000 (reserved)
 BIOS-e820: 000000001f7e0000 - 000000001f800000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
503MB LOWMEM available.
found SMP MP-table at 000ff780
Entering add_active_range(0, 0, 128896) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   128896
  HighMem    128896 ->   128896
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   128896
On node 0 totalpages: 128896
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 975 pages used for memmap
  Normal zone: 123825 pages, LIFO batch:31
  HighMem zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
DMI present.
ACPI: RSDP 000FBE60, 0014 (r0 ACPIAM)
ACPI: RSDT 1F780000, 0034 (r1 A M I  OEMRSDT  10000717 MSFT       97)
ACPI: FACP 1F780200, 0081 (r1 A M I  OEMFACP  10000717 MSFT       97)
ACPI: DSDT 1F780400, 5F17 (r1  A0797 A0797000        0 INTL 20051117)
ACPI: FACS 1F790000, 0040
ACPI: APIC 1F780390, 0068 (r1 A M I  OEMAPIC  10000717 MSFT       97)
ACPI: OEMB 1F790040, 0046 (r1 A M I  AMI_OEM  10000717 MSFT       97)
ACPI: MCFG 1F786320, 003C (r1 A M I  OEMMCFG  10000717 MSFT       97)
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:13 APIC version 20
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 20000000 (gap: 1f800000:df600000)
swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000e4000
swsusp: Registered nosave memory region: 00000000000e4000 - 0000000000100000
Built 1 zonelists in Zone order.  Total pages: 127889
Kernel command line: root=/dev/sda1 ro
mapped APIC to ffffb000 (fee00000)
mapped IOAPIC to ffffa000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 630.084 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 505044k/515584k available (2444k kernel code, 9932k reserved, 818k data, 296k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfff80000 - 0xfffff000   ( 508 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xe0000000 - 0xff7fe000   ( 503 MB)
    lowmem  : 0xc0000000 - 0xdf780000   ( 503 MB)
      .init : 0xc0435000 - 0xc047f000   ( 296 kB)
      .data : 0xc03630a9 - 0xc042f99c   ( 818 kB)
      .text : 0xc0100000 - 0xc03630a9   (2444 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Calibrating delay using timer specific routine.. 1261.87 BogoMIPS (lpj=2102196)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9fbbf 00000000 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 512K
CPU: After all inits, caps: afe9fbbf 00000000 00000000 00002040 00000000 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 11k freed
Early unpacking initramfs... done
ACPI: Core revision 20070126
ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
CPU0: Intel(R) Celeron(R) M processor          900MHz stepping 06
Total of 1 processors activated (1261.87 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Brought up 1 CPUs
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=5
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: EC: Look up EC in DSDT
ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH6 GPIO
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P6._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
ACPI: RTC can wake from S4
Time: tsc clocksource has been installed.
pnp: 00:01: iomem range 0xfed13000-0xfed19fff has been reserved
pnp: 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
pnp: 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved
pnp: 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
pnp: 00:09: iomem range 0xfee00000-0xfee00fff could not be reserved
pnp: 00:0a: iomem range 0xe0000000-0xefffffff has been reserved
pnp: 00:0b: iomem range 0xe0000000-0xefffffff has been reserved
pnp: 00:0c: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:0c: iomem range 0xc0000-0xcffff could not be reserved
pnp: 00:0c: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0c: iomem range 0x100000-0x1f7fffff could not be reserved
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: fbf00000-fbffffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
  IO window: disabled.
  MEM window: f8000000-fbefffff
  PREFETCH window: f0000000-f6ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.1[b] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.1 to 64
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1c.2 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 5, 196608 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 1439k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Boot video device is 0000:00:02.0
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
PCI: Setting latency timer of device 0000:00:1c.2 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.2:pcie00]
Allocate Port Service[0000:00:1c.2:pcie02]
isapnp: Scanning for PnP cards...
Switched to high resolution mode on CPU 0
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: module loaded
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
Freeing unused kernel memory: 296k freed
libata version 2.21 loaded.
ahci 0000:00:1f.2: version 2.3
ACPI: PCI Interrupt 0000:00:1f.2[b] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
ahci: probe of 0000:00:1f.2 failed with error -22
ata_piix 0000:00:1f.2: version 2.12
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
ACPI: PCI Interrupt 0000:00:1f.2[b] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001ffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001ffa8 irq 15
ata2.00: ATA-4: SILICONMOTION SM223AC, , max UDMA/66
ata2.00: 7815024 sectors, multi 0: LBA 
ata2.00: limited to UDMA/33 due to 40-wire cable
ata2.00: configured for UDMA/33
scsi 1:0:0:0: Direct-Access     ATA      SILICONMOTION SM n/a  PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 7815024 512-byte hardware sectors (4001 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sda] 7815024 512-byte hardware sectors (4001 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda3 sda4
sd 1:0:0:0: [sda] Attached SCSI disk
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.10.2.2-ATHEROS (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425)
wlan: 0.8.4.2 (svn r2756)
ath_pci: 0.9.4.5 (svn r2756)
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:01:00.0 to 64
ath_pci: switching rfkill capability off
ath_rate_sample: 1.2 (svn r2756)
ath_pci: switching per-packet transmit power control off
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 14.2 phy 7.0 radio 10.2
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5424/2424: mem=0xfbef0000, irq=18
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64
Asus EEEPC HOTKEY
[eeepc hotk] Hotkey init flags 0x41.
[eeepc hotk] Get control methods supported : 0x101711
ACPI: AC Adapter [AC0] (off-line)
ACPI: Battery Slot [BAT0] (battery present)
input: Power Button (FF) as /devices/virtual/input/input2
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /devices/virtual/input/input3
ACPI: Lid Switch [LID]
input: Sleep Button (CM) as /devices/virtual/input/input4
ACPI: Sleep Button (CM) [SLPB]
input: Power Button (CM) as /devices/virtual/input/input5
ACPI: Power Button (CM) [PWRB]
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI: Thermal Zone [TZ00] (50 C)
Linux agpgart interface v0.102
agpgart: Detected an Intel 915GM Chipset.
agpgart: Detected 7932K stolen memory.
Atheros(R) L2 Ethernet Driver - version 2.0.3
Copyright (c) 2007 Atheros Corporation.
agpgart: AGP aperture is 256M @ 0xd0000000
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 20, io base 0x0000e400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
intel_rng: FWH not detected
ACPI: PCI Interrupt 0000:00:1d.1[b] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000e480
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000e800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000e880
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 20, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
ACPI: PCI Interrupt 0000:00:1f.3[b] -> GSI 19 (level, low) -> IRQ 19
usb 5-5: new high speed USB device using ehci_hcd and address 2
usb 5-5: configuration #1 chosen from 1 choice
Synaptics Touchpad, model: 1, fw: 6.3, id: 0x180b1, caps: 0xa04713/0x200000
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month
input: Video Bus as /devices/virtual/input/input7
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
input: PC Speaker as /devices/platform/pcspkr/input/input8
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Marking TSC unstable due to: possible TSC halt in C2.
Time: acpi_pm clocksource has been installed.
Clocksource tsc unstable (delta = -470242256 ns)
scsi 2:0:0:0: Direct-Access     USB2.0   CardReader SD0   0100 PQ: 0 ANSI: 0
sd 2:0:0:0: [sdb] Attached SCSI removable disk
usb-storage: device scan complete
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
[drm] Initialized i915 1.6.0 20060119 on minor 0
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
ath0: no IPv6 routers present
ACPI: PCI interrupt for device 0000:01:00.0 disabled
ath_pci: driver unloaded
Stopping tasks ... done.
Suspending console(s)
sd 1:0:0:0: [sda] Stopping disk
ACPI handle has no context!
ACPI: PCI interrupt for device 0000:03:00.0 disabled
ACPI handle has no context!
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.7 disabled
ACPI: PCI interrupt for device 0000:00:1d.3 disabled
ACPI: PCI interrupt for device 0000:00:1d.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.1 disabled
ACPI: PCI interrupt for device 0000:00:1d.0 disabled
ACPI: PCI interrupt for device 0000:00:1b.0 disabled
Disabling non-boot CPUs ...
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Back to C!
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64
PM: Writing back config space on device 0000:00:1c.0 at offset 7 (was f0, writing 200000f0)
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PM: Writing back config space on device 0000:00:1c.1 at offset 7 (was f0, writing 200000f0)
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PM: Writing back config space on device 0000:00:1c.2 at offset 7 (was f0, writing 200000f0)
PCI: Setting latency timer of device 0000:00:1c.2 to 64
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.0 to 64
usb usb1: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.1[b] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
usb usb2: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.2 to 64
usb usb3: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.3 to 64
usb usb4: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.7 to 64
PM: Writing back config space on device 0000:00:1e.0 at offset f (was 60000, writing 600ff)
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt 0000:00:1f.2[b] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
pnp: Failed to activate device 00:04.
pnp: Failed to activate device 00:05.
ata2.00: configured for UDMA/33
sd 1:0:0:0: [sda] 7815024 512-byte hardware sectors (4001 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sda] Starting disk
Restarting tasks ... <6>usb 5-5: USB disconnect, address 2
done.
usb 5-5: new high speed USB device using ehci_hcd and address 3
usb 5-5: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: Direct-Access     USB2.0   CardReader SD0   0100 PQ: 0 ANSI: 0
sd 3:0:0:0: [sdb] Attached SCSI removable disk
usb-storage: device scan complete
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: HPC vendor_id 8086 device_id 2660 ss_vid 0 ss_did 0
Load service driver hpdriver on pcie device 0000:00:1c.0:pcie02
pciehp: HPC vendor_id 8086 device_id 2662 ss_vid 0 ss_did 0
Load service driver hpdriver on pcie device 0000:00:1c.1:pcie02
pciehp: HPC vendor_id 8086 device_id 2664 ss_vid 0 ss_did 0
Load service driver hpdriver on pcie device 0000:00:1c.2:pcie02
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
ath_pci: 0.9.4.5 (svn r2756)
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 18
MadWifi: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
ACPI: PCI interrupt for device 0000:01:00.0 disabled
pciehp: Card present on Slot(0001_0003)
pciehp: Device 0000:01:00.0 already exists at 1:0, cannot hot-add
pciehp: Cannot add device 0x1:0

I'll try wlassistant to see how it goes.

Last edited by zodmaner (2008-01-08 01:31:54)

Offline

#109 2008-01-08 03:35:07

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

I notice there is a folder /opt/kde/share/autostart containing .desktop files for applications that will brought up on startup. I could put an asusosd.desktop there, and it will work for kde.

Is there something similar for gnome?

I will include a dependency to libx11 in the acpid_eee PKGBUILD

Should I put the pkgbuilds up on AUR? What do you think?

http://members.shaw.ca/dkite

Derek

Offline

#110 2008-01-08 04:00:43

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

zodmaner wrote:

Hm... guys, how do you get wireless to work again after suspend? I've experienced the problem with both NetworkManager and Wicd, so I think the problem is with either the wireless driver/module or the acpi one (but I might be wrong here...).

Did anyone else also have this problem? How do you fix it? I've tried restarting hal daemon, wicd daemon, all to no avail. sad

zodmaner: are you using my acpid_eee scripts? I found an issue with lid closed sleep mode. It shuts down fine, but when it comes back on, wifi doesn't work. I noticed that the acpid daemon wasn't running (wasn't getting any responses from any button). I restarted the daemon and buttons started responding again.

If I then shut off, turn on the wlan, the device was created properly and I could connect.

There is a line in the suspend2ram.sh script (which I took from the asus code release)

(sleep 12;killall -SIGALRM acpid )&

Let me comment out that line and test...

Nope. Lights are all on, but the display is black.

Back to the drawing board. I wonder if their acpid daemon is hacked in some way.

Derek

Offline

#111 2008-01-08 04:23:48

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

killall -SIGALRM acpid

ends up in acpid calling

exit(EXIT_SUCCESS);

so yes it shuts it down. This is the arch acpid.

I'm going to dig up the xandros code from asus to see if they do differently.

# asus+ : signal the acpid to unlock a flag from suspend.

is the comment in the script.

Derek

Offline

#112 2008-01-08 04:57:35

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

Another issue I have is if I do a shutdown with the power button, it does a tidy shutdown of kde which takes a bit of time. If I close the lid before it is done, it calls the suspend2ram, saving the shutdown state. If I hit the powerbutton to start back up, it starts up the shutdown process and turns off.

I'd say that is a bug.

Derek

Offline

#113 2008-01-08 05:13:00

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: Arch on Eee PC

Wondering if any of the users in this thread are using a Live flash drive for their arch boot?

This eliminates any stresses on the internal flash device by running in ram from the usb flash device.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#114 2008-01-08 11:07:55

zodmaner
Member
Registered: 2007-07-11
Posts: 653

Re: Arch on Eee PC

dkite wrote:

zodmaner: are you using my acpid_eee scripts?

Yep. I also tried using wlassistant as filoktetes suggested, but unfortunately that didn't work either. sad So I think the problem is with the acpid. I may try filoktetes's kernel again to see if it also had this problem.

dkite wrote:

I notice there is a folder /opt/kde/share/autostart containing .desktop files for applications that will brought up on startup. I could put an asusosd.desktop there, and it will work for kde.

there something similar for gnome?

There should be something similar, but I'm not sure...  Maybe I'll ask around on the irc.

dkite wrote:

Should I put the pkgbuilds up on AUR? What do you think?

Absolutely. smile Aside from the mentioned issues, everything works fine, so I don't see why you shouldn't put it on AUR. Just add comments to let people known the current issues (no wifi after resume from suspend, etc.) and everything should be fine.

Also dkite, may I ask what are you using to connect wireless?

Thank you for taking your time to look into this problem dkite, filoktetes. You guys are the best. smile If you guys need any help with testing any packages for Eee, then don't hesitant to ask. wink

Last edited by zodmaner (2008-01-08 11:24:26)

Offline

#115 2008-01-08 15:23:09

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

zodmaner wrote:
dkite wrote:

zodmaner: are you using my acpid_eee scripts?

Yep. I also tried using wlassistant as filoktetes suggested, but unfortunately that didn't work either. sad So I think the problem is with the acpid. I may try filoktetes's kernel again to see if it also had this problem.

...

Also dkite, may I ask what are you using to connect wireless?

Thank you for taking your time to look into this problem dkite, filoktetes. You guys are the best. smile If you guys need any help with testing any packages for Eee, then don't hesitant to ask. wink

wlassistant.

Try restarting acpid after a suspend, then switching the wifi off then on with the hotkey.

Derek (who is retrying to download the asus/xandros code)

Offline

#116 2008-01-08 16:41:54

zodmaner
Member
Registered: 2007-07-11
Posts: 653

Re: Arch on Eee PC

dkite wrote:

Try restarting acpid after a suspend, then switching the wifi off then on with the hotkey.

Hey, it works! big_smile Thank you dkite. Now where do I put the script to execute the restart command after resume? smile Also, it seems I only need to do that first time I suspend because after that wireless works every time, until I restart or shutdown that is (I use Wicd, BTW).

But there's a strange issue because although wireless is working after restart acpid & switch wifi on/off, sometimes Wicd will become unresponsive and shows no connection even though wifi is connected. I'm not sure this is a problem with Wicd or something else.

UPDATE: The trick also works with NetworkManager, so I guess it is a problem with acpid after all.

Also, I've just tried the webcam, which fails to work with both ucview and cheese (yes, I've tried echo 1 > /proc/acpi/asus/camera). sad

Another thing, when I resume back from suspend. asusosd is still running, but consume 100 % CPU and doesn't respond. I have to kill it and restart it for the indicators to work again.

UPDATE2: It seems that the change screen brightness hot key stop functioning after resume and restart acpid (everything else seems to work fine). The only solution is to restart the machine.

UPDATE3: Webcam now works (with ucview) after I change my video driver from xf86-video-intel to xf86-video-i810.

Last edited by zodmaner (2008-01-10 19:28:44)

Offline

#117 2008-01-09 01:34:58

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

Thanks for the updates. I don't have time this evening to work on it, so tomorrow. I'm in the (very long) process of downloading the huge zip with the acpid and other sources from asus.

Derek

Offline

#118 2008-01-09 18:20:31

galdor
Member
From: France
Registered: 2007-10-24
Posts: 22
Website

Re: Arch on Eee PC

Hi,

I just installed the driver kit from dkit, and it seems to work fine.

But am I the only one who get errors when he tries to build ucview or luvcview ?
The first as a compile error (a function is commented in ucview.c, I had to uncomment it), then I get a link error one (missing symbol ucil_theoria_combine_av, or something like that).
The second has a lot of compile errors.

Offline

#119 2008-01-09 20:53:08

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

I figured out the coming off sleep wlan problem. In /etc/acpi/wlan.sh, the radio has to be turned on first before modprobing ath_pci. After the modproce pciehp line,

sleep 4
echo 1 > /proc/acpi/asus/wlan
sleep 4
load_modules

This fixed it so that I could connect wirelessly after sleep. The tarball will be updated later today.

The acpid daemon killing isn't solved. I'm trying to dl the 1.7 g code dump from asus, having problems getting a valid zip file. It is taking forever and the dl is failing regularly. Does anyone have the acpid .deb from that file?

Derek

Offline

#120 2008-01-09 22:27:38

thursdayknights
Member
Registered: 2007-08-25
Posts: 28

Re: Arch on Eee PC

I installed Arch using the Arch CD, and didn't use filoktetes image, or dkite's packages (mostly because I like having a slimmed down kernel). I have filoktetes kernel installed.

I can connect wirelessly after sleep without doing any tinkering whatsoever, but yes, none of hotkeys work. I don't have asusosd running ever, so I never get the notifications, but it all works.

Also, whenever I boot, my brightness is at the maximum level, so I always have to tone it down. Awkwardly, it tones down to like my previous setting or maybe just a big jump down after one Fn brightness down.

And when I wake up out of sleep, my brightness is at maximum again, but this time, I can't Fn down.

Also, Gnome Power Manager thinks my battery is broken, and when i right click it, it shows two batteries. What does that even mean?

Last edited by thursdayknights (2008-01-09 22:29:51)

Offline

#121 2008-01-10 00:35:53

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

The screen brightness issue happened to me when I tried to use the xf86-video-intel as opposed to the  xf86-video-i810 video driver.

The kde power daemon is also borked. It alerts me every time the percentage drops by 10's.

Derek

Offline

#122 2008-01-10 01:34:33

thursdayknights
Member
Registered: 2007-08-25
Posts: 28

Re: Arch on Eee PC

Well, I am using the xf86-video-intel driver, as I installed mostly using the Arch Wiki. How did you set up your xorg.conf for the xf86-video-i810 driver? Obviously using the one on the Arch Wiki with it doesn't work. Did you just use hwd -xa?

Last edited by thursdayknights (2008-01-10 01:41:42)

Offline

#123 2008-01-10 01:56:29

dkite
Member
Registered: 2007-06-01
Posts: 62

Re: Arch on Eee PC

pacman -S xf86-video-i810

Then in /etc/X11/xorg.conf look for the Device section, Driver. Your's will say something intel, replace that with i810.

Make sure you back up your xorg.conf before editing just in case something breaks.

Derek

Offline

#124 2008-01-10 02:28:16

thursdayknights
Member
Registered: 2007-08-25
Posts: 28

Re: Arch on Eee PC

I am happy to say my brightness is remembered upon waking up and stuff! However, there is definitely something wrong with my xorg.conf...

Section "ServerLayout"
       Identifier     "archeee"
       Screen      0  "Screen1"
       InputDevice    "keyboard"
       InputDevice    "mouse"
       InputDevice    "synaptics"
EndSection

Section "Files"
       ModulePath   "/usr/lib/xorg/modules"
       FontPath     "/usr/share/fonts/X11/misc"
       FontPath     "/usr/share/fonts/X11/Type1"
       FontPath     "/usr/share/fonts/X11/75dpi"
       FontPath     "/usr/X11R6/lib/X11/fonts/Type1"
EndSection

Section "Module"
       Load  "glx"
       Load  "dri"
       Load  "extmod"
       Load  "synaptics"
EndSection

Section "ServerFlags"
       Option          "AllowMouseOpenFail"
       Option          "BlankTime" "5"
       Option          "DontVTSwitch"  "true"
       Option          "AIGLX"   "false"
EndSection

Section "InputDevice"
       Identifier  "keyboard"
       Driver      "kbd"
       Option      "CoreKeyboard"
       Option      "XkbRules" "xorg"
       Option      "XkbLayout" "us"
       Option      "XkbVariant" ""
EndSection

Section "InputDevice"
       Identifier  "mouse"
       Driver      "mouse"
       Option      "Device" "/dev/input/mice"
       Option      "Protocol" "IMPS/2"
       Option      "Emulate3Buttons" "yes"
       Option      "ZAxisMapping" "4 5"
       Option      "CorePointer"
EndSection

Section "InputDevice"
       Identifier  "synaptics"
       Driver      "synaptics"
       Option      "Device"           "/dev/psaux"
       Option      "Protocol"         "auto-dev"
       Option      "LeftEdge"         "1000"
       Option      "RightEdge"        "5400"
       Option      "TopEdge"          "1000"
       Option      "BottomEdge"       "4900"
       Option      "PalmDetect"       "0"
       Option      "SHMConfig"        "true"
       Option      "SendCoreEvents"   "yes"
       Option      "HorizScrollDelta" "0"
       Option      "RBCornerButton"   "0"
       Option      "RTCornerButtom"   "0"
       Option      "MaxSpeed"         "0.1"
EndSection

Section "Monitor"
       Identifier   "Monitor1"
       VendorName   "ASUS"
       ModelName    "eeePC P701"
       Modeline     "800x480"  29.58  800 816 896 992  480 481 484 497
-HSync +Vsync # 60 Hz
EndSection

Section "Device"
       Identifier  "Device1"
       Driver      "i810"
       VendorName  "Intel Corporation"
       BoardName   "Mobile 915GM/GMS/910GML Express Graphics Controller"
       BusID       "PCI:0:2:0"
EndSection

Section "Screen"
       Identifier "Screen1"
       Device     "Device1"
       Monitor    "Monitor1"
       DefaultDepth     24
       SubSection "Display"
               Depth     8
               Virtual  1680 1680
       EndSubSection
       SubSection "Display"
               Depth     15
               Virtual  1680 1680
       EndSubSection
       SubSection "Display"
               Depth     16
               Virtual  1680 1680
       EndSubSection
       SubSection "Display"
               Depth     24
               Virtual  1680 1680
       EndSubSection
EndSection

Section "DRI"
       Mode         0666
EndSection

#Section "Extensions"
#       Option      "Composite" "Disable"
#EndSection

Using this xorg.conf, I was only able to see a fraction of my screen, and I could scroll around in it by moving my cursor to the edges. Everything, such as my fonts and menus, were a little blurry. I scanned the xorg.conf, and found this line, "Virtual 1680 1680". I changed it to "Virtual 800 480", naturally (only the last one, because I know it's going to be using a depth of 24).

So, I tried it again, but this time, strangely, I found my wallpaper cut off at the sides. I moved my cursor to the left and right, and yes, my screen was scrolling left and right, just a few centimeters this time instead of around a virtual display four times its size. I looked at my fonts and realized they were blurry; I looked at my gmrun and realized it was a lot longer than I remembered. So, naturally, I think my image is getting stretched out horizontally.

So I tried adding 'Modes "800x480"' below "Virtual 840 480". I got the same thing.

I tried Modes "800x480" by itself, deleting the "Virtual 840 480", this time. That time, it almost worked. There was no scrolling; I could see my entire wallpaper. However, my fonts and programs were still stretched out and blurry like before. Really blurry!

Is there anything I'm missing?

Last edited by thursdayknights (2008-01-10 02:28:33)

Offline

#125 2008-01-10 11:06:04

zodmaner
Member
Registered: 2007-07-11
Posts: 653

Re: Arch on Eee PC

I've also run into the same issues when using xf86-video-i810. From Xorg.log it seems that i810 driver detects Eee resolution to be 640x480 (which is obviously wrong). I've no idea how to override that, though.

Strange that Ubuntu on Eee also use i810 driver but doesn't have this issue (it detects & set resolution to 800x480 just fine)..

Last edited by zodmaner (2008-01-10 11:06:53)

Offline

Board footer

Powered by FluxBB