> > Sound like bugs in the driver. I think I've seen messages on the kernel > list about similar problems, but I don't really track those. Your best > bet is to google for similar issues and see if a fix is available > somewhere that can be included in Debian. At the moment I feel good with the bcm5700 - so I do not invest time (which I do not really have) in searching. But I'm sure I will when I run into troubles... > > Same happens during installation, but the > > DHCP-Timeout seems to be too low, so I never get a network uplink (also > > not at the vc2). > > You should be able to hit retry then. Also, with the latest versions of > the installer you can increase the timeout from the default 15s using > "netcfg/dhcp_timeout=xx" as boot parameter. Yes, retry was possible - still, did not help a lot (except from consuming time). > > The bcm57xx is a driver delivered directly from broadcom, there is also > > a debian (nonfree-)package for that > > Right. That means we cannot support it in the installer. We may add > options to load non-free drivers/firmware in the future though. Sounds interesting to me (would be the same as in Windows, where "driver disks" are possible; but then there should be also a tool or Howto to convert the various forms of drivers - disk image, ram disk, binary file...; because you cannot do that, if you are just about to install your first linux PC... - and it should not be limited to disk as in Windows, as I don't have one, for example) - a lot for the wish-list, anyway ;-) > > That would be everything in /var/log/installer? > > Not everything :-) syslog and messages should do. Ok, attached. Hope you can make something of it (I can't) - hopefully my manual interactions from con are not too confusing/disturbing. > > I plan to buy a 2nd set with the same config (if my employer agrees to > > pay > > Great. A usefull test would be to try the next Beta version we hope to > release soon (soon is flexible though). It will be announced on the d-i > project page. A separate installation report would probably be best with > reference to this one (unless nothing has changed; in that case an update > to this one is fine). Fine, will do that and take a close watch of the installer homepage. Regards, Christian
Attachment:
syslog.gz
Description: Binary data
Attachment:
messages.gz
Description: Binary data