On Wed, 16 Feb 2000, Giorgos Keramidas wrote:
> On Tue, Feb 15, 2000 at 04:10:59PM -0800, Doug Barton wrote:
> > On Tue, 15 Feb 2000, Kazutaka YOKOTA wrote:
> >
> > > `options XSERVER' is for vt0 only. sc0 doesn't need it to run the X
> > > server.
> >
> > Could you add appropriate comment
On Tue, Feb 15, 2000 at 04:10:59PM -0800, Doug Barton wrote:
> On Tue, 15 Feb 2000, Kazutaka YOKOTA wrote:
>
> > `options XSERVER' is for vt0 only. sc0 doesn't need it to run the X
> > server.
>
> Could you add appropriate comments to this effect in GENERIC and
> LINT? I have always been
On Tue, Feb 15, 2000 at 12:22:27AM -0800, David O'Brien wrote:
> No, you were right. compat3x is supose to allow 3.4 binaries to run on
> 4.0. I just missed libhistory.so.3 as being needed in the compat3x set.
Fixed -- libhistory.so.3 is now part of compat3x.
--
-- David([EMAIL PROTECTED
On Tue, 15 Feb 2000, Kazutaka YOKOTA wrote:
> `options XSERVER' is for vt0 only. sc0 doesn't need it to run the X
> server.
Could you add appropriate comments to this effect in GENERIC and
LINT? I have always been confused by this, and IMO the placement in the
file is not sufficient to
On Tue, Feb 15, 2000 at 06:44:37AM +0900, Kazutaka YOKOTA wrote:
Very detailed and presize description of
my misunderstanding of the 'moused_type' settings for ps/2
mouse.
After applaying this recomendations I now can
'tap' on my pad without (annoying) warning message after
every
"Roden, Thomas" wrote:
>
> > Problem 2
> After installing bash-2.03 from the 3.4 packages, attempting to run bash
> yields:
> /usr/libexec/ld-elf.so.1: Shared object "libhistory.so.3" not found
>
> 'ln -s libhistory.so.4 libhistory.so.3' fixes? the problem
> I assumed (perhaps incorrectl
>1. The kernel compiled from GENERIC doesn't find my PS2 mouse.=20
>2. 'options XSERVER' renders the kernel incapable of booting. The
>config file is included below.
>3. Adding 'device pcm0' also makes the kernel unable to boot. The
>bootloader loads, tries to load the kernel and freezes up.=20
On Mon, 14 Feb 2000, Hasan Diwan wrote:
> 1. The kernel compiled from GENERIC doesn't find my PS2 mouse.
You'll have to post a dmesg for further diagnosis.
> 2. 'options XSERVER' renders the kernel incapable of booting. The
> config file is included below.
This option is only useful if you ha
>>>rc.i386 configuring syscons: blank_time mousedmoused: mouse type mismatch
>>>(ps/2 != intellimouse), ps/2 is assumed
>>
>> If you read the notice in the mouse configuration screen, you should
>> have understood that you should ALWAYS choose the type "Auto" for ANY
>> mouse connected to the PS
1. The kernel compiled from GENERIC doesn't find my PS2 mouse.
2. 'options XSERVER' renders the kernel incapable of booting. The
config file is included below.
3. Adding 'device pcm0' also makes the kernel unable to boot. The
bootloader loads, tries to load the kernel and freezes up.
machine
In <[EMAIL PROTECTED]> Kazutaka YOKOTA
<[EMAIL PROTECTED]> wrote:
>>> Possible Problem 3
>>During setup, I configure my Intellimouse as an "Intellimouse" on port
>>"ps/2". The mouse cursor works as it should but during boot I get the
>>following diagnostic:
>>
>>rc.i386 configuring syscons:
"Roden, Thomas" wrote:
>
> > Problem 2
> After installing bash-2.03 from the 3.4 packages, attempting to run bash
> yields:
>
> /usr/libexec/ld-elf.so.1: Shared object "libhistory.so.3" not found
>
> 'ln -s libhistory.so.4 libhistory.so.3' fixes? the problem
>
> I assumed (perhaps inco
>> Possible Problem 3
>During setup, I configure my Intellimouse as an "Intellimouse" on port
>"ps/2". The mouse cursor works as it should but during boot I get the
>following diagnostic:
>
>rc.i386 configuring syscons: blank_time mousedmoused: mouse type mismatch
>(ps/2 != intellimouse), ps
Greetings,
During testing of 4.0 RC1 I have found the following:
> Problem 1
During installation I get a message that the setup of X has failed. Later
attempts at running XF86Setup from the command line gives the following
response:
/usr/libexec/ld-elf.so.1: Shared object "libXThrStub.so.6
14 matches
Mail list logo
