Bug#1052545: os-prober in initramfs gets repeatedly disabled
Package: os-prober Version: 1.81 Severity: normal Something happened in the last months. Whenever I upgrade, it seems like the os-prober part is disabled. This is just PITA. I can use the usual: dpkg-reconfigure -plow grub-efi-amd64 ... to turn it back on, and after an upgrade it's lost again. WHY? Now I started seeing messages after installing a new kernel package: Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... Sorry, dear maintainer, WHAT DOES THAT MEAN? Which documentation? From which package? Why does this reset my settings? Best regards, Eduard. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages os-prober depends on: ii grub-common 2.12~rc1-10 ii libc62.37-10 ii mount2.39.2-1 os-prober recommends no packages. os-prober suggests no packages. -- no debconf information -- * falky kann die Frauen einfach nicht verstehen Die Frau, das unbekannte Wesen. To boldy come where no man has come before?
Bug#929224: apt-cacher-ng, debootstrap and deb.debian.org combination fails
Hallo, * Sean Whitton [Wed, May 22 2019, 06:02:15PM]: > Hello Eduard, > > On Wed 22 May 2019 at 09:24PM +02, Eduard Bloch wrote: > > > Uhm, I suggest you do what it says and read the manual? > > I am not trying to use an https mirror. > > I don't know what's responsible for the attempt to use https, but I want > to use http://deb.debian.org/debian, and one of apt-cacher-ng, > debootstrap or the deb.debian.org service is blocking doing that. Sure you do, guess what "URL transformed to HTTPS due to an HSTS policy" is supposed to mean. --no-hsts Wget supports HSTS (HTTP Strict Transport Security, RFC 6797) by default. Use --no-hsts to make Wget act as a non-HSTS-compliant UA. As a consequence, Wget would ignore all the "Strict-Transport-Security" headers, and would not enforce any existing HSTS policy. Best regards, Eduard. -- Was gibt es denn für Alternativen zu file-roller? 100er Block Kästchenpapier und weicher Bleistift? frobnic: Ich wollte eigentlich keine Hardware-Lösung
Bug#929224: apt-cacher-ng, debootstrap and deb.debian.org combination fails
Hallo, * Sean Whitton [Sun, May 19 2019, 08:08:07AM]: > I thought that the problem is that apt-cacher-ng is not able to resolve > SRV records. However, I'm not so sure about that now. debootstrap uses > wget to download stuff, so I tried this: > > root@iris:/srv/chroot>http_proxy=http://localhost:3142 wget > http://deb.debian.org/debian/dists/sid/Release > URL transformed to HTTPS due to an HSTS policy > --2019-05-19 07:54:37-- https://deb.debian.org/debian/dists/sid/Release > Resolving localhost (localhost)... ::1, 127.0.0.1 > Connecting to localhost (localhost)|::1|:3142... connected. > Proxy tunneling failed: CONNECT denied (ask the admin to allow HTTPS > tunnels)Unable to establish SSL connection. Uhm, I suggest you do what it says and read the manual? https://www.unix-ag.uni-kl.de/~bloch/acng/html/howtos.html#ssluse The "laissez-faire method": in acng.conf (or related) configure the PassThroughPattern option to contain a regex like .* and configure the clients to use apt-cacher-ng as HTTP proxy and let the clients connect to https URLs "as usual". Some limited access control can be achieved through adjustment of the regular expression (.* permits access to any host and any port, including 443 for https). Data is not cached on the server. Also modified by debconf: dpkg-reconfigure -plow apt-cacher-ng Best regards, Eduard.
Bug#873923: installer not detecting/configuring existing LUKS/LVM setup
Package: debian-installer Severity: normal this is a follow-up to #873862 , see there for most details. So, the outcome is, when the installer fails with the problem mentioned there, I can still reboot the system. But then, the d-i is basically stuck at the same step. The LUKS partition is not displayed as LUKS or crypto but "unused". There is no way to tell it "this is crypto, unencrypt it only". The only sensible option in the usage types is apparently "PV for encryption". But then, nothing asks me for the password, instead it presents me a list of cryptsetup parameters. Hard to tell for a normal user whether it did detect LUKS or not. When I go to the main partman menu, there is the option "configure crypto volumes". But it does NOT configure the existing one. It only offers me the choice "create a new crypto volume" and "go back". This is pretty ... useless if I want to keep existing data. So apparently the d-i is inept to use the same device setup that it has created before or there is maybe no LUKS detection whatsoever? When I try to investigate later with Ubuntu Live, the file manager shows the encrypted volume and lets me unencrypt it with a a double-click and it even detects and scans the LVM and registers LVs there). It doesn't redisplay the discovered PVs in the filemanager, though, but I can mkfs and mount them manually. Regards, Eduard.
Bug#873857: Cannot use the screenshot button with keyboard
Package: debian-installer Severity: normal This is followup to #873854, see there for details. In the graphical installer, I am not able to access the "Screen picture" button in the bottom left corner with the KEYBOARD. When I use tab, the visible focus (i.e. the element with the rectangle somewhere) moves between the upper controls and the buttons in the bottom right corner, but apparently the picture button never gets focus. Regards, Eduard. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) -- GyrosGeier: We are Debian. You will be zicked. Resitance is futile.
Bug#763695: console-setup: even worse than assumed
Hallo, * Samuel Thibault [Wed, Aug 26 2015, 12:21:19AM]: > Eduard Bloch, le Wed 26 Aug 2015 00:11:10 +0200, a écrit : > > So... ok, maybe getting times from the log was a bad idea and causes > > exageration. > > Err, were you using strace for your whole timing of setupcon? It's no > wonder it takes so long in that case :) Well, during initial look at the strace log the overall execution time matched the value systemd-analyze chart very well (both indicated ~5s for the whole process) and I didn't bother to cross-check. Regards, Eduard. -- Ah. Frankfurt/Main. * weasel fragt sich ja immer, ob's auch ein Frankfurt/Contrib und Frankfurt/Non-Free gibt signature.asc Description: Digital signature
Bug#763695: console-setup: even worse than assumed
Hallo, * Samuel Thibault [Tue, Aug 25 2015, 10:52:29PM]: > Eduard Bloch, le Tue 25 Aug 2015 22:34:17 +0200, a écrit : > > Hallo, > > * Samuel Thibault [Tue, Aug 25 2015, 09:56:39PM]: > > > Eduard Bloch, le Tue 25 Aug 2015 21:35:36 +0200, a écrit : > > > > * Samuel Thibault [Tue, Aug 25 2015, 08:54:35PM]: > > > > > Just so that people reading the log don't take it too exagerated: > > > > > > > > > Eduard Bloch, le Tue 25 Aug 2015 20:24:22 +0200, a écrit : > > > > > > I checked again... about 20% of the time is spent in two calls of > > > > > > pidof > > > > > > > > > > We're here talking about ~15ms each. > > > > > > > > I don't. It's ~270ms each (I added another log with timestamps). > > > > > > How long is the readlink /proc/*/exe | grep? > > > > ~70ms (strace -f -tt -o logfile sh -c 'readlink /proc/*/exe | fgrep slash') > > strace is quite expensive, better use just Oh, you are right. I didn't expect that impact. Without strace, pidof takes ~22ms on this laptop. OTOH same with sh "readlink...|grep" also needs about ~10ms. So... ok, maybe getting times from the log was a bad idea and causes exageration. > time (readlink /proc/*/exe | fgrep slash) > > But that's already a big improvement, I'm surprised that pidof can be so > expensive. Mea culpa; pidof probably creates lots of work for strace because of the many "IO" operations on /proc. Sorry... Regards, Eduard.
Bug#763695: console-setup: even worse than assumed
Hallo, * Samuel Thibault [Tue, Aug 25 2015, 09:56:39PM]: > Eduard Bloch, le Tue 25 Aug 2015 21:35:36 +0200, a écrit : > > * Samuel Thibault [Tue, Aug 25 2015, 08:54:35PM]: > > > Just so that people reading the log don't take it too exagerated: > > > > > Eduard Bloch, le Tue 25 Aug 2015 20:24:22 +0200, a écrit : > > > > I checked again... about 20% of the time is spent in two calls of pidof > > > > > > We're here talking about ~15ms each. > > > > I don't. It's ~270ms each (I added another log with timestamps). > > How long is the readlink /proc/*/exe | grep? ~70ms (strace -f -tt -o logfile sh -c 'readlink /proc/*/exe | fgrep slash') > > > > And about 70% is spent by loadkeys executing the mentioned storm of > > > > ioctls. > > > > > > And about 70ms. > > > > Or ~1.8s on the mentioned device. > > Ouch. The optimization I mentioned could perhaps reduce that, in a not > too complex setup (shift, alt, control, altgr, capslock modifiers) by a > 4x factor. To go further a kernel patch is really needed, there is no > way around it. Ok, thanks for investigation. Regards, Eduard.
Bug#763695: console-setup: even worse than assumed
Hallo, * Samuel Thibault [Tue, Aug 25 2015, 08:54:35PM]: > Just so that people reading the log don't take it too exagerated: > Eduard Bloch, le Tue 25 Aug 2015 20:24:22 +0200, a écrit : > > I checked again... about 20% of the time is spent in two calls of pidof > > We're here talking about ~15ms each. I don't. It's ~270ms each (I added another log with timestamps). It might be true for a shiny Core-i7 system. But a low-end laptop like the mentioned one is a different league. OTOH it's just one year old and manages to boot in ~1min. Wasting 5-10% of the boot time just for keyboard/console setup is ridiculous. > > And about 70% is spent by loadkeys executing the mentioned storm of ioctls. > > And about 70ms. Or ~1.8s on the mentioned device. Even on my not-so-lame desktop (Phenom II 3.2ghz) setupcon needs almost 1.7s. That is WAY too much, IMHO. Regards, Eduard.
Bug#763695: console-setup: even worse than assumed
Hallo, * Anton Zinoviev [Mon, Aug 24 2015, 01:24:15PM]: > On Sun, Aug 23, 2015 at 02:02:30AM +0200, Cyril Brulebois wrote: > > > > > $ grep ioctl log | wc -l > > > 14035 > > > OVER 9000 ioctls! Are you kidding me? > > Console-setup is definitely not THAT slow. It is. Kind of. I checked again... about 20% of the time is spent in two calls of pidof which IMHO on Linux can be easily replaced with ONE simple readlink /proc/*/exe | grep bin/.?splashy? And about 70% is spent by loadkeys executing the mentioned storm of ioctls. > Unless your directory /etc/console-setup/ doesn't contain a cached keymap It's there. Just look at the strace log I mentioned before, here: https://www.unix-ag.uni-kl.de/~bloch/.wearetheborg/strace-log-setupcon.xz > in which case ckbcomp has to be invoked. And yes - AFAICS no call of ckbcomp there. Regards, Eduard.
Bug#763695: console-setup: even worse than assumed
Package: console-setup Version: 1.132 Followup-For: Bug #763695 Dear Maintainer, inspired by the recent talk about systemd utilities I analyzed my boot process on my lower-level laptop (CPU is ok but the harddisk is plain old mechanic thing). And it's even worse than in jak's original report, it spends 5s there and the HDD seems to be pretty busy. Just have a look at it: https://www.unix-ag.uni-kl.de/~bloch/.wearetheborg/ $ wc -l log 23053 log $ grep ioctl log | wc -l 14035 OVER 9000 ioctls! Are you kidding me? $ grep 'open\|read\|stat' log | wc -l 3881 OVER 3000 filesystem related syscalls. That all is needed to just configure the console? Seriously? Please find a way to cut down this activity, there must be a way to do that. Regards, Eduard. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.5+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages console-setup depends on: ii console-setup-linux 1.132 ii debconf 1.5.57 ii keyboard-configuration 1.132 ii xkb-data2.14-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.19-19 ii lsb-base 4.1+Debian14 Versions of packages keyboard-configuration depends on: ii debconf 1.5.57 ii initscripts 2.88dsf-59 ii liblocale-gettext-perl 1.05-9 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.132 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: * keyboard-configuration/ctrl_alt_bksp: true console-setup/fontsize-text47: 8x14 * keyboard-configuration/variantcode: console-setup/charmap47: UTF-8 * keyboard-configuration/modelcode: pc105 keyboard-configuration/unsupported_options: true * keyboard-configuration/layout: console-setup/fontsize: 8x14 console-setup/use_system_font: * keyboard-configuration/layoutcode: de * keyboard-configuration/store_defaults_in_debconf_db: true console-setup/framebuffer_only: * keyboard-configuration/toggle: No toggling * keyboard-configuration/variant: Deutsch * keyboard-configuration/xkb-keymap: de * console-setup/fontsize-fb47: 8x14 * keyboard-configuration/compose: No compose key * keyboard-configuration/other: console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/store_defaults_in_debconf_db: true keyboard-configuration/unsupported_config_options: true * keyboard-configuration/altgr: The default for the keyboard layout debian-installer/console-setup-udeb/title: * console-setup/fontface47: Fixed console-setup/guess_font: * keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) keyboard-configuration/unsupported_layout: true * keyboard-configuration/optionscode: terminate:ctrl_alt_bksp * keyboard-configuration/switch: No temporary switch keyboard-configuration/unsupported_config_layout: true console-setup/codesetcode: Lat15
Re: Processed: dealing with old installation-reports
reassign 642159 thanks * Debian Bug Tracking System [Sat, Jul 20 2013, 01:21:16PM]: > > reassign 642159 apt-cacher-ng > Bug #642159 [debian-installer] debian-installer preseed broken with > apt-cacher-ng mirror > Bug reassigned from package 'debian-installer' to 'apt-cacher-ng'. > No longer marked as found in versions debian-installer/20110106+squeeze3. > Ignoring request to alter fixed versions of bug #642159 to the same values > previously set No, please don't reassign this to me because I have no idea whether and when this bug was fixed. In case you missed the main part of this bug report, here it is: > Instead when I run applications from the Kickstart %post section, all HTTP > connections are proxied; curl, wget, lynx, hg (mercurial), everything. Once > the system installs and reboots all is good, the only remanence of the > mirror/http/proxy setting is in /etc/apt/apt.conf, which is fine (though I > think that should be configurable too). mirror/http/proxy is setting the > environment variable http_proxy. Which means: you cheat with the environment, breaking unrelated programs. Not the finest art. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130720221808.ga6...@rotes76.wohnheim.uni-kl.de
Bug#590507: please allow proxy specification without http:// prefix
Package: debian-installer Version: http://d-i.debian.org/daily-images/kfreebsd-amd64/20100726-10:40/ Severity: wishlist Hello, the subject says it all. I would like to quickly enter "10.1.2.3:1234" without the http:// prefix. Because the question is about http proxy anyway, the installer could append http:// internally if it was not specified by user. Regards, Eduard. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-rc4 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100726213957.ga24...@rotes76.wohnheim.uni-kl.de
Re: removal of svenl from the project
#include * Andres Salomon [Tue, Mar 14 2006, 09:01:09PM]: > harm upon another developer in a public forum, and then a week later > publically insults/taunts a developer (one of the Release Managers, > even), behind his back. This is incredibly childish, aggressive > behavior, and should not be tolerated within the project (IMO). He were slandering somebody and others were listening/reading without telling him that the behaviour is impolite? Well, then maybe it shows us all (or at least the readers) in a bad light. Even then, you have to deal with such offence in a more contructive way, definitely not by stupid expulsion process. Heck, even our current DPL may not be there if I would have acted like you few years ago (I did not forget comments like "Ah, Eduard Bloch joined the club of debian-legal experts, hahaha" and similar stupid rants found in IRC logs but, hey, people can change, and people can learn, and kicking someone out without giving at least one second chance is equally childish). And if I would have acted like a hot potato, I would have gone the path of Adrian Bunk at the time. Eduard. -- Auf ähnlichem Niveau bewegen sich die Gehältern von Webdesignern, die ebenfalls zu den Verlierern unter den *Informatikern* zählen. -- Unispiegel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#265183: pppoe workaround of the post-reboot problem
#include * Vassilii Khachaturov [Mon, Sep 20 2004, 11:51:31AM]: > > PS: I won't clone 265183, there are already enough bug reports to the > > pppoe module problem. > > But what about the routing loop problem I had mentioned in the original > 265183 report? It is something pretty confusing for a new user. Which loop? I do not know why your modem has an own IP, maybe it is a router and not a modem? Why does it give your local systems DHCP adresses? How are they related to whatever is connected there? Or maybe it is not a usual PPPoE modem but this other weird ip-route-over-fake-internal-network-with-dhcp-over-DSL system (*). Or what t.f. is a "LAN duplex link"? Does not say anything to me. Maybe a phantasy name from your ISP? If yes, what is in the real world terms? Regards, Eduard. PS: (*) I am still looking for somebody to explain me how this "technology" works and can provide a reliable step-for-step howto to add support for it to pppoeconf. Or even patches. From time to time people asked me to add support for their "DHCP DSL" but for real support more is needed. -- So, your "solution" is to ask "Should I break your system now or after the next reboot?". Debconf is not an alternative to fixing the problem. Such questions are still unacceptable bugs. -- asuffield in debian-devel about crazy linux-2.4 repackaging -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#272209: the dhcp progress bar could have a button to skip
Package: debian-installer Severity: wishlist Hello, when I install ubuntu in its default JohnDoe-user mode, I always have to see this DHCP lookup dialog. It needs too long. I wish there would be a button "skip" below the progress bar to stop searching and specify the network data later. Regards, Eduard. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8.1 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#265183: pppoe workaround of the post-reboot problem
severity 263224 serious reassign 262941 modutils severity 262941 serious merge 262941 263224 thanks #include * Vassilii Khachaturov [Fri, Aug 13 2004, 08:50:58AM]: > The thing that happens as a by-product of pppoeconf that enables the > pppoe to work later on is the loading of the pppoe module. So to have > pppoe working after reboot, `modprobe pppoe' is needed before `pon > dsl-provider'. I think pppoeconf should have done something differently > transparent to the user. FWIW, here's the /etc/ppp/peers/dsl-provider it > had generated. See this also in connection with the routing quirk > described in the original report (that had to be worked around with the > assigning of a static address). > > Eduard: please feel free to fork #265183 to pppoeconf bugs (on the As said to the previous bug reporters, it is simply not my job to load _kernel_ modules for some other package. It would just additional complexity while there are other places where it must be fixed. I agree that this bug looks very shameful for a fresh Debian release so it should be release critical. Especially when there is such a simple fix. PS: I won't clone 265183, there are already enough bug reports to the pppoe module problem. Regards, Eduard. -- OpenBSD fails miserably in this respect, and makes for an example of how NOT to work with the community on security issues. Their approach is, roughly, "we fixed this a while ago but didn't tell anyone, so you're vulnerable and we're not, ha-ha-ha". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264375: apt-setup does no save choosen cdrom device anyhwere
Package: base-config Version: 2.40 Severity: normal Hello, as a Joe user, I tried to install Sarge having a small netinst CD in the first drive and a few weeks old Sarge DVD in the second. In the second phase with apt-setup, I was asked to specify the device where apt should locate the media. Since the netinst CD was ejected (for reboot), I specified /dev/hdb. But this setting is not stored anwhere! When the sources are choosed, I see the prompt requesting me to insert the DVD called "Sarge..." to the drive "/cdrom". But it is not very understandable (it should say: "The drive that belongs to /path") AND it does not know which CD has been choose. APT stupidly accepts /dev/cdrom (hda) as /cdrom, though I have explicitely choosen to use /dev/sdb few seconds ago. This is uncomfortable and may be confusing. Especially since it is not clear at all how to EXIT from this prompt. There is no word about Ctrl-C or any other solution, this interaction mode looks just stupid and not userfriendly. Regards, Eduard. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 Versions of packages base-config depends on: ii adduser 3.59 Add and remove users and groups ii apt 0.5.27 Advanced front-end for dpkg ii bsdutils1:2.12-7 Basic utilities from 4.4BSD-Lite ii console-data2002.12.04dbs-44 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-55Linux console and font utilities ii debconf 1.4.30 Debian configuration management sy ii debianutils 2.8.4Miscellaneous utilities specific t ii gettext-base0.14.1-5 GNU Internationalization utilities ii passwd 1:4.0.3-30 Change and administer password and -- debconf information: tzconfig/choose_country_zone_single: true tzconfig/select_zone: tzconfig/verify_choices: * apt-setup/another: false base-config/start-display-manager: true apt-setup/directory: /debian/ base-config/menu/hostname: * apt-setup/cd/another: false apt-setup/badedit: mirror/suite: testing apt-setup/baddir: base-config/menu/pkgsel: base-config/menu/apt-get: base-config/menu/timezone: apt-setup/hostname: ftp2.de.debian.org base-config/menu/pon: * tzconfig/gmt: false apt-setup/title: mirror/http/proxy: * apt-setup/contrib: true apt-setup/non-us-failed: * tzconfig/geographic_area: Europe apt-setup/cd/dev: /dev/cdrom * apt-setup/country: Germany apt-setup/uri_type: http apt-setup/not-mirror: base-config/retry-ppp: true apt-setup/security-updates-failed: * apt-setup/cd/bad: base-config/menu/mta: tzconfig/choose_country_zone/BR: East * base-config/intro: * tzconfig/select_zone/Europe: Berlin * apt-setup/security-updates: true * base-config/run-tasksel: true mirror/distribution: base-config/title: base-config/menu/finish: base-config/stop-ppp: true debian-installer/language: * apt-setup/mirror: ftp2.de.debian.org base-config/menu/apt-setup: base-config/menu/keyboard: tzconfig/title: debian-installer/country: base-config/install-problem: true tzconfig/change_timezone: false * base-config/pkgsel: dselect - old package selector (experts only) * apt-setup/non-free: true * apt-setup/non-us: true base-config/menu/intro: base-config/menu/passwd: base-config/login: base-config/main-menu: * base-config/run-dselect: false debian-installer/keymap: base-config/remove-pcmcia: true apt-setup/badsource: * base-config/use-ppp: false tzconfig/choose_country_zone/US: Eastern base-config/get-hostname: tzconfig/choose_country_zone_multiple: tzconfig/choose_country_zone/CA: Eastern * base-config/login-with-tty: base-config/menu/shell: base-config/invalid-hostname: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#202907: Processed: language tasks pull in reams of huge packages
#include * Debian Bug Tracking System [Thu, Jul 29 2004, 11:03:04PM]: > Processing commands for [EMAIL PROTECTED]: > > > reopen 202907 > Bug#202907: language tasks pull in reams of huge packages Haha. Now you stumble around the problem that I have predicted years ago, requesting "conditional dependencies" in dpkg. Either this or another apt-get extension implementing basicaly the same feature. IMO the only good way to manage such things. Package: spanish-lang-packs Depends: openoffice.org -> openoffice.org-l10n-es, kdebase -> kde-i18n-es, ... Eduard. -- 23 bans ... die Illuminaten waren hier .oO( /kb ace lueg nicht, 24 ) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pppoe install
Moin Jan! Jan Schukat schrieb am Tuesday, den 08. June 2004: > Yesterday (June 7) I downloaded the sarge-i386-netinst.iso and installed the > base system on my new VIA CL9000 board for soon to become my DSL Router. > Now, after the first reboot, I set up root and normal user and then the ppp > configuration script starts. Well, I need pppoe with my Teledat 300 LAN. So > I changed the console and stated pppoeconf. Works fine, and I even get a > connection to my provider (plog confirms this and the received dynamic DNS > IPs). But nothing else to the outside works. I cannot even ping to any > outside IP. So either I'm completely stupid, or something pretty weird is > going on. Check your default route setting. If there is one (gateway in /etc/network/interfaces), remove it, it confuses ppp. Regards, Eduard. -- susn: koffice ist ein proof-of-concept, aber praktisch nicht wirklich nutzbar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#235068: modconf: FTBFS: Cannot find unpacked kernel source
severity 235068 important thanks > E: Package kernel-source has no installation candidate > -> Considering kernel-source-2.2.25 to satisfy the dependency Oha. > I'd suggest using a more specific kernel-source Build-Depends like > kernel-source-2.4 or kernel-source-2.4.24. Also, the kernel-source > packages only include the tar.bz2 files, while a look at > debian/mkkerneldesc.pl indicates it expects to find unpacked trees. As many other debian-boot products, this requires a human operator to get the build done. In this case it could be automated though, and if someone has the motivation to fix it, please do. Eduard. -- Ideen sind wie Kinder: Die eigenen liebt man am meisten. -- Lothar Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#227691: Really serious?
#include * Thomas Hood [Mon, Feb 09 2004, 12:11:42AM]: > Eduard Bloch wrote: > > severity 227691 serious > > thanks > > [...] > > Something that must be fixed before the Sarge release. > > Do you think that this bug is so severe that if it is not fixed then > the package had better not be released with Sarge? Yes. And I think someone will fix it, I won't now (no time). > If so then the severity should be "grave", not "serious". Wrong. "serious" is also the severity for deliberate package freezes in Sid. MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#231634: modconf dialog has broken text
retitle 231634 yesno box does not wrap text lines severity 231634 grave severity 224333 grave reassign 224333 whiptail reassign 231634 whiptail merge 231634 224333 thanks -- Seid realistisch - fordert das Unmögliche. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#227691: modconf: I can't enter in kernel/drivers/net section
severity 227691 serious thanks #include * willy [Wed, Jan 14 2004, 12:36:24PM]: > Package: modconf > Version: 0.2.45 > Severity: important > > If i try to select kernel/drivers/net modules section it return > to modules section main list. > I can't choose net modules. Something that must be fixed before the Sarge release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fixed in NMU of modconf 0.2.45
tag 174833 + fixed tag 192232 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 26 Dec 2003 17:06:43 +0100 Source: modconf Binary: modconf Architecture: source all Version: 0.2.45 Distribution: unstable Urgency: low Maintainer: Boot Floppies Team <[EMAIL PROTECTED]> Changed-By: Eduard Bloch <[EMAIL PROTECTED]> Description: modconf- Device Driver Configuration Closes: 174833 192232 Changes: modconf (0.2.45) unstable; urgency=low . * Kernel 2.6 support based on the latest patch in the bugreport, thanks to all submitters (closes: #192232) * new 2.6 compatible description harvesting method for mkkerneldesc.pl * Makefile cleanups: generic manpage installation rule, no duplicated mkkerneldesc.pl executions * added French manpage, thanks to Julien Louis (closes: #174833) Files: 8fd89f903d756e3e2c7a2bc194b0a1f9 528 base optional modconf_0.2.45.dsc 088d2e33faf3d2de5bc63e3fa5d209f1 153315 base optional modconf_0.2.45.tar.gz 5ed7c92fbb7531cbf7d8c13ef0af57b8 759644 base optional modconf_0.2.45_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/7Jcn4QZIHu3wCMURAg8RAKCHuwJVrpAd7SLXOmC1fPkqIxNq9QCaA3p1 aRxJLHfLx2zBuDUrD5WhHvw= =CxrQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#221266: 'images-1.44/rescue.bin bug
Moin Goswin! Goswin von Brederlow schrieb am Monday, den 17. November 2003: > "Tarun Kundhi" <[EMAIL PROTECTED]> writes: > > > > > > > > > Message > ... > > It would realy help if you could write a mail in english text instead > of publishing a website. He has done both. Get a MUA which can handle Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit SCNR, Eduard. -- Warum überquerte das Huhn die Straße? Albert Einstein: Ob das Huhn die Straße überquert hat oder die Straße sich unter dem Huhn bewegte, hängt von Ihrem Referenzrahmen ab. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#209301: modconf: on module installation failure, suggest isa-pnp.o to the user
#include * Ryan Underwood [Mon, Sep 15 2003, 02:55:37AM]: > > > Please refer to linux/Documentation/isapnp.txt: > > > > > > Write commands: > > > --- > > > > > > With the write interface you can activate or modify the configuration of > > > ISA Plug & Play devices. It is mainly useful for drivers which have not > > > been rewritten to use the ISA Plug & Play kernel support yet. > > > > Sorry, what is your point? > > Please go outside and get some fresh air. For your own good. I just have been there. > > First, you tell us that isa-pnp module configures the cards when > > loaded. Now, you show a way to *configure the ressources manually* via > > the proc interface. > > No, I didn't say that. (Please quote me instead of paraphrasing.) You did imply that. |After a module fails initialization, the suggestion should be made that |the user install the isa-pnp module if the hardware in question is an |ISA-PnP card. | |"The module failed initialization. Check the hardware resources (I/O, |IRQ) and if the card is a ISA PnP card, ensure that you have installed |the isa-pnp module first." And I have just told you that loading isa-pnp is not enough. The only practicable think I can imagine is extending this message to a micro-Howto about how to use isapnptools or the isa-pnp's proc interface. Both things that user can learn from RTFM before going to install. Another idea may be silent loading of isa-pnp when available and including the list of the devices in the message, suggesting how to continue. > My contention is that without isa-pnp loaded, the user could not use > modules that do not support ISA-PnP configuration themselves when the > card is not in a configured state. In the case of a new user, they see isa-pnp does not configure them when the module is just loaded. > only a failure when inserting the module for their hardware which is > clearly installed in the system, and have no idea where to proceed. The general hint is _okay_ but the advisory to load isa-pnp is not okay in the suggested form, and will confuse the user more to the end. > > Just for the case that you missed it, we do already include > > isapnptools for pre-2.4 kernels. And pnpdump&isapnp are a way more > > user-friendly and better documented than the proc interface. > > The user was installing from bf2.4. Is isapnptools included in that > case? If so, then this "wishlist" bug is in error and you may ignore It is not included. For the simple reason, I could not find a driver for any _essential (for installation)_ ISA PnP card that is not supported by isapnp manegement in 2.4.18. > it. If it is not, then I stand by my statement that there must be a > documented way for the user to configure the ISA-PnP cards, or there is > a good chance of significant confusion occurring during an installation. I am not the only modconf maintainer but I won't do much more on that because of the reasons described above and because I think that there is enough documentation around. But patches are welcome, there are surely ways to improve the failure message. MfG, Eduauard. -- Sich selbst darf man nicht für so göttlich halten, daß man seine eigenen Werke nicht gelegentlich verbessern könnte. -- Ludwig van Beethoven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#209301: modconf: on module installation failure, suggest isa-pnp.o to the user
#include * Ryan Underwood [Sun, Sep 14 2003, 10:27:40PM]: > > > If the module itself is aware of isa-pnp, then yes, this is the case. > > > However, consider this scenario: The card is a PnP card, the driver is > > > not PnP aware and would like to know the I/O and IRQ resources when > > > loaded. The card must first be configured by loading isa-pnp, and then > > > the other driver can be loaded based on the resources that the card is > > > assigned. > > > > Nonsense, pure nonsence. Please read the isapnp_init function of isapnp.c > > before claiming such thing. Then show me the place where random cards > > are configured to random ressources by isa-pnp and the users gets > > information about the ressources. > > Please refer to linux/Documentation/isapnp.txt: > > Write commands: > --- > > With the write interface you can activate or modify the configuration of > ISA Plug & Play devices. It is mainly useful for drivers which have not > been rewritten to use the ISA Plug & Play kernel support yet. Sorry, what is your point? First, you tell us that isa-pnp module configures the cards when loaded. Now, you show a way to *configure the ressources manually* via the proc interface. Just for the case that you missed it, we do already include isapnptools for pre-2.4 kernels. And pnpdump&isapnp are a way more user-friendly and better documented than the proc interface. MfG, Eduard. -- In der Mitte von Schwierigkeiten liegen die Möglichkeiten. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#209301: modconf: on module installation failure, suggest isa-pnp.o to the user
#include * Ryan Underwood [Fri, Sep 12 2003, 10:21:21PM]: > > Short answer: use precompiled kernels if you cannot do it properly in > > your own. If you build the isa-pnp module with the kernel, the created > > modules (ISA drivers) will depend on it and autoload when needed. > > I'm not sure what you are talking about. I am referring specifically > about when modconf is called during Debian installation. The new user Me too. Modconf used modprobe, modprobe looks on on modules.dep, the particular module (_if_ it works together with isa-pnp) needs isa-pnp so modprobe loads isa-pnp. Your scenario can only appear if you have a mix of modules from different kernel builds. > may have no idea that he or she needs to insert the isa-pnp module > to configure the PnP cards, before inserting the driver modules for the (s)he does not have to. When you see a such problem, examine modules.dep and file a bug report against your kernel. > In my opinion, this is a bug because modconf, an "easy to use" frontend, > is failing to inform the user of a step they may have forgotten to take It does sometimes, eg. for USB keyboards. For other things, we rely on module dependencies. > if they are unfamiliar with the system. I posted this bug on behalf of > a frustrated user who wasted many hours with an (unknown to him) > unconfigured ISA PnP card. As said before, isa-pnp is loaded when the kernel has been built with the isa-pnp module. If the particular driver does _not_ communicate with the isa-pnp module, loading it would not help anyways. MfG, Eduard. -- Das Alter hat auch gesundheitliche Vorteile: Zum Beispiel verschüttet man ziemlich viel von dem Alkohol, den man trinken möchte. -- André Gide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network card driver not found - bf24
#include * Uwe Dippel [Mon, Sep 01 2003, 11:33:12AM]: > A minor hitch: > While installing 3.0rc1 as default (Enter) on a DELL Inspiron 8100, the > NIC-module (3c59x.o) is found and installed automatically. > With bf24, it isn't. It requires manual intervention (and knowledge > about the module) to install. And that is the normal way to go. Boot-floppies in Woody did not have hardware autodetection. > I doubt a 2.4-kernel issue, because RedHat 7.3 installs flawlessly as > well. They use modularized kernel with autodetection. MfG, Eduard. -- BMW - Bei Mercedes Weggeworfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#206616: modconf: too wide for 80-column console
reassign 206616 whiptail thanks Moin Thomas! Thomas Koenig schrieb am Thursday, den 21. August 2003: > Package: modconf > Version: 0.2.44 > Severity: important > > I just ran modconf from a virtual console, and was confused when > I saw all module paths start with "/drivers". Here's what it > looks like: > > ??? Select Category > Modules are loadable device drivers. Please go through the menus > for each category and look for devices, network protocols, filesystems, > etc. that you would like to have supported by your system. You should > not install modules for devices that aren't installed in your system, > as they will sometimes cause the system to pause for a long time while > it is searching for the device. Also, drivers for devices that you > don't have use memory that you could put to better use. > > Please select the category of modules. > > Finished. Return to previous menu. > > /drivers/bluetooth. > /drivers/acpi . > /drivers/acpi/ospm/ac_adapter . > /drivers/acpi/ospm/battery. > /drivers/acpi/ospm/busmgr . > > > > ? ? > > > This may be also be a whiptail bug, or it may be due to the interaction > of whiptail and modconf. > > -- System Information: > Debian Release: testing/unstable > Architecture: i386 > Kernel: Linux meiner 2.4.20-3-k7 #1 Sun Jul 27 21:10:39 EST 2003 i686 > Locale: LANG=C, [EMAIL PROTECTED] > > Versions of packages modconf depends on: > ii modutils 2.4.21-3 Linux module utilities > ii whiptail [whiptail-provider] 0.51.4-15 Displays user-friendly dialog boxe > > -- no debconf information > > > > -- Phantasie ist wichtiger als Wissen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#205519: installation: Wrong error message when disk is full
severity 205519 minor tags 205519 + wontfix thanks #include * Michiel Holtkamp [Fri, Aug 15 2003, 09:47:19AM]: > Package: installation > Version: unavailable; reported 2003-08-15 > Severity: important > > When a partition is too small to install everything on, and packages are > unpacked to the harddisk, the install menu will fail with an error message: > "package corrupt" or similar. After checking debug messages on console 3 (I > think) it becomes clear that the disk is full. > > Thus the error messages the user receives is misleading. Install should not > assume that a package is corrupt because unpacking fails. I'm not sure how > the internals work in this case, but I'm sure somebody knows :) But I do a bit and if you are too lazy for RTFM, noone can help you. MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot.iso
#include * jayson [Tue, Aug 12 2003, 03:05:08PM]: > from http://people.debian.org/~dwhedon/boot-floppies/ > when i try to install, it boots, i press enter at the prompt then it says > keyboard: timeout - at keyboard not present? > > it is a ps2 keyboard and it obviously works if i pressed enter seconds > before.. The problem is known with some x86 hardware and kernel 2.2.x. Try the other install image with kernel 2.4 instead. MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i debcamp in Oldenburg 2003-09-25 to 2003-09-28
Moin Petter! Petter Reinholdtsen schrieb am Sunday, den 10. August 2003: > I've noted interest from the following people: > > Michael Cardenas - San Diego, USA > Joey Hess - Bristol, TN, USA > Tollef Fog Heen - Trondheim, Norway > Falk Hueffner - Tuebingen, Germany > Matt Kraai - Los Angeles, USA > Sebastian Ley - Aachen, Germany > Alastair McKinstry - Dublin, Ireland > Petter Reinholdtsen - Oslo, Norway > Giuseppe Sacco - Turin, Italy. > Thorsten Sauter - Stuttgart, Germany > Martin Sjögren - Göteborg, Sweden > Gaudenz Steinlin - Bern, Switzerland > Thomas Viehmann - ? Eduard Bloch - Karlsruhe, Germany Eduard. -- So einfach wie möglich, aber nicht einfacher! -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Status of aic79xx driver
#include * [EMAIL PROTECTED] [Tue, Aug 05 2003, 10:49:34PM]: > I have recently bought a fine server running 3 raid disks on an Adaptec > 39320D SCSI card. This card is supported by the Linux aic79xx driver > (the old one aic7xxx does not work). > ==> Is there someone out there who has a compiled module driver that > can stick on a module floppy to load the driver during installation? I guess you do not have a source package which does not depend on a certain kernel source three? I hear rumors again good/bad aic79xx driver, but either people point me to some Adaptec driver source which is meant to replace the kernel dir, or to some another source which relies on newer kernel versions or seems to rely on 2.4.20 but still does not build with them, then there is another story about working aic79xx driver in 2.4.21 (which AFAICS won't go into boot-floppies) but others said that it is not recent enough for the latest models and you some hacker patch to make it work. So could anyone bringt light into this issue and summarize all the information about this weird Adaptec product and Linux support issues? MfG, Eduard. -- Was hat denn der Gast von Tisch drei ins Beschwerdebuch geschrieben? Gar nichts, er hat das Schnitzel eingeklebt. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ITP shell-parted and debconf-partitioner
#include * Thorsten Sauter [Thu, Jul 31 2003, 10:50:12PM]: > | It would perhaps be a good idea to integrate partitioner and > | partconf, if this succeeds... > > I'm not sure, that this is the best solution. > If you would like to merge both programs, then we also need support for > lvm and raid in this program. And this makes the whole d-i concept > useless. After the merge you can't simply extend the d-i with new The whole d-i concept is useless when it comes to extensions that are outside of the default mkfs-install-bootconfig path. Whatever we will use, an "advanced" partitioner will be much more complicated than the simple question-repsonse scheme of debconf. I suggest keeping the default tools for text mode (cfdisk or shell with fdisk, lvm-tools, mdadm, evms-utils) and a nice partitioner for GUI mode only. Of course when some volumes are already prepared on the target system, we can use usual methods to autodetect them (mdrun, ?lvmstart?, evms by default) and make them useable for partconf, but every other development in TUI mode is IMO just not feasible, given the short time period for the Sarge release. MfG, Eduard. -- Verheiratete Männer leben länger als unverheiratete, aber sie sind viel eher bereit zu sterben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#191636: fix to this bug.
#include * Alastair McKinstry [Sun, Jul 27 2003, 02:26:46PM]: > As the maintainer of whiptail, I was not aware of this bug, which was > filed against modconf. In the current newt package, whiptail and > whiptail-utf8 were merged; modconf seems to work fine for me now. > > (There are some minor graphical issues in utf-8 mode, due to an error in > slang, for which a patch as been submitted; see eg. 195010). > > Could you please retest modconf against the latest whiptail, 0.51.4-8; > and if either confirm the bug or close it? Still broken. With LANG=de_DE.UTF-8, semi-graphical chars are not displayed correctly, example attached. > Incidentally, there appear to be a large number of bugs filed against > slang / slang-utf8 that I believe to be fixed by recent uploads. I may > help go through those and close some. The bug report that Junichi requested is: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201767 MfG, Eduard. -- nobse: du kannst gerne http://wwwbrauer.informatik.tu-muenchen.de/ praktikum/verifikation/WS2001-2002/p244-clarke.pdf fuer mich durcharbeiten, wenn dir langweilig ist weasel: iieh, ein pdf nobse soll ich es dir nach DOC konvertieren? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#191636: fix to this bug.
#include * Junichi Uekawa [Sun, Jul 27 2003, 08:15:22AM]: > tags 191636 + patch > thanks > > > Hi, > > whiptail-utf8 has now become 'whiptail', and so modconf can > just conflict with older versions of whiptail > > Conflicts: whiptail (<< 0.51.4-1) I am not sure, current whiptail looks completely broken, in UTF-8 mode as well as with non-UTF-8 locales. If the maintainer does not even manage to reply to my bug report, I guess we will have to go back and fork a working whiptail-utf8 again. Just my 0.02€, still hadn't time to get a close look on the problem. MfG, Eduard. -- isga: versuch mal 'apt-cache search girl friend' :-) du wirst überrascht sein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: aic79xx
#include * Petter Reinholdtsen [Fri, Jul 25 2003, 10:22:21AM]: > I believe this driver first appeared in kernel 2.4.21, so it will be > available when d-i moves from kernel 2.4.20 to 2.4.21. This > transition was delayed when we discovered that the new kernel was a > lot bigger then the currently used kernel. Same story with BF. I did try to make a 2.4.21 version for the LinuxTag-CDs, but there were a problem with size and unknown compatibility. > Rumors claimed the kernel would become smaller if another gcc version > is used to compile. I'm not sure if this is true. I tried different compilers and different flags, and all builds were much larger. Finally, some things like nfs support hat to go, but the result was still not acceptable. -Os saved few kilobytes. gcc-2.95 produced the smallest code but failed to build a driver (IIRC I had to drop a driver to work around it), gcc-3.2 a bit larger (not significantly, but it's not available on Woody), while gcc-3.0 code was about 80kB larger. Another issue is the IDE code stability. I have been told bad things about it, and could reproduce a hard crash/reboot with enabled DMA (ATAPI writes on ServerWorks chipset). Let's hope that 2.4.22 will be better. MfG, Eduard. -- susn: koffice ist ein proof-of-concept, aber praktisch nicht wirklich nutzbar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Support for Linux Driver for the Pro/1000 MT NIC -- Debian bf2.4 Woody -- Dell Optiplex 260
#include * Basab Maulik [Sat, Jul 19 2003, 06:46:22PM]: > ifconfig eth0 xx:xx:xx:xx netmask 255.255.252.0 up > > I am getting a segmentation fault and message of trying to dereference a > null pointer. > Also: > SIOCSIFADDR: No buffer space available > > Please help. Similar problems/issues with the 4.3.15 driver. Also any Try the kernel-image-2.4.20-bf2.4 kernel package from the pool (woody-proposed-updates). This will have the e1000 driver. MfG, Eduard. -- woran erkenn ich denn, dass ich ein 80-adriges Kabel drin habe? hm... indem du jede ader zählst? und wenn du bei 40 in der mitte bist, brauchst du nichtmehr weiterzählen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Freeze after startup with bf24
#include * Jeremy Hankins [Thu, Jul 17 2003, 12:19:46PM]: > Just thought I'd ask to see if anyone knew why it was freezing like > that and save myself a bit of work. I'm just hoping it's a > boot-floppies issue and not a kernel issue, so I can install 2.4 on it It sounds like a kernel issue, with borken hardware. You may try to disable framebuffer, see boot screens. Background: when the first screen appears and fb is enabled, the installer looks for translation catalogs on CDROM drives. Maybe some of your CD drives is broken, or the kernel freezes because of broken IDE driver or chipset, or whatever. As said, it's a DELL, you can never be sure when such things appear there. MfG, Eduard. -- bobby locales einstellen <_Bobby> ? dpkg-reconfigure locales also diese dau's -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Freeze after startup with bf24
#include * Jeremy Hankins [Thu, Jul 17 2003, 10:39:36AM]: > > Unfortunately, right after the boot up (when the select language > > display is up) the machine freezes and wont accept any input -- > > capslock doesn't light the keyboard led, either. The machine is a > > Precision 350 from Dell that came preinstalled with Redhat and was > > running kernel 2.4.18. The floppies I made work fine on another > > machine here. > > For what it's worth, this happens with the standard bf2.4 as well. Try the default 2.2.20-idepci flavor, or use Google. You have a Dell box, live with that. MfG, Eduard. -- hobbies: Linux, IRC -> ehm ja -> get a life! life? wasn das? ij: das is das problem vor dem du stehst wenn du im urlaub ohne computer bist CHS: urlaub? noch son unbekanntes wort... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#201619: modconf: non-visible module names in some sections
reassign 201619 whiptail thanks #include * Robert Millan [Wed, Jul 16 2003, 10:49:13PM]: > > > gnome-terminal is broken? well actualy the same happens for TERM=linux and > > > TERM=screen so it clearly has nothing to do with the terminal emulator, or > > > even with X. > > > > Please? You most-saying screenshots showed a terminal with overlapping > > chars (read: broken terminal app), and your bug report basically existed > > of this screenshot. So can you reproduce this in a terminal with fixed > > fonts or not? > > As I said, the bug doesn't depend on the terminal type or the fonts in use. Erm, that is exactly what you did NOT say. > > And when you do, please reassign your report to whiptail > > or whiptail-utf8 (man, you are a developer and should be able to > > recognize where a such problem comes from). > > No, I'm not suposed to know anything about the whiptail interface if i > haven't hacked on it. All i can say, from a quick test, is that the same > problem is reproductible with whiptail 0.51.4-6 (from testing). > > Asides from this, if you think gnome-terminal is broken in some way, then > I suggest you speak with Marillat about it; I'm sure you'll understand each > other very well. WTF do you mean? You send an unreproducible bug report without a sufficient explanation, refuse to give clear answers and expect us to deal with that? MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#201619: modconf: non-visible module names in some sections
#include * [EMAIL PROTECTED] [Wed, Jul 16 2003, 08:27:42PM]: > Package: modconf > Version: 0.2.44 > Severity: important > > An image better than thousand words. PNG attached. What is wrong? Please retry in a not broken terminal, eg. xterm or rxvt, or load a fixed font in this one if you can. MfG, Eduard. -- hobbies: Linux, IRC -> ehm ja -> get a life! life? wasn das? ij: das is das problem vor dem du stehst wenn du im urlaub ohne computer bist CHS: urlaub? noch son unbekanntes wort... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't change running i386 Woody 3.0 to LSI 53C1020
#include * Markus Rupprecht [Fri, Jul 04 2003, 07:43:50AM]: > Now I have read, that some 53C1030 users took the 2.4.20 modules floppy to > install the system. > > When I use mptbase.o from the 2.4.20 floppy modconf says, > that they were build for kernel 2.4.20 and loading fails. http://people.debian.org/~blade/bf3024/ -- bobby locales einstellen <_Bobby> ? dpkg-reconfigure locales also diese dau's -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building boot images with boot-floppies on PowerMac
#include * [EMAIL PROTECTED] [Sat, Jun 28 2003, 11:16:30AM]: > The "arch maintainer" for what? My problem is with b-f, according to > those documents you mention, this list is the right place. For the problem with your powerpc kernel package which was your initial problem. > > > > whereever it now are, it is the location of the supplementary packages > > > > like kernel-image-*; they are still located in unstable while the > > > > build scripts look in Woody. > > > > > > Why is that? I would have thought it logical to distribute b-f configured > > > > Because we need a controllable way to take the _stable_ packages for > > _stable_ branch of boot-floppies. > > My initial problem is that that is precisely what I cannot do. If I can And that is, precisely, and edge and chicken problem. The build cannot take the kernel images since they are not in the archive, but it uses the archive structure to decide which package to take (expecting "stable" package). And the packages do _not_ land in the stable branch immediately because the distro is frozen. So you stuff _will_ be buildable when r2 has been released and the SRM accepted the kernel-image* and according pcmcia-modules-* packages to stable. Until this happens and since you are using a development version of boot-floppies (*), please stop fighting windmills. (*): or an outdated/wrong version, bug FTP maintainers, and this is another story > do that, then I have a base to work on. As said, your work won't be honored enough. > > > Something needs to be done in the short term. From what I've seen there > > > are quite a few refugees from Red Hat come to Debian recently. A lot of > > > them are capable at what they do (installing and configuring Linux), and > > > they will be finding this part of Debian a nasty shock. > > > > Who are you speaking for? Newbies? They are users, not developers. > > I am a user. I'm one of many who's been using Red Hat Linux for years > (in my case since some time in '96), who's been helping out on the > various Red Hat support lists, and who doesn't like recent changes to > Red Hat's business model. Fine. Comming back to your mkisofs example, it's typical daily job for a normal user to recompile mkisofs again and again? > > > > Why /etc? We are just building a package, the changes on the host system > > > > should be minimal. > > > > > > At this level, b-f is a tool, not so different from mkisofs, that takes > > > > Loool. And KDE is just a user tool, not so different from cdrecord (in > > your categories), isn't? > > Certainly, it's tool, but I don't see that it has much similarity to > cdrecord;-) Oh, please, you tried to escape the correct answer. > > > data from various sources, processes it in magical ways, and produces > > > outputs. > > > > There is not magic in mkisofs, clean code based on almost clean specs. > > The job ob BFs is quite different. (and before you start bichting: I am > > the cdrtools comaintainer). > > I think you're concentrating on differences, I see similarities. As a I do not concentrate on anything or close my eyes, I just tell you the facts. Please estimate the level of complexity in the cooperation of different tool, platforms specifics, etc. > user, I don't care for specs, I care for results. Both take some data There won't be any results if you break with the roots. > (files), fiddle round and create files containing essentially the same > data structured differently. With this attitude you can argument even for LFS. > As for you being the cdrtools comaintainer, that doesn't carry much > weight: I have used mkisofs and cdrecord, I know what they do. I don't > care how they do it, though you might;-) I did not say cdrecord. It was your idea to distract from the KDE-vs.-single-tool argument. > > > I've not tried using it except as root - in my environment the usual > > > advice not not be root doesn't seem so sensible - but it does require > > > configuration, and /etc seems to me a sensible place for that > > > configuration. > > > > And if a developers wants to commit the changes on his personal files, > > he has to move it first? Sounds more like a cludge for me. > > I don't understand what you're saying here. Doesn't matter. > > Redhat does not have multiple kernels (does it?), so many installation > > ways withing the first stage installer, etc. > > Red Hat has many kernels for IA32. I'm not sure what the latest Yet another distraction. How many do you select when starting the installer? > I've seen > i386 > i386-BOOT > i586 > i586-smp > i686 > i686-smp > i686-enterprise > athlon > athlon-smp > athlon-enterprise We have a similar set of kernels, the user is free to install them. After the base system and the installation kernel has been installed. > RHL is also available for other architectures, to be sure not as many as > Debian. YEAH! And exactly here is the problem. Redhat supports only the "new" architectures which don't create much trouble. > If I w
Re: Building boot images with boot-floppies on PowerMac
#include * [EMAIL PROTECTED] [Thu, Jun 26 2003, 11:11:39AM]: > > > I have tried the testing version. It fails too: > > > 1393+1 records out > > > > You did not understand the problem. It is not the version of BFs > > The problem, I thought, is that the three versions of b-f I've used do > not produce bootable images. That is the reason for first asking the arch maintainer. RTF intro files in the package, starting at README. > > whereever it now are, it is the location of the supplementary packages > > like kernel-image-*; they are still located in unstable while the > > build scripts look in Woody. > > Why is that? I would have thought it logical to distribute b-f configured Because we need a controllable way to take the _stable_ packages for _stable_ branch of boot-floppies. > to look for kernels in places where they may be found. I'm new to all > this, I don't have a clue where to look. A-Ha. > > > /archive/debian/download/var/lib/apt/lists/debootstrap.invalid_dists_woody_main_binary-powerpc_Packages > > > E: Couldn't download pcmcia-modules-2.4.18-newpmac > > > E: ./kernel.sh abort > > > > And the solution is: get those packages from the pool and store them in > > your local package directory (see the "config" file). > > IMV that's more a workaround than a cure. While it will likely fix it > for me, the next person along will encounter the same difficulties. And it won't change. If you are willing to make radical changes, look at the Debian installer project. There a such problem has never existed since they have a separated tree in the FTP archive. > > You can define a mirror in the config, that is not the problem. The problem is the > > Debian release which the > > packages belong to. A possible workaround would be modifying the build > > scripts to work with the pool structure (read: having a private version > > of the /etc/apt directory where you can specify the priority of the > > packages, scanning every Packages file available on that mirror), taking > > the stable version of a package if possible and if not, fall-back on the > > Sid version of the same package. Maybe you can use apt for this purpose, > > but who is going to make this work? Many people declared the BFs as > > doomed, I doubt that you really wish to stand up and work on it. > > Something needs to be done in the short term. From what I've seen there > are quite a few refugees from Red Hat come to Debian recently. A lot of > them are capable at what they do (installing and configuring Linux), and > they will be finding this part of Debian a nasty shock. Who are you speaking for? Newbies? They are users, not developers. > > > 3. Maybe source a site configuration file from /etc/bootfloppies/ where > > > the results of steps 1 and 2 can be adjusted. > > > > Why /etc? We are just building a package, the changes on the host system > > should be minimal. > > At this level, b-f is a tool, not so different from mkisofs, that takes Loool. And KDE is just a user tool, not so different from cdrecord (in your categories), isn't? > data from various sources, processes it in magical ways, and produces > outputs. There is not magic in mkisofs, clean code based on almost clean specs. The job ob BFs is quite different. (and before you start bichting: I am the cdrtools comaintainer). > I've not tried using it except as root - in my environment the usual > advice not not be root doesn't seem so sensible - but it does require > configuration, and /etc seems to me a sensible place for that > configuration. And if a developers wants to commit the changes on his personal files, he has to move it first? Sounds more like a cludge for me. > Red Hat's equivalent tool is Anaconda, and you don't go fooling round > with the package itself to build your CDs (Anaconda does a bit more) and > boot images. Redhat does not have multiple kernels (does it?), so many installation ways withing the first stage installer, etc. > Even if you disagree on /etc, ~/boot-floppies/ remains a good place for > personal customisation. WHY? We are developers, not users. We can use diff, patch and cvs. > > > I'm sure you can argue whether this idea is slightly broken: the main > > > objective is to achieve something that is robust enough to work for the > > > > It is quite robust as-is. It is just the FTP archive that is > > incosistent. > > Robust? It doesn't work at all at present. As a user, I don't care > whether the particular problem is that the Debian respository has > changed since b-f was packaged. I don't have to be a car mechanic to > diagnose that my car won't start, and I don't care whether it's because > it's out of fuel or the spark plugs are dirty. Either way, the engine > cranks but doesn't start. Talk is cheap. > Robust means to me that when someone updates the repository, especially > with an official update, it continues to work. That is the core problem, and if you wanna complain, file a bug against ftp.debian.org. > I may be mi
Re: Building boot images with boot-floppies on PowerMac
#include * [EMAIL PROTECTED] [Wed, Jun 25 2003, 02:47:44PM]: > > > > Stable still has 3.0.22. Is there a reason 3.0.23 never moved to > > > > stable, Eduard? > > > > See above. Woody has been moved to stable under our asses, and to this > > time there were an RC bug about potential security problems. One of the > > problems with Debian's release system. > > I have tried the testing version. It fails too: > 1393+1 records out You did not understand the problem. It is not the version of BFs whereever it now are, it is the location of the supplementary packages like kernel-image-*; they are still located in unstable while the build scripts look in Woody. > /archive/debian/download/var/lib/apt/lists/debootstrap.invalid_dists_woody_main_binary-powerpc_Packages > E: Couldn't download pcmcia-modules-2.4.18-newpmac > E: ./kernel.sh abort And the solution is: get those packages from the pool and store them in your local package directory (see the "config" file). > It seems to me part of the problem is that it has hard-coded into it > versions of kernels to use, and the kernel maintainers have replaced > those packages. The kernel maintainers cannot replace or move packages easily - Woody is stale^h^hble. > I'm sure I can hack this thing to build the bootfloppies _I_ need, but > that won't help others. Part of what I would do is prevent it from > building for boxes I don't have. And that is the reason why boot-floppies are no built by build daemons but manually by each architecture maintainer. > What I think should be happening is this: > 1. Default to using mirror(s) from /etc/apt/sources.list. That would > eliminate one of the customisations I must make. > 2. Parse the Packages to the extent necessary to discover the most > recent of each of the packages needed. You can define a mirror in the config, that is not the problem. The problem is the Debian release which the packages belong to. A possible workaround would be modifying the build scripts to work with the pool structure (read: having a private version of the /etc/apt directory where you can specify the priority of the packages, scanning every Packages file available on that mirror), taking the stable version of a package if possible and if not, fall-back on the Sid version of the same package. Maybe you can use apt for this purpose, but who is going to make this work? Many people declared the BFs as doomed, I doubt that you really wish to stand up and work on it. > 3. Maybe source a site configuration file from /etc/bootfloppies/ where > the results of steps 1 and 2 can be adjusted. Why /etc? We are just building a package, the changes on the host system should be minimal. > 4. Source a personal configuration file for further fine-tuning. Feel free to create a such thing, I won't accept it in the "stable" branch. > I'm sure you can argue whether this idea is slightly broken: the main > objective is to achieve something that is robust enough to work for the It is quite robust as-is. It is just the FTP archive that is incosistent. > unsuspecting (me, for example) and to simplify customisation for more > advanced use. Customising the config file doesn't seem to me especially > elegant or robust, and I can imagine it causing problems with updates > from CVS. Nack. There only were few problems with CVS mergin in the hot development phase. MfG, Eduard. -- Zeit fuer Bloedsinn zu haben, bedeutet noch lange nicht, ihn auch zu machen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building boot images with boot-floppies on PowerMac
#include * [EMAIL PROTECTED] [Mon, Jun 23 2003, 07:19:54AM]: > /archive/debian/download/var/lib/apt/lists/debootstrap.invalid_dists_woody_main_binary-powerpc_Packages > E: Couldn't download pcmcia-modules-2.4.18-newpmac > E: ./kernel.sh abort > make[1]: *** [linuxnewpmac.bin] Error 1 > make[1]: Leaving directory `/root/cvs/bf/boot-floppies' > make: *** [build] Error 2 According to madison's output, the package is in unstable only. The reason may be some temporary RC bug that prevented the package from beeing accepted in Woody. > > Stable still has 3.0.22. Is there a reason 3.0.23 never moved to > > stable, Eduard? See above. Woody has been moved to stable under our asses, and to this time there were an RC bug about potential security problems. One of the problems with Debian's release system. > What should be in stable is working tools that may be used to create the > binaries created;-) How else can uses enjoy their GPL-given rights? It should. My bug report against ftp.debian.org has been closed quickly, so blame those guys. MfG, Eduard. -- *patsch* was bin ich bloed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: de/install broken
#include * Josip Rodin [Mon, Jun 16 2003, 03:02:16PM]: > On Mon, Jun 16, 2003 at 02:23:33PM +0200, Eduard Bloch wrote: > > > debiandoc2text -l de -O install.de.sgml > install.de.txt > > > nsgmls:de/hardware.sgml:184:8:E: document type does not allow element "EXAMPLE" > > > here; assuming missing "P" start-tag > > > make[3]: *** [install.de.txt] Error 1 > > > > We know and someone is already working on it. In the meantime, take "de" > > from the list in documentation/Makefile.docs. > > Why didn't you do it?! It doesn't take a wizard to figure out you're > breaking other languages' builds. Because I was not aware of the fact(?) that you are building BF's docs periodicaly. MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: de/install broken
#include * Josip Rodin [Sun, Jun 15 2003, 08:53:10PM]: > debiandoc2text -l de -O install.de.sgml > install.de.txt > nsgmls:de/hardware.sgml:184:8:E: document type does not allow element "EXAMPLE" > here; assuming missing "P" start-tag > make[3]: *** [install.de.txt] Error 1 We know and someone is already working on it. In the meantime, take "de" from the list in documentation/Makefile.docs. MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem Booting Install CD
#include * Chris Tillman [Mon, Jun 02 2003, 05:58:47PM]: > > In case you need more info, my system is a Dell > > Dimension 8250 w/ 2.8 gHz P4 processor, 512 MB RAM, > > 112 GB HD, ATI Radeon 9700 Pro video adapter w/128 MB > > RAM, a Turtle Beach Santa Cruz sound card, and an 18" > > Dell 1800FP LCD monitor plugged into the DVI video > > output jack. > > Does the wireless device run on the USB bus internally? Some USB > keyboards which fail when booting will work after the boot is > complete, I believe the advice is to try a standard keyboard for the > boot and then switch. There is USB keyboard support in the bf2.4 flavor, just try to boot with it. On the other hand, I had similar problems with a Logitech wireless keyboard with kernel versions up to 2.4.17. Pressing some keys simultaneously or just too fast made getty hang for 10..60 seconds. MfG, Eduard. -- Getty: Solche Aussagen tätigt man hier nicht - sonst kommt wieder der weasel daher und zitiert einen auf der #-Seite! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#186927 acknowledged by developer (Re: Bug#186927: romfs builtin)
#include * Glenn McGrath [Mon, Mar 31 2003, 09:03:51PM]: > Both ext2 and romfs could be compiled into the kernel and as long as > romfs is used for the initrd it will save space. > > If we use ext2 or cramfs on the initrd it will add 2kB. > > I cant think of any reason against using romfs for the initrd, if anyone > can please speak up. Of course there is one. Both ext2 and romfs do not compress each file, you use compression on the whole image, and the kernel extracts the beast into a ramdisk of the appropriate size. But files in cramfs are compressed separated and extracted separated on the fly, so you do not need the memory to hold the whole image. However, this is not important for a modern system with >>16MB RAM. Gruss/Regards, Eduard. -- Es fehlt immer ein Minimum, um ein Maximum zu erreichen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SCSI boot
#include * MJM Wright [Tue, Mar 25 2003, 11:50:50PM]: > I want a dual system -- not a dual-boot system. The IDE drives contain > Win 98, with all of the Debian installation on the SCSI drives. "Dual system"? What exactly is your meaning of this term? Separating to different harddisks wont work to 100% since they share the boot sequence. > I also made a Debian rescue floppy. Fine. Use that floppy till you fix LILO. > If I try to boot by setting the first boot device in the CMOS to SCSI. I > get an L, followed by 01, space, 01, space, ad infinitum. Known and well documented problem. LILO and BIOS have different ideas about the logical disk order. Read "man lilo.conf" and comments in /etc/lilo.conf about disk/bios pairs. > If I use the rescue floppy, I get a "boot:" prompt. With no key presses > it loads linux.bin from the floppy, and after about 5 minutes, > everything loads from the SCSI drive (/dev/sda1). Fine. > I have used the Adaptec utility (CTRL A after POST) and as far as I can > tell it should allow the boot. > > I have tried things like: > > boot: /vmlinux root=/dev/sda1 Please, read the boot screens. It is "linux.bin root=...". > Any advice on how to boot directly from the SCSI drive would be very > much appreciated. Also, please allow for a novice user of Debian. See lilo.conf Gruss/Regards, Eduard. -- Ein berühmter Mann verliert nicht, gewinnt vielmehr durch eine Lächerlichkeit, die man von ihm erzählt oder lieset -; aber begeht er sie vor unsern Augen, so verliert er. Allein warum? Hier wirkt die Gegenwart zu mächtig, und der Mann, erscheinend darin, nur stückweise aufglänzt; hingegen in der Erzählung herrscht und glänzt die Idee des Ganzen über den Mann. -- Jean Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#185420: marked as done (boot-floppies - bad kernel choice)
reopen 185420 severity 185420 normal tags 185420 + help thanks #include * [EMAIL PROTECTED] [Fri, Mar 21 2003, 10:46:24AM]: > Second, I agree with you that it should default to installing the same > version of the kernel I chose to install with. My install kernel is > debian/dists/woody/main/disks-i386/3.0.23-2002-05-21/bf2.4/tftpboot.img > which I have verified by md5summing all the tftpboot.img files I have in THIS IS what you should have reported from the beginning. How should I have known what t.f. you are talking about? > debian/... and the one in /tftboot. Consequently, I think the fact it > installs a 2.2 kernel is wrong. There is a small problem with tftp/PXE installs since the installer does not get the needed options and takes the wrong kernel. I am not sure how to fix this. Gruss/Regards, Eduard. -- The chances of anything coming from mars are a million to one But still the come. -- War of the Worlds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
#include * Brian Mays [Fri, Mar 21 2003, 10:19:14AM]: > > Wait, the log messages are from WOLK, but are almost identical with > > those I got from 2.4.20-bf2.4 > > Yes. Looking at your original message, I realize that I have diagnosed > the problem with WOLK. The problem with 2.4.20-bf2.4 is a little Sorry for that. > different. Cardmgr is actually using insmod instead of modprobe to load > the modules, so the problem with locating the module is not there. > > I need to see more of the logs and perhaps the config files to diagnose > this problem. It looks like the orinoco module is not being loaded at > all, but I don't know why. Those should be what you need: Mar 16 17:21:29 debian cardmgr[1060]: watching 2 sockets Mar 16 17:21:29 debian cardmgr[1061]: starting, version is 3.2.2 Mar 16 17:21:32 debian kernel: cs: memory probe 0x0d-0x0d: clean. Mar 16 17:21:32 debian cardmgr[1061]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter Mar 16 17:21:32 debian cardmgr[1061]: executing: 'modprobe orinoco_cs' Mar 16 17:21:32 debian kernel: hermes.c: 5 Apr 2002 David Gibson <[EMAIL PROTECTED]> Mar 16 17:21:32 debian kernel: orinoco.c 0.11b (David Gibson <[EMAIL PROTECTED]> and others) Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_setup Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: insmod /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o failed Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: insmod orinoco_cs failed Mar 16 17:21:32 debian cardmgr[1061]: modprobe exited with status 255 Mar 16 17:21:32 debian cardmgr[1061]: executing: 'insmod /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o' Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_setup Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol hermes_struct_init Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_shutdown Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_reset Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_proc_dev_cleanup Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_interrupt Mar 16 17:21:32 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_proc_dev_init Mar 16 17:21:32 debian cardmgr[1061]: insmod exited with status 1 Mar 16 17:21:33 debian cardmgr[1061]: get dev info on socket 1 failed: Resource temporarily unavailable Mar 16 17:22:47 debian cardmgr[1061]: executing: 'modprobe -r orinoco_cs' Mar 16 17:23:01 debian /USR/SBIN/CRON[1072]: (mail) CMD ( if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi) Mar 16 17:25:33 debian kernel: usb.c: USB disconnect on device 00:1d.1-1 address 2 Mar 16 17:26:07 debian cardmgr[1061]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter Mar 16 17:26:07 debian cardmgr[1061]: executing: 'modprobe orinoco_cs' Mar 16 17:26:07 debian kernel: hermes.c: 5 Apr 2002 David Gibson <[EMAIL PROTECTED]> Mar 16 17:26:07 debian kernel: orinoco.c 0.11b (David Gibson <[EMAIL PROTECTED]> and others) Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_setup Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: insmod /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o failed Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: insmod orinoco_cs failed Mar 16 17:26:07 debian cardmgr[1061]: modprobe exited with status 255 Mar 16 17:26:07 debian cardmgr[1061]: executing: 'insmod /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o' Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_setup Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol hermes_struct_init Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_shutdown Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_reset Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_proc_dev_cleanup Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_interrupt Mar 16 17:26:07 debian cardmgr[1061]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_cs.o: unresolved symbol orinoco_proc_dev_init Mar 16 17:26:07 debian cardmgr[1061]: insmod exited with status 1 Mar 16 17:26:08 debian cardmgr[1061]: get d
Re: [pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
#include * Brian Mays [Thu, Mar 20 2003, 04:13:29PM]: > Eduard Bloch <[EMAIL PROTECTED]> wrote: > > > Nothing relevant. It is pure 2.4.20 build from Herbert's kernle-source > > package. But we use Woody's version of pcmcia-source because it is for > > stable, ... > > That's strange, because it doesn't explain the version numbers reported > in the other email. Wait, the log messages are from WOLK, but are almost identical with those I got from 2.4.20-bf2.4 > > ... and because the Sid version refuses to build anything if pcmcia in > > kernel has been enabled. > > You can override this by setting the following environment variable: > > FORCE_CONFIG_PCMCIA=y > > This is an undocumented feature intended for building Debian packages, > when it is necessary to override the default behavior and it is assumed > that the person building the package knows what he is doing. This trick > is undocumented, because I don't want users doing this. Building two > sets of modules with the same names leads to problems, like the one > discussed here. I see. > > > One way to fix this would be to use insmod to explicitly load the > > > correct drivers, or to delete the orinoco and hermes drivers under > > > the kernel subdirectory and run depmod. The real problem is that > > > there should not be two modules with the same name. > > > > I think I will workaround by removing the kernel versions from the > > drivers tarball on boot-floppies. Any objections? > > I think that will work. The only thing I do not like is that inocent drivers that share the code like orinoco_pci driver have to go too. Gruss/Regards, Eduard. -- Zwei Knaben gingen durch das Korn der eine hinten, der and're vorn keiner ging in der Mitte folglich fehlte der dritte. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
#include * Brian Mays [Tue, Mar 18 2003, 04:04:25PM]: > The 2.4.20 kernel source (in the kernel-source package) has version > 0.11b (I think that 2.4.18 also has this version), which is why this > problem doesn't appear more frequently. What patches did you apply to > this kernel? Where did the newer driver come from? Nothing relevant. It is pure 2.4.20 build from Herbert's kernle-source package. But we use Woody's version of pcmcia-source because it is for stable, and because the Sid version refuses to build anything if pcmcia in kernel has been enabled. > One way to fix this would be to use insmod to explicitly load the > correct drivers, or to delete the orinoco and hermes drivers under the > kernel subdirectory and run depmod. The real problem is that there > should not be two modules with the same name. I think I will workaround by removing the kernel versions from the drivers tarball on boot-floppies. Any objections? Gruss/Regards, Eduard. -- Wußten Sie schon... ... daß die Zahl der jugendlichen Aussteiger bei uns sehr hoch ist, vor allem frühmorgens an den Bushaltestellen und Bahnhöfen? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
Hallo John, * John H. Robinson, IV [Sun, Mar 09 2003, 12:34:11AM]: > i have built the USB 2.0 modules in. i have also built the pcmcia > external modules. ... We have a problem: something is broken with the modules in the pcmcia-modules or with cardmgr. I think about reporting a grave bug against pcmcia-cs because of this: Mar 18 17:57:43 debian cardmgr[490]: executing: 'insmod /lib/modules/2.4.20-bf2. 4/pcmcia/orinoco_cs.o' Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_setup Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol hermes_struct_init Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_shutdown Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_reset Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_proc_dev_cleanup Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_interrupt Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_proc_dev_init Mar 18 17:57:44 debian cardmgr[490]: insmod exited with status 1 Mar 18 17:57:45 debian cardmgr[490]: get dev info on socket 1 failed: Resource t I am not sure what to do know. I have just rebuilt the packages, same problem. I am running out of ideas, I checked the dependency chain detected by depmod and loaded the modules manually - cardmgr loads the modules in the correct order. This works as-is with 2.4.18-bf2.4 and fails with 2.4.20-bf2.4. Mar 11 02:00:50 debian cardmgr[2632]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter Mar 11 02:00:50 debian cardmgr[2632]: executing: 'modprobe hermes' Mar 11 02:00:51 debian kernel: hermes.c: 5 Apr 2002 David Gibson <[EMAIL PROTECTED] dropbear.id.au> Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco' Mar 11 02:00:51 debian kernel: orinoco.c 0.11b (David Gibson <[EMAIL PROTECTED] bear.id.au> and others) Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco_cs' Mar 11 02:00:51 debian kernel: orinoco_cs.c 0.11b (David Gibson <[EMAIL PROTECTED] ropbear.id.au> and others) vs. Mar 11 22:27:22 debian cardmgr[381]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter Mar 11 22:27:22 debian cardmgr[381]: executing: 'modprobe hermes' Mar 11 22:27:22 debian kernel: hermes.c: 4 Dec 2002 David Gibson <[EMAIL PROTECTED] dropbear.id.au> Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco' Mar 11 22:27:23 debian kernel: orinoco.c 0.13b (David Gibson <[EMAIL PROTECTED] bear.id.au> and others) Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco_cs' Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_shutdown Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_reset Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_proc_dev_cleanup Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_proc_dev_init Gruss/Regards, Eduard. -- Es gibt einen neuen Aufkleber für die A-Klasse? "Ich bremse nicht für Elche!" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing debian 3.0r1 (25.01.03)
Moin kuppermanfred! kuppermanfred schrieb am Sunday, den 09. March 2003: > i copied the iso-file and made image with nero. the cd boots and give > instructions how to boot. it a notebook "baycom wolrdbook2". > the installtions starts some lines are displayed on screen but to quick > to read. then my screen start iluminating from dark to bright and on the > right side i can see the knoppix sysmbol and word in capital letters. > nothing more happens, no messages or what ever. > i'm prepared to change to the linux-world but i didn't expect an > installation failure. > > help me Installation manuall will help you, it describes your case. Reason: bad, bad video card. Solution: try VESA framebuffer or text console. Either vga=791 or video=vga16:off Gruss/Regards, Eduard. -- Wer Recht hat, muß auch Streit anfangen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: TheBase System Installation
#include * Bernard & Jean Dale [Sat, Mar 01 2003, 06:58:10PM]: > I've tried a number of times to install 3.0r0 from a set of 7 cd's > purchased over the internet but before the first installation cd has > finished I'm advised that it is unable to install the base system. > file:/instmnt/pool/main/a/adduser/adduser_3.47_all.deb > was corrupt couldn't download adduser. What is so hard to understand this message? Something is going wrong with your CDROM device or installation media. Gruss/Regards, Eduard. -- sed 's+|++g;s| *||g;s| *||g;s/$/\\bigskip/;s/\([_&$]\)/\\\1/g'\ u-liste > unterschriften.tex -- Oliver Zendel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#182642: boot-floppies: boottime keymap makes 88 key adb keyboard unusable on oldworld powermac
#include * Lee Adamson [Wed, Feb 26 2003, 06:47:31PM]: > When the box reboots after initial base system install, a boottime > keymap is loaded that seems to cause my old 88 key adb keyboard to be > mapped wrong (using the qwerty/us keymap). > > The solution I have found is to use the shell on VT2 to remove the > /target/etc/init.d/keymap.sh script (or just move it out of the way) so > that the kernel keymap is kept on reboot. Once console-tools or console > date (whichever it is that allows you to select a more specific keymap) > is configured, a working keymap (that is KERNEL) can be chosen. > > This problem arose when manually editing the sources list at install > time to point to unstable rather than stable. I do not know if the > problem appears if stable or testing are installed instead. > > The system used is a power macintosh 8500/[EMAIL PROTECTED] (xlr8), though I doubt > that has any bearing on the problem, as an apple extended 101 key adb > keyboard does not exhibit the same problem. Could anyone prove this and tell the exact reason of the problem? Problem of console-tools? Anything that can or should be fixed in boot-floppies for Woody? Please keep Cc'ing to debian-boot or me. Gruss/Regards, Eduard. -- cat `locate .signature` -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Testing netinstall and others
#include * Klaus Imgrund [Wed, Feb 26 2003, 03:05:23PM]: > With those (tried them all) the splash screen or whatever that screen It's called framebuffer console. > with tux is comes up and it loads the kernel until a error msg about a > reiser superblock that it cant find. > I do have all reiser partitions on my box but they are not even mounted > at that point. > A old potato cd boot just fine. Are you sure you have enough RAM? (eg. 14meg for i386). Your problem sounds like there was some problem extracting the installation root filesystem to the memory. Gruss/Regards, Eduard. -- Es gibt Zeiten, wo einem alles gelingt. Aber das braucht niemanden zu beunruhigen. Sie gehen sehr schnell vorüber. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network install of Woody
#include * John Summerfield [Fri, Feb 21 2003, 02:10:57PM]: > > to be a lot of interest, but not too much concrete input. Maybe > > one of the issues is there are so many ways to get it to work? > > If I were to write it (assuming I knew enough, which at present I don't), you > could probably point out errors, but not the inadequacies. > > At present, I in my ignorance am well-equipped to locate the latter. If I wait > until I have worked through it and found a path that works, then it will become > clear enough that I will no longer be able to indentify clearly what's missing, > what facts I have assumed but which might not be known to others. What about making notices on your way? Later, you can review them and remember what caused the problems and how another person may solve the problem easier. Gruss/Regards, Eduard. -- Um sich von einer zu großen Liebe oder Duldsamkeit für etwas zu heilen, muß man nicht die Feinde davon lesen, sondern die Freunde. Lavater -- Jean Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SV: loop: can't get info on device
#include * Eduard Bloch [Fri, Feb 21 2003, 10:20:45AM]: > > Yes, don't try extracting the kernel more than 7 times (assuming > > del_loop doesn't get called appropriately) ;-) > > Heh? IIRC this is dead code, I replaced loop-device operations with > direct losetup calls during the Woody freeze because of unexplainable > problems with our functions. Err, forget it. Gruss/Regards, Eduard. -- Letzte Worte eines Rennfahrers: "Ob der Mechaniker weiß, daß ich was mit seiner Freundin habe?" msg26008/pgp0.pgp Description: PGP signature
Re: SV: loop: can't get info on device
#include * Emile van Bergen [Fri, Feb 21 2003, 09:47:25AM]: > > I found a spot in boot-floppies where this could happen, and added a > > check. I think this will have to wait for r3 though. Do you see any > > possible workarounds in the find_unused_loop_device() code in > > losetup.c? > > Yes, don't try extracting the kernel more than 7 times (assuming > del_loop doesn't get called appropriately) ;-) Heh? IIRC this is dead code, I replaced loop-device operations with direct losetup calls during the Woody freeze because of unexplainable problems with our functions. Gruss/Regards, Eduard. -- Mit Kirch und Thoma geht's ins Medienkoma! -- Jörg Prante <[EMAIL PROTECTED]> msg26007/pgp0.pgp Description: PGP signature
Bug#181739: how to fix?!
And what is your idea about the possible solution for #181739? Another kernel? Feasible without breaking other things? Gruss/Regards, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A boot floppy which boots a CD ROM?!
#include Sebastian Schuon wrote on Fri Feb 14, 2003 um 11:22:49PM: > Hi all! > Does anyone happen to know if a boot floppy exists which only loads a driver > fpr the CD-Rom drive and launches the boot image found there? > My computer (P100) isn't capable to boot via CDrom and i'm to lazy to create > all these boot floppies. > Anyone got an idea? If your CD-ROM drive is supported by the kernel's drivers, you need only two, boot and root floppies. Gruss/Regards, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hung at "RAMDISK: Compressed image found at block 0".... need more RAM?
#include * Adam Robson [Sun, Feb 09 2003, 11:33:28PM]: > I think I only have 8MB of RAM is that maybe the problem? If so, is Yes. > there a way to work around that? Get Slink disks from archive.debian.org and install with them. Gruss/Regards, Eduard. -- Die Realität ist eine Illusion, die durch einen Mangel an Whiskey hervorgerufen wird. -- Schottisches Sprichwort -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Status of boot-floppies for Debian 3.0r2
Hello, after more than a month of wake-up phase, it is time to push the development a bit. Boot-Floppies 3.0.24 are almost ready, ports for most architectures have been build and we got positive test results. Outstanding issues are: - test the sparc build, any report welcome - testing and fixing the s390 build with kernel 2.4.19. A problem was figured out with our current dbootstrap code - it seems to reset the network connection that you need to continue in the combination of ctc and kernel 2.4.19. Stefan Gybas <[EMAIL PROTECTED]> and Bastian Blank <[EMAIL PROTECTED]> are working on a possible solution, please help if you can. If there will be no fix in a reasonable period, the changes will be reverted and s390 will keep the old kernel. - arm port gets a new installation flavor (riscstation), however the kernel and all needed patch packages are not ready. Please help with this task, otherwise the riscstation flavor has to go (#177187, #177188, #177192, #177196). EOD. For all other info: http://lists.debian.org/debian-boot/2002/debian-boot-200212/msg00798.html Gruss/Regards, Eduard. -- No, really: Outlook Express is an excellent newsreader. But you should not use it as a newsPOSTER. msg25732/pgp0.pgp Description: PGP signature
Re: cannot boot to install woody
#include * Fabio Calefato [Thu, Feb 06 2003, 07:46:06PM]: > anyway, boot hangs. i've tried re-writing it twice again, but noway. > so i switched from root.bin to other img, till i succeded in booting > with the rescue.bin img file. After uncompressing the img and detecting > my hw, i got a kernel panic msg: "cannot find init [...] try to pass > init= to the kernel". > what's wrong? is it possibile to install it using the rescue img? and Please RTFM. You need both floppies, you boot with rescue and insert the "root" when the kernel asks for it. Gruss/Regards, Eduard. -- Besser heimlich schlau als unheimlich blöd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Russian localized install?
#include Martin Quinson wrote on Thu Feb 06, 2003 um 09:33:14AM: > First of all, I'm not really the right person to help you coordinate your > efforts. I don't speak russian *at all*. But I participate to the > french translation effort, and can give some hints. I think I was the right person for a such request 10 months ago, see http://lists.debian.org/debian-russian/2002/debian-russian-200203/msg00081.html However, nobody volunteered to make a complete and error-free translation, so the russian version has been excluded. Today, I would only accept russian translation for boot-floppies if someone sends me a translation in the next seven days and I can proof-read it. For long-term work, please help translation the next generation Debian-Installer. Gruss/Regards, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: making my own netinstall CD
Moin Markus! Markus Schabel schrieb am Wednesday, den 05. February 2003: > Eduard Bloch wrote: > > >Use floppies and read in the manuall about kernel replacement. However, > >the old driver CONFIG_BLK_DEV_CMD680 is enabled in the new kernel of > >next (testing) release of boot-floppies. Please look at > >http://people.debian.org/~blade/bf3024/ and report the results. > > The module 3c59x seems to be broken in your bf's. Loads without > problems, I'm able to configure the interface manually, but I'm not > able to use the interface. ping get's no responses. Tried the same > with the official 2.4.18-bf24 bootfloppies, works fine... > > Any ideas what's wrong? Not really. I have a 3c59x, and it works fine for me. You could play with different module options: filename:/lib/modules/2.4.21-pre4/kernel/drivers/net/3c59x.o description: "3Com 3c59x/3c9xx ethernet driver LK1.1.16 19 July 2001" author: "Donald Becker <[EMAIL PROTECTED]>" license: "GPL" parm:debug int, description "3c59x debug level (0-6)" parm:options int array (min = 1, max = 8), description "3c59x: Bits 0-3: media type, bit 4: bus mastering, bit 9: full duplex" parm:full_duplex int array (min = 1, max = 8), description "3c59x full duplex setting(s) (1)" parm:hw_checksums int array (min = 1, max = 8), description "3c59x Hardware checksum checking by adapter(s) (0-1)" parm:flow_ctrl int array (min = 1, max = 8), description "3c59x 802.3x flow control usage (PAUSE only) (0-1)" parm:enable_wol int array (min = 1, max = 8), description "3c59x: Turn on Wake-on-LAN for adapter(s) (0-1)" parm:rx_copybreak int, description "3c59x copy breakpoint for copy-only-tiny-frames" parm:max_interrupt_work int, description "3c59x maximum events handled per interrupt" parm:compaq_ioaddr int, description "3c59x PCI I/O base address (Compaq BIOS problem workaround)" parm:compaq_irq int, description "3c59x PCI IRQ number (Compaq BIOS problem workaround)" parm:compaq_device_id int, description "3c59x PCI device ID (Compaq BIOS problem workaround)" parm:watchdog int, description "3c59x transmit timeout in milliseconds" Gruss/Regards, Eduard. -- Mache alles so einfach wie möglich, doch nicht einfacher. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Promise FastTrak133 Raid again
Moin Markus! Markus Schabel schrieb am Monday, den 03. February 2003: > > Try the new module from http://people.debian.org/~blade/install/preload/ > > and PLEASE report the result. > > > > Gruss/Regards, > > Eduard. > > Warning: kernel-module version mismatch: FastTrak.o was compiled for > 2.4.20 while this kernel is version 2.4.20-bf2.4 This module was not produced by me, and looks like you own creating, right? Please use kernel-headers-2.4.20-bf2.4 then. OTOH, it should still load, since insmod is called with -f and the message above is just a warning. Are you really sure that it failed, did you look at the kernel messages? > But the preload-image is called 2.4.18bf2.4_promise_modules.bin, so there > must be something wrong. I'll try it with non-bf2.4-floppies, perhaps that > will work? It may work with kernel-2.2x, at least the Makefile mentions it. Gruss/Regards, Eduard. -- Ich bin müde, also bin ich. -- Andreas Porr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Promise FastTrak133 Raid again
Moin Wolfgang! Wolfgang Pawlinetz schrieb am Saturday, den 01. February 2003: > Hi List, > > I was searching the web for any new ideas on installing a fairly current Debian >distribution (bf24 is an installation option) on a MSI Motherboard featuring the >Fasttrak133 IDE RAID Controller from Promise in RAID configuration. > > Has anybody got something which can solve the - admittedly well known - problem that >the installation does not detect the RAID configured harddisks? Try the new module from http://people.debian.org/~blade/install/preload/ and PLEASE report the result. Gruss/Regards, Eduard. -- Found one of the original LinuxTag event organisers gazing around in a stupified state. He said that when they'd started it five years ago, it was one evening, about Linux and about LaTeX, I think, and they'd had seventy attenders. And now... and he waved an arm around helplessly. -- Telsa Gwynne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: trouble starting up
#include * Benjamin Meakin [Sat, Feb 01 2003, 01:41:01AM]: > hello, Hello - this List is for base-installation related topics, please report funny bugs of extra package to the appropriate maintainers. Cc'ing to gnome-session maintainer. > I am having trouble getting debian and gnome to work properly. When I > start gnome, the GUI goes crazy. The desktop is offset, random icons > appear in the middle of the screen, images are distorted... Another > problem I encountered was while installing the packages for debian. I > got an error message that says: >Errors encountered while processing: > cxref > This may be a related problem, I don't know. If anybody could tell me > how I could fix either or both of these problems I would appreciate it. > > -Ben < [EMAIL PROTECTED] > > > -- Was die neuen Unwissenden holen müssen: Böschungshobel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#174050: What do you mean?
severity 174050 normal tags 174050 + moreinfo unreproducible thanks A-Ha. Sorry, your paths are Windows paths and do not tell us ANYTHING about which device is C, which is D, etc. Also, a problem with the bsdmainutils package has almost nothing in common with loadlin, so I wonder about your bug description. And, the whole story sounds like bad installation media (assuming that D: is your CD-ROM). Gruss/Regards, Eduard. -- Ist das Absicht, daß da nirgends drin steht, wo das ist? Nicht mal das Land steht drin ... -- Rainer Bawidamann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of boot-floppies for Debian 3.0r2
#include * dann frazier [Fri, Jan 24 2003, 01:20:29AM]: > done. > http://people.debian.org/~dannf/boot-floppies/sparc/ > let me know if i missed anything. Fine. BenC claimed to be the one how knows what is needed to build, but I cannot count on his promises and response times. Now, I would like to see at least one installation report with Dann's build - especially when they are problems. TOFU kept. > > > I have a sparcstation 4 running straight woody that i'd be willing to build > > > stuff on - i'm afraid i missed some context though - is this > > > for a boot-floppies update for woody? > > > > Yes, we're trying to get boot-floppies 3.0.24 for Debian 3.0r2. See > > http://people.debian.org/~blade/bf3024/ . > > > > -- > > ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> > > > -- Letzte Worte des Elektrikers: "Alles klar, kannst einschalten." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Status of boot-floppies for Debian 3.0r2
Hello, after a month of wake-up phase, it is time to push the development a bit. Boot-Floppies 3.0.24 are almost ready, ports for most architectures have been build and we got positive test results. Outstanding issues are: - help Ben Collins <[EMAIL PROTECTED]> to test the Sparc boot-floppies - testing and fixing the s390 build with kernel 2.4.19. A problem was figured out with our current dbootstrap code - under certain circumstances, it seems to reset the network connection that you need to continue. Bastian Blank <[EMAIL PROTECTED]> is preparing a possible solution, please help him with testing. - arm port gets a new installation flavor (riscstation), please help Othmar Pasteka <[EMAIL PROTECTED]> with testing of the new kernel if you own a such system - rebuilding kernel 2.4.20-bf2.4 on i386 because of #176178. IMHO not critical, but should be closed on the most used architecture. For all other info: http://lists.debian.org/debian-boot/2002/debian-boot-200212/msg00798.html Gruss/Regards, Eduard. -- Kleines Lexikon der Computerwerbung: "integriert" minderwertige Einzelteile vereint in einem katastrophalem Ganzen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: m68k 3.0.24 boot-floppies
#include
* Christian T. Steigies [Sun, Jan 19 2003, 12:47:22AM]:
> I've (re)built boot-floppies for m68k a few days ago and finally managed to
> test them on my Amiga. Installation went fine. One thing I noticed, the
> installer downloaded mac-fdisk, on an Amiga, is this necessary?
Fine ("kreuzmach"). We could exclude mac-fdisk from the basedebs list
with an debootstrap argument if the Arch is really an Amiga, but nobody
complained here before about this behaviour.
> Another problem I noticed today is with amiga-fdisk:
> According to Policy Section 2.2: Priorities packages MUST NOT depend on
> packages with lower priority values (excluding build-time dependencies). In
IIRC this was discussed during the Woody freeze and the consens was:
"serious" bugs caused by formailities are not RC if they do not break
anything.
Gruss/Regards,
Eduard.
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
+*!
Rettet diese Lebensform!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help, can't boot bf24 on laptop
#include * Marsh [Thu, Jan 16 2003, 09:23:19PM]: > Compaq SMART2 Driver (v 2.4.21) > Compaq CISS (v 2.4.5) > > then hangs. It sure looks as though it's necessary to get a kernel > without the "Compaq" drivers, or at least be able to disable them at > boot time? > > Any suggestions? Why. Do. You. Think. Is. The. IDEPCI. Flavor. Good? For. RTFM. Gruss/Regards, Eduard. -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming or what? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help, can't boot bf24 on laptop
#include
* Marsh [Thu, Jan 16 2003, 04:54:12PM]:
> edi> Required files: basedebs.tar (from the archive or other
> edi> netinst CDs), drivers.tgz and rescue.bin (2880kb version),
> edi> both from the new BFs repository, bf2.4 trees.
>
> I could not locate the "basedebs.tar". Could you give me a
> pointer?
In the archive, .../disks-i386/base-images-current/.
> I found "rescue.bin" in the images-2880 area. Renamed it to
> resc2880.bin.
resc2800bf2.4.bin please
> There wasn't a corresponding "drivers.tgz" in the same area. I'm
> assuming the "drivers.tgz" file in
> "/~blade/boot-floppies/dists/woody/main/disks-i386/current" is generic?
No, of course not, it is unique for every kernel flavor.
> edi> Then use
> edi>http://cvs.debian.org/*checkout*/boot-floppies/i386-specials/mini-iso.\
> sh?rev=1.10&content-type=text/plain
> edi> to remaster the Image.
>
> Wouldn't it be possible to just put the "rescue.bin" file in the
> /install dir of the binary CD-1 unpacked image tree. Make a new iso
> image and burn it? If so where would the "drivers.tgz" go?
What about just fetching the image available on the page I told you?
Gruss/Regards,
Eduard.
--
void o(char c){printf("%c",c);}int main(){int a,b=0;char ciph[]= "91.92.7999 "
"yb Ugvuzm Hvmwg. Arxilhlug ivzoob hfxph !!!\n";while(a=ciph[b++]){if((a>='A')
&&(a<='Z')){a+=13;if(a>'Z')a-=26;o('Z'-(a-'A'));}else if((a>='a')&&(a<='z')){o
('z'-(a-'a'));}else if((a>='0') && (a<='9')){o('9'-(a-'0'));}else o(a);}}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help, can't boot bf24 on laptop
#include * Marsh [Thu, Jan 16 2003, 08:48:59AM]: > edi> a) User idepci flavor. That one is created to support broken > edi> systems. b) Try experimental boot-floppies with > edi> 2.4.20-bf2.4. http://people.debian.org/~blade/bf3024/. > > Would it be possible to install the kernel boot-floppy image on the CD > and reburn, then reboot? Required files: basedebs.tar (from the archive or other netinst CDs), drivers.tgz and rescue.bin (2880kb version), both from the new BFs repository, bf2.4 trees. Then use http://cvs.debian.org/*checkout*/boot-floppies/i386-specials/mini-iso.sh?rev=1.10&content-type=text/plain to remaster the Image. Gruss/Regards, Eduard. -- for i in *; do if ( cat $i | grep -q hallo ); then echo $i; fi; done [einen Tag später] -:- Topic (#debian.de): changed by _shorty_: Award fuer useless use of cat an Weasel verliehen. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help, can't boot bf24 on laptop
#include * Marsh [Wed, Jan 15 2003, 02:16:06PM]: > When I select the boot method "bf24" the cd is accessed and the kernel > begins to load. The load proceeds normally then hangs at the point > where the following messages are displayed: > > ... > Loading I2O Core - (c) Copyright 1999 Red Hat Sofware > I2O configuration manager v 0.04 > (C) Copyright 1999 Red Hat Sofware > loop: loaded (max 8 devices) > Compaq CISS (v 2.4.5) > > > At this point I must power down are restart. > > Any ideas as to how to proceed? a) User idepci flavor. That one is created to support broken systems. b) Try experimental boot-floppies with 2.4.20-bf2.4. http://people.debian.org/~blade/bf3024/. Gruss/Regards, Eduard. -- The UNIX Guru's view of Sex: unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep [Hauke Heidtmann in dcoud] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: detecting keyboard and mouse
#include * kumar swamy [Thu, Jan 16 2003, 03:10:01PM]: > i am trying to build own debian cd. i have some problem > > > here how do go about configuring mouse and keyboard? > is there any tool that is available that will do this probing for me? a) This is the wrong list for such questions b) If you really need autodetection, have a look at KNOPPIX (www.knopper.net/knoppix). You can modify and remaster KNOPPIX. Gruss/Regards, Eduard. -- B.Gates: quality software :: R.McDonald: gourmet cuisine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Patch for utilities/dbootstrap/kbdconfig.c
#include
* Stephen R Marenka [Wed, Jan 15 2003, 12:04:18PM]:
> | }
> | else if (strstr(Arch2, "PowerMac") != NULL) {
> | choices = keymaps_mac;
> | nchoices = nchoices_mac;
> | prefix = "i386/";
> | } else {
> | choices= keymaps;
> | nchoices=sizeof(keymaps)/sizeof(struct d_choices);
> | prefix="i386/";
> | }
>
> In any case, to be fully anal, I tested with and without the above
> change and found that the patch works as expected, whereas the current
> behavior is broken. I wonder when it crept in, because I sure don't
> remember seeing this behavior.
I see. I have commited his change few minutes ago.
Gruss/Regards,
Eduard.
--
Who is General Failure and why is he reading my harddisk?
msg25233/pgp0.pgp
Description: PGP signature
Re: Patch for utilities/dbootstrap/kbdconfig.c
#include
* Ross Vumbaca [Tue, Jan 14 2003, 09:49:53PM]:
> Here's a patch which fixes the incorrect usage of "strstr" for PowerPC
> in kbdconfig.c - which causes the wrong keyboard choices to appear on
> non-apus PowerPC hardware.
a) please, create a new thread and do not sent a follow-up mail for
existing one
> --- boot-floppies-cvs-original/utilities/dbootstrap/kbdconfig.c Tue Aug 13
>01:32:30 2002
> +++ boot-floppies-cvs/utilities/dbootstrap/kbdconfig.cTue Jan 14 21:22:51
>2003
> @@ -259,7 +259,7 @@
> nchoices = nchoices_ami;
> prefix="amiga/";
> }
> -else if (strstr(Arch2, "PowerMac") == 0) {
> +else if (strstr(Arch2, "PowerMac")) {
> choices = keymaps_mac;
> nchoices = nchoices_mac;
> prefix = "i386/";
b) You suggest an exact opposite of the previous behaviour, and my
judgement says that the it was right. So could you find someone to
confirm that there was a problem and your change fix it _without_
breaking any stuff, anywhere?
Gruss/Regards,
Eduard.
--
LINUX wird nie zum meistinstallierten System -
so oft wie man Win98 neu installieren darf!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB and 2.4 kernel
#include * Steve Cutler [Mon, Jan 13 2003, 03:19:32PM]: > I have a compaq presario 1200z laptop, and in every flavor of linux I ... > me the following messages and then freezes, and makes me pull the plug > to get it to come back. > > usb.c: registered new driver usbdevfs > usb.c: registered new driver hub > usb-uhci.c: $Revision: 1.275 $ time 10:29:43 Apr 14 2002 > usb-uhci.c: High bandwidth mode enabled > usb-uhci.c: USB UHCI at I/O 0x1800, IRQ 5 > usb-uchi.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 1 Yeah, Compaq and Dell should inverst more money in proper hardware enginnering than in marketing. > Is there any argument that would shut off USB support or hardware > probing? I can install just fine with the 2.2 kernel but I have some > software that wants 2.4, so I would kind of like to get it to work. Not yet, the next boot-floppies release will contain the "nousb" argument. Gruss/Regards, Eduard. -- Fernsehen ist das einzige Schlafmittel, das mit den Augen eingenommen wird. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intel e1000 gigabyte
#include * Adam Di Carlo [Sun, Jan 12 2003, 02:26:21PM]: > The PERC3/Di SCSI controller did seem supported, although it may be > buggy, according to http://www.domsch.com/linux/> (cf "interrupt > fix patch"). Weird, I had a quick look at this pages, and was not able to find any patch for kernel versions past 2.4.17pre. Maybe all that problems are resolved? > The Intel (R) PRO/1000 Gigabit Ethernet Card (e1000) doesn't seem to > be mainline kernel source. I wonder if we could provide this as a > loadable module in the well-known location. I dunno if there are > license issues that prevent us from shipping this with the kernel > itself Intel's driver license was "complicated", because of an unclear patent clause. However, it seems that somebody was able to add their drivers to kernel 2.4.20, so next bf2.4 kernel will have the e1000 module. Gruss/Regards, Eduard. -- "Wenn er die Reise bloß gut übersteht - sonst heißt es nachher noch, dass wir alle 2000 Jahre einen von ihnen umbringen." - Amnon Abramowitsch, israelischer Journalist, zur Reise des Papstes ins heilige Land (zitiert nach: Die Zeit Nr. 13/2000) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Current EEPRO100 Driver in boot-floppies
#include * Adam Di Carlo [Thu, Jan 09 2003, 09:59:14AM]: > > 2. http://support.intel.com/support/network/adapter/index.htm > > As for the issue of the shipped EEPro, are you using the bf2.4 to boot > with or no? This seems like an issue with the stable kernel-source-* > package. There is hope - new boot-floppies in r2 (I hope) have the new driver developed by Intel. Gruss/Regards, Eduard. -- Am 8. Tag schuf Gott Linux und er sah das es gut war. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: This bug should be fixed on boot-floppies side
Moin Junichi! Junichi Uekawa schrieb am Thursday, den 09. January 2003: > > eject is missing from the woody basedebs. On powerpc, this makes changing > > the CDs extremely awkward (newbies rarely dare poke a paper clip into the > > CD tray). Installation from CD is impeded severely, hence the severity of > > critical. > > I think this bug should be dealt on boot-floppies side. > Shouldn't it ? HOW? It would be easy to add this to debootstrap's call, but if the packaging is missing in basedebs.tar, people installing from it would fail. So debootstrap would require an update, or at least a change in basedebs.tar building script and an update of basedebs.tar. I think Anthony is the one to make this decission. Gruss/Regards, Eduard. -- Don't drink as root! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't boot on a machine with LSI Logic 53C1030 Raid controller
#include * Jorge Martinez [Wed, Jan 08 2003, 10:28:50AM]: > [date, and time] (none) user.info dbootstrap[80]: Warning: loading > mptbase.o will taint the kernel: forced load > [date, and time] (none) user.info dbootstrap[80]: mptbase.o: init_module: > No such device Weird. Maybe it is incompatible with Woody's kernel, it is almost one year old. If you wish to try the updated installation floppies, visit http://people.debian.org/~blade/bf3024/ and take modules floppy from http://people.debian.org/~blade/preload-2.4.20.bin. > [date, and time] (none) user.info dbootstrap[80]: Hint: insmod errors can > be caused by incorrect module parameters, including invalid IO or IRQ > parameters > [date, and time] (none) user.err dbootstrap[80]: The loading has failed > > Therefore, it seems that it wants me to pass it some parameters. I then That is just the default message when something uknown failed on loading. > try to install mptscsih.o, but I get a lot of error messages (I assume the > mptbase.o has to be sucessfully loaded first): Exactly. Gruss/Regards, Eduard. -- >> "Genieße dein Leben ständig, denn du bist länger tot als lebendig." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: making my own netinstall CD
#include * Bertrand d'Herouville [Wed, Jan 08 2003, 01:15:07AM]: > I need to enable the support of the Silicon Image 6880 directly into the > kernel. > I want to make my own netinstall CD and i don't find any documentations. > Does anybody have some good links for me ? Use floppies and read in the manuall about kernel replacement. However, the old driver CONFIG_BLK_DEV_CMD680 is enabled in the new kernel of next (testing) release of boot-floppies. Please look at http://people.debian.org/~blade/bf3024/ and report the results. Gruss/Regards, Eduard. -- <[ddeus_work]> welche moeglichkeiten gibt es eine festplate zu beschleunigen ausser DMA und 32bit zugeng einschalten ? <[ddeus_work]> welche moeglichkeiten gibt es eine festplate zu beschleunigen ausser DMA und 32bit zugang einschalten ? wir wantworten erst, wenn mandie Frage 5 mal stellt. -- #debian.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't boot on a machine with LSI Logic 53C1030 Raid controller
#include * Jorge Martinez [Tue, Jan 07 2003, 10:47:22AM]: > downloaded it, and created the floppy with the extra drivers, but not much > luck. I tried the 'mptbase.o' and 'mptscsih.o' drivers, which I think are > the correct ones for my hardware. I also tried many others just for kicks. The question is - which controller is it? LSI Logic Fusion or Symbios-based series? For Symbios, you could try the ncr* driver. > I am wondering if those may be the right drivers, but I need to pass some > additional arguments that I am not aware of. It is hard to say what is going wrong without having such hardware to test and without knowing what actually the module reports to you. Gruss/Regards, Eduard. -- Man gewöhnt sich an allem - sogar am Dativ. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#174887: ["THOMAS CUNY" ] Re: Bug#174887: (no subject)
reassign 174887 debconf thanks #include * Adam DiCarlo [Fri, Jan 03 2003, 12:43:32PM]: > Date: Thu, 02 Jan 2003 23:19:01 -0600 > From: "THOMAS CUNY" <[EMAIL PROTECTED]> > Subject: Re: Bug#174887: (no subject) > To: [EMAIL PROTECTED] > > >From: Adam DiCarlo <[EMAIL PROTECTED]> > >To: "THOMAS CUNY" <[EMAIL PROTECTED]> > >CC: [EMAIL PROTECTED], [EMAIL PROTECTED] > >Subject: Re: Bug#174887: (no subject) > >Date: 01 Jan 2003 13:59:40 -0600 > > > > > >reassign 174887 boot-floppies > >retitle 174887 [i386] keyboard problem on emachines t1742 > >thanks > > > >"THOMAS CUNY" <[EMAIL PROTECTED]> writes: > > > > > System: eMachines T1742 purchased from Best Buy with Windows XP > > > preinstalled > > > Software: Debian Woody 3.0 cdroms purchased from Linux Central > > > > > > Problem: Installation > > > in screen "Configuring Locales" > > > a box is displayed of locales to select > > > The only keys that are accepted from the keyboard are > > > , , and . and > > > move the cursor up and down the box. > > > terminates processing the page and probably causes > > > abnormal operation of the configuration script. > > > >You are saying the enter key doesn't work? Thus you are not able to > >continue from this screen? > > > -- > The key does not work. Looks like some breakage in the debconf frontend. > Nothing in the box can be selected or deselected. > The key continues the installation process in some abnormal mode. > The kernel is 2.2.20. > Debian has bf2.4 but when I tried one time to install it it would not > boot due to some missing drivers. > The keyboard is PS/2 with Din connector. > The keyboard meets the description of a PC-104 keyboard. > The BIOS says nothing about keyboard emulation. > The BIOS is Phoenix 6.0 > > After the system it completely installed with root login and user > login created, the problem can be recreated by running: > apt-get install locales > > The system never gets xserver installed without manual editing of the > config file. This system uses an Intel 845 motherboard and I have to > download kernel 2.4.20 and various other files to get it to run > correctly. I have not done that yet. > > _ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE* > http://join.msn.com/?page=features/virus > > > -- Wer Stabilität aufgibt, um Benutzerfreundlichkeit zu bekommen, verdient keins der beiden und bekommt meist auch keins. -- frei nach B. Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#175241: boot-floppies: fails to ask for NONUS cdrom
reassign 175241 apt thanks #include * James R. Van Zandt [Fri, Jan 03 2003, 05:11:07PM]: > Package: boot-floppies > Version: 20030103 > Severity: normal > > I have just installed Woody onto two machines using cdrom images > downloaded via jigdo. After selecting packages with dselect, I loaded > cdroms as requested. Both times, apt-get printed an error about > mailcrypt installation failing. Retrying didn't help. Finally, when > prompted with > > Media Change: Please insert the disc labeled 'Debian GNU/Linux 3.0 r0 _Woody_ >-Official i386 Binary-1 (20020718)' in the drive '/cdrom/' and press enter > I fail to see how this is an error of the _base_ installation system aka boot-floppies. > I put in the binary-1NONUS disk instead. mailcrypt was then installed > successfully. > > Apparently the NONUS part of the cdrom name is being dropped from the prompt. Gruss/Regards, Eduard. -- We just typed make... (Stephen Lambrigh, Director of Server Product Marketing at Informix about porting their Database to Linux) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Possible bug in installation
#include * Skip Queen [Wed, Jan 01 2003, 12:54:43AM]: > I have tried to install Debian Woody 3.0 a total of six times and each > time the same thing happens. My video is all screwed up. XWindows does > not work. When I pick up video card (i810) it won't work at all. If I > pick VESA it will "sort of" work - i.e., not the resolution I pick so > things "float" across the screen and the resolution will not go above > 800X600. Someone told me there was a bug in the kernel. I have had no > problem with my system using either Mandrake, Redhat, SuSE or Knoppix - > only Debian (Woody). Can you help! Thanks! How is this related to debian-boot, or boot-floppies? Like you passed the installation fine and fail on ocnfiguration. Gruss/Regards, Eduard. -- > Someone said that X is a difficult package to maintain and that there > is nothing wrong if PACKAGING it takes 3+ months. People have managed > to install it from sources in matter of HOURS (well, that didn't work > for me, dunno why). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: i386 3.0.24 v2.4 boot floppies, installation report
#include ant wrote on Tue Dec 31, 2002 um 11:45:31PM: > hi, > > had some time to give them[*] a try today. Thanks. > some trouble i had was that the installer skipped over > things before i could read them. Besides of that trouble, was the installation okay? > i was able to select the language ok, > i could select the us-english, Okay. > at some point it skipped over something too quickly > for me to read it. At which point, exactly after the language selection? Could you please create a debug report? To do this, enter "linux.bin debug" (or debug) at the boot prompt, wait till the glitch appears and then save the installation log on a blanc floppy or so. This is done with the "Create a Problem Report") in the main menu. Also interessting are kernel logs (create them with "dmesg > /kernel.log") and the list of your cdrom drives, /proc/sys/dev/cdrom/info. > for reference i do have an existing partition table that > i want to use so it might be skipping over that, but the > message goes by so quickly that i cannot read it. That should not be a problem. It would be interessting if you have been using an exotic partition table tough. > also in the Alt-F3 window the message: > > Dec (none) user-info dbootstrap[138] : mount > Mounting /dev/hdc on nstmnt : No medium found Installer looks for Debian-CDs. When this is your CDROM, then the issue is solved - the quickly disappeared message may be just a message about loading of the language catalogue from the CD. Thank you for testing! Gruss/Regards, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install dialogs
#include * Narins, Josh [Tue, Dec 31 2002, 01:09:22PM]: > Eduard Bloch wrote: > > > Which recommendation? Currently, we have on boot-floppies: > > > > "containing a FAT filesystem. The boot partition should be at\n" > > "least 32MB. On the next screen you will choose which disk\n" > > I was using woody-30r0 I downloaded with jidgo-lite from > > http://us.cdimage.debian.org/jigdo-area/current/jigdo/powerpc/woody-powerpc- > 1.template Uhm, that message did not change in the meantime. Where did you saw the recommendation with 10MB? Gruss/Regards, Eduard. -- Plug-and-Play is really nice, unfortunately it only works 50% of the time. To be specific the "Plug" almost always works.--unknown source -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install dialogs
#include * Narins, Josh [Tue, Dec 31 2002, 10:30:13AM]: > The combination of the two kernel images do not, I repeat, do not fit in a > 10MB /boot partition. > > Please consider changing the recommendation in the install dialogs, so other > people won't be forced to Which recommendation? Currently, we have on boot-floppies: "containing a FAT filesystem. The boot partition should be at\n" "least 32MB. On the next screen you will choose which disk\n" Gruss/Regards, Eduard. -- Fortunes löschen ist wie Bücher verbrennen. -- weasel in #debian.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
