Bug#232116: success, but a partitioning problem (and some Dutch translation remarks)
On Wed, 26 May 2004 18:36:14 +0200 Wouter Verhelst <[EMAIL PROTECTED]> wrote: > Op di 25-05-2004, om 18:50 schreef Martin Michlmayr: > > * Wouter Verhelst <[EMAIL PROTECTED]> [2004-02-11 13:32]: > > > Op wo 11-02-2004, om 00:29 schreef Bastiaan Van Eeckhoudt: > > > > I made this remark before, but no harm in repeating it: if I > > > > select nl_BE, I should get be-latin1 as default keyboard. > > > > > > I disagree, it should be be2-latin1. be-latin1 is incomplete, IMO. > > > > What's the default now and are people happy with it? > > AFAIK, nobody uses be-latin1, except, as I found out this week, on > RedHat, where be2-latin1 has been merged into be-latin1, and where > 'our' be-latin1 doesn't even exist anymore. Perhaps that's not a bad > idea. > > The difference between be2-latin1 and be-latin1 is that be2-latin1 > actually gives the characters as they appear on the keyboard, while > be-latin1 does nothing more than an approximation. This has bitten so > many people, that it's one of the oldest entries in the > be.comp.os.linux FAQ... > The default now is be-latin1, you should probably change it to be2-latin1 then. I use us or uk keyboards myself, so I don't really care :) > > > > GRUB dialog translation: "niew-geÃnstalleerd" should be "net geà > > > > nstalleerd". This is consistent with later occurences of the > > > > term."schif" should be "schijf" > > > > "gebruiken wilt" should be "wilt gebruiken" > > > > > > > > The final screen before rebooting: > > > > "veranderd" should be "verandert" > > > > "op-maat-gemaakte" should be "op maat gemaakte" > > > > "het installatiemedia" should be "het installatiemedium" > > > > > > Please take these to the debian-l10n-dutch mailinglist, where we > > > discuss translations (BTW, help is still welcome there :-) > > > > Did you come to agreement about these? > > There aren't really many things one could disagree with; I merely > mentioned this to make Bastiaan aware of the l10n-dutch mailinglist. I will send some more comments on the current state of the translation to the list. Bastiaan > > -- > EARTH > smog | bricks > AIR -- mud -- FIRE > soda water | tequila > WATER > -- with thanks to fortune > -- Bastiaan Van Eeckhoudt bastiaan[at]vaneeckhoudt[dot]net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#232116: success, but a partitioning problem (and some Dutch translation remarks)
On Tue, 25 May 2004 17:54:41 +0100 Martin Michlmayr <[EMAIL PROTECTED]> wrote: > * Bastiaan Van Eeckhoudt <[EMAIL PROTECTED]> [2004-02-11 00:29]: > > At some point during hardware detection, my screen stayed blue > > without a dialog for quite a long time, I would have thought it was > > hanging if the CD drive wasn't making a lot of noise. I was using an > > old, flaky drive, maybe it was having trouble reading some files. > > Can you please try a current image from > http://gluck.debian.org/cdimage/testing/sarge_d-i/ and see if this is > still the case? Is there no progress bar on the screen at all? I can't try the install on the same machine, since it's in use. I'm running the may 26 build on my laptop, and that still has some short blank screens between the cd drive detection and loading of installation modules. maybe it's just due to slowness of the cpu (this laptop is a pentium 233) or cd drive that it takes a while? > > > When I selected my drive for partitioning, I got a message about no > > partition table being present (this was a brand new, unused disk), > > and if I wanted to start with an empty one. Selecting yes or no > > didn't make a difference, I got a red screen telling me partitioning > > failed. I switched to console, started up fdisk, made a new empty > > DOS partition table, and quit fdisk. After this cfdisk ran without a > > problem. > > I suppose you won't be able to reproduce this, or do you have a spare > disk on which you can remove all partitions? I removed the partition table on the laptop, and now the disk partitioner deals with missing partition tables without a problem. > > > Then my system rebooted. > > I got a message: GRUB loading stage 1.5 > > Then 15-20 seconds nothing. I was ready to hit the reset button and > > grab a rescue disk, and I got another message: > > GRUB loading, please wait... > > Again, 15-20 seconds nothing, but I had some more patience this > > time. > > Can you see if it still takes so long? This might be a bug in GRUB > (rather than in the installer). Can you try the new image and let me > know if this is still there? no problems in this build on the laptop > > > When selecting the timezone, Europe still gave me Australian cities. > > I though this was fixed at the time of my previous report a month > > ago? > > I'm pretty sure it's fixed now. yes this is fixed > > > One thing I noticed after the install is that I wasn't asked if I > > wanted stable, testing or unstable. Do I need to select expert to > > get this question? > > Why would it ask after install? If you use a netboot image (without > any debs), it will ask during the installation; but normally it will > just take the .debs from your CD and then default to the distribution > those .debs are from. I meant that I only noticed this after the install was done, and I seemed to remember being asked the question during an earlier install. Probably a netboot vs. businesscard image thing. The installation on my laptop went flawlessly now, nice work. I have some more comments on the translation. I'll send those to the dutch list. Bastiaan > -- > Martin Michlmayr > [EMAIL PROTECTED] > -- Bastiaan Van Eeckhoudt bastiaan[at]vaneeckhoudt[dot]net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#232116: success, but a partitioning problem (and some Dutch translation remarks)
Package: installation-reports INSTALL REPORT Debian-installer-version: 20040208 sarge-i386-netinst.iso Date: 20040210 2100 Method: boot from CD, apt install with ftp Machine: Asus Pundit Processor: Pentium 4 2.66 GHz Memory: 512MB RAM, 160GB HDD Root Device: /dev/hda Root Size/partition table: /dev/hda1: 10GB / /dev/hda2: 512MB swap /dev/hda3: 150GB ext3 /mythtv Output of lspci: Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it I did another Dutch install on a new machine. I made this remark before, but no harm in repeating it: if I select nl_BE, I should get be-latin1 as default keyboard. At some point during hardware detection, my screen stayed blue without a dialog for quite a long time, I would have thought it was hanging if the CD drive wasn't making a lot of noise. I was using an old, flaky drive, maybe it was having trouble reading some files. When I selected my drive for partitioning, I got a message about no partition table being present (this was a brand new, unused disk), and if I wanted to start with an empty one. Selecting yes or no didn't make a difference, I got a red screen telling me partitioning failed. I switched to console, started up fdisk, made a new empty DOS partition table, and quit fdisk. After this cfdisk ran without a problem. The translation of some items in the bottom menu in cfdisk is too long for the [ ] brackets, and the right bracket gets overwritten, and one of the entries (maximiser I think) is chopped off. This doesn't look very nice. After writing my table in cfdisk, it gave me a message at the bottom of the screen, but it was covered in the middle by the help text for the [bootable] menu item. I could make out something like "No primary partition ... not boot" When selecting the filesystems, the dialog talks about wisselgeheugenruimte, but when you select this, the partition is indicated as "swap". A new user might not know that both terms mean the same thing. This makes me wonder: do you need to make a partition type 82 in cfdisk to be able to make it a swap partition later? The types are not translated in cfdisk in any case. I then got another blue screen without dialog while it was creating my filesystems. A dialog telling you to be patient would be nice here. GRUB dialog translation: "niew-geÃnstalleerd" should be "net geà nstalleerd". This is consistent with later occurences of the term. "schif" should be "schijf" "gebruiken wilt" should be "wilt gebruiken" The final screen before rebooting: "veranderd" should be "verandert" "op-maat-gemaakte" should be "op maat gemaakte" "het installatiemedia" should be "het installatiemedium" Then my system rebooted. I got a message: GRUB loading stage 1.5 Then 15-20 seconds nothing. I was ready to hit the reset button and grab a rescue disk, and I got another message: GRUB loading, please wait... Again, 15-20 seconds nothing, but I had some more patience this time. The GRUB screen finally appeared, and booted automatically. When rebooting after the installation was complete, I didn't get these long pauses, so it's a mystery what was going on. In the top left of the screen there's an untranslated "Debian Configuration" title There's a text somewhere with a quite long sentence: "Het zal starten met de basis -- ... -- daarna zal het ..." I would split this sentence into "Het zal starten met de basis: ... . Daarna zal het ..." Also change "extra software nodig om" in "extra software die nodig is om" When selecting the timezone, Europe still gave me Australian cities. I though this was fixed at the time of my previous report a month ago? The apt configuration had Yes/No options in stead of Ja/Nee. I didn't notice (but didn't really check) this in other dialogs. In the "software selectie methode" dialog, "voorgedefiniÃerd" should be "voorgedefinieerd" Also the aptitude explanation doesn't fit the screen. The pcmcia-cs and exim4 dialogs are untranslated. Final screen: The sentence "U kunt nu aanmelden ... prompt" is missing a full stop. One thing I noticed after the install is that I wasn't asked if I wanted stable, testing or unstable. Do I need to select expert to get this question? Bastiaan -- Bastiaan Van Eeckhoudt bastiaan[at]vaneeckhoudt[dot]net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#226730: Problem with wireless pcmcia network card and keymap
Hi, The translation stuff seems to be fixed, or will be fixed soon. However, I didn't see much response related to my network and keymap problems. For the networking: the problem (or a part of the problem at least) seems to be that during boot (rcS), PCMCIA isn't started. /etc/network/interfaces however contains "auto eth0" and tries to run the dhcp client on this interface, before it is possible. The way to do it (according to the FAQ in the pcmcia-cs package), is to remove the auto keyword for PCMCIA network interfaces. When PCMCIA starts in runlevel 2, it will run ifup eth0 and get the network running. I'm not sure how this fits in the installer boot process but I guess you will need to handle this distinction between regular and PCMCIA interfaces. Another thing I noticed: At the first boot, hardware detection is executed. This causes the pcmcia and orinoco_cs modules to be loaded. I then get the screen asking me which network module to use. When I select orinoco_cs there, I get a red screen telling me there's no network card. I guess this is because modprobe orinoco_cs fails because the module is already loaded. If I select none of the above, I don't get an error, but I'm dropped to the menu where you can choose which installation step to perform. Selecting the hilighted step makes the install continue fine. The same thing happens when I use my pcnet_cs card. The keymap problem: the error I am getting is a bug in console-tools in testing and unstable. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226742 Bastiaan -- Bastiaan Van Eeckhoudt bastiaan[at]vaneeckhoudt[dot]net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#226730: Problem with wireless pcmcia network card and keymap
It was already renamed to initrd.old on the disk, but lilo.conf still refered to initrd.img. I also have a warning about /proc/partitions using ide/host0/... and lilo.conf having /dev/hda I manually fixed lilo.conf and rebooted The old kernel still doesn't solve keymap and network problems... My keyboard is set to us instead of uk, and I have to run either /etc/init.d/pcmcia restart or /etc/init.d/networking restart to get it to work. I can provide dmesg output or the debian-installer logs if needed. Greetings, Bastiaan -- Bastiaan Van Eeckhoudt bastiaan[at]vaneeckhoudt[dot]net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
