Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 26 Nov 2014, 16:34
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
slacko-5.6 Final - plus testing next
Moderators: Flash, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 6 of 31 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 29, 30, 31 Next
Author Message
tlchost

Joined: 05 Aug 2007
Posts: 1738
Location: Baltimore, Maryland USA

PostPosted: Thu 11 Jul 2013, 11:02    Post_subject: Wireless Problem  

Acer One Netbook Model D255E
Atom Processor

USB Bootable

Upup shows this unit as having broadecom 4313 chip.

Not recognized by any of the network wizards....any hints?

Thanks
Back to top
View user's profile Send_private_message Visit_website 
anikin

Joined: 10 May 2012
Posts: 526

PostPosted: Thu 11 Jul 2013, 13:10    Post_subject:  

Quote:
Next version will have k3.4.5x (similar to 5.5) so hopefully will work.

Hi 01micko,
This one is the fastest, coolest and smoothest of all the Slackos I've tested on my eeepc (Intel atom n270/945GSE). It even feels faster than ThinSlacko. With every release, these new 3.x.x.x kernels are getting friendlier to atom processors. I'm frustrated by your decision to downgrade the kernel. And it's surprising that you have already made up your mind at this very early stage, when the testing has barely started. Really frustrated and disappointed. No peace in the valley ... deep sigh.
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1519
Location: Worcestershire, UK

PostPosted: Thu 11 Jul 2013, 13:21    Post_subject: Re: Wireless Problem  

tlchost wrote:
Acer One Netbook Model D255E
Atom Processor

USB Bootable

Upup shows this unit as having broadecom 4313 chip.

Not recognized by any of the network wizards....any hints?

Thanks


Suggest post output of:
Code:
lspci -vnn -d 14e4:


visit:
http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices

Slacko-5.6 alpha does not currently contain the wl.ko driver so if your chip needs this it isn't currently supported Sad

look in output from dmesg to see which driver is being used and if any problems are being reported.

Cheers
peebee

_________________
LxPup-14.10 = Puppy + LXDE
Back to top
View user's profile Send_private_message Visit_website 
pemasu


Joined: 08 Jul 2009
Posts: 5465
Location: Finland

PostPosted: Thu 11 Jul 2013, 13:39    Post_subject:  

Peebee. You could try these patches with 3.10 kernel. Use unpatched source.
wl-patches-0.0.1.tar.gz
Description 
gz

 Download 
Filename  wl-patches-0.0.1.tar.gz 
Filesize  3.84 KB 
Downloaded  144 Time(s) 
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1519
Location: Worcestershire, UK

PostPosted: Thu 11 Jul 2013, 16:27    Post_subject:  

pemasu wrote:
Peebee. You could try these patches with 3.10 kernel. Use unpatched source.


Thanks pemasu

Applied your patches plus the "wlan" patch and compiled successfully - resulting pet available here

tlchost - if you need the wl driver, load the pet and then reboot.

you may also need to unblock your wifi:
Code:
rfkill unblock wlan
and put this into rc.local for persistence.

cheers
peebee

_________________
LxPup-14.10 = Puppy + LXDE
Back to top
View user's profile Send_private_message Visit_website 
01micko


Joined: 11 Oct 2008
Posts: 7841
Location: qld

PostPosted: Thu 11 Jul 2013, 16:48    Post_subject:  

01micko on the first page wrote:
Vision

OK, alpha has been out some days now and the bugs are turning up. On to that.

The immediate plan is to compile 3.4.52 with devtmpfs and f2fs support. I'll add my f2fs usb stick program, and also write up a FULL install to f2fs-usb program. This will take full advantage of f2fs usage of nand storage. After all, whacking an ext filesystem in a save file on top of f2fs probably nulifies any advantage gained by using f2fs. For a FRUGAL type situation, we need to develop f2fs SAVE files. That's down the track. The big advantage of this will be that writes will not have to be restricted so USB installs so using AUFS will act like pupmode=12 installs (on a fast hard drive).

