lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201003120058.28812.andrewb@inf.ethz.ch>
Date:	Fri, 12 Mar 2010 00:58:28 +0100
From:	Andrew Baumann <andrewb@....ethz.ch>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Andrew Baumann <andrewb@....unsw.edu.au>,
	linux-kernel@...r.kernel.org,
	Lara Michaels <laramichaels1978@...oo.com>
Subject: Re: PCI: Cannot allocate resource regions of bridge and device in ThinkPad dock

On Thursday 11 March 2010 21.05:04 Bjorn Helgaas wrote:
> On Wednesday 05 July 2006 09:45:31 pm Andrew Baumann wrote:
> > I'm unable to use a radeon card installed in the PCI slot of a thinkpad
> > docking station. This is from a clean boot in the dock (no hot
> > dock/undock), and appears on vendor-provided 2.6.16 and 2.6.17 kernels,
> > as well as on a self-built 2.6.17-git25 tree.
> 
> Did you ever get this ancient (2006!) issue resolved?  I didn't see
> any responses on the list, and Lara is having a sort of similar issue:
>   http://bugzilla.kernel.org/show_bug.cgi?id=15436
> 
> I think your problem was that Linux saw the Radeon card but didn't assign
> resources correctly, while in Lara's case, Linux doesn't see the card at
> all.

Wow, that is ancient! I'm afraid I can't help you, as I no longer have the 
hardware in question, but I found some sort of workaround. It either involved 
kernel boot parameters or a newer version of the kernel, and I don't recall 
the details, but I did eventually get the card to work.

Sorry this isn't any use,
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