Slacko 5.3.3-RC2 (5.3.2.4[0])

[grump]

...
_______________________________________________________
ALL b43 (broadcom wireless) users, I need reports. ON FAILURE I need kernel logs from a pfix=ram before you load up b43!

• /tmp/udevtrace.log,
  /var/log/messages
  /lib/modules/3.1.9-slacko_4g/modules.alias
  device ID (run lspci -nn|grep -iE wireless)
  output from lsmod

_______________________________________________________

Ok, let's see if this is ok:

The lappy is a HP Mini 2140 2gb RAM 160Gb hdd booting this shiny new Slacko from a usb stick.

The b43 module loads - not first off - have to load the module in the network wizard - and an new interface wlan0 shows up. However, it looks like the interface wont wake up. The wireless is turned on and off with a toggle switch on the front - slide to turn on, slide again to turn off. I can't tell what state the switch is in. In Windows the status light changes from orange to blue.

Hope this helps. I like the look of this pup thank you!. Using it on this ols Toshiba A200 no probs.

[majorfoo]

Hmmm... got this new pretty little pink box that pops up (first thing on the desktop) that says... ERROR: Your module doesn't work. Run "sensors-detect"

I did what it asked but no new modules were found for it to config. ?

Also got this with the last two versions of EXPRIMO.

Never seen this turkey before???

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

I had same thing when I booted 5.3.1.3.
Found culprit to be in startup menu, item is tempicon.sh which starts the cpu temp in tray on some BUT not all machines. Mine is one of those where tempicon does not work nor does cpu-temp. Something to do with my hardware.

I simply deleted tempicon.sh in startup menu and the pretty little box went bye bye.

majorfoo

[James C]

Hmmm... got this new pretty little pink box that pops up (first thing on the desktop) that says... ERROR: Your module doesn't work. Run "sensors-detect"

I did what it asked but no new modules were found for it to config. ?

Also got this with the last two versions of EXPRIMO.

Never seen this turkey before???

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

I had same thing when I booted 5.3.1.3.
Found culprit to be in startup menu, item is tempicon.sh which starts the cpu temp in tray on some BUT not all machines. Mine is one of those where tempicon does not work nor does cpu-temp. Something to do with my hardware.

I simply deleted tempicon.sh in startup menu and the pretty little box went bye bye.

majorfoo

I just tried to ignore it in hopes it would just go away......

[James C]

Assembled another box out of spare parts, so Slacko 5.3.1.2 (k-3.19) live pfix=ram.Display,sound and internet all working and correct on initial boot.
Tried Lucid and Exprimo first....both booted to a distorted,unusable display using "nv".No problem with "nouveau" though.

# report-video
VIDEO REPORT: Slacko Puppy, version 5.3.1.2

Chip description:
oem: NVIDIA
product: MCP67 - mcp68-01 Chip Rev

Driver used by Xorg:
vesa

Video mode used by Xorg:
Resolution: "1024x768" Depth: Depth 24

...the above also recorded in /tmp/report-video
#

Code: Select all

[   118.983] (--) NOUVEAU(0): Chipset: "NVIDIA NV67"
[   118.983] (**) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32

