Bug#413538: G-I freezes on directfb initialization
On Monday 05 March 2007 13:45, Frans Pop wrote:
> reassign 413538 cdebconf-gtk-udeb
> retitle 413538 G-I freezes on directfb initialization
> thanks
>
> On Monday 05 March 2007 18:46, murphymichael@netscape.net wrote:
> > Comments/Problems:
> > The only problem was with graphical installation. I wanted to give
> > it a go but admit to not trying very hard to make it work. When
> > initializing the graphical display, one can just make out a message
> > about attempting to initialize the frame buffer, then a greyish
> > screen appears with a large mouse pointer (that for a split second
> > can be moved) and then the screen/machine freezes.
>
> Hmmm. I've seen similar behavior while we were working on the
> graphical installer and in that case it was a problem/conflict with
> the initialization of the mouse. See http://bugs.debian.org/403329
> for reference.
> However, that issue was solved.
>
> Can you try booting the installer with 'installgui
> DEBIAN_FRONTEND=newt', switch to VT2 when the first dialog comes up
> [1] and then give us the output of the following commands:
> - cat /proc/bus/input/devices
> - ls -l /dev/input
> - dfbinfo
Here's the output:
cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003
I: Bus=0003 Vendor=099a Product=0536 Version=0001
N: Name="USB tenkeypad "
P: Phys=usb-0000:00:1d.7-3.2/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=120003
B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: LED=7
I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:07:00.2-2.2/input0
S: Sysfs=/class/input/input3
H: Handlers=mouse1 event3
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143
I: Bus=0011 Vendor=0002 Product=000a Version=0000
N: Name="TPPS/2 IBM TrackPoint"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/class/input/input4
H: Handlers=mouse2 event4
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
ls -l /dev/input:
crw-rw---- 1 root root 13, 64 Mar 8 10:57 event0
crw-rw---- 1 root root 13, 65 Mar 8 10:57 event1
crw-rw---- 1 root root 13, 66 Mar 8 10:57 event2
crw-rw---- 1 root root 13, 67 Mar 8 10:57 event3
crw-rw---- 1 root root 13, 68 Mar 8 10:57 event4
crw-rw---- 1 root root 13, 63 Mar 8 10:57 mice
crw-rw---- 1 root root 13, 32 Mar 8 10:57 mouse0
crw-rw---- 1 root root 13, 33 Mar 8 10:57 mouse1
crw-rw---- 1 root root 13, 34 Mar 8 10:57 mouse2
dfbinfo:
Screen (00) FBDev Primary Screen (primary screen)
Caps: VSYNC POWER_MANAGEMENT
Layer (00) FBDev Primary Layer (primary layer)
Type: GRAPHICS
Caps: SURFACE BRIGHTNESS CONTRAST SATURATION
Input (00) AT Translated Set 2 keyboard (primary keyboard)
Type: KEYBOARD
Caps: KEYS
Input (01) SynPS/2 Synaptics TouchPad (primary mouse)
Type: MOUSE
Caps: AXES BUTTONS
Max. Axis: 1
Max. Button: 2
Input (10) USB tenkeypad
Type: KEYBOARD
Caps: KEYS
Input (11) Logitech USB Receiver
Type: MOUSE
Caps: AXES BUTTONS
Max. Axis: 3
Max. Button: 15
Input (12) TPPS/2 IBM TrackPoint
Type: MOUSE
Caps: AXES BUTTONS
Max. Axis: 1
Max. Button: 2
Hope this helps.
>
> Reassigning to cdebconf-gtk until we can get a better handle on this
> issue.
>
> > That said, the text installer worked well and, I am very gratified
> > to say that this was the most error-free config-perfect linux
> > installation I've ever enjoyed. Great work to all involved!
>
> Thank you!
>
> Cheers,
> FJP
>
> [1] You can also run the first steps of the installation first until
> you have set up networking; that may make it easier to get the
> requested information off the system. scp is available if you load
> the optional component "openssh-client"; the menu option "save debug
> logs" may help as well.
Reply to: