210-5 all [installed]
firmware-linux-free/unstable,unstable,testing,now 20200122-1 all
[installed,automatic]
firmware-realtek/testing,now 20230210-5 all [installed]
Hope this helps,
--
Olaf Meeuwissen
Hi,
Again, unfortunately :-(
Diederik de Haas writes:
> On Sunday, 12 February 2023 03:29:14 CET Olaf Meeuwissen wrote:
>> Olaf Meeuwissen writes:
>> > Just checked again with 6.1.7-1 and still no joy :-(
>>
>> Glad to report joy cold-booting linux-image-6.1.0-3
Olaf Meeuwissen writes:
> Just checked again with 6.1.7-1 and still no joy :-(
Glad to report joy cold-booting linux-image-6.1.0-3-amd64.
Currrently have the following installed
$ dpkg-query -W | grep -E '(linux-image|firmware-iwlwifi)'
firmware-iwlwifi 20221
Olaf Meeuwissen writes:
> I am currently on
>
> firmware-iwlwifi/testing,now 20221214-3 all [installed]
> linux-image-6.0.0-4-amd64/now 6.0.8-1 amd64 [installed,local]
> linux-image-6.0.0-6-amd64/now 6.0.12-1 amd64 [installed,local]
> linux-image-6.1.0-1-amd64/testing
Olaf Meeuwissen writes:
> FYI, the situation is unchanged after upgrading
>
> - firmware-iwlwifi from 20221109-2 to 20221109-4
> - linux-image-6.0.0-5-amd64 from 6.0.10-1 to 6.0.10-2
> - linux-image-amd64 from 6.0.10-1 to 6.0.10-2
I am currently
Olaf Meeuwissen writes:
> Upgrading the firmware-iwlwifi package last week (2022-11-27) from
> 20221012-1 to 20221109-2 fixed the issue for linux-image-6.0.0-4-amd64
> 6.0.8-1. The changelog for 20221109-1 mentioned
>
> * iwlwifi: update firmware files for Intel Bluetooth AX2
microseconds apart.
For 6.0.0-4 there is no such error message.
Hope this helps,
--
Olaf Meeuwissen
loaded by 5.18.0-3 and
stays in the hardware's memory during the reboot so I get to use that
latest kernel with my Bluetooth-only keyboard. Cumbersome, at best.
Hope this helps,
--
Olaf Meeuwissen
Hi again,
Olaf Meeuwissen writes:
>> Package: linux-image-5.18.0-4-amd64
>> Severity: important
>>
>> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
>> Used that to report this bug as the failure to load leaves me without a
>> work
rsion, as opposed to a poweroff+boot, leaves the
keyboard in a usable state.
Hope this helps,
--
Olaf Meeuwissen
nt based on Debian 7, RHEL/CentOS 6 or
>> earlier versions."
>
> That's a good idea!
And is what I actually wanted to achieve because the message as is did
not make this "obvious" for me. Sorry for not being clear.
@Ian Thanks for the pointers, will have a
systemd (via /run/systemd/system)
Versions of packages linux-image-amd64 depends on:
ii linux-image-4.8.0-1-amd64 4.8.7-1
linux-image-amd64 recommends no packages.
linux-image-amd64 suggests no packages.
-- no debconf information
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS En
Hi Ben,
Ben Hutchings writes:
> On Fri, 2016-03-04 at 09:03 +0900, Olaf Meeuwissen wrote:
> [...]
>> The initramfs.conf file says:
>>
>> >
>> > # BUSYBOX: [ y | n ]
>> > #
>> > # Use busybox if available
>> > #
>> >
>&
amfs.conf to disable busybox unless
available. While at it, also update the comment. Another option is to
really do what that comment says, i.e. fix initramfs-tools to test for
busybox at run-time if BUSYBOX=y and act as if BUSYBOX=n when not found.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2
Just FYI, this bug is still present with
- linux-image-4.2.0-1-amd64 4.2.6-1
- linux-image-4.3.0-1-amd64 4.3.3-5
I've read through the thread and will take my system off LVM RAID1.
I have submitted #811033 against lvm2, requesting this to be documented.
Hope this helps,
--
Olaf Meeuw
o packages.
-- no debconf information
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 EPSON FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
.1.0-2-amd64/postinst/mips-initrd-4.1.0-2-amd64:
linux-image-4.1.0-2-amd64/prerm/removing-running-kernel-4.1.0-2-amd64: true
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 EPSON FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962[2]
pn firmware-qlogic
pn firmware-ralink
pn firmware-realtek
pn xen-hypervisor
-- debconf information:
linux-image-3.16.0-4-amd64/postinst/mips-initrd-3.16.0-4-amd64:
linux-image-3.16.0-4-amd64/prerm/removing-running-kernel-3.16.0-4-amd64: true
linux-imag
in our statedir lists files we don't want to end up in
the DESTDIR.
> also why does it need udev (just a minor nit..)?
There is nothing to be done if udev is not installed.
Hope this helps,
- --
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010?06?29? 07:55, maximilian attems wrote:
> On Tue, Jun 29, 2010 at 08:02:03AM +0900, Olaf Meeuwissen wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 2010???06???28??? 17:31, maximilian attems wrot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010年06月28日 17:31, maximilian attems wrote:
> On Mon, Jun 28, 2010 at 05:16:40PM +0900, Olaf Meeuwissen wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Image Scan! for Linux upstream maintainer here.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Image Scan! for Linux upstream maintainer here.
Care to point out why iscan is the culprit? I went through the logs but
nothing ran a bell.
If possible we'd like to get a fix out before squeeze goes stable ;-)
- --
Olaf Meeuwissen, L
22 matches
Mail list logo
