slacko-5.6 Final - plus testing next

[tlchost]

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

[anikin]

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.

[peebee]

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: Select all

lspci -vnn -d 14e4:

visit:
http://wireless.kernel.org/en/users/Dri ... ed_devices

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

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

Cheers
peebee

[pemasu]

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

[peebee]

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: Select all

rfkill unblock wlan

and put this into rc.local for persistence.

cheers
peebee

[01micko]

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.

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.

[Billtoo]

When will the next release be coming?
I'm eager to take it for a spin

[01micko]

Hey Billtoo

Not quite sure. It will be "soon" . 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.

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.

[tlchost]

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

you may also need to unblock your wifi:

Code: Select all

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: Select all

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

[irishrm]

peebee:

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

irishrm.

[for_wov]

tlchost - if you need the wl driver, load the pet and then reboot.
you may also need to unblock your wifi:

Code: Select all

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)

[01micko]

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.

[DaveS]

Full USB install? Def my kind of thing. No clue how to do it though

[tlchost]

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

[for_wov]

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: Select all

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.

[tlchost]

I said bootable USB

no matter. you NEAD a save file

I have a save file....so let's dispense with that as a problem.

Appreciate your suggestions....not being overly technical, a lot of this
is over my head.

Thanks anyway

[SFR]

A couple of new/old little bugs.

1. Trash again: http://www.murga-linux.com/puppy/viewto ... 099#713099

2. Xlock:

-/+grabserver
The grabserver option causes xlock to grab the server. This is not usually needed but some unsecure X servers can be defeated without this.

In case if "our" server is secure enough, would be nice to delete all (2) occurences of "-grabserver" from /usr/local/apps/Xlock/AppRun, because when this parameter exists and a composite manager is in use (Compiz/xcompmgr), xlock won't display screensaver nor password prompt.
(originally found in here some time ago)

Greetings!

[for_wov]

in full (manually installed) errors on boot: intit:can't log to /dev/tty5
starting pid 44, tty ' ': '/etc/rc.d/rc.sysinit '
/etc/rc.d/sysinit:line 170: can't create /dev/console: Read-only filesystem

?

[for_wov]

will svn work in the next release or maybe smth is wrong with my current slacko(have frugal & full on the same partition/work form frugal)

Code: Select all

svn checkout http://qtalk-ui.googlecode.com/svn/trunk/
svn: E155000: '/root/trunk' is already a working copy for a different URL

it the problem in svn as locall app or that is remote site problems? same things on different sites.

[01micko]

@for_wov

There is a lot of permissions problems in the current version because of woof bugs. Maybe the SVN one is related? I didn't test. I can say with confidence that a new test version will be out within 12 hrs with many many bugs fixed. It's a kernel rollback but there are always 2 versions of slacko so with a little patience a newer kernel version will be released too.

@SFR.. in saying "many many bugs fixed".. I'm leaving the trash one for now since it's under discussion