Bug#522234: debian-installer: Fails to boot on amd64 4GB RAM: still valid?

2010-08-25 Thread Holger Wansing
Hello,

this bug reported about d-i not beeing able to boot on a
machine with 4GB of RAM. 
It was also mentioned, that with an 2.6.28 or .29 linux kernel,
all worked fine at that time.

So, now we have 2.6.32 in d-i. 
Do you have a possibility to try, if this problem still exists?



Thanks
Holger

-- 

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
under DEBIAN GNU/LINUX 5.0.0 - L e n n y
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100825220332.ed5d36eb.li...@wansing-online.de



Bug#522234: debian-installer: Fails to boot on amd64 4GB RAM

2009-04-01 Thread Hector Oron
Package: debian-installer
Version: 20090123
Severity: normal

Hi,

  I am booting an amd64 host with PXE method, once i get to the first
screen i press 'Install'..

Decompressing Linux... Parsing ELF... done.
Booting the kernel.

Aperture beyond 4G. Ignoring
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64MB of RAM
PCI: Cannot allocate resource region 1 of device :00:14.0

halt

I had etch installed succesfully and BIOS was ok. When updating
linux-image from 2.6.18 to 2.6.26, .26 never booted on my system. I
guess the failure was related to this issue. I have tried newer kernel
versions, .28 and .29, compiled at home and linux-image from unstable
and it works fine.

Tracking this issue I got to the idea that having 4GB (my system has
8GB) does not leave space to allocate AGP devices.

If you need more info, testing or whatever, feel free to ask me for it.

Kind regards

-- 
 Héctor Orón



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org