Hello Jeff and folks,
Not 100% certain yet, but your suggestion may have saved the day here
-- after a BIOS update, which I had not considered, no crashes for 24
hours or so.
So, my suggestions about iwlwifi and the kernel versions are all
retracted -- thanks sof your perspectives here!
Cheers
Hey Jeff -- yes, good point; I just looked at the manufacturer's page
and saw a bunch of BIOS updates; I'll try this next here (well, at the
next crash...).
Cheers!
On Tue, Feb 11, 2025 at 1:33 PM Jeffrey Walton wrote:
>
> On Fri, Feb 7, 2025 at 4:47 AM Boyan Penkov wrote:
> >
> > Anybody else
On Fri, Feb 7, 2025 at 4:47 AM Boyan Penkov wrote:
>
> Anybody else seeing this in the current testing kernel?
I am not experiencing the problem; but I used wired ethernet, and not wifi.
Is the machine's BIOS/UEFI up to date? That is the very first place I
would start. dmidecode is usually a goo
On 11/02/2025 05:11, Boyan Penkov wrote:
Is this a btrfs software issue? My hard drives all pass smartctl with
no errors.
I would check filesystem consistency. Have you tried to boot an older
kernel? Do you have any clue what python processes cause failures?
I have no idea if
Oops: invali
4
```
Is this a btrfs software issue? My hard drives all pass smartctl with
no errors.
Cheers!
On Mon, Feb 10, 2025 at 3:35 PM Boyan Penkov wrote:
>
> On Sun, Feb 9, 2025 at 9:33 PM Max Nikulin wrote:
> >
> > On 07/02/2025 22:55, Boyan Penkov wrote:
> > > I uninstalled fi
On Sun, Feb 9, 2025 at 9:33 PM Max Nikulin wrote:
>
> On 07/02/2025 22:55, Boyan Penkov wrote:
> > I uninstalled firmware-iwlwifi (this machine is wired either way...),
> > and the problem has not reared its head in a few hours -- not sure if
> > that means its solve
On 07/02/2025 22:55, Boyan Penkov wrote:
I uninstalled firmware-iwlwifi (this machine is wired either way...),
and the problem has not reared its head in a few hours -- not sure if
that means its solved...
I believed that crashes related to iwlwifi affect just network
connectivity, but
I uninstalled firmware-iwlwifi (this machine is wired either way...),
and the problem has not reared its head in a few hours -- not sure if
that means its solved...
Cheers!
On Fri, Feb 7, 2025 at 10:27 AM Max Nikulin wrote:
>
> On 07/02/2025 13:57, Boyan Penkov wrote:
> >
>
On 07/02/2025 13:57, Boyan Penkov wrote:
Anybody else seeing this in the current testing kernel?
Notice that most of call traces in your log are related to some python
processes (and btrfs) rater than to iwlwifi. Taking into account your
gnome-shell issue, your troubles may be related to
Sorry, this is a bit beyond my understanding, but the first lines that
come up in red on dmesg are:
```
Feb 07 01:12:33 themachine kernel: BUG: kernel NULL pointer
dereference, address:
Feb 07 01:12:33 themachine kernel: #PF: supervisor read access in kernel mode
Feb 07 01:12:33 t
And wht is it we are looking for? Contect please.
On 2/7/25 01:58, Boyan Penkov wrote:
Hello,
Anybody else seeing this in the current testing kernel?
Cheers!
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in tha
lmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 iwlwifi aesni_intel snd_hda_codec_hdmi btrtl btintel btbcm gf128mul btmtk snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec crypto_simd bluetooth cfg80211 cryptd snd_hda_core rapl snd_hwdep snd_pcm snd_timer snd sg rfkill soundcore ccp pcs
On Mon 18 Nov 2024 at 14:10:00 (+0100), Klaus Singvogel wrote:
>
> Yesterday I upgraded my Debian Bookworm on my Thinkpad T14 Gen4 laptop.
>
> After rebooting I lost my wifi.
>
> dmesg reported that the iwlwifi module failed with ucode (-2).
> I finally fixed it by i
On 2024-11-18, Klaus Singvogel wrote:
> I finally fixed it by installing the iwlwifi-firmware package from
> bookworm-backports:
> apt install -t bookworm-backports iwlwifi-firmware
You mean
apt install -t bookworm-backports firmware-iwlwifi
Hello,
Yesterday I upgraded my Debian Bookworm on my Thinkpad T14 Gen4 laptop.
After rebooting I lost my wifi.
dmesg reported that the iwlwifi module failed with ucode (-2).
I finally fixed it by installing the iwlwifi-firmware package from
bookworm-backports:
apt install -t bookworm
On 05/10/2022 05:18, David Wright wrote:
On Mon 03 Oct 2022 at 13:27:13 (-0600), Charles Curley wrote:
On Mon, 3 Oct 2022 20:53:46 +0300 Georgi Naplatanov wrote:
Actually I think I found out what was happening:
- for failed connection attempts trough SSH - the notebook
sometimes switches
On Mon 03 Oct 2022 at 13:27:13 (-0600), Charles Curley wrote:
> On Mon, 3 Oct 2022 20:53:46 +0300 Georgi Naplatanov wrote:
>
> > Actually I think I found out what was happening:
> >- for failed connection attempts trough SSH - the notebook
> > sometimes switches to suspend/sleep mode and turns
On Tue, 4 Oct 2022 at 06:27, Charles Curley
wrote:
> On Mon, 3 Oct 2022 20:53:46 +0300 Georgi Naplatanov wrote:
>>- for high latency - 100 ms and sometimes even more - this problem
>> is in my router probably (I installed OpenWrt on it, the issue may be
>> in my local environment, busy WiFi
On Mon, 3 Oct 2022 20:53:46 +0300
Georgi Naplatanov wrote:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/
>
> it seems that version 72 is not available but I'll try with 71.
I wouldn't bother. I agree with Stefan Monnier
's observation that these occur withi
-axis ()
{
until ping -c 1 -W 1 axis | grep 'bytes from'; do
printf '%s' "axis ";
done;
printf '%(%H:%M:%S)T\n' -1 && ssh -X axis -l unlock
}
This is related to my impatience rather than any system fault.
These are the entries
On 10/3/22 20:00, Stefan Monnier wrote:
These are the entries from kernel log:
[3.453655] iwlwifi :00:14.3: firmware: failed to load
iwlwifi-QuZ-a0-hr-b0-72.ucode (-2)
[3.453695] firmware_class: See https://wiki.debian.org/Firmware for
information about missing firmware
X axis -l unlock
}
This is related to my impatience rather than any system fault.
> These are the entries from kernel log:
>
> [3.453655] iwlwifi :00:14.3: firmware: failed to load
> iwlwifi-QuZ-a0-hr-b0-72.ucode (-2)
> [3.453695] firmware_class: See https://wiki.de
> These are the entries from kernel log:
>
> [3.453655] iwlwifi :00:14.3: firmware: failed to load
> iwlwifi-QuZ-a0-hr-b0-72.ucode (-2)
> [3.453695] firmware_class: See https://wiki.debian.org/Firmware for
> information about missing firmware
> [3.454449]
to join a
network? Please show us the exact log entry.
These are the entries from kernel log:
[3.453655] iwlwifi :00:14.3: firmware: failed to load
iwlwifi-QuZ-a0-hr-b0-72.ucode (-2)
[3.453695] firmware_class: See https://wiki.debian.org/Firmware for
information about missing firmwa
On Sun, 02 Oct 2022 12:41:14 -0400
The Wanderer wrote:
> And that the SSH connection is (at least part of) what seems to be
> dropping out, which is being interpreted as evidence that there's a
> problem with the wireless connection.
Good point. Let's see if the original poster (OP) clarifies th
On 2022-10-02 at 12:33, Charles Curley wrote:
> On Sun, 2 Oct 2022 11:49:14 +0300
> Georgi Naplatanov wrote:
>
>> I have a notebook (Lenovo) with Intel's WiFi and I have minor issues
>> with it - sometimes works as expected but sometimes I cannot connect
>> to the notebook at first attempt thro
On Sun, 2 Oct 2022 11:49:14 +0300
Georgi Naplatanov wrote:
> I have a notebook (Lenovo) with Intel's WiFi and I have minor issues
> with it - sometimes works as expected but sometimes I cannot connect
> to the notebook at first attempt throw SSH or sometimes latency is
> high.
Which model Lenov
On Sun, 2 Oct 2022 11:49:14 +0300
Georgi Naplatanov wrote:
Hello Georgi,
>thanks for the advice.
YW. Sadly, that's all the advice I can offer - I have no experience of
using SSH over WiFi, let alone the specific driver set you specified
(nothing here requires those drivers). Maybe somebody el
On 10/2/22 10:22, Brad Rogers wrote:
On Sat, 1 Oct 2022 20:37:34 +0300
Georgi Naplatanov wrote:
Hello Georgi,
The package is outdated but it's important.
It's the same version as in sid. VCS has -2 (merely bookkeeping
updates). Bug tracker shows no blocker bugs and no indication of
anythi
On Sat, 1 Oct 2022 20:37:34 +0300
Georgi Naplatanov wrote:
Hello Georgi,
>The package is outdated but it's important.
It's the same version as in sid. VCS has -2 (merely bookkeeping
updates). Bug tracker shows no blocker bugs and no indication of
anything newer.
If you have specific problems
Dear Debian community,
what is the problem with firmware-iwlwifi in testing?
The package is outdated but it's important.
Kind regards
Georgi
On Thu, Jul 09, 2020 at 05:27:26PM +1000, elvis wrote:
>
> On 7/7/20 4:15 am, Henning Follmann wrote:
> > On Mon, Jul 06, 2020 at 05:47:54PM +, emerald1475 wrote:
> > > I am running debian testing on a modern dell inspiron. My kernel
> > > (5.6.0-1-amd64) cant s
On 7/7/20 4:15 am, Henning Follmann wrote:
On Mon, Jul 06, 2020 at 05:47:54PM +, emerald1475 wrote:
I am running debian testing on a modern dell inspiron. My kernel
(5.6.0-1-amd64) cant seem to load the iwlwifi driver.
dmesg:
[ 2.571320] iwlwifi :00:14.3
Hi,
6 juil. 2020 à 20:15 de hfollm...@itcfollmann.com:
> On Mon, Jul 06, 2020 at 05:47:54PM +, emerald1475 wrote:
>
>> dmesg:
>> ----
>> [ 2.571320] iwlwifi :00:14.3: firmware: failed to load
>> iwlwifi-QuZ-a0-jf-b0-52.ucode (-2)
>&
On Mon, Jul 06, 2020 at 05:47:54PM +, emerald1475 wrote:
> I am running debian testing on a modern dell inspiron. My kernel
> (5.6.0-1-amd64) cant seem to load the iwlwifi driver.
>
> dmesg:
>
> [ 2.571320] iwlwifi :00:14.3: firmware: failed to load
I am running debian testing on a modern dell inspiron. My kernel
(5.6.0-1-amd64) cant seem to load the iwlwifi driver.
dmesg:
[ 2.571320] iwlwifi :00:14.3: firmware: failed to load
iwlwifi-QuZ-a0-jf-b0-52.ucode (-2)
[ 2.572778] iwlwifi :00:14.3: Direct firmware load
Quoting Stefan Pietsch (2020-02-14 22:36:39)
> iwlwifi has a problem with the latest Debian unstable kernel package
> (5.4.0-4-amd64).
> The wifi interface is not usable.
>
> 5.4.0-3-amd64 works fine instead.
>
> Is anyone experiencing the same problem?
Best way to fi
Hi list,
iwlwifi has a problem with the latest Debian unstable kernel package
(5.4.0-4-amd64).
The wifi interface is not usable.
5.4.0-3-amd64 works fine instead.
Is anyone experiencing the same problem?
##
dmesg at boot:
[ 10.318868] iwlwifi :03:00.0: enabling device (
9.37-5+deb10u1 ?
>
> With previews version of 4.19 I had problems after suspend to disk.
> Now it seems to be fixed.
>
> There are several Bug Reports with "iwlwifi 4.19 suspend" when you
> search in on google.
>
> Best Regards
Migual has you update to 4.19.37-5+deb10u1 ?
With previews version of 4.19 I had problems after suspend to disk.
Now it seems to be fixed.
There are several Bug Reports with "iwlwifi 4.19 suspend" when you
search in on google.
Best Regards
On 11.08.19 14:43, Miguel A. Vallejo wro
Same problem here. Kernel 5.2.x makes my MT76x2 wifi very unstable,
with bad performance and lot of dropouts. Running 4.19.x for now.
> I am using Sid on my laptop (HP ZBook 15) and since first linux-image-5.2.0-1
> and then linux-image-5.2.0-2
> the wifi is not stable and goes down after few sec
.
Here is an extract of the log using first package 5.2.0-1:
Aug 7 14:51:56 hp-dark kernel: [9.179880] iwlwifi :3d:00.0:
enabling device ( -> 0002)
Aug 7 14:51:56 hp-dark kernel: [9.202169] iwlwifi :3d:00.0:
firmware: direct-loading firmware iwlwifi-7260-17.ucode
Aug 7 14:51
Hallo, Klaus.
It would seem that the file you are looking for is in this package:
https://packages.debian.org/stretch/firmware-iwlwifi
Installing it should fix your problem.
Regards,
Andrea.
Il giorno mar 19 feb 2019 alle ore 11:45 Klaus Jantzen <
k.d.jant...@mailbox.org> ha scritto:
Hi,
on my laptop I upgraded Jessie to Stretch (with dist-upgrade).
Now Stretch does not work (mouse, WLAN, ethernet) because the module
'iwlwifi-6000-4.ucode' seems to be missing.
On Github I found that module dated 2014-12-09. Could I use this module?
The main question is: where
On 2/16/19 5:41 AM, rhkra...@gmail.com wrote:
On Friday, February 15, 2019 10:39:58 PM Peter Ehlert wrote:
I don't really know,
What don't you really know? It would be a lot easier to know what you're
talking about if you put your answer under the relevant question (i.e., not
top posting)
Pa
On Friday, February 15, 2019 10:39:58 PM Peter Ehlert wrote:
> I don't really know,
What don't you really know? It would be a lot easier to know what you're
talking about if you put your answer under the relevant question (i.e., not
top posting)
> it is a net install, draws the current packag
I don't really know, it is a net install, draws the current packages
from the repos... so it must have access. no wire was plunged in and my
wifi adapter needed iwiwifi-7260-17.ucode and asked for it.
The installer seems to Only install needed/desired packages.
for example, I did Not want the "d
On 2/15/2019 11:01 AM, Peter Ehlert wrote:
Buster install on 820 Friday, February 15 2019
on USB #1: firmware-buster-DI-alpha5-amd64-netinst.iso
I also have on USB #2: firmware-9.4.0-amd64-DVD-1.iso
booted with #1, ... It did ask for firmware, I put #2 in and pressed
"continue" and install co
ct my wifi
Hopefully the same will work for you
On 2/11/19 10:33 AM, deb wrote:
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode,
iwlwif
On 14/02/19 2:30 AM, deb wrote:
> Thank you Alexander.
>
> I kinda like the idea of pulling the Intel wifi and just going with a
> Think Penguin free software wifi.
>
> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb
>
>
The one that says: "Debian 7,
On 2/12/2019 3:25 PM, Alexander V. Makartsev wrote:
In response to that painful "(still installing 9.7 ...)".
You can also use these official and unofficial at the same time images
to install Debian. [1]
As a last resort you can disassemble laptop and physically remove Intel
WiFi NIC before ins
On 12.02.2019 3:46, deb wrote:
>
> Thanks ~everyone:
>
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
>
>
> anyways:
>
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the fi
On Mon 11 Feb 2019 at 17:46:19 (-0500), deb wrote:
> [ Peter wrote: ]
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the firmware archive for your platform and unpack it into
> a directory named firmware
>
> I hear you on this @Peter^
>
> I guess I'm kinda w
On Mon 11 Feb 2019 at 17:46:19 -0500, deb wrote:
> Do I gather correctly that Brian is the resident, sarcastic, cranky-pants
> herein?
Flatterer.
--
Brian.
deb, on 2019-02-11 :
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
Well, I prefer to make no assumptions about people just by
looking on the content of two emails. After all the first
intervention from Brian has m
n 2/11/19 10:33 AM, deb wrote:
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode,
iwlwifi-8625-24.ucode, iwlwifi-8625-23.ucode, iwlwifi-862
.
sorry, I don't have my notes, and my memory is crap today
On 2/11/19 10:33 AM, deb wrote:
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-862
On Mon 11 Feb 2019 at 14:01:06 -0600, David Wright wrote:
> Are you sure about 8625, rather than 8265?
Well-spotted.
https://packages.debian.org/stretch/firmware-iwlwifi
--
Brian.
On Mon 11 Feb 2019 at 20:42:10 +0100, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
I believe you have not.
https://packages.debian.org/sid/all/firmware-misc-nonfree/filelist
--
Brian.
On Mon 11 Feb 2019 at 13:33:39 (-0500), deb wrote:
>
> Hello folks:
>
> When I hit the networking section on a fresh install of 9.6 (full
> install .ISO, not live),
>
> I'm told to insert a USB of these non-free bits.
>
> iwlwifi-8625-26.ucode, iwlwifi-8625-2
On 2/11/19 8:42 PM, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
>
> $ sudo apt install firmware-misc-nonfree
Whoopsie, one should read "firmware-iwlwifi".
Anyway, the iwlwifi-8625
90123
Now the topic...
deb, on 2019-02-11:
> I'm told to insert a USB of these non-free bits.
>
>iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode,
>iwlwifi-8625-24.ucode, iwlwifi-8625-23.ucode,
>iwlwifi-8625-22.ucode
>
> The Problem is - I can't find 26-to-23
On Mon 11 Feb 2019 at 13:33:39 -0500, deb wrote:
[...]
> * wouldn't it be useful for the installer to Also say what exact hardware it
> is, that is requiring various bits & pieces?
As far as I can see, you haven't given which hardware you are using either.
--
Brian.
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode, iwlwifi-8625-24.ucode,
iwlwifi-8625-23.ucode, iwlwifi-8625-22.ucode
The Probl
ebian-live-9.4.0-amd64-lxde+nonfree.iso.
> ^^^
> > What's a legitimate question, but much better question would be - how
> > exactly a file named iwlwifi-7265D-22.ucode ended up being in your
> > filesystem?
>
> See above. firmw
etter question would be - how
exactly a file named iwlwifi-7265D-22.ucode ended up being in your
filesystem?
See above. firmware-iwlwifi is already installed.
7;s not what dmesg says.
> iwlwifi :03:00.0: enabling device ( -> 0002)
Means that iwlwifi (a 'driver' for our Windows friends) kernel module
was loaded.
> [ 6.534224] iwlwifi :03:00.0: firmware: failed to load
> iwlwifi-7265D-26.ucode (-2)
Means that iwlwifi
should install the
package firmware-iwlwifi.
But if I install this package could it generate conflict with the driver
that is already working?
Thanks,
Markos
lspci ->
03:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
dmesg ->
iwlwifi :03:00.0: enabling device
The reason for the message was that grub wasn't installed on the first (in
boot priority) device of my raid array. Sorry
On 11/01/2018 19:00, bw wrote:
On Thu, 11 Jan 2018, Rodary Jacques wrote:
Hi
I just upgraded to Stretch. At boot I get a warning: " No
symbols table" (actually it is in French: "pas de table des
symboles"). Nevertheless everything works, except my
access point: "modprobe iwlwifi.ko" can't fi
Hi
I just upgraded to Stretch. At boot I get a warning: " No
symbols table" (actually it is in French: "pas de table des
symboles"). Nevertheless everything works, except my
access point: "modprobe iwlwifi.ko" can't find this
module in the kernel directory, but this module is there.
I remembe
On Wed 09 Mar 2016 at 20:41:56 +0100, Pascal Hambourg wrote:
> Brian a écrit :
> >
> > Why should the installer ask for firmware if it knows it is present in
> > /lib/firmware? Your problem is that the firmware is not transferred to
> > the device. The consequence is that the wireless interface w
Brian a écrit :
>
> Why should the installer ask for firmware if it knows it is present in
> /lib/firmware? Your problem is that the firmware is not transferred to
> the device. The consequence is that the wireless interface wlan0 is not
> detected. The syslog should confirm this.
Or not. It does
On 03/08/2016 11:37 AM, Brian wrote:
> On Mon 07 Mar 2016 at 12:07:21 +, Andy Smith wrote:
>
>> On Mon, Mar 07, 2016 at 10:46:47AM +, Brian wrote:
>>> 1. Stop at the 'Detect network hardware' stage and switch to a console.
>>>
>>> 2. Unpack the .deb for the firmware you want:
>>>
>>>
On Mon 07 Mar 2016 at 12:07:21 +, Andy Smith wrote:
> On Mon, Mar 07, 2016 at 10:46:47AM +, Brian wrote:
> > 1. Stop at the 'Detect network hardware' stage and switch to a console.
> >
> > 2. Unpack the .deb for the firmware you want:
> >
> > ar -x /cdrom/pool/non-free/f/firmware-non
nd booted from it.
>>
>> At no point does it tell me that it requires additional firmware. It
>> also does not load iwlwifi or any of the associated wifi modules.
>
> An off-list response said they had more success with a daily
> installer image.
>
> I tried out:
>
On Tue 08 Mar 2016 at 07:21:06 +1100, Andrew McGlashan wrote:
>
>
> On 8/03/2016 6:30 AM, Nicolas George wrote:
> > L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> >>> dpkg --fsys-tarfile /path/to/file.deb | tar x
> >>
> >> You've tried using dpkg from a console in the installer at the install
On Mon 07 Mar 2016 at 20:58:13 +0100, Nicolas George wrote:
> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > Over the years I've observed that statements based on some preconceived
> > idea take precedence over trying a procedure and coming to a conclusion
> > based on experience and what is
On 8/03/2016 6:30 AM, Nicolas George wrote:
> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
>>> dpkg --fsys-tarfile /path/to/file.deb | tar x
>>
>> You've tried using dpkg from a console in the installer at the install
>> stage we are considering? Feel free to report back on your experience.
>
L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> Over the years I've observed that statements based on some preconceived
> idea take precedence over trying a procedure and coming to a conclusion
> based on experience and what is documented.
Given your criticism, I suppose you did try. Can you cop
On Mon 07 Mar 2016 at 20:30:19 +0100, Nicolas George wrote:
> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > > dpkg --fsys-tarfile /path/to/file.deb | tar x
> >
> > You've tried using dpkg from a console in the installer at the install
> > stage we are considering? Feel free to report back o
L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > dpkg --fsys-tarfile /path/to/file.deb | tar x
>
> You've tried using dpkg from a console in the installer at the install
> stage we are considering? Feel free to report back on your experience.
No, but I am ready to bet public humiliation that t
On Mon 07 Mar 2016 at 16:19:37 +0100, Nicolas George wrote:
> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > 2. Unpack the .deb for the firmware you want:
> >
> > ar -x /cdrom/pool/non-free/f/firmware-nonfree/
> >
> > 3. Uncompress data.tar.xz:
> >
> > unxz data.tar.xz
> >
> > 4.
On Mon, 7 Mar 2016 16:19:37 +0100
Nicolas George wrote:
>L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
>> 2. Unpack the .deb for the firmware you want:
>>
>> ar -x /cdrom/pool/non-free/f/firmware-nonfree/
>>
>> 3. Uncompress data.tar.xz:
>>
>> unxz data.tar.xz
>>
>> 4. Install the f
L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> 2. Unpack the .deb for the firmware you want:
>
> ar -x /cdrom/pool/non-free/f/firmware-nonfree/
>
> 3. Uncompress data.tar.xz:
>
> unxz data.tar.xz
>
> 4. Install the firmware in /lib/firmware:
>
> tar xvf data.tar
What is the poi
Hi Brian,
On Mon, Mar 07, 2016 at 10:46:47AM +, Brian wrote:
> 1. Stop at the 'Detect network hardware' stage and switch to a console.
>
> 2. Unpack the .deb for the firmware you want:
>
> ar -x /cdrom/pool/non-free/f/firmware-nonfree/
Because I was using the non-free firmware installer
On Mon 07 Mar 2016 at 03:39:26 +, Andy Smith wrote:
> Is there any way to force the debian-installer to realise it needs
> to load firmware for this wifi device? I have a feeling that it is
> seeing there is an eth0 and giving up at that point, assuming that
> is good enough.
>
> All of my on
es it tell me that it requires additional firmware. It
> also does not load iwlwifi or any of the associated wifi modules.
An off-list response said they had more success with a daily
installer image.
I tried out:
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmw
o does not load iwlwifi or any of the associated wifi modules.
So, given this is a netinst installer I am unable to proceed.
I tried dropping to a shell and doing "modprobe iwlwifi". Although
this appeared to load the module without error (lsmod shows it), it
did not result in a wlan0 netw
On Sat, 17 Oct 2015 07:25:18 -0700 (PDT), ray wrote:
> OK, I have network connnectivitiy.
>
> While reveiwing desktop functions and properties, I found the network app.
> All the availabe networks were listed. I selected the one I want to use,
> input the password and it connected. So I will h
OK, I have network connnectivitiy.
While reveiwing desktop functions and properties, I found the network app. All
the availabe networks were listed. I selected the one I want to use, input the
password and it connected. So I will hunt down how to provide this as an
automatic connection.
Using lspci -v
produces a report of the Intel 7265 which states, and
Kernel driver in use: iwlwifi.
ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever
This is very close. Debian is installed via Live. The network is not
functioning.
History:
With the non-free iso -
Booting in CSM:
Isolinux.bin missing or corrupt.
No bootable device -- insert boot disk and press any key
Booting in UEFI:
No bootable device -- Please restart system
On Fri, 16 Oct 2015 14:34:22 -0700 (PDT), ray wrote:
> That sounds great, I will try that right now.
>
> Can files be added to the USB?
>
> I am guessing that since the USB is not mounted, DD does not require any type
> of prep.
You won't need to add any files to the image (though you could af
On Friday 16 October 2015 22:34:22 ray wrote:
> I am guessing that since the USB is not mounted, DD does not require any
> type of prep.
It would destroy any prep you had done. ;-)
Now the netinstall with firmware might work!!
Lisi
That sounds great, I will try that right now.
Can files be added to the USB?
I am guessing that since the USB is not mounted, DD does not require any type
of prep.
On Thu, 15 Oct 2015 04:51:49 -0700 (PDT), ray wrote:
> > This seems very strange- if you are able to get the free version to boot you
> > should be able to get the non-free ISO to boot as well. They are identical,
> > save the inclusion of non-free firmware.
> Yes.
> >
> > The 'no bootable devi
On Thu, Oct 15, 2015 at 08:28:14AM +0300, moxalt wrote:
> On Tue, 13 Oct 2015 12:21:16 -0700 (PDT), ray wrote:
>
> > The above reference was for the 'free' version. I have not been able to get
> > the non-free to boot. I have wiped the Win OS and now it just says no
> > bootable device. So I w
> This seems very strange- if you are able to get the free version to boot you
> should be able to get the non-free ISO to boot as well. They are identical,
> save the inclusion of non-free firmware.
Yes.
>
> The 'no bootable device' message- does this occur when you select the hard
> drive as t
On Tue, 13 Oct 2015 12:21:16 -0700 (PDT), ray wrote:
> The above reference was for the 'free' version. I have not been able to get
> the non-free to boot. I have wiped the Win OS and now it just says no
> bootable device. So I will write to another stick and see it that works.
This seems very
1 - 100 of 133 matches
Mail list logo
