Package: klibc-utils
Version: 2.0.8-6.1
Followup-For: Bug #409272
X-Debbugs-Cc: rossboy...@stanfordalumni.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Earlier in this bug, Trent Buck suggested an initramfs hook zz-nfs4 to work
around the problem. I tried it, but I still can't get an NFS
Package: initramfs-tools
Version: 0.133+deb10u1
Severity: normal
X-Debbugs-CC: rossboy...@stanfordalumni.org
Dear Maintainer,
* What led up to the situation?
PXE booting a system with NFS root using isc-dhcp-server and
tftpd-hpa, most of the options passed by the dhcp server to the
Package: initramfs-tools
Version: 0.133+deb10u1
Severity: normal
X-Debbugs-CC: rossboy...@stanfordalumni.org
Dear Maintainer,
* What led up to the situation?
PXE booting a system with NFS root using isc-dhcp-server and tftpd-hpa,
the initrd environment does not know the hostname and
Package: src:linux
Version: 3.2.32-1
Severity: normal
Dear Maintainer,
Like many others, I'm having trouble with USB 3.0. Since the problems render
the keyboards completely
inoperative all the time, this is potentially quite serious. Fortunately I
have USB 2.0 ports and SSH, and
so am able to
Package: linux-2.6
Version: 2.6.26-29
Severity: normal
Since I applied the following updates
log file=aptitude.log
[UPGRADE] base-files 5lenny10 - 5lenny11
[UPGRADE] libapr1 1.2.12-5+lenny4 - 1.2.12-5+lenny5
[UPGRADE] libapr1-dev 1.2.12-5+lenny4 - 1.2.12-5+lenny5
[UPGRADE] libpq-dev
After enabling hardware virtualization in the BIOS, the kvm-intel module
loads.
I'll close this, since the driver was working OK.
--
Ross Boylan wk: (415) 514-8146
185 Berry St #5700 r...@biostat.ucsf.edu
Dept of Epidemiology
Package: linux-image-2.6.29-trunk-amd64
Version: 2.6.29-1~experimental.2~snapshot.13314
Severity: normal
*** Please type your report below this line ***
markov:~# modprobe -v kvm-intel
insmod /lib/modules/2.6.29-trunk-amd64/kernel/arch/x86/kvm/kvm-intel.ko
FATAL: Error inserting kvm_intel
Doh!
[1039316.644309] kvm: disabled by bios
I'm not at the machine, so can't fiddle the BIOS right now. I'll report
further when I can.
Ross
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
if the tip is known not to work with 2.6.29.
I'd appreciate cc on replies.
Thanks.
Ross Boylan
P.S. image is
linux-image-2.6.29-trunk-amd64 2.6.29-1~experimental.2~snapshot.13314
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Upgrading to the trunk snapshot seems to have fixed the problem.
Thanks for the suggestion.
Ross
On Wed, 2009-04-08 at 14:31 -0600, dann frazier wrote:
On Wed, Apr 08, 2009 at 01:10:16PM -0700, Ross Boylan wrote:
It appears that the ath5k wireless driver is crashing my system. It
leaves
On Wed, 2009-04-08 at 14:31 -0600, dann frazier wrote:
On Wed, Apr 08, 2009 at 01:10:16PM -0700, Ross Boylan wrote:
It appears that the ath5k wireless driver is crashing my system. It
leaves almost no info in the logs when it does so (and thus has taken
several weeks to find).
Should
appreciate if you cc'd me on the response.
Thanks.
Ross Boylan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sun, 2008-04-06 at 14:12 +0200, maximilian attems wrote:
On Sat, Apr 05, 2008 at 08:54:04PM -0700, Ross Boylan wrote:
Or so they say. Is just following the upstream instructions at
linuxwireless.org likely to work? Will it mess up things done the
debian way?
The other
Or so they say. Is just following the upstream instructions at
linuxwireless.org likely to work? Will it mess up things done the
debian way?
The other complication is that it sounds as if the fix is to the driver,
not the firmware. The tarball doesn't appear to have any firmware in
it. They
on Athlon; I take it that it is.
Ross Boylan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: firmware-iwlwifi
Version: 0.10
Followup-For: Bug #461924
I am seeing the same message, and experiencing intermittent connection
failures, with a 4965 wireless card. Not all failures are associated
with the message, and I think I sometimes get the Microcode SW
error on start up, but it
:)
Ross Boylan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, Jul 29, 2006 at 10:29:12AM +0200, maximilian attems wrote:
reassign 380292 initramfs-tools
thanks
hello ross,
On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote:
yes it seems to be an initramfs-tools trouble.
lilo is only run if there is no /sbin/grub or no /boot
On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote:
ok cool, please post the output of
dpkg-reconfigure linux-image-2.6.16-2-k7-smp
--
maks
Script started on Sat Jul 29 11:15:17 2006
iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp
Sat Jul 29 11:15:39 PDT 2006
On Sat, Jul 29, 2006 at 09:20:21PM +0200, maximilian attems wrote:
reassign 380292 kernel-package
stop
On Sat, Jul 29, 2006 at 11:20:55AM -0700, Ross Boylan wrote:
On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote:
ok cool, please post the output of
dpkg
Package: linux-image-2.6.16-2-k7-smp
Version: 2.6.16-17
Severity: normal
I upgraded this image and the installation process re-ran lilo. This
had the unfortunate effect of taking control of the boot back from
grub, and of making my system unbootable.
I've reinstalled grub (i.e., I'm OK), but I
On Mon, Mar 27, 2006 at 01:55:53AM +0200, maximilian attems wrote:
hello ross,
adding the evms maintainer on cc.
Trimming Mark Garey, our sysadmin, from the distribution, as I doubt
he wants the blow-by-blow.
On Mon, 20 Mar 2006, Ross Boylan wrote:
On Sun, 2006-03-19 at 19:35 -0800
I can now confirm that I can start the 2.6.15 kernel after switching the
loader to grub.
Note that the default setup of grub (with update-grub) uses raw disk
devices for the name of the root partition. I modified it as in the
second line below
# kopt=root=/dev/scsi/host0/bus0/target0/lun0/part8
On Sun, 2006-03-19 at 19:35 -0800, Ross Boylan wrote:
I've looked at the initramfs image and tried to trace through
execution by inspection (I'm not at the machine). I may be off base,
but here's what I noticed. In short, it looks as if the root
parameter of /dev/evms/newroot in lilo.conf
subsequent part of /proc/cmdline looks as if it should pull
in the correct value.
Finally, a couple clarifications of previous post.
The log in my initial post includes a line consisting only of
,pimt
Something must have hit the keyboard; ignore it.
Second,
On Fri, Mar 17, 2006 at 07:40:58PM -0800, Ross
Package: initramfs-tools
Version: 0.55b
Severity: normal
I am running a mostly testing system under a 2.4.27 kernel. I built a
2.6.15 kernel with the latest sources (2.6.15-8). kernel-package
10.036. lilo 22.6.1-7 and installed it with the latest unstable
initramfs-tools (0.55b).
When I boot
Having looked more closely at some of the internals of the package, I
want to highlight one fact: the device with the new root is
/dev/evms/newroot, and it could be pretty much anything. Since it's
supplied by evms, it's probably not relevant to think of it as scsi or
ide (it might, in principle,
27 matches
Mail list logo
