[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [linrad] RE: Newcomer

It should be located in


make sure that the kernel you are installing to is the same kernel 
that you have the source pointed to by /usr/src/linux.  If not, get
the source and configure it (make cloneconfig should do it).   THEN, you
can go into svgalib-current version and do make install.
This will not install the .ko in the right place.  your locate tells
you where it is. 

cp svgalib_helper.ko /lib/modules/yourkernelversion/kernel/misc

depmod -a
modprobe svgalib_helper

should do it. It does on mine.

I have SUSE and your mileage may vary.

Good luck,

-----Original Message-----
From: owner-linrad@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-linrad@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of leif@xxxxxxxxxx
Sent: Sunday, February 06, 2005 11:51 PM
To: linrad@xxxxxxxxxxxxxxxxxxxxxx
Subject: [linrad] RE: Newcomer

Hello Patrick,

> I have the following setup :
> Linux : 32 bits FEDORA Core 3 (the 64 bits version works fine but very
> few software can run on it)
> svgalib-1.9.19 compiles ok and generates 5 devices in the /dev folder :
> svga, and svga1 to svga5 
> The /usr/local/lib folder contains the libvga.so.1.9.19 with 2 symbolic
> links pointing at it (libvga.so and libvga.so.1)
> After reboot, /dev/svga files are still there.
This is fine - but it is not the way Fedora 3 behaves when I 
install it. I have used default for everything except that I have 
included kernel sources. 

Did you run the Linrad "make svgalib" ? That would explain it 
because then the svga script Linrad has inserted in your /etc/init.d 
has put the /dev/svga files in place for you during the boot procedure.

> If I try to start linrad, I get the message : 
> svgalib: Cannot open /dev/svga
> Is svgalib_helper module loaded?
> a locate svgalib_helper give the result :
> /usr/src/svgalib/svgalib-1.9.19/kernel/svgalib_helper/svgalib_helper.ko
> If I try to do an insmod of that file,I get the message : -1 Unknown
> symbol in module
It seems to me you should have had an error message when compiling

How about kernels, have you used another kernel than the default one?
> So does anybody have an idea of what I may have done wrong ?
No. I hope you will find out without too much trouble.
Once you know, please inform me, it seems to be something
I should add at this place: