In the last mail Russell King - ARM Linux Admin said:
> Nicholas Clark writes:
> > > Depending on the kernel version you have, fbset -a will set the
> > > resolution for each and every console, including newly created ones.
> > > Some kernels may only do this for all existing consoles though.
> >
> > Is it because I have no XF86config file, so X is falling back to a nice safe
> > 640x480?
> > I don't know where to get such a file (it doesn't appear to be in the X rpms
> > on your site), or the XF86config binary to generate it.
>
> No - this X server is mostly identical to the old one - it'll work with
> the old kernels. If you want to run it at 1280x1024, try:
>
> fbset -a 1280x1024-60
>
> And that should sort you out.
No it didn't, mainly because I tried it while X was running. :-(
I wont do that again :-)
[didn't manage to fbset it back to 640x480. Did managed to enter kill -9 -1
This locked the entire machine, but bash has the command in its history file.
Odd)
> > $ insmod ppp.o
> > ppp.o: ppp.o: No such file or directory
>
> Is ppp.o in the current directory? If it's not, then this is expected.
> If you want insmod to pull it out of /lib/modules, then you should use
> insmod ppp
Also doesn't work
> Also, you can get the path which should exist for the modules by:
>
> echo /lib/modules/`uname -r`
2.2.2 - where modules are
> Check that /lib/modules/`uname -r`/misc/ppp.o exists. For msdos, check
In net, yes it's there.
> in /lib/modules/`uname -r`/fs for:
> fat.o
> msdos.o
>
Both present
> Also, have you run depmod -a ?
Yes, in /etc/rc.d/rc.sysinit
Odd,
Nick
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
