Alan Cox wrote:
>
> > > gcc -I/usr/include -I. -ldb aicasm_gram.c aicasm_scan.c aicasm.c aicasm_symbol.c
>-o aicasm
> > > /usr/i486-linux/bin/ld: cannot open -ldb: No such file or directory
> > > collect2: ld returned 1 exit status
> > > make[5]: *** [aicasm] Error 1
> > > [...]
> > >
Alan Cox wrote:
gcc -I/usr/include -I. -ldb aicasm_gram.c aicasm_scan.c aicasm.c aicasm_symbol.c
-o aicasm
/usr/i486-linux/bin/ld: cannot open -ldb: No such file or directory
collect2: ld returned 1 exit status
make[5]: *** [aicasm] Error 1
[...]
Mark Mokryn wrote:
> Is it possible to build an SMP module on a machine running a UP kernel
> (or vice versa)? We of course get unresolved symbols during module load
> due to the smp prefix on the ksyms, and haven't seen how to get around
> it. (Defining __SMP__ does not cut it, though I believe
Mark Mokryn wrote:
Is it possible to build an SMP module on a machine running a UP kernel
(or vice versa)? We of course get unresolved symbols during module load
due to the smp prefix on the ksyms, and haven't seen how to get around
it. (Defining __SMP__ does not cut it, though I believe this
The problem reported here before was switching from X to the console.
The video signal would be lost and the computer would hang.
The responses pointed out the it was the switch of video modes; XFree
would change the internals of the video controller which the frame
buffer could not cope with.
The problem reported here before was switching from X to the console.
The video signal would be lost and the computer would hang.
The responses pointed out the it was the switch of video modes; XFree
would change the internals of the video controller which the frame
buffer could not cope with.
I experienced lost of the signal when switching from X to the console
when booting with vga=ext or some of the graphic modes. It was reported
here that the problem was the Matrox drivers.
Recently, with kernel 2.4.4+ and XFree 4.0.3 (@1280x1024/head)+ Matrox
drivers
It would help if you reported which version of kernel and XF86 you are
using. I had problems using the framebuffer in the console awhile back.
Currently, running 2.4.4+ and XFree86 4.0.3 + Matrox's drivers
(http://matrox.com/mga/support/drivers/files/linux_06.cfm) give me no
problem.
I don't
It would help if you reported which version of kernel and XF86 you are
using. I had problems using the framebuffer in the console awhile back.
Currently, running 2.4.4+ and XFree86 4.0.3 + Matrox's drivers
(http://matrox.com/mga/support/drivers/files/linux_06.cfm) give me no
problem.
I don't
I experienced lost of the signal when switching from X to the console
when booting with vga=ext or some of the graphic modes. It was reported
here that the problem was the Matrox drivers.
Recently, with kernel 2.4.4+ and XFree 4.0.3 (@1280x1024/head)+ Matrox
drivers
I tried to give you some pointers in a personal email. So it's not true
you didn't receive any response. Also reminded you of the best place to
look for info, namely, that driver's mailing list. You don't seem to
have made any additional attempts at resolving it yourself since you
reposted your
I tried to give you some pointers in a personal email. So it's not true
you didn't receive any response. Also reminded you of the best place to
look for info, namely, that driver's mailing list. You don't seem to
have made any additional attempts at resolving it yourself since you
reposted your
This may be what you are looking for:
http://oss.sgi.com/projects/fam/
--
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
This may be what you are looking for:
http://oss.sgi.com/projects/fam/
--
Rafael
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
14 matches
Mail list logo
