It is Dougal's remaster script, which I did modify a little so the wireless would work.rjbrewer wrote:Another Fluppy surprise:
In order for us "full install" users to remaster it was necessary to
use "Dougals remaster script" on 4.xx and earlier Puppies.
This doesn't work with the new versions.
I tried it using Fluppys' Remaster Puppy and it worked perfectly!
I have a 168mb clone of my modified Fluppy on bootable cd......
the ultimate backup.
Edit; more surprises.
The remaster cd has this laptop intel wireless configured;
when I booted into a different laptop and pc the different
wireless cards configured automatically. Ready to browse.
Fluppy 013
vattery 0.6.2
Compaq Mini CQ10-101SO
Vattery shows Battery percentage = 0% when I disconnect the AC-adapter. Being too lazy for trying to debug Vattery, I have replaced it with.
ecube
Vattery shows Battery percentage = 0% when I disconnect the AC-adapter. Being too lazy for trying to debug Vattery, I have replaced it with.
Code: Select all
#!/bin/bash
# bat-0.1 Battery status
# 2010-07-20 OlovE Initial version
fstat="/proc/acpi/battery/BAT1/state"
finfo="/proc/acpi/battery/BAT1/info"
#
if [ -e $fstat ]; then
REM=`cat $fstat|grep remaining`; echo $REM;
REM=${REM##remaining capacity: }; REM=${REM%% *};
STATE=`cat $fstat|grep charging`; echo $STATE;
STATE=${STATE##charging state: };
else
echo "ERROR! file $fstat not found"; exit 1
fi
if [ -e $finfo ]; then
FULL=`cat $finfo|grep full`; echo $FULL;
FULL=${FULL##last full capacity: }; FULL=${FULL%% *};
else
echo "ERROR! file $finfo not found"; exit 1
fi
REM=100*$REM/$FULL; REM=`echo "scale=1; ${REM}" | bc`
yaf-splash -timeout 3 -font "9x15B" -outline 0 -margin 4 -bg cyan -placement bottom -text "Battery: $REM% $STATE"
ecube
- Attachments
-
- forum.jpg
- Battery status
- (8.33 KiB) Downloaded 1916 times
Trying to use Xorg on the new kernel versions usually didn't
work for us with Intel 855gm graphics chips.
Here is a fix for that problem that works on Luci 213 and also
works on my Fluppy 003 install.
http://www.murga-linux.com/puppy/viewto ... 855#435855
It worked a few times, then started having shutdown and reboot
problems. Only with the full install.
Edit:
2 short pushes of power button drops to X, where reboot,
poweroff or xwin can be typed.
work for us with Intel 855gm graphics chips.
Here is a fix for that problem that works on Luci 213 and also
works on my Fluppy 003 install.
http://www.murga-linux.com/puppy/viewto ... 855#435855
It worked a few times, then started having shutdown and reboot
problems. Only with the full install.
Edit:
2 short pushes of power button drops to X, where reboot,
poweroff or xwin can be typed.
Last edited by rjbrewer on Mon 26 Jul 2010, 19:09, edited 2 times in total.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
In case your Fluppy notebook gets liberated
http://adeona.cs.washington.edu/
Traces your laptop - might be nice for Fluppy
http://adeona.cs.washington.edu/
Traces your laptop - might be nice for Fluppy
Loading drivers needed to access disk drivers.....Solved!?
I have encountered some weird booting behavior when trying to install quirky120 and luci210 on my Compaq Mini CQ10-101SO. What happens is that in most cases the booting hangs at "Loading drivers needed to access disk drivers....." and a hard reset has to be performed. Fluppy-003 and puppeee-502 boot normally every time. Occasionally quirky and luci will boot as expected and install the puppies correctly (see encl).
I haven't found any correlation between the boot procedure and the unsuccessful boot. grub1 and grub2 behave the same.
Any comments would be most welcome.
ecube
Edit: Modification of initrd.gz/init seems to solve the problem
I haven't found any correlation between the boot procedure and the unsuccessful boot. grub1 and grub2 behave the same.
Any comments would be most welcome.
ecube
Edit: Modification of initrd.gz/init seems to solve the problem
Code: Select all
echo "-DEBUG" > /dev/console
for ONEMODALIAS in $MODALIASES
do
sleep 1
modprobe -q $ONEMODALIAS #-q means quiet
[ $? -eq 0 ] && echo -n "." > /dev/console
echo "$? - ONEMODALIAS=$ONEMODALIAS" > /dev/console
done
- Attachments
-
- quirky.jpg
- quirky-120
- (51.46 KiB) Downloaded 392 times
-
- luci.jpg
- luci-210
- (89.88 KiB) Downloaded 384 times
Last edited by ecube on Tue 27 Jul 2010, 20:29, edited 1 time in total.
Fluppy 003
I installed fluppy on my emachines D620 yesterday and it's working great so far.
Computer
Processor AMD Athlon(tm) Processor 2650e
Memory 1813MB (217MB used)
Operating System Puppy Linux 0.43
User Name root (root)
Date/Time Thu 29 Jul 2010 09:11:05 AM EDT
Display
Resolution 1280x800 pixels
OpenGL Renderer Mesa DRI R300 (RS690 791F) 20090101 x86/MMX+/3DNow!+/SSE2 NO-TCL
X11 Vendor The X.Org Foundation
Multimedia
Audio Adapter HDA-Intel - HDA ATI SB
thanks.
Computer
Processor AMD Athlon(tm) Processor 2650e
Memory 1813MB (217MB used)
Operating System Puppy Linux 0.43
User Name root (root)
Date/Time Thu 29 Jul 2010 09:11:05 AM EDT
Display
Resolution 1280x800 pixels
OpenGL Renderer Mesa DRI R300 (RS690 791F) 20090101 x86/MMX+/3DNow!+/SSE2 NO-TCL
X11 Vendor The X.Org Foundation
Multimedia
Audio Adapter HDA-Intel - HDA ATI SB
thanks.
I think Jemimah got aware of it in the Puppeee rc8 thread too.I have encountered some weird booting behavior when trying to install quirky120 and luci210 on my Compaq Mini CQ10-101SO. What happens is that in most cases the booting hangs at "Loading drivers needed to access disk drivers....." and a hard reset has to be performed. Fluppy-003 and puppeee-502 boot normally every time. Occasionally quirky and luci will boot as expected and install the puppies correctly (see encl).
I haven't found any correlation between the boot procedure and the unsuccessful boot. grub1 and grub2 behave the same.
Any comments would be most welcome.
Confused
ecube
Edit: Modification of initrd.gz/init seems to solve the problem
Code:
echo "-DEBUG" > /dev/console
for ONEMODALIAS in $MODALIASES
do
sleep 1
modprobe -q $ONEMODALIAS #-q means quiet
[ $? -eq 0 ] && echo -n "." > /dev/console
echo "$? - ONEMODALIAS=$ONEMODALIAS" > /dev/console
I have same problem. Sometimes I can try to boot 7 times in a row and still fail at same place as you describe too. 5 dots in the first line so two of them is still needed.
Could it be USB responding too late. I have both USB mouse keyboard so it could be them not giving feedback that works for the iso?
I am not savvy enough to try out your solution.
I experimented to add nosmp due to me having an Atom cpu in my Acer.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Wonder if this is an ancestor of Fluppy?
The Floppy Show was a Des Moines, Iowa TV show that was broadcast
on WHO-TV from 1957 to 1987.
Floppy was a beagle dog puppet that had a high voice provided by
self-taught ventriloquist Duane Ellett.
http://www.facebook.com/group.php?gid=17140830660
The Floppy Show was a Des Moines, Iowa TV show that was broadcast
on WHO-TV from 1957 to 1987.
Floppy was a beagle dog puppet that had a high voice provided by
self-taught ventriloquist Duane Ellett.
http://www.facebook.com/group.php?gid=17140830660
- Attachments
-
- n17140830660_7479.jpg
- (12.44 KiB) Downloaded 1385 times
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Boot problems
I enclose a modified version of initrd.gz for qrky-120. This is an ad hoc solution. I hope someone familiar with puppy's inner life will create a more elegant solution.
Thanks ecube
What does such modification do? Has it do do something with the relatively new Atom Netbooks or "mini" computers with Intel circuits while the iso works on Desktops with other cpu?Edit: Modification of initrd.gz/init seems to solve the problem
Code:
echo "-DEBUG" > /dev/console
for ONEMODALIAS in $MODALIASES
do
sleep 1
modprobe -q $ONEMODALIAS #-q means quiet
[ $? -eq 0 ] && echo -n "." > /dev/console
echo "$? - ONEMODALIAS=$ONEMODALIAS" > /dev/console
done
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
-
- Posts: 97
- Joined: Tue 09 Dec 2008, 06:10
- Location: USA (Springfield, Vermont)
-
- Posts: 33
- Joined: Thu 17 Jun 2010, 01:14
- Location: Atlanta, GA
Frugal Fluppy Install on 1 gb Jump Drive
I've been a satisfied user of Puppeee on my 2g surf for about a month and decided to try to create a jump drive version of Fluppy 3.0 for use on my work Lenova S10e netbook.
Based on the instructions listed on the puppeee site I'd assume that the installer script is failing. I'm using bootinst.sh since I'm doing it from a puppeee machine. The shell script has the following message prior to closing:
./boot/syslinux/syslinux: possibly unsafe /tmp/ permissions
Disk /dev/sdb1 should be bootable now. Installation finished.
I've tried booting it from both the 2g Surf and the Lenova Atom and I get the error that 'Drive is not Bootable' I've also tried using ext2, ext3 and FAT32 on this jump drive to no avail. Any suggestions?
PatrickJ
Based on the instructions listed on the puppeee site I'd assume that the installer script is failing. I'm using bootinst.sh since I'm doing it from a puppeee machine. The shell script has the following message prior to closing:
./boot/syslinux/syslinux: possibly unsafe /tmp/ permissions
Disk /dev/sdb1 should be bootable now. Installation finished.
I've tried booting it from both the 2g Surf and the Lenova Atom and I get the error that 'Drive is not Bootable' I've also tried using ext2, ext3 and FAT32 on this jump drive to no avail. Any suggestions?
PatrickJ
Congrats on releasing Puppeee.
I've been running Fluppy 003 on my desktop for a while now with no real problems,just one small aggravation.I have a wired ethernet connection and on every boot I get an Xdialog message about not detecting my wireless card.I don't use a wireless card so I'd like to get rid of the message.
Thanks in advance.
I've been running Fluppy 003 on my desktop for a while now with no real problems,just one small aggravation.I have a wired ethernet connection and on every boot I get an Xdialog message about not detecting my wireless card.I don't use a wireless card so I'd like to get rid of the message.
Thanks in advance.