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

Bug#400898: More informations needed to fix this bug



martin schneebacher wrote:
hi!

sorry for the late answer, i was really busy this week.


----- Original Message -----
From: "Attilio Fiandrotti" <attilio.fiandrotti@gmail.com>
To: 400898@bugs.debian.org, masc@operamail.com, banerian@u.washington.edu, Fabrice.Lorrain@univ-mlv.fr
Subject: More informations needed to fix this bug
Date: Sun, 03 Dec 2006 12:37:24 +0100


Dear all

We suspect the crash you reported are due to vesafb and vga16fb framebuffer devices started somehow in wrong order.
To check that, i ask you to boot a graphical installer miniiso [1] with

install DEBIAN_FRONTEND=newt

This will boot the installer with the classical textual frontend.

Now, switch to VT2 and write down on a piece of paper the output of

ls -la /dev/fb*


/dev/fb
drwxrwxrwx                                              .
drwxrwxrwx                                              ..
crw-rw----      1   root root    29,  0   Dec 9 14:26   0


cat /proc/fb


0 VGA16 VGA


It would be also useful having the syslog: you can switch back to the installer and select "Save debug logs" and select one of the options available (note that to save the installation logs via web you need to first configure network so that the installation machine can be reached from the outside :)


i wasn't able to use the usbstick nor the ethernet (just have wlan), but i wrote the fb-specific lines by hand:

[... (between cpu stuff)]
Console: colour VGA+ 80x25
[...]
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device [...]

bye...martin.

It looks like vesafb was unable to start on your Geforce, hence no /dev/fb0 was provided: we aready experience that for Inlel 82810 and S3ViRGE DX. Another user reported fb0 (vesa) and fb1 (vga 16 colours) being swapped on a grforce go 6200, but he was later unable to reroduce the swap. I prepared a patch that disables the graphical frontend in the case vesafb cannot be started at boot time and this iso [1] includes the patch. The patch should detect lack of vesafb fb device and falback to the classical textual installer, could you please test and report whether it works or not?

thanks

Attilio

[1] https://debian.polito.it/downloads/mini_vesa_check.iso



Reply to: