needs to change...
- Rich
At least on my old Netra T1, SILO has never believed in booting vmlinuz,
only vmlinux, and faults similarly if you try.
So if it just recently started faulting that way for you, perhaps any glue
that knew to unpack vmlinuz into vmlinux isn't working?
- Rich
On Sun, Jan 23, 2022 at 1:30 PM John
One more addendum - just the clm_blob alone from
https://github.com/RPi-Distro/firmware-nonfree/commit/dc406650e840705957f8403efeacf71d2d7543b3,
not even the sdio.bin with it, on top of the stock bullseye
firmware-brcm80211, works for me.
- Rich
On Sun, Nov 21, 2021 at 1:16 PM Rich wrote:
>
I appear to have just been burned by this setting up my new Pi 4B 4GB.
I likewise found that stealing just cyfmac43455-sdio.clm_blob (which
brcmfmac43455-sdio.clm_blob is a symlink to on my system) from
20210315-3+rpt3 and reloading the driver made everything happy and
functional...
- Rich
Ah, no, using this patch is a bad idea.
It worked fine for most of the day, but then I tried pushing a TB over
NFS, and it died with watchdog timeouts and indefinite hangs.
That's sad. I guess I'll go for the backup option...
- Rich
On Fri, Nov 19, 2021 at 3:19 AM Rich wrote:
>
> I
and scribble on your face with sharpie while you sleep,
just that I'm running it at the moment without such fires yet.
- Rich
On Fri, Nov 19, 2021 at 2:59 AM Rich wrote:
>
> I found the following patch generated against 5.14.0 helps and hasn't
> burned the house down in testi
I found the following patch generated against 5.14.0 helps and hasn't
burned the house down in testing so far.
---
diff --git a/drivers/net/ethernet/sun/niu.c b/drivers/net/ethernet/sun/niu.c
index 860644d182ab..70c08acd3ee5 100644
--- a/drivers/net/ethernet/sun/niu.c
+++
warm reboot, even "bad" kernel revisions will
function normally until a cold power cycle, so presumably there's some state
initialization that is no longer being done (correctly) in recent kernels?
Will continue to investigate...
System otherwise functions as expected if you apply module_bl
I see, so "kernel package in oldstable-backports is unusable" is not a bug.
Is there any way I can view why it's been sitting for so long that
this happened, or any estimate on how much longer it'll be broken?
=5.10.0-0.bpo.8-cloud-arm64
https://packages.debian.org/search?keywords=5.10.0-0.bpo.9-cloud-arm64
Thanks,
- Rich
-- System Information:
Debian Release: 10.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: arm64 (aarch64)
Kernel: Linux
on console to return to the boot prom
[101125.409302] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0009 ]---
I've done this workload a bunch, so I'm not really sure why it happened now
and not any time before, but here we are.
If you've got any suggested debugging info
,
which seems to still be true.
So...don't use GRUB, I guess?
- Rich
On Sun, Aug 22, 2021 at 4:03 AM Rich wrote:
>
> ...well that's _fascinating_.
> # grep -C3 nouveau /var/log/Xorg.0.log
> [30.712] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
> [30.712]
erm, it works with GRUB, too...
Seems GRUB screws up the world when it makes the pretty menu.
- Rich
On Sat, Aug 21, 2021 at 1:29 PM Rich wrote:
>
> https://forums.developer.nvidia.com/t/error-loading-nvidia-kernel-module-with-macbookpro3-1/39313
>
> I found other threads, but apparently th
their vBIOS out that
way, I'll see what I can do...
On Sat, Aug 21, 2021, 6:00 AM Rich wrote:
> Okay, so, I did just reboot and verify this...
>
> * kernel command line "... ro quiet":
> displays a blinking cursor in the top-left for a couple seconds and
> then ab
he config file.
(EE)
error:
(EE) no screens found(EE)
(EE)
(Full logs attached, .old is the one from "...ro" boot that didn't
display, the other is from a boot with nomodeset)
Can provide other information as useful.
- Rich
On Sat, Aug 21, 2021 at 4:28 AM Rich wrote:
>
> Also (I'v
Also (I've never used this before, so I might be holding it wrong, but...):
$ isenkram-lookup
cheese
ethtool
pcscd
scdaemon
$
On Sat, Aug 21, 2021 at 4:15 AM Rich wrote:
>
> Hi Salvatore,
> I used firmware-11.0.0-amd64-netinst.iso. And yes, I did not manually
> install firmware-
l: [2.385518] ata1.00: ATAPI: HL-DT-ST
DVDRW GSA-S10N, AP09, max UDMA/33
Aug 21 02:28:06 struth kernel: [2.457249] usb 4-1: new high-speed
USB device number 2 using ehci-pci
--
On Sat, Aug 21, 2021 at 4:03 AM Salvatore Bonaccorso wrote:
>
> Control: tags -1 + moreinfo
>
> Hi Ri
Sorry, as was pointed out to me, MacBookPro3,1 - not Macbook3,1.
Whoops.
- Rich
On Sat, Aug 21, 2021 at 2:48 AM Rich Ercolani wrote:
>
> Package: src:linux
> Version: 5.10.46-4
> Severity: normal
> X-Debbugs-Cc: rincebr...@gmail.com
>
> Dear Maintainer,
>
> (I h
y fiddling with kdump and non-journald logging so I can get a better
idea what might be happening when it stops outputting...
- Rich
-- 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
om how I'm
reporting it, it appears to have been broken all buster.)
- Rich
lt to find documentation
on how to do this properly.
- Rich
-- Package-specific info:
** Kernel log: boot messages should be attached
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: sh4
Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Lo
Sure.
https://bugzilla.kernel.org/show_bug.cgi?id=213143
- Rich
On Thu, May 20, 2021 at 1:16 AM Salvatore Bonaccorso wrote:
>
> Hi Rich,
>
> On Wed, May 19, 2021 at 12:14:49AM -0400, Rich wrote:
> > So it reproduces identically on 5.10.28 and 5.12.4 vanilla, but
&g
So it reproduces identically on 5.10.28 and 5.12.4 vanilla, but
5.13.0-rc2 fails differently, so I'm going to report that.
On Sun, May 16, 2021 at 11:13 AM Rich wrote:
>
> Sure, I'll try 5.12.4 once I'm done with the build I'm running. (I
> have no idea how long that'll be, though, I
Sure, I'll try 5.12.4 once I'm done with the build I'm running. (I
have no idea how long that'll be, though, I've never built it
before...)
- Rich
On Sun, May 16, 2021 at 11:08 AM Salvatore Bonaccorso wrote:
>
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Sat, May 15, 2021 a
Package: src:linux
Version: 5.10.28-1
Severity: normal
X-Debbugs-Cc: rincebr...@gmail.com
Dear Maintainer,
(This might also affect upstream, I haven't built a vanilla kernel to
experiment.)
On my (qemu-provided) alpha system, attempting to boot with the SMP kernel
yields the following message
Well, on my first attempt to reproduce it with no ZFS modules loaded, I got
a nice "BUG: unable to handle kernel paging request at 000168a0"
out instead of a GPF.
Is this sufficient, or would you like me to repeat until I produce a GPF
again?
- Rich
On Thu, May 12, 2016 at 9:
the drive, I either get a GPF or an Oops in my
kernel log.
The GPF follows - I could be mistaken, but I don't expect an IO error to
trigger a GPF in the kernel.
Please let me know if I can report any additional information to help with this.
- Rich
-- Package-specific info:
** Version:
Linux version
Package: linux-source-3.16
Version: 3.16.0-4
Severity: normal
Dear Maintainer,
I was going about my business, using perf top to see what I was spending a
bunch of my time in on this system, when suddenly, I got this written to
console:
[2425302.546957] Uhhuh. NMI received for unknown reason 11
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Richard Rath rcr...@yahoo.com
To: Debian Bug Tracking System 739...@bugs.debian.org
Subject: Re: linux-image-3.12-0.bpo.1-rt-686-pae: Does not boot. Hangs on
Booting
the kernel.
X-Debbugs-Cc:
.
[7.204955] radeon :01:00.0: Fatal error during GPU init
[7.205007] [drm] radeon: finishing device.
[7.205056] [drm] radeon: cp finalized
[7.209748] radeon: probe of :01:00.0 failed with error -22
Thank you for your efforts,
Rich
--
To UNSUBSCRIBE, email to debian-kernel-requ
Package: kernel
Severity: important
I'm having a problem with inconsistent numbering of the four internal
SATA ports on a Promise SATA300 TX4 controller (PCI, non-RAID, uses
Promise PDC40718 chip).
The ports are physically labelled 1, 2, 3, 4 on the card -- but the
ports are logically treated by
Package: linux-2.6
Severity: important
Tags: patch
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=C, LC_CTYPE=C
Package: kernel-source-2.6.8
Version: 2.6.8-16
Severity: important
Justification: fails to build from source
make-kpkg kernel-image against a just-fetched kernel-source-2.6.8 fails with:
cube-d:/usr/src/kernel-source-2.6.8-2.6.8# make-kpkg kernel-image
/usr/bin/make\
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-12
Severity: serious
Justification: Policy 10.7.3
Post-removal script fails reporting Not a directory: --verbose (or '-v').
kernel-image-2.6.8-powerpc is left stuck in a half-installed state and can
not be installed, removed, or upgraded via
This should be merged with 339487
(typed --body option rather than --body-file)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-k7/kernel/drivers/video/riva/rivafb.ko
to a bogus name so it wouldn't get loaded, and the system booted fine (I
suppose I'm missing some nVidia-special features, but everything looks
ok and X.org even came up using the nv driver.)
Rich
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
the judgement is it can't be legally distributed as part
of a package of Debian CD's, it isn't on a package of Debian CD's.
cheers, Rich.
--
rich walker | Shadow Robot Company | [EMAIL PROTECTED]
technical director 251 Liverpool Road |
need a Hand? London N1 1LX | +UK
37 matches
Mail list logo