-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory : 903MB (161MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Mon 23 Jan 2012 09:21:52 PM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA NVidia

-Version-
Kernel : Linux 3.1.9-slacko_4g (i686)
Compiled : #1 SMP Mon Jan 16 02:17:47 EST 2012
C Library : GNU C Library version 2.13 (stable)
Default C Compiler : Unknown
Distribution : Unknown distribution

Audio device : nVidia Corporation MCP67 High Definition Audio
VGA compatible controller : nVidia Corporation C68 [GeForce 7050 PV / nForce 630a]
Ethernet controller : nVidia Corporation MCP67 Ethernet

[James C]

Just for the heck of it, Slacko 5.3.1.3 live pfix=ram. Same results.... working well too.

-Version-
Kernel : Linux 3.1.10-slacko_4g (i686)
Compiled : #1 SMP Sun Jan 22 07:46:39 EST 2012

[sszindian]

majorfoo:
Thanks for that info on the pretty pink box!!!

James C:
That's a good one Have to remember that train of thought next time Mick throws something funny at us... for awhile I thought he might be pullin' our leg Come on... really... pretty 'pink boxes!'

Mick... you gotta cut back on that Kangaroo Juice

5.3.1.3 Very nice, working like a charm... please don't cut back to the 39 kernel, if anything, go for the new 3.3

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

[mavrothal]

Code: Select all

for x in $(udevadm trigger --dry-run --verbose); do udevadm info --query=all --path=$x; done > /root/udef_info.before     # or .after

will generate the udef_info.before (or .after) file in home.

Hi mavrothal

Here are the requested files...remove the .gz

peebee,
if you please type this in the terminal and reboot.

Code: Select all

echo SUBSYSTEM=="net", KERNEL=="wlan*", DRIVERS=="b43", NAME="wlan0" >> /etc/udev/rules.d/10-network.rules

If it does not work, type this and try again

Code: Select all

echo SUBSYSTEM=="net", KERNEL=="wlan*", DRIVERS=="b43", ATTR{address}=="00:21:00:c6:68:aa", NAME="wlan0" >> /etc/udev/rules.d/10-network.rules

[peebee]

peebee,
if you please type this in the terminal and reboot.

Code: Select all

echo SUBSYSTEM=="net", KERNEL=="wlan*", DRIVERS=="b43", NAME="wlan0" >> /etc/udev/rules.d/10-network.rules

If it does not work, type this and try again

Code: Select all

echo SUBSYSTEM=="net", KERNEL=="wlan*", DRIVERS=="b43", ATTR{address}=="00:21:00:c6:68:aa", NAME="wlan0" >> /etc/udev/rules.d/10-network.rules

Hi mavrothal

pfix=ram startup - applied the first rune - rebooted with savefile - no change, no b43 detected

applied 2nd rune - rebooted - still no change, no b43 detected.

In both cases checked that the line was in 10-network.rules

Let me know if there is anything else I can try or any other evidence I can provide for this perplexing problem...

Cheers
peebee

[mavrothal]

Let me know if there is anything else I can try or any other evidence I can provide for this perplexing problem...

Yes one more thing if you please, to make sure that the rules worked.
What is the output of

Code: Select all

dmesg | grep wlan

?

[BarryK]

Regarding b43 firmware not loading, I might have the fix;

http://bkhome.org/blog/?viewDetailed=02651

[peebee]

What is the output of

Code: Select all

dmesg | grep wlan

?

Hi mavrothal and 01micko

the output is null - there is no output

but Barry may have found the problem which seems to be a k2 dependency that needed to be fixed for k3 as I understand his blog.

Do we have to wait for a new puppy built with the latest woof to test his supposition or is there something we can do to test on slacko5.3.1.3??

Cheers
peebee (standing ready to test)

[pemasu]

That is one way. Another is to download latest woof2 commit. Pick up the updated rc.sysinit file. Make a pet and post it so that people can test it. Reboot is needed after installing the pet.

[peebee]

That is one way.

IT WORKS

Thanks Barry & Pemasu.....

The output of lsmod after pfix=ram boot, load pemasu's pet, reboot with savefile is attached and as can be seen b43 is once again being automagically loaded - great!

Cheers
peebee

[01micko]

m m m.. might be win-win ... I got 3.2.1 to compile .. off to my college orientation day today so maybe more tonight

[grump]

IT WORKS

Thanks Barry & Pemasu.....

It works for some - but not for me.

Downloaded the above pet (on my other Slacko lappy), copied into the HP Mini. (see my prev post) AFAIK the wireless switch was in the on state because it was on when in Windows before I restarted to Puppy. Ran the pet, restarted and found that the b43 was loaded. However, when running the network wizard and trying to scan for wireless the msgbox says:

Failed to raise interface wlan0.
failed command was: ifconfig wlan0 up
Error returned was:
ifconfig: SIOCIFFLAGS: No such file or directory

I'll get back to this later today.

[Keef]

01micko

5.3.1.2 boots without problem on the Compaq. (Intel P3 450)

5.3.1.3 did actually boot on the Athlon, (Mobile Athlon XP-M 2800) but there are display problems.

[BarryK]

That is one way. Another is to download latest woof2 commit. Pick up the updated rc.sysinit file. Make a pet and post it so that people can test it. Reboot is needed after installing the pet.

You don't have to download all of Woof, Fossil allows you to download individual files. You have to login as anonymous, click on 'Files' in menu, locate the file, then click 'Download'. Simple!

[James C]

Just for the record, i got my Athlon going, 5.3..1.2 is fine, 5.3.1.3 no go. Smae as other Athlon users' reports, hangs at blinking cursor.

Just for the record, Aptosid (k-3.1.6) will not boot on my Athlon XP box either....darn bfs......

[01micko]

bfs certainly gave me a bf!

-

I use "fossil update" then make a new woof tree. Only downloads a few k (latest commits since last run, and you get the commit message ). Seems to work ok. I guess that's how it's supposed to be used, though I'm a dummy when it comes to version control systems!

[mavrothal]

Ran the pet, restarted and found that the b43 was loaded. However, when running the network wizard and trying to scan for wireless the msgbox says:

Failed to raise interface wlan0.
failed command was: ifconfig wlan0 up
Error returned was:
ifconfig: SIOCIFFLAGS: No such file or directory

I'll get back to this later today.

If you run "dmesg | grep b43" in the terminal you may see why.
Most likely does not have the proper firmware for your chip.
(still did not managed to get/extract the proper firmware for my iMac )