Fluppy 013

For talk and support relating specifically to Puppy derivatives
Message
Author
Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#91 Post by Roy »

jemimah,

Still no joy. 'iwconfig' shows wlan0, 'ifconfig wlan0 up' shows 'ifconfig: SIOCSIFFLAGS: No such file or directory'

But I want you to help me check something else....

There was a Puppy distro (past-tense) that always failed to unzip the broadcom firmware... where would I look to make sure this is not happening here?

-Roy

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#92 Post by jemimah »

Tried with both the windows and the linux installer and I can't reproduce it. I wonder what you are doing differently than what I do.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#93 Post by Roy »

No idea, jemimah. Never had this happen before. I'm actually in front of two machines ATM; one running XP and the other running Mint 9. The Fluppy stick and my external hard disc drive are the only things that are mine... so my troubleshooting is limited.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#94 Post by Roy »

Okay, I rebooted without my save file, renamed my save file so that it would not be recognized as such, and rebooted again...

Boot error

Back to the XP machine to rebuild the boot record... again.

Back to the netbook and rebooted. Created new save file. Rebooted. Put b43.tar.gz into /lib/modules/all-firmware/ and rebooted. Checked /lib/firmware/ directory to see if the firmware was being extracted.... nope.

Used my bcm43xx-firmware.pet to put the extracted firmware into that directory (maybe an earlier -- too early? -- version) and rebooted again.

Pwireless2 still shows zero access points and I'm still getting the 'ifconfig:SIOCSFIFFLAGS : no such file or directory'

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#95 Post by jemimah »

Can you try creating a bootable drive using BootFlash on Puppy and see if you still have the same problem creating files?

Use Bootflash to format a blank drive - say no when it asks if you want to install Puppy. Then copy the Fluppy files to the new drive. But don't copy the ldlinux.sys file - leave the one that Bootflash creates untouched.

Also, can you send me the output of dmesg?

User avatar
Timmi
Posts: 27
Joined: Fri 23 Oct 2009, 06:04

#96 Post by Timmi »

eeePC 900SD
Would not allow to add a profile for a hidden SSID on wifi.
Pretty slow on this machine (celeron 800MH, 512MB, 8GB SSD) - I guess this is as stated, better for Atom or better.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#97 Post by Roy »

Here is what I've been working with....

Your Broadcom firmware in /modules/....
Your Broadcom firmware manually extracted to /firmware/ (creates directory)
My Broadcom firmware .pet installed (puts broadcom firmware in /firmware/ without additional directory and adds microcode)

Sleep value in rc.d whatever adjusted to 10, then 100, then 400....

dmesg.txt sent via EMAIL (problems trying to attach)

-Roy

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#98 Post by jemimah »

Timmi wrote:eeePC 900SD
Would not allow to add a profile for a hidden SSID on wifi.
Pretty slow on this machine (celeron 800MH, 512MB, 8GB SSD) - I guess this is as stated, better for Atom or better.
Yeah it's going to be slow compared to Puppeee (especially booting, but I expect it should run ok) - it's amazing what a custom kernel buys you!

The hidden SSID thing is a bug in the RT2860 driver. Does work in Puppeee? I use the manufacturer's driver there - might be less buggy - I haven't got a lot of feedback either way.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#99 Post by Roy »

Used Igulder's pup-432-2.6.25.16.iso to use BootFlash; exited process upon being asked for a Puppy image. Copied fluppy02.zip onto 4G thumb drive and opened extraction utility; removed ldlinux.sys file from file selection and extracted remaining files.

This is not a bootable disc

Placed thumb drive back into running linux environment and ran bootinst.sh; created bootins.bat

This is not a bootable disk

Put the thumb drive back into an XP environment and ran the Windows boot utility

Success!

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#100 Post by jemimah »

So bootflash doesn't work - something is awry.

Try running bootflash, but don't copy anything to the drive afterwards. When you try to boot it, you should get an error about not being able to find linux - but not an error about the drive not being bootable.

Then if that works, don't copy the zip file to the drive - extract the files somewhere else, then copy the files to the flash drive. Make sure to preserve the directory structure.

Also try a different usb drive and see if you get the same results.

Keep an eye on the ldlinux.sys file and make sure it doesn't disappear at any time during the process. This is not a regular file - if it gets moved or overwritten, it breaks.

TomRhymer
Posts: 95
Joined: Fri 18 Sep 2009, 05:06

#101 Post by TomRhymer »

jemimah wrote:Tried with both the windows and the linux installer and I can't reproduce it. I wonder what you are doing differently than what I do.

The problem does have something to do with the size of the drive. I just installed Fluppy to an 8GB flash drive and was able to reboot after saving without any problems. But I get the problem with 2 different 512MB drives. Just my luck that I have a stack of 512MB drives that I use for testing Puppies.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#102 Post by Roy »

jemimah,

We're close... drilling down to /lib/firmware/b43 in your previously attached firmware file and depositing that buried b43 directory in Fluppy's /lib/firmware/ directory provided me with 2 access points in Pwireless2.

Then I broke it by not inputing a requested SSID. What are testers for, right? Pwireless won't show me those access points a second time. I suspect that something is running in the background, but don't know where to look.

-Roy

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#103 Post by jemimah »

To reset Pwireless2, first delete any profiles in the profiles tab. Then go to the debug tab and hit the reset button.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#104 Post by Roy »

Okay, I think I've got it this time. I deleted my save file and started over....

It needs your provided b43.tar.gz in /lib/modules/all-firmware/ and the unzipped b43 directory that contains all the actual firmware in /lib/firmware/.

I believe the /lib/modules/all-firmware/b43.tar.gz is supposed to unzip itself and copy into /lib/firmware/ by itself upon booting, but I'm not taking anything for granted just yet.

With your provided directories placed in those two places, Pwireless2 is giving me 5 different access points to choose from ATM.

Now, let's see if I can break it while trying to connect..... yep. I broke it. Deleted a duplicate profile. Selecting 'Refresh' under Debug tab of Pwireless2... doesn't seem to do anything. wpa-state=INACTIVE Selecting 'Reset Wpa_supplicant' appears to restart eth0 and wlan0, but wpa_state=INACTIVE in Debug tab and no access points appear in the Networks tab. 'Refresh' under Networks tab does nothing.

Reboot. Pwireless2 show zero access points. 'Refresh'...nothing. 'Reset'...nothing. 'Refresh'...nothing.

Ctrl-Alt-Backspace... zero access points.

Reboot... zero access points.

Jemimah, are you sure you want ME testing this?

-Roy

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#105 Post by Roy »

/lib/modules/all-firmware/b43.tar.gz does not automatically unzip and install /b43 into /lib/firmware/. This must be done manually by the user.

I still can't get wireless access points to return (and there is one 20 feet away), even with the second save file. Something must be running in the background that I can't stop (or auto starting on each subsequent boot).

-Roy

current dmesg output:

Code: Select all

lp: driver loaded but no devices found
b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#106 Post by jemimah »

I will add CONFIG_B43_FORCE_PIO to the next kernel and see if that will fix it.

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#107 Post by Roy »

Thanks!

Looking forward to trying it.

-Roy

JustGreg
Posts: 782
Joined: Tue 24 May 2005, 10:55
Location: Connecticut USA

#108 Post by JustGreg »

I have an Intel Classmate with a 800 by 480 (7 inch) screen, Celeron 900 MHz processor, 512 Mbytes of ram and 2 Gbyte USB flash drive. Fluppy install correctly and runs. I did find the battery monitor did not work correctly. It detected the use of AC power, but, did not show the correct battery condition. The monitor has the battery discharged at all times and not charging. I also tried Lucid Puppy 5.0 and the battery monitor with Lucid worked correctly. The battery was charging properly.

I do not think the issue of the Classmate and battery monitor is a major one and needs to be fixed. In case of the Classmate and its small keyboard, I can only use it for a limited period before I give up typing and go to hunt and peck. This post is to tell how Fluppy works on different hardware.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#109 Post by jemimah »

Out of curiousity what are the contents of /proc/acpi/battery/BAT0/state?

There is a script in /root/Startup that decides whether to run vattery or vattery-old-version. Vattery-old-version works in some cases where the battery reports unexpected things, so you could try running it and see if that fixes it and I can adjust the script if it works.

JustGreg
Posts: 782
Joined: Tue 24 May 2005, 10:55
Location: Connecticut USA

#110 Post by JustGreg »

I checked /proc/acpi/battery/BAT0/state and found there is no BAT0 directory. However, there is a BAT1 directory with all the information. So the problem is the Vattery is looking in wrong directory. Will the vattery-old look at the correct directory?

Yes, I have tried both vattery an vattery-old-version in console terminal window. The vattery-old-version fails with an error saying no BAT0 directory. The vattery program just reports the battery is discharge due to the lack of the information. This is a ClassMate specific issue to me since everything else has BAT0.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

Post Reply