Ubuntu
xserver-xorg-video-i128 package

startup crash - undefined symbol xf86usleep

Bug #306970 reported by Ed Straker on 2008-12-10

Affects		Status	Importance	Assigned to
	xorg xf86-video-i128	Fix Released	Undecided	Unassigned
	xserver-xorg-video-i128 (Fedora)	Won't Fix	Medium	redhat-bugs #447061
	xserver-xorg-video-i128 (Ubuntu)	Fix Released	Undecided	Unassigned
Nominated for Intrepid by Tormod Volden

Bug Description

Binary package hint: xorg

Gents,

I'm having major problems with xorg (1:7.4~5ubuntu3) in Ubuntu 8.10. Installed are two Number Nine Revolution IV LVD cards (plus 2 SGI 1600SW monitors), and with an adjusted xorg.conf this worked perfectly up to 8.04 (although both video cards and screens were not properly detected).
8.10 gives me neither a desktop nor a login prompt, and after fiddling around for some time I discovered that there seems to be a library problem:

alien@nostromo:/etc$ sudo Xorg -config /etc/X11/xorg.conf
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux nostromo 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
Build Date: 24 October 2008 08:00:16AM
xorg-server 2:1.5.2-2ubuntu3 (<email address hidden>)
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 10 22:14:30 2008
(++) Using config file: "/etc/X11/xorg.conf"
Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers//i128_drv.so: undefined symbol: xf86usleep

I'm not expert in this, for me it looks like a compilation problem. The log file does not show problems (see attachment).

Seems I have to go back to 8.04...

Thanks!
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82875P/E7210 Memory Controller Hub [8086:2578] (rev 02)

Subsystem: Super Micro Computer Inc Device [15d9:4580]

02:03.0 VGA compatible controller [0300]: Number 9 Computer Company Revolution 4 [105d:5348] (rev 02)

Subsystem: Number 9 Computer Company Device [105d:0017]

02:05.0 VGA compatible controller [0300]: Number 9 Computer Company Revolution 4 [105d:5348] (rev 02)

Subsystem: Number 9 Computer Company Device [105d:0017]

Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-

Subsystem: Intel Corporation Device [8086:1213]

Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-

SUMMARY:

The i128 driver needs a libpciaccess bugfix (see upstream bug) in order to start up without crashing. The fix is needed both for Intrepid and Jaunty.
The Intrepid package also needs the xf86usleep fix which was added upstream in 1.3.1.

These fixes should be safe for FFe and SRU, especially since the i128 never worked for anyone in Intrepid or Jaunty.

See original description

Tags:

Revision history for this message

In Red Hat Bugzilla #447061, Bernhard (bernhard-redhat-bugs) wrote on 2008-05-17:

#30

Description of problem:

/usr/bin/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers//i128_drv.so:
undefined symbol: xf86usleep
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.

Version-Release number of selected component (if applicable):
X.Org X Server 1.4.99.901 (1.5.0 RC 1)
Build ID: xorg-x11-server 1.4.99.901-29.20080415.fc9

How reproducible:

starting X11 with startx or xinit

Steps to Reproduce: see above
Actual results: error message on tty
Expected results: X11 server running

--
http://politics.wikia.com/index.php?title=Extending_human_legislation_to_artific
ial_intelligences
http://education.wikia.com/wiki/User:Fasten/Pilingual_Primer
http://en.wikibooks.org/wiki/Mentoring_Handbook
http://en.wikiversity.org/wiki/Topic:Assistant_teacher_program

Revision history for this message

In Red Hat Bugzilla #447061, Bernhard (bernhard-redhat-bugs) wrote on 2008-05-17:

#31

Created attachment 305806
Xorg.0.log

Revision history for this message

Ed Straker (ed-straker) wrote on 2008-12-10:

xorg.conf Edit (4.1 KiB, text/plain)

Revision history for this message

Ed Straker (ed-straker) wrote on 2008-12-10:

lspci-vvnn.txt Edit (13.3 KiB, text/plain)

Revision history for this message

Ed Straker (ed-straker) wrote on 2008-12-10:

Xorg.0.log Edit (7.0 KiB, text/plain)

Bryce Harrington (bryce) on 2009-01-09

Changed in xserver-xorg-video-i128:
status:	New → Confirmed

Bryce Harrington (bryce) on 2009-01-17

description:

updated

Revision history for this message

Greg (pcguy11) wrote on 2009-02-19:

I too have a problem with my Number Nine Revolution IV video card. I am using the BackTrack 4 beta and when I copy my working xorg.conf to the beta and do a startx I get a black screen. Ctrl-Alt-BackSpace doesn't work so I can only reboot using Ctrl-Alt-Delete to get back to a prompt.

I have to same xorg.conf but with only 1 screen.

Revision history for this message

Greg (pcguy11) wrote on 2009-02-21:

OK I switched back to tty1 and saw:
(++) Using config file: "/root/xorg.conf.new"
Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers//i128_drv.so: undefined symbol: xf86usleep

Basically what happened is I did X -config /root/xorg.conf.new and it stops at a black screen which I didn't realize was really tty7. I do a Ctrl-Alt-1 and see the above message.

Revision history for this message

Greg (pcguy11) wrote on 2009-02-27:

Can someone please recompile the driver and let us see if that fixes the problem?

Revision history for this message

Greg (pcguy11) wrote on 2009-03-04:

I tried to compile the driver myself and am getting an error. This is what I am doing:
apt-get source xserver-xorg-video-i128
apt-get build-dep xserver-xorg-video-i128
cd xserver...
./configure
make
No rule to make target 'i128' needed by 'all-am'

What did I do wrong?

Revision history for this message

In Red Hat Bugzilla #447061, greg (greg-redhat-bugs-1) wrote on 2009-03-05:

#32

Ubuntu has the same problem with intrepid:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-i128/+bug/306970

Revision history for this message

Greg (pcguy11) wrote on 2009-03-05:

This might be the fix:
http://lists.debian.org/debian-x/2008/09/msg00117.html
I applied the include <uninstd.h> and changed all the xf86usleep to usleep
However I still cannot get past the
No rule to make target 'i128' needed by 'all-am'

Revision history for this message

Greg (pcguy11) wrote on 2009-03-06:

AddScreen/ScreenInit failed for driver 0 Edit (21.2 KiB, text/plain)

The fix for the No rule to target i128 is too copy /usr/share/xserver-xorg/pci/i128.ids to the src directory. Apparently i128.ids is missing from the source code. I managed to compile the i128 with the above patch and I now I am getting:
Fatal server error:
AddScreen/ScreenInit failed for driver 0

Revision history for this message

Greg (pcguy11) wrote on 2009-03-06:

#10

I just download the jaunty source code (1:1.3.1-2) and still get the above error

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-06:

#11

If you have downloaded the source (as a Debian source package) you should build it with "debuild -b -us -uc" and not run configure or make manually.

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-06:

#12

I have added a backport of latest git (for intrepid) to my PPA, https://launchpad.net/~tormodvolden/+archive/ppa

Revision history for this message

Greg (pcguy11) wrote on 2009-03-07:

#13

log from using driver 1.3.1+git Edit (22.2 KiB, text/plain)

Thanks for the tip about building from source. I downloaded the file you created (thanks by the way) and did this:
apt-get remove xserver-xorg-video-i128
dpkg -i xserver-xorg-video-i128_1.3.1+git20090306.8bd4dc99-0ubuntu0tormod~intrepid_i386.deb

and still get the same error. I am attaching the Xorg.0.log file from the test. Let me know what you need. Thanks.

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-08:

#14

Do you see the same error when using Jaunty? In which case we should put more effort into it.

Revision history for this message

Greg (pcguy11) wrote on 2009-03-08:

#15

I have intrepid installed as I need that version for work. If you have jaunty on a live CD or usb drive I can download I will try it.

Revision history for this message

Greg (pcguy11) wrote on 2009-03-08:

#16

I found http://cdimage.ubuntu.com/releases/jaunty/alpha-5/ after a quick google. I am downloading the PC (Intel x86) desktop CD now. I will get back to you.

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-08:

#17

I am afraid all non-xrandr 1.2 drivers (including i128) were broken in Jaunty in alpha-5. Please try the latest daily build: http://cdimage.ubuntu.com/daily-live/current/ You do not have to download it all over again, you can upgrade your alpha-5 iso using rsync: https://help.ubuntu.com/community/RsyncCdImage

Revision history for this message

Greg (pcguy11) wrote on 2009-03-09:

#18

