Bug#698197: forwarded bug address

[Will Set]

https://bugs.freedesktop.org/show_bug.cgi?id=59436

thankyou

Bug#627019: linux-image-2.6.39-rc7-686-pae: several kernel hangs before geting to login

[Will Set]

3.2.15 fixed for me.

Bug#649304: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels

[Will Set]

3.2.15  fixed  for me.

Bug#665413: BUG: unable to handle kernel paging request

[Will Set]

Friday, March 23, 2012 11:06 PMDaniel Kahn Gillmor wrote:
On Fri, 23 Mar 2012 19:51:37 -0700 (PDT), Will Set  
wrote:

>> I know of 5 bug reports that confirm using boot parameter - processor.nocst=1
>> as a workaround for kernels < 2.6.38
>
>Thanks, i will try this the next time i get a chance to restart this
>machine (it's currently crashed again and i don't have physical access
>right now).

Probably not necessary since you are using 2.6.32 (squeeze) kernels.
Normally, kernels older than 2.6.39 don't need the extra boot parameter.
But 4 GiB of ram is max for the board and although HP has spec for 4 GiB of ram 
for your model, 
they also have notes recommending only 2 GiB of Ram, in another doc.
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c00072736/c00072736.pdf

>
>Do you have a link to a couple of these bug reports so i could read them
>myself?  I'd appreciate it if you do.

https://bugzilla.redhat.com/show_bug.cgi?id=727865

>
>> linux-image-2.6.39 through linux-image 3.3.0-rc6-686-pae - on both of
>> my 865g based boxes.
>
>I'm not sure what this sentence means -- is it related to the sentence
>above?  if so, how?

I have two computers with i865g chipsets and 1 GiB of ram each.
I'm not sure what I was thinking when I refered to kernels your not using.

>
>> Also, iirc, the bigmem kernel was swallowed by the 686-pae kernel, 
>> which might be a reason for the instability when using 486.
>
>I wouldn't expect the -486 flavor to be able to fully address all 4GiB
>of RAM (i.e. i doubt it would make use of the physical address
>extensions).  But i don't understand why this would cause instability.
>My workload during these crashes is definitely not memory-intensive.
>This is the first i'm hearing that the -486 flavor would cause
>instability on highmem machines.
>
>Can you point me to some documentation so i could understand why that
>might be the case?

Here is a link to linux-image-2.6.32-5-686-bigmem
http://packages.debian.org/squeeze/linux-image-2.6-686-bigmem.

best regards,
Will

Bug#665413: BUG: unable to handle kernel paging request

[Will Set]

  Friday, March 23, 2012 6:42 PM Daniel Kahn Gillmor

>The only kernel boot parameter on this run was console=ttyS0,115200n8 --
>i brought up the rest of the system by hand during this fallback
>attempt.

According to HP,

http://h18000.www1.hp.com/products/quickspecs/11632_ca/11632_ca.html    --->

http://h18000.www1.hp.com/products/quickspecs/11632_di/11632_div.html#Standard%20Features%20-%20Select%20Models

the mobo has an 865g chipset.
I know of 5 bug reports that confirm using boot parameter - processor.nocst=1
as a workaround for kernels  < 2.6.38
linux-image-2.6.39  through linux-image 3.3.0-rc6-686-pae   - on both of my 
865g based boxes.

Also, iirc, the bigmem kernel was swallowed by the 686-pae kernel, 
which might be a reason for the instability when using 486.

>
>I've run memtest86+ on this machine and the memory shows no errors in
>that program.
>
>Let me know if there are other details i can report that would help with
>this bug report; sorry i'm not able to get the machine to a stable point
>yet to run reportbug on it directly.

best regards,
Will

Bug#656375: libdrm-intel1: screen corruptions, kernel message "*ERROR* Prepared flip multiple times"

[Will Set]

 Saturday, January 21, 2012 5:20 AMCyril Brulebois wrote:
