Re: [Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[PRP Company]

OK, here is what worked on Lubuntu to blacklist the module of interest:

In LXTERMINAL:

sudo leafpad /opt/ltsp/i386/etc/modprobe.d/blacklist.conf

Add this to the end of the file and save:

blacklist i2c_piix4

Then in LXTERMINAL once again:

sudo ltsp-update-image

In my application, the host/server and terminal/client are both i386 
(32-bit), but if the server were 64-bit and the client 32-bit, then I 
would have run instead:


sudo ltsp-update-image --arch i386

(The --arch switch is just as for the ltsp-build-client command for that 
architecture scenario.)


By the way, nowhere could I find a document with this sort of 
instruction for blacklisting an LTSP module.  I found such instructions 
for the standalone desktop, and I found other instructions that made 
reference to updating the image under various circumstances, but it was 
only by way of piecing together such information that I arrived at the 
above.  So I'll post afresh on the more general topic for the sake of 
other newbies to come.  (When you are new to this, nothing can be taken 
for granted, and nothing is obvious!)


*** But one follow-up question ***: My solution here works only for the 
case where all clients/terminals have the same problem, and where it is 
believed that leaving the SMBus controller disabled will do no harm.  
But if that were not the case, is there provision for generating and 
assigning more than one image FOR THE SAME ARCHITECTURE?


On 7/27/2012 8:39 PM, PRP Company wrote:
For an LTSP network where all the clients show this client boot error, 
can I

sudo gedit /opt/ltsp/i386/etc/modprobe.d/blacklist.conf

then add
blacklist i2c_piix4
to the blacklist and save,

then
sudo ltsp-build-client --arch i386
to rebuild my LTSP client image?

Is that likely to fix the problem?

--John Hupp

P.S. I have been on mail lists where the convention was to reply with 
new material at the top of the email, others where they wanted all 
posts in plain text (no rich text or HTML), and I think others where 
they wanted all posts trimmed of previous material.  One person on 
this list declared that the accepted practice here was to add new 
material to the bottom of the email, following all the older 
material.  Can anyone confirm or deny?


(As you can see from this email, I've been using the new-stuff-on-top 
approach.)


On 7/27/2012 1:18 PM, PRP Company wrote:
Addendum: Even though I reference Lubuntu 12.04, I find that the 
behavior is exactly the same under Edubuntu 12.04.


On 7/25/2012 2:56 PM, PRP Company wrote:

A refined request:

The research that I have done on this has not shown that this 
condition ever did any harm.  So instead of asking how to enable the 
controller somehow, I would now ask: How can I modify the image 
being downloaded to the terminal so that the error does not appear?  
For instance, can I blacklist a module in the image?


--John Hupp

On 7/23/2012 9:41 PM, PRP Company wrote:

Hi, all.

Continuing to work through my newbie questions on my first LTSP setup:

After Lubuntu 12.04 has begun booting on an eMachines iTower 500i 
client, it generates the error:


/piix4_smbus :00:0.7.3: Host SMBus controller not enabled/

But it continues booting and, so far as I can tell at the moment, 
everything works.


When the machine is then shut down or rebooted, a similar message 
appears:


/saned disabled; edit /etc/default/saned/
/Host SMBus controller not enabled/

Even if everything works, these are disturbing messages.

Some online posts associate these messages with various things that 
don't work, so it may be that I simply have not discovered the 
damage yet.


For situations not involving LTSP, a couple sources prescribe adding
/blacklist i2c_piix4/
to /etc/modprobe.d/blacklist.conf

I did this on the LTSP server, but whatever the effect on the 
server, it did not solve the problem on the client.


Other sources also recommend upgrading the BIOS to solve this 
problem.  They note that some BIOS implementations leave the SMBus 
controller disabled by default.  I did upgrade the BIOS on the 
eMachines, but it did not fix the problem, and I did not recognize 
any BIOS settings that might allow me to enable the SMBus controller.


I think that the error reports refer to the state of the eMachines 
PC, since another LTSP client does not generate the error.


Anyone recognize this problem and have a solution?

--John Hupp


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
   https://lists.sourceforge

Re: [Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[PRP Company]

Thanks for the freedom, Jim.

--John Hupp

On 7/27/2012 9:22 PM, James McQuillan wrote:



On Fri, Jul 27, 2012 at 8:39 PM, PRP Company > wrote:


For an LTSP network where all the clients show this client boot
error, can I
sudo gedit /opt/ltsp/i386/etc/modprobe.d/blacklist.conf

then add
blacklist i2c_piix4
to the blacklist and save,

then
sudo ltsp-build-client --arch i386
to rebuild my LTSP client image?

Is that likely to fix the problem?

--John Hupp

P.S. I have been on mail lists where the convention was to reply
with new material at the top of the email, others where they
wanted all posts in plain text (no rich text or HTML), and I think
others where they wanted all posts trimmed of previous material. 
One person on this list declared that the accepted practice here

was to add new material to the bottom of the email, following all
the older material.  Can anyone confirm or deny?


This mailing list has no "official" way of posting.  As far as I'm 
concerned,  if someone wants to take the time to comment on an email, 
and hopefully offer help, they can post any way they like. 
 top,bottom,inline, whatever. We're all smart enough to figure out the 
thread.


Personally, I prefer the top-most thing to be the answer, unless 
there's several questions, then I prefer to post my answers inline 
just below each question.


My attitude on top vs bottom vs inline posting is certainly going to 
draw some criticism but that's Ok.  I'd still prefer the content to be 
the most important thing, not the style.


Jim McQuillan (creator of this list and ltsp)


(As you can see from this email, I've been using the
new-stuff-on-top approach.)

On 7/27/2012 1:18 PM, PRP Company wrote:

Addendum: Even though I reference Lubuntu 12.04, I find that the
behavior is exactly the same under Edubuntu 12.04.

On 7/25/2012 2:56 PM, PRP Company wrote:

A refined request:

The research that I have done on this has not shown that this
condition ever did any harm.  So instead of asking how to enable
the controller somehow, I would now ask: How can I modify the
image being downloaded to the terminal so that the error does
not appear?  For instance, can I blacklist a module in the image?

--John Hupp

On 7/23/2012 9:41 PM, PRP Company wrote:

Hi, all.

Continuing to work through my newbie questions on my first LTSP
setup:

After Lubuntu 12.04 has begun booting on an eMachines iTower
500i client, it generates the error:

/piix4_smbus :00:0.7.3: Host SMBus controller not enabled/

But it continues booting and, so far as I can tell at the
moment, everything works.

When the machine is then shut down or rebooted, a similar
message appears:

/saned disabled; edit /etc/default/saned/
/Host SMBus controller not enabled/

Even if everything works, these are disturbing messages.

Some online posts associate these messages with various things
that don't work, so it may be that I simply have not discovered
the damage yet.

For situations not involving LTSP, a couple sources prescribe
adding
/blacklist i2c_piix4/
to /etc/modprobe.d/blacklist.conf

I did this on the LTSP server, but whatever the effect on the
server, it did not solve the problem on the client.

Other sources also recommend upgrading the BIOS to solve this
problem.  They note that some BIOS implementations leave the
SMBus controller disabled by default.  I did upgrade the BIOS
on the eMachines, but it did not fix the problem, and I did not
recognize any BIOS settings that might allow me to enable the
SMBus controller.

I think that the error reports refer to the state of the
eMachines PC, since another LTSP client does not generate the
error.

Anyone recognize this problem and have a solution?

--John Hupp



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel onirc.freenode.net  








--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respon

Re: [Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[James McQuillan]

On Fri, Jul 27, 2012 at 8:39 PM, PRP Company  wrote:

>  For an LTSP network where all the clients show this client boot error,
> can I
> sudo gedit /opt/ltsp/i386/etc/modprobe.d/blacklist.conf
>
> then add
> blacklist i2c_piix4
> to the blacklist and save,
>
> then
> sudo ltsp-build-client --arch i386
> to rebuild my LTSP client image?
>
> Is that likely to fix the problem?
>
> --John Hupp
>
> P.S. I have been on mail lists where the convention was to reply with new
> material at the top of the email, others where they wanted all posts in
> plain text (no rich text or HTML), and I think others where they wanted all
> posts trimmed of previous material.  One person on this list declared that
> the accepted practice here was to add new material to the bottom of the
> email, following all the older material.  Can anyone confirm or deny?
>

This mailing list has no "official" way of posting.  As far as I'm
concerned,  if someone wants to take the time to comment on an email, and
hopefully offer help, they can post any way they like.  top,bottom,inline,
whatever. We're all smart enough to figure out the thread.

Personally, I prefer the top-most thing to be the answer, unless there's
several questions, then I prefer to post my answers inline just below each
question.

My attitude on top vs bottom vs inline posting is certainly going to draw
some criticism but that's Ok.  I'd still prefer the content to be the most
important thing, not the style.

Jim McQuillan (creator of this list and ltsp)



>
> (As you can see from this email, I've been using the new-stuff-on-top
> approach.)
>
>  On 7/27/2012 1:18 PM, PRP Company wrote:
>
> Addendum: Even though I reference Lubuntu 12.04, I find that the behavior
> is exactly the same under Edubuntu 12.04.
>
>  On 7/25/2012 2:56 PM, PRP Company wrote:
>
> A refined request:
>
> The research that I have done on this has not shown that this condition
> ever did any harm.  So instead of asking how to enable the controller
> somehow, I would now ask: How can I modify the image being downloaded to
> the terminal so that the error does not appear?  For instance, can I
> blacklist a module in the image?
>
> --John Hupp
>
>  On 7/23/2012 9:41 PM, PRP Company wrote:
>
> Hi, all.
>
> Continuing to work through my newbie questions on my first LTSP setup:
>
> After Lubuntu 12.04 has begun booting on an eMachines iTower 500i client,
> it generates the error:
>
> *piix4_smbus :00:0.7.3: Host SMBus controller not enabled*
>
> But it continues booting and, so far as I can tell at the moment,
> everything works.
>
> When the machine is then shut down or rebooted, a similar message appears:
>
> *saned disabled; edit /etc/default/saned*
> *Host SMBus controller not enabled*
>
> Even if everything works, these are disturbing messages.
>
> Some online posts associate these messages with various things that don't
> work, so it may be that I simply have not discovered the damage yet.
>
> For situations not involving LTSP, a couple sources prescribe adding
> *blacklist i2c_piix4*
> to /etc/modprobe.d/blacklist.conf
>
> I did this on the LTSP server, but whatever the effect on the server, it
> did not solve the problem on the client.
>
> Other sources also recommend upgrading the BIOS to solve this problem.
> They note that some BIOS implementations leave the SMBus controller
> disabled by default.  I did upgrade the BIOS on the eMachines, but it did
> not fix the problem, and I did not recognize any BIOS settings that might
> allow me to enable the SMBus controller.
>
> I think that the error reports refer to the state of the eMachines PC,
> since another LTSP client does not generate the error.
>
> Anyone recognize this problem and have a solution?
>
> --John Hupp
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _
> Ltsp-discuss mailing list.   To un-

Re: [Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[PRP Company]

For an LTSP network where all the clients show this client boot error, 
can I

sudo gedit /opt/ltsp/i386/etc/modprobe.d/blacklist.conf

then add
blacklist i2c_piix4
to the blacklist and save,

then
sudo ltsp-build-client --arch i386
to rebuild my LTSP client image?

Is that likely to fix the problem?

--John Hupp

P.S. I have been on mail lists where the convention was to reply with 
new material at the top of the email, others where they wanted all posts 
in plain text (no rich text or HTML), and I think others where they 
wanted all posts trimmed of previous material.  One person on this list 
declared that the accepted practice here was to add new material to the 
bottom of the email, following all the older material.  Can anyone 
confirm or deny?


(As you can see from this email, I've been using the new-stuff-on-top 
approach.)


On 7/27/2012 1:18 PM, PRP Company wrote:
Addendum: Even though I reference Lubuntu 12.04, I find that the 
behavior is exactly the same under Edubuntu 12.04.


On 7/25/2012 2:56 PM, PRP Company wrote:

A refined request:

The research that I have done on this has not shown that this 
condition ever did any harm.  So instead of asking how to enable the 
controller somehow, I would now ask: How can I modify the image being 
downloaded to the terminal so that the error does not appear?  For 
instance, can I blacklist a module in the image?


--John Hupp

On 7/23/2012 9:41 PM, PRP Company wrote:

Hi, all.

Continuing to work through my newbie questions on my first LTSP setup:

After Lubuntu 12.04 has begun booting on an eMachines iTower 500i 
client, it generates the error:


/piix4_smbus :00:0.7.3: Host SMBus controller not enabled/

But it continues booting and, so far as I can tell at the moment, 
everything works.


When the machine is then shut down or rebooted, a similar message 
appears:


/saned disabled; edit /etc/default/saned/
/Host SMBus controller not enabled/

Even if everything works, these are disturbing messages.

Some online posts associate these messages with various things that 
don't work, so it may be that I simply have not discovered the 
damage yet.


For situations not involving LTSP, a couple sources prescribe adding
/blacklist i2c_piix4/
to /etc/modprobe.d/blacklist.conf

I did this on the LTSP server, but whatever the effect on the 
server, it did not solve the problem on the client.


Other sources also recommend upgrading the BIOS to solve this 
problem.  They note that some BIOS implementations leave the SMBus 
controller disabled by default.  I did upgrade the BIOS on the 
eMachines, but it did not fix the problem, and I did not recognize 
any BIOS settings that might allow me to enable the SMBus controller.


I think that the error reports refer to the state of the eMachines 
PC, since another LTSP client does not generate the error.


Anyone recognize this problem and have a solution?

--John Hupp


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net






--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[PRP Company]

Addendum: Even though I reference Lubuntu 12.04, I find that the 
behavior is exactly the same under Edubuntu 12.04.


On 7/25/2012 2:56 PM, PRP Company wrote:

A refined request:

The research that I have done on this has not shown that this 
condition ever did any harm.  So instead of asking how to enable the 
controller somehow, I would now ask: How can I modify the image being 
downloaded to the terminal so that the error does not appear?  For 
instance, can I blacklist a module in the image?


--John Hupp

On 7/23/2012 9:41 PM, PRP Company wrote:

Hi, all.

Continuing to work through my newbie questions on my first LTSP setup:

After Lubuntu 12.04 has begun booting on an eMachines iTower 500i 
client, it generates the error:


/piix4_smbus :00:0.7.3: Host SMBus controller not enabled/

But it continues booting and, so far as I can tell at the moment, 
everything works.


When the machine is then shut down or rebooted, a similar message 
appears:


/saned disabled; edit /etc/default/saned/
/Host SMBus controller not enabled/

Even if everything works, these are disturbing messages.

Some online posts associate these messages with various things that 
don't work, so it may be that I simply have not discovered the damage 
yet.


For situations not involving LTSP, a couple sources prescribe adding
/blacklist i2c_piix4/
to /etc/modprobe.d/blacklist.conf

I did this on the LTSP server, but whatever the effect on the server, 
it did not solve the problem on the client.


Other sources also recommend upgrading the BIOS to solve this 
problem.  They note that some BIOS implementations leave the SMBus 
controller disabled by default.  I did upgrade the BIOS on the 
eMachines, but it did not fix the problem, and I did not recognize 
any BIOS settings that might allow me to enable the SMBus controller.


I think that the error reports refer to the state of the eMachines 
PC, since another LTSP client does not generate the error.


Anyone recognize this problem and have a solution?

--John Hupp


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net




--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[PRP Company]

A refined request:

The research that I have done on this has not shown that this condition 
ever did any harm.  So instead of asking how to enable the controller 
somehow, I would now ask: How can I modify the image being downloaded to 
the terminal so that the error does not appear?  For instance, can I 
blacklist a module in the image?


--John Hupp

On 7/23/2012 9:41 PM, PRP Company wrote:

Hi, all.

Continuing to work through my newbie questions on my first LTSP setup:

After Lubuntu 12.04 has begun booting on an eMachines iTower 500i 
client, it generates the error:


/piix4_smbus :00:0.7.3: Host SMBus controller not enabled/

But it continues booting and, so far as I can tell at the moment, 
everything works.


When the machine is then shut down or rebooted, a similar message appears:

/saned disabled; edit /etc/default/saned/
/Host SMBus controller not enabled/

Even if everything works, these are disturbing messages.

Some online posts associate these messages with various things that 
don't work, so it may be that I simply have not discovered the damage yet.


For situations not involving LTSP, a couple sources prescribe adding
/blacklist i2c_piix4/
to /etc/modprobe.d/blacklist.conf

I did this on the LTSP server, but whatever the effect on the server, 
it did not solve the problem on the client.


Other sources also recommend upgrading the BIOS to solve this 
problem.  They note that some BIOS implementations leave the SMBus 
controller disabled by default.  I did upgrade the BIOS on the 
eMachines, but it did not fix the problem, and I did not recognize any 
BIOS settings that might allow me to enable the SMBus controller.


I think that the error reports refer to the state of the eMachines PC, 
since another LTSP client does not generate the error.


Anyone recognize this problem and have a solution?

--John Hupp


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

[Ltsp-discuss] Client boot error: piix4_smbus ... Host SMBus controller not enabled

[PRP Company]

Hi, all.

Continuing to work through my newbie questions on my first LTSP setup:

After Lubuntu 12.04 has begun booting on an eMachines iTower 500i 
client, it generates the error:


/piix4_smbus :00:0.7.3: Host SMBus controller not enabled/

But it continues booting and, so far as I can tell at the moment, 
everything works.


When the machine is then shut down or rebooted, a similar message appears:

/saned disabled; edit /etc/default/saned/
/Host SMBus controller not enabled/

Even if everything works, these are disturbing messages.

Some online posts associate these messages with various things that 
don't work, so it may be that I simply have not discovered the damage yet.


For situations not involving LTSP, a couple sources prescribe adding
/blacklist i2c_piix4/
to /etc/modprobe.d/blacklist.conf

I did this on the LTSP server, but whatever the effect on the server, it 
did not solve the problem on the client.


Other sources also recommend upgrading the BIOS to solve this problem.  
They note that some BIOS implementations leave the SMBus controller 
disabled by default.  I did upgrade the BIOS on the eMachines, but it 
did not fix the problem, and I did not recognize any BIOS settings that 
might allow me to enable the SMBus controller.


I think that the error reports refer to the state of the eMachines PC, 
since another LTSP client does not generate the error.


Anyone recognize this problem and have a solution?

--John Hupp
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net