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

[linrad] Re: Debian

Hello dear Roger!

w3sz wrote:
Hello, All,

With the help of Ramiro and Patrick and Zaba's recent 'HOW-TO's and with Zaba's giving me some advice on OSS's FTP address, I was today able to get Linrad running under Debian with kernel 2.6.8-2-386. THANKS GUYS for the helpful advice and 'cheat-sheets'!!

Thank you very much for your report!

My first impressions are:

1. Linrad seems to work as well under Debian as it did under Fedora Core 3.

2. I have NOT been able to get XWINDOWS working under Debian [even with the VESA driver], and while that doesn't matter for Linrad, it makes doing everything else with Linux much more difficult. It is like turning the clock back 25 years to the DOS and CPM days...not pretty. Doing the dpkg-reconfigure xserver-xfree86 thing didn't help with my hardware [Intel Extreme Graphics 2]. X Windows still fails to start with Debian. It worked 'right out of the box' with FC3.

Well, as you have seen, you can install Debian from the simplest textmode OS, to the most complicated window manager. I do see that as an advantage. :-) The advantage is that you understand how the OS is made from the bottom to the top layers. I see that Debian if a bit difficult at the start, as was for me, but after the first month everything starts making sense and you control everything.

I do not understand why you can not start X even with the vesa driver. I supose you have made many tries and you know your case better than me, but what are the error messages? (/var/log/Xfree....). I supose that Fedora uses the Xorg instead the Xfree that Debian uses now. Debian is going to switch to Xorg as soon as Sarge is released. Tell me what x-related packages you have installed. "dpkg -l |less" What X driver do you use under Fedora ? Is it included on the Xfree of debian. I think vesa should work.

I had some additional issues that arose in getting Debian and Linrad to play nice with each other:

1. I had the same trouble with svgalib in Debian that I had with Fedora core 3, presumably due to the 2.6.x kernels. Compiling svgalib 1.9.20 wrote the svga* devices to /dev, but these disappeared on rebooting as they weren't saved. So I had to do a cp -a /dev/svga* /etc/udev/devices before rebooting. To do thisI had to first create the directory /etc/udev/devices as it didn't exist. With Debian, linux doesn't automatically put these devices back into /dev on rebooting, so one then needs to do a cp -a /etc/udev/devices/svga* /dev/ when rebooting.

Well, I do not understand. I installed Debian from the rc-3 installer and it cames with NO udev of devfs by default. Did you install udev yourself? I do not use udev now, and I prefer to manually manage the devices. Anyway, Debian lets you the ability of installing udev whenever you want after the install if you desire.

2. My Delta 44 and other soundcards would NOT work with the alsa-oss sound under Debian. I had to ftp oss3992c-linux-x86-v26.tar.gz from www.se.opensound.com . The file is in the directory /pub/oss/linux. You need to log on as anonymous. For Debian I needed the nonregparm version, which is what I listed here. FC3 required the other one [regparm].

Thank you! I can not test that because I do not have the Delta card here. Are you sure that they can not work?

Many thanks for the link. It would be good that Leif include your information for people with that card on the guide I wrote.

3. OSS would not install because of the sound system already in place, and although oss-install tried to remove the sound system, it failed. I had to remove the 'snd' file from the appropriate directory and reboot. Then sound couldn't start on reboot, and then OSS would install OK. OSS gave some error messages on install, but it still works OK.

You can do it by removing the alsa related packages
"apt-get remove --purge package" will remove even the configuration files. That is because alsa-base instructed "discover" to ignore the OSS drivers, I think....

4. I had 19 sound devices once oss installed, and the ?logical? choices in Linrad produced no properly working results. So I ran osstest and it showed me the /dsp numbers of each device as it ran. It turned out that I had to use /dsp6 for the Delta 44, and /dsp1 for the Intel CH5. When running ossmix to set envy24.rate to 96000, the Delta44 was d3. All of this will vary for your setup.

Leif, please add this information to the guide.

5. Just in case someone just tuned in: the 'modprobe svgalib_helper' thing is still necessary. So is adding /dev/input/mice to the /etc/vga/libvga.config file.

The same.

SO, if I can get XWINDOWS working with Debian, I might make it my main installation. Otherwise, it is just too much of a headache to use for everything other than Linrad without XWINDOWS. Since I never had FC3 lock up when running Linrad for 24 hours or so like it did for Leif, there is really no motivation for me to switch, other to be able to say I did it, and to stay compatible with those who are running Linrad and Debian. My Debian vs FC3 install time comparison must now be something like 30 hours for Debian vs 30 minutes for FC3. FC3 works perfectly for me. Debian still doesn't have XWINDOWS. Hmmm... ;)

Well, installing Debian now that you know how to do it will take you no more than 30 minutes.hi..Even less if you install it from a full CD (not the mininst 100MB CD)

Anyway, I am preocupied for your X issue. Keep me informed.
If you can not start X your system will not be good for daily use, of course.

Hope the above helps!



This message is sent to you because you are subscribed to
 the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>