So why the trouble? I believe puppy's niche is USB installs. I use them extensively. Currently, the system of caching everything in RAM until a set interval (default 30 minutes) and saving back to the save file has it's limitations.
  • The 'snapmerge' (as it is known) can take up to several minutes and the system cops a substantial performance penalty.
  • Using FAT filesystems (and NTFS for that matter) is not Linux friendly as those FS do not respect UNIX permissions
  • RAM can fill up in that 30 minute period and cause RAM crash, then everything in that period is lost. Sure, that could be monitored but the systems that suffer these problems (old ones) then cop another performance penalty by adding another daemon.
This configuration is known as "pupmode=13". I don't particularly like it and I think kirk and jamesbond dumped that method in FatDog (confirmation of that please?).

***************************

I will stick with k3.10 series for the high end (PAE) version. I will wait until 3.10.1 before compiling. With the newer kernels though and an older lib base (slackware-14.0's base is approaching 12 months old, that is ancient in Linux Years) we run the risk of poor driver support in the graphics stack. A few kernel devs are also Xorg devs (Alan Cox comes to mind) so the kernel and Xorg are undergoing some parallel developments.

So there you have it, my rough plan.

Mick

--------------------------------------------------------------------------------

Woohoo! I got the f2fs patches to work cleanly and compile in k3.4.52.

Below are the patches for safe keeping.

NOTE: there is an alteration from standard to accomodate AUFS in kconfig and Makefile.


anikin wrote:
Hi 01micko,
This one is the fastest, coolest and smoothest of all the Slackos I've tested on my eeepc (Intel atom n270/945GSE). It even feels faster than ThinSlacko. With every release, these new 3.x.x.x kernels are getting friendlier to atom processors. I'm frustrated by your decision to downgrade the kernel. And it's surprising that you have already made up your mind at this very early stage, when the testing has barely started. Really frustrated and disappointed. No peace in the valley ... deep sigh.

Now pick up those heads and shoulders.

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send_private_message Visit_website 
Billtoo


Joined: 07 Apr 2009
Posts: 2156
Location: Ontario Canada

PostPosted: Thu 11 Jul 2013, 19:05    Post_subject: slacko-5.6 alpha
Sub_title: next release
 

When will the next release be coming?
I'm eager to take it for a spin Smile
Back to top
View user's profile Send_private_message 
01micko


Joined: 11 Oct 2008
Posts: 7841
Location: qld

PostPosted: Thu 11 Jul 2013, 19:18    Post_subject:  

Hey Billtoo

Not quite sure. It will be "soon" Laughing . I am trying to get f2fs booting from a usb stick as a FULL install, then I have to write it up as a script to automate it. It requires a full install with an initrd because no bootloader recognises f2fs just yet. I'm trail blazing here! The init script in Slackware is very simple and an adaptation of that should do the job. It's is a requirement of a puppy full install that the "initrd" is gone when the main filesystem is mounted. Slackware's initrd does just that. Smile

All that said, I might even release the next "alpha" without that functionality, as everything else is in place. Also, I'm sweating on k3.10.1 for the high end version. Greg Kroah-Hartman just released the patch set so it might be a day or 3 before we see it. Can't see anything in those patches that fixes Broadcom wireless, however, that bug could have been caused by the bad permissions which are fixed in my next release.

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send_private_message Visit_website 
tlchost

Joined: 05 Aug 2007
Posts: 1738
Location: Baltimore, Maryland USA

PostPosted: Thu 11 Jul 2013, 21:02    Post_subject:  

peebee wrote:

tlchost - if you need the wl driver, load the pet and then reboot.

you may also need to unblock your wifi:
Code:
rfkill unblock wlan
and put this into rc.local for persistence.



Did that...still no device detected by any of the network wizards. Here's
what lsusb reports after the above:

Code:

02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
   Subsystem: Broadcom Corporation Device [14e4:0510]
   Flags: bus master, fast devsel, latency 0, IRQ 17
   Memory at 56000000 (64-bit, non-prefetchable) [size=16K]
   Capabilities: [40] Power Management version 3
   Capabilities: [58] Vendor Specific Information: Len=78 <?>
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
   Capabilities: [d0] Express Endpoint, MSI 00
   Capabilities: [100] Advanced Error Reporting
   Capabilities: [13c] Virtual Channel
   Capabilities: [160] Device Serial Number 00-00-4e-ff-ff-97-90-00
   Capabilities: [16c] Power Budgeting <?>
   Kernel driver in use: bcma-pci-bridge
Back to top
View user's profile Send_private_message Visit_website 
irishrm


Joined: 14 Mar 2009
Posts: 223

PostPosted: Thu 11 Jul 2013, 21:51    Post_subject:  

peebee:

Just to let you know your wl driver pet worked for me.

irishrm.
Back to top
View user's profile Send_private_message 
for_wov


Joined: 10 May 2013
Posts: 25
Location: Europe:Kiev

PostPosted: Fri 12 Jul 2013, 01:21    Post_subject:  

tlchost wrote:
peebee wrote:

tlchost - if you need the wl driver, load the pet and then reboot.
you may also need to unblock your wifi:
Code:
rfkill unblock wlan
and put this into rc.local for persistence.
the key words in peebee's reply were IF YOU NEAD but you don't. just blacklist b43 module through menu=>system=>bootmanager and reboot (if in full installation). I wasn't trying to get wify(brcsmac) to work in live or remaster (may try to change /etc/rc.d/PUPSTATE from 5 to 2 than launch bootmanager and blacklist b43 but still you nead to reboot)
Back to top
View user's profile Send_private_message 
01micko


Joined: 11 Oct 2008
Posts: 7841
Location: qld

PostPosted: Fri 12 Jul 2013, 02:03    Post_subject:  

Got the f2fs thing working, with some issues, but that's why I want to get it out there.

Attached is the initrd skeleton. (mainly for safe keeping).

Yes, it's a full USB stick install with an inird.gz. Anyone who knows about booting please take a look.

EDIT: Barry is going to take it from here now, so that's cool. Hopefully I'll get a release out late tonight.
initrd-skel-0.1.tar.bz2
Description 
bz2

 Download 
Filename  initrd-skel-0.1.tar.bz2 
Filesize  7.66 KB 
Downloaded  143 Time(s) 

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send_private_message Visit_website 
DaveS


Joined: 09 Oct 2008
Posts: 3726
Location: UK

PostPosted: Fri 12 Jul 2013, 02:44    Post_subject:  

Full USB install? Def my kind of thing. No clue how to do it though Smile
_________________
Spup Frugal HD and USB
Root forever!
Back to top
View user's profile Send_private_message 
tlchost

Joined: 05 Aug 2007
Posts: 1738
Location: Baltimore, Maryland USA

PostPosted: Fri 12 Jul 2013, 04:03    Post_subject:  

for_wov wrote:
but you don't. just blacklist b43 module through menu=>system=>bootmanager and reboot (if in full installation).


I never said I had a full installation, I said bootable USB

In any event boot manager reports that I do NOT have the .pci driver for the broadcom....so. it may be beyond my understanding on how to blacklist what I don't have.

Thanks for the reply
Back to top
View user's profile Send_private_message Visit_website 
for_wov


Joined: 10 May 2013
Posts: 25
Location: Europe:Kiev

PostPosted: Fri 12 Jul 2013, 05:52    Post_subject:  

tlchost wrote:
I said bootable USB
no matter. you NEAD a save file (was trying to establish network with pfix=ram -- no results so far) there are 2 major versions of drivers for brcm4313(i have the same) b43 & bcma which conflict each other. so only 1 should stay (bcma in our case) suppose rervin's logic is a bit incorrect. The only solution so far is to make a save, blacklist b43 and reboot (rechecked twice - works). on previous slackos(wlan was present) launched network wizard(Bary) refused from wl than started simple network setup or frisbee and worked.

Full installation failed (permissions on console or smth like that). I copied vmlinuz to boot directory on hdd than made full installation by puppy universal installer from flugal on usbflash(as usually). copied devx through
Code:
cp -a --remove-destination . /PATH_TO_MY_MOUNTED_SDA_PARTITION
folder /usr/share/pkgconfig didn't copy because same folder on main sfs is a symlink to /usr/lib/pkgconfig supposed that should work later (manually copied). booted from usb established wify in frugal first replied to tlchost and after rebooted to full on hdd but problem with console permissions occured. any ideas how to solve

PS:suppose full works. what is the easiest way to upgrade slacko 5.5 to current without reformatting (no practical skills on deltas (they are for iso i suppose) system on hdd.
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 6 of 31 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 29, 30, 31 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1129s ][ Queries: 12 (0.0112s) ][ GZIP on ]