topic title: BroadcomStartup Failure During Boot-Up
Posts: 1,028
SamK
Joined: 21 Aug 2011
#1
This problem was reported during 16-b1 and 16-b2.1.
The relevant fix post: post46440.html#p46440

Abstract from screen shot of error message using antiX-16_386-full.iso
BroadcomStartup Error
BroadcomStartup Error
Posts: 88
kmathern
Joined: 25 Aug 2012
#2
SamK wrote:This problem was reported during 16-b1 and 16-b2.1.
The relevant fix post: post46440.html#p46440
It looks like the forum /etc posting workaround of putting a space between the"/" and the"etc" ended up in the BroadcomStartup script.
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#3
Bugfix deb uploaded to repos (antix-goodies).

Line 90 of BroadcomStartup script has a space between / etc (OK for the forum, but not the script)
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#4
for any non-dev reading this, note that the broadcom driver selection should go through ok. the script is trying to start a service present in MX edition but not in mainline antiX 16. the error message is real but harmless to function.
Posts: 88
kmathern
Joined: 25 Aug 2012
#5
dolphin_oracle wrote:for any non-dev reading this, note that the broadcom driver selection should go through ok. the script is trying to start a service present in MX edition but not in mainline antiX 16. the error message is real but harmless to function.
I'm not sure if it's completely harmless, does the script still keep running after it encounters the error on line #90 ?

If it doesn't the b44 module might not get loaded by the modprobe command on line #92.

One good thing though, the error only affects wired connections that use the Broadcom b44 module, wireless isn't affected.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#6
kmathern wrote:
dolphin_oracle wrote:for any non-dev reading this, note that the broadcom driver selection should go through ok. the script is trying to start a service present in MX edition but not in mainline antiX 16. the error message is real but harmless to function.
I'm not sure if it's completely harmless, does the script still keep running after it encounters the error on line #90 ?

If it doesn't the b44 module might not get loaded by the modprobe command on line #92.

One good thing though, the error only affects wired connections that use the Broadcom b44 module, wireless isn't affected.
ah, good point. I think it will work though, since there is nothing wrong with the syntax of the command.