Activity for Chris
-
Chris posted a comment on ticket #87
Ah, ok. That makes sense. Thanks, Chris Maness -Sent from my iPhone On Thu, May 30, 2024 at 7:00 AM Dave van der Locht davevdl@users.sourceforge.net wrote: No, I think you're misunderstanding me... There's a config parameter in one of LinFBB's C header files to force support for FBB data files generated/used by a 32-bit version of FBB. That parameter needs to be set ONLY if you need to use FBB datafiles from a 32-bit FBB version in a 64-bit version of FBB... It makes LinFBB on a 64-bit OS compatible...
-
Did you have to do anything different to your 64bit Slackware-current to make sure there is 32 bit support? I did not with Slack15 release. It all works fine here. But what you are explaining does sound like a reasonable explanation with what is going on. -Chris KQ6UP On Thu, May 30, 2024 at 2:31 AM Dave van der Locht davevdl@users.sourceforge.net wrote: As mentioned earlier I've tested with the 7.0.11 release of LinFBB (see Files section). With the latest development (SVN) source there shouldn't...
-
Dave, did you pull the latest source off of sourceforge for your test? I tried something. I pulled my satel.dat file that was working on my system at work, and installed it on the slack-current system. The satellite list was all scrambled in FBB. That is really weird, and I have never seen that before. I have been able to use those files even on WinFBB from that system. -Chris KQ6UP On Thu, May 23, 2024 at 12:17 PM Chris kq6up@users.sourceforge.net wrote: Just to make sure I was not going crazy,...
-
Just to make sure I was not going crazy, I tried the same keps (downloaded from amsat.org) on my Slack14.1 system at work. Worked like a charm! I am doing the EXACT same thing on the system at home. The system at home is a fresh build with the iso that you linked too. I built a freshly downloaded source from sourceforge, and did a completely new install. See the output below: satupdat dailytle.txt /n /s Update of F6FBB's BBS satellite data base orbital parameters Version 1.89 - February 2015 - Bernard...
-
Wow, fresh install Slackware-current and still getting the same error. What browser are you using to download the keps? This has got to be something obvious, and thank you for your patients. Are you also using a x86_64 system? I am doing satupdat with /n (and tried all three other possible flags and get the same problem). On Wed, May 22, 2024 at 1:40 PM Dave van der Locht davevdl@users.sourceforge.net wrote: You can test both... Before and after, just to see where things go (or already are) wrong...
-
Nope -- still fails. Had to do the autoreconf bit too. That was a first for me. Here is the output: g++ -DHAVE_CONFIG_H -I. -I../../.. -g -O2 -MT mail_screen.o -MD -MP -MF .deps/mail_screen.Tpo -c -o mail_screen.o mail_screen.cc mail_screen.cc: In function ‘void init_main_screen()’: mail_screen.cc:39:16: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’} 39 | maxx = stdscr->_maxx; | ^~ In file included from mail_screen.cc:13: /usr/include/curses.h:456:16: note: forward declaration...
-
But doing the slackpkg update/upgrade first, or no? Thanks, Chris Maness -Sent from my iPhone On Wed, May 22, 2024 at 12:46 PM Dave van der Locht davevdl@users.sourceforge.net wrote: Ok, so you did something else before testing on a fresh install. Please also try without patching the kernel (or doing any other things) before testing satupdat initially. Just to verify if something in the steps in between is or isn't messing things up big time. One step at a time... [tickets:#87] https://sourceforge.net/p/linfbb/tickets/87/...
-
Strange issue you (still) have... Compiling without X support is done with ./configure --disable-x-utils, see ./configure --help. Will do that. How do you download or transfer the input file onto the system? Are you sure the input file isn't corrupted somehow? You're sure you haven't done anything else besides installing the OS and compiling linfbb to test? Although higly unlikely, things that could break the standard C library? No. I only patched the kernel for the AX.25 bug, and I have downloaded...
-
Now on EXT4. No difference. How do you compile without X support in Slackware-current? I remove motif library while compiling, am not sure if that would make a difference (I doubt it). I have done that on other systems where having X configured causes compile to fail. Is there a variable I can set before running ./configure that will turn of X? -Chris KQ6UP On Wed, May 22, 2024 at 5:12 AM Chris kq6up@users.sourceforge.net wrote: Ok. I will update it and test satupdate on the new EXT4 system. On Tue,...
-
Compile Failure Slackware-current
-
Ok. I will update it and test satupdate on the new EXT4 system. On Tue, May 21, 2024 at 11:52 PM Dave van der Locht davevdl@users.sourceforge.net wrote: My slackware-current test system is using the 6.9.1 kernel. I've tested satupdat with this kernel version using an EXT4 filesystem. [tickets:#87] CRC Error with Satellite Database Update Status: open Milestone: 7.0.11 Labels: satelite CRC error Created: Mon May 20, 2024 02:33 AM UTC by Chris Last Updated: Tue May 21, 2024 01:40 PM UTC Owner: nobody...
-
Did you do slackpkg update/upgrade-all? The image you linked to me had 6.6.25 kernel. I did the slackpkg update which brought me to the current and most recent stable fork off the mainline tree. That is 6.9.1. That way we are comparing apples to apples. I just built the system with that image using ext4, but wanted to see if the filesystem is what makes the difference because that would be odd to me. So if you get yours up to 6.9.1, and it still works for you, I will proceed with my experiment here....
-
I am having issues with BTRFS on this system, but it is related to making tarballs from snapshots. The / file system goes to 100% even though I am writing the tarball to nfs or even another mounted drive. BTRFS has been how I do backups, as it is easy to take reliable snapshots of a live system. However those snapshots are not as useful if I can’t dump them to a tarball for offline safe keeping. -I will have to build a new system as I am having issues with uronode connecting on the NETROM layer....
-
It is still doing it for me. What commands are you issuing it? I am also using the bulletin keps found here (tho I tried the ones from the link you sent me and had the same problem): https://www.amsat.org/tle/daily-bulletin.txt I am using BTRFS for my filesystem, but I am not thinking that should affect anything. -Chris KQ6UP On Tue, May 21, 2024 at 5:09 AM Chris kq6up@users.sourceforge.net wrote: Good to know. I am wondering if I should try to rebuild it against the new libraries and try it again....
-
Good to know. I am wondering if I should try to rebuild it against the new libraries and try it again. I can also send you a kernel patch that makes 6.9.1 stable for use with AX.25 if you are interested. 6.9.1 crashes with incoming connections without it. -Chris KQ6UP On Tue, May 21, 2024 at 1:54 AM Dave van der Locht davevdl@users.sourceforge.net wrote: I've just installed a (64-bit) slackware-current test system using this night's ISO. After compiling and installing VE7FET's libax25 I started compiling...
-
For what it is worth, I have never seen this on any other slackware or Debian based system before. This only happens in Slackware-current. It is a brand new system with only FBB and VE7FET's packet stuff installed on it. I only mentioned the kernel patches to explain why I am running Slackware-current instead of a stable release. I just applied a patch manually this morning (the only one that I have done) to the stock 6.9.1 kernel. It is supposed to make the system stable when incoming connections...
-
No, there is some issue with the OS satupdate. Even the keps from your link do the same thing. Do you want this system? I can post it on google drive for you. It is a virtual system running in VirtualBox. I have been testing the new kernel that they have been working on the AX.25 stack. -73 de Chris KQ6UP On Mon, May 20, 2024 at 12:46 AM Dave van der Locht davevdl@users.sourceforge.net wrote: Are you sure you're input file isn't corrupted / wrong? The satupdat source only relies on some standard...
-
CRC Error with Satellite Database Update
-
Mail List Support Page
-
News Groups (NNTP)
1