Re: Security updates for wheezy breaking my FAI-installation

2015-05-05 Thread Alexis


Christian Seiler  writes:

Ok, since there appears to be some kind of confusion, I'll 
explain.


[snip comprehensive explanatory/summary of what the various 
official Debian repos are used for]


Thank you very much for all this - it's greatly appreciated! i'd 
like to suggest that this summary (or at least some parts thereof) 
be put on the Debian Wiki, e.g. as an 'OfficialRepositories' page 
(which seems to not exist, currently), and that it be linked to 
from various relevant pages. i feel this information is too 
valuable to perhaps get lost amongst the welter of emails to this 
list. :-)


Thanks again!


Alexis.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/87twvqib51@gmail.com



Re: bug report

2015-05-05 Thread Umarzuki Mochlis
could be debian-installer package?

2015-05-06 11:13 GMT+08:00 Nader :
> hi, I need to report a bug in the debian installation system. I do not
> know the name of the package that reportbug needs. Please let me know
> how to proceed.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> https://lists.debian.org/caj19urtnz2l94d2jukdruoubeqnqjxweinnti-26bykzkfl...@mail.gmail.com
>


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAHW9mbxiiLyz85D5vLBLkt-a8XOFbNqHnaw=_purgxgfhbp...@mail.gmail.com



bug report

2015-05-05 Thread Nader
hi, I need to report a bug in the debian installation system. I do not
know the name of the package that reportbug needs. Please let me know
how to proceed.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caj19urtnz2l94d2jukdruoubeqnqjxweinnti-26bykzkfl...@mail.gmail.com



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread David Wright
Quoting Charles Kroeger (ckro...@frankensteinface.com):
> 
> root@mundo:/home/charles# ifconfig -a
> eth0  Link encap:Ethernet  HWaddr 00:1b:21:4f:60:49  
>   inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
>   inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:1051 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:502 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:291611 (284.7 KiB)  TX bytes:82072 (80.1 KiB)
>   Interrupt:17 Memory:fbfe-fc00 
> 
> loLink encap:Local Loopback  
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:55 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0 
>   RX bytes:15256 (14.8 KiB)  TX bytes:15256 (14.8 KiB)
> 
> wlan0 Link encap:Ethernet  HWaddr 00:c0:ca:72:68:d4  
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> wlan0:avahi Link encap:Ethernet  HWaddr 00:c0:ca:72:68:d4  
>   inet addr:169.254.10.111  Bcast:169.254.255.255  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
> 
> root@mundo:/home/charles# lsmod | grep ath
> ath9k_htc  52702  0 
> ath9k_common   12687  1 ath9k_htc
> ath9k_hw  341687  2 ath9k_common,ath9k_htc
> ath21417  3 ath9k_common,ath9k_htc,ath9k_hw
> mac80211  358182  1 ath9k_htc
> cfg80211  319971  3 ath,mac80211,ath9k_htc
> usbcore   134993  6
> usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc

At this stage, I would run wicd-curses (not as root) and type P.
I would make sure the Wireless and Wired Interfaces were correctly
named wlan0 and eth0, set automatic reconnection and any other options
I wanted, save that, scan for APs with Fn5, select one and press ->
to configure it. I would remove the ethernet cable because I have
that set to take priority. After saving the configuration, I'd press
Return and hope to have a wireless connection come up.

It's too long since I bothered to configure all this through
/etc/network/interfaces, which reminds me: for wicd to manage
the network, you should comment all but
  auto lo
  iface lo inet loopback
in that file.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150506030242.GA20972@alum



Encrypted DVDs Do Not Autoplay

2015-05-05 Thread Daniel Casey

I have installed Debian 8 (Cinnamon desktop) from a live DVD.

When I insert an Audio CD or a non-encrypted DVD into the drive a window 
will appear asking me what I want to do.  I know how to change the 
settings to cause the disk to automatically play with a particular 
program (e.g. VLC).


However, when I insert an encrypted DVD into the drive this window does 
not appear.


I am, however, able to open VLC and play the encrypted DVD without any 
problems.


Although this is not a hardship, I would like to learn how to resolve it.

Thanks,

Daniel


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55497248.9090...@q.com



bad ABI version?

2015-05-05 Thread Dale Harris
I'm running sid. I can't currently install xserver-xorg-video-intel.  I get:

# apt-get install --reinstall xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-18
 E: Unable to correct problems, you have held broken packages.


However, looks like abi-18 is old, looks like the latest should be 19.
Because when I run Xorg -configure, I get:

(EE) module ABI major version (15) doesn't match the server's version
(19)


Is xserver-xorg-core just out of date?  Any suggestions on how to fix
this? I did try reinstalling xserver-xorg-core but with no luck.

-- 
Dale Harris
rod...@maybe.org
rod...@gmail.com
/.-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caebw9tycynoa+aqwm9b5pq-+p9g0ir9y+ggvrgbr_cqqxpw...@mail.gmail.com



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Charles Kroeger
On Wed, 06 May 2015 01:10:02 +0200
Brian  wrote:

> Please post the outputs of
> 
>   ifconfig -a
> 
> and
> 
>   lsmod | grep ath


root@mundo:/home/charles# ifconfig -a
eth0  Link encap:Ethernet  HWaddr 00:1b:21:4f:60:49  
  inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1051 errors:0 dropped:0 overruns:0 frame:0
  TX packets:502 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:291611 (284.7 KiB)  TX bytes:82072 (80.1 KiB)
  Interrupt:17 Memory:fbfe-fc00 

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:55 errors:0 dropped:0 overruns:0 frame:0
  TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:15256 (14.8 KiB)  TX bytes:15256 (14.8 KiB)

wlan0 Link encap:Ethernet  HWaddr 00:c0:ca:72:68:d4  
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0:avahi Link encap:Ethernet  HWaddr 00:c0:ca:72:68:d4  
  inet addr:169.254.10.111  Bcast:169.254.255.255  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1



root@mundo:/home/charles# lsmod | grep ath
ath9k_htc  52702  0 
ath9k_common   12687  1 ath9k_htc
ath9k_hw  341687  2 ath9k_common,ath9k_htc
ath21417  3 ath9k_common,ath9k_htc,ath9k_hw
mac80211  358182  1 ath9k_htc
cfg80211  319971  3 ath,mac80211,ath9k_htc
usbcore   134993  6
usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc

-- 
CK


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/cqt5tnft2i...@mid.individual.net



Re: no root file system after encryption

2015-05-05 Thread David Christensen

On 05/05/2015 10:34 AM, Juha Heinanen wrote:

Here are the steps I made.
Detect disk results in screen where the disk that I try to partition
shows pri/log 15.8 GB FREE SPACE.


I will assume you have a 16 GB drive with no other partitions.



