Bug#196293: installation-reports: trying debian-installer (2003-06-04)
Hi,
On Tue, Jun 10, 2003 at 11:04:11AM +0200, Martin Sjögren wrote:
> > I selected German (Germany) as language. The German Umlauts don't work. Some
> > are just not printed, some look like UTF8 on non UTF-8 aware consoles.
>
> Indeed, the Unicode support is sketchy at best right now.
Another tiny buglet: I'm not sure if this is related but when the
CDROM is detected, I'm getting the following output:
Detecting HW and loading kernel modulesurde erkannt
The last part could be "wurde erkannt" (=was detected). Looks funny :-)
> > I need the rtl8139 kernel module wich doesn't seem to be available on the
> > CD. I'm asked for a driver disk which I find a bit confusing when booting from
> > a CD that should contain all the drivers. So no network on this machine...
>
> As you noted in the other mail, the module is called 8139too in 2.4,
> this problem will go away when we've finished migrating to discover 2.
Ok. I probably wouldn't have noticed that all if the manual loading
of 8139too had worked.
With netinst 2003-06-09, the problem with the 8139too (and other)
modules not found because they are searched in /kernel is fixed.
Loading 8139too when selected from the list manually works now.
> > The installation program prints '{MODULE}' and '{CARDNAME}' literally. I guess
> > these are variables that should be expanded?
>
> Hrrm, yes. That should work. Strange. Can't say I've seen that fail...
Still happens with the netinst iso from 2003-06-09.
> > ide-scsi is tried to load but fails (probably because the IDE CDROM is already
> > claimed by the IDE CDROM driver?)
>
> Dunno, I haven't had any problems... Hm. CC:ing Petter who's written the
> hardware detection udebs. Petter, any ideas?
With the latest version I haven't seen that problem.
> > Now I tried to "configure and mount partitions". After I selected one
> > partition for an ext2 fs and one for swap, I got "Can't open
> > mkfs.ext2". "Create filesystems (OLD) also bailed out (no error message).
>
> Veeerry strange! Since it offers ext2 as a choice, that means that
> a) ext2 is in /proc/filesystems, and
> b) /sbin/mkfs.ext2 exists
Still happens. This time there already was an ext2 fs on that
partition that was created by a woody install I did some days ago. I
got the following message:
Failed to create ext2 file system on /dev/ide/host0/bus0/target/0/lun0/part5
An error occured when the ext2 file system was created on
/dev/ide/host0/bus0/target/0/lun0/part5. Please see tty3 or /var/log/messages
for more information.
tty3 shows:
partconf: Creating ext2 files system on /dev/ide/host0/bus0/target/0/lun0/part5
/bin/sh: Can't open mkfs.ext2
mkfs.ext2 does exist in /sbin but if I try to run it in the shell I
get the exact same error from /bin/sh. Maybe that's because its size i
0 (zero) bytes?
Now I tried ext3 (as that isn't 0 bytes) but I got an error about the
swap space (device or resource busy). Looks like it was already
activated from the test with ext2 and it can't handle that case. So
the ext3 wasn't created.
Calling mkfs.ext3 manually worked however.
> > So no new fs on my hard disk.
> >
> > I wanted to save /proc/pci, partition info etc. on a floppy, but a mount
> > /floppy failed. Looks like it couldn't detect the filesystem on the disk
> > (probably msdos?)
>
> I haven't had any problems with this either... Couldn't you just say
> mount -tmsdos?
It accesses the floppy for about 10 seconds and tells me "invalid
argument" after that. I tried some different disks so I don't thinks
it's because they are corrupt.
After the installation of sarge succeeded and a reboot I could access
the floppy without any problem. But when I boot from the
debian-installer CD it doesn't work.
> > As I didn't have any more options I wanted to stop the installation. But there
> > is no menu item for that kind of action :-) And pressing ctrl-al-del is also
> > blocked.
>
> The ctrl-alt-del issue should be fixed by now, at least in CVS. I think.
This time installing the base system also worked. Well, at the end it
told me "I: Base system installed successfully.". But there was no
option on how to go on. Pressing some keys didn't work. ctrl-c took me
back to the menu.
Installing the kernel seems to have worked.
When I tried to install lilo, I got the following funny German
message:
"Auf welchem Gerät soll LILO den Totoblock installieren?" (Probably
should mean: On which device LILO should install the boot block?)
"Totoblock" does not mean boot block. The "Deutscher Lotto- und
Totoblock" is in fact the organization of the German national lottery.
"Bootblock" is probably the correct "translation".
The question on which device the boot block should be installed will
be scary for anyone who has never installed Debian before or knows the
/dev/ide/ syntax :-)
rebooting and base-config worked ok. Yeah! the fisrt time I could
install sarge with debiab-installer :-)
Summary:
Initial boot worked: [O]
Configure network HW: [O] (manually)
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [E]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
Bye,
Henning
Reply to: