Obviously this is a temporary workaround, for personal testing only.
I added these two lines to the 030-early-packages script.
cp /root/acpid.deb $ROOT
chroot $ROOT dpkg -i /acpid.deb
This is what my
"/usr/share/ltsp/plugins/ltsp-build-client/Ubuntu/030-early-packages" file
lo
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/11074551/Xorg.0.log
--
X Server fails to start. -- i815
https://bugs.launchpad.net/bugs/178837
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
Public bug reported:
Binary package hint: xserver-xorg-driver-i810
Hardy: Alpha 2
I installed from netboot using hardy repositories.
Upon first boot, the console flashes three or four times and the XKeepsCrashing
script pops up.
I can send full Xorg.0.log if needed.
Below are snippets from X
Okay, I seem to have resolved this problem on my own.
I edited my /etc/X11/xorg.conf and inserted
DefaultFbBpp 24
within: Section "Screen"
I know this is a trivial fix for me, but a lambda user would be stuck. I was
honestly expecting the
BulletProof X system or something to show
** Changed in: xserver-xorg-video-intel (Ubuntu)
Sourcepackagename: xserver-xorg-driver-i810 => xserver-xorg-video-intel
** Summary changed:
- X Server fails to start. -- i815
+ X Server fails to start. -- Intel i815
** Description changed:
- Binary package hint: xserver-xorg-driver-i810
+ Bina
I tested the new driver out too and everything works fine now without the
DefaultFbBpp statement.
However I now have strange artifacts, especially around the mouse pointer.
Reverting to the old intel driver and reinserting DefaultFbBpp makes the
artifacts go away (and seems to reduce CPU usage
More testing has revealed that using the *new* driver with DefaultFbBpp 24 does
not have the artifacts.
Manually setting DefaultFbBpp to 16 does have artifacts
Is this a problem with DRI? (As stated above, 24bit does not have DRI, but
16bit does.)
New bug report?
--
X Server fails to start. --
Public bug reported:
ltsp-build-client fails when installing ltsp-client package in the
chroot because ltsp-client depends on acpid, which does not seem to be
available on the powerpc arch.
** Affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
--
powerpc: ltsp-build-client f
I can confirm this bug as well.
I created a dummy acpid package and hacked it into the install scripts
to copy it to the chroot and install it before ltsp-client.
** Attachment added: "Dummy acpid created with equivs"
http://launchpadlibrarian.net/13156286/acpid_1.0.4-5ubuntu6_all.deb
--
lt
