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

[linrad] RE: Linrad and Fedora Core 3



Hi Roger,

> Unfortunately, I still have the problem after rebooting.
> 
OK. I know now it is because the /dev/svga files are missing.

The solution I adapted was to run the svga file.

I put copies and links as in Makefile.ext which might
be part of the next Linrad version. (Unless Matan 
releases a new version that makes it superfluous)

Afterwords I got the following from Matan:

> I use FC3, and don't have this problem. FC3 uses udev, which creates 
> the devices automatically when the modules is inserted. 
> Do you run modprobe svgalib_helper, or trust kmod to load the module? 
> udev does not support this method, since the devices are not there 
> before the module is loaded.
>
> Anyway, since udev creates the /dev/ directory every boot, if you want a 
> permanent device that udev does not create for some reason, run
> 
> cp -a /dev/svga* /etc/udev/devices
>
> Since udev (or fedora startup scripts) copy devices from there to /dev 
> on boot.

Maybe using modprobe rather than insmod makes something automatically?

I tried svgalib-1.9.19 on several old distributions and it does not
work. I have sent error messages to Matan, maybe he can fix it easily.
I think it is valuable to keep backwards compatibility and make
Linrad easy to use on elderly computers. None of the modern distributions
runs directly on my old Pentium although it is fully adequate for 
Linrad with 5 kHz bandwidth. Maybe if I recompile the kernels for it
on another computer.....

The old svgalib-1.4.3 can still be used (of course) but its VESA driver
is so hopelessly slow.

Roger, I guess you are no longer interested in Fedora Core 3 judging 
all the posts on the list about other alternatives, but I try to ensure
Linrad will work under any distribution.......

73

  Leif / SM5BSZ

Attachment: Makefile.ext
Description: Binary data

Attachment: svga.dat
Description: Binary data

LINRADDARNIL
!