I select it and on the next screen, I select Create a new partition.
This is going to be /boot and I set the size to 16MB and select primary.
On Partition settings screen, I choose Use as Ext2, Mount point /boot, and
Bootable flag on.  Then I choose Done setting up the partition.



That is much too small.  The Wheezy machine I'm typing on has 512 MB for 
/boot (~18 MB used).  Why ext2?  I use ext4.




Next I select to automatically partition the remaining free space that
results in two logical partitions 15.1 GB ext4 mount point / and 693.1
MB swap.


Don't select automatic -- do everything manually.  You want to create a 
second primary partition at the beginning for swap (I allocate 512 MB), 
use it as physical volume for encryption, with a random encryption key. 
 Then create a third primary partition at the beginning for root (I 
allocate 13.4 GB), use it as a physical volume for encryption, with 
passphrase encryption key.  Then configure the encrypted volumes. 
sda2_crypt will end up as swap.  Then configure sda3_crypt as as root.



David


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554963b6.5080...@holgerdanske.com



Re: Default virtualhost on Debian Jessie with Apache 2.4.10

2015-05-05 Thread Bob Proulx
Daniel Bareiro wrote:
> Marco Stoecker wrote:
> > I do have the same issue. I disabled the default config in
> > "sites-enabled" (which in fact removed the symbolic link to the
> > 000-default.conf in "sites-available") and did a restart of apache, but
> > still the default page is showing up. I there another way to disable the
> > default site? I'd like to have only the mailman site enabled.
> 
> Thanks for confirm the behavior that I had mentioned. I don't remember
> this happening with Apache 2.2.22 on Debian Wheezy. So at the beginning
> of this thread I had asked whether it is likely that this configuration
> is compiled into Apache.

I cannot reproduce the behavior that you have reported.  I had
previously tested on my Sid system.  I just now debootstrap'd a
pristine Jessie 8 system and tested and apache2 is not listening to
port 80 after performing the following configuration which was
previously discussed in this thread.

Ensure that no web server is running in the host environment.

  service apache2 stop
  service nginx stop
  service ... stop  # ... any other installed web servers ...
  wget -O/dev/null -S http://127.0.0.1/
  --2015-05-05 17:01:51--  http://127.0.0.1/
  Connecting to 127.0.0.1:80... failed: Connection refused.
  ... Good.  No web servers are running as verified above. ...

Then set up a pristine test case system in a chroot.

  debootstrap jessie /srv/chroot/jessie http://http.debian.net/debian
  mount -o bind /proc /srv/chroot/jessie/proc
  chroot /srv/chroot/jessie su -
  apt-get install apache2
  ln -sfn ../sites-available/default-ssl.conf 
/etc/apache2/sites-enabled/000-default.conf
  a2enmod ssl
  sed --in-place '/^Listen 80/s/^/# /' /etc/apache2/ports.conf
  service apache2 restart

At that point apache is running.  It is not listening on port 80.

  # wget -O/dev/null -S http://127.0.0.1/
  --2015-05-05 17:01:51--  http://127.0.0.1/
  Connecting to 127.0.0.1:80... failed: Connection refused.

It is listening on port 443 with ssl.

  # wget -O/dev/null -S -q --no-check-certificate https://127.0.0.1/
HTTP/1.1 200 OK
Date: Tue, 05 May 2015 23:01:14 GMT
Server: Apache/2.4.10 (Debian)
Last-Modified: Tue, 05 May 2015 22:47:53 GMT
ETag: "2b60-5155d780793dc"
Accept-Ranges: bytes
Content-Length: 11104
Vary: Accept-Encoding
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html

Please double check and ensure that you have accomplished all of the
required steps again.  I feel certain that one of them has been left
out.

If you still think there is a problem then try the above steps to
reproduce it using a pristine system.  Then compare the pristine
environment to the problem environment.

Bob


signature.asc
Description: Digital signature


Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Brian
On Tue 05 May 2015 at 17:10:31 -0400, Charles Kroeger wrote:

> On Tue, 05 May 2015 21:30:02 +0200
> Brian  wrote:
> 
> > You could try
> > 
> >   ifconfig wlan0 up
> > 
> > to activate the interface before following the remainder of the advice
> > given.
>  
> I tried that but it complained about not being able to find wlan0

Please post the outputs of

  ifconfig -a

and

  lsmod | grep ath


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/0605201526.33c8d3d65...@desktop.copernicus.demon.co.uk



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread David Wright
Quoting Charles Kroeger (ckro...@frankensteinface.com):
> On Tue, 05 May 2015 21:30:02 +0200
> Brian  wrote:
> 
> > You could try
> > 
> >   ifconfig wlan0 up
> > 
> > to activate the interface before following the remainder of the advice
> > given.
>  
> I tried that but it complained about not being able to find wlan0

That was the idea behind running iwconfig and ifconfig with no
arguments: to see if there was a wireless interface present. There's
always the possibility that it's called something silly like eth1.

After this step, I think I'd rmmod and modprobe the kernel module and
watch kern.log for messages to see if it finds anything.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505214940.GA15504@alum



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Charles Kroeger
On Tue, 05 May 2015 22:30:02 +0200
David Wright  wrote:

> Perhaps I wasn't clear!
> 
> iwconfig and ifconfig are programs that you run. Because /sbin isn't
> in the user's $PATH, you need to prefix with the pathname.

I get this from #ifconfig

root@mundo:/home/charles# ifconfig
eth0  Link encap:Ethernet  HWaddr 00:1b:21:4f:60:49  
  inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:21946 errors:0 dropped:0 overruns:0 frame:0
  TX packets:12589 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:12859474 (12.2 MiB)  TX bytes:1590982 (1.5 MiB)
  Interrupt:17 Memory:fbfe-fc00 

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:72 errors:0 dropped:0 overruns:0 frame:0
  TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:17302 (16.8 KiB)  TX bytes:17302 (16.8 KiB)

and this from #iwconfig

root@mundo:/home/charles# iwcofig
bash: iwcofig: command not found
root@mundo:/home/charles# iwconfig
eth0  no wireless extensions.

lono wireless extensions.

Thanks for the suggestion David, just fun'in you there.

-- 
CK


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/cqsqj2fo65...@mid.individual.net



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Charles Kroeger
On Tue, 05 May 2015 21:30:02 +0200
Brian  wrote:

> You could try
> 
>   ifconfig wlan0 up
> 
> to activate the interface before following the remainder of the advice
> given.
 
I tried that but it complained about not being able to find wlan0

-- 
CK 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/cqspu7fo65...@mid.individual.net



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread David Wright
Quoting Charles Kroeger (ckro...@frankensteinface.com):
> On Tue, 05 May 2015 15:10:02 +0200
> David Wright  wrote:
> 
> > What do /sbin/iwconfig and /sbin/ifconfig show?
> 
> ^?ELF^B
[...]

Perhaps I wasn't clear!

