I had checked that my installer had 5.10.0 and if your assessement is
right then my installer must have been a daily build. Thanks a lot Roland
for keeping the finger on this issue!
*t
On Wed, 14 Apr 2021, Roland Clobus wrote:
reopen 986506
thanks
On 14/04/2021 08:58, Tomas Pospisek wrote
In #740499 Chris Bainbridge writes that:
[...] but firmware-7.4.0-amd64-netinst.iso does not contain
Broadcom firmware (at least not b43).
I can see that there are firmware packages for Broadcom b43 in contrib:
https://packages.debian.org/search?suite=bullseye=all=any=names=firmware-b
Could
Hi William,
if you still have access to the hardware it would be nice if you could
test whether the coming Debian bullseye installer still fails with it - I
assume this should have been fixed in the meanwhile - so this bug report
could be closed?
Thanks,
*t
Am 07.08.2014 12:32, schrieb Anton Zinoviev:
I have two bugs reported against console-setup about keybord not working
properly under X Window. In both cases I have asked the reportes to
provide the file /etc/default/keyboard and in both cases the file was
correct. Therefore, the bugs are
Package: boot-floppies
Version: N/A; reported 2002-03-18
Severity: minor
That's all I can say.
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux tpo2 2.4.16 #2 Fri Jan 4 18:17:17 CET 2002 i686
Locale: LANG=C, LC_CTYPE=C
--
To UNSUBSCRIBE, email to [EMAIL
Package: boot-floppies
Version: N/A; reported 2002-03-12
Severity: important
The main documentation index main/disks-*/current/doc/index.html has bad
link to the Release Notes (it currently links to
dists/testing/main/upgrade-i386/ which does not exist).
As of now the Release Notes seem to be
Is it appropriate to Cc: you? Or do you guys get the bugreport anyway?
On Sun, 6 Jan 2002, Philip Blundell wrote:
In message [EMAIL PROTECTED], Tomas Pospisek? writes:
That when something breaks during install of the basesystem, as f.ex.
a disk error etc., a newby will *not* be able
a install machine at hand at the moment, so I can not
test it in the near future :-/
*t
---
Tomas Pospisek
sourcepole- Linux Open Source Solutions
http://sourcepole.com
Elestastrasse 18, 7310 Bad Ragaz
Zitiere Adam Di Carlo [EMAIL PROTECTED]:
tags 127677 + wontfix
thanks
Tomas Pospisek [EMAIL PROTECTED] writes:
while trying to somehow find a basedebs.tgz
Why were you even looking for it? Why didn't you follow the normal
install the base system steps?
How would you install
can not read them.
The exact message is:
modprobe: modprobe: Can't open dependencies file /lib/modules/2.2.20/modules.dep
(No such file or directory)
*t
---
Tomas Pospisek
sourcepole- Linux Open Source
a partition is being mounted read only f.ex. when reading the base system
from it.
*t
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: minor
while trying to somehow find a basedebs.tgz I erroneously installed a powerpc
basedebs.tgz on
a i386 machine. Once I understood what went wrong I (after 4h of searching!) found a
i386
basedebs.tgz and installed it. But somehow
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: normal
after having the base system installed and rebooted the system will continue with
installing the
rest of debian. I did this through a ppp-style install. Unfortunately the system was
unable to
detect that a ppp connection went
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: normal
Instead of a scrollbar, I am seeing one or more #'s that seem to get placed
at the right window border aparently at random places.
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux eisberg 2.2.18 #1
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: normal
At some point during the install, the installation screen decided it would
switch to a black background. This certainly doesn't hurt but it's really
awkward.
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Package: boot-floppies
Version: 3.0.18-2001-11-21
Severity: wishlist
canceling when reading in root/rescue/driver-disks should not forget, or at
least let you use old read in stuff. Otherwise one has to repeat (and wait)
the procedure over and over if one has problems f.ex. with a bad disk or
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: important
The install process seems to be having some major problems with finding
out which partitions are currently mounted or not.
During the install I've been changing frequently between read (install disks
etc.) from harddisk or
Package: boot-floppies
Version: N/A; reported 2002-01-02
Due to a missconfiguration here - please use [EMAIL PROTECTED] for
replies. Sorry and thanks,
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux eisberg 2.2.18 #1 Thu Jan 18 11:10:26 CET 2001 i586
Locale:
Package: boot-floppies
Version: N/A; reported 2002-01-02
Severity: important
I did:
* mount a FAT32 partition while installing
* mv drivers-1.bin driver-1.bin.old
and the file just plain disapeared, without a warning or an error.
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: minor
When installing a module from the install menu I see in the buglog (tty3):
/target/usr/sbin/modconf: cannot create directory nonexistant
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux eisberg
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: wishlist
In the modules selection there is one section that says:
cdrom - Device drivers for CD-ROM drives
That's missleading, these are just drivers for non-(standard) IDE/ATAPI drives!
Newbies will think that they are not able to
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: minor
when I first try to install a module (driver) from the install menu each
time I do this I'll get (example for the 8139 module):
installing module 8139too
/lib/modules/2.2.20/net/8139too.o: init_module: Device or resource busy
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: minor
The description in the modules configuration says:
...You can read a page about the purpose of any module and then you can enable
or disable it.
Only that there is no page with a description of a module or if there is it's
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: minor
There are various description lines that are too long, that means that they
go over the width off the window and can't be read. F.ex in the misc
devices:
vfb - Virtual Frame Buffer support (ONLY FOR TESTI
*t
-- System
Package: boot-floppies
Version: N/A; reported 2002-01-02
sorry, my system was misconfigured: please use [EMAIL PROTECTED] for
replies. sorry and thanks,
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux eisberg 2.2.18 #1 Thu Jan 18 11:10:26 CET 2001 i586
Locale:
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: wishlist
When something goes wrong I would suggest a better strategy:
apart from the popup that tells the user *that* something goes wrong:
1) give him the exact error message (at least advanced users will know what to
do from it)
Package: boot-floppies
Version: N/A; reported 2002-01-02
sorry, my system was misconfigured - please use [EMAIL PROTECTED]
for replies.
*t
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux eisberg 2.2.18 #1 Thu Jan 18 11:10:26 CET 2001 i586
Locale: LANG=C, LC_CTYPE=C
Package: boot-floppies
Version: 3.0.18-2001-12-21
Severity: normal
The Installation Manual says in 2.2.0:
Diskless installation, using network booting from a local area network and
NFS-mounting of all local filesystems, is another option you'll probably need at
least 16MB of RAM for a
28 matches
Mail list logo
