In the last mail Russell King - ARM Linux Admin said:
> Ok, fix already exists - there is a new X server binary in the FTP site
> in /pub/armlinux/testing/X I think. I know of one problem with it - since
> the kernel now passes the keyboard-generated autorepeat to the X server,
> the X server cockes up doing it's own autorepeat.
mknod /dev/fb0 c 29 0
and it works fine on 2.2.2 (albeit in 640x480x16 colours)
What happens when I plug a TV into my RiscPC instead of a monitor?
(I have the lead to do this). I note the code that returns monitor type
currently always returns 4 (SVGA), but it it returned 1, what would the rest of
the boot sequence do?
> > I can't run screen - I get many many lines of "modprobe: Out of file handles"
> > and then a final message about no more ptys.
>
> Aha! You probably haven't got the correct major/minor numbers for
> /dev/?ty[p-s]*. Have a look at linux/Documentation/devices.txt for
> the correct numbers. These will be backwards compatible with the
> 2.0.3x kernels.
Fixed /dev/MAKEDEV and then fixed this. screen works. 2.0.35 still works.
> > Finally, tab completion in bash, and pressing backspace at the start of a line
> > causes an extra space to be printed. I did "stty sane" and it still does it.
>
> Do you mean that the cursor is at the end of a line? If so, this is a bug
> in all PC kernels 1.x and so far 2.x. I thought that my patches fixed that...
> Hmm, just tried it, and if I have a line of 'a's with the cursor sitting under
> the last one, then hit backspace, it leaves the last 'a' there...
No, pressing tab sometimes generates spaces, and backspace on an empty line
(ie just a shell prompt) generates spaces.
2 other problems:
crond doesn't start: can't lock /var/run/cron.pid - other process may be 67108304.
invalid argument
(ish, in that punctuation may be wrong)
architecture is arm4vl, which causes modutil's configure to barf (so I
explicitly specified arm-linux, and it was happy)
This feels like some massive initiative test, which I'm struggling with.
I'm trying to make a list of all the right things to do in the right order,
starting with a bare bones a.out 2.0.35 installation. and ending up with ELF
and 2.2.2, but with 2.0.35 still bootable. I've still got 2.0.35 bootable,
but that's only because willy supplied me with a spare / partition, which
has got me out of trouble twice now.
Still can't get ppp to load - will compile 2.2.3 with it linked in :-)
eth0 says that its initialisation is delayed -would this be consistent with
insmod not getting the EtherH driver to load?
Nick
PS Is that supposed to be a pint in the penguin's flipper? I'm surprised that
the penguin didn't take it back to get it topped up - it's >15% head. :-(
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
