Bug#649217: Bug#638979: grub-mount, os-prober and symlinks traversal failures
On Sun, Nov 18, 2012 at 10:18:13AM +, Colin Watson wrote:
> On Fri, Nov 16, 2012 at 08:04:19PM +0100, Václav Ovsík wrote:
> > affects 638979 +os-prober
> > thanks
> >
> > There is already a patch?
> > http://lists.gnu.org/archive/html/grub-devel/2012-10/msg00021.html
>
> No, that fixes a regression in 2.00 which caused any
> symlink-to-directory encountered in a directory's contents to cause the
> directory to appear as though it were empty. That bug was not present
> in 1.99, where this bug was originally reported in Debian, so please
> don't conflate them.
Sorry for my laziness and the low effort to understand a thread I gave
a link :(.
To prove I can give a more effort to this thing I sit down to change
os-prober code to comply with grub-mount feature (symlink behaviour).
A first level of problem is duplicating output of the same kernel/initrd
filename pairs. Duplicates appears because the patterns tried are not
disjunctive at the line 15 of /usr/lib/linux-boot-probes/mounted/90fallback.
for kernpat in /vmlinuz /vmlinux /boot/vmlinuz /boot/vmlinux "/boot/vmlinuz*" \
"/boot/vmlinux*" "/vmlinuz*" "/vmlinux*" "/kernel-*"
"/boot/kernel-*"; do
I don't know why there are pattern pairs /vmlinuz and "/vmlinuz*" and so
on. Shell wild-card "/vmlinuz*" is expanded in the alphabetical order,
so potential /vmlinuz alone is expanded always first if exists. I'm not
certain the reasoning... aha in between is /boot/vmlinuz, so if both
exists /vmlinuz and /boot/vmlinuz, they appear in that order
(/boot/vmlinuz appears before /vmlinuz).
...initrd patterns at the line 27...:
initrdname=$(echo "$kernfile" | sed
"s/vmlinu[zx]/initrd\*/")
# Yellow Dog Linux appends .img to it.
initrdname1="${initrdname}.img"
The following patch removes duplicates from expanded patterns of kernels and
initrd images:
--- /usr/lib/linux-boot-probes/mounted/90fallback~ 2012-11-18
20:40:05.050334822 +0100
+++ /usr/lib/linux-boot-probes/mounted/90fallback 2012-11-18
21:16:50.846268406 +0100
@@ -21,6 +21,8 @@
fi
for kernfile in $(eval ls "$mpoint$kernpat" 2>/dev/null); do
kernbasefile=$(echo "$kernfile" | sed "s!^$mpoint!!")
+ echo "$kernfile_seen" | fgrep -q " $kernbasefile " && continue
+ kernfile_seen="$kernfile_seen $kernbasefile "
if [ -f "$kernfile" ] && [ ! -L "$kernfile" ]; then
initrdname=$(echo "$kernfile" | sed
"s/vmlinu[zx]/initrd\*/")
# Yellow Dog Linux appends .img to it.
@@ -35,7 +37,7 @@
# And Gentoo's also
initrdname4=$(echo "$kernfile" | sed
"s/kernel/initramfs\*/")
foundinitrd=0
- for initrd in $(eval ls "$initrdname" "$initrdname1"
"$initrdname2" "$initrdname3" "$initrdname4" 2>/dev/null); do
+ for initrd in $(eval ls "$initrdname" "$initrdname1"
"$initrdname2" "$initrdname3" "$initrdname4" 2>/dev/null | sort | uniq); do
if [ "$initrd" != "$kernfile" ] && [ -f
"$initrd" ] && [ ! -L "$initrd" ]; then
initrd=$(echo "$initrd" | sed
"s!^$mpoint!!")
result
"$partition:$kernbootpart::$kernbasefile:$initrd:root=$mappedpartition"
Before the patch:
bobek:~# /usr/lib/linux-boot-probes/50mounted-tests /dev/mapper/vg-deboot
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/boot/vmlinuz-3.2.0-4-amd64:/boot/initrd.img-3.2.0-4-amd64:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
After the patch:
bobek:~# /usr/lib/linux-boot-probes/50mounted-tests /dev/mapper/vg-deboot
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/boot/vmlinuz-3.2.0-4-amd64:/boot/initrd.img-3.2.0-4-amd64:root=/dev/dm-23
I hope the above change is worth doing anyway.
We can go further and try to identify the identical file's with
different filenames. (This problem is introduced by grub-mount behaviour
on symlinks.)
--- /usr/lib/linux-boot-probes/mounted/90fallback~zito1 2012-11-19
01:04:58.817863969 +0100
+++ /usr/lib/linux-boot-probes/mounted/90fallback 2012-11-19
01:49:23.941785223 +0100
@@ -9,6 +9,11 @@
mpoint="$3"
type="$4"
+getmd5()
+{
+ md5sum "$1" | cut -f1 -d ' '
+}
+
mappedpartition=$(mapdevfs "$partition" 2>/dev/null) ||
mappedpartition="$partition"
exitcode=1
@@ -24,6 +29,7 @@
echo "$kernfile_seen" | fgrep -q " $kernbasefile " && continue
kernfile_seen="$kernfile_seen
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
On Mon 19 Nov 2012 at 02:09:47 -0500, Lou Poppler wrote: > Comments/Problems: This machine started with Win7 installation occupying > the entire disk. I resized the windows partition to 1/2 of the disk, > and installed wheezy into the new partitions [ /boot and / plus swap ], > which I created using manual partitioning in the installer. > When we got to the install GRUB phase, I see this message: > "[!] Install the GRUB boot loader on a hard disk > It seems that this new installation is the only operating system on this > computer. If so, it should be safe to install the GRUB boot loader to > the master boot record of your first hard drive." Bug#650819 maybe. Should be fixed in beta-4. > This is not what I want -- I want to set this up as dual-boot, win7/wheezy. > I said no to installing GRUB, and finished the install with no boot loader > changes. This should be a simple case for the installer to get right. > The manual for beta D-I doesn't steer me to any way to solve this, other > than to see the GRUB manual. Did you get that advice from section 6.3.6.1? I'd agree it is less helpful than intended. > So now I'm trying to become enough of a GRUB > expert to be able to create a manual boot loader configuration that will > maybe result in a working dual boot. It's a pity you declined to install GRUB. At least you should have got a bootable system from which to attempt to get the missing entry into the GRUB menu. You could consider a reinstall. Then boot into the new system and run update-grub as root. Alternatively, you could boot the netinst ISO in Rescue mode. From there you can reinstall GRUB and get a shell to use 'update-grub'. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121119110049.GA15581@desktop
Processed (with 1 errors): correct earlier mistake
Processing commands for cont...@bugs.debian.org: > block 693470 by 693709 Bug #693470 [capistrano,ruby-capistrano-ext] ruby-capistrano-ext and capistrano: error when trying to install together 693470 was blocked by: 692540 693466 692815 693470 was not blocking any bugs. Added blocking bug(s) of 693470: 693709 > unblock 693470 by 692540 Bug #693470 [capistrano,ruby-capistrano-ext] ruby-capistrano-ext and capistrano: error when trying to install together 693470 was blocked by: 693709 692540 693466 692815 693470 was not blocking any bugs. Removed blocking bug(s) of 693470: 692540 and 692815 > By mistake, I sent removal request against a bug report instead of > submit@b.d.o Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if you need assistance. -- 693470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13533396707224.transcr...@bugs.debian.org
Bug#693718: debootstrap: wrong 'for' in kldstat checks for freebsd
Package: debootstrap Version: 1.0.42 In the deboostrap scripts the string in sh: " for module in "linprocfs fdescfs tmpfs linsysfs"; do " it is interpreted as one string, so kldstat -m "$module" > /dev/null 2>&1 is always produce warning. Please remove double quotes for fix problem: --- /usr/local/sbin/debootstrap.bak 2012-11-19 19:44:00.529532488 +0400 +++ /usr/local/sbin/debootstrap 2012-11-19 19:48:17.165541277 +0400 @@ -437,7 +437,7 @@ fi if [ "$HOST_OS" = "kfreebsd" ] || [ "$HOST_OS" = "freebsd" ]; then - for module in "linprocfs fdescfs tmpfs linsysfs"; do + for module in linprocfs fdescfs tmpfs linsysfs; do kldstat -m "$module" > /dev/null 2>&1 || warning SANITYCHECK "Probably required module %s is not loaded" "$module" done fi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201211192001.59041.olev...@olevole.ru
debootstrap: wrong 'for' in kldstat checks for freebsd
Hi, In the deboostrap scripts the string in sh: " for module in "linprocfs fdescfs tmpfs linsysfs"; do " it is interpreted as one string, so kldstat -m "$module" > /dev/null 2>&1 is always produce warning. Please remove double quotes for fix problem: --- /usr/local/sbin/debootstrap.bak 2012-11-19 19:44:00.529532488 +0400 +++ /usr/local/sbin/debootstrap 2012-11-19 19:48:17.165541277 +0400 @@ -437,7 +437,7 @@ fi if [ "$HOST_OS" = "kfreebsd" ] || [ "$HOST_OS" = "freebsd" ]; then - for module in "linprocfs fdescfs tmpfs linsysfs"; do + for module in linprocfs fdescfs tmpfs linsysfs; do kldstat -m "$module" > /dev/null 2>&1 || warning SANITYCHECK "Probably required module %s is not loaded" "$module" done fi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201211191957.42847.olev...@olevole.ru
Bug#693510: Fwd: Bug#693510: installation report
Hi, On 11/19/2012 05:05 AM, Cyril Brulebois wrote: > Could not get identity of device /dev/ada0 - Inappropriate ioctl for device > any insight for this kfreebsd installation report? I'm getting this regularly on some machines where I installed kfreebsd. Despite of the annoying warning during installation a few times it is harmless and no side effects seem to appear. At least to me, I could continue any installation where this message appeared. It might be helpful to know which ioctl d-i tries to call down the bus, as I suspect it is one not supported by the FreeBSD kernel. Hence, bypassing that code may help. Aside, I had Wheezy d-i installations running on Virtualbox without problems. Let me know if I can provide you more details/testing. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#659131: marked as done (installation-report: grub-install fails on btrfs filesystem)
Your message dated Mon, 19 Nov 2012 18:50:40 +0100 with message-id <20121119185040.d066c2c2.li...@wansing-online.de> and subject line installation-report: grub-install fails on btrfs filesystem - already fixed has caused the Debian Bug report #659131, regarding installation-report: grub-install fails on btrfs filesystem to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 659131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Version: 2.45 Severity: normal Tags: d-i -- Package-specific info: Boot method: CD Image version: 7.0 (Wheezy) - installer build 20120206-00:09 Date: 08-Feb-2010 Machine: Virtual box (fails on bare metal as well) Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 7993344 805644 6460588 12% / udev devtmpfs512536 0512536 0% /dev tmpfs tmpfs 103464 188103276 1% /run /dev/disk/by-uuid/bbb7467e-1ee2-46ed-80fb-104fb48ba3d0 btrfs 7993344 805644 6460588 12% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 206928 16206912 1% /tmp tmpfs tmpfs 206928 0206928 0% /run/shm Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: Problem occurs when /boot is on btrfs (in this particular case, there is just a single btrfs filesystem) grub-install /dev/sda fails, because it does not see the btrfs filesystem This is because /proc is not mounted. So there is an easy workaround: Once it fails, ask a shell; mount /proc: mount -t proc proc /target/proc and resume the install, grub will then complete successfully. As a side note, as long as there is no fsck.btrfs the system will not boot if root is on brtfs as the fsck pass will fail. So for btrfs it would be good to set the root fs in fstab in 'pass 0' to skip the check: # # / was on /dev/sda1 during installation UUID=/ btrfs defaults0 0 -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120206-00:09" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux woppy 3.2.0-1-486 #1 Wed Feb 1 08:35:59 UTC 2012 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:001e] lspci -knn: Kernel driver in use: e1000 lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] lspci -knn: 00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01) lspci -knn: Subsystem: Intel Corporation Device [8086:] lspci -knn: 00:06.0 USB controller [0c03]: Apple Computer Inc. KeyLargo/Intrepid USB [106b:003f] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) lspci -k
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Am 15.10.2012 um 22:42 schrieb Andreas B. Mundt: > Package: installation-reports > Severity: normal > > Hi, > > the wheezy default kernel 3.2 does not provide an appropriate nouveau > driver to start X on this machine. It is certainly supposed to do that, however. How exactly does it fail? > I have to use linux-image-3.5-trunk-amd64 to be able to start X. Can you please boot the 3.2 kernel, try to start X and send the output of "/usr/share/bug/xserver-xorg-core/script 3>&1" ? Thanks, Sven -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/873905jwy7@turtle.gmx.de
Bug#693510: Fwd: Bug#693510: installation report
On 19/11/12 04:05, Cyril Brulebois wrote: > update-dev: warning: unable to find udevadm; skipping > partman: mkfs.ufs: /dev/ada0s1: failed to open disk for writing A wild guess here, but maybe this is to do with the kfreebsd-8/9 renaming of /dev/ada0 -> /dev/ad0 Anton, please could you say which kernel you tried to install with? Did you choose kFreeBSD 9 from the installer GRUB menu or kFreeBSD 8? Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Re: building and testing d-i with jenkins
Hi, Holger Levsen wrote: > ok, I've renamed the d_i_manual_$LANG jobs to d_i_manual_$LANG_html and > created all d_i_manual_$LANG_pdf, which are triggered by success of their > d_i_manual_$LANG_html job. > > And, all new d_i_manual_$LANG_pdf jobs resulted in "unstable" builds due to > the four warnings each of them has: > > d-i_manual_de_pdf/builds/1/log-Architecture: hurd > d-i_manual_de_pdf/builds/1/log:Warning: The following formats failed to > build: > pdf > d-i_manual_de_pdf/builds/1/log-Architecture: hurd-i386 > d-i_manual_de_pdf/builds/1/log:Warning: The following formats failed to > build: > pdf > d-i_manual_de_pdf/builds/1/log-Architecture: kfreebsd > d-i_manual_de_pdf/builds/1/log:Warning: The following formats failed to > build: > pdf > d-i_manual_de_pdf/builds/1/log-Architecture: linux > d-i_manual_de_pdf/builds/1/log:Warning: The following formats failed to > build: > pdf 1. the error for arch hurd-i386 was a real error, which I fixed some minutes ago (for en). 2. the other errors are no real errors. The architectures "hurd", "kfreebsd" and "linux" are no 'real' architectures in the meaning of manual-building: "hurd" is "hurd-i386", "kfreebsd" is "kfreebsd-i386" or "kfreebsd-amd64" and "linux" is one of "amd64, i386, powerpc, sparc, ...". So, "hurd", "kfreebsd" and "linux" are kernels, no architectures, and are to be omitted for the builds. I don't know, why Jenkins tries to build those 'architectures'. Do you use the same scripts/methods to build, which are also used for regular package building? Or do you trigger all those builds by separate, custom commands? Holger W. -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 3.0.2 under D e b i a n G N U / L I N U X 6.0 ( S q u e e z e ) Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121119205346.8f6d1eeb.li...@wansing-online.de
Bug#693510: Fwd: Bug#693510: installation report
I have selected kfreebsd 9 kernel. There is no option to use 8. Regards, Anton On Mon, Nov 19, 2012 at 7:35 PM, Steven Chamberlain wrote: > On 19/11/12 04:05, Cyril Brulebois wrote: >> update-dev: warning: unable to find udevadm; skipping >> partman: mkfs.ufs: /dev/ada0s1: failed to open disk for writing > > A wild guess here, but maybe this is to do with the kfreebsd-8/9 > renaming of /dev/ada0 -> /dev/ad0 > > Anton, please could you say which kernel you tried to install with? Did > you choose kFreeBSD 9 from the installer GRUB menu or kFreeBSD 8? > > Thanks! > Regards, > -- > Steven Chamberlain > ste...@pyro.eu.org > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag3tgcpkfvbqmmbe68_jwk-snjsnox1htlffpjqkuun4uww...@mail.gmail.com
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Hi Sven, On Mon, Nov 19, 2012 at 06:59:12PM +0100, Sven Joachim wrote: > Am 15.10.2012 um 22:42 schrieb Andreas B. Mundt: > > > Package: installation-reports > > Severity: normal > > > > the wheezy default kernel 3.2 does not provide an appropriate nouveau > > driver to start X on this machine. > > It is certainly supposed to do that, however. How exactly does it fail? Perhaps I should be more accurate. The machine freezes when booting and I have to power off (Sys-Rq and other key combinations do not help). The last line shown on the screen (with "quiet" removed from the kernel boot stanza) differs. If it helps I can run a series and report the final lines. However, I am able to boot with "nomodeset" added to the boot parameters. > > I have to use linux-image-3.5-trunk-amd64 to be able to start X. > > Can you please boot the 3.2 kernel, try to start X and send the output > of "/usr/share/bug/xserver-xorg-core/script 3>&1" ? I attached the output when started with "nomodeset" as kernel boot parameter. The screen resolution is pretty bad (1024x768) compared to the resolution when running kernel 3.5. Please let me know if you need any other information, I am happy to provide what's needed. Best regards, Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121119203856.GA4388@lmz
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Am 19.11.2012 um 21:38 schrieb Andreas B. Mundt: > Hi Sven, > > On Mon, Nov 19, 2012 at 06:59:12PM +0100, Sven Joachim wrote: >> Am 15.10.2012 um 22:42 schrieb Andreas B. Mundt: >> >> > Package: installation-reports >> > Severity: normal >> > >> > the wheezy default kernel 3.2 does not provide an appropriate nouveau >> > driver to start X on this machine. >> >> It is certainly supposed to do that, however. How exactly does it fail? > > Perhaps I should be more accurate. > > The machine freezes when booting and I have to power off (Sys-Rq and > other key combinations do not help). The last line shown on the screen > (with "quiet" removed from the kernel boot stanza) differs. If it > helps I can run a series and report the final lines. However, I am > able to boot with "nomodeset" added to the boot parameters. Well, the problem is indeed in the graphics driver then, since "nomodeset" effectively disables it. Does it work with nouveau.noaccel=1 instead of nomodeset? > I attached the output when started with "nomodeset" as kernel boot > parameter. The screen resolution is pretty bad (1024x768) compared to > the resolution when running kernel 3.5. Yes, because you then get to use the vesa driver for X which does not support modern wide screens. > Please let me know if you need any other information, I am happy to > provide what's needed. Do you have another computer where you can capture kernel messages via netconsole? A short HOWTO for netconsole is on http://blog.mraw.org/2010/11/08/Debugging_using_netconsole, also see Documentation/networking/netconsole.txt in the kernel source. Cheers, Sven -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87sj85i9ym@turtle.gmx.de
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Hi Sven, On Mon, Nov 19, 2012 at 10:01:05PM +0100, Sven Joachim wrote: > Am 19.11.2012 um 21:38 schrieb Andreas B. Mundt: > > On Mon, Nov 19, 2012 at 06:59:12PM +0100, Sven Joachim wrote: > >> Am 15.10.2012 um 22:42 schrieb Andreas B. Mundt: > > > > The machine freezes when booting and I have to power off (Sys-Rq and > > other key combinations do not help). The last line shown on the screen > > (with "quiet" removed from the kernel boot stanza) differs. If it > > helps I can run a series and report the final lines. However, I am > > able to boot with "nomodeset" added to the boot parameters. > > Well, the problem is indeed in the graphics driver then, since > "nomodeset" effectively disables it. Does it work with > nouveau.noaccel=1 instead of nomodeset? No, it freezes again with nouveau.noaccel=1. > > I attached the output when started with "nomodeset" as kernel boot > > parameter. The screen resolution is pretty bad (1024x768) compared to > > the resolution when running kernel 3.5. > > Yes, because you then get to use the vesa driver for X which does not > support modern wide screens. OK > Do you have another computer where you can capture kernel messages via > netconsole? A short HOWTO for netconsole is on > http://blog.mraw.org/2010/11/08/Debugging_using_netconsole, also see > Documentation/networking/netconsole.txt in the kernel source. OK, I will look into that tomorrow and report back. Good night, Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121119212639.GA2540@fuzi
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
On Mon, Nov 19, 2012 at 10:01:05PM +0100, Sven Joachim wrote: [...] > Do you have another computer where you can capture kernel messages via > netconsole? A short HOWTO for netconsole is on > http://blog.mraw.org/2010/11/08/Debugging_using_netconsole, also see > Documentation/networking/netconsole.txt in the kernel source. It's attached. Cheers, Andi [0.007880] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [0.007881] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [0.008158] mce: CPU supports 9 MCE banks [0.008290] CPU0: Thermal monitoring enabled (TM1) [0.008418] using mwait in idle threads. [0.008992] ACPI: Core revision 20110623 [0.030623] DMAR: Host address width 36 [0.030742] DMAR: DRHD base: 0x00fed91000 flags: 0x1 [0.030871] IOMMU 0: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f0105a [0.031038] DMAR: RMRR base: 0x00bf69a000 end: 0x00bf6b9fff [0.031235] IOAPIC id 0 under DRHD base 0xfed91000 IOMMU 0 [0.031361] HPET id 0 under DRHD base 0xfed91000 [0.031482] HPET id 0 under DRHD base 0xfed91000 [0.031603] HPET id 0 under DRHD base 0xfed91000 [0.031725] HPET id 0 under DRHD base 0xfed91000 [0.031846] HPET id 0 under DRHD base 0xfed91000 [0.031968] HPET id 0 under DRHD base 0xfed91000 [0.032088] HPET id 0 under DRHD base 0xfed91000 [0.032209] HPET id 0 under DRHD base 0xfed91000 [0.032417] Enabled IRQ remapping in x2apic mode [0.032538] Enabling x2apic [0.032652] Enabled x2apic [0.032777] Switched APIC routing to cluster x2apic. [0.033340] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.073088] CPU0: Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz stepping 07 [0.179657] Performance Events: PEBS fmt1+, SandyBridge events, Intel PMU driver. [0.180034] PEBS disabled due to CPU errata. [0.187430] ... version:3 [0.187549] ... bit width: 48 [0.187669] ... generic registers: 4 [0.187788] ... value mask: [0.187911] ... max period: 7fff [0.188035] ... fixed-purpose events: 3 [0.188154] ... event mask: 0007000f [0.188410] NMI watchdog enabled, takes one hw-pmu counter. [0.188623] Booting Node 0, Processors #1 [0.299552] NMI watchdog enabled, takes one hw-pmu counter. [0.299778] #2 [0.407466] NMI watchdog enabled, takes one hw-pmu counter. [0.407686] #3 [0.515272] NMI watchdog enabled, takes one hw-pmu counter. [0.515488] #4 [0.623076] NMI watchdog enabled, takes one hw-pmu counter. [0.623294] #5 [0.730988] NMI watchdog enabled, takes one hw-pmu counter. [0.731207] #6 [0.838793] NMI watchdog enabled, takes one hw-pmu counter. [0.839011] #7 Ok. [0.946630] NMI watchdog enabled, takes one hw-pmu counter. [0.946782] Brought up 8 CPUs [0.946896] Total of 8 processors activated (38312.50 BogoMIPS). [0.954270] devtmpfs: initialized [0.957684] PM: Registering ACPI NVS region at bf6bd000 (1048576 bytes) [0.957981] print_constraints: dummy: [0.958151] NET: Registered protocol family 16 [0.958354] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.958524] ACPI: bus type pci registered [0.958720] PCI: MMCONFIG for domain [bus 00-ff] at [mem 0xe000-0xefff] (base 0xe000) [0.958894] PCI: MMCONFIG at [mem 0xe000-0xefff] reserved in E820 [0.978885] PCI: Using configuration type 1 for base access [0.979971] bio: create slab at 0 [0.980181] ACPI: Added _OSI(Module Device) [0.980301] ACPI: Added _OSI(Processor Device) [0.980421] ACPI: Added _OSI(3.0 _SCP Extensions) [0.980544] ACPI: Added _OSI(Processor Aggregator Device) [2.957185] ACPI: Interpreter enabled [3.307695] VFS: Disk quotas dquot_6.5.2 [3.307837] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [3.315327] msgmni has been set to 32073 [3.315578] alg: No test for stdrng (krng) [3.315722] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [3.315882] io scheduler noop registered [3.315994] io scheduler deadline registered [3.316133] io scheduler cfq registered (default) [ 38.356750] EXT4-fs (dm-1): INFO: recovery required on readonly filesystem [ 38.356885] EXT4-fs (dm-1): write access will be enabled during recovery [ 40.886481] iTCO_vendor_support: vendor-support=0 [ 40.891634] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [ 40.891835] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) [ 40.892047] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 40.904133] parport_pc 00:09: reported by Plug and Play ACPI [ 40.904351] parport0: PC-style at 0x378 (0x778), irq 5 [PCSPP,TRISTATE] [ 40.939369] [drm] Initialized drm 1.1.0 20060810 [ 40.982166] wmi: Mapper loaded [ 41.025398] Bluet
Bug#693756: installation-reports: thinkpad edge e135: graphics broken, needs nonfree firmware and experimental libdrm
Package: installation-reports Severity: normal -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso (2012-11-13) Date: 2012-11-18 Machine: Lenovo ThinkPad Edge E135 (bios disabled, using only uefi) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: the wifi was detected and loaded nonfree firmware from usb, but couldn't connect. seems to be an rf-kill problem that has yet to be investigated and is likely to spawn its own bug report. the main issue was getting the graphics to run -- the symptom being that after the system was installed and starts up, the display shows a random image that looks like memory. (random colours over large areas, large black areas, some white areas, occasionally black areas with a few coloured pixels). changing terminals didn't affect the screen's state. debugging based on init=/bin/sh revealed that the state occurs when udev loads the `radeon` module, and that the relevant dmeesg log line is: > kernel: [...] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing > generic drivers setting the module option radeon.modeset=0 in the kernel command line makes the garbage go away, but x still fails to start. with help from #radeon and a very helpful jcristau, i got things to run; those were the minimal steps required: * download the .bin files from [1] to `/lib/firmware/radeon`. i didn't have the patience to determine which exactly are needed, but PALM_pfp.bin is among them. those files are non-free, but hey, better than needing fglrx which runs non-free software on my cpu. * install libdrm-radeon1 and libdrm2 >= 2.4.40 (from experimental; works with a system that is otherwise wheezy) gdm and lightdm still fail to start, and strange graphics bugs show up in the gnome shell, but the system appears to be usable with xdm and xfce4 with and without compositing. armagetronad runs fluently to make me assume hardware 3d acceleration is active. [1] http://people.freedesktop.org/~agd5f/radeon_ucode/ -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20121113-00:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux artemis 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510] lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Device [1002:9808] lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314] lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1513] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1514] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1515] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:10.0 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB XHCI Controller [1022:7812] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] Hudson SATA Controller [AHCI mode] [1022:7801] lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB OHCI Controller [1022:7807] (rev 11) lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] Hudson USB EHCI Controller [1022:7808] (rev 11) lspci -knn: Subsystem: Lenovo Device [17aa:5105] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] Hu
Re: building and testing d-i with jenkins
Hi Holger, (btw: there are irc notifications now.) On Montag, 19. November 2012, Holger Wansing wrote: > 1. the error for arch hurd-i386 was a real error, which I fixed some > minutes ago (for en). nice! > 2. the other errors are no real errors. The architectures "hurd", > "kfreebsd" and "linux" are no 'real' architectures in the meaning of > manual-building: "hurd" is "hurd-i386", "kfreebsd" is "kfreebsd-i386" or > "kfreebsd-amd64" and "linux" is one of "amd64, i386, powerpc, sparc, ...". > So, "hurd", "kfreebsd" and "linux" are kernels, no architectures, and are > to be omitted for the builds. > I don't know, why Jenkins tries to build those 'architectures'. jenkins builds them, cause they exist in trunk/manual/build/arch-options/ :-) - and because jobs for the html versions build those fine. I'll omit those three kernel archs in my jenkins script now. And indeed, http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_en_pdf/3/ was successful now. I'll trigger the other translations. (And jobs for the other type of manual translations should follow soon.) > Do you use the same scripts/methods to build, which are also used for > regular package building? Or do you trigger all those builds by > separate, custom commands? for the manuals, I build them using a custom script, the above fix is here http://anonscm.debian.org/gitweb/?p=users/holger/jenkins.debian.net.git;a=commitdiff;h=5d4bcb4808b78fe989b9c955d7ab23e0075a60b4 the full script is at http://anonscm.debian.org/gitweb/?p=users/holger/jenkins.debian.net.git;a=blob;f=bin/d- i_manual.sh - it's really simple. you can view also the jenkins configuration yourself, eg for this job the url is http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_en_pdf/configure-readonly (there is a link in the sidebar of each job.) but those commands I use there are really taken from svn/trunk/manual :) thanks for your feedback, much appreciated! cheers, Holger -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201211200135.46446.hol...@layer-acht.org
