Thanks golinux. I've learned to not do a c/p from an .odt document into yahoo
mail.Here's the reformatted version. (Sorry folks.)
----- Forwarded Message -----
From: "[email protected]" <[email protected]>
To: dan pridgeon <[email protected]>
Sent: Tuesday, March 20, 2018 2:18 PM
Subject: Re: [DNG] Ascii install problems (solved?). Was: Install experiments
with FAT partition
Hi Dan,
Just a note for formatting. ...
I don't know what could have caused this.
On 2018-03-20 13:16, dan pridgeon wrote:
I've encountered several problems while trying to install Ascii.
- (intermittent) failure to detect CD-rom drive. (retries worked)
- (once) failure-to-mount partitions – which caused bizzare behavior while
using the Graphical install. The failure-to-mount problem migrated to the next
drive on the next several partitions.
BTW, screen shots taken during Graphical mode do not appear to be
preserved after installation.
- (once) debootstrap problem indicating not a clean disk. Reformatting
(twice) did not help.
- (once) The install process, just before finishing, dumped me out into a TTY1
terminal.
- (consistent failure) After 'successful' install, the system is extremely
slow. (wicd window took ~18 seconds to open).
- (consistent failure) wicd does not find any access points.
I began to suspect that something was wrong with the netinstall.iso USB
thumb drive since the sha256sum is always correct. I suspected
that the data rate might have something to do with the problem. I burned the
netinstall.iso to a 128GB USB 3.0 thumb drive. I was sure that it was fast
enough to keep the USB 2.0 bus saturated, and that this might make the USB
device driver happy(er) - if that was a problem.
I have now done nine installs without error.
It appears that the USB data stream is being corrupted and not crashing the
system in the process. Could it be that data under-runs or other speed related
problems,
are causing unexpected behavior of the device driver? I would like to look
into this further
but I don't know yet how to break into the install process to get into some
debug mode, or to just look at /var/log/syslog at the point of failure to help
identify the problem(s).
Any help would be appreciated. Still learning. Feel free to contact me off
list.
The issues surrounding the use of FAT partitions are explained ina previous
post but the jist is this:
- partman does not offer a force-format option for FAT partitions.
This means that the only way to (re-)format a FAT partition is to change the
fs type.
BTW, if you don't format a FAT partition during the install process, partman
will scan it
and declare an "uncorrected errors found” error.
I don't know what this means or how it might affect the installation if left
uncorrected.
- partman's resize option for FAT partitions does not work correctly in all
cases.
The workaround is to change it to an ext(i) fs type, resize it as desired,
and then change it back to a FAT fs.
Thanks for devuan.
_______________________________________________
Dng mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
