Re: 2.2.17pre10-ben1 & dmasound & atfb driver

Re: 2.2.17pre10-ben1 & dmasound & atfb driver

[Nelson Abramson]

Iain Sandoe wrote:

> <snip>
> Also, someone posted some instructions on how to set up the new input layer
> but I can't seem to find them in my linuxppc archive  - I'm assuming that
> the new stack has been back-ported to 2.2.17pre10 which is why my adbmouse
> doesn't...

I can't find the message in my archive, but here's the skinny (mainly quoted
from BenH--I wrote it down :-) ):

Delete both /dev/usbmouse and /dev/mouse (I moved them to temp_* just in
case).
cd /dev
mkdir input
mknod input/mice c 13 63
ln -s input/mice mouse
ln -s input/mice usbmouse

and add:
 none   /proc/bus/usb     usbdevfs    defaults 0 0
to your /etc/fstab


HTH
--Nelson Abramson


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

2.2.17pre10-ben1 & dmasound & atfb driver

[Iain Sandoe]

Hi,

well the good news.. is that the dmasound patch (referred to earlier)
applies cleanly and runs ok on 2.2.17pre10-ben1.

The bad news is that the fb doesn't work on my G3/beige (mach64) - starts
and then the screen 'slips sideways' by half and the whole thing stops dead
(no regs dump output).  I haven't got a serial term at present so no xmon
:-(

reverting to offb got it all up - although I need to reconfigure the mouse
stuff as well.

any ideas what I might be doing wrong?

Also, someone posted some instructions on how to set up the new input layer
but I can't seem to find them in my linuxppc archive  - I'm assuming that
the new stack has been back-ported to 2.2.17pre10 which is why my adbmouse
doesn't...

G3/beige
2.2.17pre10-ben1 ati support complied in.
BootX 1.2.2

TIA,
Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.2.17pre10-ben1 & dmasound & atfb driver

[Claus Enneper]

 >:
 >: I can't find the message in my archive, but here's the skinny (mainly quoted
 >: from BenH--I wrote it down :-) ):

<http://home.munich.netsurf.de/Franz.Sirl/inputppc.html>

--
Yours, ce

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

pmac-time.c bug in 2.4.0-test3

[Martin Costabel]

Symptom: Booting a recent 2.4.0-test3 kernel from bitkeeper gives me a
wrong system time. The corresponding boot message is, for example
Jul  7 06:54:51 chezmoi kernel: GMT Delta read from XPRAM: 0 minutes,
DST: off
This is 2 hours off.

Booting with  2.2.17pre10 gives me the correct message
Jul  8 12:10:05 chezmoi kernel: GMT Delta read from XPRAM: 120 minutes,
DST: on

Looking through my log files, I find that this has been the same
situation since the changes in pmac-time.c were introduced:

In Paul's pmac-stable 2.2.16 and then in 2.2.17-pre5 from bk (patch of
21 June, according to bk sccstool), this XPRAM stuff showed up and
worked correctly.

In the bk linuxppc_2_3 tree, this showed up in 2.4.0-test3 on 27/28 June
(according to my logs), and it did not work correctly. In addition to
the wrong reading of the initial system time, I get the following
message every 61 (!) seconds
Jun 29 01:27:31 chezmoi kernel: pmac_set_rtc_time: got 3 byte reply
Jun 29 01:28:32 chezmoi kernel: pmac_set_rtc_time: got 3 byte reply
Jun 29 01:29:33 chezmoi kernel: pmac_set_rtc_time: got 3 byte reply
and so on.

I tried to set CONFIG_PPC_RTC to y or n, but this didn't seem to have an
influence. Other ideas for debugging?

My system is still the old Pmac 6400.

--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/