Bug#451230: linux-image-2.6-s390 / qeth - HSI-interface doesn't come up after reboot
severity 451230 normal tags 451230 moreinfo s390 never had automatic setup of devices. Please show your configuration. The debian installer sets up a configuration in /etc/sysconfig/hardware which lists all hardware devices which are used during the installation. Bastian --- Our HSI-NIC is integrated in the path /etc/sysconfig/hardware with config-ccw-0.0.0800. The only content in this file is: CCWGROUP_CHANS=(0.0.0800 0.0.0801 0.0.0802) Is this correct that the file has only one line? Excursion: == Sorry, we didn't describe our environment sufficiently. We running our Linux servers under Z/VM in different LPARs. The NICs and other hardware (DASDs) are defined in Z/VM for every guest (Linux). The physical hardware adapters so are mapped in virtual addresses. We aren't running Linux natively on a LPAR. We use these Linux-servers in a productive environment. At maintenance work (for example by a power on reset) we load the Linux guests from one LPAR (which will be maintained) to another LPAR. So we have the need that it works well. In SLES9 the HSI-NIC comes up while rebooting the linux-server by IPL from the Z/VM an we have our network connectivity. But we aren't happy about SLES10 and so we are looking for an alternative distribution. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#450836: installation-reports: Does not allow ethernet over firewire
clone 450836 -1 reassign -1 linux-2.6 thanks On Thursday 15 November 2007, Frans Pop wrote: Those should all be set for powerpc and should also be available during installation. Please check: - whether these modules are present - whether they are loaded automatically or not - if not, whether loading them manually gives you firewire support If the new firewire stack does not work for powerpc, that will have to be discussed with the kernel team. It looks as if the new stack just does not have any Ethernet support (yet?). I also no longer have a firewire Ethernet device on my x86_64 system. This is confirmed on: http://wiki.linux1394.org/JujuMigration That same page lists several issues with the new stack when compared to the old one and also has the following recommendation: ! ! Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux ! distributors (kernel packagers) as well as to regular users is: Build only ! the old IEEE 1394 drivers. Please activate the old stack again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#450836: installation-reports: Does not allow ethernet over firewire
On Thu, Nov 15, 2007 at 12:53:31PM +0100, Frans Pop wrote: On Thursday 15 November 2007, Frans Pop wrote: Those should all be set for powerpc and should also be available during installation. Please check: - whether these modules are present - whether they are loaded automatically or not - if not, whether loading them manually gives you firewire support If the new firewire stack does not work for powerpc, that will have to be discussed with the kernel team. It looks as if the new stack just does not have any Ethernet support (yet?). I also no longer have a firewire Ethernet device on my x86_64 system. This is confirmed on: http://wiki.linux1394.org/JujuMigration That same page lists several issues with the new stack when compared to the old one and also has the following recommendation: ! ! Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux ! distributors (kernel packagers) as well as to regular users is: Build only ! the old IEEE 1394 drivers. Please activate the old stack again. the new stack is very promising, we will reconsider later if no eth1394 shows up, for now that's just a minor regression. see discussions on d-kernel, nobody spoke up when the anncouncement about missing eth1394 was declared. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451367: installation-reports: Does not allow ethernet over firewire
(Moving thread to cloned BR.) On Thursday 15 November 2007, you wrote: the new stack is very promising, we will reconsider later if no eth1394 shows up, for now that's just a minor regression. No, that is not a minor regression. Half the functionality of the old drivers is missing! see discussions on d-kernel, nobody spoke up when the anncouncement about missing eth1394 was declared. What discussion? I googled for it and after skimming through about 20 pages I still have not found it. What I _did_ find is several other reports of problems with the new stack, two of which complain about missing Ethernet support: - http://lists.debian.org/debian-kernel/2007/10/msg00414.html - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441206 - http://www.debianhelp.org/node/9328 So Google does not help. Let's check the changelog: linux-2.6 (2.6.22~rc5-1~experimental.1) experimental; urgency=low * Enable the new firewire stack labeled to be more simple and robust. -- Bastian Blank [EMAIL PROTECTED] Tue, 19 Jun 2007 17:49:52 +0200 Strange. No mention of the fact that the new stack is [1]: - experimental - not recommended for distributions by its upstream developers - has a _major_ regression in it's lack of Ethernet support - lacks userspace integration - has had only limited testing Hmm. One more try. Let's check the mailing list for June. Ah, a hit! http://lists.debian.org/debian-kernel/2007/06/msg00079.html No discussion though (at least, I don't usually call a single message a discussion). Not all that surprising that no users spoke up since the message is only to the kernel list, which is a _developer_ list. I'd say the lack of response is a better indication of the fact that other kernel developers did not really care about the change than about what users think of it. What you are forgetting is that unstable kernels also migrate to testing and that Debian has been promoting testing as an alternative to stable for users who want a more current desktop, but don't want to deal with the frequent breakage of packages in unstable. Thanks for confirming that the kernel team cares more about the latest and greatest upstream than about its users. Debian unstable and testing are _not_ testbeds for upstream development! [1] http://wiki.linux1394.org/JujuMigration -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#450836: installation-reports: Does not allow ethernet over firewire
Processing commands for [EMAIL PROTECTED]: clone 450836 -1 Bug#450836: installation-reports: Does not allow ethernet over firewire Bug 450836 cloned as bug 451367. reassign -1 linux-2.6 Bug#451367: installation-reports: Does not allow ethernet over firewire Bug reassigned from package `installation-reports' to `linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#433187: [Fwd: Re: Fix for sparc64 cpu hangs.]
On Tue, Nov 13, 2007 at 05:53:51PM -0700, dann frazier wrote: A sparc build hasn't appeared in the snapshots repo yet, but I've posted a build of the latest here: http://people.debian.org/~dannf/bugs/433187/sparc-result/ A sparc snapshot is now available on buildserver.net, so I'm going to remove this one to free space on gluck. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425851: Manifests with VMWare Server 1.0.3, too
I encountered this bug when running VMWare Server 1.0.3 on CentOS (4 or 5, I think). The guest OS was a fresh Debian Etch AMD64 system (using 2.6.18) which I dist-upgraded to Lenny (using 2.6.22). The 2.6.22 kernel could not detect the SCSI drive, with the same diagnostics as reported by OP. The 2.6.18 kernel booted fine. Upgrading VMWare Server to 1.0.4 resulted in 2.6.22 booting correctly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
