Re: X Mouse and Drive errors
sto0 <stuart@tvrr.demon.co.uk> writes:
> *··· hi,*
>
> > I think the amiga mouse driver is built into the kernel. Make sure that
> > /dev/mouse points to /dev/amigamouse and that X is configured to use it
> > (.X86Config??)
>
> Actually, after writing the mail, i spent some more time working out
> how to do it and managed what you have said here, but thanks anyhow!
> Well, i had a look around my dir`s, and i altered the mouse file to
> point to amigamouse (which is definitely the driver i was looking
> for), and made sure that XF86Config was looking at the correct
> place. Now, my next problem is two-fold: a) my hard disk comes up
> with "hdb1: read_intr {DriveReady... (or something)}" or "hdb1:
> unexpected_intr {etc.... whatever}" most of the time when it
> accesses the HD. I have reformatted my HD under AmigaOS and used
> DiskSalv, HDToolBox etc... and physically the drive is fine. What is
> this, as i don`t think that it`s good? Are there any HD checking
> tools like DiskSalv that check at low-level? I have run fsck, but
> this hasn`t done much... b) i have X windows installed, some fonts,
> fvwm95 etc... but when i run "startx" it loads up X windows, prints
> out the read errors as mentioned in a), and begins to construct the
> GUI of fvwm. This is all okay, but firstly the mouse doesn`t work
> even though i`ve make the link perfectly, and secondly, it seems to
> freeze up after the GUI screen has come up.
>
> Help! I`m totally out of my depth with this one!
Try to switch back to a console (ctrl-alt-Fx), logon there and type
"xterm -display :0". Switch back to X (alt-F7) and see if theres a new
Xterm on the screen (or a faint outline of it querying you where to
stick it). If that works, its just the mouse thats not
working.
May the Source be with you.
Mrvn
Reply to: