> I'm stuck with this Motorola winmodem too (sm56 chipset).
> I tried to search for its driver's source code so I can compile it, but
> I didn't find it. All I find is Motorola's rpm file which doesn't work
> on RedHat 7.2
>
> Does anyone here know where can I find the driver's source?
>
As f
it's not the lilo. it's the kernel... it's the framebuffer driver you
use to get graphics mode. it is well known to improve performance.
Noam
On Fri, 2001-12-21 at 22:44, Diego G. Iastrubni wrote:
> Hi all
>
> I started playing with my system (now I have ext3, which means i can just press the
>
Hi all,
I've seen that many people started spreading the Conexant winmodem drivers
for linux (for kernel 2.2.x and 2.4.x)
All the details are at my little web site:
http://witch.dyndns.org/article.php?sid=3
--
Hetz Ben Hamo
[EMAIL PROTECTED]
=
Hi all
I started playing with my system (now I have ext3, which means i can just press the
power button
like I do on windows..) and decided to change lilo from a graphic boot into a menu.
Which looks cool
either way.
When I boot from a text menu in lilo, in X I see a ugly "noise" or distorcion
I'm stuck with this Motorola winmodem too (sm56 chipset).
I tried to search for its driver's source code so I can compile it, but
I didn't find it. All I find is Motorola's rpm file which doesn't work
on RedHat 7.2
Does anyone here know where can I find the driver's source?
Boaz Yagodiner
---
> if you simply need to write text files - use vi/vim
> for word-like word processor - use KOfiice with biditext patch.
> if you need to write hebrew text with many formulae, simply use the good
> old Latex, and then compress it into postscript.
> if you want to create compatibile *.doc files - u
> Hi!
> I'm using linux for more then 3 years, so I sure don't
> consider myself a newbe (although I'm not a linux
> expert either.) Recently I've decided to update my
> RH7.1 to 7.2. During the installation I've got a
> report of a bug. I've searched the web for the answer
> (RH site and archives
> At 12:30 21/12/2001, you wrote:
> >For some reason the behavior of gdb when I split a C++ program into
> >multiple files is not the same as when there is only one source file.
> >In particular, in the multiple file case gdb does not recognize local
> >variables and does not honor breakpoints tha
On Fri, 21 Dec 2001, Max Kovgan wrote:
> if you simply need to write text files - use vi/vim
>
> for word-like word processor - use KOfiice with biditext patch.
This is not good, because they won't be printed right.
> if you need to write hebrew text with many formulae, simply use the good
> ol
At 12:30 21/12/2001, you wrote:
>For some reason the behavior of gdb when I split a C++ program into
>multiple files is not the same as when there is only one source file.
>In particular, in the multiple file case gdb does not recognize local
>variables and does not honor breakpoints that are set
For some reason the behavior of gdb when I split a C++ program into
multiple files is not the same as when there is only one source file.
In particular, in the multiple file case gdb does not recognize local
variables and does not honor breakpoints that are set by line numbers.
What am I missin
11 matches
Mail list logo