Upup Raring 3.9.9.2 with non-PAE 3.9.9 kernel. 13 July 2013
CuteSDR?
I used PPM to acquire and install CuteSDR_1.0.5-3 along with all of the dependencies.
The only thing missing was "update-job". (Which appears to be a ubuntu script or something to monitor version changes.)
I ran an update of the PPM/ubuntu respositories just prior to this.
I have the devx sfs set for boot.
I have tried the qt-4.7.1.sfs set for boot and removed, no difference.
CuteSDR fails to recognize my terratec SDR and sometimes freezes and has to be killed.
Anyone tried this and/or have a suggestion as to what may cause this, please?
The only thing missing was "update-job". (Which appears to be a ubuntu script or something to monitor version changes.)
I ran an update of the PPM/ubuntu respositories just prior to this.
I have the devx sfs set for boot.
I have tried the qt-4.7.1.sfs set for boot and removed, no difference.
CuteSDR fails to recognize my terratec SDR and sometimes freezes and has to be killed.
Anyone tried this and/or have a suggestion as to what may cause this, please?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
SDR app Direwolf - compile as PET or SFS?
Just discovered an app called Direwolf that includes Gqrx but once the Linux source is unzipped I have no idea how to successfully get it into a PET or SFS for Raring 3992.
Has anyone compiled this for Puppy?
http://home.comcast.net/~wb2osz/site/?/page/Download/
Has anyone compiled this for Puppy?
http://home.comcast.net/~wb2osz/site/?/page/Download/
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
edoc
Rename Makefile.linux to Makefile, or symlink it.
Run 'make' and it compiles quite quickly.
Have a look in the Makefile at the 'install' section. It shows the directory structure - what goes where. Create this in a 'direwolf-0.9' directory and copy the relevant files over.
This is what it is like - file first, followed by destination (just stripped this out of the Makefile).
You could probably skip the Windows.pdf...
Run dir2pet or dir2sfs on this directory, and off you go.
Rename Makefile.linux to Makefile, or symlink it.
Run 'make' and it compiles quite quickly.
Have a look in the Makefile at the 'install' section. It shows the directory structure - what goes where. Create this in a 'direwolf-0.9' directory and copy the relevant files over.
This is what it is like - file first, followed by destination (just stripped this out of the Makefile).
Code: Select all
decode_aprs /usr/local/bin
text2tt /usr/local/bin
tt2text /usr/local/bin
ll2utm /usr/local/bin
utm2ll /usr/local/bin
aclients /usr/local/bin
tocalls.txt /usr/share/direwolf/tocalls.txt
dw-icon.png /usr/share/direwolf/dw-icon.png
direwolf.desktop /usr/share/applications/direwolf.desktop
direwolf.conf ~
dw-start.sh ~
CHANGES.txt /usr/local/share/doc/direwolf/CHANGES.txt
LICENSE-dire-wolf.txt /usr/local/share/doc/direwolf/LICENSE-dire-wolf.txt
LICENSE-other.txt /usr/local/share/doc/direwolf/LICENSE-other.txt
User-Guide.pdf /usr/local/share/doc/direwolf/User-Guide.pdf
Raspberry-Pi-APRS.pdf /usr/local/share/doc/direwolf/Raspberry-Pi-APRS.pdf
APRStt-Implementation-Notes.pdf /usr/local/share/doc/direwolf/APRStt-Implementation-Notes.pdf
Quick-Start-Guide-Windows.pdf /usr/local/share/doc/direwolf/Quick-Start-Guide-Windows.pdf
Run dir2pet or dir2sfs on this directory, and off you go.
Thank you Keef ...
I renamed Makefile.linux to Makefile.
I ran Make.
When you wrote the following were you referring to the text that scrolled as Make did it's thing?
This next I don't understand.
Thanks!
I renamed Makefile.linux to Makefile.
I ran Make.
When you wrote the following were you referring to the text that scrolled as Make did it's thing?
So, what I am looking for is in the Console history?Have a look in the Makefile at the 'install' section. It shows the directory structure - what goes where.
This next I don't understand.
Are you saying that I need to create a file of some sort into which I copy the list that you extracted (or a list like it from my Console history)?Create this in a 'direwolf-0.9' directory and copy the relevant files over.
Thanks!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
I'll start again!!
I'm assuming 'make' ran ok, and you have got the binaries.
You now need to make a new directory for direwolf to create the pet or sfs. You also need to replicate the file structure the relevant files would be installed to.
This is quite easy, if a little tedious:
Open a terminal and type (or copy and paste)
[mkdir foo will make a single directory called 'foo'. mkdir -p foo/boo makes 'foo' and another inside it called 'boo'. In case you wondered what '-p' was for]
You can check in a rox window (or whatever filemanager you use) that this looks ok.
Leave the terminal open.
You don't actually need to look at the Makefile (Makefile.linux) as I gave you the information anyway.
You don't have to copy it - just read it!
It tells you where each file needs to go eg direwolf, aclients, and gen_fff etc go in /usr/local/bin
dw-icon.png goes into /usr/share/direwolf/
..and so on.
The direwolf.conf and dw-start.sh files go into the 'root' directory (shown by '~' in the list).
Just drag'n'drop using Rox will do. Set the window to list the contents then sort by 'Type' to make it easier (see pic below)
(I don't think the other folders in there 'misc' 'regex' 'utm' are needed for anything).
Once you've done copying, type
This takes you up a couple of levels so you are outside the 'direwolf-0.9' directory.
Now, if you want a pet, just type 'dir2pet direwolf-0.9' and follow the instructions.
For a sfs..
dir2sfs direwolf-0.9
You can make all the directories with Rox if you prefer - just right click, 'New' > 'Directory' then enter the name. Click on the new directory and do the next one etc..
Hope this is clearer.
I'm assuming 'make' ran ok, and you have got the binaries.
You now need to make a new directory for direwolf to create the pet or sfs. You also need to replicate the file structure the relevant files would be installed to.
This is quite easy, if a little tedious:
Open a terminal and type (or copy and paste)
Code: Select all
mkdir -p direwolf-0.9/usr/local/bin direwolf-0.9/root
cd direwolf-0.9/usr/
mkdir -p share/direwolf local/share/doc share/applications
You can check in a rox window (or whatever filemanager you use) that this looks ok.
Leave the terminal open.
You don't actually need to look at the Makefile (Makefile.linux) as I gave you the information anyway.
You don't have to copy it - just read it!
It tells you where each file needs to go eg direwolf, aclients, and gen_fff etc go in /usr/local/bin
dw-icon.png goes into /usr/share/direwolf/
..and so on.
The direwolf.conf and dw-start.sh files go into the 'root' directory (shown by '~' in the list).
Just drag'n'drop using Rox will do. Set the window to list the contents then sort by 'Type' to make it easier (see pic below)
(I don't think the other folders in there 'misc' 'regex' 'utm' are needed for anything).
Once you've done copying, type
Code: Select all
cd ../../
Now, if you want a pet, just type 'dir2pet direwolf-0.9' and follow the instructions.
For a sfs..
dir2sfs direwolf-0.9
You can make all the directories with Rox if you prefer - just right click, 'New' > 'Directory' then enter the name. Click on the new directory and do the next one etc..
Hope this is clearer.
- Attachments
-
- Screenshot_2013-11-20_132625.png
- (167.77 KiB) Downloaded 438 times
Thank you for your patience and the extra detail.
I go way back in Linux ... and way back in missing the tiny steps that others take for granted (Debian drove me nuts) ... so I've learned to wait on others, to request paint-by-numbers instructions, or to live without.
After I get some breakfast and coffee I me I'll walk through this and report back.
Thanks again ... I have printed this and will save it in my Linux binder ... just maybe there will be a breakthrough in my aversion to compiling & creating PETs!
I go way back in Linux ... and way back in missing the tiny steps that others take for granted (Debian drove me nuts) ... so I've learned to wait on others, to request paint-by-numbers instructions, or to live without.
After I get some breakfast and coffee I me I'll walk through this and report back.
Thanks again ... I have printed this and will save it in my Linux binder ... just maybe there will be a breakthrough in my aversion to compiling & creating PETs!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Finally got to try this.
/usr/share/applications/ was actually /usr/share/apps - is that OK?
Is the "WARNING" in this next part of things of concern?
I had to manually create the /usr/share/direwolf/ directorysh-4.1# mkdir -p direwolf-0.9/usr/local/bin direwolf-0.9/root
sh-4.1# cd direwolf-0.9/usr/
sh-4.1# mkdir -p share/direwolf local/share/doc share/applications
sh-4.1# cd ../ ../
/usr/share/applications/ was actually /usr/share/apps - is that OK?
Is the "WARNING" in this next part of things of concern?
GUI window
Press ENTER key to bring up a GUI window that will help you to create
a database entry for the package. This will be shown in a text editor
for saving somewhere, also written to file 'pet.specs' inside the pkg.
Press ENTER:
** (gtkdialog4:23553): WARNING **: The recently launched window "DLG_REPONAME" is missing an equivalently named variable directive <variable>DLG_REPONAME</variable> which is a requirement of the launch action.
|ubuntu|raring||ewolf|0.9||Network|8136K||direwolf-0.9.pet||APRS Soundcard TNC
Creating package...
File ./direwolf-0.9.tar.gz created. Now converting to .pet...
direwolf-0.9.pet has been created. Finished.
If you look in direwolf-0.9 you will see the new '.specs' file.
Directory direwolf-0.9 is now configured correctly as a PET package
and in future you do not need to go through this script again.
You could manually edit the files if required, and create another
.pet package just by doing this:
# tar -c -f direwolf-0.9.tar direwolf-0.9/
# gzip direwolf-0.9.tar
# tgz2pet direwolf-0.9.tar.gz
dir2pet exited.
sh-4.1#
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
LXDE derivative
If anybody wants to try a derivative of Upup Raring 3.9.9.2 with LXDE as the desktop environment, the iso is available from:
Sourceforge - 201MB
Cheers
peebee
Sourceforge - 201MB
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Did a full install on yet another old box...... working well.
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation NV18 [GeForce4 MX 4000] (rev a4)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb fbdevhw glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
376 frames in 5.0 seconds = 75.187 FPS
382 frames in 5.0 seconds = 76.332 FPS
471 frames in 5.0 seconds = 94.172 FPS
390 frames in 5.0 seconds = 77.868 FPS
363 frames in 5.0 seconds = 72.504 FPS
.
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3800+
Memory : 2073MB (272MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Thu 21 Nov 2013 02:08:49 AM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : VIA8237 - VIA 8251
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation NV18 [GeForce4 MX 4000] (rev a4)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb fbdevhw glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
376 frames in 5.0 seconds = 75.187 FPS
382 frames in 5.0 seconds = 76.332 FPS
471 frames in 5.0 seconds = 94.172 FPS
390 frames in 5.0 seconds = 77.868 FPS
363 frames in 5.0 seconds = 72.504 FPS
.
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3800+
Memory : 2073MB (272MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Thu 21 Nov 2013 02:08:49 AM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : VIA8237 - VIA 8251
Code: Select all
# free
total used free shared buffers
Mem: 2073568 402848 1670720 0 8860
-/+ buffers: 393988 1679580
Swap: 2150396 0 2150396
#
- Attachments
-
- Raring.jpg
- (60.96 KiB) Downloaded 979 times
3.5.2.8
Post to wrong thread... sorry
Thanks for catching that edoc.... just out of hospital, not thinking clear yet I guess, was just excited to see pemasu on a roll again!
>>>---Indian------>
Thanks for catching that edoc.... just out of hospital, not thinking clear yet I guess, was just excited to see pemasu on a roll again!
>>>---Indian------>
Last edited by sszindian on Thu 21 Nov 2013, 18:10, edited 2 times in total.
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
I'm confused ... big surprise, huh?
Can you explain the numbering sequence that makes 3.5.2.4 progress from 3.9.9.2, please?
Can you explain the numbering sequence that makes 3.5.2.4 progress from 3.9.9.2, please?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
This:Can you explain the numbering sequence that makes 3.5.2.4 progress from 3.9.9.2, please?
http://www.murga-linux.com/puppy/viewtopic.php?t=80546
Ah, OK, sszindian messed with my mind by posting that here rather than in the Wheezy thread.
Thanks!
I don't know how you do it all!
BTW: Someone is trying to teach me how to compile & build a PET ... can you believe that? I have, of course, triggered a couple of oddball outputs ... it's what I do ... and await his clarification as to how to proceed.
Who knows, this could be a breakthrough after so many years.
Thanks!
I don't know how you do it all!
BTW: Someone is trying to teach me how to compile & build a PET ... can you believe that? I have, of course, triggered a couple of oddball outputs ... it's what I do ... and await his clarification as to how to proceed.
Who knows, this could be a breakthrough after so many years.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Absent a reply I tried the PET.
It created no Menu entry and neither "direwolf" or "direwolf-0.9" are recognized in Console.
Apparently either one of the anomalies I mentioned is causing this or else I missed a step or ...
Where do I begin looking for the problem, please?
It created no Menu entry and neither "direwolf" or "direwolf-0.9" are recognized in Console.
Apparently either one of the anomalies I mentioned is causing this or else I missed a step or ...
Where do I begin looking for the problem, please?
edoc wrote:direwolf-0.9.pet has been created. Finished.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Re: 3.5.2.8
Hopefully on the road to 100% mend from the hospital?sszindian wrote:Post to wrong thread... sorry
Thanks for catching that edoc.... just out of hospital, not thinking clear yet I guess, was just excited to see pemasu on a roll again!
>>>---Indian------>
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
{Enter shameless plug mode}
I have built a voice-controlled puppy based on Upup 3.9.9.2 : Thread here:
http://murga-linux.com/puppy/viewtopic.php?t=90391
So if your mouse breaks or your arms fall off you will still be able to control Upup!
{Exit shameless plug mode}
I have built a voice-controlled puppy based on Upup 3.9.9.2 : Thread here:
http://murga-linux.com/puppy/viewtopic.php?t=90391
So if your mouse breaks or your arms fall off you will still be able to control Upup!
{Exit shameless plug mode}
GCC-4.7.3 question
Hi pemasu,
upup Raring has GCC-4.7.3 - the same version as in Ubuntu. Barry's Raring GCC version is 4.6.4. I want to upgrade that to 4.7.3. Downloaded the deb package from this link:http://packages.ubuntu.com/raring/gcc-4.7, unpacked it and the structure is absolutely different from what I see in the devx. First of all, these are missing '/usr/bin/c89-gcc' '/usr/bin/c99-gcc'.
usr/lib/gcc is an entirely different animal in devx. Can I just copy over GCC files from your Raring to Barry's? If yes, can you help me pinpoint them?
Thank you in advance.
.
upup Raring has GCC-4.7.3 - the same version as in Ubuntu. Barry's Raring GCC version is 4.6.4. I want to upgrade that to 4.7.3. Downloaded the deb package from this link:http://packages.ubuntu.com/raring/gcc-4.7, unpacked it and the structure is absolutely different from what I see in the devx. First of all, these are missing '/usr/bin/c89-gcc' '/usr/bin/c99-gcc'.
usr/lib/gcc is an entirely different animal in devx. Can I just copy over GCC files from your Raring to Barry's? If yes, can you help me pinpoint them?
Thank you in advance.
.
radio tnc ax25 kissattach usb
I am trying to connect to a radio TNC-type device via USB.
ax25 was apparently not installed
I installed ax25-tools, ax25-tools, ax25-xtools via Puppy Package Manager.
From Console "dmesg | grep ttyACM0" produces:
"[ 18.647282] cdc_acm 2-1:1.0: ttyACM0: USB ACM device"
I believe that I need to run kissattach with ttyACM0 but am not sure from the dmesg output how to correctly do that.
"ls /dev/ttyA*" produces:
"/dev/ttyACM0 /dev/ttyACM1"
The ACM0 is yellow, the ACM1 is blue.
No idea why the different colors.
Any ideas, please?
Thanks!
ax25 was apparently not installed
I installed ax25-tools, ax25-tools, ax25-xtools via Puppy Package Manager.
From Console "dmesg | grep ttyACM0" produces:
"[ 18.647282] cdc_acm 2-1:1.0: ttyACM0: USB ACM device"
I believe that I need to run kissattach with ttyACM0 but am not sure from the dmesg output how to correctly do that.
"ls /dev/ttyA*" produces:
"/dev/ttyACM0 /dev/ttyACM1"
The ACM0 is yellow, the ACM1 is blue.
No idea why the different colors.
Any ideas, please?
Thanks!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Edoc.
# modprobe ax25
# modprobe mkiss
# lsmod
Module Size Used by
mkiss 6394 0
ax25 34108 1 mkiss
So...I can tell that Upup Raring has those needed kernel modules included.
Otherwise....ham radio stuff...well...as I posted earlier. It is stuff for ham radio hobbyists and enthusiasts. I think you should ask those questions in some ham radio forum or search the net with google search.
# modprobe ax25
# modprobe mkiss
# lsmod
Module Size Used by
mkiss 6394 0
ax25 34108 1 mkiss
So...I can tell that Upup Raring has those needed kernel modules included.
Otherwise....ham radio stuff...well...as I posted earlier. It is stuff for ham radio hobbyists and enthusiasts. I think you should ask those questions in some ham radio forum or search the net with google search.