Re: Dell Latitude LX

2000-10-13 Thread Kero van Gelder
> The second is when I bought it, it had windows 95 on it with no > documention. My development efforts involve OpenGL (really MESA) > and I need some rudimentry X support. Does anyone know which > chipset this laptop uses and more importantly which X-server to use? Try VGA16. We used it on an o

Re: Dell Latitude LX

2000-10-13 Thread Kero van Gelder
> The second is when I bought it, it had windows 95 on it with no > documention. My development efforts involve OpenGL (really MESA) > and I need some rudimentry X support. Does anyone know which > chipset this laptop uses and more importantly which X-server to use? Try VGA16. We used it on an

Re: Damage line on screen

2000-09-20 Thread Kero van Gelder
> I sort of assumed on a laptop list that you would expect it to be an lcd. Oops... missed hat one. Too many debian newsgroups in one folder :-/ > and yes, I think suddenly, as in I noticed it once it was there. OK. > Until I bring up the X-window manager - i.e. at the just booted stage, the >

Re: Damage line on screen

2000-09-20 Thread Kero van Gelder
> I sort of assumed on a laptop list that you would expect it to be an lcd. Oops... missed hat one. Too many debian newsgroups in one folder :-/ > and yes, I think suddenly, as in I noticed it once it was there. OK. > Until I bring up the X-window manager - i.e. at the just booted stage, the >

Re: Damage line on screen

2000-09-19 Thread Kero van Gelder
> A vertical damage line (single column of pixels showing red on black > background) has appeared on my screen exactly at the centre which is > luckily between the 2 windows I normally use. Hm... What do you mean with ``black background''? If it is one column... > Is it possible I have done this

Re: Damage line on screen

2000-09-19 Thread Kero van Gelder
> A vertical damage line (single column of pixels showing red on black > background) has appeared on my screen exactly at the centre which is > luckily between the 2 windows I normally use. Hm... What do you mean with ``black background''? If it is one column... > Is it possible I have done thi

Re: printing ascii files

2000-09-17 Thread Kero van Gelder
> This should be an easy one to answer. When I print ascii files, I often > get word-overflow. In other words, a word at the end of a line gets > split between that line and the next like this: > > Printing ASCII should be rela > tively easy, but for newbies > it is not. > > > I have read the p

Re: printing ascii files

2000-09-17 Thread Kero van Gelder
> This should be an easy one to answer. When I print ascii files, I often > get word-overflow. In other words, a word at the end of a line gets > split between that line and the next like this: > > Printing ASCII should be rela > tively easy, but for newbies > it is not. > > > I have read the

Re: DELL Inspiron 5000 wrong harddisk-size

2000-04-11 Thread Kero van Gelder
> I've got my first notebook a Dell Inspiron 5000. For all I've read, > I thought this one would work with Linux. But: > First thing, Linux complains about the harddisk which was preinstalled > with WIN98 (sorry for the words...). It has 12GB. After killing all > partitions under DOS, formatting a

Re: modules on kernels with flavor

2000-04-11 Thread Kero van Gelder
> >> - The cardmgr complains the pcmcia modules are not for this kernel, > >> and I have to compile/install pcmcia modules manually. > > Kero> I had the same. Documented feature, as far as I recollect. > > Well, it is documented that you have to recompile them, but I > couldn't recompile with ma

Re: modules on kernels with flavor

2000-04-07 Thread Kero van Gelder
> Hi, does anybody compiles his own kernel with > flavor around here? When I did this, I had > the following problems: > > - The modules go to /lib/modules/`uname -r`-flavor > but the module loader searches on /lib/modules/`uname -r` Worked fine with me, kernel 2.2.14 You'd not happen to use an

Re: Fast shutdown without filesystemcheck on next boot?

2000-04-07 Thread Kero van Gelder
> I trying to find a way to shut down my laptop > *really* quick (1 - 2 seconds) from the console. > > I can't wait until all processes have died. What I > want to do is "sync" - "close all open filehandles" > "umount" "poweroff" > > the problem is that unmount often says that > some filesystems

Re: Help! How not to start X ?

2000-03-14 Thread Kero van Gelder
> Hi, > > I installed debian's base and X on my notebook. but failed to follow > the advice not to start X at boot time. > > Now, X got started, but then frozes. Log in from a remote server, issue `chvt 1` as root. You should (with some luck) be back at the console now, with a frozen X still liv