Lines with string "unknown" in second and/or third column should be removed from /lib/discover/pci.lst
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Baltix |
New
|
Undecided
|
Unassigned | ||
discover-data (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: discover1-data
There are lost of problems when /lib/discover/
100271c4 unknown unknown M56GL [ATI Mobility FireGL V5200]
These lines couses discover1 parse error's, when discover1 is called during xserver-
There are several bugs already reported about such problems, when in /lib/discover/
Look at the lines from /lib/discover/
grep -n "10de0244" /lib/discover/
2731: 10de0244 unknown unknown C51 PCI Express Bridge
grep -n "53338d01" /lib/discover/
6949: 53338d01 video unknown 86C380 [ProSavageDDR K4M266]
grep "100271c4" /lib/discover/
100271c4 unknown unknown M56GL [ATI Mobility FireGL V5200]
Discover1 output when there are lines with strings "unknown" :
:~$ sudo discover --disable=
parse error reading X server string `unknown'
parse error reading X server string `unknown'
nVidia Corporation C51 PCI Express Bridge unknown unknown
Discover1 output when there are lines with strings "unknown" are removed:
:~$ sudo discover --disable=
nVidia Corporation NVIDIA Default Card XFree86 nv
Another solution for such problems is to patch discover1 tool to ignore X server string `unknown' and behave identifically, like when this string is removed (choose default driver for video card manufacturer).
So the problem is that claiming it is unknown results in discover not attempting to guess? This sounds like the right thing to do in this case, frankly. Choosing "vesa" is a lot better than it choosing wrong resulting in no X server starting...