From: giskard <giskard@autistici.org>
To: luming.yu@intel.com, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: error on handling I/O ports
Date: Fri, 13 May 2005 18:19:37 +0200 [thread overview]
Message-ID: <20050513181937.471934b2@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
>Could you just try acpi=off ?
pcmcia seems work with acpi=off but obviously battery and cpu scaling
are not supported. any hint?
On Monday 25 April 2005 22:09, giskard wrote:
> hi all,
>
> The 2.6.* kernel doesn't seems to handle properly the I/O ports for
> devices.
>
> I bought a toshiba satellite a80-111 and with 2.4 series all devices
> work good, with 2.6 series i get some errors:
>
> - the 2.4 kernel uses ide-generic (with sata support) for use the
> hd, with 2.6 i need libata SATA support because i get this error
>
> ide0: I/O resource 0x1F0-0x1F7 not free.
> ide0: ports already in use, skipping probe
>
> - i have a 0000:06:04.0 CardBus bridge: Texas Instruments Texas
> Instruments PCIxx21/ x515 Cardbus Controller
>
> i can get it work with the 2.4 series with no problem (yenta
> socket), the 2.6 series uses also yenta sockets but when i start
> pcmcia service (/ etc/ init.d/pcmcia start) the kernel freezes when
> it checks the i/o ports.
>
>
> mrspurr:/usr/src/linux# uname -a
> Linux mrspurr 2.6.11.7 #12 Mon Apr 18 01:51:04 CEST 2005 i686 GNU/
> Linux
>
> i attached lspci -vvv log, iomem log, ioports log, cpuinfo log
>
> thank you in advance
--
ciao giskard
spero nel ritorno del grande bastardo.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-05-13 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 16:19 giskard [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-25 14:09 PROBLEM: error on handling I/O ports giskard
2005-04-27 2:34 ` Yu, Luming
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=20050513181937.471934b2@localhost.localdomain \
--to=giskard@autistici.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox