[linrad] Re: Debian Etch
Leif Asbrink wrote: Hi All, This is only for those of you who run Debian Etch. Running apt-get upgrade may make your system impossible to boot. For a while I thought my hard disk was corrupted because the last thing I had done before rebooting was to try the SDR-14 which did not work (2.14 under X11/Debian) Now I know the problem and the cure so I thought I should share it with you. What happens after apt-get upgrade is that the next boot fails like this: Begin: Waiting for root file system... If I wait for a long time some more text appears: Done. Alert /dev/hda1 does not exist. Dropping to shell! . . . A simple way to cure this problem: 1) Mount the hard disk on the second IDE bus so it becomes /dev/hdc 2) Put something that works as /dev/hda (I used a hard disk with RedHat 9 on it) 3) Boot up and mount /dev/hdc1 as /mnt/hdc1 4) Type chroot /mnt/hdc1 5) Type apt-get install udev 6) Shut down, put the Debian Etch disk back as /dev/hda and reboot. Info is available on the Internet, but maybe it will save some time for someone to find it here:-) 73 Leif SM5BSZ Thanks Leif for the advice! I think that it also can be fixed easily using a livecd and following a similar procedure. I have not upgraded to etch yet. I am working with stable. Ramiro. PS: I have been busy in the last month so I have not been able to play with new versions of Linrad! EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: svgalib segfaults
Leif Asbrink wrote: Hello Ramiro, I also have not been able to reproduce the bug on my desktop computer. The bug shows only on my laptop computer. I have been trying to run Linrad under gdb and valgrind but any of them allows it. I cant run Linrad within them. This seems odd, I thought that an X11 installation would always look the same to an application (like valgrind). Can you install valgrind without errors? Hello Leif, I use valgrind stardard Debian sarge package, so there is no problem in installing it. I have no idea what this means. Maybe you could install the lastest one, svgalib-1.9.24. If you do, and if you do not remove the old /etc/vga/libvga.config you will have to edit the file manually to add a line NoHelper to avoid having to install svgalib_helper. I am going to try it now. What can I do to run Linrad under the debuggers? Hopefully someone else can answer this:-) No one answered that :-( 73, Ramiro. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: svgalib segfaults
Hello again! I have just compiled svgalib 1.9.24 and linrad works great using NO_HELPER mode! No crashes, it works just fine. Can we conclude it was a svgalib bug? 73, Ramiro, EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: svgalib segfaults
Leif Asbrink wrote: Hi Ramiro, -- sgvalib linrad 02.07 works for some while and segfaults: svgalib: signal 4: Illegal instruction received svgalib: signal 11: Segmentation fault received I have not been able to reproduce. I have tried Sarge with the 2.6.8 kernel but it just runs fine. The 8-bit ALSA is OK under Sarge so the only problem I can see is that I can not read all the bits from the Delta44 using ALSA. Hello Leif, I also have not been able to reproduce the bug on my desktop computer. The bug shows only on my laptop computer. I have been trying to run Linrad under gdb and valgrind but any of them allows it. I cant run Linrad within them. This is the error message I have got (without any debugger): Using VESA driver, 7872KB. VBE3 svgalib 1.4.3 vm86() failed return = 0x1 eax = 0x2164e001 ebx = 0x ecx = 0xff01 edx = 0x esi = 0x edi = 0x ebp = 0x0fda eip = 0x0001 cs = 0xc000 esp = 0x0fd8 ss = 0x1000 ds = 0x es = 0x1121 fs = 0x gs = 0x eflags = 0x00233206 cs:ip = [ 55 aa 7a e9 f7 df 30 30 30 30 30 30 30 30 30 30 ] svgalib: Signal 11: Segmentation fault received. Violaci¢n de segmento debian-pcbox:/home/ramiro/linrad-02.07# screendump leif1.txt What can I do to run Linrad under the debuggers? Thanks 73, Ramiro. EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: svgalib segfaults
On 4/21/06, Leif Asbrink [EMAIL PROTECTED] wrote: Hi Ramiro, -- sgvalib linrad 02.07 works for some while and segfaults: svgalib: signal 4: Illegal instruction received svgalib: signal 11: Segmentation fault received I have not been able to reproduce. I have tried Sarge with the 2.6.8 kernel but it just runs fine. The 8-bit ALSA is OK under Sarge so the only problem I can see is that I can not read all the bits from the Delta44 using ALSA. Fine Leif. I can reproduce the segfault every time try it. I think I could debug it fine because it crashes with consistence. I am at work know, I will try to do the debugging when I arrive at home and tell you the results. It is obvious that you have detected a bug. Maybe you can use a debugger to get some info about it? It could be an error in the Linrad code that might lead to various problems in the future so I am very interested to know. It could also be a bug inside svgalib or ALSA that cause an interrupt-related problem. Ok Leif, we will keep in touch! Ramiro. EA1ABZ. 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad-02.07
Leif Asbrink wrote: Hi All, Known bugs are now corrected:-) Hello Leif, -- Xlinrad 02.07 works very well, no crashes, no segfaults, no problems at all. -- sgvalib linrad 02.07 works for some while and segfaults: svgalib: signal 4: Illegal instruction received svgalib: signal 11: Segmentation fault received Congratulations for your work! 73, Ramiro, EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad 02.06a
Leif Asbrink wrote: Hello Ramiro, xlinrad crashes under Debian Sarge and shows the following Segmentation Fault debbuged with gdb. I send it to you just in case it gives you some clues. Is the 890=0x37A port a parallel port register? What is it used for under Linrad? Linrad uses the parallel port to control the WSE hardware. For this reason one has to run Linrad as root, something that also makes it easier to use svgalib. Oh my good, I was running xlinrad as a normal user, what a mistake. It works as root! I asumed that root was neccesary only for svgalib :-( Sorry for that I will elaborate later, I must go work know. Thanks!! and Sorry!!! EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad 02.06a
Linrad uses the parallel port to control the WSE hardware. For this reason one has to run Linrad as root, something that also makes it easier to use svgalib. Thanks, I shoud have read the manual. If you want to disable the parallel port reads and writes, set VALGRIND TRUE in vernr.h Ok. I have now downloaded Sarge and it does not support my Delta44 so I have to use the SCSI card in RDWR mode. This made me discover a bug in 06a (and a few earlier ones): Linrad closes the device before it stopped both input and output which causes segfaults. It has nothing to do with Sarge, I noticed because Sarge made me try RDWR which I had not done for quite some time. Interesting. At least your 12 hours download worth the effort! RDWR is the mode I use! Ramiro, since your hardware does not need the parallel port, you should make a users hwaredriver that does not offend your preferred mode of operation. That is another way to disable parallel port access. Linrad 02-07 will (hopefully) give an error message rather than a segfault. Thank you very much Leif for the suggestions. I hope one day I can understand how Linrad works internally. Anyway, I am learning C reading your code under Vim editor and it is a very good learning experience. This editor is really efficient for jumping between function calls. ;-) 73 Ramiro. EA1ABZ. 73 Leif # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad 02.05 part II, svgalib version.
I do not undertand why this happens, because I chose N to the question:
use mlockall to prevent swapping ? (Y/N) - N
This is a trivial bug. There should have been a test if(ui.memloc==0)
Ok. The xz() function has been a very efective way of finding where the
crash occured. Thanks for the tip!
In 02.06 and later renamed to if(ui.no_memlock == FALSE)
I have started to use TRUE/FALSE for variables used as boolean variables
and sometimes the variable name has to change to reflect whether
a 0 or a 1 matches what the name suggests. (I do not want to change
parameter values)
Understood.
Early like this the mlocall call seldomly fails, that is why I never
detected it. As a temporary solution, just remove the line lir_lock_mem();
Yes, mlockall fails with consistence here within linrad, but if I do
this simple program never fails here.
#include sys/mman.h
#include stdio.h
void main(void){
int i;
i=mlockall(MCL_CURRENT);
printf(returned value is %d \n,i);
}
It always return a 0 value and never crashes
Who knows!! :-)
73, Ramiro.
There will be a greatly improved Lir-02.06 tomorrow:-)
We will wait for the new version
Thank you very much!!!
#
This message is sent to you because you are subscribed to
the mailing list linrad@antennspecialisten.se.
To unsubscribe, E-mail to: [EMAIL PROTECTED]
To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED]
To switch to the INDEX mode, E-mail to [EMAIL PROTECTED]
Send administrative queries to [EMAIL PROTECTED]
[linrad] Linrad 02.05
Hello again. I have tested xLinrad 02.05 on both very different machines. A 1.86 GHz 1GB RAM Pentium Centrino laptop and a 1.2 GHz AMD Athlon 256 MB desktop computer. I get an strange CPU usage increase up to 100 % before real operation, in the parameter selection screen. xlinrad * *** Both computers, same result. *** I press S I choose 1 font size. I choose N to allow swapping. I press A for weak signal CW I choose device 63 /dev/dsp I choose RDRW W I choose one RX channel I choose 44100 sampling rate close and reopen? YES I press a key to return to the main menu. I press w to save setup I press A for weak signal CW. I enter into the parameter selection screen At this point the CPU usage goes up to 100%!!! The laptop fan starts going fast! top - 12:43:15 up 1:14, 3 users, load average: 0.93, 0.44, 0.17 Tasks: 80 total, 1 running, 78 sleeping, 0 stopped, 1 zombie Cpu(s): 99.7% us, 0.3% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si Mem: 1028320k total, 385420k used, 642900k free,28092k buffers Swap: 489972k total,0k used, 489972k free, 174272k cached I press Enter I press Enter I press Enter I press Enter It bombs out: segmentation fault Thank you very much. Ramiro, EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad 02.05 part II, svgalib version.
[EMAIL PROTECTED] wrote: Hi Ramiro, The way I locate this kind of errors is th change DUMPFILE, now in vernr.h, to 1. Hello Leif, I have done the debugging you suggested. After some compilation and xz iterations, I have found that the funcion that completly crashes my computer is mlockall(), called from function lir_lock_mem() in lsys.c. lir_lock_mem() is called from main() in lmain.c The call to mlockall() never returns and crashes the computer. I do not undertand why this happens, because I chose N to the question: use mlockall to prevent swapping ? (Y/N) - N Svgalib mouse settings are ok cause mousetest works fine. Tell me if you want me to do more tests. Ramiro. EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad 02.05 part II, svgalib version.
Hi Leif,
Forgot to post the debugging xz:
int lir_lock_mem(void)
{
int i,k;
xz(lir_lock_mem_1);
i= mlockall(MCL_CURRENT);
xz(lir_lock_mem_2);
if(i==0)return 0;
k=errno;
munlockall();
errno=k;
return i;
}
More information about the mlockall issue.
This dirty code modification removes the first crash and linrad
screen appears and works well during some time, until it crashes again
when I press X.
The crash blocks all pure text consoles, but I can get GNOME with
ctrl-alt-F7. I run ps ax and can not locate any linrad process running
in order to kill them.
int lir_lock_mem(void)
{
int i,k;
//i= mlockall(MCL_CURRENT);
i=0;
if(i==0)return 0;
k=errno;
munlockall();
errno=k;
return i;
}
I do not understand anything... :-(
Regards.
Ramiro.
EA1ABZ
#
This message is sent to you because you are subscribed to
the mailing list linrad@antennspecialisten.se.
To unsubscribe, E-mail to: [EMAIL PROTECTED]
To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED]
To switch to the INDEX mode, E-mail to [EMAIL PROTECTED]
Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad-02.05
Robert McGwier wrote: Thank you for getting there before I had a chance. I love this tool. It has saved my technical ife on three occassions in the last year. Bob Hello Bob, I had heard about gdb but never heard valgrind. You were the first person that let me know that valgrind existed. I have not used any of them except for finding bugs for other expert people. My programming skills are not good. I would like in the future to be able to write good programs but I am not sure of that. I think that programming is an art, and cannot be understood just by reading books as I have done. The only way to learn how to program is programming. So I admire people who write good code. Thanks. Ramiro. EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad-02.04
Leif Asbrink wrote: Hi Ramiro, I have just downloaded Linrad-02.05 and I can go a little bit further but It crashes again. This is the sequence of commands I press S I choose 1 font size. I choose N to allow swapping. I press A for weak signal CW I choose device 63 /dev/dsp I choose RDRW W I choose one RX channel I choose 44100 sampling rate close and reopen? YES I press a key to return to the main menu. I press w to save setup I press A for weak signal CW. I enter into the parameter selection screen I press Enter I press Enter I press Enter I press Enter It bombs out: segmentation fault Could be CPU overload. Try to deselect fft2 and also set baseband storage time low. Remove par_wcw first because otherwise you may not be able to reach the parameter setting screens. (or edit par_wcw manually) Hello Leif, I have done the changes that you suggested with no luck. The program crashes at the same function. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1132374960 (LWP 6457)] 0x080a7bb1 in rx_output () I have disabled second fft and reduced baseband storage to 1 second. I am running a 1 GB RAM, 1.86 GHz Pentium Centrino laptop. If you need more tests please let me know. Ramiro. EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
