Unichrome Via Vesa and the missing network

Are you using 6.5-beta 6, snaker?

My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.

Yes I am running 6.5-beta 6, I am trying to use dsmeg but I am getting no response. Command not found

'dmesg', maybe?


My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.

Thanks

[17179569.184000] Linux version 2.6.15-27-desktop (root@mepis-pro) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Wed Jan 31 11:14:45 EST 2007
[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[17179569.184000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[17179569.184000] BIOS-e820: 0000000000100000 - 000000001bfd0000 (usable)
[17179569.184000] BIOS-e820: 000000001bfd0000 - 000000001bfde000 (ACPI data)
[17179569.184000] BIOS-e820: 000000001bfde000 - 000000001c000000 (ACPI NVS)
[17179569.184000] BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
[17179569.184000] 0MB HIGHMEM available.
[17179569.184000] 447MB LOWMEM available.
[17179569.184000] found SMP MP-table at 000ff780
[17179569.184000] On node 0 totalpages: 114640
[17179569.184000] DMA zone: 4096 pages, LIFO batch:0
[17179569.184000] DMA32 zone: 0 pages, LIFO batch:0
[17179569.184000] Normal zone: 110544 pages, LIFO batch:31
[17179569.184000] HighMem zone: 0 pages, LIFO batch:0
[17179569.184000] DMI 2.3 present.
[17179569.184000] ACPI: RSDP (v000 ACPIAM ) @ 0x000f7480
[17179569.184000] ACPI: RSDT (v001 A M I OEMRSDT 0x12000415 MSFT 0x00000097) @ 0x1bfd0000
[17179569.184000] ACPI: FADT (v002 A M I OEMFACP 0x12000415 MSFT 0x00000097) @ 0x1bfd0200
[17179569.184000] ACPI: MADT (v001 A M I OEMAPIC 0x12000415 MSFT 0x00000097) @ 0x1bfd0390
[17179569.184000] ACPI: OEMB (v001 A M I AMI_OEM 0x12000415 MSFT 0x00000097) @ 0x1bfde040
[17179569.184000] ACPI: DSDT (v001 E12K0 E12K0001 0x00000001 INTL 0x02002026) @ 0x00000000
[17179569.184000] ACPI: PM-Timer IO Port: 0x808
[17179569.184000] ACPI: Local APIC address 0xfee00000
[17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[17179569.184000] Processor #0 15:12 APIC version 16
[17179569.184000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[17179569.184000] IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[17179569.184000] ACPI: IRQ0 used by override.
[17179569.184000] ACPI: IRQ2 used by override.
[17179569.184000] ACPI: IRQ9 used by override.
[17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs
[17179569.184000] Using ACPI (MADT) for SMP configuration information
[17179569.184000] Allocating PCI resources starting at 20000000 (gap: 1c000000:e3780000)
[17179569.184000] Built 1 zonelists
[17179569.184000] Kernel command line: root=/dev/hda2 nomce quiet vga=791
[17179569.184000] mapped APIC to ffffd000 (fee00000)
[17179569.184000] mapped IOAPIC to ffffc000 (fec00000)
[17179569.184000] Initializing CPU#0
[17179569.184000] PID hash table entries: 2048 (order: 11, 32768 bytes)
[17179569.184000] Detected 1603.945 MHz processor.
[17179569.184000] Using pmtmr for high-res timesource
[17179569.184000] Console: colour dummy device 80x25
[17179570.628000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179570.628000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[17179570.636000] Memory: 449692k/458560k available (2741k kernel code, 8332k reserved, 931k data, 192k init, 0k highmem)
[17179570.636000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[17179570.716000] Calibrating delay using timer specific routine.. 3211.73 BogoMIPS (lpj=6423479)
[17179570.716000] Security Framework v1.0.0 initialized
[17179570.716000] SELinux: Disabled at boot.
[17179570.716000] Capability LSM initialized
[17179570.716000] Mount-cache hash table entries: 512
[17179570.716000] CPU: After generic identify, caps: 078bfbff c3d3fbff 00000000 00000000 00000000 00000000 00000001
[17179570.716000] CPU: After vendor identify, caps: 078bfbff c3d3fbff 00000000 00000000 00000000 00000000 00000001
[17179570.716000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[17179570.716000] CPU: L2 Cache: 256K (64 bytes/line)
[17179570.716000] CPU: After all inits, caps: 078bfbff c3d3fbff 00000000 00000410 00000000 00000000 00000001
[17179570.716000] mtrr: v2.0 (20020519)
[17179570.716000] CPU: AMD Mobile AMD Sempron(tm) Processor 2800+ stepping 00
[17179570.716000] Enabling fast FPU save and restore... done.
[17179570.716000] Enabling unmasked SIMD FPU exception support... done.
[17179570.716000] Checking 'hlt' instruction... OK.
[17179570.732000] ACPI: Looking for DSDT ... not found!
[17179570.732000] ENABLING IO-APIC IRQs
[17179570.736000] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[17179570.876000] NET: Registered protocol family 16
[17179570.876000] ACPI: bus type pci registered
[17179570.876000] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
[17179570.876000] PCI: Using configuration type 1
[17179570.876000] ACPI: Subsystem revision 20051216
[17179570.880000] ACPI: Interpreter enabled
[17179570.880000] ACPI: Using IOAPIC for interrupt routing
[17179570.880000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[17179570.880000] PCI: Probing PCI hardware (bus 00)
[17179570.884000] PCI quirk: region 0800-087f claimed by vt8235 PM
[17179570.884000] PCI quirk: region 0400-040f claimed by vt8235 SMB
[17179570.884000] Boot video device is 0000:01:00.0
[17179570.884000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[17179570.896000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[17179570.900000] ACPI: Embedded Controller [EC0] (gpe 4) interrupt mode.
[17179571.652000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[17179571.652000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 10 11 12 14 15)
[17179571.652000] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 11 12 14 15)
[17179571.652000] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 10 11 12 14 15)
[17179571.652000] Linux Plug and Play Support v0.97 (c) Adam Belay
[17179571.652000] pnp: PnP ACPI init
[17179571.656000] pnp: PnP ACPI: found 11 devices
[17179571.656000] PnPBIOS: Disabled by ACPI PNP
[17179571.656000] SCSI subsystem initialized
[17179571.656000] usbcore: registered new driver usbfs
[17179571.656000] usbcore: registered new driver hub
[17179571.656000] PCI: Using ACPI for IRQ routing
[17179571.656000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[17179571.660000] PCI: Bridge: 0000:00:01.0
[17179571.660000] IO window: disabled.
[17179571.660000] MEM window: fc200000-fe2fffff
[17179571.660000] PREFETCH window: f2100000-fa0fffff
[17179571.660000] PCI: Bus 2, cardbus bridge: 0000:00:0a.0
[17179571.660000] IO window: 00001000-000010ff
[17179571.660000] IO window: 00001400-000014ff
[17179571.660000] PREFETCH window: 20000000-21ffffff
[17179571.660000] MEM window: 22000000-23ffffff
[17179571.660000] PCI: Setting latency timer of device 0000:00:01.0 to 64
[17179571.660000] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 16
[17179571.660000] Machine check exception polling timer started.
[17179571.660000] audit: initializing netlink socket (disabled)
[17179571.660000] audit(1172460202.660:1): initialized
[17179571.660000] VFS: Disk quotas dquot_6.5.1
[17179571.660000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[17179571.660000] squashfs: version 3.1 (2006/08/15) Phillip Lougher
[17179571.660000] NTFS driver 2.1.25 [Flags: R/W].
[17179571.660000] JFS: nTxBlock = 3514, nTxLock = 28115
[17179571.664000] Registering unionfs 1.1.2
[17179571.664000] Initializing Cryptographic API
[17179571.664000] io scheduler noop registered
[17179571.664000] io scheduler anticipatory registered
[17179571.664000] io scheduler deadline registered
[17179571.664000] io scheduler cfq registered
[17179571.664000] vesafb: framebuffer at 0xf4000000, mapped to 0xdca80000, using 3072k, total 65536k
[17179571.664000] vesafb: mode is 1024x768x16, linelength=2048, pages=41
[17179571.664000] vesafb: protected mode interface info at c000:9b9d
[17179571.664000] vesafb: scrolling: redraw
[17179571.664000] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[17179571.664000] vesafb: Mode is VGA compatible
[17179571.808000] Console: switching to colour frame buffer device 128x48
[17179571.808000] fb0: VESA VGA frame buffer device
[17179571.808000] isapnp: Scanning for PnP cards...
[17179572.120000] isapnp: No Plug & Play device found
[17179572.132000] Non-volatile memory driver v1.2
[17179572.132000] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[17179572.132000] i8042.c: Detected active multiplexing controller, rev 1.1.
[17179572.136000] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[17179572.136000] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[17179572.136000] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[17179572.136000] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[17179572.136000] serio: i8042 KBD port at 0x60,0x64 irq 1
[17179572.136000] Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
[17179572.136000] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[17179572.136000] loop: loaded (max 8 devices)
[17179572.136000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179572.136000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[17179572.136000] VP_IDE: IDE controller at PCI slot 0000:00:11.1
[17179572.136000] ACPI: PCI Interrupt 0000:00:11.1[A]: no GSI
[17179572.136000] PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 15
[17179572.136000] VP_IDE: chipset revision 6
[17179572.136000] VP_IDE: not 100% native mode: will probe irqs later
[17179572.136000] VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
[17179572.136000] ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
[17179572.136000] ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:pio
[17179572.136000] Probing IDE interface ide0...
[17179572.556000] hda: IC25N060ATMR04-0, ATA DISK drive
[17179572.892000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179572.892000] Probing IDE interface ide1...
[17179573.756000] hdc: HL-DT-ST DVD-RW GCA-4080N, ATAPI CD/DVD-ROM drive
[17179574.092000] ide1 at 0x170-0x177,0x376 on irq 15
[17179574.092000] hda: max request size: 1024KiB
[17179574.112000] hda: Host Protected Area detected.
[17179574.112000] current capacity is 108058859 sectors (55326 MB)
[17179574.112000] native capacity is 117210240 sectors (60011 MB)
[17179574.112000] hda: Host Protected Area disabled.
[17179574.112000] hda: 117210240 sectors (60011 MB) w/7884KiB Cache, CHS=16383/255/63, UDMA(100)
[17179574.112000] hda: cache flushes supported
[17179574.112000] hda: hda1 hda2 hda3
[17179574.172000] hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
[17179574.172000] Uniform CD-ROM driver Revision: 3.20
[17179574.180000] ACPI: bus type scsi registered
[17179574.180000] libata version 1.20 loaded.
[17179574.180000] Driver 'sd' needs updating - please use bus_type methods
[17179574.180000] ieee1394: Initialized config rom entry `ip1394'
[17179574.180000] ieee1394: raw1394: /dev/raw1394 device initialized
[17179574.180000] sbp2: $Rev: 1306 $ Ben Collins
[17179574.180000] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
[17179574.180000] ieee1394: sbp2: Try serialize_io=0 for better performance
[17179574.180000] usbmon: debugfs is not available
[17179574.180000] ACPI: PCI Interrupt 0000:00:10.3[D] -> GSI 21 (level, low) -> IRQ 17
[17179574.180000] PCI: Via IRQ fixup for 0000:00:10.3, from 7 to 1
[17179574.180000] ehci_hcd 0000:00:10.3: EHCI Host Controller
[17179574.180000] ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
[17179574.180000] ehci_hcd 0000:00:10.3: irq 17, io mem 0xfebfdc00
[17179574.180000] ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[17179574.180000] hub 1-0:1.0: USB hub found
[17179574.180000] hub 1-0:1.0: 6 ports detected
[17179574.284000] Initializing USB Mass Storage driver...
[17179574.468000] usbcore: registered new driver usb-storage
[17179574.468000] USB Mass Storage support registered.
[17179574.468000] mice: PS/2 mouse device common for all mice
[17179574.468000] NET: Registered protocol family 2
[17179574.504000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[17179574.504000] TCP established hash table entries: 16384 (order: 4, 65536 bytes)
[17179574.504000] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[17179574.504000] TCP: Hash tables configured (established 16384 bind 16384)
[17179574.504000] TCP reno registered
[17179574.504000] ip_tables: (C) 2000-2002 Netfilter core team
[17179574.540000] TCP bic registered
[17179574.540000] NET: Registered protocol family 1
[17179574.540000] NET: Registered protocol family 8
[17179574.540000] NET: Registered protocol family 20
[17179574.540000] Using IPI Shortcut mode
[17179574.540000] ACPI wakeup devices:
[17179574.540000] PCI0 MC97 USB1 USB2 USB3 EHCI CBC0 ILAN SLPB
[17179574.540000] ACPI: (supports S0 S3 S4 S5)
[17179574.596000] EXT3-fs: INFO: recovery required on readonly filesystem.
[17179574.596000] EXT3-fs: write access will be enabled during recovery.
[17179574.624000] input: AT Translated Set 2 keyboard as /class/input/input0
[17179577.488000] EXT3-fs: hda2: orphan cleanup on readonly fs
[17179577.488000] ext3_orphan_cleanup: deleting unreferenced inode 3647172
[17179577.488000] EXT3-fs: hda2: 1 orphan inode deleted
[17179577.488000] EXT3-fs: recovery complete.
[17179577.488000] kjournald starting. Commit interval 5 seconds
[17179577.516000] EXT3-fs: mounted filesystem with ordered data mode.
[17179577.516000] VFS: Mounted root (ext3 filesystem) readonly.
[17179577.516000] Freeing unused kernel memory: 192k freed
[17179579.072000] EXT3 FS on hda2, internal journal
[17179583.540000] Adding 1116508k swap on /dev/hda3. Priority:1 extents:1 across:1116508k
[17179583.828000] EXT3 FS on hda2, internal journal
[17179586.708000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179586.816000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179586.856000] USB Universal Host Controller Interface driver v2.3
[17179586.856000] ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 17
[17179586.856000] PCI: Via IRQ fixup for 0000:00:10.0, from 5 to 1
[17179586.856000] uhci_hcd 0000:00:10.0: UHCI Host Controller
[17179586.856000] uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
[17179586.856000] uhci_hcd 0000:00:10.0: irq 17, io base 0x0000e400
[17179586.856000] hub 2-0:1.0: USB hub found
[17179586.856000] hub 2-0:1.0: 2 ports detected
[17179586.928000] ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 16 (level, low) -> IRQ 18
[17179586.928000] rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com
[17179586.972000] ACPI: PCI Interrupt 0000:00:10.1[B] -> GSI 21 (level, low) -> IRQ 17
[17179586.972000] PCI: Via IRQ fixup for 0000:00:10.1, from 4 to 1
[17179586.972000] uhci_hcd 0000:00:10.1: UHCI Host Controller
[17179586.972000] uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
[17179586.972000] uhci_hcd 0000:00:10.1: irq 17, io base 0x0000e800
[17179586.972000] hub 3-0:1.0: USB hub found
[17179586.972000] hub 3-0:1.0: 2 ports detected
[17179586.996000] Linux agpgart interface v0.101 (c) Dave Jones
[17179587.076000] ACPI: PCI Interrupt 0000:00:10.2[C] -> GSI 21 (level, low) -> IRQ 17
[17179587.076000] PCI: Via IRQ fixup for 0000:00:10.2, from 3 to 1
[17179587.076000] uhci_hcd 0000:00:10.2: UHCI Host Controller
[17179587.076000] uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
[17179587.076000] uhci_hcd 0000:00:10.2: irq 17, io base 0x0000ec00
[17179587.076000] hub 4-0:1.0: USB hub found
[17179587.076000] hub 4-0:1.0: 2 ports detected
[17179587.108000] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 16
[17179587.108000] Yenta: CardBus bridge found at 0000:00:0a.0 [14ff:0613]
[17179587.108000] Yenta: adjusting diagnostic: 40 -> 60
[17179587.108000] Yenta: Enabling burst memory read transactions
[17179587.108000] Yenta: Using CSCINT to route CSC interrupts to PCI
[17179587.108000] Yenta: Routing CardBus interrupts to PCI
[17179587.108000] Yenta TI: socket 0000:00:0a.0, mfunc 0x012c1202, devctl 0x44
[17179587.120000] irda_init()
[17179587.120000] NET: Registered protocol family 23
[17179587.156000] Real Time Clock Driver v1.12
[17179587.340000] Yenta: ISA IRQ mask 0x08c0, PCI irq 16
[17179587.340000] Socket status: 30000006
[17179587.344000] input: PC Speaker as /class/input/input1
[17179587.468000] usb 3-1: new low speed USB device using uhci_hcd and address 2
[17179587.628000] ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 19
[17179587.628000] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
[17179587.628000] PCI: Setting latency timer of device 0000:00:11.5 to 64
[17179587.632000] PCI: Setting latency timer of device 0000:00:11.6 to 64
[17179587.700000] Synaptics Touchpad, model: 1, fw: 5.1, id: 0x8f40b1, caps: 0x80471b/0x0
[17179587.740000] input: SynPS/2 Synaptics TouchPad as /class/input/input2
[17179587.740000] wbsd: Winbond W83L51xD SD/MMC card interface driver, 1.5
[17179587.740000] wbsd: Copyright(c) Pierre Ossman
[17179587.740000] wbsd: PnP active but chip not configured! You probably have a buggy BIOS. Configuring chip manually.
[17179587.748000] mmc0: W83L51xD id 7112 at 0x248 irq 5 dma 2 PnP
[17179587.828000] via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
[17179587.888000] cs: IO port probe 0x100-0x3af: clean.
[17179587.892000] cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
[17179587.892000] cs: IO port probe 0x820-0x8ff: clean.
[17179587.892000] cs: IO port probe 0xc00-0xcf7: clean.
[17179587.892000] cs: IO port probe 0xa00-0xaff: clean.
[17179588.024000] usbcore: registered new driver hiddev
[17179588.040000] input: Logitech Trackball as /class/input/input3
[17179588.040000] input: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:10.1-1
[17179588.040000] usbcore: registered new driver usbhid
[17179588.040000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[17179588.172000] ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 20
[17179588.172000] PCI: Via IRQ fixup for 0000:00:12.0, from 3 to 4
[17179588.176000] eth0: VIA Rhine II at 0x1d400, 00:40:45:26:6b:83, IRQ 20.
[17179588.176000] eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
[17179588.600000] agpgart: Detected AGP bridge 0
[17179588.604000] agpgart: AGP aperture is 64M @ 0xd0000000
[17179589.304000] fuse init (API version 7.
[17179589.304000] fuse distribution version: 2.6.1
[17179589.516000] md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
[17179589.516000] md: bitmap version 4.39
[17179590.092000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
[17179591.348000] cdrom: open failed.
[17179597.980000] powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.4)
[17179597.984000] powernow-k8: 0 : fid 0x0 (800 MHz), vid 0x13 (1075 mV)
[17179597.984000] powernow-k8: 1 : fid 0x8 (1600 MHz), vid 0x8 (1350 mV)
[17179597.984000] cpu_init done, current fid 0x8, vid 0xc
[17179597.984000] powernow-k8: ph2 null fid transition 0x8
[17179598.000000] powernow: This module only works with AMD K7 CPUs
[17179598.116000] floppy0: Unable to grab DMA2 for the floppy driver
[17179598.940000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
[17179599.068000] usbcore: registered new driver ndiswrapper
[17179601.048000] ACPI: AC Adapter [AC] (on-line)
[17179601.460000] ACPI: Battery Slot [BAT0] (battery present)
[17179601.520000] ACPI: Power Button (FF) [PWRF]
[17179601.520000] ACPI: Sleep Button (CM) [SLPB]
[17179601.520000] ACPI: Lid Switch [LIDD]
[17179601.520000] ACPI: Power Button (CM) [PWRB]
[17179601.628000] ibm_acpi: ec object not found
[17179601.660000] pcc_acpi: loading...
[17179601.876000] ACPI: Thermal Zone [THRM] (79 C)
[17179601.920000] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[17179608.264000] rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel
[17179608.264000] rt2500 EEPROM: 4 4 4 4 4 5 6 6 6 6 6 6 7 7 dBm Maximum
[17179608.280000] eth0: link down
[17179611.752000] lp: driver loaded but no devices found
[17179611.772000] ppdev: user-space parallel port driver
[17179623.352000] rt2500MlmeEnqueue full, msg dropped and may corrupt MLME
[17179703.948000] rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel
[17179703.948000] rt2500 EEPROM: 4 4 4 4 4 5 6 6 6 6 6 6 7 7 dBm Maximum
[17179778.332000] usb 3-1: USB disconnect, address 2
[17179790.144000] psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 1 bytes away.
[17179790.144000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179790.144000] rt2500MlmeEnqueue full, msg dropped and may corrupt MLME
[17179793.788000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179793.800000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179793.804000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[17179793.808000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179793.808000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179793.808000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179793.812000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[17179793.820000] psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
[17179905.344000] usb 2-2: new low speed USB device using uhci_hcd and address 2
[17179905.532000] input: Logitech Trackball as /class/input/input4
[17179905.532000] input: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:10.0-2
[17180061.440000] rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel
[17180061.440000] rt2500 EEPROM: 4 4 4 4 4 5 6 6 6 6 6 6 7 7 dBm Maximum

I noticed you have a semprom 64 bit processor--doesn't that mean you have a 3270 model? Anyway, you might backup your /etc/X11/xorg.conf file and then run as root in a terminal

dpkg-reconfigure xserver-xorg

try accepting all the default responses

if this breaks your GUI, log in as root text mode

cd /etc/X11/

cp xorg.conf.bak (or whatever you named it) xorg.conf

startx

Let me check but I have had this laptop for a while and I am positive it is a 3250. But let me make sure.
OK here it is. I take it as a 32bit.

Processor: AMD Athlon XP-M 2200+ (1.67 GHz)
Operating System: MEPIS 6.5-beta 6
Display: 12.1 inch 1024 x 768 XGA LCD; S3 Unichrome display controller /w shared video memory
Memory: 512 MB PC2700 (333 MHz) DDR RAM
Storage: 80 GB 4200 RPM 9.5mm Hitachi Travelstar hard drive
Optical Drive: QSI SDW-042 dual format 4x/2x DVD RW drive
Size & Weight: 10.9 inches wide x 9.6 inches deep x 1.0 inch thick, 4.4 pounds
Expansion: 1x CardBus slot, 1x VGA out, 1x RJ45 ethernet, 1x RJ11 modem, 3x USB 2.0 ports
Docking: No docking connector
Communication: Integrated 802.11g WiFi, 10/100 ethernet, 56k modem

Audio: 1x headphone jack, 1x microphone jack, internal stereo speakers
Input: Standard keyboard, touchpad
Battery: 44 watt-hour (11.1 volt, 4.0 amp-hour) Lithium Ion battery

root@1[snaker]# dpkg-reconfigure xserver-xorg
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 column
s wide.)
debconf: falling back to frontend: Readline
Configuring xserver-xorg
------------------------

You should choose this option if you would like to attempt to autodetect the
recommended X server and driver module for your video card. If the
autodetection fails, you will be asked to specify the desired X server and/or
driver module. If it succeeds, further configuration questions about your video
hardware will be pre-answered.

[More]

If you would rather select the X server and driver module yourself, do not
choose this option. You will not be asked to select the X server if there is
only one available.

Attempt to autodetect video hardware?

Attempt to autodetect video hardware?

Attempt to autodetect video hardware?

Attempt to autodetect video hardware?

Attempt to autodetect video hardware? yes

For the X Window System graphical user interface to operate correctly, it is necessary to select a video card driver for the X server.

Drivers are typically named for the video card or chipset manufacturer, or for a specific model or family of chipsets.

1. apm 4. chips 7. fbdev 10. i740 13. mga 16. nsc 19. s3 22. siliconmotion 25. tdfx 28. tseng 31. via
2. ark 5. cirrus 8. glint 11. i810 14. neomagic 17. nv 20. s3virge 23. sis 26. tga 29. vesa 32. vmware
3. ati 6. cyrix 9. i128 12. imstt 15. newport 18. rendition 21. savage 24. sisusb 27. trident 30. vga 33. voodoo

X server driver: 19

The X server configuration file associates your video card with a name that you may provide. This is usually the vendor or brand name
followed by the model name, e.g., "Intel i915", "ATI RADEON X800", or "NVIDIA GeForce 6600".

Identifier for your video card: s3

Users of PowerPC machines, and users of any computer with multiple video devices, should specify the BusID of the video card in an accepted
bus-specific format.

Examples:

ISA:1
PCI:0:16:0
SBUS:/iommu@0,10000000/sbus@0,10001000/SUNW,tcx@2,800000

For users of multi-head setups, this option will configure only one of the heads. Further configuration will have to be done manually in the
X server configuration file, /etc/X11/xorg.conf.

You may wish to use the "lspci -X" command to determine the bus location of your PCI, AGP, or PCI-Express video card.

When possible, this question has been pre-answered for you and you should accept the default unless you know it doesn't work.

Video card's bus identifier:

Typically, the amount of dedicated memory used by the video card is autodetected by the X server, but some integrated video chips (such as
the Intel i810) have little or no video memory of their own, and instead borrow main system memory for their needs.

This parameter should usually be left blank and specified only if the video card lacks RAM, or if the X server has trouble autodetecting the
RAM size.

Amount of memory (kB) to be used by the video card:

Rather than communicating directly with the video hardware, the X server may be configured to perform some operations, such as video mode
switching, via the kernel's framebuffer driver.

In theory, either approach should work, but in practice, sometimes one does and the other does not. Enabling this option is the safe bet,
but feel free to turn it off if it appears to cause problems.

Use kernel framebuffer device interface?

Use kernel framebuffer device interface? yes

The default keyboard layout selection for the Xorg server will be based on a combination of the language and the keyboard layout selected in
the installer.

Choose this option if you want the keyboard layout to be redetected. Do not choose it if you want to keep your current layout.

Autodetect keyboard layout?

Autodetect keyboard layout? yes

xserver-xorg config warning: failed to infer keyboard layout from layout/lang
'10 debian-installer/keymap doesn't exist--10 debian-installer/language
doesn't exist'
For the X server to handle the keyboard correctly, a keyboard layout must be entered. Available layouts depend on which XKB rule set and
keyboard model were previously selected.

Experienced users can use any layout supported by the selected XKB rule set. If the xkeyboard-config package has been unpacked, see the
/etc/X11/xkb/rules directory for available rule sets.

Users of U.S. English keyboards should enter "us". Users of keyboards localized for other countries should generally enter their ISO 3166
country code. E.g., France uses "fr", and Germany uses "de".

Keyboard layout: us

For the X server to handle the keyboard correctly, an XKB rule set must be chosen.

Users of most keyboards should enter "xorg". Users of Sun Type 4 and Type 5 keyboards, however, should enter "sun".

Experienced users can use any defined XKB rule set. If the xkeyboard-config package has been unpacked, see the /etc/X11/xkb/rules directory
for available rule sets.

When in doubt, this value should be set to "xorg".

XKB rule set to use: xorg

For the X server to handle the keyboard correctly, a keyboard model must be entered. Available models depend on which XKB rule set is in
use.

With the "xorg" rule set:
- pc101: traditional IBM PC/AT style keyboard with 101 keys, common in
the United States. Has no "logo" or "menu" keys;
- pc104: similar to pc101 model, with additional keys, usually engraved
with a "logo" symbol and a "menu" symbol;
- pc102: similar to pc101 and often found in Europe. Includes a "< >" key;
- pc105: similar to pc104 and often found in Europe. Includes a "< >" key;
- macintosh: Macintosh keyboards using the new input layer with Linux
keycodes;
- macintosh_old: Macintosh keyboards not using the new input layer.
With the "sun" rule set:
- type4: Sun Type4 keyboards;
- type5: Sun Type5 keyboards.

Laptop keyboards often do not have as many keys as standalone models; laptop users should select the keyboard model most closely approximated
by the above.

Experienced users can use any model defined by the selected XKB rule set. If the xkeyboard-config package has been unpacked, see the
/etc/X11/xkb/rules directory for available rule sets.

Users of U.S. English keyboards should generally enter "pc104". Users of most other keyboards should generally enter "pc105".

Keyboard model: pc104

For the X server to handle the keyboard as desired, a keyboard variant may be entered. Available variants depend on which XKB rule set,
model, and layout were previously selected.

Many keyboard layouts support an option to treat "dead" keys such as non-spacing accent marks and diaereses as normal spacing keys, and if
this is the preferred behavior, enter "nodeadkeys".

Experienced users can use any variant supported by the selected XKB layout. If the xkeyboard-config package has been unpacked, see the
/etc/X11/xkb/symbols directory for the file corresponding to your selected layout for available variants.

Users of U.S. English keyboards should generally leave this entry blank.

Keyboard variant:

For the X server to handle the keyboard as desired, keyboard options may be entered. Available options depend on which XKB rule set was
previously selected. Not all options will work with every keyboard model and layout.

For example, if you wish the Caps Lock key to behave as an additional Control key, you may enter "ctrl:nocaps"; if you would like to switch
the Caps Lock and left Control keys, you may enter "ctrl:swapcaps".

As another example, some people prefer having the Meta keys available on their keyboard's Alt keys (this is the default), while other people
prefer having the Meta keys on the Windows or "logo" keys instead. If you prefer to use your Windows or logo keys as Meta keys, you may
enter "altwin:meta_win".

You can combine options by separating them with a comma, for instance "ctrl:nocaps,altwin:meta_win".

Experienced users can use any options compatible with the selected XKB model, layout and variant.

When in doubt, this value should be left blank.

Keyboard options:

1. ImPS/2 2. ExplorerPS/2

Mouse protocol:

Mouse protocol: 1

Most programs in the X Window System expect the mouse to have 3 buttons (left, right, and middle). Mice with only 2 buttons can emulate the
presence of a middle button by treating simultaneous clicks or drags of the left and right buttons as middle button events.

This option may also be used on mice with 3 or more buttons; the middle button will continue to work normally.

Note that mouse buttons in excess of five (counting a scroll wheel as two buttons, one each for "up" and "down", and a third if the wheel
"clicks") are not yet supported with this configuration tool.

Emulate 3 button mouse?

Emulate 3 button mouse? yes

This option is recommended to experienced users only. In most cases, all of these modules should be enabled.

- glx : support for OpenGL rendering;
- dri : support in the X server for DRI (Direct Rendering Infrastructure);
- vbe : support for VESA BIOS Extensions. Allows to query
the monitor capabilities via the video card;
- ddc : support for Data Display Channel, respectively. Allows to query
the monitor capabilities via the video card;
- int10 : real-mode x86 emulator used to softboot secondary VGA cards.
Should be enabled if vbe is enabled;
- dbe : enables the double-buffering extension in the server.
Useful for animation and video operations;
- extmod: enables many traditional and commonly used extensions, such as
shaped windows, shared memory, video mode switching, DGA, and Xv;
- record: implements the RECORD extension, often used in server testing;
- bitmap: font rasterizer (so are freetype, and type1 modules).

For further information about these modules, please consult the X.Org documentation.

1. bitmap 3. ddc 5. extmod 7. glx 9. record 11. v4l 13. none of the above
2. dbe 4. dri 6. freetype 8. int10 10. type1 12. vbe

(Enter the items you want to select, separated by spaces.)

X.Org server modules that should be loaded by default:

The Files section of the X server configuration file tells the X server where to find server modules, the RGB color database, and font files.
This option is recommended to experienced users only. In most cases, it should be enabled.

Disable this option if you want to maintain a custom Files section into the X.Org server configuration file. This may be needed to remove
the reference to the local font server, add a reference to a different font server, or rearrange the default set of local font paths.

Write default Files section to configuration file?

Write default Files section to configuration file? yes

md5sum: /etc/X11/xorg.conf: No such file or directory
Many monitors (including LCD's) and video cards support a communication protocol that allows the monitor's technical characteristics to be
communicated back to the computer. If the monitor and video card support this protocol, further configuration questions about the monitor
will be pre-answered.

If autodetection fails, you will be asked for information about the monitor.

Attempt monitor autodetection?

Attempt monitor autodetection? yes

The X server configuration file associates the monitor with a name that you may provide. This is usually the vendor or brand name followed
by the model name, e.g., "Sony E200" or "Dell E770s".

Identifier for the monitor: lcd

Please keep only the resolutions you would like the X server to use. Removing all of them is the same as removing none, since in both cases
the X server will attempt to use the highest possible resolution.

1. 1920x1440 4. 1792x1344 7. 1440x900 10. 1280x960 13. 1280x768 16. 1152x768 19. 640x480
2. 1920x1200 5. 1680x1050 8. 1400x1050 11. 1280x854 14. 1200x800 17. 1024x768 20. none of the above
3. 1856x1392 6. 1600x1200 9. 1280x1024 12. 1280x800 15. 1152x864 18. 800x600

(Enter the items you want to select, separated by spaces.)

Video modes to be used by the X server: 16 17 18 19

For the X Window System graphical user interface to operate correctly, certain characteristics of the monitor must be known.

The "simple" option will prompt about the monitor's physical size; this will set some configuration values appropriate for a typical CRT of
the corresponding size, but may be suboptimal for high-quality CRT's.

The "medium" option will present you with a list of resolutions and refresh rates, such as "800x600 @ 85Hz"; you should choose the best mode
you wish to use (and that you know the monitor is capable of).

The "advanced" option will let you specify the monitor's horizontal sync and vertical refresh tolerances directly.

1. Simple 2. Medium 3. Advanced

Method for selecting the monitor characteristics: 2

Choose the "best" resolution and refresh rate the monitor is capable of. Larger resolutions and refresh rates are better. With a CRT
monitor, it is perfectly acceptable to select a "worse" video mode than the monitor's best if you wish. Users of LCD displays may also be
able to do this, but only if both the video chipset and the driver support it; if in doubt, use the video mode recommended by the
manufacturer of your LCD.

1. 640x480 @ 60Hz 7. 1024x768 @ 60Hz 13. 1280x960 @ 60Hz 19. 1600x1024 @ 60Hz 25. 1792x1344 @ 75Hz 31. 1920x1440 @ 75Hz
2. 640x480 @ 72Hz 8. 1024x768 @ 70Hz 14. 1280x960 @ 85Hz 20. 1600x1200 @ 60Hz 26. 1856x1392 @ 60Hz 32. 1920x1440 @ 85Hz
3. 800x600 @ 60Hz 9. 1024x768 @ 75Hz 15. 1280x1024 @ 60Hz 21. 1600x1200 @ 75Hz 27. 1856x1392 @ 75Hz 33. 2048x1536 @ 60Hz
4. 800x600 @ 72Hz 10. 1152x768 @ 54.8Hz 16. 1400x1050 @ 60Hz 22. 1600x1200 @ 85Hz 28. 1920x1200 @ 60Hz 34. 2048x1536 @ 75Hz
5. 800x600 @ 85Hz 11. 1152x768 @ 60Hz 17. 1400x1050 @ 75Hz 23. 1680x1050 @ 75Hz 29. 1920x1200 @ 75 Hz 35. 2048x1536 @ 85Hz
6. 832x624 @ 75Hz 12. 1152x864 @ 75Hz 18. 1440x900 @ 100Hz 24. 1792x1344 @ 60Hz 30. 1920x1440 @ 60Hz

Monitor's best video mode: 9

The monitor synchronization ranges should be autodetected by the X server in most cases, but sometimes it needs hinting. This option is for
experienced users, and should be left at its default.

Write monitor sync ranges to the configuration file?

Write monitor sync ranges to the configuration file? yes

Usually 24-bit color is desirable, but on graphics cards with limited amounts of framebuffer memory, higher resolutions may be achieved at
the expense of higher color depth. Also, some cards support hardware 3D acceleration only for certain depths. Consult your video card
manual for more information.

So-called "32-bit color" is actually 24 bits of color information plus 8 bits of alpha channel or simple zero padding; the X Window System
can handle both. If you want either, select 24 bits.

1. 1 2. 4 3. 8 4. 15 5. 16 6. 24

Desired default color depth in bits: 6