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
Reply to: