[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#339563: amd64 etch beta 1 release

Uhm, this is strange: it seems that the miniiso cdrom has booted in graphical mode even if you told it at boot time to start the textual semi-graphical frontend based on the newt libraries (using "install DEBIAN_FRONTEND=newt"). 
Could this be a bug in some of the components of the graphical miniiso?
When screen flashes continuously is because the graphical frontend chashes and restarts continuously in an infiniteloop fashion. I'm sending this mail to debian-boot too too to see if anyone can reproduce this bug (missing NEWT frontend in the AMD64 miniiso and crashing graphical frontend) on a AMD64 machine. Maybe specifi problems on AMD64 are related to bug 316484 reported by cjw in cdebconf 0.81? i've looked at the code, if you think i could think about a patch to dpkg-reconfigure if this bug is lethal to the AMD64 graphical instaler. 

Attilio



andrew.laughton@westnet.com.au wrote:

Hi People

When I installed with the "install DEBIAN_FRONTEND=newt" option I got
the following result:
The system finished formating the hard drive, and did the flashing
screen again.
Most of the time the screen is black, with a cursor in the top left
hand corner.
When it flashes white, there is a black block cursor in the top left
hand corner and the screen sometimes shows up to 6 or 8 lines of what
appears to be a console heading.
It appears to be;
DirectFB v 0.9.22

but is very hard to tell because it flashes so fast.

Andrew.







---- Original Message ----
From: Davide.Viti@siemens.com
To: fiandro@tiscalinet.it, andrew.laughton@westnet.com.au
Subject: RE: Bug#339563: FW: amd64 etch beta 1 release
Date: Thu, 17 Nov 2005 14:31:28 +0100



Hi,



if you try to boot the same iso image with
install DEBIAN_FRONTEND=newt
does the crash still happens?
if it doesn't, could you switch to VT2 (ctrl+alt+F2) and type

export MALLOC_CHECK_=1
export DEBIAN_FRONTEND=gtk
debian-installer

and then report here the output?
this should allow us to understand if the crash is related to the
new
GTK frontend of the debian-installer or not, and in the case it is where the bug is originated. 

Unfortunately I could not switch to VT2 with the AMD64 mini.iso, not
even when
Progressbar is not running (see #339379)
Maybe starting with the newt fe it's possible to see what happens.
I cannot be very productive with helping doing tests since the port


was


done inside qemu which is
Far too slow for tests/development.
Help from people with real amd64 hw is very welcome

Regards,
Davide
Reply to: