date:20110703

On Sunday 03 July 2011 23:56:30 you wrote:
> On Sun, 2011-07-03 at 23:40 +0100, Lisi wrote:
> > On Sunday 03 July 2011 22:35:08 Ross Boylan wrote:
> > > (see original message)
> >
> > Not a very productive instruction to those of us who have HTML display
> > turned off.
> >
> > Lisi
>
> That's interesting.  The messages are not in html.  However, I did use a
> little pseudo-XML (with angle brackets--I'm deliberately not repeating
> it here) to distinguish material I copied from the terminal.
>
> I haven't noticed problems in evolution, mutt, or thunderbird.
>
> Any opinions from anyone on whether pseudo-XML is inadvisable?
>
> Lisi, could this be a problem with your particular mail client?

Not that I know of - but that doesn't mean that it isn't so.  Does anyone 
know?   I am using Kmail 1.9.9. 

I shall have to look into it.  Google and ask on another list etc.  I am using 
Kmail 1.9.9.  I'll get back to you - I hope.  I have a memory that resembles 
a sieve more than anything else. :-(

Lisi



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107040655.02725.lisi.re...@gmail.com

Squeeze - Virtualbox - No Installable Kernel

2011-07-03 Thread scottmaccal

Greetings,

I recently installed VirtualBox on Squeeze by following these 
instructions: http://wiki.debian.org/VirtualBox. During the install 
of an Ubuntu 8.04 server virtual machine I got the following error: 
No installable kernel was found in the defined APT sources. Has 
anyone else encountered this and found a fix? If so, could they 
please share?

Thank you,

Scott


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110704035920.297c710e...@smtp.hushmail.com

kvm

2011-07-03 Thread Khosrow Hassani

Hi,
I am running kvm 0.12.5 from Squeeze. the problem I am having is that kvm -hda 
disk1.img -hdb disk2.img doesn't give me 2 drives in my Windows xp inside kvm, 
even when I run it as root. only the first disk where windows is installed 
shows up!  I created the other image using kvm-img with qcow2 format. Also, the 
-usb works only for root but not for normal user! when I run it as normal user 
I get permission error.

any idea?
thanks, Khosrow

Re: monitor detection maybe not working


On 07/03/2011 04:27 PM, Brian wrote:

On Sun 03 Jul 2011 at 16:06:24 -0700, Paul Scott wrote:


On 07/02/2011 04:04 AM, Claudius Hubig wrote:

I don't think he did. :)


Paul Scott   wrote:

On 07/01/2011 03:46 PM, Brian wrote:

On Fri 01 Jul 2011 at 15:19:21 -0700, Paul Scott wrote:

  1024x768   60.0*
  800x60060.3 56.2
  848x48060.0
  640x48059.9
My LCD monitor's native resolution is 1280x1024

xrandr believes VGA-1 is only capable of 1024x768.  Why do you believe
1280x1024 is possible?

I didn't show all of xrandr:

You've not shown it here, either. :)


Oops!  My current screen setup in addition to the wrong resolution has a 
vertical displacement.


Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1024x768   60.0*
   800x60060.3 56.2
   848x48060.0
   640x48059.9
VGA-2 disconnected (normal left inverted right x axis y axis)
TV-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   720x57650.0 +
   1024x768   50.0*
   800x60050.0
   720x48050.0
   640x48050.0
   400x300   100.0
   320x240   100.0
   320x200   100.0
DVI-D-1 disconnected (normal left inverted right x axis y axis)

Does this not say that the card will support up to 4096x4096 ?



No. 4096x4096 is the maximum virtual screen size.


Where do you find the output description?  I didn't see it in man xrandr.

Thanks,

Paul




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

Archive: http://lists.debian.org/4e1124d4.6050...@ultrasw.com

Re: message formatting and pseudo XML [was Re: disk problems: which ATA?]

2011-07-03 Thread David Jardine

On Sun, Jul 03, 2011 at 03:56:30PM -0700, Ross Boylan wrote:
> On Sun, 2011-07-03 at 23:40 +0100, Lisi wrote:
> > On Sunday 03 July 2011 22:35:08 Ross Boylan wrote:
> > > (see original message)
> > 
> > Not a very productive instruction to those of us who have HTML display 
> > turned 
> > off.
> > 
> > Lisi
> > 
> That's interesting.  The messages are not in html.  However, I did use a
> little pseudo-XML (with angle brackets--I'm deliberately not repeating
> it here) to distinguish material I copied from the terminal.
> 
> I haven't noticed problems in evolution, mutt, or thunderbird.
> 
> Any opinions from anyone on whether pseudo-XML is inadvisable?
> 

I don't even know what pseudo-XML is, but your message was clearly 
displayed for me (with indentations, without raw markup) by mutt with 
a more-or-less default configuration.

David


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110704002627.GA3833@gennes.augarten

Re: mdadm and UUIDs for its component drives

2011-07-03 Thread Luke Kenneth Casson Leighton

On Mon, Jun 27, 2011 at 1:59 PM, Philip Hands  wrote:

>>  ok, i bring in phil now, who i was talking to yesterday about this.
>> what he said was (and i may get this wrong: it only went in partly) -
>> something along the lines of "remember to build the drives with
>> individual mdadm bitmaps enabled".  this will save a great deal of
>> arseing about when re-adding drives which didn't get properly added:
>> only 1/2 a 1Tb drive will need syncing, not an entire drive :)  the
>> bitmap system he says has hierarchical granularity apparently.
>
> What I said was: "internal" bitmaps

 ahh.  yes.  i missed the word "internal" but heard the good bits,
then looked up the man page and went "ohh, ok, that must be it".  i
get there in the end :)

>> also, he recommended taking at least one of the external drives *out*
>
> I think I said: WTF?

 ha ha :)

>  You buy a machine that had 4 hot swap SATA bays,
> and you're plugging crappy external USB drives into it instead?  Are you
> mental?  (or at least, if I didn't say that out loud, that's what I was
> thinking ;-)

 i seem to remember the incredulity which definitely had the words
"are you mental??" behind it

> I must say that I'm a little beffuddled about how you managed to make
> the system sensitive to which device contains which MD component -- I
> seem to remember you mentioning that you had devices listed in your
> mdadm.conf -- just get rid of them.

 well, i may have implied that, on account of not being able to
express it - i get it now: the things i thought were "devices" are
actually the UUIDs associated with the RAID array...

> ARRAY /dev/md/2 metadata=1.2 UUID=65c09661:02fc3a16:402916d3:5d4987f4 
> name=sheikh:2

 ... just like this.

> No mention of devices, which is a good job because that machine seems
> to randomise the device mapping on each boot, and is capable of moving
> them about when running if you pop the drive out of the machine and back
> in again.

 yehhs, i noticed that.  even the bloody boot drive comes up as
/dev/sde occasionally.  last reboot i was adding drive 4 to the array,
it was named /dev/sda.  kinda freaky.

 ok.

 so.

 let's have a go at some updating the docs...

 DESCRIPTION
   RAID  devices  are  virtual devices created from two or more real block
   devices.  This allows multiple devices (typically disk drives or parti‐
   tions  thereof)  to be combined into a single device to hold (for exam‐
   ple) a single filesystem.  Some RAID levels include redundancy  and  so
   can survive some degree of device failure.

   Linux  Software  RAID  devices are implemented through the md (Multiple
   Devices) device driver.  UUIDs are used internally through Linux Software
   RAID to identify any device that is part of a RAID.  In this
way, names may
   change but the innocent are protected.

 ok, scratch that last sentence :)

   Linux  Software  RAID  devices are implemented through the md (Multiple
   Devices) device driver.  UUIDs are used internally in Linux Software RAID
   to identify any device that is part of a RAID, thus ensuring
that even if the
   name changes (such as may happen if devices are removed and placed
   into another system, or if using removable hot-swappable media) Linux
   RAID can still correctly identify the component devices.

can we start with that - what you think, martin?  it's right at the
top: it spells things out, and it makes linux RAID look good :)  i'll
try to find appropriate places to put the same info, but the page is
really quite long.  perhaps on "--add" somewhere?

 l.

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/capweedxp2gfowv0xj9x6+0bmfi85w8mndr4czgy9xhv7cp1...@mail.gmail.com

Re: disk problems: which ATA?

On Sun, 2011-07-03 at 23:48 +0100, Brian wrote:
> On Sun 03 Jul 2011 at 11:25:18 -0700, Ross Boylan wrote:
> 
> > How can I tell which ata device is which hard drive?  It's come up
> > several times for me, most recently with
> > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> 
> For ata1.00 on this machine:
> 
>ls -l /sys/class/scsi_disk/0:0:0:0/device/ | grep block:
Does ata1 always go with scsi 0:0:0:0?
and ata2 with scsi 1:0:0:0?
etc?

The information in the directory you mention gets me from the scsi
location to the symbolic drive (e.g., sda)--which is good to know.  But
I'm not sure how to go from ata -> scsi.
> 
> > I'd also welcome advice about the disk problems, but I was hoping to
> > raise the odds of an answer by keeping it simple :)
> 
> You thought devising an answer to your first question would be easy?
Neither I nor my real sysadmin could figure it out.  I was hoping it
would be easy for someone :)

> I've just spent the best part of two hours on it! 
Thank you very much!

> No time now to sort
> out your disk problem. :)
I have survived my reboot, and all the LVs not backed by the bad disk seem OK.

That startup was interesting: the filesystems backed by the bad disk
were mounted; an ext3 volume replayed the journal and a reiser volume
started an fsck.  The latter bombed part way through and various
hardware looking errors popped up.  I got dropped into the startup
subshell with only / mounted.  I issued mount -a and proceeded with the
boot.

LVM tools (I tried lvs) still aren't getting anything but errors,
concluding with the message
  Couldn't find all physical volumes for volume group daisy.
  Volume group "daisy" not found
which is pretty odd, since I'm running on volumes from daisy.

Maybe if I pull the hard drive completely LVM will be happier.

Ross

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1309738194.11383.10.ca...@corn.betterworld.us

Re: OT: CamaleÃ³n

2011-07-03 Thread William Hopkins

On 07/03/11 at 02:46pm, CamaleÃ³n wrote:
> On Sun, 03 Jul 2011 03:26:52 +, T o n g wrote:
> 
> > On Sat, 02 Jul 2011 12:36:14 +1000, Scott Ferguson wrote:
> > 
> >> you're best sticking with CamaleÃ³n if possible - she does run Gnome and
> >> . . .
> > 
> > I don't know western names well and I had always thought that CamaleÃ³n
> > is a man, although being "overly" polite (than ordinary man).
> 
> :-)
> 
> "CamaleÃ³n" is a sort of nickname I chose long time ago because of the 
> openSUSE mascot (Geeko). It translates as "Chameleon" in English.
>  
> > Is CamaleÃ³n really a girl?
> > 
> > Just curious.
> 
> Yes, I am. 

This explains the politeness, but not the uncanny ability to find relevant
bugreports within minutes.

That surely cannot be a trait imparted by gender.

-- 
Liam


signature.asc
Description: Digital signature

Re: disk problems: which ATA?

2011-07-03 Thread Pablo Sánchez


Ross, maybe it's been suggested, but running smartctl -i /dev/sdb on all drives,
you could get serial numbers. If you get all but one, open the case, identify 
those
you already listed on smartctl , the other(s) one(s) are the problematic ones.

I had to do it some time ago.

Pablo Sánchez


On Sun, 2011-07-03 at 19:19 +, Camaleón wrote:

On Sun, 03 Jul 2011 11:25:18 -0700, Ross Boylan wrote:


How can I tell which ata device is which hard drive?  It's come up
several times for me, most recently with ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen

(...)

You can:

- Run "smartctl -i /dev/sdb | grep -i model"

Except the drive isn't responding to smartctl (see original message).
I tried adding -T permissive, but all that gets me is
Short INQUIRY response, skip product id
(curiously, no error about command failed).

- Then "dmesg | grep -i ata2"
- To finally compare by hdd model :-)

That works for my current machine.  But on another machine I want to
figure out which drive an error message goes with, and there are 2
identical drivers.  I suppose that even if I new which sd device the ata
went with, I still wouldn't be sure which physical drive that was...

As per the error itself, you can use the manufacturer hard disk
diagnostic tools which uses to run from a LiveCD and will provide
accurate results about your hdd health and status.

OTOH, I've also seen that kind of error coming from bad sata cable or bad
sit connection to motherboard/disk. You may also check this.

I think I already tried reseating, but I suppose it's worth trying
again.  I'm concerned if I power down I may not be able to get back up,
since the failing hard disk is actually part of an LVM volume group.  I
am also unable to get information on that VG right now.

Most of the logical vomes in the group are backed by other hard drives,
but I'm not quite sure what will happen if the disk is toast.  At the
moment, I have access to most of the LVs, even though I can't get info
on the PV that contains them (!).

Ross

P.S. For the record, kernel logs need to be read carefully to figure out
which drive is ata2.  Mine had
Jun 22 09:24:10 corn kernel: [7.767461] hdf: 26563824 sectors (13600 MB) 
w/256KiB Cache, CHS=26353/16/63
Jun 22 09:24:10 corn kernel: [7.798391] hdf: cache flushes not supported
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: New USB device found, 
idVendor=04b8, idProduct=011e
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: New USB device strings: 
Mfr=1, Product=2, SerialNumber=0
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: Product: EPSON Scanner
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: Manufacturer: EPSON
Jun 22 09:24:10 corn kernel: [7.967458]  hdf:<6>ata2.00: ATA-8: 
ST31000340AS, SD15, max UDMA/133
Jun 22 09:24:10 corn kernel: [8.135686]  hdf1 hdf2 hdf3
Jun 22 09:24:10 corn kernel: [8.129867] ata2.00: 1953525168 sectors, multi 
16: LBA48 NCQ (depth 0/32)
Jun 22 09:24:10 corn kernel: [8.241613] ata2.00: configured for UDMA/133
Jun 22 09:24:10 corn kernel: [8.129867] scsi 0:0:0:0: Direct-Access ATA 
 WDC WD2500JS-00M 02.0 PQ: 0 ANSI: 5
Jun 22 09:24:10 corn kernel: [8.290133] scsi 1:0:0:0: Direct-Access ATA 
 ST31000340AS SD15 PQ: 0 ANSI: 5

The key point is that although the message about ata2.00 (at 7.967458)
appears in the middle of the hdf information, the 2 have no relation.
It seems the<6>  indicates an asyncronous message dumped before the end
of the line.  Later comes
Jun 22 09:24:10 corn kernel: [9.520209] sd 1:0:0:0: [sdb] 1953525168 
512-byte hardware sectors (1000205 MB)
so the sector count indicates this matches ata2.00, which is the Seagate 
ST31000340AS at scsi 1:0:0:0.
I guess the first ata line (after the<6>) gives the model.





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

Archive: http://lists.debian.org/4e1100a1.1010...@adinet.com.uy

Re: monitor detection maybe not working

On Sun 03 Jul 2011 at 16:06:24 -0700, Paul Scott wrote:

> On 07/02/2011 04:04 AM, Claudius Hubig wrote:

I don't think he did. :)

>> Paul Scott  wrote:
>>> On 07/01/2011 03:46 PM, Brian wrote:
 On Fri 01 Jul 2011 at 15:19:21 -0700, Paul Scott wrote:
>  1024x768   60.0*
>  800x60060.3 56.2
>  848x48060.0
>  640x48059.9
> My LCD monitor's native resolution is 1280x1024
 xrandr believes VGA-1 is only capable of 1024x768.  Why do you believe
 1280x1024 is possible?
>
> I didn't show all of xrandr:

You've not shown it here, either. :)

> VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis)  
> 0mm x 0mm
>1024x768   60.0*
>800x60060.3 56.2
>848x48060.0
>640x48059.9
> VGA-2 disconnected (normal left inverted right x axis y axis)
> TV-1 connected 1024x768+0+0 (normal left inverted right x axis y axis)  
> 0mm x 0mm
>720x57650.0 +
>1024x768   50.0*
>800x60050.0
>720x48050.0
>640x48050.0
>400x300   100.0
>320x240   100.0
>320x200   100.0
> DVI-D-1 disconnected (normal left inverted right x axis y axis)
>
> Does this not say that the card will support up to 4096x4096 ?

No. 4096x4096 is the maximum virtual screen size.

http://www.thinkwiki.org/wiki/Xorg_RandR_1.2


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703232703.GW15615@desktop

Re: monitor detection maybe not working


On 07/02/2011 04:04 AM, Claudius Hubig wrote:

Paul Scott  wrote:

On 07/01/2011 03:46 PM, Brian wrote:

On Fri 01 Jul 2011 at 15:19:21 -0700, Paul Scott wrote:

 1024x768   60.0*
 800x60060.3 56.2
 848x48060.0
 640x48059.9
My LCD monitor's native resolution is 1280x1024

xrandr believes VGA-1 is only capable of 1024x768.  Why do you believe
1280x1024 is possible?


I didn't show all of xrandr:

VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1024x768   60.0*
   800x60060.3 56.2
   848x48060.0
   640x48059.9
VGA-2 disconnected (normal left inverted right x axis y axis)
TV-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   720x57650.0 +
   1024x768   50.0*
   800x60050.0
   720x48050.0
   640x48050.0
   400x300   100.0
   320x240   100.0
   320x200   100.0
DVI-D-1 disconnected (normal left inverted right x axis y axis)

Does this not say that the card will support up to 4096x4096 ?

I have run 1600x1200 on a different monitor.

Thanks,

Paul




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

Archive: http://lists.debian.org/4e10f5f0.4000...@ultrasw.com

Re: disk problems: which ATA?

On Sun 03 Jul 2011 at 11:25:18 -0700, Ross Boylan wrote:

> How can I tell which ata device is which hard drive?  It's come up
> several times for me, most recently with
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

For ata1.00 on this machine:

   ls -l /sys/class/scsi_disk/0:0:0:0/device/ | grep block:

> I'd also welcome advice about the disk problems, but I was hoping to
> raise the odds of an answer by keeping it simple :)

You thought devising an answer to your first question would be easy?
I've just spent the best part of two hours on it! No time now to sort
out your disk problem. :)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703224839.GV15615@desktop

Re: NVIDIA - URGENT

2011-07-03 Thread Andrej Kacian

On Sat, 02 Jul 2011 23:54:01 +0200
Hans Vogelsberger  wrote:

>instead of moving 
>/etc/X11/xorg.conf, I again changed its driver line in section "device" 
>to nouveau - and SUCCEDED: After a reboot xdm started X normally, not 
>even startx was necessary.

I tried to do the same, but alas, Xorg doesn't like noveau driver:

[  1528.909] drmOpenDevice: node name is /dev/dri/card0
[  1528.916] drmOpenByBusid: Searching for BusID pci::01:00.0
[  1528.916] drmOpenDevice: node name is /dev/dri/card0
[  1528.924] drmOpenByBusid: drmOpenMinor returns -1
[  1528.924] drmOpenDevice: node name is /dev/dri/card1
[  1528.929] drmOpenByBusid: drmOpenMinor returns -1
[  1528.929] drmOpenDevice: node name is /dev/dri/card2
[  1528.932] drmOpenByBusid: drmOpenMinor returns -1
[  1528.932] drmOpenDevice: node name is /dev/dri/card3
[  1528.936] drmOpenByBusid: drmOpenMinor returns -1
[  1528.936] drmOpenDevice: node name is /dev/dri/card4
[  1528.940] drmOpenByBusid: drmOpenMinor returns -1
[  1528.940] drmOpenDevice: node name is /dev/dri/card5
[  1528.944] drmOpenByBusid: drmOpenMinor returns -1
[  1528.944] drmOpenDevice: node name is /dev/dri/card6
[  1528.947] drmOpenByBusid: drmOpenMinor returns -1
[  1528.947] drmOpenDevice: node name is /dev/dri/card7
[  1528.951] drmOpenByBusid: drmOpenMinor returns -1
[  1528.951] drmOpenDevice: node name is /dev/dri/card8
[  1528.955] drmOpenByBusid: drmOpenMinor returns -1
[  1528.955] drmOpenDevice: node name is /dev/dri/card9
[  1528.959] drmOpenByBusid: drmOpenMinor returns -1
[  1528.959] drmOpenDevice: node name is /dev/dri/card10
[  1528.962] drmOpenByBusid: drmOpenMinor returns -1
[  1528.962] drmOpenDevice: node name is /dev/dri/card11
[  1528.966] drmOpenByBusid: drmOpenMinor returns -1
[  1528.966] drmOpenDevice: node name is /dev/dri/card12
[  1528.970] drmOpenByBusid: drmOpenMinor returns -1
[  1528.970] drmOpenDevice: node name is /dev/dri/card13
[  1528.973] drmOpenByBusid: drmOpenMinor returns -1
[  1528.973] drmOpenDevice: node name is /dev/dri/card14
[  1528.977] drmOpenByBusid: drmOpenMinor returns -1
[  1528.977] drmOpenDevice: node name is /dev/dri/card15
[  1528.981] drmOpenByBusid: drmOpenMinor returns -1
[  1528.981] drmOpenDevice: node name is /dev/dri/card0
[  1528.986] drmOpenDevice: node name is /dev/dri/card0
[  1528.989] drmOpenDevice: node name is /dev/dri/card1
[  1528.993] drmOpenDevice: node name is /dev/dri/card2
[  1528.997] drmOpenDevice: node name is /dev/dri/card3
[  1529.001] drmOpenDevice: node name is /dev/dri/card4
[  1529.004] drmOpenDevice: node name is /dev/dri/card5
[  1529.008] drmOpenDevice: node name is /dev/dri/card6
[  1529.012] drmOpenDevice: node name is /dev/dri/card7
[  1529.015] drmOpenDevice: node name is /dev/dri/card8
[  1529.019] drmOpenDevice: node name is /dev/dri/card9
[  1529.023] drmOpenDevice: node name is /dev/dri/card10
[  1529.026] drmOpenDevice: node name is /dev/dri/card11
[  1529.030] drmOpenDevice: node name is /dev/dri/card12
[  1529.033] drmOpenDevice: node name is /dev/dri/card13
[  1529.037] drmOpenDevice: node name is /dev/dri/card14
[  1529.041] drmOpenDevice: node name is /dev/dri/card15
[  1529.044] (EE) [drm] failed to open device
[  1529.044] (EE) No devices detected.

It should work, though, GT200 series should be supported by nouveau.

root@penny:/etc/X11# lspci | grep -i nv
01:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260]
(rev a1)

Any ideas?

Thanks in advance,
-- 
Andrej Kacian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110704005812.257a7a43@penny

message formatting and pseudo XML [was Re: disk problems: which ATA?]

On Sun, 2011-07-03 at 23:40 +0100, Lisi wrote:
> On Sunday 03 July 2011 22:35:08 Ross Boylan wrote:
> > (see original message)
> 
> Not a very productive instruction to those of us who have HTML display turned 
> off.
> 
> Lisi
> 
That's interesting.  The messages are not in html.  However, I did use a
little pseudo-XML (with angle brackets--I'm deliberately not repeating
it here) to distinguish material I copied from the terminal.

I haven't noticed problems in evolution, mutt, or thunderbird.

Any opinions from anyone on whether pseudo-XML is inadvisable?

Lisi, could this be a problem with your particular mail client?

Ross

P.S. I'm about to reboot.  It may be awhile before I'm back :(.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1309733790.10857.46.ca...@corn.betterworld.us

Re: OT: Camaleón


On 07/03/2011 03:25 PM, Lisi wrote:

On Sunday 03 July 2011 21:44:21 Paul Scott wrote:

"Camaleón" is a sort of nickname I chose long time ago because of the
openSUSE mascot (Geeko). It translates as "Chameleon" in English.

Actually gecko and chameleon are different varieties of lizards.  Both
words are used in English and don't translate to each other.

I think that Camaleón meant that her name translates to Chameleon in English,
which is correct.  She said that she chose the nickname because of the
openSUSE mascot, which she correctly called a gecko in English.  It is a
gecko.  And I am sure that she knows that gecko and chameleon are both
varieties of lizard.  That surely is the point??


Works for me.

Thanks,

Paul




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

Archive: http://lists.debian.org/4e10f090.80...@ultrasw.com

Re: disk problems: which ATA?

On Sunday 03 July 2011 22:35:08 Ross Boylan wrote:
> (see original message)

Not a very productive instruction to those of us who have HTML display turned 
off.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107032340.05709.lisi.re...@gmail.com

Re: disk problems: which ATA?

2011-07-03 Thread Mike Castle

On Sun, Jul 3, 2011 at 11:25 AM, Ross Boylan
 wrote:
> How can I tell which ata device is which hard drive?  It's come up
> several times for me, most recently with
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Depending on how long since boot, you can often explore the output of
dmesg to figure out which drive is which.

Sometimes what I do is something like this pseudocode:

for disk in /dev/sd?; do
  echo $disk
  smartctl -i $disk | grep -e Model -e Serial
done

And write down each working drive's model and serial number.

Reboot. and do it again.

In many cases, I've been lucky that the failing drive would work for a
little while (say, until a write).  So I could compare the two lists,
and figure out which model/serial is failing, and pull it.

Failing that, I have a list of known good disks, and can go through
all of the disks in the machine until I find the failing one.  And at
that point, since I have the case open, reseat all cables and cards,
just in case that's the problem.

mrc

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CA+t9iMwkN-Atum5kdYUdQmjA1Tmat+bz=6ka-zzaf4nttgs...@mail.gmail.com

Re: OT: Camaleón

On Sunday 03 July 2011 21:44:21 Paul Scott wrote:
> > "Camaleón" is a sort of nickname I chose long time ago because of the
> > openSUSE mascot (Geeko). It translates as "Chameleon" in English.
>
> Actually gecko and chameleon are different varieties of lizards.  Both
> words are used in English and don't translate to each other.

I think that Camaleón meant that her name translates to Chameleon in English, 
which is correct.  She said that she chose the nickname because of the 
openSUSE mascot, which she correctly called a gecko in English.  It is a 
gecko.  And I am sure that she knows that gecko and chameleon are both 
varieties of lizard.  That surely is the point??

Lisi

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107032325.17357.lisi.re...@gmail.com

Re: disk problems: which ATA?

On Sun, 2011-07-03 at 12:07 -0700, JD wrote:
> On 07/03/2011 11:25 AM, Ross Boylan wrote: 
> > How can I tell which ata device is which hard drive?  It's come up
> > several times for me, most recently with
> > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> > 
> > It appears from other info that sdb is the problem:
> > 
> > # smartctl -H /dev/sdb
> > Sun Jul  3 10:26:29 PDT 2011
> > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
> > Allen
> > Home page is http://smartmontools.sourceforge.net/
> > 
> > Short INQUIRY response, skip product id
> > A mandatory SMART command failed: exiting. To continue, add one or more
> > '-T permissive' options.
> > 
> > but I'd like to know how to do this in general.
> > 
> > I'd also welcome advice about the disk problems, but I was hoping to
> > raise the odds of an answer by keeping it simple :)
> > 
> > sdb has had hardware problems for awhile; it wouldn't be surprising if
> > it's failed.
> > 
> > Running lenny with linux 2.6.26-2-686.
> > 
> > Thanks.
> > Ross
> > 
> > 
> 
> My basic advice in this situation is:
> 1. unmount the failing drive if it is mounted, and mount it's
> partitions read only.
It's a bit tricky, since my mounts are mostly on LVM logical volumes.
The main volume group I use includes the failing disk and some good
disks.  Unfortunately, LVM (specifically pvs or vgdisplay) won't give me
info on the VG, even though I seem to have continuing access to many of
its LVs.  I *think* I've already moved most LVs to be backed by other
disks.
> 2. back up it's mounted partitions to a good drive using tar:
> Assuming the mount points are
> /sdb1  /sdb2/sdb3
> cd /
> for i in 1 2 3; do
> tar cf-   sdb$i  |  bzip2 -c -9 > /somewhere/backup/sdb$i
> done
The latest problem emerged while doing my monthly (full) backups.  I
think the backups are good but the partition with the iso image failed.
> 3. If the drive is still under warranty, then run secure erase.
> read up on hdparm (man hdparm)
> If you go this route, I can send you a script
> for proper use of hdparm to securely erase a drive.
> After erasing, then get and RMA and send it away for
> replacement.
> 
It was when it started to fail.  I was hoping to do some kind of LVM
migration to get the info off, and so things have dragged on.
> 4. If you purchase a new drive, you will then partition it
> and tar back the backups to it.
Thanks for the advice.
> 
> -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with
> a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org Archive:
> http://lists.debian.org/4e10bde7.4040...@gmail.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1309729495.10857.40.ca...@corn.betterworld.us

Re: disk problems: which ATA?

On Sun, 2011-07-03 at 19:19 +, Camaleón wrote:
> On Sun, 03 Jul 2011 11:25:18 -0700, Ross Boylan wrote:
> 
> > How can I tell which ata device is which hard drive?  It's come up
> > several times for me, most recently with ata2.00: exception Emask 0x0
> > SAct 0x0 SErr 0x0 action 0x6 frozen
> 
> (...)
> 
> You can:
> 
> - Run "smartctl -i /dev/sdb | grep -i model"
Except the drive isn't responding to smartctl (see original message).
I tried adding -T permissive, but all that gets me is
Short INQUIRY response, skip product id
(curiously, no error about command failed).
> - Then "dmesg | grep -i ata2"
> - To finally compare by hdd model :-)
That works for my current machine.  But on another machine I want to
figure out which drive an error message goes with, and there are 2
identical drivers.  I suppose that even if I new which sd device the ata
went with, I still wouldn't be sure which physical drive that was...
> 
> As per the error itself, you can use the manufacturer hard disk 
> diagnostic tools which uses to run from a LiveCD and will provide 
> accurate results about your hdd health and status.
> 
> OTOH, I've also seen that kind of error coming from bad sata cable or bad 
> sit connection to motherboard/disk. You may also check this.
I think I already tried reseating, but I suppose it's worth trying
again.  I'm concerned if I power down I may not be able to get back up,
since the failing hard disk is actually part of an LVM volume group.  I
am also unable to get information on that VG right now.  

Most of the logical vomes in the group are backed by other hard drives,
but I'm not quite sure what will happen if the disk is toast.  At the
moment, I have access to most of the LVs, even though I can't get info
on the PV that contains them (!).

Ross

P.S. For the record, kernel logs need to be read carefully to figure out
which drive is ata2.  Mine had
Jun 22 09:24:10 corn kernel: [7.767461] hdf: 26563824 sectors (13600 MB) 
w/256KiB Cache, CHS=26353/16/63
Jun 22 09:24:10 corn kernel: [7.798391] hdf: cache flushes not supported
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: New USB device found, 
idVendor=04b8, idProduct=011e
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: New USB device strings: 
Mfr=1, Product=2, SerialNumber=0
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: Product: EPSON Scanner
Jun 22 09:24:10 corn kernel: [7.829859] usb 1-4: Manufacturer: EPSON
Jun 22 09:24:10 corn kernel: [7.967458]  hdf:<6>ata2.00: ATA-8: 
ST31000340AS, SD15, max UDMA/133
Jun 22 09:24:10 corn kernel: [8.135686]  hdf1 hdf2 hdf3
Jun 22 09:24:10 corn kernel: [8.129867] ata2.00: 1953525168 sectors, multi 
16: LBA48 NCQ (depth 0/32)
Jun 22 09:24:10 corn kernel: [8.241613] ata2.00: configured for UDMA/133
Jun 22 09:24:10 corn kernel: [8.129867] scsi 0:0:0:0: Direct-Access ATA 
 WDC WD2500JS-00M 02.0 PQ: 0 ANSI: 5
Jun 22 09:24:10 corn kernel: [8.290133] scsi 1:0:0:0: Direct-Access ATA 
 ST31000340AS SD15 PQ: 0 ANSI: 5

The key point is that although the message about ata2.00 (at 7.967458)
appears in the middle of the hdf information, the 2 have no relation.
It seems the <6> indicates an asyncronous message dumped before the end
of the line.  Later comes
Jun 22 09:24:10 corn kernel: [9.520209] sd 1:0:0:0: [sdb] 1953525168 
512-byte hardware sectors (1000205 MB)
so the sector count indicates this matches ata2.00, which is the Seagate 
ST31000340AS at scsi 1:0:0:0.
I guess the first ata line (after the <6>) gives the model.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1309728908.10857.30.ca...@corn.betterworld.us

Re: rsnapshot and cron :-)

2011-07-03 Thread Aniruddha

On Wed, Jun 29, 2011 at 11:21 AM, Pol Hallen  wrote:
> Hi folks
>
> Using rsnapshot I've unsure about maintein my backup for almost 24 months:
>
> in rsnapshot.conf I have:
>
> interval        hourly  6
> interval        daily   7
> interval        weekly  4
> interval       monthly 24
>
> (I hope that "interval monthly 24" is same of maintein my backup for 2 years
>

This setting means how many copies will be saved.  If you make a
backup each month it will keep them for 2 years.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMpSvvxy1rbO4L8jyRxCvC=7-ctcegieca0btg10g3u1vsk...@mail.gmail.com

Re: OT: Camaleón


On 07/03/2011 07:46 AM, Camaleón wrote:

On Sun, 03 Jul 2011 03:26:52 +, T o n g wrote:


On Sat, 02 Jul 2011 12:36:14 +1000, Scott Ferguson wrote:


you're best sticking with Camaleón if possible - she does run Gnome and
. . .

I don't know western names well and I had always thought that Camaleón
is a man, although being "overly" polite (than ordinary man).

:-)

"Camaleón" is a sort of nickname I chose long time ago because of the
openSUSE mascot (Geeko). It translates as "Chameleon" in English.


Actually gecko and chameleon are different varieties of lizards.  Both 
words are used in English and don't translate to each other.


Have fun,

Paul Scott




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

Archive: http://lists.debian.org/4e10d4a5.8010...@ultrasw.com

Re: cannot go back from nouveau to nv

2011-07-03 Thread Stephen Powell

On Sun, 03 Jul 2011 03:56:34 -0400 (EDT), Paul Scott wrote:
> 
> or that read-edid is broken?  ddcprobe seems to provide correct 
> information for my ViewSonic VA703b.  read-edid does not.

By the way, have you noticed that nv (xserver-xorg-video-nv)
has been dropped from Wheezy (testing) now?  I'm still running it,
but I had to download the source code and compile my own version
from source.  That still works.  But I'm living on borrowed time.
I noticed build warnings that the driver is referring to deprecated
fields.  It's only a matter of time before I start to get FTBFS
errors.  And then, if the lack of support for interlaced modes
has not been addressed in nouveau, I will have to get rid of my
monitor.  (My monitor requires an interlaced mode.  That's why
I still use nv.)

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1115482411.499673.1309725595751.javamail.r...@md01.wow.synacor.com

Re: Hibernate fails

2011-07-03 Thread Carl Fink

On Fri, Jul 01, 2011 at 06:48:33PM +1000, Scott Ferguson wrote:

> If ACPI is broken you'll see messages in dmesg.

A quick scan shows this:
   26.446021] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects 
found.
[   26.446024] [Firmware Bug]: powernow-k8: Try again with latest BIOS.

There are no updates available for my BIOS.

> Thanks for that
> Do you have a /var/log/wpa_action.log??
> If so please post

No such file.
-- 
Carl Fink   nitpick...@nitpicking.com 

Read my blog at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703203750.ga26...@panix.com

Re: Squeeze and root in graphical mode

2011-07-03 Thread Nico Kadel-Garcia

On Sun, Jul 3, 2011 at 4:44 AM, Nicolas Bercher  wrote:
> On 03/07/2011 10:25, alex.pad...@laposte.net wrote:
>>
>> Hi,
>>
>> I would like to know if the root have a graphical environnement ?
>> I don't connect with login root with the password of root but in
>> terminal window I can connect me as root.
>> Regards.
>>
>> Alex PADOLY
>
> Probably because you have to authorize X connections to any other user:
>
>  xhost +
>
> before su as root (or whatever other user).
>
> Nicolas

Why don't I just paste my keys taped to my front door, while I'm at
it? Running "xhosst +" allows anyone to run X sessions on that same X
server behind your back, including shells with keystroke recording,to
grab your passwords, or my personal favorite, the "xroach" program to
hide cockroach icons behind your windows and make them scurry for
cover when a window moves.

The shrieks from the programmer I'd warned about this security hole
echoed down the hall and got me in professional trouble

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOCN9ryS49vuX6k-r6Mq8A2gz=gD=awjbs8_bp6sqjaxiwe...@mail.gmail.com

Re: My CD and DVD are messed up

2011-07-03 Thread T o n g

On Sun, 03 Jul 2011 15:51:56 +, Camaleón wrote:

>> I put them in another file, /etc/udev/rules.d/71-my-cd.rules, but how
>> would I overwrite the settings in /etc/udev/rules.d/70 -persistent-
>> cd.rules, which was automatically generated by the 75-cd -aliases-
>> generator.rules? I.e., wouldn't those line that I disabled (by #) would
>> come up again once the /etc/udev/rules.d/70-persistent -cd.rules is
>> regenerated?
> 
> . . . 
> 
> Unless someone knows the answer (I don't) you will have to test ;-)

I believe that my guess would be true. So I think I'd better stick to 
/etc/udev/rules.d/70-persistent-cd.rules file, not using another file 
then.

Thanks everyone for the replies!

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/iuqfdu$ka5$1...@dough.gmane.org

Re: disk problems: which ATA?

On Sun, 03 Jul 2011 11:25:18 -0700, Ross Boylan wrote:

> How can I tell which ata device is which hard drive?  It's come up
> several times for me, most recently with ata2.00: exception Emask 0x0
> SAct 0x0 SErr 0x0 action 0x6 frozen

(...)

You can:

- Run "smartctl -i /dev/sdb | grep -i model"
- Then "dmesg | grep -i ata2"
- To finally compare by hdd model :-)

As per the error itself, you can use the manufacturer hard disk 
diagnostic tools which uses to run from a LiveCD and will provide 
accurate results about your hdd health and status.

OTOH, I've also seen that kind of error coming from bad sata cable or bad 
sit connection to motherboard/disk. You may also check this.

Greetings,

-- 
Camaleón

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.19.19...@gmail.com

Re: disk problems: which ATA?

2011-07-03 Thread JD



  
  
On 07/03/2011 11:25 AM, Ross Boylan wrote:

  How can I tell which ata device is which hard drive?  It's come up
several times for me, most recently with
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

It appears from other info that sdb is the problem:

# smartctl -H /dev/sdb
Sun Jul  3 10:26:29 PDT 2011
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more
'-T permissive' options.

but I'd like to know how to do this in general.

I'd also welcome advice about the disk problems, but I was hoping to
raise the odds of an answer by keeping it simple :)

sdb has had hardware problems for awhile; it wouldn't be surprising if
it's failed.

Running lenny with linux 2.6.26-2-686.

Thanks.
Ross





My basic advice in this
situation is:
1. unmount the failing drive if it is mounted, and mount it's
partitions read only.
2. back up it's mounted partitions to a good drive using tar:
    Assuming the mount points are
    /sdb1  /sdb2    /sdb3
    cd /
    for i in 1 2 3; do
        tar cf-   sdb$i  |  bzip2 -c -9 >
/somewhere/backup/sdb$i
    done
3. If the drive is still under warranty, then run secure erase.
    read up on hdparm (man hdparm)
    If you go this route, I can send you a script
    for proper use of hdparm to securely erase a drive.
    After erasing, then get and RMA and send it away for
    replacement.

4. If you purchase a new drive, you will then partition it
    and tar back the backups to it.

  
  



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e10bde7.4040...@gmail.com

Votre annonce.

2011-07-03 Thread annoncezvous . biz65


Salut,

Votre annonce sur:

http://www.annoncez-vous.biz

Merci.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703175746.f359b13...@60gp.ovh.net

disk problems: which ATA?

How can I tell which ata device is which hard drive?  It's come up
several times for me, most recently with
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

It appears from other info that sdb is the problem:

# smartctl -H /dev/sdb
Sun Jul  3 10:26:29 PDT 2011
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more
'-T permissive' options.

but I'd like to know how to do this in general.

I'd also welcome advice about the disk problems, but I was hoping to
raise the odds of an answer by keeping it simple :)

sdb has had hardware problems for awhile; it wouldn't be surprising if
it's failed.

Running lenny with linux 2.6.26-2-686.

Thanks.
Ross


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1309717518.10857.9.ca...@corn.betterworld.us

Re: install squeeze con core i5 2500 motherboard 1155

2011-07-03 Thread Pablo Sánchez


Camaleón, maybe it's a bug with de motherboard, besides that,
i also prefer to build software raid before using the chipset's "fake raid".

I cannot find what's that hotplug stuff in the motherboard manual.
Will have to look on asus site.


Pablo Sánchez.



On Sun, 03 Jul 2011 09:49:55 -0300, Pablo Sánchez wrote:

Pablo Sánchez   writes:


Well, i got an ASUS P8H67-M LX with H67 B3 revision intel chipset
with a core i5 2500 .

The machine has 3 Samsung 1TB disks , that i see on the bios config,
connected to sata 3gb ports .

After inserting an usb stick with realtek firmware-realtek 0.28,
config the network, I'm stuck on Scanning disk on starting up the
partitioner on 50 % progress : it's stalled .

Do you see any messages about the disks in the syslog?

lee, i didn't take a look at syslog. dmesg showed they were there.

What i ended doing, was play with the hotplug option for each disk on
the bios, and it worked. I have the system running, but i'm now trying
to learn what that option means . I don't think it's a real hotplug
thing, as changing drives without shutting down the computer. Actually
got it working setting two of the drives with hotplug on and one off .

What's that "hotplug" thingy of the BIOS? I've never heard before about
that :-?

If that option was the one making noise and the hard disk controller had
problems at the install stage, it could be due to a BIOS bug/issue.

Also, having the hdd controller set to RAID (fake-raid) can also present
problems for the installer. I prefer to use AHCI, if possible.

Greetings,




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

Archive: http://lists.debian.org/4e10ab88.1040...@adinet.com.uy

Re: Squeeze and root in graphical mode

On Sunday 03 July 2011 18:28:51 Camaleón wrote:
>  SuSE (with which I also
>
> > started. But I didn't use it for long because I couldn't stand YaST).
>
> 
> YaST is one of the best tools an admin (and a user) can find! And now is
> GPL :-)
> 

Yes, it seems to inspire either love or hate and very little indifference!

I still don't like it.  I had to install openSUSE on my granddaughter's laptop 
because of her school's wireless network (don't ask!!) and calling my 
knowledge of yam and rpm rudimentary would be a gross overstatement.

Lisi

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107031840.28897.lisi.re...@gmail.com

Re: Squeeze and root in graphical mode

On Sun, 03 Jul 2011 18:06:55 +0100, Lisi wrote:

> On Sunday 03 July 2011 17:32:19 Camaleón wrote:
>> I was one of those newbies that sometimes logged as root when I was
>> giving my first steps in Linux. I remember in that time (2003, KDE
>> 3.2.x, IIRC) there was a background image¹ for root login with bright
>> red and plenty of bombs. Yes, bombs, for the user to understand the
>> risk of having that session open :-)
>>
>> Nowadays, KDE and also GNOME discourage using root GUI sessions but it
>> still possible to get them.
> 
> That bomb screen was, I think, special to SuSE (with which I also
> started. But I didn't use it for long because I couldn't stand YaST). 


YaST is one of the best tools an admin (and a user) can find! And now is 
GPL :-)


> And yes, I too logged in as root in those days.  But only because I had
> no idea at that stage what else to do for anything that needed root
> access.

He, he... me also :-P
 
> I *think* that it is Debian, not KDE, that won't key you log in to a GUI
> session as root.  There certainly was a phase when Debian wouldn't and
> PPLinuxOS, also with KDE, would.  (No, I didn't make a habit of logging
> in as root.  I tried once, and logged out again immediately - it wasn't
> just the cat who was killed by curiosity!)

I don't think so.

KDE disabled root logins by default in KDM since some time ago, while 
GNOME (GDM) was still allowing it (not sure is that's remains true by 
now). And I speak here for no specific distro, this has been happenning 
in other distributions as well. But distributions are changing/revisiting 
their default settings every year...

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.17.28...@gmail.com

Re: monitor detection maybe not working - another try

On Sun 03 Jul 2011 at 00:17:16 -0700, Paul Scott wrote:

> I believe that if my monitor info were being read correctly I would have  
> no problem with monitor resolution.  Is is possible that I just need to  
> file a bug against read-edid?

More likely the bug would be in the kernel but I'm no expert. As far as
I can see the read-edid package is not necessary for X to probe the
monitor. It's not on any of my machines.

You probably can't pin-point when X ceased to give 1280x1024, can you?
It might help if it came to a bug report. If a Squeeze live cd gave this
resolution it would be supporting evidence.

As Camaleón said, you could wait for further changes in Sid and the
problem might be rectified, but a bug report would speed the process. 

Your Xorg.0.log seems ok except

> [ 96967.536] (II) NOUVEAU(0): EDID for output VGA-1

should be followed by a block of data relating to the monitor. The same
data should appear in 'xrandr --prop'.

In the meantime a modes line in xorg.conf would restore the monitor's
optimum resolution in X.

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703165445.GU15615@desktop

Re: Squeeze and root in graphical mode - ERRATUM

On Sunday 03 July 2011 18:06:55 Lisi wrote:
>  that won't *key* you log

that won't *let* you.

Sorry - I'm a lousy typist. :-(



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107031811.46186.lisi.re...@gmail.com

Re: Squeeze and root in graphical mode

On Sunday 03 July 2011 17:32:19 Camaleón wrote:
> I was one of those newbies that sometimes logged as root when I was
> giving my first steps in Linux. I remember in that time (2003, KDE 3.2.x,
> IIRC) there was a background image¹ for root login with bright red and
> plenty of bombs. Yes, bombs, for the user to understand the risk of
> having that session open :-)
>
> Nowadays, KDE and also GNOME discourage using root GUI sessions but it
> still possible to get them.

That bomb screen was, I think, special to SuSE (with which I also started.  
But I didn't use it for long because I couldn't stand YaST).  And yes, I too 
logged in as root in those days.  But only because I had no idea at that 
stage what else to do for anything that needed root access.

I *think* that it is Debian, not KDE, that won't key you log in to a GUI 
session as root.  There certainly was a phase when Debian wouldn't and 
PPLinuxOS, also with KDE, would.  (No, I didn't make a habit of logging in as 
root.  I tried once, and logged out again immediately - it wasn't just the 
cat who was killed by curiosity!)

Lisi

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107031806.55703.lisi.re...@gmail.com

Success! no longer stranded between lenny and squeeze

2011-07-03 Thread Hendrik Boom

On Sun, 03 Jul 2011 01:45:54 +, Hendrik Boom wrote:

> On Sat, 02 Jul 2011 17:53:50 +, Hendrik Boom wrote:
> 
> 
>> Thanks for the advice.  I'll ssh in and if the text consoles don't
>> reappear after completing the upgrade, I can investigate further at
>> leisure.
> 
> Upgrade completed using ssh over a LAN.  Unfortunately, I won't have
> time to reboot and see if the text consoles reappear until tomorrow.
> 
> -- hendrik

When I got back to the machine just now, it was still running an X 
session.  I was able to close a few windows and log out.  But then it was 
black screen completely -- no text consoles *or* gdm logins available.

I did a hard reset to reboot the machine.  It recovered my file systems 
nicely (they're reiser or ext3), and came up, complete with text consoles 
and gdm login prompt.  I logged in through gdm and started Pan to post 
this message.

This is a success.  Thanks for all the advice, especially for the caveats 
about what might go wrong, but, because I knew what to be careful of, it 
didn't.

-- hendrik.

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/iuq5qv$3dl$1...@dough.gmane.org

Re: Squeeze and root in graphical mode

On Sun, 03 Jul 2011 16:23:46 +0100, Lisi wrote:

> On Sunday 03 July 2011 15:27:03 Camaleón wrote:
>> It is not a good idea to run a GUI session with the root user. It can
>> be done, but better if you first explain what is goal for doing it
>> so...
> 
> I run Konqueror as root for some file maniplulations on files which are
> owned by root.

Which is fine. 

Running an app as root ! login into a KDE session as root.

> I simply don't trust myself not to do: 
> # cd /
> # rm -R  *.*
> 
> or copy something trivial on top of something important, or do something
> else disastrous.

Have you considered in using Midnight Commander?

Is the "swiss-knife" tool for managing almost any aspects of your day to 
day linux box at console but with a wizard to avoid such dumb situations 
(fat fingers or a bad day) we all can face :-)

> With Konqueror I have to mistake the visual representation as well as
> what I am telling the system to do.

Sure, GUI has some advantages.

> I would, however, genuinely like to have it expained to me why 5 minutes
> of running a GUI file manager as root is less secure than running  a
> root terminal for 15 minutes or more.  If I enable root running
> Konqueror, Konqueror is, so far as I can see, the only application that
> can run as root. From the CLI, other applications can be launched, in
> particular vi, vim. nano etc.  The system can be edited, shut down,
> destroyed (see above!) etc.  A file manager can do none of those things.

The risk is the same, but again, one thing is running an application as 
root to perform a couple of tasks and quit and another different thing is 
login as root into your DE. That's something anyone should avoid unless 
you know very very (yes, two "very") well what you are doing and leave as 
soon as possible.

I was one of those newbies that sometimes logged as root when I was 
giving my first steps in Linux. I remember in that time (2003, KDE 3.2.x, 
IIRC) there was a background image¹ for root login with bright red and 
plenty of bombs. Yes, bombs, for the user to understand the risk of 
having that session open :-)

Nowadays, KDE and also GNOME discourage using root GUI sessions but it 
still possible to get them.

¹http://www.freeimagehosting.net/uploads/5ac7077004.png

Greetings,

-- 
Camaleón

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.16.32...@gmail.com

Re: My CD and DVD are messed up


On 25/06/2011 19:58, lee wrote:

T o n g  writes:


On my system the /dev/cdrom is actually DVD while My CD is actually /dev/
cdrom1. This confuse most of the media software. How can I fix it?


Do you have entries about these devices in /etc/fstab?


Be careful that entries in /etc/fstab are only useful to actually mount a cdrom file 
system.  When ripping audio cds, the /etc/fstab entry is completely useless because you're 
not supposed to mount an audio cd (even though this is possible with the package cdfs-src).


Nicolas


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

Archive: http://lists.debian.org/4e109457.90...@yahoo.fr

Re: My CD and DVD are messed up


On 28/06/2011 20:48, Tom Furie wrote:

Or perhaps edit /etc/udev/rules.d/70-persistent-cd.rules so that the
devices get the links in /dev that he wants.

Cheers,
Tom
I also think this is the solution because udev names devices on startup, so if you want 
something permanent, that's the way to do it.


Things in /dev/disk/by-* are only views constructed afterwards.

Nicolas


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

Archive: http://lists.debian.org/4e109286.2090...@yahoo.fr

Re: My CD and DVD are messed up

On Sun, 03 Jul 2011 03:18:05 +, T o n g wrote:

> On Sat, 02 Jul 2011 16:06:23 +, Camaleón wrote:
> 
>> just read Debian udev the docs to follow the instructions.
> 
> Hi Camaleón,
> 
> Thanks for your reply. However, I was having a hard time trying to find
> what you meant by "Debian udev the docs". 

There was an error on my phrase. I should have written "just read Debian 
udev docs".

> All that I found are bit and pieces here and there. Would you be so
> kind to give me a list to read please?

I don't think Debian wiki is updated enough but this can also be of help:

http://wiki.debian.org/udev

And of course, "udev" package docs:

/usr/share/doc/udev/*

>> I would try:

(...)

>> That is:
>> 
>> - From the DVD entries, disable (#) all but the one that makes "dvd"
>> node.
>> - From the CD-R entries, disable (#) all and add a new one that makes
>> "cdrom" node.
> 
> That looks substantially different from the examples given from
> http://reactivated.net/writing_udev_rules.html

> #example-cdrom:
> 
>  SUBSYSTEM=="block", KERNEL=="hdc", SYMLINK+="dvd", GROUP="cdrom"
>  SUBSYSTEM=="block", KERNEL=="hdd", SYMLINK+="dvdrw", GROUP="cdrom"
> 
> I guess the above example is already obsolete, or it is still OK?

More than obsolete, I think udev provides many ways for doing the same 
thing. Also, if you carefully look at the "/etc/udev/rules.d/70-
persistent-cd.rules" file, it says that all the entries have to finish 
with "ENV{GENERATED}=1" flag, and this can be a requirement only for 
Debian.

>>> Where should I put those rules? I believe that /etc/udev/rules.d/70-
>>> persistent-cd.rules is automatically generated by the 75-cd-aliases-
>>> generator.rules. I hope that I can put those rules in a standalone
>>> file which can overwrite settings in
>>> /etc/udev/rules.d/70-persistent-cd.rules.
>> 
>> You can edit the same file. If after that it works as you want, you can
>> then put them in another file,
> 
> Ok, so say after it works as I want, 

You need first to catch the bear before sell his skin :-) 

> I put them in another file, /etc/udev/rules.d/71-my-cd.rules,
> but how would I overwrite the settings in /etc/udev/rules.d/70
> -persistent- cd.rules, which was automatically generated by the 75-cd
> -aliases- generator.rules? I.e., wouldn't those line that I disabled (by
> #) would come up again once the /etc/udev/rules.d/70-persistent
> -cd.rules is regenerated?

Good question. Let's see what "man udev" has to say:

***
Rules files

The udev rules are read from the files located in the default rules
directory /lib/udev/rules.d/, the custom rules directory /etc/udev/
rules.d/ and the temporary rules directory /dev/.udev/rules.d/. All rule 
files are sorted and processed in lexical order, regardless in which of 
these directories they live. Every line in the rules file contains at 
least one key value pair. There are two kind of keys, match and 
assignment keys. If all match keys are matching against its value, the 
rule gets applied and the assign keys get the specified value assigned.

(...)
***

So here we have a problem. What will prevail...? 

1/ A matching rule read at first place (e.g., 69-my-cd.rules) → once a 
rule hits a match, the rest are ignored

2/ A matching rule read at last (e.g., 71-my-cd.rules) → last match wins

3/ None of the above → there can't be "confronting" rules

Unless someone knows the answer (I don't) you will have to test ;-)

Greetings,

-- 
Camaleón

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.15.51...@gmail.com

Re: NVIDIA - URGENT

2011-07-03 Thread David Baron

> I know this is playing with fire but I did this:
> sudo ln -s /etc/alternatives/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so.1
> 
> This points the "multiarch" version to where the /usr/lib version points.
> Save the original symlink to libGL.so.1.2 to be safe but easy enough to
> restore is need be. You might also manually point the nvidia/diversion to
> that one.
> 
> Anyway, I had X and NVidia driver working fine but openGL apps crashed out.
> After this symlink, flightgear started fine so it fixed my problem in any
> event. Nouveau might not find libGL at all right now.

However, when I restart the computer, this change seems to get undone! I am 
not upgrading any mesa, glu, nvidia, any of it! I even have a pkg-divert on 
this. Still gets undone.

Re: install squeeze con core i5 2500 motherboard 1155

On Sun, 03 Jul 2011 09:49:55 -0300, Pablo Sánchez wrote:
> 
>> Pablo Sánchez  writes:
>>
>>> Well, i got an ASUS P8H67-M LX with H67 B3 revision intel chipset 
>>> with a core i5 2500 .
>>>
>>> The machine has 3 Samsung 1TB disks , that i see on the bios config,
>>> connected to sata 3gb ports .
>>>
>>> After inserting an usb stick with realtek firmware-realtek 0.28,
>>> config the network, I'm stuck on Scanning disk on starting up the
>>> partitioner on 50 % progress : it's stalled .

>> Do you see any messages about the disks in the syslog?

> lee, i didn't take a look at syslog. dmesg showed they were there.
> 
> What i ended doing, was play with the hotplug option for each disk on
> the bios, and it worked. I have the system running, but i'm now trying
> to learn what that option means . I don't think it's a real hotplug
> thing, as changing drives without shutting down the computer. Actually
> got it working setting two of the drives with hotplug on and one off .

What's that "hotplug" thingy of the BIOS? I've never heard before about 
that :-?

If that option was the one making noise and the hard disk controller had 
problems at the install stage, it could be due to a BIOS bug/issue.

Also, having the hdd controller set to RAID (fake-raid) can also present 
problems for the installer. I prefer to use AHCI, if possible.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.15.27...@gmail.com

Re: Squeeze and root in graphical mode

On Sunday 03 July 2011 15:27:03 Camaleón wrote:
> It is not a good idea to run a GUI session with the root user. It can be
> done, but better if you first explain what is goal for doing it so...

I run Konqueror as root for some file maniplulations on files which are owned 
by root.

I simply don't trust myself not to do:
# cd /
# rm -R  *.*

or copy something trivial on top of something important, or do something else 
disastrous.

With Konqueror I have to mistake the visual representation as well as what I 
am telling the system to do.

I would, however, genuinely like to have it expained to me why 5 minutes of 
running a GUI file manager as root is less secure than running  a root 
terminal for 15 minutes or more.  If I enable root running Konqueror, 
Konqueror is, so far as I can see, the only application that can run as root.  
From the CLI, other applications can be launched, in particular vi, vim. nano 
etc.  The system can be edited, shut down, destroyed (see above!) etc.  A 
file manager can do none of those things.

Lisi

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107031623.46732.lisi.re...@gmail.com

Re: monitor detection maybe not working

On Sat, 02 Jul 2011 17:39:50 -0700, Paul Scott wrote:

> On 07/02/2011 12:23 PM, Paul Scott wrote:
>> On 07/02/2011 02:05 AM, Camaleón wrote:

(...)

>>> Also, better if you upload your full "/var/log/Xorg.0.log" somewhere,
>>
>> I will do that soon but I believe it will show you that read-edid is
>> not reading my monitor info correctly which is why I started this
>> thread.
> 
> Attached is the Xorg.0.log after nvidia-xconfig after restarting gdm3
> and X does not start.

(...)

> [ 96967.423] (--) NOUVEAU(0): Chipset: "NVIDIA NV1f" 
> [ 96967.423] (II) NOUVEAU(0): Creating default Display subsection in Screen 
> section "Default Screen Section" for depth/fbbpp 24/32

Errr, it seems that nvidia driver is not being loaded but nouveau. 

You should fix this (nouveau driver has to be blacklisted¹), unless you 
really want to keep nouveau, which is not a bad option.

¹http://wiki.debian.org/KernelModesetting#Disabling_KMS

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.15.16...@gmail.com

Re: monitor detection maybe not working

On Sat, 02 Jul 2011 12:23:34 -0700, Paul Scott wrote:

> On 07/02/2011 02:05 AM, Camaleón wrote:
>> On Fri, 01 Jul 2011 13:22:02 -0700, Paul Scott wrote:
>>
>>> I'm running sid.
>>>
>>> My monitor stopped going to the correct resolution some upgrades ago. 
>>> I have an
>>>
>>> nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev a3).
>> Which VGA driver are you using?
> 
> Whatever nvidia-kernel-dkms left me with.  Is there an easy way to tell
> which driver is active?

You can look at Xorg logs, for instance:

grep -i nvidia /var/log/Xorg.0.log

Or you can ask lspci:

lspci -v | grep nvidia
 
>> Nvidia closed driver provides "nvidia-settings" app to manage the
>> basics of the card.
> 
> Running this now gives me a dialog box which tells me I am not using the
> NVIDIA X driver and that I should run nvidia-xconfig.  This tells me I
> need to fix xorg.conf which I will do later today.

Oops. That can be cause of the wrong resolution :-?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.15.10...@gmail.com

Re: Stranded between lenny and squeeze

On Sat, 02 Jul 2011 21:29:12 -0400, Nico Kadel-Garcia wrote:

> On Sat, Jul 2, 2011 at 5:10 AM, Camaleón  wrote:
>> On Sat, 02 Jul 2011 01:47:38 +, Hendrik Boom wrote:
>>
>> (...)
>>
>>> Or is there some devious trick I'm missing?  Will an ssh connection
>>> from another machine survive the upgrade process, for example?
>>
>> Yes, I would try that way.
>>
>> Given your current situation I'd say a SSH session would be more than
>> convenient. The system is already installed and an upgrade should not
>> broke the network service.
> 
> Doing forklift upgrades without console access is always a risk. An SSH
> session is sensitive to network interruptions in the midst of the
> update, for example, leaving you in a fractured state. (This is hardly
> unique to Debian.)

The install process was indeed somehow broken so why not giving SSH a 
try? Maybe he only needed to get a small set of packages. I barely sit in 
front of the computer I'm upgrading.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.15.06...@gmail.com

Re: NetworkManager (was: Re: Stranded between lenny and squeeze)

On Sun, 03 Jul 2011 14:04:21 +, Curt wrote:

> On 2011-07-02, Camaleón  wrote:
>>
>> And of course, warning about NM can leave the system disconnected is a
>> very good point (I didn't know NM can take that path...), so in the
>> evnt this can happen and the OP is using NM, he can just turn it off
>> before doing the upgrade and turn it on aftwewards.
> 
> What's wrong with just doing "apt-get -d dist-upgrade" first, thus
> rendering the whole question of NM dropping the connection or not moot.

You mean running the dist-upgrade routine locally? The OP was facing two 
problems for this to be done easily, IIRC.

> Or am I missing something?

Yep, you missed the OP:

1/ Got a blank screen when jumping to console (tty)
2/ GDM session expired quickly

So SSH was the option Hendrik also considered and that I found appropiate 
for this case (yes, he also could have try to load the VESA driver in 
order to get a readable console or diving into GDM logs and figure out 
why session expired so quick but this can even take more time that a 
simple SSH update).

Greetings,

-- 
Camaleón

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.15.02...@gmail.com

Re: OT: Camaleón

On Sun, 03 Jul 2011 03:26:52 +, T o n g wrote:

> On Sat, 02 Jul 2011 12:36:14 +1000, Scott Ferguson wrote:
> 
>> you're best sticking with Camaleón if possible - she does run Gnome and
>> . . .
> 
> I don't know western names well and I had always thought that Camaleón
> is a man, although being "overly" polite (than ordinary man).

:-)

"Camaleón" is a sort of nickname I chose long time ago because of the 
openSUSE mascot (Geeko). It translates as "Chameleon" in English.
 
> Is Camaleón really a girl?
> 
> Just curious.

Yes, I am. 

Well, as Lisi pointed out, "woman" fits better, I guess. My real name is 
Elsa.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.14.46...@gmail.com

Re: Squeeze and root in graphical mode

On Sun, 03 Jul 2011 08:25:32 +, alex.padoly wrote:

> I would like to know if the root have a graphical environnement ? 

Yes, well... it can have.

> I don't connect with login root with the password of root but in
> terminal window I can connect me as root. Regards.

It is not a good idea to run a GUI session with the root user. It can be 
done, but better if you first explain what is goal for doing it so...

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.14.27...@gmail.com

Re: Problen installing Debian

On Sat, 02 Jul 2011 18:30:56 -0400, Robert Mansell wrote:

> I installed Debian on my desktop and it works fine. I tried installing
> Debian on a laptop and a another desktop and neither computer
> is even booting up. Can anyone help?

And the error you get is...?
And the error happens, at what stage of the install...?

More information is required :-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.03.14.29...@gmail.com

multiple images and usb not working in kvm

2011-07-03 Thread Khosrow Hassani

Hi,
I am running kvm from Squeeze. the problem I am having is that kvm -hda 
disk1.img -hdb disk2.img doesn't give me 2 drives in my Windows xp inside kvm, 
even when I run it as root. there is always only one dirve (C). I created the 
other image using kvm-img with qcow2 format. the -usb works only for root but 
not for normal user! 
any idea?

thanks,
Khosrow

Re: Computer instability under Debian Stable


On 03/07/2011 15:10, Adrian Levi wrote:

I don't see anything on the screen, Can't wake up the screen (it goes
blank) no oops, no nothing. Dosen't even respond to a num-lock,
caps-lock button press.

Adrian

OK, so you may want to use a live cd to inspect the Debian logs...?

Nicolas


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

Archive: http://lists.debian.org/4e1078d1.2040...@yahoo.fr

Re: NetworkManager (was: Re: Stranded between lenny and squeeze)

2011-07-03 Thread Curt

On 2011-07-02, Camaleón  wrote:
>
> And of course, warning about NM can leave the system disconnected is a 
> very good point (I didn't know NM can take that path...), so in the evnt 
> this can happen and the OP is using NM, he can just turn it off before 
> doing the upgrade and turn it on aftwewards.

What's wrong with just doing "apt-get -d dist-upgrade" first, thus
rendering the whole question of NM dropping the connection or not moot.

Or am I missing something?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnj10tjv.31e.cu...@einstein.electron.org

Re: Computer instability under Debian Stable

2011-07-03 Thread green

Adrian Levi wrote at 2011-07-03 01:43 -0600:
> My issue is I have no sound output and overnight the computer will
> hard lock-up so that the num-lock light won't even toggle.

If you are not getting any sound anyway, have you tried removing all the snd 
modules?


signature.asc
Description: Digital signature

Re: monitor detection maybe not working

On Sat 02 Jul 2011 at 10:44:51 -0700, Paul Scott wrote:

> I wasn't sure whether you were giving me an example or the exact line I  
> needed.  The above gives:
>
> X Error of failed request:  BadName (named color or font does not exist)
>   Major opcode of failed request:  150 (RANDR)
>   Minor opcode of failed request:  16 (RRCreateMode)Thanks
>   Serial number of failed request:  31
>   Current serial number in output stream:  31

You have probably tried to add the same mode twice. There is also a
missing --addmode.

1. See the present modes X uses with the command 'xrandr'.

2. Generate a modeline with 'cvt 1280 1024'. 

3. Describe the new mode to X:

xrandr --newmode 

4. Add the mode for VGA-1 to use:

xrandr --addmode VGA-1 1280x1024_60

5. Check the output of the 'xrandr' command.

6. Switch to using X with 1280x1024_60:

xrandr --output VGA-1 --mode 1280x1024_60


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703131701.GT15615@desktop

Re: Experience of Debian in a Macbook pro

2011-07-03 Thread Jerome BENOIT


Hello,

On 03/07/11 14:19, lee wrote:

Jerome BENOIT  writes:


The very first stage is to install refit ( http://refit.sourceforge.net/ ) from 
Mac OS X.
And then Debian can be installed quite as usual.
For more details see http://wiki.debian.org/MacBookPro


Thanks for the info :)  It seems once you get refit working, you could
use a Debian installer CD and get it installed.  However, the Mac sucks
too much to try: You can't install more then two disks,


what do you mean by disk ?

 and you can't

install any of them in the right orientation.


I am getting more confused here:
are you dealing with a MacBookPro or a MacPro ?

  I have another disk I

could use (if the Mac supports SATA disks),  but since it's always been
installed in the right orientation, it's too likely to fail.


Your issues seem rather as hardware issues.

Jerome


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

Archive: http://lists.debian.org/4e106abf.4090...@rezozer.net

Re: Computer instability under Debian Stable

2011-07-03 Thread Adrian Levi

On 3 July 2011 21:27, lee  wrote:

> You need to figure out what happens to trigger the freezing.  Are there
> any entries in syslog that might indicate something?  There's cron
> scripts running over night ... Perhaps the easiest way to approach this
> is setting the system clock 12 hours or so ahead and see if the freeze
> occurs at a different time.  If it does, you can try to track down what
> scripts are running over night and find out which one causes the
> freeze.
>
> Or you could try to stop the cron daemon and see if it still freezes.
>
> Take a look at /Documentation/sysrq.txt in the kernel source
> tree. Perhaps you can get at least some info when the computer is frozen
> with that.

I'll have to try sysrq key combinations.

Adrian

-- 
24x7x365 != 24x7x52 Stupid or bad maths?
 hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CABAdhH4F7aknpS5h9EH+o9hf9EoufpQ9-E7mDmiMBrd=x2r...@mail.gmail.com

Re: Debian 6 causes my SunFire T2000 system to not boot

2011-07-03 Thread Osamu Aoki

On Thu, Jun 30, 2011 at 09:43:51AM -0700, Scott Simpson wrote:
> I'm using 6.2.0.1 from June 26th. Should be pretty current. I can think of 
> two 
> approaches:

I see. I overlooked this.  Dah ...  Sorry for noise.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703125337.gb10...@debian.org

Re: Computer instability under Debian Stable

2011-07-03 Thread Adrian Levi

On 3 July 2011 18:56, Nicolas Bercher  wrote:

Hi Nicolas,

> So, before upgrading the kernel to 2.6.38, where you using the standard
> stable Debian kernel (2.6.32)?  If not (but seems yes), maybe downgrading
> the kernel back to the stable one is a good thing to test.

The problem was also in 2.6.32 ans was the reason I tried 2.6.38.

> Maybe this is still a hardware issue (typically bad electrical contacts) you
> have temporarly disabled because of physical manipulations on the machine.
>  So, I encourage you to retry Debian and see how long the uptime can be.  Of
> course this test may require several days...

The chassis is fine, Running an Ubuntu Live CD and Win7Pro 64bit works
flawlessly.
If I reboot out of Ubuntu it will fail overnight, sometimes less than 2 hours.

> Another thing, have you see any kernel oops (Call Trace, etc.) in the logs?
> Did you try to unload kernel modules you might have installed recently?

I don't see anything on the screen, Can't wake up the screen (it goes
blank) no oops, no nothing. Dosen't even respond to a num-lock,
caps-lock button press.

Adrian

-- 
24x7x365 != 24x7x52 Stupid or bad maths?
 hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cabadhh4-aawuk_nuxbcno7v-f5wwtvwchabiddgm2slnam3...@mail.gmail.com

Re: Debian 6 causes my SunFire T2000 system to not boot

2011-07-03 Thread Osamu Aoki

Hi,

Wow SunFire T2000... That is fancy ULTRASPARC machine.

On Thu, Jun 30, 2011 at 09:43:51AM -0700, Scott Simpson wrote:
> I'm using 6.2.0.1 from June 26th. Should be pretty current. I can think of 
> two 
> approaches:
> 
> 1. Boot version 5 and see if my video card isn't the one mentioned in the bug 

Which bug ???

> and try disabling that on the boot line.

version 5? 

Debian 5.0 (lenny)  That is old.  The latest stable release is Debian
6.0 sarge (6.0.2).  Why trying to use oldstable image?

You should check our site first for the latest situation:
  http://www.debian.org/

> 2. Remove the video card.
> 
> I'm going to try both. This is really depressing since the system is down and 
> I can't get it booted. Sigh

Since you sounds like booted system, please follow instruction of
installation via ssh.  If CD have problems, follow netboot methods.
Video card support is not going to be the initial issue if you do like
these.  These are all written in install guide etc.. for Debian 6.0
sarge.

  Debian SPARC Port
  http://www.debian.org/ports/sparc/

  Debian 6.0 -- Release Notes
  http://www.debian.org/releases/stable/releasenotes
  Release Notes for Debian GNU/Linux 6.0 (squeeze), SPARC
  http://www.debian.org/releases/stable/sparc/release-notes/

  Debian GNU/Linux Installation Guide
  http://www.debian.org/releases/stable/installmanual
  http://www.debian.org/releases/stable/sparc/ 

Please check important mailing list archives first before discussing
problem.

http://lists.debian.org/debian-boot/
http://lists.debian.org/debian-sparc/

Osamu


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110703125033.ga10...@debian.org

Re: install squeeze con core i5 2500 motherboard 1155

2011-07-03 Thread Pablo Sánchez


lee, i didn't take a look at syslog. dmesg showed they were there.

What i ended doing, was play with the hotplug option for each disk on the bios, 
and it worked.
I have the system running, but i'm now trying to learn what that option means .
I don't think it's a real hotplug thing, as changing drives without shutting 
down the computer.
Actually got it working setting two of the drives with hotplug on and one off .


BTW it's a core i 2400 not 2500 .

Regards

Pablo Sánchez.



Pablo Sánchez  writes:


Well, i got an ASUS P8H67-M LX with H67 B3 revision intel chipset  with a core 
i5 2500 .

The machine has 3 Samsung 1TB disks , that i see on the bios config, connected 
to sata 3gb ports .

After inserting an usb stick with realtek firmware-realtek 0.28, config the 
network,
I'm stuck on Scanning disk on starting up the partitioner on 50 % progress : 
it's stalled .

Do you see any messages about the disks in the syslog?





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

Archive: http://lists.debian.org/4e106573.9050...@adinet.com.uy

Re: Computer instability under Debian Stable

2011-07-03 Thread lee

Adrian Levi  writes:

> My home server has been experiencing instability issues running Debian stable.
>
> My issue is I have no sound output and overnight the computer will
> hard lock-up so that the num-lock light won't even toggle. I updated
> to 2.6.38 thinking it might be a kernel compatibility issue but the
> problem remains. I downloaded and booted from an Ubuntu 11.04 CD and
> the system has been running stable over the last 5 something days.

You need to figure out what happens to trigger the freezing.  Are there
any entries in syslog that might indicate something?  There's cron
scripts running over night ... Perhaps the easiest way to approach this
is setting the system clock 12 hours or so ahead and see if the freeze
occurs at a different time.  If it does, you can try to track down what
scripts are running over night and find out which one causes the
freeze.

Or you could try to stop the cron daemon and see if it still freezes.

Take a look at /Documentation/sysrq.txt in the kernel source
tree. Perhaps you can get at least some info when the computer is frozen
with that.

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87boxbli3m@yun.yagibdah.de

Re: install squeeze con core i5 2500 motherboard 1155

2011-07-03 Thread lee

Pablo Sánchez  writes:

> Well, i got an ASUS P8H67-M LX with H67 B3 revision intel chipset  with a 
> core i5 2500 .
>
> The machine has 3 Samsung 1TB disks , that i see on the bios config, 
> connected to sata 3gb ports .
>
> After inserting an usb stick with realtek firmware-realtek 0.28, config the 
> network,
> I'm stuck on Scanning disk on starting up the partitioner on 50 % progress : 
> it's stalled .

Do you see any messages about the disks in the syslog?


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87hb73lis5@yun.yagibdah.de

Re: OT: Camaleón

On Sunday 03 July 2011 04:26:52 T o n g wrote:
> On Sat, 02 Jul 2011 12:36:14 +1000, Scott Ferguson wrote:
> > you're best sticking with Camaleón if possible - she does run Gnome and
> > . . .
>
> I don't know western names well and I had always thought that Camaleón is
> a man, although being "overly" polite (than ordinary man).
>
> Is Camaleón really a girl?

No - a woman.  You didn't say "boy". ;-)

Her name is almost unique to her - and we in the west can't tell from her name 
either.

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107031050.43864.lisi.re...@gmail.com

Re: Computer instability under Debian Stable

On 03/07/2011 09:43, Adrian Levi wrote:

My home server has been experiencing instability issues running Debian stable.

My issue is I have no sound output and overnight the computer will
hard lock-up so that the num-lock light won't even toggle.
I updated to 2.6.38 thinking it might be a kernel compatibility issue
but the problem remains.
I downloaded and booted from an Ubuntu 11.04 CD and the system has
been running stable over the last 5 something days.

Ram has passed countless passes on Memtest86+, The CPU i'd have
figured would have failed running any OS.
Likewise the system is stable running Win 7 64bit.

I have attached an lspci -vv and lsmod.
I have a feeling that my issue might be Debians firmware stripped
kernel but don't know where else to look for problems, dmesg dosen't
seem to provide any hints.

So, before upgrading the kernel to 2.6.38, where you using the standard stable Debian
kernel (2.6.32)? If not (but seems yes), maybe downgrading the kernel back to the stable
one is a good thing to test.

Maybe this is still a hardware issue (typically bad electrical contacts) you have
temporarly disabled because of physical manipulations on the machine. So, I encourage you
to retry Debian and see how long the uptime can be. Of course this test may require
several days...

Another thing, have you see any kernel oops (Call Trace, etc.) in the logs?
Did you try to unload kernel modules you might have installed recently?

Nicolas

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

Archive: http://lists.debian.org/4e102eaf.2090...@yahoo.fr

Re: Squeeze and root in graphical mode


On 03/07/2011 10:25, alex.pad...@laposte.net wrote:

Hi,

I would like to know if the root have a graphical environnement ?
I don't connect with login root with the password of root but in
terminal window I can connect me as root.
Regards.

Alex PADOLY


Probably because you have to authorize X connections to any other user:

 xhost +

before su as root (or whatever other user).

Nicolas


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

Archive: http://lists.debian.org/4e102bf3.60...@yahoo.fr

Squeeze and root in graphical mode

2011-07-03 Thread alex . padoly

Hi,

 I would like to know if the root have a graphical environnement ?
 I don't connect with login root with the password of root but in terminal 
window I can connect me as root.
 Regards.

 Alex PADOLY

Re: cannot go back from nouveau to nv


On 04/02/2011 03:44 AM, Sven Joachim wrote:

On 2011-04-02 10:24 +0200, Fumiaki Okushi wrote:


On 04/02/2011 12:43 AM, Sven Joachim wrote:

On 2011-04-02 08:49 +0200, Fumiaki Okushi wrote:


I'm running Debian Squeeze amd64.
I'm trying to go back to using nv after trying to get nouveau working
and failed.

I'm sorry that nouveau did not work for you.  Could you please elaborate
what the problem was?

Thank you for your response.

To be honest with you, I don't know what the problem was.
First, my monitor refused saying that it's out of range.
The dmesg showed that it inferred the screen size to be 1024x768,
so I booted with video=1920x1080 (native monitor size).

I would suspect that the monitor is broken and provides no or invalid
EDID.


or that read-edid is broken?  ddcprobe seems to provide correct 
information for my ViewSonic VA703b.  read-edid does not.


Paul Scott



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

Archive: http://lists.debian.org/4e1020b2.9080...@ultrasw.com

Re: NVIDIA - URGENT

2011-07-03 Thread Aniruddha

On Sat, Jul 2, 2011 at 6:44 PM, Hans Vogelsberger  wrote:
> Todays testing update, safe-upgrade and full-upgrade totally killed my X
> which ran with NVIDIA driver. Even this posting I must send from my old
> computer which is in a terrible state because I did nothing on it since I
> use the new one. Without X, most work I do on my computer cannot be done.
>


I had the same issue I've solved doing a upgrade to sid. I recommend
you to install Debian stable though.


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

Computer instability under Debian Stable

2011-07-03 Thread Adrian Levi

My home server has been experiencing instability issues running Debian stable.

My issue is I have no sound output and overnight the computer will
hard lock-up so that the num-lock light won't even toggle.
I updated to 2.6.38 thinking it might be a kernel compatibility issue
but the problem remains.
I downloaded and booted from an Ubuntu 11.04 CD and the system has
been running stable over the last 5 something days.

Ram has passed countless passes on Memtest86+, The CPU i'd have
figured would have failed running any OS.
Likewise the system is stable running Win 7 64bit.

I have attached an lspci -vv and lsmod.
I have a feeling that my issue might be Debians firmware stripped
kernel but don't know where else to look for problems, dmesg dosen't
seem to provide any hints.

Basic rundown of the system is:
AMD 235 40w CPU
Asus M4A88TD-V EVO/USB3 Motherboard.
16G DDR3 1333 Ram (Kingston)
6 HDD comprising:
750G for OS,
5x 2TB in software raid 6,
Satasil card in JBOD mode for extra SATA ports.

I have attached files from Ubuntu 11.04 Live CD where everything works.

I would appreciate pointers as to where to continue my search for the problem.

Adrian


-- 
24x7x365 != 24x7x52 Stupid or bad maths?
 hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
Subsystem: ASUSTeK Computer Inc. Device 843e
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [b0] Subsystem: ASUSTeK Computer Inc. Device 843e
Kernel modules: shpchp

00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge 
(PCIE port 5) (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, 
L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 
<64ns, L1 <1us
ClockPM- Surprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #10, PowerLimit 25.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, 
Selectable De-emphasis: -3.5dB
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0300c  Data: 4149
Capabilities: [b0] Subsystem: ASUSTeK Computer Inc. Device 843e
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [110 v1]

Re: monitor detection maybe not working - another try