Page 12 of 100

Posted: Wed 07 Jul 2010, 15:17
by pemasu
Could it be possible to include also atheros NIC driver to the next Fluppy . Acer uses it in timelinex series laptops.

Package included which I found from the net following ubuntu discussion threads. Original place I dont remember.

Posted: Wed 07 Jul 2010, 15:46
by jemimah
Are these cards not handled by the ath5k and ath9k drivers?

Posted: Wed 07 Jul 2010, 18:24
by pemasu
Atheros Wlan card is handled, but NIC card isnt. Normally I use wlan, but sometimes Ethernet connection is needed

Needed driver module seems to be atl1e.

EDIT: I forgot to say that existing atl1e does not recognize ethernet card.

Posted: Wed 07 Jul 2010, 20:26
by jemimah
pemasu wrote:Atheros Wlan card is handled, but NIC card isnt. Normally I use wlan, but sometimes Ethernet connection is needed

Needed driver module seems to be atl1e
That should work fine on anything newer than 2.6.31, I believe.

Posted: Wed 07 Jul 2010, 21:13
by abushcrafter
jemimah wrote:There's a driver for it but I hear it's unstable. I will grab the latest version and add it to the next Fluppy.
Thanks, However I can't test it as I don't have it. I am curently deciding on which netbook to get.

Posted: Thu 08 Jul 2010, 03:39
by James C
I did a frugal install of Fluppy 003 on one of my desktops (2.0 ghz Athlon XP/1 gb ddr ram/1.25gb swap) a couple of days ago and everything worked fine out of the box.

Just wanted to tell you, "Great job". :)

Posted: Thu 08 Jul 2010, 12:15
by jemimah
abushcrafter wrote:
jemimah wrote:There's a driver for it but I hear it's unstable. I will grab the latest version and add it to the next Fluppy.
Thanks, However I can't test it as I don't have it. I am curently deciding on which netbook to get.
Get an EeePC. Puppeee can boot in 10 or 15 seconds if properly configured, plus out of the box support for over/under clocking, fan control. Suspend/hibernate definitely works, and is totally stable. No driver issues. Puppeee also recognizes and optimizes performance on SSDs.

Posted: Thu 08 Jul 2010, 15:38
by aarf
jemimah wrote: Get an EeePC. Puppeee can boot in 10 or 15 seconds if properly configured.
(COUGH) Oh? do tell. my puppeeerc7 needs little configuring.

Posted: Thu 08 Jul 2010, 16:52
by jemimah
http://puppeee.com/web/blog/how-to-boot-fast

Basically, you run the Zdrive cutter, then do a full install and switch to Xvesa, and a couple other tweaks.

Note, you probably shouldn't do a full install on an SSD unless you consider the drive disposable.

Posted: Thu 08 Jul 2010, 18:17
by aarf
jemimah wrote:http://puppeee.com/web/blog/how-to-boot-fast

Basically, you run the Zdrive cutter, then do a full install and switch to Xvesa, and a couple other tweaks.

Note, you probably shouldn't do a full install on an SSD unless you consider the drive disposable.

ok jemimah i'll take your word for. my fast pace action packed split-second life will have to make do without those precious few seconds. :wink: :lol:

Posted: Fri 09 Jul 2010, 13:29
by mikul101
Jemimah is there an eta for fluppy 4 as I have the same issue with the Samsung N130 which has the same Realtek RTL8192E wireless card?

Posted: Fri 09 Jul 2010, 15:49
by jemimah
Probably two or three weeks. I want to release Puppeee, then build Fluppy 004 from Puppeee 1.0.

I may be convinced to post that driver sooner though. :)

Fluppy-003 patch suggestions

Posted: Wed 14 Jul 2010, 17:53
by ecube
Jemimah,

I have been running luci-210 (USB-stick installation) on an old HP laptop without hard disk and battery. The other day I bought a Compaq C0101-101S0 mini-pc as a possible replacement. Alas, luci-210 wouldn't boot on the Compaq. Fortunately, thanks to your excellent work, fluppy-003 turned out to work flawlessly.

I have added a few patches which may be of interest to you.

1. The quirky version of PartView. It replaced the version fluppy is using. It shows mounted drives as default with "All Drives" as an option which can be slow on low-end hardware.

2. Network_tray-2.1. A small modification of the query version.

Code: Select all

 network_tray.c
void tray_icon_on_click(GtkStatusIcon *status_icon, gpointer user_data)
{
    system("pip");
}
Clicking on the Network_tray icon shows the IP-address or "No IP-address found". The icon didn't show up after I installed the pet. But by clicking on the empty space between the fremem-applet and the loadspeaker in the tray, you can test the function.

3. Pdict. A minor improvement.

4. SwissWatch. For users liking analog clocks.

Keep up the good work
:D
ecube
Edit: 1. The icons added to network_tray pet. 2 pdict window adjusted

Posted: Fri 16 Jul 2010, 18:32
by rjbrewer
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.

Re: Fluppy-003 patch suggestions

Posted: Sun 18 Jul 2010, 17:31
by jemimah
ecube wrote:
I have added a few patches which may be of interest to you.
Thank you. I will check it out.

Posted: Sun 18 Jul 2010, 17:32
by jemimah
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.
It is Dougal's remaster script, which I did modify a little so the wireless would work.

vattery 0.6.2

Posted: Tue 20 Jul 2010, 17:03
by ecube
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.

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"
:D
ecube

Posted: Wed 21 Jul 2010, 04:37
by rjbrewer
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.

Posted: Sat 24 Jul 2010, 14:45
by Lobster
In case your Fluppy notebook gets liberated
http://adeona.cs.washington.edu/

Traces your laptop - might be nice for Fluppy 8)

Loading drivers needed to access disk drivers.....Solved!?

Posted: Sun 25 Jul 2010, 17:33
by ecube
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

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