Upup Precise 5.3.3.3 with kernel 3.3.2

[musher0]

You just need to install tzdata package with PPM and you get full time zone data.

I see. Thanks.

[James C]

Been primarily splitting time today between Precise 5.3.3.1 and the latest and greatest Slacko release......other than the expected early little problems it's looking really solid........Particularly since this is an early test build.
Excellent work as usual.

[Volhout]

Pesamu,

Thanks for all your effort. But it didn't work. Dmesg still only informs is see the USB device, but does not load any drivers for it. Also lsmod does not indicate any drivers loaded. When I try a modules with different chip (Realtek) I see both lsmod as dmesg indicate what it is doing.
It seems the USB ID is not "linked" to the Broadcom driver.
And I have no idea if that can be forced manually.

Regards,

Volhout

P.S. is this driver PET very specific for UPUP 5.3.3, or can it be used with other kernels also ?

[pemasu]

Volhout. Could you post lspci -nn findings concerning your wireless chip. I need to check what it tells.

The support for your broadcom usb chip is new.

The pet I provided has just the supposed needed firmwares. You can try them in other Puppy which has that brcm* drivers included. There wasnt any kernel driver module included.

What we test now is brand new testing...

[Volhout]

Hi Pesamu,

lspci missed some libs in 5.3.3. I used a different puppy (Slacko) to try the lspci, and it did not list the module. But "lsusb" did.....

• # lsusb
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 0a5c:bd17 Broadcom Corp.
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

These id's are the same as in the listing I did post earlier from dmesg.
I'll see if I can find a puppy that already has these (but older) drivers. Maybe Slacko has (3.2.7 kernel).

Volhout

Verbose list:

Code: Select all

Bus 001 Device 002: ID 0a5c:bd17 Broadcom Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0a5c Broadcom Corp.
  idProduct          0xbd17 
  bcdDevice            0.01
  iManufacturer           1 Broadcom
  iProduct                2 Remote Download Wireless Adapter
  iSerial                 3 000000000001
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           46
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              200mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      2 
      bInterfaceProtocol    255 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               4
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Connection timed out
Device Status:     0x0000
  (Bus Powered)

[pemasu]

Volhout. I checked the information once more. I am not sure that the kernel module brcmfmac.ko is still ready to support usb modules. There isnt in .config specs option for usb modules, there is sdio module option only.

Even though there is already firmware available...it can be that the brcmfmac.ko supports those 2 usb chips in the future. I cant do much more atm.

Jim1911. I checked the firmware.dep file and it seems I have missed the dependency for iwlwifi.ko module.

Here is the updated firmware.dep file. Just install the pet. And maybe reboot....or just try once again with rmmod iwlwifi and modprobe iwlwifi.

Also...brcmsmac.ko support has been nowadays linked to broadcom spesific amba. If I would enable it...the broadcom ssb dependent modules will be dropped out. Oh well....there isnt justice in this world. I am thinking to revert back to 3.2.14 kernel. Mavrothal would be happy with this decision....lol..

[vtpup]

Just loaded 5.3.3.1 -- sound works, wifi works -- both seem to require puppies with 3.x kernels (so far tested) on this new machine.

key assignments (screen brightness keys, volume and mute keys, etc, still don't work.

In Racy 5.3 (by comparison), brightness keys do work (though reversed). Volume does not.

In case of any use, below is a snip from /tmp/xerrs.log:

Code: Select all

FATAL: Module fbcon not found.
ls: cannot access /root/.pup_event: No such file or directory
/usr/bin/jwm
/usr/sbin/quicksetup: line 740:  9954 Terminated              yaf-splash -bg orange -fg black -placement center -close never -fontsize large -icon /usr/share/doc/puppylogo96.png -text "$WELCOMEMSG"
/usr/sbin/delayedrun: line 185: welcome1stboot: command not found
Playing Sparc Audio '/usr/share/audio/2barks.au' : Mu-Law, Rate 8000 Hz, Mono
/usr/bin/acpitool
  AC adapter     : off-line 
+ gtkdialog-splash -timeout 3 -placement top -bg lightblue -text 'Switching to Performance Mode'
EXIT="Exit on timeout"
++ cat /etc/acpi/performance-brightness
+ BRIGHT=10
+ echo 10
++ tr -d :
++ tail -n 1
++ cut -f3 '-d '

[pemasu]

vtpup. Nothing serious in those messages.

[vtpup]

Pemasu, I've tried your combo xkeybindings, vattery etc .pets in this machine with various other puppies (looks like it's incorporated in this one) and the machine is unresponsive to it. Continues to ignore the bindings.

battery display is okay in UP5331 as is proc and speaker in the bar, so those portions do seem to work.

Do you have a default set of key bindings in this puppy, or are they all to be added by the user?

[pemasu]

I have compiled now the latest xbindkeys in upup precise. Lets see if it helps you.

Yeah...there is the old default set. You see them by running from the menu xbindkeys-config. I havent given much thought yet for finetuning.

You can remove existing keybindings and create them again with your wanted commands with xbindkeys-config

[musher0]

Pemasu, I've tried your combo xkeybindings, vattery etc .pets in this machine with various other puppies (looks like it's incorporated in this one) and the machine is unresponsive to it. Continues to ignore the bindings.

(...)

Hello, vtpup.

On the subject of xbindkeys, I have two experiences to share:

xbindkeys provide a low-level binding with the keyboard keys.
You can have interference from a superior level, like

from the key shortcuts you can set up with the ROX-Filer.

For example, if you have set Ctrl-A in xbindkeys to lauch
abiword and in ROX you have set Ctrl-A to launch Alsa-config,
the ROX shortcut will have precedence. Alsa-config will be launched, not abiword.

or

from the window manager, which has absolute precedence over all keybindings.
For example, jwm or icewm will steal any keybinding involving a mouse click. In other words, if you have a key binding in xbindkeys such as Ctrl+A+leftmouse click = abiword, it will be inoperative in jwm or icewm because any desktop click is transmitted to them, not to the xbindkeys program.

So, when you prepare the key conbinations in xbindkeys, make sure that
you do not have a mouse-click reference (which is handled by the window manager) and
that the key shortcut is unique (that the same shortcut does not exist in ROX-Filer).

I hope this helps your understanding of xbindkeys.

BFN.

Note. Icewm can be made NOT to control the background clicks iun the preferences file. Oroborus does not control any background click. Aewm and Echinus, only the left-mouse click (if I remember correctly). In short, you have to test with the window manager you are using.

[musher0]

Addendum:
here is another consideration. Most programs (opera, geany, ROX, for example) reserve control of the mouse right-click for their own context operations. So generally, its of no use to try to configure the mouse right-click in xbindkeys.

[musher0]

@pemasu.

Would you know if the kernel for Upup-Precise has been compiled to read / accept sfs files compacted with the latest gz (with lzma / xz)?

There is supposed to be a 25 % gain of space if the sfs is compacted with the recent xz.

I ask because I tried recompacting the Precise sfs file with a recent xz enabled sfs-utility. The space saving promise seems to be true, but I got a "kernel panic - not syncing" message at reboot.

Of course, "kernel panic" messages can be triggered by many causes, but I would like to eliminate this possibility.

Thanks in advance. Regards.

[pemasu]

CONFIG_SQUASHFS_ZLIB=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y

I do think that you cant just compress main sfs and get it working. I have done the xz compression always with woof.

For fun of it I could build one experimental build with xz compression,

I do have tough time to get transmission to really download torrents.

When I try to download for example this:
http://torrent.ubuntu.com/edubuntu/rele ... so.torrent

I get this in console:
# transmission
** Message: Couldn't read "http://torrent.ubuntu.com/edubuntu/rele ... so.torrent": Operation not supported

I have tried to get understanding of underlying problem with no cure yet.

This is with build without libssl-0.98....just symlinks.

I have compiled transmission several times and it compiles easily and I have tried to throw everything possible needed in to os without cure....

[pemasu]

I suppose you first unsquashed the sfs and the resquashed it with
mksquashfs source nameof.sfs -comp xz

Have you tested also if just unsquashing and then resquashing with default gzip compression boots.
I had once problem with the name of my sfs. Barrys code didnt like too many letters in it. Numbers in version should be ok, it should support as long versioning as you want.

Of course dont change the default version numbering or naming...it surely fails.

[oui]

resquashing is no problem

but I don t find the traditional directory Desktop of the old Puppy s

[Jim1911]

Jim1911. I checked the firmware.dep file and it seems I have missed the dependency for iwlwifi.ko module.

Here is the updated firmware.dep file. Just install the pet. And maybe reboot....or just try once again with rmmod iwlwifi and modprobe iwlwifi.

Also...brcmsmac.ko support has been nowadays linked to broadcom spesific amba. If I would enable it...the broadcom ssb dependent modules will be dropped out. Oh well....there isnt justice in this world. I am thinking to revert back to 3.2.14 kernel. Mavrothal would be happy with this decision....lol..

New firmware worked. Now online using it. Upup Precise is already looking good. I hope that you will stick with the newer kernel.

However, I am not able to connect to my wifi network printer.

Cheers,
Jim

[pemasu]

You need to copy for example from slacko snmp file to cups backend folder:
/usr/lib/cups/backend/snmp

I am not sure if that is enough to get network printing working.

Great to hear that the firmware worked. I suppose you mean firmware file...not the firmware.dep file with iwlwifi.ko definition. Or when I read above again you meant the updated firmware.dep....time to get sleep...lol.

I will include that firmware.dep and also the updated iwlwifi firmwares to the build.

Older Transmission works fine with libssl-0.9.8.

I will include it still with older libssl + newer libssl to the next version until I learn to compile transmission in upup precise.

I suppose I will upload the next version tomorrow. It does not contain yet anything dramatic. I have fixed the devx sfs stuff by test compiling some apps.

[oui]

sorry

no way to print actually!

[sszindian]

In a previous test I posted in this thread, I was commenting about how good that videos played with Precise... let me clarify that a little...

'IF' you use one of the chrome-type browsers that will be TRUE! (I happen to be using 'Iron-18-Lucid.pet' that can be obtained from the lucid ibiblio repository.) It works very nice and no dependencies are required for install.

'IF' you use Seamonky (the default browser that currently comes with Precise)some of the places you visit for videos will really give you a very un-happy experience and you'll probable blame Precise!

So... before jumping to conclusions about a particular distro... Remember...Browsers make a world of difference!!!!

>>>---Indian------>