Re: freezeups with Logitech wireless mouse

2003-01-30 Thread Paul Winkler

I have used both "woody" (xfree 4.1) and now "testing"  (Xfree 4.2) with 
the wireless logitech keyboard and mouse.  I have had no problems which 
were not resolved by pushing the reset switch on the keyboard, mouse, 
and control unit.  Each of these buttons looks different and fooled me 
for sometime - make certain you are indeed pushing all the correct 
buttons if you have trouble.

Below is how my Xf86Config-4 file (/etc/X11) is setup, the mouse wheel 
works fine.

---
Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/psaux"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

--

Paul Winkler




On Thursday 30 January 2003 11:24 am, Bob Paige wrote:
> I purchased the Logitech wireless mouse/keyboard combo (I really like
> it) but have always had some amount of trouble with them.
>
> Under Mandrake, I could never start X with the wireless mouse
> connected. If I did, the mouse would be very jerky. Instead, I had to
> connect a wired mouse, start X, then connect the wireless mouse.
>
> Under Debian (and XFree86 4.2), if I start X with the wireless mouse
> connected, the computer freezes. I literally have to power-cycle it.
> If I start X with a wired mouse then switch, it works fine.
>
> Clearly, the mouse is the problem.
>
> Any thoughts as to how I can fix this annoyance? Granted, I don't
> reboot the machine often (this is Linux!) but if I forget to swap out
> the mouse, rebooting becomes very time-consuming.
>
> Related issue: the logitech mouse has a scroll wheel and an
> additional button for the thumb that I've never been able to get to
> work under Linux.
>
> Thanks in advance!
>
> - Bobman


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Screen resolution in KDE or Gnome

2003-01-07 Thread Paul Winkler
This is more a KDE or gnome question then a Debian question however...

In KDE 3.1 you would click on Control Center->peripherals->X Display

This will allow you to change resolution, color depth, and virtual 
desktop size.  It edits the XF86 Config-4 file for you automatically.  

For the changes to take place you must restart X windows, usually 
accomplished with a ctrl-alt-backspace, followed by a startx.  A reboot 
of the OS is not needed.

For further questions on KDE see www.kde.org, there you can subscribe to 
mailing lists specific to you questions.

Paul Winkler



On Tuesday 07 January 2003 08:26 am, Joe Bosak wrote:
> Is there an easy way to switch between screen resolutions when using
> a GUI like KDE or Gnome?
>
> I'm using Debian 3, stable release.
>
>
> - Joe


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Advansys ABP3922 -> "LSR safety check engaged"

2003-01-12 Thread Paul Winkler

I am running Debian testing, 2.4.17 kernel, with 2 ide cdroms  (scsi 
emulation enabled), and a single ide hard drive.  Everything works 
fine.

Next,  I plug in an Advansys ABP3922 (pci) scsi controller in order to 
use an external slide scanner.  Support for scsi, plug and play, and 
the advansys driver has been compiled into the kernel.  When the system 
boots the 3922 is correctly identified, however I now get and error 
message "LSR safety check engaged" for the ttyS4 serial port, which on 
my system is a 56K 3com PNP modem.

The error message from what I've read is from the serial device driver 
indicating something has been read from the UART which is not possible.  
The modem is no longer availabe for use.  It does not seem to be an 
interrupt or io address conflict.

If I plug a different drive into the above hardware with win2000 
installed everything works, so the hardware all looks good.

Any suggestions will be appreciated - thank in advance.

Paul Winkler



  


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: X11

2003-01-17 Thread Paul Winkler

I had a similiar problem with an ATI AIW 8500dv.  I ended up upgrading 
to xfree86 4.2 from 4.1, (which necessitated an upgrade from "Woody" to 
"Testing") this fixed the problem, I specified the radeon driver.

Here is a link to the ATI website where they provide instructions on how 
to install a binary module in the kernel to support the 9000. 

   http://mirror.ati.com/support/drivers/linux/radeon-linux.html

This however involves an rpm package - the process looked to fraught 
with danger to me so I chose to upgrade to Xfree86 4.2 instead.  
Xfree86 4.3 will contain better support for accelerated 3D, but if all 
you need is 2d Xfree86 4.2 will work fine.

Paul Winkler


On Friday 17 January 2003 07:20 am, Vanilla wrote:
> I still can't start X with and Ati 9000 (on a desktop).
> I'd try: ati, atimisc, radeon, vesa and vga.
> If I use the vga driver, I can start X, but ...
> I dont need 3D, only 2D 24 color bits.
>
> Tanks in advance


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: X11

2003-01-17 Thread Paul Winkler


Nick -

  Thanks for your posting, if I can summon the courage I will give 
it a try.  

Paul Winkler


> I thought so also, until I read ATI's HOWTO. The RPM converted easily
> with alien, then I performd a dpkg -i --force-ovrwrite, ran 2 scripts
> and then their Xfree setup utility. I had my 8500 running in less
> than 20 min, and that was with compiling a custom module for my
> 2.4.20 kernel. They are currently supporting X 4.1 and 4.2. I'm using
> the Radeon 8500 on testing with Xfree 4.2


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Slow floppy boot

1999-04-19 Thread Paul Winkler

I boot linux (presently Debian 2.1) from a floppy disk.  Before Debian 2.0, I
had no problems, since then however the boot process takes between 6 and 7
minutes to complete!  It used to take only a few seconds.

I notice when the floppy is being prepared by the installation program a
calibration of some sort is performed and number is generated which is supposed
to be included in /etc/driveprm.  I have tried this with no success.

Any suggestions would be greatly appreciated.  Thanks in advanced.


Re: kde

1999-04-20 Thread Paul Winkler

I recently installed Kde 1.1 on Debian 2.1.  I did it this way;

1.  Install the qt library version 1.42 -2 from the debian site

2.  Download from ftp://ftp.kde.org/pub/kde/Incoming/debian ,
(or a mirror) , the following fpackages and install them using dpkg
(dpkg -i package.deb) in this order:

kdelib2g
kdebase1.1
kdebase-il8n
kdeanim
kdesupport
kdegames
kdegraphics
kdenetwork
kdetoys
kdeutils
kdewallpapers

This desktop is very nice!




Re: kde

1999-04-20 Thread Paul Winkler
On Tue, 20 Apr 1999, ktb wrote:
>
> I haven't been paying much attention to kde/gnome strings as I'm happy
> with xdm and fvwm2 but I'm starting to get curious.  It wouldn't be
> worth it to me to loose the gui setup I have now.  Is it possible to
> have xdm/fvwm2 and kde coexist?  It would be nice to leave my "F7"
> terminal the way it is and have kde on "F8."  I'd like to know if this
> is possible before trying to install kde.  I'm using Slink.  
> thanks,
> kent
> 
> 
> -- 

My install of Kde 1.1 did not bother my existing xdm/fvwm2 setup.

The installation places the line - /usr/X11R6/bin/kde in the file
/etc/X11/windowmanagers.  If you do not wish to boot Kde, place a # sign
at the beginning of the line (i.e. comment it out).  The first line in this file
determines which window mamager boots.



 > Unsubscribe?  mail -s unsubscribe
[EMAIL PROTECTED] < /dev/null


Re: floppy too slow during bootup (fwd)

1999-04-20 Thread Paul Winkler
On Tue, 20 Apr 1999, Fethi A. Okyar wrote:
> I am wondering why in the world does my floppy get
> sooo slow while its reading the kernle image during
> a boot process??
> 
> It takes approximately 5-6 minutes until it finishes
> just reading the kernel image and then bang!! 2 seconds
> to decompress it.
> 
> Are there any parameters that I have to tweak when I
> get the boot: mesage, so that I can speed the process?

