Bug#450836: installation-reports: Does not allow ethernet over firewire
Hello Maximilian, On Thu, Nov 15, 2007 at 01:24:32PM +0100, maximilian attems wrote: On Thu, Nov 15, 2007 at 12:53:31PM +0100, Frans Pop wrote: On Thursday 15 November 2007, Frans Pop wrote: 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. Well, for *me* at least this is not minor, because it means I need to rebuild the kernel before I can start installing, as I've currently only have a spare firewire cable (which I frequently used with various kernels already). At which state do you reconsider eth1394 support? Given that the developer of this module is a DD I hope this happens soon. see discussions on d-kernel, nobody spoke up when the anncouncement about missing eth1394 was declared. It would be kind if you could announce this a little more prominently (e.g. on http://www.debian.org/devel/debian-installer/ ) as I do not read d-kernel. Thanks! Greetings Helge -- Dr. Helge Kreutzmann [EMAIL PROTECTED] Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#450836: installation-reports: Does not allow ethernet over firewire
Your report is missing some basic information. Please always attach the hardware-summary that is created at the end of an install (or can be created on demand by running the save debug logs component from the main menu of the installer). It can be found in /var/log/installer after installation or in /var/log/ during installation. On Sunday 11 November 2007, Helge Kreutzmann wrote: A)No eth1394 driver for ethernet over firewire. I routinely use this and actually do not have a network cable arount ATM, so it is the only way to connect (and my main system proxies connections via firewire into the internet just fine). During installation, I do not see the network interfaces for firewire, nor do I find the modules, essentially breaking the netinst idea. I do see the device on my main system in the logs, so the connection is fine). After install, I see that # CONFIG_IEEE1394 is not set This is probably because the Debian kernel has been switched to use the new firewire stack, which uses: CONFIG_FIREWIRE CONFIG_FIREWIRE_OHCI - module firewire-ohci CONFIG_FIREWIRE_SBP2 - module firewire-sbp2 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. B)After setting up crypto and lvm volumes, I choose by accident one of the crypto volumes and was told, this does not work and I could choose back or continue. I chose back and the installer hung. After Ctrl-C I was in the main menu (and in english[1]). I cannot reproduce this. Please describe in detail the steps needed to reproduce this situation. Choosing Partitioning disks again, the progress bar with Starting up the partitioner hung at 52% (showing Please wait). Ctrl-C did not work now, so I rebootet. Using ctrl-c is not really supported in the installer. If you really need to kill processes, switch to a debug console and selectively use kill instead. However, it is never guaranteed that you can continue the installation after that. Without additional information this is impossible to trace. If you can reproduce it, I can give you some instructions on how to get that info. A start would be the output of 'ps' at the time the system is hanging. C)Second attempt, now all partitions properly created (still present on disk), but forgot to assign mount points for crypted volumes. I said yes to return to the partitioning, but after creating of the file systems, I was dropped on the main menu (I had returned earlier when I missed to create a New World boot partition) This is somewhat expected after certain error situations. You can always get back to the default mode using the menu option change debconf priority and setting it to high. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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]
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#450836: installation-reports: Does not allow ethernet over firewire
Package: installation-reports severity: important I installed a PowerBook G4 with a recent netinst: -rw-r--r-- 1 helge helge 227418112 2007-10-30 22:35 debian-testing-powerpc-netinst.iso md5sum: e9495d1a6997f9fc8aa7ad85df67a365 debian-testing-powerpc-netinst.iso (This is a 7447A, altivec supported PowerPC machine). The following major issues appeared: A)No eth1394 driver for ethernet over firewire. I routinely use this and actually do not have a network cable arount ATM, so it is the only way to connect (and my main system proxies connections via firewire into the internet just fine). During installation, I do not see the network interfaces for firewire, nor do I find the modules, essentially breaking the netinst idea. I do see the device on my main system in the logs, so the connection is fine). After install, I see that # CONFIG_IEEE1394 is not set I definitly installed on PPC via firewire before, but probably pre-sarge. And at least up to 2.6.19.2 this worked fine (tried with various kernels, both Debian and self rolled ones). Since firewire is very popular on PPC (at least on apple machines) I see no reason not to support it, especially since this worked before (i.e. this is a regression). B)After setting up crypto and lvm volumes, I choose by accident one of the crypto volumes and was told, this does not work and I could choose back or continue. I chose back and the installer hung. After Ctrl-C I was in the main menu (and in english[1]). Choosing Partitioning disks again, the progress bar with Starting up the partitioner hung at 52% (showing Please wait). Ctrl-C did not work now, so I rebootet. C)Second attempt, now all partitions properly created (still present on disk), but forgot to assign mount points for crypted volumes. I said yes to return to the partitioning, but after creating of the file systems, I was dropped on the main menu (I had returned earlier when I missed to create a New World boot partition) Please clone and reassign as necessary and do not hesitate to ask for more information. -- Dr. Helge Kreutzmann [EMAIL PROTECTED] Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
