Raspberry Pi Buster Raspup
This is expected behaviour. The save file/folder is coded to the file bootmenu.txt on the first partition at save time. No searching is performed unless you select that option in the boot menu.Dud wrote:Hi Micko,
When creating a save file the defaults work fine.
When the file is placed on another partition - in my case the other part of the micro SD, it is not found.
- this from a one-off situation, not exhaustively checked.
Cheerio,
Puppy Linux Blog - contact me for access
@ Dud
If you hash out all the labels in bootmenu.txt except the .4fs you want to use, you will never see the blue box again. With my wireless keyboard I cannot use the blue box, no drivers available yet.
I guess if you have more than one .4fs then you will have to hash out the one you dont want then reboot, not a problem
Dont laugh, just dont laugh, I was locked out of the savefile for 2 days before the penny dropped that what is in the blue box is what is in the bootmenu.
Here is my bootmenu.
DEFAULT raspupsave-813.4fs
#LABEL raspup
PMEDIA usbflash
#LABEL "raspup pfix-ram"
PFIX ram
#LABEL "raspup pfix-copy"
PFIX copy
#LABEL search
SEARCH_DRIVE all
#LABEL "ram disk shell"
PFIX rdsh
LABEL raspupsave-813.4fs
PMEDIA usbflash
PUPSFS mmcblk0p1:/puppy_raspup_8.1.3.sfs
PSAVE sda2:/raspupsave-813.4fs
Thanks for the lx terminal Micko, cant see the cpu meter you nicked from fatdog !!
Has anyone been able to get a video downloader working on their pi?
If you hash out all the labels in bootmenu.txt except the .4fs you want to use, you will never see the blue box again. With my wireless keyboard I cannot use the blue box, no drivers available yet.
I guess if you have more than one .4fs then you will have to hash out the one you dont want then reboot, not a problem
Dont laugh, just dont laugh, I was locked out of the savefile for 2 days before the penny dropped that what is in the blue box is what is in the bootmenu.
Here is my bootmenu.
DEFAULT raspupsave-813.4fs
#LABEL raspup
PMEDIA usbflash
#LABEL "raspup pfix-ram"
PFIX ram
#LABEL "raspup pfix-copy"
PFIX copy
#LABEL search
SEARCH_DRIVE all
#LABEL "ram disk shell"
PFIX rdsh
LABEL raspupsave-813.4fs
PMEDIA usbflash
PUPSFS mmcblk0p1:/puppy_raspup_8.1.3.sfs
PSAVE sda2:/raspupsave-813.4fs
Thanks for the lx terminal Micko, cant see the cpu meter you nicked from fatdog !!
Has anyone been able to get a video downloader working on their pi?
@spotted
Menu >> Setup >> Set Default Boot Option
The GUI offers to boot the entry chosen as default.. can be changed at each boot if desired.
Menu >> Setup >> Set Default Boot Option
The GUI offers to boot the entry chosen as default.. can be changed at each boot if desired.
Puppy Linux Blog - contact me for access
Yes micko, after I had the savefile sorted I went into 'rasp pi boot' to try to have it boot to a 'raspupsave' (not a .4fs one) from another SD card. Could not get the boot process / rasp pi boot to pick up the imported 'raspupsave', deleted it.
Next project is to read up on f2fs filesystem to see if it works with raspup to see if I can use wiper to trim the SSD.
go figure booting from a micro SD card write, speed 22mbs, is 8 seconds faster than a USB3 bridge 400 mbs, (supposedly), SSD to boot.
Thanks for all your work.
Next project is to read up on f2fs filesystem to see if it works with raspup to see if I can use wiper to trim the SSD.
go figure booting from a micro SD card write, speed 22mbs, is 8 seconds faster than a USB3 bridge 400 mbs, (supposedly), SSD to boot.
Thanks for all your work.
Didnt take very long, f2fs works, but wiper dont. Try that on doze.
# ./wiper.sh /mnt/home
wiper.sh: Linux SATA SSD TRIM utility, version 3.6, by Mark Lord.
/sbin/hdparm: unrecognized option: V
BusyBox v1.31.0 (2019-08-05 23:31:11 +08) multi-call binary.
Usage: hdparm [OPTIONS] [DEVICE]
-v Defaults; same as -mcudkrag for IDE drives
-V Display program version and exit immediately
./wiper.sh: line 123: [: -lt: unary operator expected
/dev/mmcblk0p2: unable to reliably determine the underlying physical device name, aborting
#
# ./wiper.sh /mnt/home
wiper.sh: Linux SATA SSD TRIM utility, version 3.6, by Mark Lord.
/sbin/hdparm: unrecognized option: V
BusyBox v1.31.0 (2019-08-05 23:31:11 +08) multi-call binary.
Usage: hdparm [OPTIONS] [DEVICE]
-v Defaults; same as -mcudkrag for IDE drives
-V Display program version and exit immediately
./wiper.sh: line 123: [: -lt: unary operator expected
/dev/mmcblk0p2: unable to reliably determine the underlying physical device name, aborting
#
-
- Posts: 564
- Joined: Tue 09 Jun 2009, 21:06
Still running great.
Couple of minor issues to point out.
I installed Hexchat from the PPM which runs now having checked the SSL boxes but I get this message up beforehand '* Running IRC as root is stupid! You should create a User Account and use that to login'.
Also,after making a Pupsave Backup from the utility menu,this message stays behind 'Saving Session to Savfolder', until a 'Restart graphical server' is performed.
Couple of minor issues to point out.
I installed Hexchat from the PPM which runs now having checked the SSL boxes but I get this message up beforehand '* Running IRC as root is stupid! You should create a User Account and use that to login'.
Also,after making a Pupsave Backup from the utility menu,this message stays behind 'Saving Session to Savfolder', until a 'Restart graphical server' is performed.
Problem with Cameras on Raspup Buster
Hi Micko. Thank you for amazing Puppy edition for Paspberri Pi. It's very impressive to run Puppy in RAM.
I installed Motion Package from repository and trying to use both built-in and USB cameras on Raspup Buster. So far no luck with recognizing cameras. Modprobe /dev/video* returns video10, video11, video12 but not video0.
Sorry, I didn't use boot options for long time. What is difference between "raspup-ram" and "raspup-copy" options in bootmenu? Thank you.
I installed Motion Package from repository and trying to use both built-in and USB cameras on Raspup Buster. So far no luck with recognizing cameras. Modprobe /dev/video* returns video10, video11, video12 but not video0.
Sorry, I didn't use boot options for long time. What is difference between "raspup-ram" and "raspup-copy" options in bootmenu? Thank you.
Raspup is a great innovation. Because of the few OS available for the Pi 4, Raspup is very useful way to try the Pi 4 as a desktop replacement.
I've just Installed the latest version and loaded LibreOffice and Vivaldi, which runs well in my Pi 4.
Qn: However, Im not sure why Libre office Draw is not available in the menu.
Rasbian is a great system but comes with only basic apps. With Raspup one is ready to go with a wide variety of options. And the boot options are accessible, if not immediately understood, by new users.
Qn: How can one change the order of the blue boot menu options ? I would like my pupsave boot to appear at the top and/or be the default.
I really appreciate the sfs download menu item, even if there are only a few items available at present.
Great job, and thanks.
I've just Installed the latest version and loaded LibreOffice and Vivaldi, which runs well in my Pi 4.
Qn: However, Im not sure why Libre office Draw is not available in the menu.
Rasbian is a great system but comes with only basic apps. With Raspup one is ready to go with a wide variety of options. And the boot options are accessible, if not immediately understood, by new users.
Qn: How can one change the order of the blue boot menu options ? I would like my pupsave boot to appear at the top and/or be the default.
I really appreciate the sfs download menu item, even if there are only a few items available at present.
Great job, and thanks.
Re: Problem with Cameras on Raspup Buster
No use to 'modprobe /dev/video' because that isn't a module.Polivko wrote:Hi Micko. Thank you for amazing Puppy edition for Paspberri Pi. It's very impressive to run Puppy in RAM.
I installed Motion Package from repository and trying to use both built-in and USB cameras on Raspup Buster. So far no luck with recognizing cameras. Modprobe /dev/video* returns video10, video11, video12 but not video0.
Sorry, I didn't use boot options for long time. What is difference between "raspup-ram" and "raspup-copy" options in bootmenu? Thank you.
motion program works here with a logitec webcam.
Be sure to run
Code: Select all
motion -h
Adjust the config file at /etc/motion/motion.conf and where it says videodevice adjust to a valid device, /dev/video10 or whatever.
Code: Select all
ls /dev | grep video
video0
video1
video10
video11
video12
You can test your cam in gnome-mplayer. Menu >> MultiMedia >> GNOME Mplayer
Once it opens go to File >> TV >> Open Analog TV
Hope this helps.
- Attachments
-
- mott.png
- 'motion' in action - saves mkv video file in /var/lib/motion
- (63.5 KiB) Downloaded 730 times
Puppy Linux Blog - contact me for access
To keep it light I left Draw and others out of the libreoffice sfs. If you remove the sfs the full libreoffice should install ok from PPM, that's how I made the sfs, however it may be that you need to install the individual components.Geek3579 wrote:Raspup is a great innovation. Because of the few OS available for the Pi 4, Raspup is very useful way to try the Pi 4 as a desktop replacement.
I've just Installed the latest version and loaded LibreOffice and Vivaldi, which runs well in my Pi 4.
Qn: However, Im not sure why Libre office Draw is not available in the menu.
Rasbian is a great system but comes with only basic apps. With Raspup one is ready to go with a wide variety of options. And the boot options are accessible, if not immediately understood, by new users.
Qn: How can one change the order of the blue boot menu options ? I would like my pupsave boot to appear at the top and/or be the default.
I really appreciate the sfs download menu item, even if there are only a few items available at present.
Great job, and thanks.
To boot the save file by default look in the menu .. Menu >> Setup >> Set Default Boot Option. This will take effect even if you do not save the session.
HTH
Puppy Linux Blog - contact me for access
Unfortunately, built-in camera doesn't respond to any changes of video device setting in /etc/motion/motion.conf. USB camera works fine (as /dev/video0) in Motion and in GNOME Mplayer. It looks like the native Raspberry camera doesn't enable. Is there any chance to enable it (like config script on Raspbian)?
Polivko
Can you post your /var/log/messages file please soon after boot? I don't own a native pi camera so there may be some software or firmware missing from raspup.
If you run that code in a virtual terminal that will compress the log in /root so you can easily upload it to this forum as an attachment.
Can you post your /var/log/messages file please soon after boot? I don't own a native pi camera so there may be some software or firmware missing from raspup.
Code: Select all
cat /var/log/messages | gzip -9 > $HOME/messages_log.gz
Puppy Linux Blog - contact me for access
Polivko
Your kernel log looks in order, however I think that the kernel module for the native camera is not loading.
Can you provide an from raspbian with the camera plugged in? Then provide the same for raspup.
That will show what modules are loaded in respective OS.
Thanks
Your kernel log looks in order, however I think that the kernel module for the native camera is not loading.
Can you provide an
Code: Select all
lsmod # may need sudo lsmod
That will show what modules are loaded in respective OS.
Thanks
Puppy Linux Blog - contact me for access
Here is lsmod from Raspbian:
Code: Select all
~ $ sudo lsmod
Module Size Used by
rfcomm 49152 4
bnep 20480 2
hci_uart 40960 1
btbcm 16384 1 hci_uart
serdev 20480 1 hci_uart
bluetooth 389120 29 hci_uart,bnep,btbcm,rfcomm
ecdh_generic 28672 1 bluetooth
8021q 32768 0
garp 16384 1 8021q
stp 16384 1 garp
llc 16384 2 garp,stp
brcmfmac 311296 0
brcmutil 16384 1 brcmfmac
sg 28672 0
uas 24576 0
sha256_generic 20480 0
cfg80211 614400 1 brcmfmac
rfkill 28672 6 bluetooth,cfg80211
snd_bcm2835 24576 1
snd_pcm 102400 1 snd_bcm2835
snd_timer 32768 1 snd_pcm
raspberrypi_hwmon 16384 0
hwmon 16384 1 raspberrypi_hwmon
snd 73728 5 snd_timer,snd_bcm2835,snd_pcm
bcm2835_codec 36864 1
v4l2_mem2mem 24576 1 bcm2835_codec
videobuf2_dma_contig 20480 1 bcm2835_codec
fixed 16384 0
uio_pdrv_genirq 16384 0
uio 20480 1 uio_pdrv_genirq
bcm2835_v4l2 45056 1
bcm2835_mmal_vchiq 32768 2 bcm2835_codec,bcm2835_v4l2
vc_sm_cma 36864 1 bcm2835_mmal_vchiq
v4l2_common 16384 1 bcm2835_v4l2
videobuf2_vmalloc 16384 1 bcm2835_v4l2
videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_vmalloc
videobuf2_v4l2 24576 3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common 45056 4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev 200704 8 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
media 36864 3 bcm2835_codec,videodev,v4l2_mem2mem
i2c_dev 20480 0
ip_tables 24576 0
x_tables 32768 1 ip_tables
ipv6 450560 26
Here is lsmod for raspup:
Code: Select all
# lsmod
Module Size Used by
joydev 20480 0
8021q 32768 0
garp 16384 1 8021q
stp 16384 1 garp
llc 16384 2 garp,stp
brcmfmac 282624 0
brcmutil 16384 1 brcmfmac
sha256_generic 20480 0
cfg80211 598016 1 brcmfmac
rfkill 28672 1 cfg80211
snd_bcm2835 24576 0
snd_pcm 98304 1 snd_bcm2835
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_rawmidi 32768 1 snd_seq_midi
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 32768 2 snd_seq,snd_pcm
snd 73728 6 snd_seq,snd_timer,snd_rawmidi,snd_seq_device,snd_bcm2835,snd_pcm
raspberrypi_hwmon 16384 0
hwmon 16384 1 raspberrypi_hwmon
fixed 16384 0
bcm2835_codec 36864 0
v4l2_mem2mem 24576 1 bcm2835_codec
videobuf2_dma_contig 20480 1 bcm2835_codec
bcm2835_v4l2 45056 0
bcm2835_mmal_vchiq 32768 2 bcm2835_codec,bcm2835_v4l2
vc_sm_cma 36864 1 bcm2835_mmal_vchiq
v4l2_common 16384 1 bcm2835_v4l2
videobuf2_vmalloc 16384 1 bcm2835_v4l2
videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_vmalloc
videobuf2_v4l2 24576 3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common 45056 4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev 184320 6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
media 36864 3 bcm2835_codec,videodev,v4l2_mem2mem
uio_pdrv_genirq 16384 0
uio 20480 1 uio_pdrv_genirq
hid_logitech_dj 20480 0
hid_logitech_hidpp 36864 0
#
A reminder to partition the first partition fat32 rather than fat16.
I made that mistake because I was using an old SD card that used berryboot (that uses fat16).
I spotted error in terminal output.
___________________________________________________________
My TV is used for screen. Raspup recognizes full resolution better than fatdogarm.
______________________________________
Slow to boot on first try. Faster the second time. I will report back.
__________________________________________________________
I made that mistake because I was using an old SD card that used berryboot (that uses fat16).
I spotted error in terminal output.
___________________________________________________________
My TV is used for screen. Raspup recognizes full resolution better than fatdogarm.
______________________________________
Slow to boot on first try. Faster the second time. I will report back.
__________________________________________________________
Just got around to using it on my v.3B+. Very clumsy SDcard prep and very slow start up with far too many selection menus upfront. Default res. is tiny and stresses my ageing monitor, not to mention eyes! But it works, including wifi. Any chance of streamlining things and more universal defaults selection? Raspbian std. seems a better choice at present.
It needs to formatted by linux machine using gparted.Very clumsy SDcard prep
because of two partitions,
... but I wonder if it could be installed on a SD card that is fully fat32
which is how I have used fatdogarm. This works well since RAM is used.
Then a savefile is saved during shutdown. All files are fat32 compatible.
_______________________________________________________