From: Andrew W. <qw...@gm...> - 2005-06-09 02:10:06
|
On Thu, 02 Jun 2005 6:48 pm, Svetoslav Slavtchev wrote: > > If you are using the kernel-source package, this may be due to a > > Debian-specific patch to the kernel source code. Rename the > > file /usr/src/linux/Debian.src.changelog (I think that's it) and try > > compiling again. > > > > Ken > > yes, that could be the reason > i think debian had included some VT changes > > please try recompiling using vanilla(unpatched) linux-2.6.8 > and if it works, try downloading kernel-patch-debian (IIRC) > to check which patch from the debian modifications exactly brakes > the build OK, I have tried compiling a nearly vanilla kernel 2.6.8 (I used kernel-patch-debian to roll back to vanilla 2.6.8, then manually applied a few patches from debian 2.6.8-1) with the ruby patches. After disabling mdacon it built and booted, but I am having a few problems. The primary display is using the onboard Via/S3 UniChrome graphics adapter, a ps/2 keyboard and a USB mouse. The second display uses a 4MB SiS PCI graphics adapter, a ps/2 keyboard and a serial mouse. If I change to virtual consoles 1-6 on the primary screen, the first VC is displayed no matter which I switch to, and nothing I type shows up. If I press enter, the picture on the second screen is shifted to the left by about 1/3 the screen width and some white lines show up at the bottom of the second screen. If I stop kdm (and hence the X servers), the primary screen shows light blue and red lines, while the second screen flickers with random lines. There appears to be no way out of this state. Also, the NumLock and CapsLock LEDs don't work on the primary keyboard. There appear to be problems with 3D acceleration causing freezes, which I need to investigate further. What is causing these problems, and how can I fix them? Andrew Walbran |