iwconfig and ifconfig are programs that you run. Because /sbin isn't
in the user's $PATH, you need to prefix with the pathname.

You might see output like

wlan0 IEEE 802.11abg  ESSID:"foo"
  Mode:Managed  Frequency:2.462 GHz  Access Point: 44:...
  Bit Rate=54 Mb/s   Tx-Power=15 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Power Management:off
  Link Quality=69/70  Signal level=-41 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:59   Missed beacon:0

lono wireless extensions.

eth0  no wireless extensions.

and

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:1131 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1131 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:101396 (99.0 KiB)  TX bytes:101396 (99.0 KiB)

wlan0 Link encap:Ethernet  HWaddr 00:...
  inet addr:192.168.1.15  Bcast:192.168.1.255
  Mask:255.255.255.0
  inet6 addr: fe80.../64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:481394 errors:0 dropped:0 overruns:0 frame:0
  TX packets:393808 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:362857903 (346.0 MiB)  TX bytes:61878630 (59.0 MiB)

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505202606.GA13802@alum



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Charles Kroeger
On Tue, 05 May 2015 15:10:02 +0200
David Wright  wrote:

> What do /sbin/iwconfig and /sbin/ifconfig show?

^?ELF^B^A^A^@^@^@^@^@^@^@^@^@^B^@>^@^A^@^@^@\^Y@^@^@^@^@^@@^@^@^@^@^@^@^@Xb^@^@^@^@^@^@^@^@^@^@@^@8^@
^@@^@^\^@^[^@^F^@^@^@^E^@^@^@@^@^@^@^@^@^@^@@^@@^@^@^@^@^@@^@@^@^@^@^@^@ø^A^@^@^@^@^@^@ø^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^C^@^@^@^D^@^@^@8^B^@^@^@^@^@^@8^B@^@^@^@^@^@8^B@^@^@^@^@^@^\^@^@^@^@^@^@^@^\^@^@^@^@^@^@^@^A^@^@^@^@^@^@^@^A^@^@^@^E^@^@^@^@^@^@^@^@^@^@^@^@^@@^@^@^@^@^@^@^@@^@^@^@^@^@<8c>X^@^@^@^@^@^@<8c>X^@^@^@^@^@^@^@^@
^@^@^@^@^@^A^@^@^@^F^@^@^@^H^^@^@^@^@^@^@^H^`^@^@^@^@^@^H^`^@^@^@^@^@h^C^@^@^@^@^@^@X^E^@^@^@^@^@^@^@^@
^@^@^@^@^@^B^@^@^@^F^@^@^@0^^@^@^@^@^@^@0^`^@^@^@^@^@0^`^@^@^@^@^@°^A^@^@^@^@^@^@°^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^D^@^@^@^D^@^@^@T^B^@^@^@^@^@^@T^B@^@^@^@^@^@T^B@^@^@^@^@^@D^@^@^@^@^@^@^@D^@^@^@^@^@^@^@^D^@^@^@^@^@^@^@Påtd^D^@^@^@(S^@^@^@^@^@^@(S@^@^@^@^@^@(S@^@^@^@^@^@¼^@^@^@^@^@^@^@¼^@^@^@^@^@^@^@^D^@^@^@^@^@^@^@Qåtd^F^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^H^@^@^@^@^@^@^@Råtd^D^@^@^@^H^^@^@^@^@^@^@^H^`^@^@^@^@^@^H^`^@^@^@^@^@ø^A^@^@^@^@^@^@ø^A^@^@^@^@^@^@^A^@^@^@^@^@^@^@/lib64/ld-linux-x86-64.so.2^@^D^@^@^@^P^@^@^@^A^@^@^@GNU^@^@^@^@^@^B^@^@^@^F^@^@^@^Z^@^@^@^D^@^@^@^T^@^@^@^C^@^@^@GNU^@<94>T¡V<8d>7"Í¡<8c><86>^E<97>V^ZX¦ÒÜä%^@^@^@7^@^@^@^@^@^@^@'^@^@^@^@^@^@^@+^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
@
@
@
@
@   
   @
  @ 
 @  

"/sbin/iwconfig" [noeol][converted] 56L, 33541C 


^?ELF^B^A^A^@^@^@^@^@^@^@^@^@^B^@>^@^A^@^@^@¾7@^@^@^@^@^@@^@^@^@^@^@^@^@H^D^A^@^@^@^@^@^@^@^@^@@^@8^@
^@@^@^[^@^Z^@^F^@^@^@^E^@^@^@@^@^@^@^@^@^@^@@^@@^@^@^@^@^@@^@@^@^@^@^@^@ø^A^@^@^@^@^@^@ø^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^C^@^@^@^D^@^@^@8^B^@^@^@^@^@^@8^B@^@^@^@^@^@8^B@^@^@^@^@^@^\^@^@^@^@^@^@^@^\^@^@^@^@^@^@^@^A^@^@^@^@^@^@^@^A^@^@^@^E^@^@^@^@^@^@^@^@^@^@^@^@^@@^@^@^@^@^@^@^@@^@^@^@^@^@<84>ë^@^@^@^@^@^@<84>ë^@^@^@^@^@^@^@^@
^@^@^@^@^@^A^@^@^@^F^@^@^@^Pî^@^@^@^@^@^@^Pî`^@^@^@^@^@^Pî`^@^@^@^@^@H^U^@^@^@^@^@^@<98>#^@^@^@^@^@^@^@^@
 
^@^@^@^@^@^B^@^@^@^F^@^@^@(î^@^@^@^@^@^@(î`^@^@^@^@^@(î`^@^@^@^@^@Ð^A^@^@^@^@^@^@Ð^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^D^@^@^@^D^@^@^@T^B^@^@^@^@^@^@T^B@^@^@^@^@^@T^B@^@^@^@^@^@D^@^@^@^@^@^@^@D^@^@^@^@^@^@^@^D^@^@^@^@^@^@^@Påtd^D^@^@^@¼Î^@^@^@^@^@^@¼Î@^@^@^@^@^@¼Î@^@^@^@^@^@ô^C^@^@^@^@^@^@ô^C^@^@^@^@^@^@^D^@^@^@^@^@^@^@Qåtd^F^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^P^@^@^@^@^@^@^@Råtd^D^@^@^@^Pî^@^@^@^@^@^@^Pî`^@^@^@^@^@^Pî`^@^@^@^@^@ð^A^@^@^@^@^@^@ð^A^@^@^@^@^@^@^A^@^@^@^@^@^@^@/lib64/ld-linux-x86-64.so.2^@^D^@^@^@^P^@^@^@^A^@^@^@GNU^@^@^@^@^@^B^@^@^@^F^@^@^@
 
^@^@^@^D^@^@^@^T^@^@^@^C^@^@^@GNU^@^S^_9hjMOö«©_Òv.³£Q<85>J¤^B^@^@^@K^@^@^@^A^@^@^@^F^@^@^@^@^A^@^@^@^@^@^B^@^@^@^@K^@^@^@9ò<8b>^\^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^M^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<83>^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<8c>^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@×^A^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Í^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Â^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@·^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<8e>^A^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Ç^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^R^A^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<96>^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@@^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@²^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@I^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@q^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
"/sbin/ifconfig" [noeol][converted] 320L, 87918C

Are you a machine that's got loose out there and posing as a good natured
Englishman?

-- 
CK












 and /sbin/ifconfig show?
> 
> Cheers,
> David.
> 
> 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/cqsiejfo65...@mid.individual.net



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Brian
On Tue 05 May 2015 at 14:49:18 -0400, Charles Kroeger wrote:

> On Tue, 05 May 2015 12:10:02 +0200
> Brian  wrote:
> 
> > The non-free firmware-atheros package has the firmware for the adapter.
> 
> I have the 'firmware-atheros' package installed. I take it that's the free
> non-working version of the non-free package
> 
> I have non-free sources in my sources.list wonder why it didn't show up?
> 
> You don't have a location for this do you?
> 
> I'll also have a look out there.
> 
> Thanks for the suggestion.  That may solve the problem.

I mentioned firmware-atheros because it is in the Debian archives and
not because getting the firmware file your adapter needs from elsewhere
is a problem. In fact, I don't believe what you have is a problem.

You could try

  ifconfig wlan0 up

to activate the interface before following the remainder of the advice
given.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/05052015201449.b01cf93a2...@desktop.copernicus.demon.co.uk



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Charles Kroeger
On Tue, 05 May 2015 12:10:02 +0200
Brian  wrote:

> The non-free firmware-atheros package has the firmware for the adapter.

I have the 'firmware-atheros' package installed. I take it that's the free
non-working version of the non-free package

I have non-free sources in my sources.list wonder why it didn't show up?

You don't have a location for this do you?

I'll also have a look out there.

Thanks for the suggestion.  That may solve the problem.

-- 
CK


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/cqshlefo65...@mid.individual.net



Re: no root file system after encryption

2015-05-05 Thread Juha Heinanen
Here are the steps I made.

Detect disk results in screen where the disk that I try to partition
shows pri/log 15.8 GB FREE SPACE.

I select it and on the next screen, I select Create a new partition.
This is going to be /boot and I set the size to 16MB and select primary.
On Partition settings screen, I choose Use as Ext2, Mount point /boot, and
Bootable flag on.  Then I choose Done setting up the partition.

Next I select to automatically partition the remaining free space that
results in two logical partitions 15.1 GB ext4 mount point / and 693.1
MB swap.

Next I choose Configure encrypted volumes and get a screen that tells
that before encrypted volumes can be configured, current partitioning
scheme has to be written to disk.  I then go ahead and select yes to
write the changes to disk.

After writing is done, I get screen that has two entries: Create
encrypted volumes and Finish.  I choose the first and on next screen
select the ext4 device and swap device to encrypt.  Then I get screen
that shows partition settings of the ext4 partition.  Mount point is /
as it should.  I choose the defaults except not to erase data and then
Done with setting up the partition.

Then I do the same with the swap partition and after that I again get
the screen that has two choices: Create encrypted volumes and Finish.
Now I choose the latter and get screens that ask for encryption password
for both of the encrypted partitions.

After that I get again the main Partition disk screen.  It now shows
three partitions:

#1 primary 14.7 MB   ext2 /boot
#5 logical 15.1 GB   crypto   (sdc5_crypt)
#6 logical 693.1 MB  crypto   (sdc5_crypt)

Then I select Finish partitioning and write changes to disk. That
results in red screen complaining No root file system Please correct
this from the partitioning menu.

What went wrong?  Why the root mount point disappeared? Why didn't the
process tell me earlier that something is wrong?  Or is it so that the
installer is broken?

-- Juha


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/21832.65306.873002.567...@tutpro.com



Re: Systemd Problem: No VGA after /etc/init.d/gdm3 start

2015-05-05 Thread Thomas H. George
On Tue, May 05, 2015 at 05:54:53PM +0200, Michael Biebl wrote:
> Am 05.05.2015 um 17:13 schrieb Thomas H. George:
> > Entered /etc/init.d/gdm3 start from a root console. Response was to
> > check systemctl status gdm.service and journalctl -xn. A script of the
> > output of these entries:
> > 
> > 
> > Script started on Tue 05 May 2015 10:58:05 AM EDT
> > Zebra:~# systemctl status gdm.service
> > ● gdm.service - GNOME Display Manager
> >Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
> >Active: failed (Result: start-limit) since Tue 2015-05-05 
> > 10:57:11 EDT; 1min 28s ago
> >   Process: 1920 ExecStartPre=/bin/sh -c [ "$(cat 
> > /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] 
> > (code=exited, status=1/FAILURE)
> 
> [..]
> 
> > How do I correct this problem?
> 
> 
> What does /etc/X11/default-display-manager say?
> dpkg-reconfigure gdm3 and selecting gdm3 as default display manager
> should fix the problem.

No luck. This did restore the login screen but as soon as I logged the
screen went blank and the no vga signal found.
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505162850.ga28...@tomgeorge.info



Re: no root file system after encryption

2015-05-05 Thread Juha Heinanen
Patrick Bartek writes:

> More details of exactly what you did would help. That is. Did you use
> LVM or Primary/Logical partitioning? Which partitions did you encrypt?
> You didn't encrypt /boot did you?  Did you let the installer handle the
> partitioning and encryption or did you set up encryption after the OS
> installation.  Etc.

Ok, I'll try again and report all the details.

-- Juha


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/21832.62889.957561.197...@tutpro.com



Re: no root file system after encryption

2015-05-05 Thread Juha Heinanen
David Christensen writes:

> This video shows creating an unencrypted /boot partition and an 
> encrypted partition with LVM with swap and root:
> 
>  https://www.youtube.com/watch?v=Z9pn2PYbDdA

I'll watch the video, but I was not planing to use LVM and my problem is
related to non-LVM partition encyrption.

> Briefly -- to obtain encrypted file systems, the process is to create 
> partitions, mark them as encrypted volumes, configure the encrypted 
> volumes, and then put LVM and/or file systems into the encrypted
> volumes.

And that does not work as I tried to describe.  After I have properly
configured encrypted root partition (mount point is /) and then write the
partition to disk, the mount point has disappeared and I get the error
message "No root file system defined".  When I have more time, I'll send
detailed email about the steps.

-- Juha




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/21832.62828.97395.37...@tutpro.com



Re: no root file system after encryption

2015-05-05 Thread Patrick Bartek
On Mon, 04 May 2015, Juha Heinanen wrote:

> I'm trying to install debian jessie with three partitions: /boot, /,
> and swap.  i'm able to create and encrypt the partitions fine, but
> when I then try to changes to disk, installer complains:
> 
>   No root file system defined, please correct this from partitioning
> menu.
> 
> The second partition had / as its mount point before the encryption.
> Why was it lost?  What is the correct procedure to create the
> encrypted partitions?
> 
> Also, looks like it is not possible to correct anything from
> partitioning menu because of the encryption.

More details of exactly what you did would help. That is. Did you use
LVM or Primary/Logical partitioning? Which partitions did you encrypt?
You didn't encrypt /boot did you?  Did you let the installer handle the
partitioning and encryption or did you set up encryption after the OS
installation.  Etc.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505094423.469a3...@debian7.boseck208.net



Re: no root file system after encryption

2015-05-05 Thread David Christensen

On 05/04/2015 11:02 AM, Juha Heinanen wrote:

I'm trying to install debian jessie with three partitions: /boot, /, and
swap.  i'm able to create and encrypt the partitions fine, but when I
then try to changes to disk, installer complains:
   No root file system defined, please correct this from partitioning menu.
The second partition had / as its mount point before the encryption.
Why was it lost?  What is the correct procedure to create the encrypted
partitions?
Also, looks like it is not possible to correct anything from
partitioning menu because of the encryption.


This video shows creating an unencrypted /boot partition and an 
encrypted partition with LVM with swap and root:


https://www.youtube.com/watch?v=Z9pn2PYbDdA


Briefly -- to obtain encrypted file systems, the process is to create 
partitions, mark them as encrypted volumes, configure the encrypted 
volumes, and then put LVM and/or file systems into the encrypted volumes.



David


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5548f241.3050...@holgerdanske.com



Motorola Bluetooth adaptor not working on jessie

2015-05-05 Thread Ayan Agrawal
Hi all. I have an HP pavillion dv6 6131tx laptop late 2011 laptop with Motorola 
Bluetooth 3.0 hs adaptor. It works fine on Windows but not on Debian Jessie (64 
bit gnome) (I have both windows and debian installed as dual boot). Bluetooth 
menu shows on the panel. It also tries to search for devices but is not able to 
do so nor does my laptop's bluetooth shows up on any bluetooth device although 
I have set it visisble. Another fact: I can't turn it off from the panel. I 
then googled it to get some idea and came to know running lspci command tells 
information about pci buses and devices and I ran it and found that bluetooth 
device doesn't show up there too. I am new to Linux and Debian. Any help is 
highly appreciated.
P.S. It used to work on Wheezy 7.8.

Thanks folks!


Re: Systemd Problem: No VGA after /etc/init.d/gdm3 start

2015-05-05 Thread Michael Biebl
Am 05.05.2015 um 17:13 schrieb Thomas H. George:
> Entered /etc/init.d/gdm3 start from a root console. Response was to
> check systemctl status gdm.service and journalctl -xn. A script of the
> output of these entries:
> 
> 
> Script started on Tue 05 May 2015 10:58:05 AM EDT
> Zebra:~# systemctl status gdm.service
> ● gdm.service - GNOME Display Manager
>Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
>Active: failed (Result: start-limit) since Tue 2015-05-05 
> 10:57:11 EDT; 1min 28s ago
>   Process: 1920 ExecStartPre=/bin/sh -c [ "$(cat 
> /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] 
> (code=exited, status=1/FAILURE)

[..]

> How do I correct this problem?


What does /etc/X11/default-display-manager say?
dpkg-reconfigure gdm3 and selecting gdm3 as default display manager
should fix the problem.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: Systemd Problem: No VGA after /etc/init.d/gdm3 start

2015-05-05 Thread Darac Marjal
On Tue, May 05, 2015 at 11:13:15AM -0400, Thomas H. George wrote:
> Entered /etc/init.d/gdm3 start from a root console. Response was to
> check systemctl status gdm.service and journalctl -xn. A script of the
> output of these entries:
> 
> 
> Script started on Tue 05 May 2015 10:58:05 AM EDT
> Zebra:~# systemctl status gdm.service
> ● gdm.service - GNOME Display Manager
>Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
>Active: failed (Result: start-limit) since Tue 2015-05-05 
> 10:57:11 EDT; 1min 28s ago
>   Process: 1920 ExecStartPre=/bin/sh -c [ "$(cat 
> /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] 
> (code=exited, status=1/FAILURE)
> 
> May 05 10:57:09 Zebra systemd[1]: gdm.service: control process exited, 
> code=exited status=1
> May 05 10:57:09 Zebra systemd[1]: Failed to start GNOME Display 
> Manager.
> May 05 10:57:09 Zebra systemd[1]: Unit gdm.service entered failed 
> state.
> May 05 10:57:09 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
> Invalid argument
> May 05 10:57:11 Zebra systemd[1]: gdm.service start request repeated 
> too quickly, refusing to start.
> May 05 10:57:11 Zebra systemd[1]: Failed to start GNOME Display 
> Manager.
> May 05 10:57:11 Zebra systemd[1]: Unit gdm.service entered failed 
> state.
> May 05 10:57:11 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
> Invalid argument
> Zebra:~# journalctl -xn
> 
-- Logs begin at Tue 2015-05-05 10:37:24 EDT, end at Tue 2015-05-05 10:57:11 
EDT. --
> May 05 10:57:08 Zebra systemd[1]: Unit gdm.service entered failed 
> state.
> May 05 10:57:08 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
> Invalid argument
> May 05 10:57:09 Zebra systemd[1]: gdm.service: control process exited, 
> code=exited status=1
> May 05 10:57:09 Zebra systemd[1]: Failed to start GNOME Display 
> Manager.
> -- Subject: Unit gdm.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit gdm.service has failed.
> -- 
> -- The result is failed.
> May 05 10:57:09 Zebra systemd[1]: Unit gdm.service entered failed 
> state.
> May 05 10:57:09 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
> Invalid argument
> May 05 10:57:11 Zebra systemd[1]: gdm.service start request repeated 
> too quickly, refusing to start.
> May 05 10:57:11 Zebra systemd[1]: Failed to start GNOME Display 
> Manager.
> -- Subject: Unit gdm.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit gdm.service has failed.
> -- 
> -- The result is failed.
> May 05 10:57:11 Zebra systemd[1]: Unit gdm.service entered failed 
> state.
> May 05 10:57:11 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
> Invalid argument
> 
Zebra:~# exit
> 
> Script done on Tue 05 May 2015 10:59:22 AM EDT
> 
> 
> How do I correct this problem?

I'd look first at /var/log/Xorg.0.log. GDM isn't reporting any errors
(at least nothing useful) so it might be X itself failing (for example a
X-driver/kernel-driver mismatch could cause this).

> 
> Tom
> 
> 
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/20150505151314.ga27...@tomgeorge.info
> 

-- 
For more information, please reread.


signature.asc
Description: Digital signature


[SOLVED] Re: New Jessie Install: Laptop fan doesn't run

2015-05-05 Thread Ralph Katz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 05/04/2015 11:01 PM, Glen Reesor wrote:
> On 2015-05-03 16:00, Glen Reesor wrote:
>> 
>> 
>> On 2015-05-03 14:20, Ralph Katz wrote:
> Please don't top post; it makes following the thread harder. My
> reply follows below...
> 
> On 05/02/2015 07:23 PM, Glen Reesor wrote:
> I've done some more research, and it appears that the fan
> control is only happening at boot, in *both* the installed
> system and the livecd. So if the machine is hot at boot,
> the fan runs and stays running regardless of temperature
> changes. If the machine is cool at boot, the fan doesn't
> run, regardless of temperature changes.
> 
> I've discovered interesting behavior with the sensors
> command and acpi -t.
> 
> Sensors currently shows: acpitz-virtual-0 Adapter: Virtual
> device temp1:+40.0°C  (crit = +100.0°C) <-
> This never changes after boot
> 
> coretemp-isa- Adapter: ISA adapter Core 0:
> +56.0°C  (high = +100.0°C, crit = +100.0°C) Core 1:
> +57.0°C  (high = +100.0°C, crit = +100.0°C)
> 
> However acpi -t shows: Thermal 0: ok, 40.0 degrees C
> 
> The temp1 line reported by sensors never changes after
> boot, and neither does the output from acpi -t. So it looks
> like acpi is looking at the wrong temperature, as it's only
> the Core 0 and Core 1 temperatures that change.
> 
> On 2015-05-02 10:02, Glen Reesor wrote:
>> Some more information...
>> 
>> I have confirmed that the fan runs when the Jessie livecd
>> is running, but the fan doesn't run for amd64 or i386
>> installations. I've compared syslog, daemon.log, and
>> lsmod and found:
>> 
>> syslog: Both livecd and amd64 installation have these
>> lines: kernel: [0.020564] CPU0: Thermal monitoring
>> enabled (TM1) kernel: [0.943898] thermal LNXTHERM:00:
>> registered as thermal_zone0 kernel: [0.943904] ACPI:
>> Thermal Zone [TZ01] (50 C)
>> 
>> syslog: There is a slight difference in the following
>> line: livecd: kernel: [3.144083] acpi device:3a:
>> registered as cooling_device0 amd64: kernel: [
>> 8.712124] acpi device:3a: registered as cooling_device2
>> 
>> lsmod has slight differences: livecd: thermal
>> 17343  0 thermal_sys27122  3
>> video,thermal,processor
>> 
>> amd64: thermal17559  0 thermal_sys
>> 27642  3 video,thermal,processor
>> 
>> In daemon.log, the amd64 installation has the following
>> lines (but they may be the result of installing the
>> sensors package, which the livecd does not have): May  2
>> 08:36:48 amd64 sensors[492]: acpitz-virtual-0 May  2
>> 08:36:48 amd64 sensors[492]: Adapter: Virtual device May
>> 2 08:36:48 amd64 sensors[492]: temp1: +0.0°C  (crit =
>> +100.0°C) May  2 08:36:48 amd64 sensors[492]:
>> coretemp-isa- May  2 08:36:48 amd64 sensors[492]:
>> Adapter: ISA adapter May  2 08:36:48 amd64 sensors[492]:
>> Core 0: +25.0°C  (high = +100.0°C, crit = +100.0°C) May
>> 2 08:36:48 amd64 sensors[492]: Core 1: +26.0°C  (high =
>> +100.0°C, crit = +100.0°C)
>> 
>> Any help would be greatly appreciated.
>> 
>> Glen
>> 
>> On 2015-04-30 20:40, Glen Reesor wrote:
>>> I have done a fresh install of Jessie on an old Acer
>>> laptop and the fan never runs, so it overheats.
>>> Interestingly, the fan *does* run while Jessie is being
>>> installed.
>>> 
>>> Has anyone had similar problems? Does anyone have
>>> suggestions on how to diagnose this?
>>> 
>>> Thanks.
> 
> Glen, I'm not sure how much this will help, but my old Acer laptop 
> running Jessie seems to be fine out of the box.  Here are some 
> comparable outputs [pasted as quotes to prevent line wrapping]:
> 
> ralph@spike2 ~$ zgrep sensors /var/log/daemon.log* 
> /var/log/daemon.log.1:Apr 27 15:48:53 spike2 sensors[864]: 
> acpitz-virtual-0 /var/log/daemon.log.1:Apr 27 15:48:53
> spike2 sensors[864]: Adapter: Virtual device 
> /var/log/daemon.log.1:Apr 27 15:48:53 spike2 sensors[864]: 
> temp1:+50.0°C  (crit = +87.0°C) 
> /var/log/daemon.log.1:Apr 27 15:48:53 spike2 sensors[864]: 
> temp2:+45.0°C  (crit = +105.0°C) 
> /var/log/daemon.log.1:Apr 27 15:48:53 spike2 sensors[864]: 
> coretemp-isa- /var/log/daemon.log.1:Apr 27 15:48:53
> spike2 sensors[864]: Adapter: ISA adapter 
> /var/log/daemon.log.1:Apr 27 15:48:53 spike2 sensors[864]:
> Core 0:   +44.0°C  (high = +85.0°C, crit = +85.0°C) 
> /var/log/daemon.log.1:Apr 27 15:48:53 spike2 sensors[864]:
> Core 1:   +47.0°C  (high = +85.0°C, crit = +85.0°C) 
> ralph@spike2 ~$ acpi -t -i Thermal 0: ok, 39.0 degrees C 
> Thermal 0: trip point 0 switches to mode critical at
> temperature 105.0 degrees C Thermal 1: ok, 39.0 deg

Systemd Problem: No VGA after /etc/init.d/gdm3 start

2015-05-05 Thread Thomas H. George
Entered /etc/init.d/gdm3 start from a root console. Response was to
check systemctl status gdm.service and journalctl -xn. A script of the
output of these entries:


Script started on Tue 05 May 2015 10:58:05 AM EDT
Zebra:~# systemctl status gdm.service
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
   Active: failed (Result: start-limit) since Tue 2015-05-05 
10:57:11 EDT; 1min 28s ago
  Process: 1920 ExecStartPre=/bin/sh -c [ "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] 
(code=exited, status=1/FAILURE)

May 05 10:57:09 Zebra systemd[1]: gdm.service: control process exited, 
code=exited status=1
May 05 10:57:09 Zebra systemd[1]: Failed to start GNOME Display 
Manager.
May 05 10:57:09 Zebra systemd[1]: Unit gdm.service entered failed 
state.
May 05 10:57:09 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
Invalid argument
May 05 10:57:11 Zebra systemd[1]: gdm.service start request repeated too 
quickly, refusing to start.
May 05 10:57:11 Zebra systemd[1]: Failed to start GNOME Display 
Manager.
May 05 10:57:11 Zebra systemd[1]: Unit gdm.service entered failed 
state.
May 05 10:57:11 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
Invalid argument
Zebra:~# journalctl -xn

-- Logs begin at Tue 2015-05-05 10:37:24 EDT, end at Tue 2015-05-05 10:57:11 
EDT. --
May 05 10:57:08 Zebra systemd[1]: Unit gdm.service entered failed 
state.
May 05 10:57:08 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
Invalid argument
May 05 10:57:09 Zebra systemd[1]: gdm.service: control process exited, 
code=exited status=1
May 05 10:57:09 Zebra systemd[1]: Failed to start GNOME Display 
Manager.
-- Subject: Unit gdm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit gdm.service has failed.
-- 
-- The result is failed.
May 05 10:57:09 Zebra systemd[1]: Unit gdm.service entered failed 
state.
May 05 10:57:09 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
Invalid argument
May 05 10:57:11 Zebra systemd[1]: gdm.service start request repeated too 
quickly, refusing to start.
May 05 10:57:11 Zebra systemd[1]: Failed to start GNOME Display 
Manager.
-- Subject: Unit gdm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit gdm.service has failed.
-- 
-- The result is failed.
May 05 10:57:11 Zebra systemd[1]: Unit gdm.service entered failed 
state.
May 05 10:57:11 Zebra systemd[1]: Failed to enqueue OnFailure= job: 
Invalid argument

Zebra:~# exit

Script done on Tue 05 May 2015 10:59:22 AM EDT


How do I correct this problem?

Tom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505151314.ga27...@tomgeorge.info



Re: Colorized Prompts Problem - Thanks for the Deconstruction

2015-05-05 Thread Thomas H. George
On Mon, May 04, 2015 at 12:31:15PM -0500, David Wright wrote:
> Quoting Thomas H. George (li...@tomgeorge.info):
> > On Mon, May 04, 2015 at 06:54:40AM +, Bonno Bloksma wrote:
> > > Hi,
> > > 
> > > > I entered the following in .bashrc
> > > > 
> > > >PS1='\033[01;33m\h:\w\$ \033[00m'   
> > > > 
> > > > to colorize the prompt (very handy to find the prompt when a command
> > > > fills the console screen with lines of text)
> > > > 
> > > > The only problem occurs when the next entry is more than one line.  In 
> > > > that
> > > > case the entry wraps around without moving to a new line.
> > > 
> > > I had the same problem using the prompt I found at first, I think it is 
> > > the same you are using. It seems there is a problem in closing the ANSI 
> > > code string.
> > > Someone else gave me this:
> > >   PS1='\[\e[0;31m\]${debian_chroot:+($debian_chroot)}\h:\w\$\[\e[m\] '
> > > This does not have the problem, I have been using this now for over a 
> > > year, no problems at all.
> > > 
> > > Bonno Bloksma
> > > 
> > Thank you, this works while nothing else did.  The sequences to start
> > and end coloring are different and the colors are different too.
> 
> Perhaps it's worth deconstructing this into its constituents:
> 
> '\[\e[0;31m\]${debian_chroot:+($debian_chroot)}\h:\w\$\[\e[m\] '
> 
> Take out ${debian_chroot:+($debian_chroot)}
> As explained before, this prints the value of $debian_chroot but uses
> the :+ trick to avoid printing () when $debian_chroot is empty/unset.
> 
> '\[\e[0;31m\]\h:\w\$\[\e[m\] '
> 
> Take out the two \[ and \] brackets.
> As explained before, these brackets must enclose anything that doesn't
> advance the cursor, ie the colouring strings. That tells bash to
> ignore those strings in calculating how much room the prompt has taken
> up. That's the fix for your original complaint.
> 
> '\e[0;31m\h:\w\$\e[m '
> 
> Take out \h:\w\$ and that space at the end.
> That's the prompt that you want to see coloured. (In your original,
> the space at the end of the prompt was coloured too.)
> 
> '\e[0;31m' and '\e[m'
> 
> Now all that remains is colour-on and colour-off.
> 
> Off: Where you had \033[00m this has \e[m because the 00 before the
> m is unnecessary (blank is zero), and \e is a clearer way of writing
> the ESCape character (octal 33) in more modern versions of bash.
> (The latter eliminates one source of confusion: the mixture of octal
> and decimal numbers.)
> 
> On: Similarly, where you had \033[01;33m this has \e[0;31m which,
> as pointed out below, changes the foreground colour to normal red.
> So you should set it back to \e[1;33m
> 
> It is harmless, but that leading 0 that you had in 01;33m could be a
> cause for confusion; the numbers before the m are *decimal* whereas
> \033 is octal. So 33m actually means 30 + 3 m where 30 is the
> foreground colour, 3 is the yellow, and m is colouring rather than,
> say, moving the cursor.
> 
> Cheers,
> David.
> 
Your explanation is very helpful, converts the jumble I copied from a
website into a logical sequence of instructions. I really appreciate
being able to understand the meaning of the prompt.

Tom

> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/20150504173115.GA12593@alum
> 
> 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505135311.ga26...@tomgeorge.info



Re: irqbalance affinity problem

2015-05-05 Thread Johann Spies
On 5 May 2015 at 15:32, Pol Hallen  wrote:


> Can you do some benchmarks with/without those options?
>

Good suggestion. Thanks.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


Re: irqbalance affinity problem

2015-05-05 Thread Pol Hallen

What do I look for in the Bios (which is not an easy path to walk on the
server)?


it's too hard remember exaclty settings of bios...


I can then in /etc/default/irqbalance put OPTIONS = "--intpolicy=ignore"
but I am not sure what the effect will be on the server performance.


might be useful do audit of system and undestand if these messages are 
"only" some warnings (so you can serenely ignore it setting: 
"--intpolicy=ignore") or no.



Do you have knowledge of such a setting?


many many years ago.

Can you do some benchmarks with/without those options?

Pol


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5548c673.3070...@fuckaround.org



Re: irqbalance affinity problem

2015-05-05 Thread Johann Spies
On 5 May 2015 at 15:11, Pol Hallen  wrote:

> Linux kbase 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)
>> x86_64 GNU/Linux
>>
>
> have you tried with other kernels and/or check bios settings?
>

Thanks for your attention to my question.

No.  I do not want to reboot the server often.

What do I look for in the Bios (which is not an easy path to walk on the
server)?


I see in the changelog of the Debian package that the suggested solution as
showed by the Ubuntu bug report was accepted as part of the Debian
Package.

I can then in /etc/default/irqbalance put OPTIONS = "--intpolicy=ignore"

but I am not sure what the effect will be on the server performance.

Do you have knowledge of such a setting?

The error message suggests that "subset" is the default choice for this
setting.



Regards
Johann


On 5 May 2015 at 15:24, Johann Spies  wrote:

>
>
> On 5 May 2015 at 15:11, Pol Hallen  wrote:
>
>> Linux kbase 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)
>>> x86_64 GNU/Linux
>>>
>>
>> have you tried with other kernels and/or check bios settings?
>>
>
> Thanks for your attention to my question.
>
> No.  I do not want to reboot the server often.
>
> What do I look for in the Bios (which is not an easy path to walk on the
> server)?
>
>
> I see in the changelog of the Debian package that the suggested solution
> as showed by the Ubuntu bug report was accepted as part of the Debian
> Package.
>
> I can then in /etc/default/irqbalance put OPTIONS = "--intpolicy=ignore"
>
> but I am not sure what the effect will be on the server performance.
>
> Do you have knowledge of such a setting?
>
> The error message suggests that "subset" is the default choice for this
> setting.
>
>
> Regards
> Johann
>
>
> --
> Because experiencing your loyal love is better than life itself,
> my lips will praise you.  (Psalm 63:3)
>



-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


Solved : Upgrade to Jessie : some network problems

2015-05-05 Thread Nicolas FRANCOIS
Le Mon, 4 May 2015 11:52:18 +0200,
Petter Adsen  a écrit :

> Are you sure you might not have gotten a different IP address after
> the upgrade? And what does the line for /mnt/nfssave in /etc/fstab on
> the client and the appropriate line in /etc/exports on the server say?

That solved the trick :-(

I had static IPs on all my network, so I thought the updgrade to Jessie
would keep it this way. But I have two wifi routeurs on my network that
provide DHCP to the wifi net, and clearly ALSO on the wired net.

Thank you for pointing me on this one, I was starting to become
crazy ;-)

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505151540.3a767...@gaston.baronie.vez



Re: irqbalance affinity problem

2015-05-05 Thread Pol Hallen

Linux kbase 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)
x86_64 GNU/Linux


have you tried with other kernels and/or check bios settings?

Pol


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5548c182.8020...@fuckaround.org



Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread David Wright
Quoting Charles Kroeger (ckro...@frankensteinface.com):
> On Tue, 05 May 2015 04:00:02 +0200
> David Wright  wrote:
> 
> > Does   dmesg | grep -i firmware   show the firmware being loaded?
> 
> root@mundo:/home/charles# dmesg | grep -i firmware[1.400040] platform
> microcode: firmware: agent loaded amd-ucode/microcode_amd.bin into
> memry[   25.257358] usb 7-2: ath9k_htc: Firmware htc_9271.fw
> requested[   25.268624] usb 7-2: firmware: agent loaded htc_9271.fw into
> memoryroot@mundo:/home/charles#
> 
> Yes it's there, the ath9k_htc_9271.fw

What do /sbin/iwconfig and /sbin/ifconfig show?

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150505130437.GA5597@alum



Re: irqbalance affinity problem

2015-05-05 Thread Johann Spies
On 5 May 2015 at 14:56, Pol Hallen  wrote:


> which kernel do you use?
>

Linux kbase 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64
GNU/Linux

Regards
Johann
-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


Re: irqbalance affinity problem

2015-05-05 Thread Pol Hallen

May  5 12:26:28 kbase /usr/sbin/irqbalance: irq 104 affinity_hint subset
empty
May  5 12:26:28 kbase /usr/sbin/irqbalance: irq 105 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 98 affinity_hint subset
empty

[...]

which kernel do you use?

Pol


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5548be0a.5020...@fuckaround.org



irqbalance affinity problem

2015-05-05 Thread Johann Spies
On our server with 32 cores we see this in /var/log/syslog.

May  5 12:26:28 kbase /usr/sbin/irqbalance: irq 104 affinity_hint subset
empty
May  5 12:26:28 kbase /usr/sbin/irqbalance: irq 105 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 98 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 99 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 100 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 101 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 102 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 103 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 104 affinity_hint subset
empty
May  5 12:26:38 kbase /usr/sbin/irqbalance: irq 105 affinity_hint subset
empty

I have seen a related bugreport on Ubuntu(
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1328556), but I
am not convinced that the solution it suggests is the correct one.  What
will be the effect if I put

HINTPOLICY=ignore

in /etc/default/irqbalance
on the system?

Regards
Johann
-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


Re: Penguin Wireless N USB Adapter TPE-N150USBL

2015-05-05 Thread Brian
On Mon 04 May 2015 at 19:39:33 -0400, Charles Kroeger wrote:

> After using this adapter for a few months (18 months ago) I committed out all 
> my
> wireless lines in /etc/network/interfaces and stopped using it because it kept
> breaking the connection at odd times.
> 
> I have to take a trip and this computer goes with me where I'll need to use 
> WiFi and
> so I uncommitted out my network interfaces file,  loaded the firmware (from 
> the
> think penguin help site) plugged in the adapter but nothing happens.

The non-free firmware-atheros package has the firmware for the adapter.
 
> # The loopback network interface
> 
> auto lo
> 
> iface lo inet loopback
> 
> # The primary network interface
> 
> allow-hotplug eth0
> 
> iface eth0 inet dhcp
> 
> auto wlan0

I'd be inclined to have 'allow-hotplug wlan0'.

> iface wlan0 inet dhcp
> wpa-ssid  
> wpa-psk 
> 
> I followed these instructions for the latest  firmware at the think penguin 
> help
> site for this adapter:
> 
> cd /lib/firmware
> 
> wget 
> https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_9271.fw
> wget 
> https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_7010.fw
> 
> rebooted the computer
> 
> however..the adapter is still not connected 

It's very surprising a reboot didn't bring up the interface.

> this after ifup wlan0:
> 
> # ifup wlan0
> wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
> run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
> Failed to bring up wlan0.
> 
> any suggestions to what might be missing here?

Most of the on-screen message you saw? :)

Check if the supplicant is running; 'ps ax | grep wpa'. Terminate it
with 'wpa_cli terminate'. Retry 'ifup wlan0'.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/05052015105754.eb9ae86d3...@desktop.copernicus.demon.co.uk



Re: Jessie: XFCE4 Desktop background stopped working

2015-05-05 Thread Johann Spies
Andre N Batista wrote:

>
> I suspect this might be a bug on the upgrade process. About two weeks
> ago a user whom I help had a similar complaint.
>
> What I found out was: xfdesktop had crashed and the system was
> configured to auto save sessions so it wasn't being brought up even
> after restarting the system.
>
> The solution was just:
>
> $ xfdesktop &
>
> Anyone else?
>
>
>
Thanks!  That fixed the problem.  Which files did xfdesktop change?


Now I can move back to XFCE4 again after using Gnome for a few days. :)

Regards
Johann.
-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)