On 10/13/2017 01:56 PM, Emanuel Berg wrote:
Felix Miata wrote:
What I would do is remove the HD currently
installed, temporarily install some other HD,
install Windows on that, install the BIOS
update, then reinstall the original HD that
has Debian already installed.
Why not install XP, apply
David Wright wrote:
> Perhaps someone (me?) needs to explain that
> when you do what Brian asks, nothing happens
> to the installation you've already done.
> The network configuration is done right near
> the start, before the partitioning and before
> the installation of anything on the
> compute
On Fri 13 Oct 2017 at 22:02:54 (+0200), Emanuel Berg wrote:
> Brian wrote:
>
> > What does the installer tell you about the
> > network interfaces?
>
> I didn't check that because when I installed it
> I tried the new tethered USB Ethernet idea and
> then the DHCP autoconfig didn't fail. I can
>
On 10/13/2017 09:02 AM, Dejan Jocic wrote:
> On 13-10-17, Emanuel Berg wrote:
>> Curt wrote:
>>
I managed to install it by unplugging the
Ethernet cable, moving the computer to
another place, and instead using
a smartphone with USB-tethering to provide
Internet. Now one w
Emanuel Berg composed on 2017-10-13 22:56 (UTC+0200):
> Felix Miata wrote:
>> What I would do is remove the HD currently
>> installed, temporarily install some other HD,
>> install Windows on that, install the BIOS
>> update, then reinstall the original HD that
>> has Debian already installed.
>
Felix Miata wrote:
> What I would do is remove the HD currently
> installed, temporarily install some other HD,
> install Windows on that, install the BIOS
> update, then reinstall the original HD that
> has Debian already installed.
Why not install XP, apply the upgrade, and
install Debian? Isn'
Brian wrote:
> It took you about a minute to write your
> response. It would take no more five minutes
> to get the information asked for.
> USB tethering and noapic are sideshows,
I don't have an Ethernet connection here.
I moved the computer. If I can get the
information post-installation, and
Emanuel Berg composed on 2017-10-13 21:20 (UTC+0200):
> Felix Miata wrote:
>> https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-compaq-6720s-notebook-pc/3442832/swItemId/ob-66967-1
> An .exe file, is this the one you'd run after
> first installing Windows XP?
Yes.
> Then run it,
No.
On Fri 13 Oct 2017 at 22:02:54 +0200, Emanuel Berg wrote:
> Brian wrote:
>
> > What does the installer tell you about the
> > network interfaces?
>
> I didn't check that because when I installed it
> I tried the new tethered USB Ethernet idea and
> then the DHCP autoconfig didn't fail. I can
> c
Emanuel Berg composed on 2017-10-13 21:36 (UTC+0200):
>> OK, found it [1], in
>> /boot/grub/grub.conf
>> do "acpi=off", for example
>> kernel /vmlinuz-2.6.18-194.el5 ro
>> root=/dev/VolGroup00/LogVol00 rhgb quiet noapic
>> acpi=off
>> [1] https://access.redhat.com/solutions/58790
> Hm
Brian wrote:
> What does the installer tell you about the
> network interfaces?
I didn't check that because when I installed it
I tried the new tethered USB Ethernet idea and
then the DHCP autoconfig didn't fail. I can
check next time if the noapic idea
doesn't work.
--
underground experts unit
On Fri 13 Oct 2017 at 21:10:52 +0200, Emanuel Berg wrote:
> Brian wrote:
>
> > There isn't a single bit of evidence from the
> > OP that there is an ethernet firmware issue.
> > When asked to provide information on what the
> > installer sees and what happens
> >
> > https://lists.debian.org/de
I wrote:
>> He might also like to try before flashing
>> the bios or buying new material the "noapic"
>> kernel boot parameter the linux laptop site
>> referred to in the notes (although I have no
>> idea whether it is a sensible, viable
>> workaround or not).
>
> OK, found it [1], in
>
> /boo
Felix Miata wrote:
> https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-compaq-6720s-notebook-pc/3442832/swItemId/ob-66967-1
An .exe file, is this the one you'd run after
first installing Windows XP? Then run it, and
reinstall Debian?
They mention "RedFlag Linux", which is unknown
to
Curt wrote:
> He might also like to try before flashing the
> bios or buying new material the "noapic"
> kernel boot parameter the linux laptop site
> referred to in the notes (although I have no
> idea whether it is a sensible, viable
> workaround or not).
OK, found it [1], in
/boot/grub/gr
Curt wrote:
> He might also like to try before flashing the
> bios or buying new material the "noapic"
> kernel boot parameter the linux laptop site
> referred to in the notes (although I have no
> idea whether it is a sensible, viable
> workaround or not).
It sounds like something one would try
Brian wrote:
> There isn't a single bit of evidence from the
> OP that there is an ethernet firmware issue.
> When asked to provide information on what the
> installer sees and what happens
>
> https://lists.debian.org/debian-user/2017/10/msg00323.html
>
> he declined to provide it.
>
> He's pon
Michael Stone wrote:
> The thread got too long, so I'd forgotten
> what you'd meant by USB-ethernet. So yes, the
> thing you're doing works because it's not
> using the internet ethernet that has the
> firmware issue.
And by "firmware" you mean the "new" firmware
issue which is the DMI issue indi
Emanuel Berg composed on 2017-10-13 16:26 (UTC+0200):
> Curt wrote:
>> You must upgrade to the newest BIOS, because
>> the F.07< bioses, were known to have trouble
>> with ethernet drivers in Linux (and also in
>> Windows XP). After that you don't have to add
>> `noacpi` options on boot, as it is
On 2017-10-13, Michael Stone wrote:
>>
>>So you are saying, it is likely
>>"cable Ethernet" doesn't work because of the
>>DMI being outdated, and "USB Ethernet" works
>>because it has nothing to do with the DMI?
>
> The thread got too long, so I'd forgotten what you'd meant by
> USB-ethernet. So
On Fri 13 Oct 2017 at 14:15:41 -0400, Michael Stone wrote:
> On Fri, Oct 13, 2017 at 08:04:28PM +0200, Emanuel Berg wrote:
> > Michael Stone wrote:
> >
> > > USB ethernet would not be affected, but will
> > > also be slower/more cpu-intensive than
> > > internal PCI/PCIe ethernet. If you're happy
On Fri, Oct 13, 2017 at 08:04:28PM +0200, Emanuel Berg wrote:
Michael Stone wrote:
USB ethernet would not be affected, but will
also be slower/more cpu-intensive than
internal PCI/PCIe ethernet. If you're happy
with how the USB ethernet is working, then
just stick with it.
I'm not happy with
Michael Stone wrote:
> USB ethernet would not be affected, but will
> also be slower/more cpu-intensive than
> internal PCI/PCIe ethernet. If you're happy
> with how the USB ethernet is working, then
> just stick with it.
I'm not happy with it, or rather the guy who is
supposed to have the comput
On Fri, Oct 13, 2017 at 07:10:09PM +0200, Emanuel Berg wrote:
Because, when they say "ethernet drivers",
does that refer to the physical Ethernet port
only? I'm asking because the USB-tethering
works with no problem. And that would seem like
much more recent technology? Isn't that
Ethernet as wel
Dejan Jocic wrote:
>>> You must upgrade to the newest BIOS,
>>> because the F.07< bioses, were known to
>>> have trouble with ethernet drivers in Linux
>>> (and also in Windows XP). After that you
>>> don't have to add `noacpi` options on boot,
>>> as it is said in some forums.
>>
>> Upgrade the
On 13-10-17, Emanuel Berg wrote:
> Curt wrote:
>
> >> I managed to install it by unplugging the
> >> Ethernet cable, moving the computer to
> >> another place, and instead using
> >> a smartphone with USB-tethering to provide
> >> Internet. Now one wonders, what will happen
> >> when I plug in an
Curt wrote:
>> I managed to install it by unplugging the
>> Ethernet cable, moving the computer to
>> another place, and instead using
>> a smartphone with USB-tethering to provide
>> Internet. Now one wonders, what will happen
>> when I plug in an Ethernet cable once more
>> and expect Internet t
On 2017-10-12, Emanuel Berg wrote:
> Brian wrote:
>>
>> Choose an interface and move on. Is this
>> where it fails? Let us know what you see.
>> Stop, switch to console 2 and do 'more
>> /var/log/syslog'. Anything towards the end of
>> that log?
>
> I managed to install it by unplugging the
> Ethe
Brian wrote:
> In line with bw's suggestion you can now
> provide some hard information to base
> theories and solutions on.
>
> We surmise your computer is connected to
> a router by an ethernet cable. Boot the
> installer in expert mode and go through the
> first two screens. Say "no" to providi
On Mon, Oct 09, 2017 at 04:58:43PM +, Curt wrote:
> On 2017-10-09, rhkra...@gmail.com wrote:
> > On Sunday, October 08, 2017 05:07:13 PM bw wrote:
> >> On Sun, 8 Oct 2017, Emanuel Berg wrote:
> >> > Actually I don't care about wireless stuff, I always considered it
> >> > unreliable and error-
rhkramer writes:
> IIRC, the higher the frequency, the higher the energy in those
> waves--thus the more likely to have an effect.
I take it that you live in total darkness, then. But wait! Everything
around you is emitting infrared, at *much* higher frequencies than any
radio! Eek!
--
John Ha
On 2017-10-09, rhkra...@gmail.com wrote:
> On Sunday, October 08, 2017 05:07:13 PM bw wrote:
>> On Sun, 8 Oct 2017, Emanuel Berg wrote:
>> > Actually I don't care about wireless stuff, I always considered it
>> > unreliable and error-prone and it seems at least in this case I was
>> > correct :)
>
On Sunday, October 08, 2017 05:07:13 PM bw wrote:
> On Sun, 8 Oct 2017, Emanuel Berg wrote:
> > Actually I don't care about wireless stuff, I always considered it
> > unreliable and error-prone and it seems at least in this case I was
> > correct :)
>
> I know there is a legacy of this kind of thi
Brian wrote:
> Two bites of the cherry.
I actually did have a strange feeling I had
been thru all this before - but I thought it
was in a previous life... Anyway that time
I don't think I ever got past the whole WiFi
misconception, so it looks more hopeful this
time, God willing.
--
underground
On 10/08/2017 11:12 PM, anxious...@gmail.com wrote:
On Monday, 9 October 2017 06:50:03 UTC+1, Jimmy Johnson wrote:
Is there some kind of man page or something to explain what foo.deb is
and or bar.deb is, because in my 20+ years googling or other ways I
don't understand. If not I've been doi
On Sun, Oct 08, 2017 at 04:57:13PM -0400, bw wrote:
On Sun, 8 Oct 2017, Jimmy Johnson wrote:
On 10/08/2017 07:07 AM, Emanuel Berg wrote:
> Jimmy Johnson wrote:
>
> > You will need to download the depends too and
> > then cd to the directory that holds the files
> > and #dpkg -i (the package n
On Monday, 9 October 2017 06:50:03 UTC+1, Jimmy Johnson wrote:
>
> Is there some kind of man page or something to explain what foo.deb is
> and or bar.deb is, because in my 20+ years googling or other ways I
> don't understand. If not I've been doing fine without knowing. I will
> say I pro
On 10/08/2017 05:29 PM, David Wright wrote:
On Sun 08 Oct 2017 at 13:26:54 (-0700), Jimmy Johnson wrote:
On 10/08/2017 07:07 AM, Emanuel Berg wrote:
Jimmy Johnson wrote:
You will need to download the depends too and
then cd to the directory that holds the files
and #dpkg -i (the package name)
On Sun 08 Oct 2017 at 13:26:54 (-0700), Jimmy Johnson wrote:
> On 10/08/2017 07:07 AM, Emanuel Berg wrote:
> >Jimmy Johnson wrote:
> >
> >>You will need to download the depends too and
> >>then cd to the directory that holds the files
> >>and #dpkg -i (the package name) to install.
> >
> >OK. How s
On 10/08/2017 09:07 AM, Brian wrote:
On Sun 08 Oct 2017 at 17:28:31 +0200, Emanuel Berg wrote:
Brian wrote:
Install using the ethernet connection on the
machine. Then sort out the WiFi.
Ethernet doesn't work either! After the
firmware issue is brought up, the DHCP autoconf
fails. You are sa
On 10/08/2017 01:57 PM, bw wrote:
On Sun, 8 Oct 2017, Jimmy Johnson wrote:
On 10/08/2017 07:07 AM, Emanuel Berg wrote:
Jimmy Johnson wrote:
You will need to download the depends too and
then cd to the directory that holds the files
and #dpkg -i (the package name) to install.
OK. How shou
On Sun 08 Oct 2017 at 23:34:55 +0200, Emanuel Berg wrote:
> Brian wrote:
>
> > As for following up with a solution - don't
> > keep your hopes high.
>
> ?
Two bites of the cherry.
https://lists.debian.org/debian-user/2017/08/msg00457.html
--
Brian.
Brian wrote:
> As for following up with a solution - don't
> keep your hopes high.
?
--
underground experts united
http://user.it.uu.se/~embe8573
On Sun 08 Oct 2017 at 17:07:13 -0400, bw wrote:
> On Sun, 8 Oct 2017, Emanuel Berg wrote:
>
> > Actually I don't care about wireless stuff, I always considered it
> > unreliable and error-prone and it seems at least in this case I was
> > correct :)
>
> I know there is a legacy of this kind of
On Sun, 8 Oct 2017, Jimmy Johnson wrote:
> On 10/08/2017 07:07 AM, Emanuel Berg wrote:
> > Jimmy Johnson wrote:
> >
> > > You will need to download the depends too and
> > > then cd to the directory that holds the files
> > > and #dpkg -i (the package name) to install.
> >
> > OK. How should t
On 10/08/2017 07:14 AM, Emanuel Berg wrote:
Jimmy Johnson wrote:
You will need to download the depends too and
then cd to the directory that holds the files
and #dpkg -i (the package name) to install.
Do I abort the OS installation to do this or do
I "complete" it without network support and
On 10/08/2017 07:07 AM, Emanuel Berg wrote:
Jimmy Johnson wrote:
You will need to download the depends too and
then cd to the directory that holds the files
and #dpkg -i (the package name) to install.
OK. How should the depends be organized? I.e.,
the dir structure?
You should only need to
Brian wrote:
> In line with bw's suggestion you can now
> provide some hard information to base
> theories and solutions on.
>
> We surmise your computer is connected to
> a router by an ethernet cable. Boot the
> installer in expert mode and go through the
> first two screens. Say "no" to providi
On Sun 08 Oct 2017 at 18:29:04 +0200, Emanuel Berg wrote:
> Brian wrote:
>
> > If "yes", the failure to get an IP address
> > via DHCP has nothing to do with missing
> > wireless chip firmware.
>
> OK!
>
> So any theories as to why that happens?!
>
> I have another Debian computer there which
bw wrote:
> Also I did a quick search for Compaq 6720s
> and it the links I found don;t mention
> a broadcom device, it should have an intel
> wireless setup?
... okay?
Actually I don't care about wireless stuff,
I always considered it unreliable and
error-prone and it seems at least in this cas
Brian wrote:
> If "yes", the failure to get an IP address
> via DHCP has nothing to do with missing
> wireless chip firmware.
OK!
So any theories as to why that happens?!
I have another Debian computer there which
doesn't have an Ethernet problem save for I run
'dhclient eth0' every time the co
On Sun 08 Oct 2017 at 17:28:31 +0200, Emanuel Berg wrote:
> Brian wrote:
>
> > Install using the ethernet connection on the
> > machine. Then sort out the WiFi.
>
> Ethernet doesn't work either! After the
> firmware issue is brought up, the DHCP autoconf
> fails. You are saying this isn't relate
Brian wrote:
> Install using the ethernet connection on the
> machine. Then sort out the WiFi.
Ethernet doesn't work either! After the
firmware issue is brought up, the DHCP autoconf
fails. You are saying this isn't related to the
missing firmware?
If the firmware is only for WiFi, then it is
a
On 2017-10-08, Emanuel Berg wrote:
> Jimmy Johnson wrote:
>
>> You will need to download the depends too and
>> then cd to the directory that holds the files
>> and #dpkg -i (the package name) to install.
>
> OK. How should the depends be organized? I.e.,
> the dir structure?
>
I opened up the is
On 10/08/2017 09:14 AM, Emanuel Berg wrote:
Jimmy Johnson wrote:
You will need to download the depends too and
then cd to the directory that holds the files
and #dpkg -i (the package name) to install.
Do I abort the OS installation to do this or do
I "complete" it without network support and
On Sun 08 Oct 2017 at 15:45:40 +0200, Emanuel Berg wrote:
> Brian wrote:
>
> > https://wiki.debian.org/bcm43xx
>
> Thanks, however the installation guide says use
> the Internet to get it, and the reason that
> isn't working is the missing firmware!
Install using the ethernet connection on the
Jimmy Johnson wrote:
> You will need to download the depends too and
> then cd to the directory that holds the files
> and #dpkg -i (the package name) to install.
Do I abort the OS installation to do this or do
I "complete" it without network support and
then patch it later?
That probably makes
Jimmy Johnson wrote:
> You will need to download the depends too and
> then cd to the directory that holds the files
> and #dpkg -i (the package name) to install.
Or do you mean install the depends the same
way? I hope they don't depend on too much as
well :)
--
underground experts united
http:
Jimmy Johnson wrote:
> You will need to download the depends too and
> then cd to the directory that holds the files
> and #dpkg -i (the package name) to install.
OK. How should the depends be organized? I.e.,
the dir structure?
--
underground experts united
http://user.it.uu.se/~embe8573
On 10/08/2017 06:48 AM, Emanuel Berg wrote:
Jimmy Johnson wrote:
Is this what you are looking for:
https://packages.debian.org/stretch/firmware-b43-installer
Can I download that package with another
computer, install Debian without network
support, bring the installer over, and manually
insta
Jimmy Johnson wrote:
> https://packages.debian.org/stretch/firmware-b43-installer
The installer (the Debian installer on the
laptop) says I can insert a USB stick with the
missing firmware to patch the installation.
However it doesn't say in what form it should
come. Just having the files on the
Jimmy Johnson wrote:
> Is this what you are looking for:
> https://packages.debian.org/stretch/firmware-b43-installer
Can I download that package with another
computer, install Debian without network
support, bring the installer over, and manually
install it without Internet?
If so, how?
--
un
Brian wrote:
> https://wiki.debian.org/bcm43xx
Thanks, however the installation guide says use
the Internet to get it, and the reason that
isn't working is the missing firmware!
--
underground experts united
http://user.it.uu.se/~embe8573
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 08, 2017 at 05:17:44AM -0400, bw wrote:
[...]
> Yes, that isn't included. The firmware must be extracted from the
> proprietary (windows?) driver from Broadcom. It's possibly a legal hurdle
> set up by the manufacturer?
Yeah. If anyo
On 10/08/2017 12:46 AM, Emanuel Berg wrote:
First I downloaded this ISO:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/i386/iso-cd/firmware-9.2.0-i386-netinst.iso
Then I burned it onto a CD-R, and booted into
the installer.
The computer is a HP Comp
On Sun 08 Oct 2017 at 09:46:19 +0200, Emanuel Berg wrote:
> First I downloaded this ISO:
>
>
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/i386/iso-cd/firmware-9.2.0-i386-netinst.iso
>
> Then I burned it onto a CD-R, and booted into
> the installer.
First I downloaded this ISO:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/i386/iso-cd/firmware-9.2.0-i386-netinst.iso
Then I burned it onto a CD-R, and booted into
the installer.
The computer is a HP Compaq 6720s laptop.
However the installer doesn't
67 matches
Mail list logo