Bug#994727: reportbug: Hang at boot (pre-X) with [drm] CPU Pipe A FIFO underrun [workaround included]

2021-09-19 Thread John Goerzen
Package: src:linux
Version: 5.10.46-4
Severity: critical

Hello,

After upgrading this laptop from buster to bullseye, I started to have
issues.  The laptop uses a LUKS root, so it pauses before loading X to
prompt for a password.  Therefore I know this problem is not just X.

Immediately after putting in my password, I would observe screen corruption
(random garbage on the top few rows of pixels) followed by a complete
system hang.  Occasionally I was able to see a message on the console
first:

[drm] CPU Pipe A FIFO underrun

I tried booting the Debian bullseye live image, and it too would hang a few
minutes into the session (which was X-based) with no message at all.

Quite a bit of searching brought me to #884116 and this thread
https://lists.debian.org/debian-kernel/2017/12/msg00350.html.
Unfortunately, it didn't immediately help.

I tried iommu=soft and other iommu options, but they only resolved the
corruption but not the crash.

Eventually, I found
https://askubuntu.com/questions/895329/flickering-screen-cpu-pipe-b-fifo-underrun-when-i-use-the-termnal
which recommended these kernel options:

i915.enable_psr=0 i915.edp_vswing=2

This resolved the issue and the system booted normally.  That report also
mentions screen flickering; I also have been experiencing that in the
console (but not X) and the flickering persisted, but that is not a big
deal to me since most of the time is spent in X.

The askubuntu page also referenced disabling C-states in BIOS, though that
was not necessary for me.

This system is a Dell Latitude 7480 with a Core i7-7600U and Intel HD
Graphics 620.



-- Package-specific info:
** Version:
Linux version 5.10.0-8-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.46-4 (2021-08-03)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 root=ZFS=rpool/ROOT/debian-1 ro 
i915.enable_psr=0 i915.edp_vswing=2

** Tainted: PUOE (12353)
 * proprietary module was loaded
 * taint requested by userspace application
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[9.961833] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (1bcf:2b96)
[9.966740] dell_laptop: Using i8042 filter function for receiving events
[9.982813] input: Integrated_Webcam_HD: Integrate as 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input11
[9.987357] Console: switching to colour dummy device 80x25
[9.987385] i915 :00:02.0: vgaarb: deactivate vga console
[9.991762] usbcore: registered new interface driver uvcvideo
[9.991766] USB Video Class driver (1.1.1)
[   10.010681] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   10.013323] i915 :00:02.0: firmware: direct-loading firmware 
i915/kbl_dmc_ver1_04.bin
[   10.013611] i915 :00:02.0: [drm] Finished loading DMC firmware 
i915/kbl_dmc_ver1_04.bin (v1.4)
[   10.033304] i915 :00:02.0: [drm] Panel advertises DPCD backlight 
support, but VBT disagrees. If your backlight controls don't work try booting 
with i915.enable_dpcd_backlight=1. If your machine needs this, please file a 
_new_ bug report on drm/i915, see 
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for 
details.
[   10.042820] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
[   10.043946] Intel(R) Wireless WiFi driver for Linux
[   10.044259] iwlwifi :02:00.0: enabling device ( -> 0002)
[   10.078776] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-8265-36.ucode
[   10.079252] iwlwifi :02:00.0: loaded firmware version 36.ad812ee0.0 
8265-36.ucode op_mode iwlmvm
[   10.079281] iwlwifi :02:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[   10.079283] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   10.153860] Bluetooth: Core ver 2.22
[   10.153883] NET: Registered protocol family 31
[   10.153886] Bluetooth: HCI device and connection manager initialized
[   10.153890] Bluetooth: HCI socket layer initialized
[   10.153892] Bluetoo
th: L2CAP socket layer initialized
[   10.153896] Bluetooth: SCO socket layer initialized
[   10.170927] usbcore: registered new interface driver btusb
[   10.185285] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[   10.186286] Bluetooth: hci0: Device revision is 16
[   10.186289] Bluetooth: hci0: Secure boot is enabled
[   10.186290] Bluetooth: hci0: OTP lock is enabled
[   10.186291] Bluetooth: hci0: API lock is enabled
[   10.186292] Bluetooth: hci0: Debug lock is disabled
[   10.186293] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   10.189271] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-12-16.sfi
[   10.189278] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[   10.281773] EXT4-fs (sda2): mounting ext2 file 

Bug#934160: nfs-common: Umask ignored, all files created world-writable on NFS

2019-08-07 Thread John Goerzen
Package: nfs-common
Version: 1:1.3.4-2.5
Severity: grave
Tags: security
Justification: user security hole

I have an NFS client and server both running Debian.  I recently
upgraded them both to buster.

I discovered today that the regular process umask has been ignored on
my nfs mounts since the upgrade, and all files and directories are
being created a+rw.

On the client, the fstab fstype is nfs4 and the mount options are
hard,intr,bg,noatime.  The relevant datasets are exported
rw,no_root_squash,no_subtree_check from the server.

In researching this, I stumbled across
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736 and
https://bugzilla.redhat.com/show_bug.cgi?id=1667761 which indicate the
problem is present elsewhere as well.  Adding vers=4.1 to my client's
mount options completely resolved the problem.  (Though now I have a
couple weeks' worth of files with unintentionally open permissions to
wade through.)

I tagged this as security and grave because it opens up quite a few
scenarios for users to receive privileges they shouldn't, and for
other potential mischief (placing malicious executables in
world-writable directories, etc).

The server is indeed running zfs with its default acltype setting
(off).  As the Ubuntu bug report shows, mounting with noacl doesn't
resolve the behavior either.  The RedHat bug occurred with an OpenWRT
server, unlikely to be running zfs.  I do not believe this bug should
be pinned down to ZFS; a filesystem not supporting ACLs should not
result in umask 0 for all clients in any scenario.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-common depends on:
ii  adduser 3.118
ii  keyutils1.6-6
ii  libc6   2.28-10
ii  libcap2 1:2.25-2
ii  libcom-err2 1.44.5-1
ii  libdevmapper1.02.1  2:1.02.155-3
ii  libevent-2.1-6  2.1.8-stable-4
ii  libgssapi-krb5-21.17-3
ii  libk5crypto31.17-3
ii  libkeyutils11.6-6
ii  libkrb5-3   1.17-3
ii  libmount1   2.33.1-0.1
ii  libnfsidmap20.25-5.1
ii  libtirpc3   1.1.4-0.4
ii  libwrap07.6.q-28
ii  lsb-base10.2019051400
ii  rpcbind 1.2.5-0.3
ii  ucf 3.0038+nmu1

Versions of packages nfs-common recommends:
ii  python  2.7.16-1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- no debconf information



Bug#737333: initramfs-tools: Please support virtfs root

2014-02-01 Thread John Goerzen
Package: initramfs-tools
Severity: normal

This package doesn't support virtfs root.  It would be great if id did;
see

http://www.spinics.net/lists/linux-initramfs/msg02529.html

for an example patch.


-- 
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/20140201195922.23967.36591.report...@minerva.lan.complete.org



Bug#673290: nfs-common: rpc.idmapd drashes when given -d

2012-05-17 Thread John Goerzen
Package: nfs-common
Version: 1:1.2.5-4
Severity: normal

The manpage for rpc.idmapd documents the -d option.  However, when
given, it says:

the -d, -U, and -G options have been removed; please use the
configuration file instead.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  55360  status
1000241   tcp  46123  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = lan.complete.org
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
erwin:/nocrypt /nfs/nocrypt nfs4 hard,intr,bg,noatime 0 12
erwin:/media-crypt /nfs/media-crypt nfs4 hard,intr,bg,noatime,noauto 0 12
-- /proc/mounts --
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu1
ii  initscripts 2.88dsf-22.1
ii  libc6   2.13-32
ii  libcap2 1:2.22-1
ii  libcomerr2  1.42.2-2
ii  libdevmapper1.02.1  2:1.02.67-2
ii  libevent-2.0-5  2.0.18-stable-1
ii  libgssapi-krb5-21.10+dfsg~beta1-2
ii  libgssglue1 0.3-4
ii  libk5crypto31.10+dfsg~beta1-2
ii  libkeyutils11.5.5-2
ii  libkrb5-3   1.10+dfsg~beta1-2
ii  libmount1   2.20.1-4
ii  libnfsidmap20.25-2
ii  libtirpc1   0.2.2-5
ii  libwrap07.6.q-23
ii  lsb-base4.1+Debian2
ii  rpcbind 0.2.0-7
ii  ucf 3.0025+nmu3

