According to
http://dri.freedesktop.org/wiki/ATI?highlight=%28CategoryHardware%29
The Radeon seems to have problems with certain early VIA chipsets. Your best
bet is to try and see if it works.
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of
According to
http://dri.freedesktop.org/wiki/ATI?highlight=%28CategoryHardware%29
The Radeon seems to have problems with certain early VIA chipsets. Your best
bet is to try and see if it works.
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of
Package: linux-2.6
Version: 2.6.22-4
Severity: normal
Default operation of xserver fails because DRI locks system (disabling
DRI works). This is probably because the video card in question (a Radeon
8500 LE / Radeon R200 QL) is not detected by the kernel drm module.
This card worked on
On Monday 19 November 2007 04:58, Frans Pop wrote:
On Sunday 18 November 2007, Daniel Dickinson wrote:
Comments/Problems:
Install fails with error on chroot to target (with mount -t proc as the
command) because mount is not on /target (I checked).
I can reproduce this issue
Package: installation-reports
Boot method: Netinst CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/20071118-1/i386/iso-cd/
Date: 3:00 PM EST [-0500 UTC] Sunday, November 18, 2007
Machine: Soyo SY-K7VTA-B with Dell Perc 3/DCL (LSI MegaRaid)
Processor: Athlon 1000
Memory:
Package: reportbug
Version: 3.31
Severity: important
On a minimal install (i.e. no Standard tasksel, nor any others) apt-get
install reportbug is insufficient to get a working reportbug; gettext
must also be installed (as per reportbug's error messages)
-- Package-specific info:
** Environment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
maximilian attems wrote:
On Mon, 28 Aug 2006, Daniel Dickinson wrote:
On a system that works with 2.6.16-2-k7_2.6.16-18 upgrading to
2.6.17-2-k7_2.6.17-7 results in a system for which the mouse (a
Logitech TrackMan) is flaky (jumps around
Package: hwinfo
Version: 13.0-6
Followup-For: Bug #381387
start debug info
libhd version 13.0 (ia32)
using /var/lib/hardware
kernel version is 2.6
- /proc/cmdline -
root=/dev/md1 ro
- /proc/cmdline end -
debug = 0xff77
probe =
Package: www.debian.org
Severity: normal
The link http://wiki.debian.org/copyright.html (which is supposed to
point to the copyright notice) linked from
http://wiki.debian.org/About does not exist. Also, as with
www.debian.org a link to the license should be at the bottom of, at
least, the
Package: linux-image-2.6.17-2-k7
Version: 2.6.17-7
Severity: important
On a system that works with 2.6.16-2-k7_2.6.16-18 upgrading to
2.6.17-2-k7_2.6.17-7 results in a system for which the mouse (a
Logitech TrackMan) is flaky (jumps around on the screen) and which
feels sluggish (perhaps just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 21 Aug 2006 06:33:36 -0700
[EMAIL PROTECTED] (Debian Bug Tracking System) wrote:
This is an automatic notification regarding your Bug report
#383740: quik-installer incorrectly allows separate root and /boot,
which was filed against the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 21 Aug 2006 10:15:19 +0200
[EMAIL PROTECTED] wrote:
On Fri, Aug 18, 2006 at 11:13:06PM -0400, Daniel Dickinson wrote:
Package: quik
Severity: normal
Due to the manpage stating that separate root and /boot are
possible a bug
Package: quik
Severity: normal
Due to the manpage stating that separate root and /boot are possible a
bug report stating that quik-installer's insistence on root and /boot
being the same was incorrect. This bug was fixed, however testing an
installation with separate root and /boot reveals that
Package: quik-installer
Severity: normal
Due to a bug in the quik manpage stating that root and /boot can be on
different partitions quik-installer was 'fixed' to allow installation
of quik when /boot and root were not the same partition (but on the
same disk). This is incorrect as testing
the default ui would have to changed to
commandline using pv instead of dialog, if dialog and zenity were to
be suggests or recommends).
#!/bin/bash
# fburn 1.2 is used to write raw data (usually a floppy image) to a
# floppy.
# Copyright (C) 2006 Daniel Dickinson [EMAIL PROTECTED]
# This program
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mdadm version is 1.9.0-4sarge1
Output of mdadm --examine --scan is,
ARRAY /dev/md0 level=raid1 num-devices=3
UUID=183e8bbf:4b7a95cd:f5b4be0c:3fe0c682
devices=/dev/hdc1,/dev/hdb1,/dev/hda1 ARRAY /dev/md1 level=raid5
num-devices=3
Package: initramfs-tools
Version: 0.73c
Severity: important
Upgrading initramfs (when package in testing changed) resulted in
non-booting system. I managed to fix things by adding a script to
init-premount that activates (mdam -assemble's) the raid5 device
(/dev/md1) that contains my root
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have append=console=tty0 console=ttyS0,115200 in my quik.conf and
booting bombs out with:
pmac_zilog: 0.6 (Benjamin Herrenschmidt [EMAIL PROTECTED])
pmac_zilog: Error registering serial device, disabling pmac_zilog.
pmac_zilog: Did another serial
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following are the same for kernel 2.6.16-2-powerpc 2.6.16-16 and
2.6.17-1-powerpc 2.6.17-3 - I tried to get around #364637 (pmac_zilog
serial conflict when using a serial console) but was unsuccessful, so
the following is hand-copied:
TCP: Hash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please ignore the last message; It
a) should have gone to control, and
b) It is unconfirmed (the success may have been with 2.6.15).
Must be less quick with bts...
- --
And that's my crabbing done for the day. Got it out of the way early,
now I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity important
thanks
This, apparently, does not affect all systems, therefore, while it
limits my ability to test etch (after reboot), it is not
severity grave.
- --
And that's my crabbing done for the day. Got it out of the way early,
now I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought it was fixed because after a reinstall using stable, then
adding 2.6.15, 2.6.15 failed to boot, but upgrading initramfs-tools
fixed things. I mistakenly concluded that was the same bug as was
affecting 2.6.16, which is not the case.
- --
Package: debian-installer
Severity: important
Tags: powerpc debian-installer
For Old World PowerPC Macintosh BootX hangs at the 'MMU:exit' line of
the kernel boot for both hd-media and cdrom kernel and initrd images,
but the miBoot floppy works. All methods use a variant of
2.6.16-2-powerpc,
~/.weexrc
[default]
FollowSymlinks = true
IgnoreLocalDir = ./RCS
LogDetailLevel = 3
[bmts-quickie]
DestDir = /public_html
HostName = ftp.bmts.com
LoginName = joe
RenameOK = true
SrcDir = /home/dfd/WebWIP/joe
---
The command 'weex bmts-quickie' prints 'Segmentation
Package: weex
Version: 2.6.1-6sarge1
Severity: important
If you have a line like
IgnoreLocalDir = ./RCS
weex borks with a segfault.
Commenting out the line is a workaround, but makes this option unuseable
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (50,
Package: debian-installer
Severity: important
Using the 2006-06-24 vmlinux, initrd.gz, and mini.iso booted the BootX
kernel screen flashes for a moment and then the screen becomes
garbled (I think part of the kernel bootstap process is working, but
not enough to even get the loading of
On Fri, Jun 23, 2006 at 11:42:59AM +0200, [EMAIL PROTECTED] wrote:
quik uses the input-device and output-device of openfirmware as the
console. Unfortunately many old world macs default to a serial console
for openfirmware thus the user never sees the quik boot screen, and
can't select
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have confirmed that this is required to successfully boot oldworld
mac after the install completes and am ready to make use of the
updated kernel, so if you could add the /proc/device-tree (openfirmware
device tree) to the miboot kernel it would be
Package: quik-installer
Version: 0.0.10
Severity: normal
quik-installer complains that quik requires that /boot and root be on
the same partition. This is incorrect. quik only requires that boot
and root be on the same disk.
--
And that's my crabbing done for the day. Got it out of the way
Package: debian-installer
Severity: normal
On Macs floppy drives don't come with a manual eject button; you are
expected to eject floppies through software. This is a problem for
floppy installs of debian because the boot floppy is not ejected to
permit the insertion of the root floppy, nor is
Package: linux-image-2.6.16-2-powerpc
Version: 2.6.16-14
Severity: important
quik writes to whatever input-device and output-device are
configured in open firmware. Unfortunately for many old world macs
(including mine), this defaults to the ttya (/dev/ttyS0) which means
all the user sees is a
Package: quik
Version: 2.1-8
Severity: important
quik uses the input-device and output-device of openfirmware as the
console. Unfortunately many old world macs default to a serial console
for openfirmware thus the user never sees the quik boot screen, and
can't select what image to boot (or
Package: linux-image-2.6-powerpc-miboot
Severity: important
In order to fix the bug which prevents quik-installer in
debian-installer from working, I need /proc/device-tree. The module
for this was removed from the miBoot floppies, but is on the other
types of install (cd, hd-media, etc).
With
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 28 May 2006 20:39:02 -0400
Joey Hess [EMAIL PROTECTED] wrote:
So, the weird thing here is that nothing on the powerpc or boot floppy
side of things is exactly currently in a state of flux. As far as I
can see, the code is exactly the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erm, I decided to do a RFC on debian-boot first; my proposed fix could
result in a unbootable system, if it fails. That situation would
require opening the case to correct, so I've decided to ask if a big
scary warning before performing the operation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 28 May 2006 22:07:01 -0400
Joey Hess [EMAIL PROTECTED] wrote:
--447a5b42_7346d134_4354
Daniel Dickinson wrote:
Well, I just loop mounted the 27th's floppy image and copied it's
contents to a temporary directory for comparison
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 28 May 2006 23:44:01 -0400
Joey Hess [EMAIL PROTECTED] wrote:
--447a6fa2_40410769_4354
Daniel Dickinson wrote:
Okay, there is something very strange going on here. I just checked
the 13th, and it's image is now empty as well
Package: debian-installer
Severity: important
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (50, 'testing'), (7, 'unstable'), (3, 'experimental')
Architecture: powerpc
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
On a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It appears that the bug appears when a database-level constraint is
violated (e.g. an unique index constraint is violated by adding a
record with index fields that are the same as an existing record), and
macros are active on save. E.g. the Before
Package: openoffice.org-base
Version: 2.0.1-5
Severity: important
OpenOffice.org Base crashes in a database form (NewItemForm in database to be
attached) on trying to save a record. It
looks like there is a dialogue box trying to come up, but it never appears, and
OOo is complete frozen and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I disabled macros and discovered that the error message that was trying
to come was a notification that a required field had no value. Fixing
the required field (made the database automatically insert a default
value) worked. After that enable the
Package: initramfs-tools
Version: 0.60
Followup-For: Bug #362816
As the previous reporter reported, linux-image-2.6.15 and
initramfs-tools 0.60 results in a non-booting system on some hardware.
In my case I need the ide-generic module, which wasn't being loaded.
I switched to yaird and my
Package: linux-image-2.6.15-1-486
Version: 2.6.15-8
Severity: normal
Using the mousedev module doesn't work with sermouse, for my mouse (the
mouse is not detected, as evidenced by udev not create a new
/dev/input/mouse0 when modprobe sermouse is performed, and X loading,
but with a frozen
Package: fop
Version: 1:0.20.5-5
Severity: wishlist
fop works fine with gij 4.1.0-1 and classpath 0.12-1, it doesn't actually need
the non-free java2-runtime. I faked out path into
thinking I had a 'real' java2-runtime by using equivs to create a dummy package
that Provides: java2-runtime.
Package: gnucash
Version: 1.9.3-1
Severity: normal
Before I updated g-wrap to 1.9.5-2 and installed guile-g-wrap, gnucash
1.9.3-1 was unabled to start, giving an error message that a gtk module
was missing (g-wrap gw standard).
-- System Information:
Debian Release: 3.1
APT prefers testing
Package: gnucash
Version: 1.9.3-1
Severity: important
Tags: experimental
When editing a transaction in a register set to view|auto-split entry of
the first line (date, payee) works fine, but tabbing from the
description field to the transfer field hangs gnucash, which must be
killed to exit.
Package: portmap
Version: 5-9
Severity: grave
Tags: security
Justification: user security hole
The following hosts.deny
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've logged into x during the NOLOGIN period (by removing the check I
had in Xesssion.d/...) and have found that I get messages that logins
are not allowed, but I am not logged out of my x session. My window
manager is WindowMaker, I don't use GNOME
Package: timeoutd
Version: 1.5-10
Severity: important
timeoutd isn't working for me. It doesn't do the main thing I want, which is
to kill user (including root sessions) during the nologon period. I have
implented this for X by adding an Xsession.d check of timeoutd, but would
prefer to
Package: openoffice.org-writer
Version: 2.0.2-2
Severity: normal
1) Create blank text document
2) Use Format|Page and change Format to Env. #10
3) Change to Landscape (else you have a tall narrow envelope instead of
a short wide envelope that is typically used)
4) Enter some text
5) Attempt to
Package: pdns
Version: 2.9.17-13sarge1
Severity: serious
Justification: Policy 6.5.4
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-mornir-smp-1.4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages pdns depends on:
ii
Package: cloop-src
Version: 2.01.5-4
Severity: normal
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-mornir-smp-1.4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages cloop-src depends on:
ii module-assistant 0.9
Package: partimage-server
Version: 0.6.4-11
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages
Package: partimage
Version: 0.6.4-11
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages partimage depends on:
Package: e2fsprogs
Version: 1.37-2sarge1
Severity: normal
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages e2fsprogs depends on:
ii e2fslibs
Package: cpqarrayd
Version: 2.0-3
Severity: normal
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages cpqarrayd depends on:
ii libc6
Package: netatalk
Version: 2.0.2-3
Severity: normal
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages netatalk depends on:
ii libc6
This appears to have been due to upgrading smbldap-tools but not the
rest of the ldap stuff at the same time. In any event it works now that
I have upgraded everything (though my database got wiped during the
first attempted upgrade and I had to start over).
--
To UNSUBSCRIBE, email to
Package: smbldap-tools
Version: 0.8.7-4
Severity: grave
Justification: renders package unusable
Since updating smbldap-tools I have been unable to add more than one user to
newly created groups user smbldap-modify. Adding to existing groups succeeds
as does adding to the group by using
Package: debian-installer
Severity: critical
Justification: breaks system unless you can boot another way and apply
workaround
This is also a kernel bug, but I don't know how to send the report to
both debian-installer (which needs to work around the problem or get
questions on why an affected
Package: kernel-image-2.6.8-1-386
Version: 2.6.8-10
Severity: critical
File: kernel-image-2.6.8
Justification: breaks unrelated software
The USB controller on my board doesn't work with 2.6.8 but does with
2.6.10. I've called this critical but you may only consider it grave
sicne not too many
901 - 961 of 961 matches
Mail list logo
