LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 07-17-2012, 03:40 PM   #136
inph
LQ Newbie
 
Registered: Jul 2012
Posts: 9

Rep: Reputation: Disabled

Booted with udev_log="debug"

firmware failed to load on boot, following is /var/log/messages

# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
SIOCADDRT: No such process
# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
#

Failed to load firmware: http://pastie.org/4273577

Firmware loaded: http://pastie.org/4273602

Failure
Code:
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0'(err) 'libudev: main: error sending firmware 'e100/d102e_ucode.bin' to device'
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0'(err) 'libudev: set_loading: error: can not open '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0/loading''
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0' [2148] exit with return code 4
Successful
Code:
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0'(err) 'libudev: set_loading: '
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0'(err) 'error: can not open '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0/loading''
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0' [2187] exit with return code 0
return code 4 is consistent with the code in firmware.c

Code:
/*udev:extras/firmware/firmware.c*/
        util_strscpyl(datapath, sizeof(datapath), udev_get_sys_path(udev), devpath, "/data", NULL);
        if (!copy_firmware(udev, fwpath, datapath, statbuf.st_size)) {
                err(udev, "error sending firmware '%s' to device\n", firmware);
                set_loading(udev, loadpath, "-1");
                rc = 4;
                goto exit;
        };

Not being able to access /sys/.../loading doesn't seem to affect the outcome, but this is probably because the e100 module doesnt have /sys/.../loading capabilities.
Code:
'firmware --firmware=e100/d102e_ucode.bin --devpath=/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0'(err) 'libudev: set_loading: error: can not open '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:01.0/firmware/0000:01:01.0/loading''
Any pointers on where to go next? Short of hunting down changes between udev v165 and v175.

Edit: the band aid workaround is to add 10-20 lines of: /etc/rc.d/rc.inet1 eth0_start to rc.local to force the interface up and force the firmware to be loaded when the machine boots.

Last edited by inph; 07-17-2012 at 04:32 PM.
 
Old 07-17-2012, 07:43 PM   #137
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,281

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Quote:
what is the correct way to upgrade using slackpkg? I've attempting to upgraded three salckware-current systems. Two broke during upgrading, and I believe one was after the fixes.
I found that when doing the 'slackpkg update', 'slackpkg install-new', 'slackpkg upgrade-all' sequence, there is a problem after the gnutls package is upgraded as wget no longer works and all further packages are skipped. I needed to use 'lftp' to download the openssl package and the wget package, manually install those and then redo 'slackpkg upgrade-all' to complete the upgrade.

Last edited by allend; 07-17-2012 at 07:44 PM.
 
Old 07-17-2012, 07:56 PM   #138
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware
Posts: 14,868
Blog Entries: 2

Rep: Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805Reputation: 3805
This should already be fixed, but can also easily be avoided by configuring slackpkg to first download all the packages before installing them. Have a look at the DOWNLOAD_ALL option in your slackpkg.conf.
 
Old 07-17-2012, 08:38 PM   #139
Grischuna
Member
 
Registered: Mar 2009
Distribution: Slackware64 14.0 multilib
Posts: 39

Rep: Reputation: 0
Hello,

I have exactly the same issue that inph and QuasarDonkey are describing. I have a Broadcom bcm4312 card:

Code:
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
I get as well the following logs in dmesg:

Code:
37.222984] firmware ssb0:0: firmware_loading_store: unexpected value (0)
[   37.230105] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[   37.230117] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[   37.230125] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
After unloading and reloading b43 module a couple of times I can as well get my WIFI to work but this is not how it should be ;-)

Regards,
Grischuna
 
Old 07-17-2012, 09:29 PM   #140
inph
LQ Newbie
 
Registered: Jul 2012
Posts: 9

Rep: Reputation: Disabled
Quote:
Originally Posted by Grischuna View Post
After unloading and reloading b43 module a couple of times I can as well get my WIFI to work but this is not how it should be ;-)
You shouldn't need to unload and reload the module, just try ifconfig up the interface since that's the event that causes udev to try to load the firmware. I use /etc/rc.d/rc.inet1 <interface>_start to handle addressing at the same time.
 
Old 07-17-2012, 09:37 PM   #141
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,281

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Quote:
This should already be fixed, but can also easily be avoided by configuring slackpkg to first download all the packages before installing them. Have a look at the DOWNLOAD_ALL option in your slackpkg.conf.
he download
I had the same experience before and after the Jul 15 updates. I was aware of the download all option, but I am sure the devs would like feedback from all use cases.
 
Old 07-17-2012, 10:02 PM   #142
Grischuna
Member
 
Registered: Mar 2009
Distribution: Slackware64 14.0 multilib
Posts: 39

Rep: Reputation: 0
Quote:
Originally Posted by inph View Post
You shouldn't need to unload and reload the module, just try ifconfig up the interface since that's the event that causes udev to try to load the firmware. I use /etc/rc.d/rc.inet1 <interface>_start to handle addressing at the same time.
My comment was unclear. I use
Code:
rmmod b43 && modprobe b43 && /etc/rc.d/rc.inet1 wlan0_start
multiple times to bring my bcm4312 to life. Possibly I could just run your command as well without unloading the module.

Other option would be to try the broadcom-sta packages from Slackbuilds.org but it needs now a patch before running correctly with the new kernel from -current. I created the package but I haven't tested it yet. Has to wait until tomorrow.

Regards,
Grischuna
 
Old 07-18-2012, 11:40 AM   #143
BrZ
Member
 
Registered: Apr 2009
Distribution: Slackware
Posts: 485

Rep: Reputation: 79
Nope, still there =[
Quote:
Jul 18 12:36:39 m1 udevd[438]: failed to create queue file: No such file or directory
The PNP0B00 issue was suppressed by commenting "alias acpi:PNP0B00: rtc-cmos" inside /etc/modprobe.d/isapnp.conf. It try to load rtc as module and I have it right on kernel.
 
Old 07-18-2012, 01:17 PM   #144
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 136

Rep: Reputation: 46
This snippet from the latest ChangeLog.txt puzzles me a bit:
l/wv2-0.4.2-x86_64-1.txz: Removed.
Calligra doesn't require this (it bundles a forked version), nor does
anything else in Slackware. It is unmaintained upstream and requires
patching to compile with the recent glib2. Perhaps SlackBuilds.org
should take it over? If so, change all occurances of:
#include <glib/*> to #include <glib.h>

Yet this package was upgraded?
bash-4.2$ ls /var/log/packages/ |grep wv
wv2-0.4.2-x86_64-2
bash-4.2$ ls /var/log/removed_packages/ |grep wv
wv2-0.4.2-x86_64-1-upgraded-2012-07-18,19:35:08

Last edited by mats_b_tegner; 07-18-2012 at 01:20 PM.
 
Old 07-18-2012, 01:27 PM   #145
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620
Quote:
Originally Posted by mats_b_tegner View Post
This snippet from the latest ChangeLog.txt puzzles me a bit:
l/wv2-0.4.2-x86_64-1.txz: Removed.
Calligra doesn't require this (it bundles a forked version), nor does
anything else in Slackware. It is unmaintained upstream and requires
patching to compile with the recent glib2. Perhaps SlackBuilds.org
should take it over? If so, change all occurances of:
#include <glib/*> to #include <glib.h>

Yet this package was upgraded?
bash-4.2$ ls /var/log/packages/ |grep wv
wv2-0.4.2-x86_64-2
bash-4.2$ ls /var/log/removed_packages/ |grep wv
wv2-0.4.2-x86_64-1-upgraded-2012-07-18,19:35:08
Oops! Yes, I had made the patches in question after Woodsman sent them too me, and then was almost immediately thereafter made aware that KOffice/Calligra had quit using it some time back and decided that it was better removed. Looks like I left the new package in the tree anyway. Oh well, if you need it for something, now's your chance, because it's on the way out shortly.
 
2 members found this post helpful.
Old 07-18-2012, 03:26 PM   #146
rg3
Member
 
Registered: Jul 2007
Distribution: Slackware Linux
Posts: 498

Rep: Reputation: Disabled
Shouldn't the reference to rc.hald be removed from rc.M now that hal is gone?
 
Old 07-18-2012, 04:49 PM   #147
andrew.46
Member
 
Registered: Oct 2007
Distribution: Slackware
Posts: 639

Rep: Reputation: 90
Hmmm.... just caught up with the latest updates and I have noticed one odd thing that I cannot fix (edit: just saw this confirmed a few posts back). Using fluxbox with thunar as file manager whenever I delete a file from within thunar the file deletes cleanly but thunar also shuts down. Anybody else experience this?

Edit: Error when opening thunar from terminal and doing above:

Code:
GLib (gthread-posix.c): Unexpected error from C library during 'pthread_cond_timedwait': Invalid argument.  Aborting.
Aborted

Last edited by andrew.46; 07-18-2012 at 04:59 PM.
 
Old 07-18-2012, 05:14 PM   #148
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,406
Blog Entries: 1

Rep: Reputation: 951Reputation: 951Reputation: 951Reputation: 951Reputation: 951Reputation: 951Reputation: 951Reputation: 951
Quote:
Originally Posted by andrew.46 View Post
Hmmm.... just caught up with the latest updates and I have noticed one odd thing that I cannot fix (edit: just saw this confirmed a few posts back). Using fluxbox with thunar as file manager whenever I delete a file from within thunar the file deletes cleanly but thunar also shuts down. Anybody else experience this?

Edit: Error when opening thunar from terminal and doing above:

Code:
GLib (gthread-posix.c): Unexpected error from C library during 'pthread_cond_timedwait': Invalid argument.  Aborting.
Aborted
Oh, it's not just me then. It happens to me when I copy a file. I thought it might have something to do with my recent changes in hardware but clearly not.
 
Old 07-18-2012, 06:56 PM   #149
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.0
Posts: 104

Rep: Reputation: 18
Wheee!!

Well this go-round of updates (starting with Friday The 13th / Mercury in Retrograde batch) has certainly given Pat the opportunity to add more comments to the changelog (like he mentioned wanting to do in his interview).

I love it! Makes for pretty exciting reading!

Things are still a bit spicy for my blood, though.

I'll stay where I am until xfce and some of these other things get resolved. Yes, I "know what [I'm] doing" ;-)

However, it has inspired me to resurrect my VirtualBox Slack64 on my old XP system and join in the fun from there.

Slackware IS the ideal system for learning Linux!!
 
Old 07-18-2012, 07:45 PM   #150
andrew.46
Member
 
Registered: Oct 2007
Distribution: Slackware
Posts: 639

Rep: Reputation: 90
Quote:
Originally Posted by leeeoooooo View Post
I'll stay where I am until xfce and some of these other things get resolved.
I suspect a version bump for xfce is coming.......
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Microsoft forms open source subsidiary on Friday the 13th LXer Syndicated Linux News 0 04-13-2012 06:50 PM
LXer: Linux Gets Gooey on Friday the 13th LXer Syndicated Linux News 0 02-13-2009 10:10 PM
LXer: One of those magic times: On Friday the 13th! LXer Syndicated Linux News 1 02-07-2009 09:43 AM
LQ Security Report - February 13th 2005 Capt_Caveman Linux - Security 4 02-13-2005 09:51 PM
LQ security report - Feb 13th 2004 unSpawn Linux - Security 5 02-13-2004 11:36 AM


All times are GMT -5. The time now is 06:55 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration