On 19/09/17 22:01, deloptes wrote:
what if you do
cd .../brcm/
sudo ln -s brcmfmac43602-pcie.bin brcmfmac43602-pcie.txt
On reboot I had a kernel panic. After removing that link everything
works again. These are the messages I got:
=
solitone wrote:
> brcm/brcmfmac43602-pcie.bin is the firmware for my Broadcom BCM43602
> wireless card, contained in package firmware-brcm80211. Without it the
> wifi network adapter didn't work, so I provided it during installation,
> and then that package was automatically installed. I don't und
On 19/09/17 14:11, Greg Wooledge wrote:
On Tue, Sep 19, 2017 at 07:54:32AM +0200, solitone wrote:
On 18/09/17 07:11, Jimmy Johnson wrote:
The packages you need to install are firmware-linux* and intel-microcode.
Would firmware-linux-nonfree bring any advantage as far as performance is
Bob Bernstein composed on 2016-06-03 22:29 (UTC-0400):
Felix Miata wrote:
In summary, 16x32 at a lower screen resolution translates to a
bigger glyph on any given display.
Thanks. That comports with my feeble cogitations. I'll give her
a whirl.
How did it go? What font size did you wind
Den 04. juni 2016 03:24, skrev Bob Bernstein:
> GRUB_GFXMODE=1024x768
> GRUB_GFXPAYLOAD_LINUX=1024x768
> and rem'd out
> # GRUB_TERMINAL=console
>
> The output of 'hwinfo --framebuffer' suggests I have many other larger
> and smaller resolutions available to me, but I am not one to muck
> around wi
On Fri, 3 Jun 2016, Felix Miata wrote:
In summary, 16x32 at a lower screen resolution translates to a
bigger glyph on any given display.
Thanks. That comports with my feeble cogitations. I'll give her
a whirl.
--
Man is essentially a dreamer, wakened sometimes for a
moment by some peculiar
Bob Bernstein composed on 2016-06-03 21:48 (UTC-0400):
I discovered and remedied that I only had one of the
firmware-linux-free/nonfree packages installed. Then I enabled
framebuffer and began to run dpkg-reconfigure console-setup with
some success. I now have Terminus2Bold 16x32 to use in my
ck with an
impossibly small console font (or, is "terminal font" the
correct verbiage?). Last night I hurled all caution to the wind
and revisited this situation. For those keeping score at home,
this is Jessie, sans systemd, running AMD64.
I discovered and remedied that I only had
covered and remedied that I only had one of the
firmware-linux-free/nonfree packages installed. Then I enabled
framebuffer and began to run dpkg-reconfigure console-setup with
some success. I now have Terminus2Bold 16x32 to use in my console,
or terminal, or whatever.
But I want bigger, to ac
ings, but dmesg
> stille gives the same error.
> *ERROR* radeon kernel modesetting for R600 or later requires
> firmware-linux-nonfree
>
> What can I do about this?
Install the firmware-linux-nonfree package? *Hint* check the repos or
just use apt-get.
Oh, crap! I replied to the
ings, but dmesg
> stille gives the same error.
> *ERROR* radeon kernel modesetting for R600 or later requires
> firmware-linux-nonfree
>
> What can I do about this?
Install the firmware-linux-nonfree package? *Hint* check the repos or
just use apt-get.
--
Bob Holtzman
A man is a m
>Just a hunch but maybe you booted the wrong kernel, or the initrd for
>some reason wasn't regenerated after the firmware was installed?
Exactly right!
When initrd was updated correctly, everything worked as advertised.
(FYI, this is live-8.3.0 with persistence, booted by legacy grub.)
Trond
s, but dmesg stille gives the same error.
> *ERROR* radeon kernel modesetting for R600 or later requires
> firmware-linux-nonfree
>
> What can I do about this?
>
> Trond
How about doing:
sudo apt-get install firmware-linux-nonfree
Cheers, Gene Heskett
--
"There are four box
s, but dmesg stille gives the same error.
> *ERROR* radeon kernel modesetting for R600 or later requires
> firmware-linux-nonfree
>
> What can I do about this?
Just a hunch but maybe you booted the wrong kernel, or the initrd for
some reason wasn't regenerated after the firmware was
or later requires
firmware-linux-nonfree
What can I do about this?
Trond
On Fri 22 May 2015 at 18:07:16 +, Curt wrote:
> On 2015-05-22, Brian wrote:
> >>
> >> Prolixity killed the cat.
> >
> > Commiserations. There's no accounting for the behaviour of a dog which
> > has been given that name.
> >
>
> I nicknamed him Fido.
But have you got an alias in ~/.bashrc?
On 2015-05-22, Brian wrote:
>>
>> Prolixity killed the cat.
>
> Commiserations. There's no accounting for the behaviour of a dog which
> has been given that name.
>
I nicknamed him Fido.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
On Fri 22 May 2015 at 15:48:04 +, Curt wrote:
> On 2015-05-21, Brian wrote:
> >
> > After the reboot:
> >
> > setupcon
> >
> > Please forgive my lack of verboseness.
> >
>
> Prolixity killed the cat.
Commiserations. There's no accounting for the behaviour of a dog which
has been given tha
On 2015-05-21, Brian wrote:
>
> After the reboot:
>
> setupcon
>
> Please forgive my lack of verboseness.
>
Prolixity killed the cat.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https
On Thu, 21 May 2015, Sven Arvidsson wrote:
It's probably a good idea to have the firmware
packages installed, I think these are used to handle
throttling to make sure it doesn't overheat.
Thank you for this insight and all the others you have
shared. I am still sufficiently gun-shy that I fe
On Thu 21 May 2015 at 11:35:52 -0400, Bob Bernstein wrote:
> On Thu, May 21, 2015 at 03:28:26PM +0200, Sven Arvidsson wrote:
>
> > dpkg-reconfigure console-setup
>
> After using the above, and rebooting, whatever changes the above
> made did not appear to "take" i.e. the teeny tiny console font
ed. The problem arose exactly
> simultaneously with my installing the firmware-linux
> metapackage. 'dpkg -r'ing the firmware-linux-free and -nonfree
> packages fixed the problem.
Oh, I see.
I think what happens is Kernel Mode Setting. With the proper firmware
for your graphic
On Thu, May 21, 2015 at 03:28:26PM +0200, Sven Arvidsson wrote:
> Probably something changed the console font, or you didn't
> have console-setup installed before.
Console-setup was already installed. The problem arose exactly
simultaneously with my installing the firmware-linux
On Thu, 2015-05-21 at 08:22 -0400, Bob Bernstein wrote:
> On Thu, 21 May 2015, Umarzuki Mochlis wrote:
>
> > dpkg-reconfigure ?
>
> I wonder: could you be a bit more verbose as to how
> you think I might use that command?
>
> Thanks!
Hi,
Probably something changed the console font, or you did
On Thu, 21 May 2015, Umarzuki Mochlis wrote:
dpkg-reconfigure ?
I wonder: could you be a bit more verbose as to how
you think I might use that command?
Thanks!
--
These are not the droids you are looking for.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subjec
2015-05-21 11:10 GMT+08:00 Bob Bernstein :
> I always cleave to my number one fundamental rule: if it ain't
> broke don't fix it. Unless of course curiosity comes into the
> picture and momentarily releases the crazy person who lives in
> my head.
>
> It wasn't pure unalloyed curiosity. I did see a
I always cleave to my number one fundamental rule: if it ain't
broke don't fix it. Unless of course curiosity comes into the
picture and momentarily releases the crazy person who lives in
my head.
It wasn't pure unalloyed curiosity. I did see a line in dmesg
telling me I should install the pac
On 07/08/2010 12:08 AM, Andrei Popescu wrote:
On Mi, 07 iul 10, 16:08:19, Paul Scott wrote:
I would kill NetworkManager and test whether your card can associate
with the AP if you set it up directly in /etc/network/interfaces. (Check
the output of"iwconfig eth2").
Stopping network-manager got
On Mi, 07 iul 10, 16:08:19, Paul Scott wrote:
> >
> >I would kill NetworkManager and test whether your card can associate
> >with the AP if you set it up directly in /etc/network/interfaces. (Check
> >the output of"iwconfig eth2").
>
> Stopping network-manager got me an instant association with
>
On 07/07/2010 02:46 PM, Florian Kulzer wrote:
On Wed, Jul 07, 2010 at 14:30:00 -0700, Paul Scott wrote:
On 07/07/2010 02:05 PM, Paul Scott wrote:
On 07/07/2010 01:46 PM, Sven Joachim wrote:
On 2010-07-07 22:17 +0200, Florian Kulzer wrote:
I would kill NetworkManager and test whether your
irmware.git;a=tree
[...]
> That at least got me a copy of the file. Thanks.
> >>
> >>They are also identical to the files in the Debian
> >>firmware-linux-nonfree package.
[...]
> Installing the above version of agere_sta_fw.bin elimated the
> eth2: Lucent
On 2010-07-07 23:40 +0200, Paul Scott wrote:
> Admitting I don't know the whole process well enough: Is it possible
> that the installing of firmware-linux-nonfree somehow doesn't properly
> download the agere*.bin as described in this thread?
>
> https://bugs.launchpad
t; link to the right of the names of the files
that you need. According to the "history" links, these two files were
added to the kernel in 2008 and have not been changed since.
They are also identical to the files in the Debian
firmware-linux-nonfree package.
Are you s
s
that you need. According to the "history" links, these two files were
added to the kernel in 2008 and have not been changed since.
That at least got me a copy of the file. Thanks.
They are also identical to the files in the Debian
firmware-linux-nonfree package.
Are you s
e "raw" link to the right of the names of the files
>>> that you need. According to the "history" links, these two files were
>>> added to the kernel in 2008 and have not been changed since.
>>
>> They are also identical to the files in the Debian
On 07/07/2010 01:46 PM, Sven Joachim wrote:
On 2010-07-07 22:17 +0200, Florian Kulzer wrote:
On Wed, Jul 07, 2010 at 12:50:09 -0700, Paul Scott wrote:
Hi,
From everything I can find the versions of firmware-linux-nonfree
for sid and unstable (0.26) contain corrupted versions of
On 2010-07-07 22:17 +0200, Florian Kulzer wrote:
> On Wed, Jul 07, 2010 at 12:50:09 -0700, Paul Scott wrote:
>> Hi,
>>
>> From everything I can find the versions of firmware-linux-nonfree
>> for sid and unstable (0.26) contain corrupted versions of
>> agere_sta_f
On Wed, Jul 07, 2010 at 12:50:09 -0700, Paul Scott wrote:
> Hi,
>
> From everything I can find the versions of firmware-linux-nonfree
> for sid and unstable (0.26) contain corrupted versions of
> agere_sta_fw.bin and agere_ap_fw.bin version 9.48
>
> Does someone know how
Hi,
From everything I can find the versions of firmware-linux-nonfree for
sid and unstable (0.26) contain corrupted versions of agere_sta_fw.bin
and agere_ap_fw.bin version 9.48
Does someone know how I can the uncorrupted versions of these files?
When I try to download them from the sites I
On Monday 20 April 2009 00:00:26 debian-user-digest-requ...@lists.debian.org
wrote:
> > I just noticed a new package in squeeze, firmware-linux, which contains
> > the binary firmware that was formerly included in Debian kernels [...]
> >
> > What I want to know is what k
Justin The Cynical wrote:
> Personally, my fix would to either get better kit than Dell or install
> an Intel based NIC, but since I don't control the purse strings in the
> company, I'll take what I can get.
DELL's not an option for me. Maybe I should look at Intel NICs,
though. Thanks for the
Alex Samad wrote:
> Another thought for remote install's what baout pxe-boot and add it to
> that image
This might work for others, but I usually have nothing onsite that can
deliver a PXE boot image so unfortunately it would gain me nothing.
Cheers,
Chris
--
To UNSUBSCRIBE, email to debian-
On Sun, Apr 19, 2009 at 02:45:33PM -0700, Justin The Cynical wrote:
> Chris Davies wrote:
>
[snip]
>
>> If I wasn't such a diehard Debian advocate, I'd have seriously considered
>> moving to another distribution. On the other hand, I can completely
>> understand /why/ Debian installations no long
Chris Davies wrote:
It's now become /really/ awkward to install Debian on DELL 2950s or any
other kit containing Broadcom NICs. You need to have a USB stick
that contans the relevant firmware package, and have that present
during the installation process. In and of itself this is only mildly
fid
tyler wrote:
> I just noticed a new package in squeeze, firmware-linux, which contains
> the binary firmware that was formerly included in Debian kernels [...]
> What I want to know is what kinds of problems I might experience when I
> move to a 'free' kernel? [...]
I
[...]
> Testing is pretty darn manageable, even for those of us who aren't
> compiling our own kernels. No offence meant, but you might want to
> recalibrate your ideas about the expertise required to run it.
>
I hear your opinion, however, from my experience with questions that have
been asked o
Thorny writes:
>> [...]
>> What I want to know is what kinds of problems I might experience when I
>> move to a 'free' kernel? Are these problems easily discoverable when I
>> switch? I'm most concerned about two possibilities - my system becomes
>> inoperable due to some dependency on binary fir
> [...]
> What I want to know is what kinds of problems I might experience when I
> move to a 'free' kernel? Are these problems easily discoverable when I
> switch? I'm most concerned about two possibilities - my system becomes
> inoperable due to some dependency on binary firmware; or the absence
Andrei Popescu writes:
>
> But if it breaks you still get to keep both parts.
>
Well, when you put it that way, it sounds like fun!
Cheers,
Tyler
--
The purpose of models is not to fit the data but to sharpen the
questions. --Samuel Karlin
--
To UNSUBSCRIBE, e
On Tue,31.Mar.09, 21:59:28, tyler wrote:
> I don't know enough about what the listed firmware does, or how it might
> relate to my hardware, to interpret the list. If the problems are all of
> the 'hardware doesn't work' variety that's easily managed by keeping a
> old kernel installed as a backu
Andrei Popescu writes:
> On Tue,31.Mar.09, 11:19:37, tyler wrote:
>>
>> What I want to know is what kinds of problems I might experience when I
>> move to a 'free' kernel?
>
> I'm guessing that the devices which need that firmware will just stop
> working. If that particular device is your HDD
On Tue,31.Mar.09, 11:19:37, tyler wrote:
> Hi,
>
> I have a naive question about binary firmware in Debian. I appreciate
> your patience with me!
>
> I just noticed a new package in squeeze, firmware-linux, which contains
> the binary firmware that was formerly included i
Hi,
I have a naive question about binary firmware in Debian. I appreciate
your patience with me!
I just noticed a new package in squeeze, firmware-linux, which contains
the binary firmware that was formerly included in Debian kernels. I'm
glad to see that it has been pulled out, so that w
53 matches
Mail list logo