I posted the same question recently and received some kind responses however
so far I'm still in slow motion.  

The behavior of the floppy suggests to me the low level formatting of the floppy
is not optimal, i.e. perhaps the interleaving in incorrect causing the floppy to
rotate once for each sector read.  

Or it maybe something entirely different.

I believe this problem first appeared in Debian 2.0. 


Re: floppy too slow during bootup (fwd)

1999-04-20 Thread Paul Winkler
On Tue, 20 Apr 1999, Fethi A. Okyar wrote:
> Did you have the same problem when you built
> a custom floppy for your system, or does this
> problem only occur when you used the original
> boot disk that was included in the distribution?
> 
The boot disk I use was produced by the installation program on the
rescue1440.bin floppy. Since Debian 2.0 I have not recompiled the kernel and
produced a custom boot disk.


Re: floppy too slow during bootup

1999-04-20 Thread Paul Winkler
On Tue, 20 Apr 1999, James Dietrich wrote:
> On Tue, Apr 20, 1999 at 10:37:18AM -0500, Fethi A. Okyar wrote:
> > 
> > I am wondering why in the world does my floppy get
> > sooo slow while its reading the kernle image during
> > a boot process??
> > 
> > It takes approximately 5-6 minutes until it finishes
> > just reading the kernel image and then bang!! 2 seconds
> > to decompress it.
> 
> I have had the same problem myself--here are a few more details
> that may be helpful in figuring this out.
> 
> I installed Debian 2.1 and the Custom Boot Floppy it made during
> the initial install takes _forever_ to boot.  However, I later
> made my own boot disk using the Bootdisk HOWTO and it booted up
> at a normal speed.  It appears to me, then, that it isn't the
> fault of the drive itself or the floppy disk, but rather something
> about the way the boot disk is created during the install process.
> Interestingly enough, the rescue disk also boots at a normal speed
> on the same computer.  BTW, this was not a problem for me when I
> installed an earlier version of Debian several years ago.
> 
> Does anyone with more knowledge about boot disks have any
> idea why there is such a large discrepancy between the booting
> time off the rescue floppy and the custom boot floppy created
> during install?
> 
> Thanks.
> James


Moments ago I just recompiled my kernel and produced a custom boot disk-
oh joy, now my floppy boots at normal speed!

Earlier George Bonser indicated that a boot floppy made with the tecra-safe.bin
images exhibited "this feature" of a slow boot, however I had not used that
image so I did not think this was the problem.

The Debian 2.0 and 2.1 install procedure produces a slow floppy boot which was
not the case pre 2.0.


Re:Booting from floppy slow

1999-11-06 Thread Paul Winkler
When I first installed slink - I had the same problem.  For some reason
the floppy boot is very slow when you use the supplied boot disk from
slink.

To cure this simply compile the kernel, make a bzImage and copy it to a
floppy.

This solves the problem, the floppy boot will be quite fast.

Others have had this same problem, you are not alone.

Paul Winkler


Re: Trouble getting my screen resolution correct.

2002-04-06 Thread Paul Winkler
Does your X86Config-4 file contain a modeline for 1280x1024?

The xserver contains some internal modelines for "normal resolutions" but 
requires you add a modeline for others.  I had the same problem trying to get 
1152x864.  You might try xvidtune to generate a modeline, I am sure there are 
other tools available, or if you have a copy of an XF86config file for XFree86 
version 3 which had worked for your video card and monitor you can copy this 
to your XF86Config-4 file, below is where I placed my modeline in my 
XF86Config-4 file.

Section "Device"
Identifier  "Matrox Mystique 220"
Driver  "mga"
EndSection

Section "Monitor"
Identifier  "Sony MultiScan 17sf II"
HorizSync   31-65
VertRefresh 50-120
Option  "DPMS"

Modeline  "1152x864"   921152 1208 1368 1474   864  865  875  895

EndSection

Paul Winkler




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]