All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <Stephen.Clark@seclark.us>
To: Luming Yu <luming.yu@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: New laptop - problems with linux
Date: Wed, 08 Nov 2006 10:56:04 -0500	[thread overview]
Message-ID: <4551FE14.7010801@seclark.us> (raw)
In-Reply-To: <3877989d0611080704j30b88bd4o4558e606fd6ffc11@mail.gmail.com>

Luming Yu wrote:

>On 11/8/06, Stephen Clark <Stephen.Clark@seclark.us> wrote:
>  
>
>>Hi list,
>>
>>I just purchased a VBI-Asus S96F laptop Intel 945GM &  ICH7, with a Core
>>2 Duo T560,0 2gb pc5400 memory.
>> From checking around it appeared all the
>>hardware was well supported by linux - but I am having major problems.
>>
>>
>>1. neither the wireless lan Intel pro 3945ABG or built in ethernet
>>RTL-8169C are detected and configured
>>2. the disk which is a 7200rpm Hitachi travelmate transfers data at 1.xx
>>mb/sec
>>   according to hdparm. This same drive in my old laptop an HP n5430 with a
>>   850 duron the rate was 12-14 mb/sec.
>>
>>Attached are the output of lspci -vvv, dmesg and hdparm
>>Any insight would be greatly appreciated.
>>
>>    
>>
>
>Sounds like interrupt problem. Could you post /proc/interrupts?
>It is worthy to try pci=noacpi.
>
>  
>

           CPU0       CPU1
  0:     902788     893290    IO-APIC-edge  timer
  1:       1444       1393    IO-APIC-edge  i8042
  8:          1          0    IO-APIC-edge  rtc
  9:      16443      16618   IO-APIC-level  acpi
 12:      13089      14223    IO-APIC-edge  i8042
 14:          0          0    IO-APIC-edge  libata
 15:     223418     202091    IO-APIC-edge  ide1
169:     129430     129240   IO-APIC-level  uhci_hcd:usb4, ohci1394, HDA 
Intel, i915@pci:0000:00:02.0
177:          0          0   IO-APIC-level  sdhci:slot0
185:          0          0   IO-APIC-level  uhci_hcd:usb3
225:        527        660   IO-APIC-level  uhci_hcd:usb1, ehci_hcd:usb5
233:        629        145   IO-APIC-level  uhci_hcd:usb2
NMI:          0          0
LOC:    1793413    1794404
ERR:          0
MIS:          0

tried pci=noacpi
only minor difference in interrupt assignments.

Steve

-- 

"They that give up essential liberty to obtain temporary safety, 
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty 
decreases."  (Thomas Jefferson)




  reply	other threads:[~2006-11-08 15:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 14:41 New laptop - problems with linux Stephen Clark
2006-11-08 14:59 ` Arjan van de Ven
2006-11-08 15:12   ` Stephen Clark
2006-11-08 15:04 ` Luming Yu
2006-11-08 15:56   ` Stephen Clark [this message]
2006-11-08 15:11 ` Jiri Slaby
2006-11-08 15:20   ` Stephen Clark
2006-11-08 15:28     ` Jiri Slaby
2006-11-08 18:26     ` Francois Romieu
2006-11-08 19:39       ` Stephen Clark
2006-11-08 20:26         ` Stephen Hemminger
2006-11-08 20:34           ` Stephen Clark
2006-11-08 20:53             ` Jesper Juhl
2006-11-08 21:21               ` Stephen Clark
2006-11-09  4:38             ` Tejun Heo
2006-11-09  8:32 ` Jarek Poplawski
2006-11-09 14:08   ` Stephen Clark
2006-11-10  7:08     ` Jarek Poplawski
2006-11-10 14:39       ` Stephen Clark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4551FE14.7010801@seclark.us \
    --to=stephen.clark@seclark.us \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.