Versions of packages nfs-common recommends:
ii  python  2.7.2-10

nfs-common suggests no packages.

-- no debconf information



-- 
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/20120517140949.8830.70530.report...@hephaestus.lan.complete.org



Bug#638316: More info

2012-02-01 Thread John Goerzen
Looks like there might be a patch to fix this - see 
https://bugzilla.redhat.com/show_bug.cgi?id=550724




--
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/4f294a21.2030...@complete.org



Bug#607298: firmware-linux-nonfree: Please include edgeport/down3.bin

2010-12-16 Thread John Goerzen
Package: firmware-linux-nonfree
Version: 0.27
Severity: wishlist

The edgeport/1 firmware, specifically edgeport/down3.bin, is included
in the 2.6.32 kernel.org tree but nowhere in Debian according to apt
and Contents-amd64.gz.  This is needed for USB-to-serial converters.

-- John

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (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/dash

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-tools   0.98.5 tools for generating an initramfs
ii  linux-image-2.6.32-3-amd64 [l 2.6.32-9   Linux 2.6.32 for 64-bit PCs
ii  linux-image-2.6.32-5-amd64 [l 2.6.32-28  Linux 2.6.32 for 64-bit PCs

-- no debconf information



-- 
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/20101216183553.31448.14989.report...@wile.internal.excelii.com



Bug#607298: firmware-linux-nonfree: Please include edgeport/down3.bin

2010-12-16 Thread John Goerzen

On 12/16/2010 01:27 PM, Ben Hutchings wrote:

On Thu, Dec 16, 2010 at 12:35:53PM -0600, John Goerzen wrote:

Package: firmware-linux-nonfree
Version: 0.27
Severity: wishlist

The edgeport/1 firmware, specifically edgeport/down3.bin, is included
in the 2.6.32 kernel.org tree but nowhere in Debian according to apt
and Contents-amd64.gz.  This is needed for USB-to-serial converters.


The licence information we have is:

Licence: Allegedly GPLv2+, but no source visible. Marked:
//**
//* Edgeport/4 Binary Image
//* Generated by HEX2C v1.06
//* Copyright (C) 1998 Inside Out Networks, All rights reserved.
//**

This means we do not have clear permission to distribute it.  You could
try talking to Inside Out Networks (which now seems to be part of Digi
International) about fixing this.  I have had some success with other
companies.


Hi Ben,

Over at 
ftp://ftp1.digi.com/support/beta/linux/edgeport/edgeport-0.5-1.gz (this 
is a tar file, despite the name), there is what appears to be this file 
in drivers/io_fw_down3.h; though the header there is:


//**
//* Edgeport Binary Image (for TI based products)
//* Generated by TIBin2C v2.00 (watchport)
//* Copyright (C) 2001 Inside Out Networks, All rights reserved.
//**

A copy of the GPL is included in this archive as COPYING, though is not 
explicitly referenced from this file.


That file is #included solely from drivers/io_ti.c, which bears this notice:

/*
 * Edgeport USB Serial Converter driver
 *
 * Copyright (C) 2000-2002 Inside Out Networks, All rights reserved.
 * Copyright (C) 2001-2002 Greg Kroah-Hartman g...@kroah.com
 *
 *  This program is free software; you can redistribute it and/or 
modify
 *  it under the terms of the GNU General Public License as 
published by

 *  the Free Software Foundation; either version 2 of the License, or
 *  (at your option) any later version.

drivers/Makefile.in, also explicitly under the GPL, flags it as a 
dependency for io_ti.o as well.


What are your thoughts on whether that is sufficient to merit rights to 
redistribute as part of the non-free package?


-- John



--
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/4d0a7c3a.5080...@complete.org



Xen, KVM, Squeeze

2010-02-26 Thread John Goerzen
Hi folks,

I posed these questions on debian-devel and was told I should be asking
them here.  Also, I got some rather contradictory information on -devel
so perhaps this is a good idea.  I'll repeat my questions along with the
answers I saw on -devel, and perhaps some light can be shed on it here.
 I will happily summarize on -devel.

According to http://wiki.debian.org/SystemVirtualization :

Qemu and KVM - Mostly used on Desktops/Laptops

VirtualBox - Mostly used on Desktops/Laptops

Xen - Provides para-virtualization and full-virtualization. Mostly used
on servers. Will be abandoned after squeeze.

 + Andrew M. A. Cater: Xen doesn't keep anywhere current in terms of
kernel - if we release Squeeze this year with kernel 2.6.3*, Debian will
have to maintain all the patches/ forward port them to 2.6.32 or
2.6.33 as was done with 2.6.2*.

 + Goswin von Brederlow: I think we can all agree that the old style xen
patches from 2.6.18 and forward ported to newer kernels in lenny are
unmaintainable. But the pv-ops xen kernel is shaping up well and that is
what Bastian Banks is working on. They have a proper upstream and follow
the latest vanilla kernel well enough. According to the wiki the plan is
to have pv-ops merge into vanilla with 2.6.34.

 + Olivier Bonvalet: Linux dom0 kernel from Lenny doesn't work at all on
some hardware with recent pv_ops domu.  In that case you have to change
to a different version...

The Xen page on the wiki makes no mention of this.

So, I am wondering about our direction in this way:


*** 1) Will a squeeze system be able to run the Xen hypervisor?  A Xen dom0?

 + Ben Hutchings: Maybe.  Ian Campbell and Bastian Blank are working on it.

 + Bastian Blank: [re hypervisor] Why not? I see packages laying around.
[re dom0] Most likely yes.  I'm currently ironing out the obvious bugs.


*** 2) Will a squeeze system be able to be installed as a Xen domU with
a lenny dom0?  What about squeeze+1?

 + Ben Hutchings: lenny's xen-flavour kernels (needed for dom0, optional
for domU) are not supportable even now.

 + Bastian Blank: Yes. It should even run on RHEL 5.

 + Olivier Bonvalet: I have a Debian squeeze running on a Lenny Dom0
Xen.  Today it seem to works.


*** 3) What will be our preferred Linux server virtualization option
after squeeze?  Are we confident enough in the stability and performance
of KVM to call it such?  (Last I checked, its paravirt support was of
rather iffy stability and performance, but I could be off.)

 + Marco d'Itri: [regarding KVM stability]: Yes. [regarding my
impressions of KVM being wrong]: You are, KVM had huge changes in the
last year.

 + Andrew M.A. Cater: KVM is shaping up well and appears to be very well
supported by Red Hat.

 + Goswin von Brederlow: But still slower and less secure due to qemu.


*** 3a) What about Linux virtualization on servers that lack hardware
virtualization support, which Xen supports but KVM doesn't?

Marco d'Itri: Tough luck.


*** 4) What will be our preferred server virtualization option for
non-Linux guests after squeeze?  Still KVM?

 + Marco d'Itri: Yes, virtualized Windows works much better in (modern)
KVM than Xen.


*** 5) Do we recommend that new installations of lenny or of squeeze
avoid Xen for ease of upgrading to squeeze+1?  If so, what should they use?

 + Ben Hutchings: I would discourage use of the xen-flavour in lenny.

 + Marco d'Itri: It depends. KVM in lenny is buggy and lacks important
features. While it works fine for development and casual use I do not
recommend using it in production for critical tasks. This is where Red
Hat really beats us: RHEL shipped Xen years ago but recently they
released an update which provides a backported and stabilized KVM.

 + Andrew M. A. Cater: New Squeeze - use KVM? New Lenny - whatever you
want, because at this point you have (days until release of Squeeze + 1
year) to find an alternative.

*** 6) Are we communicating this to Debian users in some way?  What can
I do to help with this point?

 + Marco d'Itri: Remind people that Xen is dying and KVM is the present
and the future.

 + Samuel Thibault: [to Marco] No FUD, thanks.

Thanks,

-- John


-- 
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/4b87d8a3.10...@complete.org



Bug#413990: linux-image-2.6.18-4-686: inotify CREATE events not sent for ??nfs4 filesystems

2008-12-17 Thread John Goerzen
Moritz Muehlenhoff wrote:
 On Thu, Mar 08, 2007 at 07:30:11AM -0600, John Goerzen wrote:
 Package: linux-image-2.6.18-4-686
 Version: 2.6.18.dfsg.1-11
 Severity: normal

 On nfs4 filesystems, inotify CREATE events are not being sent.  When I 
 touch a file, an open event is sent, and a proper event is sent when the 
 file is removed.  When I touch a file on a non-nfs4 filesystem, CREATE 
 events occur like normal.  This is confusing Nautilus, which does not 
 display new files that are saved to Desktop (/home is nfs-4 mounted)

 These creations are all occuring on the local machine.  I am not 
 expecting creations from other machines to be noticed.
 
 Does this error still occur with more recent kernel versions?

What kernel version in particular would you like me to test with?
2.6.26 new enough?



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



Bug#419254: linux-headers-2.6.20-1-k7: Fails to install due to missing dep

2007-04-14 Thread John Goerzen
Package: linux-headers-2.6.20-1-k7
Version: 2.6.20-1
Severity: grave
Justification: renders package unusable

katherina:/tmp# dpkg -i linux-headers-2.6.20-1-k7_2.6.20-1_i386.deb
Selecting previously deselected package linux-headers-2.6.20-1-k7.
(Reading database ... 221096 files and directories currently installed.)
Unpacking linux-headers-2.6.20-1-k7 (from
linux-headers-2.6.20-1-k7_2.6.20-1_i386.deb) ...
dpkg: dependency problems prevent configuration of
linux-headers-2.6.20-1-k7:
 linux-headers-2.6.20-1-k7 depends on linux-kbuild-2.6.20; however:
  Package linux-kbuild-2.6.20 is not installed.
dpkg: error processing linux-headers-2.6.20-1-k7 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-2.6.20-1-k7


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-headers-2.6.20-1-k7 depends on:
ii  gcc-4.1   4.1.1-21   The GNU C compiler
ii  linux-headers-2.6.20-12.6.20-1   Common header files for Linux 2.6.
pn  linux-kbuild-2.6.20   none (no description available)

linux-headers-2.6.20-1-k7 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409271: initramfs-tools: NFSv4 not supported for root fs

2007-02-01 Thread John Goerzen
Package: initramfs-tools
Version: 0.85e
Severity: normal

It appears to be largely undocumented, but a review of
/usr/share/initramfs/scripts/nfs shows that this package supports NFSv2
and v3 only.  I don't know why v4 isn't supported.

-- Package-specific info:
-- /proc/cmdline
root=/dev/hda10 ro 

-- /proc/filesystems
cramfs
xfs
ext2
iso9660

-- lsmod
Module  Size  Used by
ppdev   8964  0 
vmnet  34796  13 
parport_pc 32612  0 
parport33672  2 ppdev,parport_pc
vmmon 104236  0 
nls_iso8859_1   4544  0 
isofs  33276  0 
binfmt_misc11272  1 
cpufreq_ondemand6924  1 
nfsd  199792  10 
exportfs6080  1 nfsd
button  6928  0 
ac  5508  0 
battery 9924  0 
nfs   203980  2 
lockd  55240  3 nfsd,nfs
nfs_acl 3904  2 nfsd,nfs
sunrpc139772  13 nfsd,nfs,lockd,nfs_acl
ipv6  228064  28 
ext2   59656  1 
mbcache 8644  1 ext2
dm_crypt   11272  0 
powernow_k813696  1 
freq_table  4832  1 powernow_k8
floppy 53668  0 
psmouse35336  0 
rtc12788  0 
pcspkr  3392  0 
serio_raw   6980  0 
snd_intel8x0   30620  2 
snd_ac97_codec 83360  1 snd_intel8x0
snd_ac97_bus2688  1 snd_ac97_codec
snd_pcm_oss39200  0 
i2c_nforce2 7232  0 
snd_mixer_oss  15552  1 snd_pcm_oss
shpchp 33312  0 
pci_hotplug29056  1 shpchp
i2c_core   20096  1 i2c_nforce2
snd_pcm68996  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer  21316  1 snd_pcm
snd47524  10 
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore   9568  1 snd
snd_page_alloc  9928  2 snd_intel8x0,snd_pcm
amd64_agp  12292  1 
agpgart30216  1 amd64_agp
eth139418756  0 
joydev  9408  0 
tsdev   7808  0 
evdev   9408  0 
xfs   480024  4 
dm_mirror  19600  0 
dm_snapshot15840  0 
dm_mod 50776  10 dm_crypt,dm_mirror,dm_snapshot
ide_cd 36576  0 
cdrom  33056  1 ide_cd
ide_disk   15168  8 
sata_nv11332  0 
libata 90644  1 sata_nv
generic 5316  0 [permanent]
usbhid 37856  0 
ohci1394   31344  0 
ieee1394   88376  2 eth1394,ohci1394
aic7xxx   151764  0 
scsi_transport_spi 22656  1 aic7xxx
scsi_mod  124872  3 libata,aic7xxx,scsi_transport_spi
amd74xx13340  0 [permanent]
ide_core  110984  4 ide_cd,ide_disk,generic,amd74xx
ehci_hcd   28488  0 
ohci_hcd   18564  0 
forcedeth  38596  0 
usbcore   113412  4 usbhid,ehci_hcd,ohci_hcd
thermal13896  0 
processor  29128  2 powernow_k8,thermal
fan 5124  0 

-- kernel-img.conf
# Do not create symbolic links in /
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook   = /sbin/update-grub


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.1.3-3  Tiny utilities for small and embed
ii  cpio  2.6-17 GNU cpio -- a program to manage ar
ii  klibc-utils   1.4.30-3   small statically-linked utilities 
ii  module-init-tools 3.3-pre4-1 tools for managing Linux kernel mo
ii  udev  0.103-2/dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#397954: usplash: Doesn't work until undocumented steps are taken

2006-11-10 Thread John Goerzen
Package: usplash
Version: 0.3e
Severity: important

this package needs basic documentation.

Upon installing usplash, it integrates with initramfs (good).

But it doesn't document that a person needs to add usplash to the kernel
command line.

It also has a pretty much useless theme (is it even a real theme?) by
default.  There is no documentation in the package on how to build one's
own theme.

This makes it pretty much useless.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-486
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#397970: usplash: New upstream package available

2006-11-10 Thread John Goerzen
Package: usplash
Version: 0.3e
Severity: normal

Ubuntu is up to 0.4-33, and they appear to have quite a number of
improvements.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-486
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#397954: usplash: Doesn't work until undocumented steps are taken

2006-11-10 Thread John Goerzen
On Fri, Nov 10, 2006 at 07:16:55PM +0100, maximilian attems wrote:
  This makes it pretty much useless.
 
 version 0.4 is themable, but didn't yet work with the debian kernels.
 that means didn't display the splash screen.
 will hack on it this weekend.

It's working fine for me with the kernel in testing, 2.6.17.
  
 -- 
 maks
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380004: submitter address changed (initramfs-tools: wish vol_id would try to identify FSTYPE when fstype fails)

2006-07-26 Thread John Goerzen
Uhm, why did you do this?  It makes no sense.

On Wed, Jul 26, 2006 at 12:33:54PM -0700, Debian Bug Tracking System wrote:
 The submitter address recorded for your Bug report
 #380004: initramfs-tools: wish vol_id would try to identify FSTYPE
 has been changed.
 
 The old submitter address for this report was
 John Goerzen [EMAIL PROTECTED].
 The new submitter address is
 Alex Owen [EMAIL PROTECTED].
 
 This change was made by
 Alex Owen [EMAIL PROTECTED].
 If it was incorrect, please contact them directly.
 
 Debian bug tracking system administrator
 (administrator, Debian Bugs database)
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#362442: initramfs-tools: A few simple options for greater flexibility

2006-04-13 Thread John Goerzen
Package: initramfs-tools
Version: 0.59b
Severity: wishlist

Hello,

I am working on updating my DFS bootable Debian CDs to work with kernel
initrds in Debian.

There are a few things I would find helpful:

1) If scripts in local_top could change the notion of ROOT.

   I have a script that probes the system to find where the DFS CD is, 
   and then mounts it, since there is no ability to specify a custom
   ROOT.  Fortunately this works since the local script doesn't do
   error-checking.

2) If scripts in local_top could override the fstype guess.

   The fstype reports unknown for ISO9660 filesystems.  Ideally it would
   suport them, but even though it doesn't, it would be fine with me if
   I could override the detected value.

3) It should be documented that hooks and scripts may not contain
   hyphens in their names.

#1 and #2 could be accomplished by sourcing instead of executing
scripts, or perhaps by having a well-defined filename that the scripts
could create that would then be sourced.  Or even by creating a system
similar to the dependency one that's there already.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.3
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.01-4   Tiny utilities for small and embed
ii  cpio  2.6-11 GNU cpio -- a program to manage ar
ii  klibc-utils   1.2.6-1small statically-linked utilities 
ii  module-init-tools 3.2.2-2tools for managing Linux kernel mo
ii  udev  0.088-2/dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]