Ok I finished downloading alpha-5 and then I did the rsync. I burned the iso to cd-rw, booted from the cd, selected English, removed splash and quiet from the command line and pressed enter. About 2 or 3 seconds into the boot the screen went from text to graphical text. Once the system fully started, X tried to start and I saw Ubuntu is running in low graphics mode
your screen, graphics card, and input device settings
could not be detected correctly. You will need
to configure these yourself.
I click on reconfigure graphics
and then click on create new configuration for this hardware
and X goes black and the led switches to a flashing yellow light instead of steady green.
My guess is Ubuntu is using the vesa driver and not the i128 driver during boot and X won't/can't switch to the i128 driver, but I don't know.
Is there a way I can boot to a text console instead of a graphical console? Then I can copy my xorg.conf to /etc/X11 and run startx.

I have the 4 Xorg logs from booting from the CD if you want them. A quick look at Xorg.0.log and Xorg.99.log both show
Fatal server error:
AddScreen/ScreenInit failed for driver 0

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-09:

#19

> Is there a way I can boot to a text console instead of a graphical console?

Yes, you can boot with the "text" option. At the command prompt you can then run "startx". Please attach the log from running with the default xorg.conf.

description:

updated

Revision history for this message

Greg (pcguy11) wrote on 2009-03-09:

#20

jaunty daily build live cd booted with text option and default xorg.conf Edit (20.9 KiB, text/plain)

The one option I didn't try.....

Here is the log you requested. Also I noticed that when I booted with the text option I still get the graphical text instead of just text.

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-09:

#21

I found an upstream bug report with a patch that can be related. I uploaded a new intrepid package with this patch to my PPA, please test it: 1:1.3.1+git20090306.8bd4dc99-0ubuntu0tormod~intrepid2

Revision history for this message

Greg (pcguy11) wrote on 2009-03-10:

#22

I can finally run startx and X works great. However if I logout of X and run startx again the keyboard/PC freezes at a black screen. I don't know if the PC is frozen or if it is just the keyboard.
Thank you for your efforts to fix this problem.

Revision history for this message

Greg (pcguy11) wrote on 2009-03-10:

#23

The computer is frozen. I can usually turn off the PC by pressing the power button but when I run startx the second time the power button doesn't do anything.

Revision history for this message

In Red Hat Bugzilla #447061, greg (greg-redhat-bugs-1) wrote on 2009-03-10:

#33

Some good news is there is a fix at:
http://bugs.freedesktop.org/show_bug.cgi?id=20541
but running startx a second time (startx, logout, startx) causes the PC to freeze.

Bug Watch Updater (bug-watch-updater) on 2009-03-10

Changed in xf86-video-i128:
status:	Unknown → Confirmed

Tormod Volden (tormodvolden) on 2009-03-10

description:

updated

Revision history for this message

Greg (pcguy11) wrote on 2009-03-10:

#24

Fedora also has this problem.
https://bugzilla.redhat.com/show_bug.cgi?id=447061

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-10:

#25

Since we are facing different issues here (unrelated, although they both cause a start-up crash) I have opened a new bug 340750 for the AddScreen/ScreenInit failure.

I will keep this bug for tracking the xf86usleep issue, which is already fixed in Jaunty but needs a Stable Release Update for Intrepid.

Changed in xserver-xorg-video-i128:
status:	Confirmed → Fix Released

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-10:

#26

upstream patch Edit (1.4 KiB, text/plain)

To fix this issue in Intrepid, this upstream commit needs to added: http://cgit.freedesktop.org/xorg/driver/xf86-video-i128/commit/?id=3b1d9fe8694df9b63ad12c7fe5cd059f4132a8ce

In order to have a working driver, bug #340750 also needs to be fixed, so updating to an upstream version which fixes all these issues (not yet available) would be an alternative.

The Intrepid driver never worked for anyone because of these two issues.

Changed in xf86-video-i128:
importance:	Unknown → Undecided
status:	Confirmed → New
status:	New → Fix Released

Revision history for this message

Greg (pcguy11) wrote on 2009-03-10:

#27

Should I open a third bug to fix the X crashes when doing a startx, logout, startx problem?

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2009-03-10:

#28

Yes, please. It could be related to bug 340750 but until we know more let's track it separately.

Bug Watch Updater (bug-watch-updater) on 2009-03-11

Changed in xserver-xorg-video-i128:
status:	Unknown → In Progress

Revision history for this message

Greg (pcguy11) wrote on 2009-03-11:

#29

I opened https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-i128/+bug/341189

Thanks for all of your help.

Revision history for this message

In Red Hat Bugzilla #447061, Bug (bug-redhat-bugs) wrote on 2009-06-10:

#34

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message

In Red Hat Bugzilla #447061, Bug (bug-redhat-bugs) wrote on 2009-07-14:

#35

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Bug Watch Updater (bug-watch-updater) on 2009-07-14