[...]
a couple of my installs ( syslogs ) grew to several GiB`s 
for the two weeks of so I noticed this page_flip spamming on my old 
i865g stuff.

>Back to the original topic: it is very difficult for Intel techs to
>support old (and I'm just echo-ing their views on hardware) hardware,
>even if older versions of the x driver might have worked at some point.
>That is sad, but that's the state of affairs today.

I follow right behind you on this note.
I'm still amazed at how much hardware (old and new) this OS supports.

Sorry for the extra noise.
Will 

>
>Mraw,
>KiBi.

Bug#656375: libdrm-intel1: screen corruptions, kernel message "*ERROR* Prepared flip multiple times"

[Will Set]

Saturday, January 21, 2012 4:17 AMJonathan Nieder wrote:


>Cyril Brulebois wrote:
>> Jonathan Nieder  (21/01/2012):
>
 After logging into GNOME, I started getting LOTS of
 [  239.494761] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple
 times
 in kernel log repeated ever few microseconds.

Already fixed 2 weeks ago...

>>>
>>> Kernel log = kernel bug. :)  Reassigning.
>>
>> No. Please don't waste our time.
>
>Sorry to waste your time.  My tongue was in cheek when I said "kernel
>log = kernel bug", and I apologize for that.
>
>However, I fear I must have committed some other offense on top of
>that.  Could you elaborate so I know what not to do again?
>
>Confused,
>Jonathan
>
Will

Bug#627019: several kernel hangs before geting to login

[Will Set]

  

Monday, December 26, 2011 5:24 PMWill Set wrote:

>Sunday, December 25, 2011 4:24 AM Jonathan Nieder wrote:
>>Will Set wrote:
>>> Jonathan Nieder wrote
>>
>>>> but the boot fails in some way unless you
>>>> add processor.nocst=1 to the kernel command line.  
[...]

>I had to test using  3.1.0-1-686-pae 
>( which I believe is an old experiemtnal kernel and not a sid or wheezy kernel)

ooops : sorry for confusion: 3.1.0-1-686-pae is a sid kernel.

>I rebooted 3.1.0-1-686-pae 10 times with hyperthreading enabled,
>and got 10 different dmesg problems  very
 near if not exactly while 
>udev was populating /dev
>
Best Regards,
Will

Bug#627019: several kernel hangs before geting to login

[Will Set]

  Friday, December 23, 2011 6:54 PMJonathan Nieder wrote
>Hi Will,
>
>Will Set wrote:
>
>> I was able to take three pictures of the boot messages by scrolling up the 
>> boot buffer from the login prompt, while booting 3.2.0-rc4-686-pae
>> to illustrate what I did my best to explain yesterday.
>>
>> I'll also attach the dmesg.udev-2 and acpidump-udev-2 
>
>Thanks.
>
>If I understand you correctly, udev 175-2 segfaults at boot.

No, Not always a segfault.

Sometimes udev just hangs, leaving the machine without keyboard access.
And it's way to early in the boot process to get normal network connectivity,

Other times the kernel will panic.
And when the kernel panics I'm not able to save any data from the boot buffer 
other than the screen full of data showing when the boot buffer finishes 
sending the trace data to the buffer.

Boot also fails in at least one other way.
Where I can see a "udev settle" message and  messages showing the /sys 
directory structure.
But when this type of issue happens I am able to login and run the system 
console.
But, if I start the xserver under these condition I have no keyboard or mouse.

These failures have not changed much since I initially reported this.
But I have seen the failures so may times now that I'm a bit less confused by 
them.


> udev 175-3 does _not_ segfault, 

No, udev 175-3 also segaults iirc
but I have not "re - upgraded" udev to 175-3 to test exactly what it shows, yet.

>but the boot fails in some way unless you
>add processor.nocst=1 to the kernel command line.  

Yes, 
Adding processor.nocst=1 has always worked for me on all effected kernels I've 
tested so far.

But, the boot fails consistently when using udev 175-3  unstable with 
3.2.0-rc4-686-pae 
and without processor.nocst=1 added to the boot command. 

>Which is already
>weird, since the only advertised changes in 175-3 were a fix to the
>systemd service file and a fix to udev rules for Xen support.  Based
>on the kernel log you sent, you are not using systemd, and I assume
>you're not using Xen.

Please understand that a failed boot, appears - at least from what I can see 
here, 
always to have something to do with udev.

>
>This is on the machine with a D865GBF motherboard.

No,
This report is and always will be  Intel D865GRH mobo.
My other mobo is an Intel D865PERLK

There is another Debian user that has an Intel D865GBF mobo  
with a  "very" similar debian bug report filed.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631597

[9.132009] Pid: 311, comm: modprobe Tainted: G  D
2.6.39-2-686-pae #1  /D865GBF

And this user has also filed a bug report upstream after Ben requested he do so.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631597#15

>
>Anyway, you were able to take advantage of this situation to get an acpidump.
>
>Are these results reproducible?

Yes, But, the fail is not consistently one failure.
I had three failed boot attempts today while testing with a clean kernel 
commandline.
ie: processor.nocst=1 was not added to the commandline. on any of my 4 boot 
attempts today.
The fourth time the machine booted to a useable state.

>

I hope you can find some clues in this email that will make this issue less 
weird to understand.
And as always I'll do my best to get timely responses back to you, even though 
I have been busy 
elsewhere recently.
I've not had my usual amount of time to devote to testing and learning about 
the kernel.

Best Regards,
Will

>Hope that helps,
>Jonathan
>

Bug#650676: xserver-xorg: weird colors and garbled video after update

[Will Set]

 Thursday, December 1, 2011 7:56 PM Rares Aioanei  wrote:
>Package: xserver-xorg
>Version: 1:7.6+9
>Severity: normal
>

>

>After updating my system and starting X, the Fluxbox theme that's
>supposed to be green is black now (standard zimek_green), 


Does the fluxbox style (standard zimek_green) display correctly  after, 

 < restart fluxbox > ?

see also:  fluxbox style bugs: 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616655
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649935



>konsole's
>borders are pink instead of beige and starting a video in vlc shows
>garbled images and weird colors. This worked before the update with the
>same kernel.
>
>-- Package-specific info:
>X server symlink status:
>
>lrwxrwxrwx 1 root root 13 Nov 12 19:43 /etc/X11/X -> /usr/bin/Xorg
>-rwxr-xr-x 1 root root 2056592 Nov 29 18:11 /usr/bin/Xorg
>
>VGA-compatible devices on PCI bus:
>--
>03:00.0 VGA compatible controller [0300]: nVidia Corporation NV44 [GeForce 
>6200 TurboCache(TM)] [10de:0161] (rev a1)

I'm also wondering why, 3.2.0-rc3-00023-g401d006 is dropping nouveau and using 
fbdev.

>
>/etc/X11/xorg.conf does not exist.
>
>/etc/X11/xorg.conf.d does not exist.
>
>KMS configuration files:
>
>/etc/modprobe.d/i915-kms.conf:
>  options i915 modeset=1
>/etc/modprobe.d/radeon-kms.conf:
>  options radeon modeset=1
>
>Kernel version (/proc/version):
>---
>Linux version 3.2.0-rc3-00023-g401d006 (arares@debianfs1) (gcc version 4.6.2 
>(Debian 4.6.2-5) ) #3 SMP Mon Nov 28 19:26:42 EET 2011

I realize the main issue is nouveau/fbdev driver for this report.

Just checking if the fluxbox style issue is related or not.


regards,

Will

Bug#649304: needed for 686-pae kernels

[Will Set]

 Saturday, November 19, 2011 2:32 PM Jonathan Nieder : wrote
>forcemerge 627019 649304
>quit
>
>Hi Will,
>
>Will Set wrote:
>
>> [Subject:  needed for 686-pae kernels]
>
>You haven't described the actual symptoms here.  I assume that they
>are segfaults and hangs, as before?

Yes, the kernel still hangs early in boot.  The difference being 
the kernel hang without   looks to me to be more 
consistent now, than when I originally reported
the problem with the 2.6.39-rc7-686 kernel.

>
>> I first noticed this issue using 2.6.38-rc5-686 and 2.6.38-rc6-686. 
>> Although, 2.6.38-1-686 worked out of the box, the regession showed again 
>> using 2.6.39-rcX kernels,
>> and continues to show using all 686-pae kernels.
>> Adding  to the kernel commandline works around the issue.
>>
>> Using 486 kernels is another workaround to this issue.
>
>Please send full "dmesg" output from booting up and reproducing the
>bug.  Attaching "acpidump" output would be useful, too.

I'll also be away from my desk for a few days, and will followup, 
with dmesg and acpidump, as soon as I return.

Best Regards,
Will


>
>> see: #627019  linux-image-2.6.39-rc7-686-pae: several kernel hangs ... 
>
>Thanks for filing a separate bug so we can keep track of the
>information about each machine separately.  I'm marking the two
>reports as related for easy reference.
>
>Thanks and hope that helps,
>Jonathan

Bug#649304: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels

[Will Set]

Package: linux-2.6

Version: 3.1.1-1
Severity: normal
Tags: d-i

I first noticed this issue using 2.6.38-rc5-686 and 2.6.38-rc6-686. 
Although, 2.6.38-1-686 worked out of the box, the regession showed again 
using 2.6.39-rcX kernels,
and continues to show using all 686-pae kernels.
Adding  to the kernel commandline works around the issue.

Using 486 kernels is another workaround to this issue.

see: #627019  linux-image-2.6.39-rc7-686-pae: several kernel hangs ... 


-- Package-specific info:
** Version:
Linux version 3.1.0-1-686-pae (Debian 3.1.1-1) (b...@decadent.org.uk) 
(gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:24:20 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-686-pae root=/dev/sdb8 ro processor.nocst=1

** Not tainted

** Kernel log:
[5.702701] [drm] nouveau :01:00.0: Detected an NV40 generation card 
(0x04a100a1)
[5.704709] IR RC5(x) protocol handler initialized
[5.706708] [drm] nouveau :01:00.0: Attempting to load BIOS image from 
PRAMIN
[5.798468] [drm] nouveau :01:00.0: ... appears to be valid
[5.798533] [drm] nouveau :01:00.0: BIT BIOS found
[5.798591] [drm] nouveau :01:00.0: Bios version 05.44.a2.07
[5.798650] [drm] nouveau :01:00.0: TMDS table version 1.1
[5.798707] [drm] nouveau :01:00.0: BIT table 'd' not found
[5.798765] [drm] nouveau :01:00.0: Found Display Configuration Block 
version 3.0
[5.798836] [drm] nouveau :01:00.0: Raw DCB entry 0: 01000300 0028
[5.798895] [drm] nouveau :01:00.0: Raw DCB entry 1: 02011310 0028
[5.798953] [drm] nouveau :01:00.0: Raw DCB entry 2: 01011312 
[5.799012] [drm] nouveau :01:00.0: Raw DCB entry 3: 020223f1 0084c030
[5.799071] [drm] nouveau :01:00.0: DCB connector table: VHER 0x30 5 7 2
[5.799131] [drm] nouveau :01:00.0:   0: 0x: type 0x00 idx 0 tag 
0xff
[5.799202] [drm] nouveau :01:00.0:   1: 0x2230: type 0x30 idx 1 tag 
0x08
[5.799272] [drm] nouveau :01:00.0:   2: 0x0110: type 0x10 idx 2 tag 
0xff
[5.799341] [drm] nouveau :01:00.0:   3: 0x0111: type 0x11 idx 3 tag 
0xff
[5.799410] [drm] nouveau :01:00.0:   4: 0x0113: type 0x13 idx 4 tag 
0xff
[5.799484] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 
0xDD1E
[5.802028] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 
0xE00C
[5.807894] IR RC6 protocol handler initialized
[5.815248] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset 
0xE546
[5.815342] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset 
0xE6A3
[5.816531] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset 
0xE82C
[5.816604] [drm] nouveau :01:00.0: mem timing table length unknown: 14
[5.816664] [drm] nouveau :01:00.0: timingset 255 does not exist
[5.833530] i2c-core: driver [msp3400] using legacy suspend method
[5.833597] i2c-core: driver [msp3400] using legacy resume method
[5.836820] [drm] nouveau :01:00.0: 1 available performance level(s)
[5.836885] [drm] nouveau :01:00.0: 0: memory 532MHz core 350MHz 
fanspeed 100%
[5.836963] [drm] nouveau :01:00.0: c: memory 401MHz core 200MHz
[5.837330] [TTM] Zone  kernel: Available graphics memory: 448398 kiB.
[5.837449] [TTM] Zone highmem: Available graphics memory: 516082 kiB.
[5.837514] [TTM] Initializing pool allocator.
[5.837601] [drm] nouveau :01:00.0: Detected 256MiB VRAM
[5.837895] agpgart-intel :00:00.0: AGP 3.0 bridge
[5.837974] agpgart: modprobe tried to set rate=x12. Setting to AGP3 x8 mode.
[5.838116] IR JVC protocol handler initialized
[5.838325] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode
[5.838540] nouveau :01:00.0: putting AGP V3 device into 8x mode
[5.838634] [drm] nouveau :01:00.0: 256 MiB GART (aperture)
[5.838876] [drm] nouveau :01:00.0: Saving VGA fonts
[5.914955] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.915027] [drm] No driver support for vblank timestamp query.
[5.917941] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder 
(output 0)
[5.918021] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder 
(output 1)
[5.918097] [drm] nouveau :01:00.0: Setting dpms mode 3 on tmds encoder 
(output 2)
[5.918179] [drm] nouveau :01:00.0: Setting dpms mode 3 on TV encoder 
(output 3)
[5.948032] intel8x0_measure_ac97_clock: measured 55898 usecs (2693 samples)
[5.948101] intel8x0: clocking to 48000
[5.962545] IR Sony protocol handler initialized
[5.971068] IR MCE Keyboard/mouse protocol handler initialized
[5.979526] bttv0: audio absent, no audio device found!
[6.057390] i2c-core: driver [tuner] using legacy suspend method
[6.057461] i2c-core: driver [tuner] using legacy resume method
[6.058546] lirc_dev: IR Remote Control driver registered, major

Bug#627019: several kernel hangs before geting to login

[Will Set]

Tuesday, November 15, 2011 3:10AM Jonathan Nieder wrote:
>
>Hi,
>
>Will Set
 wrote:
>
>- you have tested some 3.1.0-1-686-pae kernel (I assume
>   3.1.0-1~experimental.1 from experimental).

Yes, 3.1.0-1~experimental.1 from experimental 

>- unless you add "processor.nocst=1", it reliably hangs at boot time.
>- adding "processor.nocst=1" makes it boot without hanging.
>- in addition to this machine, you have another machine that has an
>   i865 chipset.  It produces the same symptoms.
>- in addition, you have a machine with an i915 chipset, which works
>   fine, with no need for special boot parameters.

Yes.

>
>In the bug log, I see:
>
>- this is an Acer Aspire One AO521, board JV01-NL, BIOS v1.08
>- the chipset is indeed an 82865G
>- oopses are all over the place.  Feels like corruption somewhere.
>- with debug=3, we see that the DMI
 says this is board D865GRH, BIOS
>   BF86510A.86A.0077.P25.0508040031 --- wait, are these even the same
>   machine?
>- the other i865 is D865PERLK.

What I have gathered so far from reading docs and reports
 it looks like a C state problem.
I think there isn't a CST in this processor... 
If CST adjusts processor voltage and stepping for energy saving when idle? 
I;m thinking legacy FADT is all this chip can use..

It's not a big deal for me to use the workaround Len Brown suggested
https://bugzilla.redhat.com/show_bug.cgi?id=727865#c16
for 2.6.38-rc  and newer kernels. --->
Debian stable / 2.6.32-5-686 kernel still works fine.
 
And I'm still OK if it's an upstream ( will not fix issue).
But I would like a fix as well, if one is possible.  

>
>Ok.  The processor.nocst=1 workaround indicates that the ACPI
 tables
>might be incorrect or being incorrectly parsed.  For the D865GBF, such
>a problem is being tracked as bug#630031 and upstream bug 38262.
>Compare v2.6.22-rc1~1112^2^2 (ACPICA: clear fields reserved before
>FADT r3, 2007-04-28).  To move forward on that, the right thing to do
>would be to get in touch with Len Brown, for example by answering his
>questions from the Fedora bugtracker at
><https://bugzilla.redhat.com/show_bug.cgi?id=727865>.

All my answers to  Len Browns questions are identical to
Adam 's  https://bugzilla.redhat.com/show_bug.cgi?id=727865#c17
answers to Len Browns questions.

$ grep . /sys/devices/system/cpu/cpu0/cpuidle/*/*  -->  doesn't exist.
$/sys/firmware/acpi/tables/dynamic/* -->  doesn't exist in the filesystem.

>
>For the D865PERLK, a quick web search does not show anyone but you
>having this problem.
>
>You've said you have three boards you're checking with and only two
>exhibit the problem.  I'm not sure where the JV01-NL fits into the
>picture.

 I'm not sure how the JV01-NL got into the picture either.

>
>Anyway, for the future, it would be way less confusing to have one bug
>per machine, 

Yes, I agree 100%

>unless they are identically configured or we can
 be
>reasonably certain for some other reason that the
 same fix will apply
>to all of them.  

Yes,  at this preliminary stage, I think the issue is exactly the same, 
or at least close enough, on my two Intel 865 chipset machines.

Even though the two mobos are not identical,  
the processors, memory and disks  are identical in both machines.

>Please provide a summary of which machines that you
>use are affected and not affected, and I can clone this bug and let
>you know the bug number assigned to each.

I will file a separate bug report from the other machine.

>
>Thanks for your help and patience.
>
>Regards,
>Jonathan

Best Regards,
Will

Bug#645736: Please hide xterm and uxterm icons from the GNOME menu

[Will Set]

 Wednesday, October 19, 2011 10:48 AM Fabian Greffrath wrote:
Am 19.10.2011 16:41, schrieb Will Set:
>> the request to hide xterm icons from the gnome-desktop maybe a moot point.
>> Please take a look at the gnome-menu rewrite ...
>> and see if the xterm icons still adversely affect the Gnome-Desktop
>> experience.
>I am using the fallback session (i.e. gnome-panel with classic menu) of GNOME 
>3 myself. That's how this icon caught my attention. The fact that it probably 
>will not show up on the firts page of gnome-shell's application overview does 
>not imply that this issue should remain unfixed.
 sorry, I don't follow..
are you planning to look at the gnome-menu rewrite?

Bug#645736: Please hide xterm and uxterm icons from the GNOME menu

[Will Set]

 
 Wednesday, October 19, 2011 3:22 AMFabian Greffrath  wrote: 
>Am 18.10.2011 18:14, schrieb Will Set:
>>  >a typical GNOME desktop has gnome-terminal installed and this should
>> Gnome desktop - new-features?
>> cc: ing to possible interested list and devs.
>
>What exactly do you mean?
Depending on,
which of the current changes made to Gnome in Debian experimental,
get released to Debian unstable in the next few weeks,
>gnome-terminal has always been a dependency of gnome-core.
the request to hide xterm icons from the gnome-desktop maybe a moot point.
Please take a look at the gnome-menu rewrite ...
and see if the xterm icons still adversely affect the Gnome-Desktop experience.

Bug#645736: Please hide xterm and uxterm icons from the GNOME menu

[Will Set]

Monday, October 17, 2011 4:17 PM Fabian Greffrath wrote:

>Package: xterm
>Version: 276-1
>Severity: minor
>
>Hi,
>
>a typical GNOME desktop has gnome-terminal installed and this should be the
Gnome desktop - new-features?
cc: ing to possible  interested list and devs. 
>most prominent terminal application known to its users. Since version 276-1 the
>xterm package provides another two icons to start other terminal applications,
>that are not at all integrated into the GNOME desktop, though. While I have no
>doubt these two additional starters are valuable in desktop environments that
>do not provide their own terminal application, they are simply confusing and
>redundant in GNOME. Thus, please cosider adding a line "NotShowIn=GNOME" to the
>two corresponding desktop files.
>

Bug#642066: linux-image-loongson-2f: Please include gnewsense patches [bug #34331] Request to submit linux patches upstream

[Will Set]

please re-read  the reply to your wishlist bug report. 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642066#10

Which is directing you to ask gnewsense project to submit their kernel changes 
to upstream kernel.org


1:
Ask please, the gnewsense project
http://www.gnewsense.org/Main/HomePage 

to submit their changes upstream. At  

http://kernel.org

2:

And please ask to have both wishlist bug reports you opened at savannah 

http://savannah.nongnu.org/bugs/?34331
and debian 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642066
closed[...]

or linked to 

a new wishlist request you make at the gnewsense project.


thanks for your cooperation.

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

[Will Set]

Thursday, October 13, 2011 10:07 AM Jort Koopmans wrote:

>>>Instead of patching this here and there with band aids, I suggest
>>>that everyone with an interest instead invests time in testing
>>>mdadm/experimental, which provides event-based assembly, 
>>
>>I was wondering what documentation the reporter was following. 
>>
>>I haven't seen RAID on USB supported in stable.
>
>I've not followed any documentation, 

I posted my question to the list for a reason.  hint! 

>I was just hoping to get it working
>since I assumed it would be possible. It was not aware of Raid 1 on USB
>being explicitly not supported, if that's the case you can also consider
>my report to be a feature request :), even though it applies to all
>slowly initialized devices (not per definition USB devices).

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

[Will Set]

Thursday, October 13, 2011 9:06 AM martin f krafft wrote:
>also sprach Jort Koopmans  [2011.10.12.2143 +0200]:
>> In the mean while I've checked another solution; moving the call
>> to the local-top scripts till after the ROOTDELAY loop (within the
>> local file).
>
>init-top/udev also uses it.
thanks for the clues :)
>
>> This works in my config. But this would delay finding the ROOT dir
>> in normal instances (where devices are quick enough)
>
>So?
>
>Instead of patching this here and there with band aids, I suggest
>that everyone with an interest instead invests time in testing
>mdadm/experimental, which provides event-based assembly, 

I was wondering what documentation the reporter was following. 

I haven't seen RAID on USB supported in stable.

>and helps
>porting the changes to current mdadm (since I don't have the time at
>the moment). And then, LVM is up next.

Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M

[Will Set]

Monday, September 19, 2011 9:18 AM  Michel Dänzer wrotew:
> On Mon, 2011-09-19 at 15:55 +0300, Tomi Leppänen wrote: 
>>  ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti:
>>  > On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: 
>>  > > la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti:
>>  > > > 
>>  > > >   Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote:
>>  > > > > pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder 
> kirjoitti:
>>  > 
>>  > > I wonder why my grub is just some colorful crap on bottom of my 
> screen.
>>  > > I can't really edit anything on fly but I have to always make 
> changes
>>  > > to /etc/default/grub and then issue update-grub. That may have 
> something
>>  > > to do with this bug.
>>  > 
>>  > It's further indication that the problem may stem from the BIOS, 
> or
>>  > possibly even the hardware itself.
>> 
>>  If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work
>>  completely. (though that card doesn't support interlacing)
>>  I can get dmesg for that too if needed but it takes probably a bit
>>  longer.
> 
> I don't think that'll buy anything at this point.

Problem  iirc, both your other video cards -- ATI Rage 128VR and Nvidia GeForce 
2 MX (AGP) --  have less than 64 MB of VRAM.
I've found with my old AGP cards, 64MBs  VRAM to be a minimum for mode 
switching as a general rule.
Mobos with video onboard have different limits.
I'm starting to see other pentium 4 limits with the newer 3.0.0 kernels,
so I'm not really surprised having troubles trying 3.0.0 kernels

And the PCI card is  IMHO way to new to be used in the PCI slot of that old 
mobo. 
The video card has almost as much processing power as the mobo does.
I'll bet the mobo's chipset can't access even half that Radeon 9200SE's 
resources.
> 
> 
>>  > > I also noticed that all of my memory is LOWMEM. Though graphics 
> card
>>  > > doesn't change that (tried with ATI Rage 128VR that has 
> trouble with DRI
>>  > > on Debian 6).
>>  > 
>>  > Does that card basically work though? Do you also get PCI related 
> errors
>>  > in dmesg with it?
>> 
>>  Yes, it does work.
> 
> Then it seems most likely that the problem is with the BIOS or the card.
> At this point I don't see many options left other than trying if the
> card works in another machine or with another OS, or maybe trying to
> re-flash the ROM image on the card if that's possible.

I agree, especially if the BIOS is not being changed to reflect the PCI socket 
is being used for video 
instead of the mobos AGP slot.
http://www.gigabyte.lv/products/mb/specs/ga-6bxe.html?&print_page=1

I'd suggest using a Debian Live CD while testing, 
especially with older and oddly mixed hardware.
http://cdimage.debian.org/cdimage/release/current-live/i386/iso-hybrid/
>



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

Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M

[Will Set]

  Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote:
> pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti:
>>  Hi Tomi,
>> 
>>  Tomi Leppänen wrote:
>> 
>>  > [    0.073485] PCI: Ignoring host bridge windows from ACPI; if 
> necessary, use "pci=use_crs" and report a bug
>> 
>>  I was hoping it would be that.  Does adding pci=use_crs to the kernel
>>  command line help?
>> 
>>  Thanks,
>>  Jonathan
> 
> Didn't make any difference. Here is dmesg now:

If you turn modesetting off you should be able to get the xserver running again.

see from your initial Xorg.0.log file
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176


 (II) Primary Device is: PCI 01@00:00:0
 (II) [KMS] drm report modesetting isn't supported.
 [...]
 (EE) RADEON(0): No valid linear framebuffer address
 [...]
 (EE) Screen(s) found, but none have a usable configuration.

 Fatal server error:
 no screens found

If you have a newer mobo to test with this video card it might be interesting 
to see
if it handles modeswitching with a newer than ( Intel 440BX ) chipset and a 
pentium 4 processor.

>>> There are no newer BIOS updates for that motherboard (Gigabyte GA-6BXE
>>> with Intel 440BX) and I've updated it once already. Although I could try
>>> Coreboot (I may do it just for fun), because it seems to support this
>>> motherboard and I've got a spare BIOS chip from another broken GA-6BXE.

thanks for testing with a mainline Linux version 3.0.0-1-486 kernel

> [    0.00] Initializing cgroup subsys cpuset
> [    0.00] Initializing cgroup subsys cpu
> [    0.00] Linux version 3.0.0-1-486 (Debian 3.0.0-3)
> (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 Sat Aug
> 27 15:56:48 UTC 2011
> [    0.00] BIOS-provided physical RAM map:
> [    0.00]  BIOS-e820:  - 0009fc00 (usable)
> [    0.00]  BIOS-e820: 0009fc00 - 000a
> (reserved)
> [    0.00]  BIOS-e820: 000f - 0010
> (reserved)
> [    0.00]  BIOS-e820: 0010 - 1fff (usable)
> [    0.00]  BIOS-e820: 1fff - 1fff3000 (ACPI
> NVS)
> [    0.00]  BIOS-e820: 1fff3000 - 2000 (ACPI
> data)
> [    0.00]  BIOS-e820:  - 0001
> (reserved)
> [    0.00] Notice: NX (Execute Disable) protection missing in CPU!
> [    0.00] DMI 2.1 present.
> [    0.00] DMI:    /i440BX-8671, BIOS 4.51 PG 02/06/01
> [    0.00] e820 update range:  - 0001
> (usable) ==> (reserved)
> [    0.00] e820 remove range: 000a - 0010
> (usable)
> [    0.00] last_pfn = 0x1fff0 max_arch_pfn = 0x10
> [    0.00] MTRR default type: uncachable
> [    0.00] MTRR fixed ranges enabled:
> [    0.00]   0-9 write-back
> [    0.00]   A-B uncachable
> [    0.00]   C-C7FFF write-protect
> [    0.00]   C8000-F7FFF uncachable
> [    0.00]   F8000-FBFFF write-through
> [    0.00]   FC000-F uncachable
> [    0.00] MTRR variable ranges enabled:
> [    0.00]   0 base 0 mask FE000 write-back
> [    0.00]   1 disabled
> [    0.00]   2 disabled
> [    0.00]   3 disabled
> [    0.00]   4 disabled
> [    0.00]   5 disabled
> [    0.00]   6 disabled
> [    0.00]   7 disabled
> [    0.00] PAT not supported by CPU.
> [    0.00] initial memory mapped : 0 - 0180
> [    0.00] Base memory trampoline at [c009c000] 9c000 size 12288
> [    0.00] init_memory_mapping: -1fff
> [    0.00]  00 - 40 page 4k
> [    0.00]  40 - 001fc0 page 2M
> [    0.00]  001fc0 - 001fff page 4k
> [    0.00] kernel direct mapping tables up to 1fff @
> 17fb000-180
> [    0.00] RAMDISK: 1777b000 - 18034000
> [    0.00] ACPI: RSDP 000f6ee0 00014 (v00 GBT   )
> [    0.00] ACPI: RSDT 1fff3000 00028 (v01 GBT    AWRDACPI 42302E31
> AWRD )
> [    0.00] ACPI: FACP 1fff3040 00074 (v01 GBT    AWRDACPI 42302E31
> AWRD )
> [    0.00] ACPI: DSDT 1fff30c0 02629 (v01 GBT    AWRDACPI 1000
> MSFT 010C)
> [    0.00] ACPI: FACS 1fff 00040
> [    0.00] 0MB HIGHMEM available.
> [    0.00] 511MB LOWMEM available.
> [    0.00]   mapped low ram: 0 - 1fff
> [    0.00]   low ram: 0 - 1fff
> [    0.00] Zone PFN ranges:
> [    0.00]   DMA      0x0010 -> 0x1000
> [    0.00]   Normal   0x1000 -> 0x0001fff0
> [    0.00]   HighMem  empty
> [    0.00] Movable zone start PFN for each node
> [    0.00] early_node_map[2] active PFN ranges
> [    0.00]     0: 0x0010 -> 0x009f
> [    0.00]     0: 0x0100 -> 0x0001fff0
> [    0.00] On node 0 totalpages: 130943
> [    0.00] free_area_init_node: node 0, pgdat c13b2ae8, node_mem_map
> dfbef200
> [    0.00

Bug#627019: Bug#632734: 627019:

[Will Set]

 Wednesday, August 31, 2011 1:22 PM  Will Set  wrote:

>

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627019

> I have  two i865 mobos D865GRH, D865PERLK that both have trouble booting 
> 2.6.39 
> and 3.0.0 kernels

> Yes
> Len Brown suggested workaround

https://bugzilla.redhat.com/show_bug.cgi?id=727865#c16

> processor.nocst=1
> is working for me so far too..
> 
> Will



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

Bug#627019: Bug#632734: 627019:

[Will Set]

  Tuesday, August 30, 2011 5:59 PM wzab  wrote:


> I found this bug, when I was looking for solution for my problem related to 
> the 
> newest kernels and a machine based on D865GBF motherboard.
I have  two i865 mobos D865GRH, D865PERLK that both have trouble booting 2.6.39 
and 3.0.0 kernels
> I was striked by the fact, that problem reported here occured in a machine 
> with 
> the same motherboard and the newest kernel.
> 
> My problem (machine not starting when HT is on) is reported as Debian bug 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631597 and was later 
> redirected 
> to https://bugzilla.kernel.org/show_bug.cgi?id=38262

Yes
Len Brown suggested workaround
processor.nocst=1
is working for me so far too..

Will
> 
> Maybe these two problems are correlated?
> (The same applies also to Debian bug 630031 )
> -- Regards,
> WZab




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

Bug#632734: Strange

[Will Set]

--- On Mon, 7/25/11, Frank McCormick  wrote:

> From: Frank McCormick 
> Subject: Bug#632734: Strange
> To: "Ben Hutchings" 
> Cc: 632...@bugs.debian.org
> Date: Monday, July 25, 2011, 1:09 PM
> On 22/07/11 02:04 PM, Frank McCormick
> wrote:
> > On 21/07/11 08:10 PM, Ben Hutchings wrote:
> >  > Please always cc the bug address when
> replying to bug-related mails.
> >  >
> >  > On Sat, 2011-07-16 at 09:54 -0400, Frank
> McCormick wrote:
> >  >> On 11/07/11 12:12 AM, Ben Hutchings
> wrote:
> >  >>> On Tue, 2011-07-05 at 17:29 -0400,
> Frank wrote:
> >   On 05/07/11 04:23 PM, Ben
> Hutchings wrote:
> >  > On Tue, Jul 05, 2011 at
> 02:48:26PM -0400, Frank M wrote:
> >  >> I find it strange that
> the PAE kernel is the ONLY one which
> > gives me
> >  >> any trouble.
> >  >> I guess it could be
> hardware related, but 2.6.38-1 and 2.6.38-2
> > have both been
> >  >> booting fine for
> months.
> >  >> Is there something
> about the PAE series that would uncover
> > hardware faults which
> >  >> may have existed for a
> long time ?
> >  >
> >  > Have you tried booting
> those earlier versions recently?
> >  >>
> >  
> >   Yes I've been booting them
> everyday for the past month or so - the
> >   PAE series is the first time in
> years, literally, that I have had
> >   problems like this.
> >  >>>

Frank, I reported very similar findings also. 
I also have been keeping track of 5 or 6 other bug reports that look similar, 
with a Pentium 4 3GHz 800 MHz bus / 512kb of L2 cache
see my bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627019

My Pentium D 3GHz 800 MHz bus / 1mb of L2 cache ( next generation) is not 
showing any of these issues ( yet).


> >  >
> >  > This sounds like there is some sort of
> hardware fault, but I can't see
> >  > why it would only occur when using PAE. It
> is just possible that the
> >  > circuitry for PAE is faulty, but I think
> that is only a very small part
> >  > of the chip.
> >  >
> >  > Please do consider the suggestions in.
> > 
> > Will do.
> > 
> > 
> 
>     Well I have solved this problem..but I'm not
> sure I like the solution. I installed the "new" 3.0.0 kernel
> this morning and started trying changing things in the BIOS
> setup. Nothing worked to allow me to boot UNTIL I turned off
> what Intel calls "hyper-threading". Now the kernel boots
> fine, but according to lshw-gtk, the system sees only one
> CPU. This is a dual-core system which was always seen by
> Linux as a dual core with in effect two CPU's.
> What's the connection between hyper-threading , and PAE
> which is apparently the only change in the new kernels ??
> 
Again, very similarly, I have been able to boot successfully using the 486 
flavor kernel ( but also not gettting SMP support for hyper threading.
I have had some success boot the 686-pae flavor by adding 
debug=3 or debug=4 to the linux commandline in grub-pc
I also have compiled a vanilla (upstreams default config) linux-image-3.0-rc7 
and it worked well for several days ( but still showing minor glitches at boot 
time)
But, after the udev upgrade to 172-1
the upstream kernel started showing the same seg faults  and other stuff  the 
debian 686-pae flavor kernels since 2.6.39-rc3-686-pae (iirc) have been showing.

I just upgraded to 3.0.0-1-686-pae and it took three reboots to get to a login 
screen.
The hang point on the second boot attempt was

waiting for dev to be fully populated ( which froze there, but I only waited a 
minute or two  before I shut down than rebooted.

Than the third time I still got a udevd seg fault, but it was not fatal this 
time and I'm able to login.

I didn't upgrade the grub packages yet, holding for next time.

> 
> 
> -- Cheers
> Frank




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

Bug#632772: [why not at least try first? ] Re: Bug#632772: Wheezy: KDE hangs on logout

[Will Set]

T Elcor   Mon, July 18, 2011 5:47:42 AM wrote
> --- On Fri, 7/8/11, T Elcor  wrote:
> 
> > >  Is the firmware-linux-nonfree package installed?
> > 
  > > No.
  > > 
  > > # aptitude search firmware-linux-nonfree
  > >  p   firmware-linux-nonfree   
  > >  
  > >- Binary firmware  for various drivers in
  > > the Linux ker
> 
> Can this issue be  resolved without installing the firmware-linux-nonfree 
package? I'm not too keen  on installing drivers from non-free. Thanks

Unless an issue is trust of debian non-free repo, why not try the 
firmware-nonfree package seeing if it solves your issue?
You always have the option to purge the package and remove non-free from your 
sources.list, if you so choose.

ps: The kernel team ( and other teams) worked tirelessly to create kernel 
packages free of fimware blobs. ( moving them to appropriate repo/package[s] )



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

Bug#628694: xorg-core: does not work with GNOME3

[Will Set]

Ana Guerrero  Sun, June 5, 2011
> Thanks for your quick reply.
> 
> On Tue, May 31, 2011 at 07:02:59PM  +0200, Michel Dänzer wrote:
> > On Die, 2011-05-31 at 18:53 +0200, Michel  Dänzer wrote: 
> > > On Die, 2011-05-31 at 14:36 +0200, Ana Guerrero  wrote: 
> > > > > 
> 
> > > > The mouse works just fine,  i do wonder if could be some desktop effect 
>from
> > > > gnome makes  the system very very slow?
> > > 
> > > It sounds like more likely  the GPU locks up. I suppose the 'working
> > > drivers from squeeze'  involve a different version of libgl1-mesa-dri,
> > > and possibly the  kernel?*
> 
> No, when I downgraded to Squeeze I only downgrade some xorg-*  packages
> (4-5 packages, I don't have the list here, but I can tell you if  needed), 
> everything else was kept to their versions in unstable. Of  course,
> it made the system non upgradeable, but it also made the system  usable.
I had a similar issue with gnome3  as you originally reported.
( xsession started but desktop didn't finish loading )
I noticed gnome-session or gnome-settings-daemon was seg faulting
and I read a bug report with a similar gnome3 session? settings-daemon? seg 
fault - two weeks ago?.
If I remember correctly after I purged gnome-session I found a few new 
gnome3-session packages
in unstable/experimental that installed  without issue, than the desktop loaded 
completely again.
> 
> > Does libgl1-mesa-dri 7.10.2-3 work better by any  chance?
> 
> No :(
> 
> > If not, does
> > 
> > Option  "EnablePageFlip" "off"
> > 
> > (verify in Xorg.0.log that it takes  effect) work around the problem?
> 
> Tried that with libgl1-mesa-dri 7.10.2-2  after a suggestion of jcristau, 
> and later with 7.10.2-3 and it did not  work.
> 
> 
> Ana




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

Bug#627837: linux-2.6: Aufs apparently silently dropped, breaking debian-live

[Will Set]

Daniel Baumann May 29, 2011 5:18:27 PM
> On 05/29/2011 10:34 PM, Julien Cristau wrote:
> > The maintainers have  already made that call, and I don't see a reason to
> > override their  decision.
> 
> so no change after squeeze, the release team gives a shit about  breaking
> debian-live, sigh. but don't worry, from now on, i will not care  anymore
> either.

It's not fun here either.
fwiw:
38 started getting less stable than what I'm used to seeing for at least a year 
now.
39 is much more volatile than any other kernel I've seen in unstable for more 
than a year.

I have no advice for either side of this.
> 
> bye, have fun.



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

Bug#627019: 627019 39 steadily improving on i865 chipset

[Will Set]

After upgrading to 2.6.39-1-686-pae  I have fewer boot attempts hanging.
Usually one or two before a successful boot.
It appears that if I downgrade udev one version (udev_169-1) 
I get better results (at least with today set of packages).

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627019

I've also noticed that the 2 i865 chipset machines are much more
sensitive to booting the 39 kernels than the i915 chipset machine.
The i915 machine was booting 39 consistently with 39-rc6 and beyond, 



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

Bug#616655: fluxbox: backgrounds are not changed when selecting new style from the menu

[Will Set]

Package: fluxbox
Version: 1.3.1~dfsg1-1
Severity: minor

last style used sets the fluxbox background at the begining of a new xsession
that inital background is not changed when a new style is selected from the 
fluxbox style menu.
a new background can still be set using fbsetbg on the commandline.
This sid install has 199 upgradable packages as you can see from the version 
list below.
I tested earlier on a fully updated sid install.
I grabbed fluxbox version 1.3.0 from snapshot.debian.org and I think that is 
the first
effected version.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.37-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages fluxbox depends on:
ii  libc6   2.11.2-11Embedded GNU C Library: Shared lib
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.4.2-2.1FreeType 2 font engine, shared lib
ii  libfribidi0 0.19.2-1 Free Implementation of the Unicode
ii  libgcc1 1:4.4.5-10   GCC support library
ii  libice6 2:1.0.7-1X11 Inter-Client Exchange library
ii  libimlib2   1.4.2-8+b2   powerful image loading and renderi
ii  libsm6  2:1.2.0-1X11 Session Management library
ii  libstdc++6  4.4.5-10 The GNU Standard C++ Library v3
ii  libx11-62:1.4.1-4X11 client-side library
ii  libxext62:1.2.0-2X11 miscellaneous extension librar
ii  libxft2 2.2.0-2  FreeType-based font drawing librar
ii  libxinerama12:1.1.1-1X11 Xinerama extension library
ii  libxpm4 1:3.5.9-1X11 pixmap library
ii  libxrandr2  2:1.3.1-1X11 RandR extension library
ii  libxrender1 1:0.9.6-1X Rendering Extension client libra
ii  menu2.1.44   generates programs menu for all me
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages fluxbox recommends:
ii  feh   1.11.2-1   imlib2 based image viewer
ii  xfonts-terminus   4.30-2 Fixed-width fonts for fast reading

Versions of packages fluxbox suggests:
pn  fbautostart(no description available)
pn  fbdesk (no description available)
pn  fbpager(no description available)

-- no debconf information



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

Bug#606985: hot keys still cold

[Will Set]

testing dwm 5.8.3-2 from sid 
I'm still seeing black screen drawn on root window with functional mouse cursor.
No status bar shows up and  I can't find any hot key combination to work except
Ctrl + Alt + Fx keys to bring me back to  VT 1 through 6
I tested with both suckless-tools and older dwm-tools installed
and currently testing with only dwm installed  ( suckless-tools is now 
recommend?)  :)
also tested with (new dwm recommend?) x11-xserver-utils installed..
also tested new with newer kernels 2.6.37-1-686 and 2.6.38-rc6-686

dwm 5.8.2-2 - still fully functional :)



  



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

Bug#546836: Bug confirmed: Matrox G550 unusable under squeeze

[Will Set]

- Original Message 
From: Etienne Vogt 
To: Cyril Brulebois 
Cc: ev...@free.fr; 546...@bugs.debian.org; Michel Dänzer 
Sent: Fri, January 28, 2011 5:31:06 PM
Subject: Bug#546836: Bug confirmed: Matrox G550 unusable under squeeze



On Fri, 28 Jan 2011, Cyril Brulebois wrote:

> Hmm, I can't reproduce this. Is there anything referencing
> /usr/X11R6/lib as a path which can hold libraries and which should be
> searched into? Maybe something like /etc/ld*?

Yes, in /etc/ld.so.conf :

/usr/X11R6/lib/Xaw3d
/usr/X11R6/lib
/usr/i486-linuxlibc1/lib

include /etc/ld.so.conf.d/*.conf

The first 3 lines refer to obsolete directories. I've just removed them.

-- Etienne Vogt.




-- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.deb.2.00.1101282327001.3...@coniglio.vogt-bodving.test






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

Bug#606985: 606985 update: dwm_5.8.2-3 now starts like dwm.web

[Will Set]

dwm_5.8.2-3 starts cleaner and behaves the same as dwm.web, showing the mouse 
cursor on the root window.
with dwm_5.8.2-3
and suckless-tools installed and dwm-tools not installed I still see the font 
errors showing up to the console whhen closing the xsession..
.

dwm_5.8.2-1 and dwm_5.8.2-2 both works fine 
with dwm_5.8.2-1 and dwm_5.8-2-2
with dwm-tools installed I don't see the font errors on the controlling console 
when closing the xsession..



  



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

Bug#606985: startx, dwm shows error messages on a non functional fullscreen xterm

[Will Set]

Package: dwm
Version: 5.8.2-3
Severity: minor

Dwm is showing a white background for xterm with 15 error messages
and the terminal is non responssive.
error messages 
dwm: missing fontset: ISO10646-1
dwm: missing fontset: JISX00201.1976-0
dwm: missing fontset: GB2312.1980-0
"  :   ": KSO5601.1987-0
   :: JISX0208.1983-0
   :: ISO8859-15
   :: ISO8859-14
   :: ISO8859-13
   :: ISO8859-9
   :: ISO8859-7
   :: KOI8-R
   :: ISO8859-5
   :: ISO8859-4
   :: ISO8859-3
dwm: missing fontset: ISO8859-2
Dwm dddoesn't show it's normal panel or menu and its hotkeys don't work at all 
either.
I am able to end teh xsession by using several different key combinations.
'Alt F4' 'Ctrl 4' 'Ctrl Alt F1 -> Crtl C'
If I downgrade dwm to version 8.5.2-1 I get most of dwm's functionality back.
But dwm starts with a non functional xterm on desktop1 and I'm unable to open 
another instance of xterm either by 'Alt Shift Enter' or using the menu.
I can use dwm menu to open other apps such as www-browser, graphics apps,
smplayer, etc

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.37-rc4-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dwm depends on:
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxinerama1  2:1.1.1-1  X11 Xinerama extension library

Versions of packages dwm recommends:
ii  suckless-tools38-1   simple commands for minimalistic w
ii  x11-xserver-utils 7.5+2  X server utilities

dwm suggests no packages.

-- no debconf information
--
-- xserver-xorg-core bug script

/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Jun 25 23:07 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1733512 Dec  2 00:16 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics 
Controller (rev 02)

/etc/X11/xorg.conf does not exist.

Kernel version (/proc/version):
Linux version 2.6.37-rc4-686 (Debian 2.6.37~rc4-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-6) ) #1 SMP Mon Dec 6 
15:57:14 UTC 2010

Xorg X server log files on system:
-rw-r--r-- 1 root root 19240 Dec 13 11:10 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-5-686 i686 Debian
Current Operating System: Linux sdb8 2.6.37-rc4-686 #1 SMP Mon Dec 6 15:57:14 
UTC 2010 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-rc4-686 root=/dev/sdb8
Build Date: 02 December 2010  01:08:37AM
xorg-server 2:1.7.7-10 (Julien Cristau ) 
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 13 11:10:10 2010
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor ""
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
(II) Loader magic: 0x81ec060
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(--) using VT number 7

(--) PCI:*(0:0:2:0) 8086:2572:8086:5248 Intel Corporation 82865G Integrated 
Graphics Controller rev 2, Mem @ 0xf000/134217728, 0xfeb8/524288, I/O @ 

Bug#593432: Black screen with kms and i915

[Will Set]

I have a i830 also..
If you turn off KMS  the old framebuffer driver works fine
obviously, this means 2.6.34 and beyond are unusable at this point in time on 
the i830
although I did get the blacklight on in the terminal using 2.6.35 with KMS on 

My Toshiba 1200-S212 "i830" only has 8 megs of video ram,
which I concluded was not enough to run the new drmframebuffer drivers...
Than intel introduced the virtual memory stuff, but AFAICT it's not active on 
the i830 yet

"from memory" (so forgive the incomplete description) 
both pipe A and pipe B are active 
when cloning the xorg.conf device and [screen or monitor] sections...
but I also haven't attached an external monitor to look at how it behaves...
"1there are only so many (24) hours in one day" [-) ...



- Original Message 
From: Julien Cristau 
To: san...@zedat.fu-berlin.de; 593...@bugs.debian.org
Sent: Wed, August 18, 2010 8:55:35 AM
Subject: Bug#593432: Black screen with kms and i915

retitle 593432 [i830] Black screen with kms and i915
kthxbye

On Wed, Aug 18, 2010 at 07:53:29 +0200, san...@zedat.fu-berlin.de wrote:

> When booting the screen goes black at the moment the frame buffer is
> switched on.
> Booting continues until the 'login prompt', but the screen remains black. 
> When
> switching to a text screen, the screen gets darker for a second, but no
> text login
> appears.  I can then, however, login blind and the machine works.  For
> example,
> I can reboot it when logging in as root and calling 'shutdown' (all blind,
> of course).
> 
> The problem goes away when adding the line
> 
> options i915 modeset=0
> 
> to the file /etc/modprobe.d/i915-kms.conf, so I guess it is a kms problem.
> 
> If I wasn't a newbie I'd mark this bug as 'important', because it left a
> freshly installed machine more or less completely unusable.
> 
Is this a regression from a previous revision?  Can you attach the dmesg
from a kms boot?

Cheers,
Julien



  



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

Bug#589547: xserver-xorg-video-nv: (EE) NV: Kernel modesetting driver in use, refusing to load: no xorg after kernel upgrade

[Will Set]

 install: 
xserver-xorg-video-nouveau

see if fixed..

- Original Message 

From: r.ductor 
To: Debian Bug Tracking System 
Sent: Sun, July 18, 2010 5:40:51 PM
Subject: Bug#589547: xserver-xorg-video-nv: (EE) NV: Kernel modesetting driver 
in use, refusing to load: no xorg after kernel upgrade

Package: xserver-xorg-video-nv
Version: 1:2.1.17-3
Severity: grave
Justification: renders package unusable

Hi after full-upgrading from 2.6.32-trunk-486 to 2.6.32-5-486 (and touching
nothing on the config)  the xserver is no more loaded due to a nv-driver/module
problem:

(EE) NV: Kernel modesetting driver in use, refusing to load
(EE) No devices detected.

Do not know what means  Kernel modesetting driver, in trunk all was fine. (I'm
writing my report from the trunk kernel). My card is a GeForce FX 5200. Here's
a log of the attempts.


  



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

Bug#587542: x11-xserver-utils: please split out xhost

[Will Set]

--- On Tue, 6/29/10, Josselin Mouette  wrote:

> From: Josselin Mouette 
> Subject: Bug#587542: x11-xserver-utils: please split out xhost
> To: sub...@bugs.debian.org
> Date: Tuesday, June 29, 2010, 12:40 PM
> Package: x11-xserver-utils
> Version: 7.5+1
> Severity: wishlist
> 
> Hi,
> 
> the xhost tool is something very dangerous and users have a
> strong
> tendency to abuse it by following stupid documentations
> that ask them to
> do “xhost +”.

Is the warning given in the package description insufficient?

http://packages.debian.org/squeeze/x11-xserver-utils

> 
> Please split it out in a separate package so that it can be
> uninstalled
> and avoid a lot of security problems.
> 
> Thanks,
> -- 
>  .''`.
> : :' :      “Fuck you sir, don’t be
> suprised when you die if
> `. `'       you burn in Hell,
> because I am a solid Christian
>   `-        and I am praying for
> you.”   --  Mike
> 







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

Bug#586006: initramfs-tools: noisy resume

[Will Set]

it looks a bit different from a cold boot

[   21.469292] PM: Starting manual resume from disk
[   21.469727] PM: Resume from partition 9:2
[   21.469730] PM: Checking hibernation image.
[   21.796903] PM: Error -22 checking image file
[   21.796908] PM: Resume from disk failed.

 2.6.35  controlling hibernation?
 

--- On Tue, 6/15/10, maximilian attems  wrote:

> From: maximilian attems 
> Subject: Bug#586006: initramfs-tools: noisy resume
> To: "Colin Watson" , 586...@bugs.debian.org
> Date: Tuesday, June 15, 2010, 12:21 PM
> reassign 586006 klibc
> thanks
> 
> On Tue, Jun 15, 2010 at 05:21:27PM +0100, Colin Watson
> wrote:
> > 
> > We had a bug report (https://bugs.launchpad.net/bugs/432585) a while
> > back about kinit saying things like "No resume image,
> doing normal
> > boot..." on startup.  Scott James Remnant 
> corrected
> > this by just throwing away stdout and stderr from
> /bin/resume, with this
> > changelog message:
> > 
> >   * Silence output when trying to
> resume, since the only output is bitching
> >     that we can't resume because
> we didn't hibernate in the first place.
> >     LP: #432585.
> > 
> > Here's his patch, rebased on current git:
> > 
> > diff --git a/scripts/local-premount/resume
> b/scripts/local-premount/resume
> > index 11acfc7..1cfc479 100755
> > --- a/scripts/local-premount/resume
> > +++ b/scripts/local-premount/resume
> > @@ -57,7 +57,7 @@ esac
> >  
> >  # hardcode path, uswsusp ships an resume binary
> too
> >  if [ -n "${resume_offset}" ]; then
> > -    /bin/resume ${resume}
> ${resume_offset}
> > +    /bin/resume ${resume}
> ${resume_offset} >/dev/null 2>&1
> >  else
> > -    /bin/resume ${resume}
> > +    /bin/resume ${resume}
> >/dev/null 2>&1
> >  fi
> > 
> > Thanks,
> 
> this should be reassigned to klibc and is fixed in my
> latest
> patch queue to hpa with
>  [klibc] resume: silence warning on resume try
> 
> will hack next weekend on that queue to finalize it's
> submission.
> 
> thank you.
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20100615162134.gn9...@baikonur.stro.at
> 
>







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

Bug#585556: full dmesg output from boot

[Will Set]

shutdown machine
remove the DVD-RW devices data plug and power plug
restart the machine 
reply with new dmesg 


[1.324944] handlers:
[1.324977] [] (piix_interrupt+0x0/0x192 [ata_piix])
[1.325076] Disabling IRQ #5
[1.347126] ata1.00: ATAPI: DVD-RW IDE1108, VER B018, max UDMA/66
[1.347150] ata1.00: limited to UDMA/33 due to 40-wire cable
[1.352539] ata3.01: ATA-7: SAMSUNG HD161HJ, JF100-19, max UDMA7
[1.352542] ata3.01: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
[1.352677] ata4.00: ATA-8: ST3500412AS, CC32, max UDMA/133
[1.352680] ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[1.360583] ata3.01: configured for UDMA/133
[1.360627] ata1.00: configured for UDMA/33
[1.368445] ata4.00: configured for UDMA/133
[1.924066] scsi 0:0:0:0: CD-ROMDVDRWIDE1108  B018 
PQ: 0 ANSI: 5
[1.924414] scsi 2:0:1:0: Direct-Access ATA  SAMSUNG HD161HJ  JF10 
PQ: 0 ANSI: 5
[1.924630] scsi 3:0:0:0: Direct-Access ATA  ST3500412AS  CC32 
PQ: 0 ANSI: 5
[1.940555] sd 2:0:1:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 
GiB)
[1.940604] sd 2:0:1:0: [sda] Write Protect is off
[1.940607] sd 2:0:1:0: [sda] Mode Sense: 00 3a 00 00
[1.940627] sd 2:0:1:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[1.940759]  sda:
[1.940940] sd 3:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 
GiB)
[1.940986] sd 3:0:0:0: [sdb] Write Protect is off
[1.940988] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[1.941009] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[1.941121]  sdb: sda1 sda2 sda3 < sda5 sda6 sdb1 sdb2 < sda7 sdb5 sdb6 >
[1.989456] sd 3:0:0:0: [sdb] Attached SCSI disk
[1.992236]  sda8 sda9 >
[2.017576] sd 2:0:1:0: [sda] Attached SCSI disk
[   32.816059] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   32.816109] sr 0:0:0:0: CDB: Mode Sense(10): 5a 00 2a 00 00 00 00 00 80 00
[   32.816127] ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 
in
[   32.816130]  res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 
(timeout)
[   32.816217] ata1.00: status: { DRDY }
[   37.856021] ata1: link is slow to respond, please be patient (ready=0)
[   42.840023] ata1: device not ready (errno=-16), forcing hardreset
[   42.840032] ata1: soft resetting link
[   43.012216] ata1.00: configured for UDMA/33
[   43.324053] ata1: EH complete
[   73.816050] ata1.00: limiting speed to UDMA/25:PIO4
[   73.816056] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   73.816101] sr 0:0:0:0: CDB: Mode Sense(10): 5a 00 2a 00 00 00 00 00 80 00
[   73.816118] ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 
in
[   73.816120]  res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 
(timeout)
[   73.816207] ata1.00: status: { DRDY }
[   78.856026] ata1: link is slow to respond, please be patient (ready=0)
[   83.840022] ata1: device not ready (errno=-16), forcing hardreset
[   83.840031] ata1: soft resetting link
[   84.020215] ata1.00: configured for UDMA/25
[   84.324054] ata1: EH complete
[  114.816047] ata1.00: limiting speed to PIO4
[  114.816052] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  114.816098] sr 0:0:0:0: CDB: Mode Sense(10): 5a 00 2a 00 00 00 00 00 80 00
[  114.816114] ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 
in
[  114.816116]  res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 
(timeout)
[  114.816204] ata1.00: status: { DRDY }
[  119.856027] ata1: link is slow to respond, please be patient (ready=0)
[  124.840023] ata1: device not ready (errno=-16), forcing hardreset
[  124.840032] ata1: soft resetting link
[  125.012216] ata1.00: configured for PIO4
[  125.324053] ata1: EH complete
[  125.524047] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[  125.524052] Uniform CD-ROM driver Revision: 3.20
[  125.524198] sr 0:0:0:0: Attached scsi CD-ROM sr0
[  125.530066] sr 0:0:0:0: Attached scsi generic sg0 type 5
[  125.530386] sd 2:0:1:0: Attached scsi generic sg1 type 0
[  125.530699] sd 3:0:0:0: Attached scsi generic sg2 type 0
 

--- On Fri, 6/11/10, jeanseb  wrote:

> From: jeanseb 
> Subject: Bug#585556: full dmesg output from boot
> To: 585...@bugs.debian.org
> Date: Friday, June 11, 2010, 4:27 PM
> Hi
> here full dmesg log early after boot.


  



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

Bug#583390: linux-image-2.6.32-5-686: Hangs with "ata frozen" on boot

[Will Set]

[sorry for the noise]
I haven't filed my own bugreport because it's not a big issue for me, ATM.
I'd rather wait the extra minute or so during boot, than change my disk maps 
and menus...

I have a very similar dmesg ata1: lost interrupt (Status 0x58) - and the 
kernel times out for about (30 seconds on each PATA Channel) 
while waiting for dma [on the slave of both PATA channels]... 
Both primary and secondary channel masters are hard disks and both primary and 
seconardy slaves are DVD burners...
The primary PATA channel slave is initialized at 33mbs
and the secondary channel slave is initialzed at 25mbs on the bus..

I saw this behavior "once" before while testing the last pre-release of the d-i 
just before Lenny was released. I worked around the issue at that time by 
fiddling with (ATA/IDE Configuration - enhanced/legacy SATA/PATA) and onboard  
(SATA RAID) BIOS settings...

Before sending this I
Unplugged both DVD burners, rebooted
Double checked disk jumpers, rebooted.
Disabled BIOS setting "PCI ATA Bus Master" rebooted
Installed 2.6.34-1-686, rebooted
Disabled "ATA/IDE Configuration" BIOS setting, rebooted

Changing BIOS setting:  
Drive Configuration -> 
ATA/IDE Configuration (Legacy) ->
Legacy IDE Channels (SATA PO/P1 only)

gets rid of the kernel timeout
but no longer initializes any of the PATA Channels

Intel D865PERLK mobo - 2 SATA channels - first generation
All disk channels populated.


--- On Thu, 5/27/10, Adrian Lang  wrote:

> From: Adrian Lang 
> Subject: Bug#583390: linux-image-2.6.32-5-686: Hangs with "ata frozen" on boot
> To: "Debian Bug Tracking System" 
> Date: Thursday, May 27, 2010, 10:44 AM
> Package: linux-2.6
> Version: 2.6.32-13
> Severity: important
> Tags: sid
> 
> After "Loading, please wait...", linux hangs for 30
> seconds. after that, it logs:
> 
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen
> ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma
> 16512 in
>          res
> 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }
> 
> These messages are repeated after 40 seconds, and again 40
> seconds.
> 
> linux-image-2.6.32-3-686 works, linux-image-2.6.33-2-686
> and linux-image-2.6.34-1-686 show the same behaviour.
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached
> 
> ** Model information
> not available
> 
> ** PCI devices:
> 00:00.0 Host bridge [0600]: Intel Corporation
> 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev
> 10)
>     Subsystem: ASUSTeK Computer Inc.
> P5KPL-VM Motherboard [1043:82b0]
>     Control: I/O- Mem+ BusMaster+ SpecCycle-
> MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> DisINTx-
>     Status: Cap+ 66MHz- UDF- FastB2B+
> ParErr- DEVSEL=fast >TAbort-  >SERR-      Latency: 0
>     Capabilities: 
> 
> 00:01.0 PCI bridge [0604]: Intel Corporation
> 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1]
> (rev 10) (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-      Latency: 0, Cache Line Size: 32 bytes
>     Bus: primary=00, secondary=01,
> subordinate=01, sec-latency=0
>     Memory behind bridge: fc00-fe9f
>     Prefetchable memory behind bridge:
> e000-efff
>     Secondary status: 66MHz- FastB2B-
> ParErr- DEVSEL=fast >TAbort-       BridgeCtl: Parity- SERR+ NoISA- VGA+
> MAbort- >Reset- FastB2B-
>         PriDiscTmr-
> SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
>     Capabilities: 
>     Kernel driver in use: pcieport
> 
> 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7
> Family High Definition Audio Controller [8086:27d8] (rev
> 01)
>     Subsystem: ASUSTeK Computer Inc.
> P5KPL-VM Motherboard [1043:8290]
>     Control: I/O- Mem+ BusMaster+ SpecCycle-
> MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> DisINTx-
>     Status: Cap+ 66MHz- UDF- FastB2B-
> ParErr- DEVSEL=fast >TAbort-  >SERR-      Latency: 0, Cache Line Size: 32 bytes
>     Interrupt: pin A routed to IRQ 16
>     Region 0: Memory at fbffc000 (64-bit,
> non-prefetchable) [size=16K]
>     Capabilities: 
>     Kernel driver in use: HDA Intel
> 
> 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7
> Family PCI Express Port 1 [8086:27d0] (rev 01) (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-      Latency: 0, Cache Line Size: 32 bytes
>     Bus: primary=00, secondary=03,
> subordinate=03, sec-latency=0
>     I/O behind bridge: 1000-1fff
>     Memory behind bridge: 8000-801f
>     Prefetchable memory behind bridge:
> 8020-803f
>     Secondary status: 66MHz- FastB2B-
> ParErr- DEVSEL=fast >TAbort-       BridgeCtl: Parity- SERR+ NoISA- VGA-
>

Bug#577534: base: fails too with -11 kernel

[Will Set]

 #wodim --devices might show the correct /dev that is on the #lshw list

--- On Thu, 4/22/10, Javier Barroso  wrote:

> From: Javier Barroso 
 
> # lshw  # cdrom output
>            *-cdrom
>                
> description: DVD writer
>                
> product: DVD+-RW GSA-H53L
>                
> vendor: HL-DT-ST
>                
> physical id: 0.0.0
>                 bus
> info: s...@0:0.0.0
>                
> logical name: /dev/cdrom
>                
> logical name: /dev/cdrom1
>                
> logical name: /dev/cdrw
>                
> logical name: /dev/cdrw1
>                
> logical name: /dev/dvd
>                
> logical name: /dev/dvd1
>                
> logical name: /dev/dvdrw
>                
> logical name: /dev/dvdrw1
>                
> logical name: /dev/scd0
>                
> logical name: /dev/sr0
>                







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

Bug#551387: stable vs testing xorg

[Will Set]

--- On Mon, 4/12/10, M  wrote:

> From: M 
> Subject: Bug#551387: stable vs testing xorg
> To: "Julien Cristau" 
> Cc: "martin" , 551...@bugs.debian.org
> Date: Monday, April 12, 2010, 2:37 PM
> Julien Cristau wrote:
> 
> > apt-get install xserver-xorg-video-intel -t
> experimental
> > should work.


It installed nicely for me using 


> 
> no such luck:
> 
> The following packages have unmet dependencies.
>   xserver-xorg-video-intel: Depends: libx11-xcb1 but
> it is not installable

http://packages.debian.org/sid/libx11-xcb1

>                
>             Depends:
> libxcb-dri2-0 (>= 0) but it is not
> installable


http://packages.debian.org/sid/libxcb-dri2-0  


> 
> Thanks,
> M








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

Bug#472108: Found a solution

[Will Set]

Anthony,
I'm glad you were able to find a solution that meets your present 
needs...
The state of xserver at the moment in sid is a very fast moving target.
To my best understanding , what is happening is that all the video 
configuration is being moved to the kernel kms is just the first step in 
removing all the video and than input configs from the xserver...

The behavior of the (xserver video drivers especially) since the beginning of 
this year is changing continually ( weekly for the most part, but daily at 
times as well) and documentation of this is mostly confined to the debian 
package and upstream changlogs for the time being 

vvill

ps: whenever you upgrade your kernel you may want to test re-enabling kms, as 
it works well for the most part with kernels 2.6.32-4 and beyond..

> 
> Perhaps this information should also be included in the
> documentation
> for xserver-xorg-video-ati?
> 
> Anthony




  



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

Bug#548849: xserver-xorg_1%3a7.4+4_i386.deb - Caught signal 11. Server aborting

[Will Set]

Package: xserver-xorg
Version: 1:7.4+3
Severity: minor

After upgrading Sept 28 2009 X aborted. My first thought was to upgrade from 
2.6.30-2-686 to 2.6.31 to match to the build machine.
Instead I downgraded back to -xserver-xorg_1%3a7.4+3_i386.deb - 
xserver-xorg-core_2%3a1.6.3.901-1_i386.deb 
 xserver-xorg-input-evdev_1%3a2.2.4-1_i386.deb - and 
xserver-xorg-video-intel_2%3a2.8.1-1_i386.deb

reportbug also failed after upgrading to xserver-xorg_1%3a7.4+4_i386.deb  and I 
was not able to reconfigure reportbug to text mode

in debconf information:  below
* xserver-xorg/config/device/identifier: nVidia Corporation NV44A [GeForce 6200]
was removed and onboard intel 865 video is being used presently.




-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Sep 29 00:43 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1690904 Sep 14 17:29 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics 
Controller (rev 02)

/etc/X11/xorg.conf does not exist.

Xorg X server log files on system:
-rw-r--r-- 1 root root 26983 Sep 29 00:43 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30.6-dsa-ia32 i686 Debian
Current Operating System: Linux debiandunes 2.6.30-2-686 #1 SMP Sat Sep 26 
01:16:22 UTC 2009 i686
Build Date: 14 September 2009  05:23:17PM
xorg-server 2:1.6.3.901-1 (bui...@murphy.debian.org) 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 29 00:43:51 2009
(II) Loader magic: 0xa40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7

(--) PCI:*(0:0:2:0) 8086:2572:8086:5248 Intel Corporation 82865G Integrated 
Graphics Controller rev 2, Mem @ 0xf000/134217728, 0xfeb8/524288, I/O @ 
0xec00/8
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier  "Builtin Default intel Device 0"
Driver  "intel"
EndSection
Section "Screen"
Identifier  "Builtin Default intel Screen 0"
Device  "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default i810 Device 0"
Driver  "i810"
EndSection
Section "Screen"
Identifier  "Builtin Default i810 Screen 0"
Device  "Builtin Default i810 Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default vesa Device 0"
Driver  "vesa"
EndSection
Section "Screen"
Identifier  "Builtin Default vesa Screen 0"
Device  "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default fbdev Device 0"
Driver  "fbdev"
EndSection
Section "Screen"
Identifier  "Builtin Default fbdev Screen 0"
Device  "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier  "Builtin Default Layout"
Screen  "Builtin Default intel Screen 0"
Screen  "Builtin Default i810 Screen 0"
Screen  "Builtin Default vesa Screen 0"
Screen  "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default i810 Screen 0" (1)
(**) |   |-->Monitor ""
(**) |   |-->Devic