Bug#288902: Slight install glitch, some suggestions
Package: installation-reports Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc2/sarge-i386-netinst.iso uname -a: Linux mofo 2.4.27-1-386 #1 Wed Dec 1 19:43:08 JST 2004 i686 GNU/Linux Date: Jan 1 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? Boot from cd. Network install: ftp://ftp.us.debian.org, ftp://debian.uchicago.edu no proxy Machine: Penguin Computing Processor: Dual 600MHz Pentium III Memory: 1GB RAM Root Device: SCSI sdb Root Size/partition table: l# sfdisk -l /dev/sdb Disk /dev/sdb: 2213 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sdb1 0+ 5 6- 48163+ 83 Linux /dev/sdb2 6 491 4863903795 83 Linux /dev/sdb3492 540 49 393592+ 82 Linux swap /dev/sdb454122121672 13430340f W95 Ext'd (LBA) /dev/sdb5541+ 16341094- 8787523+ 83 Linux /dev/sdb6 1635+ 2212 578- 4642753+ 83 Linux # df -h FilesystemSize Used Avail Use% Mounted on /dev/sdb2 3.7G 107M 3.4G 4% / tmpfs 443M 0 443M 0% /dev/shm /dev/sdb1 45M 9.3M 33M 23% /boot /dev/sdc2 17G 14G 2.5G 85% /home /dev/sdb5 8.3G 1.3G 6.6G 17% /usr /dev/sdb6 4.4G 397M 3.8G 10% /var /dev/sda21012M 783M 178M 82% /mnt/sda2 /dev/sda6 4.0G 3.1G 724M 82% /mnt/sda2/usr /dev/sda71012M 456M 505M 48% /mnt/sda2/var Output of lspci and lspci -n: # lspci :00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) :00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) :00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:10.0 SCSI storage controller: Adaptec AIC-7892B U160/m (rev 02) :00:12.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 07) :00:14.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) :01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) # lspci -n :00:00.0 0600: 8086:7190 (rev 03) :00:01.0 0604: 8086:7191 (rev 03) :00:07.0 0601: 8086:7110 (rev 02) :00:07.1 0101: 8086:7111 (rev 01) :00:07.2 0c03: 8086:7112 (rev 01) :00:07.3 0680: 8086:7113 (rev 02) :00:10.0 0100: 9005:0081 (rev 02) :00:12.0 0401: 1274:1371 (rev 07) :00:14.0 0200: 8086:1229 (rev 08) :01:00.0 0300: 102b:0525 (rev 04) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it 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: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Network configured manually. Hard drive partitioned manually. Boot loader installed to floppy. After reboot (?), I believe in base-config where you choose what kind of system you want, I mistakenly pressed the return key instead of the space bar when trying to mark X windows desktop system, and then got nothing installed. So, wound up using apt-get to install x-window-manager and gnome manually. Somewhere in there a do-over question would have been really helpful, I only now feel like I can remember base-config (or is it tasksel) that I would need to type to recover from this error. And it's _easy_ to make the mistake of not pressing space to mark the item. Maybe at the very beginning of the install the user could get, by default, a little training in pressing the space bar to mark things and using the tab button to move around. Yup, I think a little Do you want me to show you how to use this installation program [Y,n]: at the beginning would be a good thing. Nobody reads the instructions even when they're on the screen at the bottom when you need them. (Face it, we all feel clever when we're working with a program and get stuck, and then solve our problem by actually reading the instructions at the bottom of the screen.) The tuitorial can force the user to learn to use the tab key, the space bar, and the return key just by requiring their use. (One page with instructional text, user must un-mark a check box, mark another, tab to an appropriate button and press enter to proceed.) For an enhancement, the installer could optionally start by testing hardware. Using memtest and badblocks. (I prefer
Bug#288701: Selected keymap not used for gdm, gnome or kde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 January 2005 18:59, Christian Perrier wrote: There is no real solution to this. Console and X keymaps are currently disconnected. A workaround is bringed by the localization-config package which is run at the end of the install and preseeds the X settings with defaults related to the chosen locale (roughly language+country combination). apt-get install localization-config update-locale-config right ? (will test later... need breakfast first :) Given that this is a very well known problem, we should maybe document this in the install manual, if not already done. Frans? Absolutly. Together with 'apt-get install xdebconfigurator xdebconfigurator. But this really (= no user interaction needed) only helps when preseeding this as base-config/early_command - but of course it very good to know even when not preseeding. And it will be easier to close such bugs reports with RTFM, paragraph xy :-) regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB3QDLUHLQNqxYNSARAhhgAKDJH5LT6cESSFtRgg3jNtKiOCtx/gCglI36 lxSMKkjdhyhM0RuvdZZKsbQ= =zYyM -END PGP SIGNATURE-
Bug#278186: Should we correct 278186?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Tuesday 04 January 2005 19:19, Christian Perrier wrote: About b) I have seen very few people even mentioning they are working with preseed files in localized environments. For sure there are some and we may break their work, but I think these people are skilled enough for just asking in -boot if they experience problemsand as you said, we'd better fix this now...:-) When it comes to automated installs, they're simply very difficult to do currently in localised environment, so I really think this patch is worth to go in sarge. seconded. regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB3RIjUHLQNqxYNSARAvUvAKCLT2TmOqVZJbAsJFTpDLRKDAClDgCeMbJo 4I5njns6X+LmSZCkdm9ws64= =VXGd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dual-boot 64-32bit
I decided to start again with a fresh install, erasing the whole disk. I started fresh with demudi and after trying various options in the BIOS and boot flags I tried boot: linux noapic nolapic This worked and I was able to reboot. Installed all packages. I have a problem starting x, but I don't think that's a boot problem... Then I installed debian-amd64 in the free space on the disk. That booted ok. Now I can boot into either system, demudi-1.2.1-rc1-i386 or debian/pure64/sid. I selected multi-user for each system so the partition table is quite large. i have left the /etc/fstab files alone. Norv -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 January 2005 20:44, Joey Hess wrote: I use a consistent set of rules, as documented in the tasksel source, for all decisions involving the contents of tasksel tasks. If I just you are refering to ./tasksel-$version/tasks/README ? The way I read it (I might be wrong), it says nothing against having a full desktop-task (with kde, gnome, fvwm and gnustep) and single-wm/de-Desktop-tasks. I don't see a problem if full-desktop, kde-desktop, gnome-desktop, whatever-desktop are all available and if they overlap. If a user selects some overlaping tasks (for instance full-desktop and kde-desktop), that's a little strange but would resolve well. So, I don't see a problem when just adding more tasks (for now as a workaround), but please don't hesitate to point it out to me. And/but I do realize the frozen state of tasksel/d-i and that this is an important issue. (We should release sarge, not break it! ;) regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB3SR2UHLQNqxYNSARAg1BAJ9ZkJZV+RTYgi1+JBciVU0+iCPcoQCeKjBd FlHml6bgt8cvUbtydnEylC4= =ODlv -END PGP SIGNATURE-
Re: Desktop task broken on !(i386/powerpc)
[Christian Perrier] We're dealing here with a quite informal population of people wanting to easily install Debian and indeed we're probably having hard times in figuring out exactly what they might expect. Yes. And some of these do not want the congintive strain that options they do not understand will give them. All extra options and flexibility will scare some unskilled users away. I've seen untrained users stopp on the first screen on the woody installer (you know, the large text block explaining that all you need to do to continue is press [ENTER]), and sit down and read it for several minutes trying to understand what it said. For these, all extra options increase their confusion, and make them more insecure during the installation process. For these, we should hide as much complexity and flexibility as possible. I normally ask people to imagine their religions teacher doing the install. It is normally a little easier to imagine than Bob User, as Bob User is different for all users. My religions teacher was not very technically skilled. Your grandmother might work as well, when you try to imagine how an unskilled user will react to questions and options. How you you explain the difference of KDE and Gnome to your grandmother, in a way to allow her to make an informed choice between them? In tasksel, you got around 40 characters to do it. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
TG3 NIC autodetection fails with Supermicro P8SCI server motherboard
Hi! I just installed sarge/testing with network installation CD from 27-12-2004. I used linux26 kernel. NIC autodetection did not detect onboard tg3 NIC's. But when I chose tg3 from the manual driver selection list, the NIC was detected OK. Output of lspci for Supermicro P8SCI server motherboard: :04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) Subsystem: Super Micro Computer Inc: Unknown device 02c6 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort-TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 169 Region 0: Memory at d010 (64-bit, non-prefetchable) [size=64K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3Enable- Address: 0053089d82ff4ff8 Data: befc Capabilities: [d0] #10 [0001] :05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) Subsystem: Super Micro Computer Inc: Unknown device 02c6 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort-TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 177 Region 0: Memory at d020 (64-bit, non-prefetchable) [size=64K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3Enable- Address: a31f7f0b9df77bf8 Data: fff4 Capabilities: [d0] #10 [0001] If you have any questions, please CC to me, I'm not subscribed to the list.. Thanks. -- Pasi Kärkkäinen ^ . . Linux /-\ Choice.of.the .Next.Generation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
Petter Reinholdtsen wrote: [Christian Perrier] We're dealing here with a quite informal population of people wanting to easily install Debian and indeed we're probably having hard times in figuring out exactly what they might expect. Yes. And some of these do not want the congintive strain that options they do not understand will give them. All extra options and flexibility will scare some unskilled users away. I've seen untrained users stopp on the first screen on the woody installer (you know, the large text block explaining that all you need to do to continue is press [ENTER]), and sit down and read it for several minutes trying to understand what it said. For these, all extra options increase their confusion, and make them more insecure during the installation process. For this target audience, a desktop-only install without seeing tasksel seems to be the best option. For these, we should hide as much complexity and flexibility as possible. Which wouldn't work well for more experienced people. The usual answer for this problem is to provide different modes, like standard/user defined/special. Currently we don't, which means Bob User still sees some strange questions, while e.g. somebody who got a static IP address from his network administrator has to type in some strange kernel parameters. I still think it would be better to ask this mode question up-front instead of hiding it away, because it allows to make the rest of an standard installation even simpler as it currently is. We can't do that now because it would dumb down the installer too much for too many people. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: TG3 NIC autodetection fails with Supermicro P8SCI server motherboard
On Thursday 06 January 2005 15:41, Pasi Kärkkäinen wrote: I just installed sarge/testing with network installation CD from 27-12-2004. I used linux26 kernel. NIC autodetection did not detect onboard tg3 NIC's. But when I chose tg3 from the manual driver selection list, the NIC was detected OK. Please file a bugreport against package discover1-data including the output of 'lspci' _and_ 'lspci -n' (lspci -v is not necessary). We can then add the PCI info in our driver database that's used for auto detection. Alternatively, you can file an installation report [1] and we will make sure it get's reassigned properly. [1] http://www.debian.org/devel/debian-installer/report-template TIA, FJP pgpVYmj9vG80b.pgp Description: PGP signature
Bug#288964: installation-reports
Package: installation-reports Debian-installer-version: Debian GNU/Linux testing _Sarge_ - Official Snapshot i386 Binary-1 (20041121) uname -a: Linux desktop 2.6.8-1-686-smp #1 SMP Thu Nov 25 04:55:00 UTC 2004 i686 GNU/Linux Date: Thu Dec 06 05:00:00 UTC 2004 Method: network install using linux26 from CD and ftp2.fr.debian.org repositories behind a firewall running latest woody Machine: Motherboard Asus P4P800 Deluxe Processor: Intel PIV HT 2,6GHz Memory: 2x512Mo DDR Root Device: IDE (/dev/hda3) Root Size/partition table: # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hda3 / ext3defaults,errors=remount-ro 0 1 /dev/hda2 /boot ext3defaults0 2 /dev/hda5 noneswapsw 0 0 /dev/hdc/media/cdrom0 iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 Output of lspci and lspci -n: # lspci :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) :00:1f.2 RAID bus controller: Intel Corp. 82801EB (ICH5R) SATA (cc=RAID) (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) :02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) :02:04.0 RAID bus controller: VIA Technologies, Inc. VT6410 ATA133 RAID controller (rev 06) :02:05.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12) :02:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06) :02:09.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 06) :02:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) :02:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) :02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) #lspci -n :00:00.0 0600: 8086:2570 (rev 02) :00:01.0 0604: 8086:2571 (rev 02) :00:1d.0 0c03: 8086:24d2 (rev 02) :00:1d.1 0c03: 8086:24d4 (rev 02) :00:1d.2 0c03: 8086:24d7 (rev 02) :00:1d.3 0c03: 8086:24de (rev 02) :00:1d.7 0c03: 8086:24dd (rev 02) :00:1e.0 0604: 8086:244e (rev c2) :00:1f.0 0601: 8086:24d0 (rev 02) :00:1f.1 0101: 8086:24db (rev 02) :00:1f.2 0104: 8086:24df (rev 02) :00:1f.3 0c05: 8086:24d3 (rev 02) :01:00.0 0300: 10de:0322 (rev a1) :02:03.0 0c00: 1106:3044 (rev 80) :02:04.0 0104: 1106:3164 (rev 06) :02:05.0 0200: 10b7:1700 (rev 12) :02:09.0 0401: 1102:0002 (rev 06) :02:09.1 0980: 1102:7002 (rev 06) :02:0a.0 0400: 109e:036e (rev 11) :02:0a.1 0480: 109e:0878 (rev 11) :02:0d.0 0200: 10ec:8169 (rev 10) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Detect hard drives partially worked because of the non detection of the VT6410 RAID chipset from VIA. A kernel patch enabling generic IDE support for this device is available at : http://robertk.com/source/ (Bottom of the page). And a proprietary module driver is available at : http://www.viaarena.com/default.aspx?PageID=2Type=3 but only for Red Hat/Fedora/Mandrake/Suse distributions. I was expecting this but I think it's worth a report as its an integrated motherboard feature and this motherboard is quite common. Everything else worked like a charm. Many thanks to the Debian community!
Bug#288974: Debian installer report: i386, d-i RC2, 2004-12-29
Package: installation-reports INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc2/sarge-i386-netinst.iso uname -a: Linux belanna 2.6.9.200501060123 #1 Thu Jan 6 01:51:46 CET 2005 i686 GNU/Linux (the original kernel was 2.6.8-1-386) Date: 2004-12-29 Method: Debian-Installer RC2 Netinst CD image, with Debian base 'expert' mode, 2.6 kernel Machine: Intel D865GBF board (for details cf. lspci output below) Processor: Intel Celeron 2.8 GHz Memory: 1 GB Root Device: S-ATA hard disk, 160 GB, SAMSUNG SP1614C Root Size/partition table: [EMAIL PROTECTED]:~# fdisk -l /dev/hde Disk /dev/hde: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hde1 1 6 48163+ 83 Linux /dev/hde2 7 130 996030 82 Linux swap /dev/hde3 131 19457 155244127+ 83 Linux [EMAIL PROTECTED]:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hde3 / ext3defaults,errors=remount-ro 0 1 /dev/hde1 /boot ext3defaults0 2 /dev/hde2 noneswapsw 0 0 /dev/hdc/media/cdrom0 iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 [..] Output of lspci and lspci -n: [EMAIL PROTECTED]:~# lspci :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) :01:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 01) [EMAIL PROTECTED]:~# lspci -n :00:00.0 0600: 8086:2570 (rev 02) :00:02.0 0300: 8086:2572 (rev 02) :00:1d.0 0c03: 8086:24d2 (rev 02) :00:1d.1 0c03: 8086:24d4 (rev 02) :00:1d.2 0c03: 8086:24d7 (rev 02) :00:1d.3 0c03: 8086:24de (rev 02) :00:1d.7 0c03: 8086:24dd (rev 02) :00:1e.0 0604: 8086:244e (rev c2) :00:1f.0 0601: 8086:24d0 (rev 02) :00:1f.1 0101: 8086:24db (rev 02) :00:1f.2 0101: 8086:24d1 (rev 02) :00:1f.3 0c05: 8086:24d3 (rev 02) :00:1f.5 0401: 8086:24d5 (rev 02) :01:08.0 0200: 8086:1050 (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it 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: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] Comments/Problems: * The installer asked about _3_ times if I have any PCMCIA devices. No real problem but a little annyoing. * During the installation various messages where shown that several modules could not be loaded. I guess they were loaded at a later stage or were not needed anyway. So again no problem but a little confusing. * Sound: After the base install and with the shipped kernel sound didn't work. After compiling a custom kernel with ALSA and without OSS everything is fine. * Grub: Here comes the only real problem: I installed Debian on the S-ATA drive (shown as /dev/hde above, originally named /dev/sda). The machine contains an old IDE drive too (/dev/hda - primary master). The BIOS is set to boot from the S-ATA drive i.e. BIOS reports it as the first and the IDE drive as the second hard disk. But: grub thought that the S-ATA drive with Debian was (hd1) - and therefore didn't boot - until I changed it to (hd0) in /boot/grub/menu.lst. (Additionally the grub install detected my old Windows on the IDE drive but
Bug#288981: busybox-cvs: FTBFS (amd64/gcc-4.0): conflicting types for 'build_bl_tree'
Package: busybox-cvs
Severity: normal
Tags: patch
gcc -I./include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -Wstrict-prototypes -Wshadow -Os
-fomit-frame-pointer -DNDEBUG -c -o archival/gzip.o archival/gzip.c
archival/gzip.c:2166: warning: type qualifiers ignored on function return type
archival/gzip.c:2166: error: conflicting types for 'build_bl_tree'
archival/gzip.c:1643: error: previous declaration of 'build_bl_tree' was here
make[1]: *** [archival/gzip.o] Error 1
make[1]: Leaving directory `/busybox-cvs-20040623'
make: *** [build-arch-deb-stamp] Error 2
With the attached patch 'busybox-cvs' can be compiled
on amd64 using gcc-4.0.
Regards
Andreas Jochens
diff -urN ../tmp-orig/busybox-cvs-20040623/archival/gzip.c ./archival/gzip.c
--- ../tmp-orig/busybox-cvs-20040623/archival/gzip.c2004-04-15
22:52:48.0 +0200
+++ ./archival/gzip.c 2005-01-06 14:37:51.0 +0100
@@ -1640,7 +1640,7 @@
static void build_tree(tree_desc * desc);
static void scan_tree(ct_data * tree, int max_code);
static void send_tree(ct_data * tree, int max_code);
-static int build_bl_tree(void);
+static const int build_bl_tree(void);
static void send_all_trees(int lcodes, int dcodes, int blcodes);
static void compress_block(ct_data * ltree, ct_data * dtree);
static void set_file_type(void);
diff -urN ../tmp-orig/busybox-cvs-20040623/modutils/obj/depmod.c
./modutils/obj/depmod.c
--- ../tmp-orig/busybox-cvs-20040623/modutils/obj/depmod.c 2005-01-06
17:21:18.225188952 +0100
+++ ./modutils/obj/depmod.c 2005-01-06 16:37:07.450168008 +0100
@@ -642,7 +642,7 @@
for (ksym = ksyms; so_far nksyms; ++so_far, ksym++) {
if (strncmp((char *)ksym-name, GPLONLY_, 8) == 0)
- ((char *)ksym-name) += 8;
+ ksym-name = ((char *)ksym-name) + 8;
assert(n_syms MAX_MAP_SYM);
symtab[n_syms++] = addsym((char *)ksym-name, mod,
SYM_DEFINED, 0);
}
diff -urN ../tmp-orig/busybox-cvs-20040623/modutils/obj/insmod.c
./modutils/obj/insmod.c
--- ../tmp-orig/busybox-cvs-20040623/modutils/obj/insmod.c 2005-01-06
17:21:18.234187584 +0100
+++ ./modutils/obj/insmod.c 2005-01-06 17:00:52.415540344 +0100
@@ -119,7 +119,7 @@
if (strncmp((char *)s-name, GPLONLY_, 8) == 0) {
gplonly_seen = 1;
if (gpl)
- ((char *)s-name) += 8;
+ s-name = ((char *)s-name) + 8;
else
continue;
}
diff -urN ../tmp-orig/busybox-cvs-20040623/modutils/obj/modstat.c
./modutils/obj/modstat.c
--- ../tmp-orig/busybox-cvs-20040623/modutils/obj/modstat.c 2005-01-06
17:21:18.226188800 +0100
+++ ./modutils/obj/modstat.c2005-01-06 17:07:37.572947056 +0100
@@ -199,6 +199,7 @@
s-name += (unsigned long) syms;
}
next:
+ continue;
}
if (type K_SYMBOLS) { /* Want info about symbols */
diff -urN ../tmp-orig/busybox-cvs-20040623/modutils/obj/obj_kallsyms.c
./modutils/obj/obj_kallsyms.c
--- ../tmp-orig/busybox-cvs-20040623/modutils/obj/obj_kallsyms.c
2005-01-06 17:21:18.217190168 +0100
+++ ./modutils/obj/obj_kallsyms.c 2005-01-06 17:12:08.635739248 +0100
@@ -200,8 +200,8 @@
/* Initial contents, header + one entry per input section. No strings. */
osec-header.sh_size = sizeof(*a_hdr) + loaded*sizeof(*a_sec);
-a_hdr = (struct kallsyms_header *) osec-contents =
- xmalloc(osec-header.sh_size);
+osec-contents = xmalloc(osec-header.sh_size);
+a_hdr = (struct kallsyms_header *) osec-contents;
memset(osec-contents, 0, osec-header.sh_size);
a_hdr-size = sizeof(*a_hdr);
a_hdr-sections = loaded;
@@ -275,8 +275,8 @@
a_hdr-symbol_off +
a_hdr-symbols*a_hdr-symbol_size +
strings_size - strings_left;
-a_hdr = (struct kallsyms_header *) osec-contents =
- xrealloc(a_hdr, a_hdr-total_size);
+osec-contents = xrealloc(a_hdr, a_hdr-total_size);
+a_hdr = (struct kallsyms_header *) osec-contents;
p = (char *)a_hdr + a_hdr-symbol_off;
memcpy(p, symbols, a_hdr-symbols*a_hdr-symbol_size);
free(symbols);
diff -urN ../tmp-orig/busybox-cvs-20040623/networking/ifupdown.c
./networking/ifupdown.c
--- ../tmp-orig/busybox-cvs-20040623/networking/ifupdown.c 2004-05-07
15:47:44.0 +0200
+++ ./networking/ifupdown.c 2005-01-06 15:32:58.886238656 +0100
@@ -148,7 +148,7 @@
static char no_act = 0;
static char verbose = 0;
-static char **environ = NULL;
+static char **environm = NULL;
#ifdef CONFIG_FEATURE_IFUPDOWN_IP
@@ -545,21 +545,6 @@
return(0);
}
-static int dhcp_down(struct interface_defn_t *ifd, execfn *exec)
-{
- int result = 0;
- if
Bug#288884: Sarge Installation fails with auto-partioning on 4G drive
On Thursday 06 January 2005 12:38 am, you wrote: snip Of course, when users choose Desktop machine for partitioning, one can maybe assume safely that (s)he will choose the Desktop task when the time comes for installing packages. So, IMHO, the minimum size for the root partition should then be raised to more than the size of the installed Desktop task in th partman-auto receipe named desktop. My suggestion is highly debatable, for sure...but let's discuss it. I even tag this as important as we're dealing with a probable frequent problem here... I would agree that your suggestion would be prudent, as it does seem like it would come up fairly often, especially on older machines that don't have particularly large disks. I, and others, tout that as one of the many features of using a Linux system - being able to use older hardware with an up to date (and updatable) OS. A situation like this could be disastrous for an inexperienced user. For my business, I do quite a few of Linux installations on older machines of this type (disks 5 Gigs), then optimize them for performance as well as possible. Since I use Debian branches almost exclusively, this could haunt me a bit if I inadvertently hit that particular partitioning scheme without noticing. Finding out that there's a space issue only _after_ downloading 500+ megs of packages is, how should I put it... rather infuriating - on any net connection. Regards, Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website [long]
Hello Frank,
On Tuesday 28 December 2004 17:57, Frank Lichtenheld wrote:
On the directory structure I have researched how difficult it would
be to adjust the filenames and links. Turns out it is not difficult at
all. Proof-of-concept patch against the sarge branch:
Working from your patches I think I have created a workable solution.
It consists of an extra stylesheet that takes care of your filenaming
wishes and a new wrapper script for buildone.sh specifically for the
website (both attached for review).
This solution needs only a minor change in buildone.sh:
-stylesheet_html=$stylesheet_dir/style-html.xsl
+if [ ! $web_build ]; then
+stylesheet_html=$stylesheet_dir/style-html.xsl
+else
+stylesheet_html=$stylesheet_dir/style-html-web.xsl
+fi
The advantage of this solution is that it leaves the builds for the
debian-installer-manual package and for the CD's unaffected.
As content negociation only works if the files are served from a webserver
that supports it, I see no benefits in changing the filenames there.
(As they will mostly be opened from a file browser.)
I have built a testset using the new wrapper script for a limited set of
arches and langs, available at [1].
Please let me know if this meets with your requirements.
Looking at [2] I think that, for content negotiation, naming the files
name.format.lang is preferable over name.lang.format.
With a few minor changes in the attached files this could be supported.
In style-html-web.xsl:
-xsl:param name=html.ext select=concat('.',/book/@lang,'.html')/
+xsl:param name=html.ext select=concat('.html.',/book/@lang)/
And in buildweb.sh:
-mv ./build.out/install.$lang.$format $destination/$destsuffix
+mv ./build.out/install.$lang.$format \
+ $destination/$destsuffix/install.$format.$lang
What do you think?
[1] http://home.tiscali.nl/isildur/d-i/manual_web.tar.gz
[2] http://httpd.apache.org/docs-2.0/content-negotiation.html.en#naming
Cheers,
FJP
buildweb.sh
Description: application/shellscript
pgpBimCYu48LJ.pgp
Description: PGP signature
Re: Bug#288701: Selected keymap not used for gdm, gnome or kde
Quoting Holger Levsen ([EMAIL PROTECTED]): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 January 2005 18:59, Christian Perrier wrote: There is no real solution to this. Console and X keymaps are currently disconnected. A workaround is bringed by the localization-config package which is run at the end of the install and preseeds the X settings with defaults related to the chosen locale (roughly language+country combination). apt-get install localization-config update-locale-config right ? (will test later... need breakfast first :) No. Running l-c is already done in d-i.but indeed, l-c does not choose the X keyboard based on the console keyboard chosen. So, in this bug report, the user who choosed a Dvorak keyboard just ends up with a US oneeven if (s)he uses localization-config. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
I normally ask people to imagine their religions teacher doing the Man, I live in one of the very few (IIRC) laic countries in the world (hmm, dunno if laic is English, indeedI hope you get the point if it is not...basically means that official institutions are completely separated from all religions). So, no religion teacher comes to my mind as I never had one. Nor had I to repeat some allegence to God at school like one has to do in some middle age countries..:-) But, anyway and back on topic, point taken for sure. How you you explain the difference of KDE and Gnome to your grandmother, in a way to allow her to make an informed choice between them? In tasksel, you got around 40 characters to do it. :) Even less, because you have to think about the poor people using verbose languages..:-) The only way I see would be something like If you don't know this means, check both.or indeed having both subtasks checked when Desktop is checked. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
[Christian Perrier] Man, I live in one of the very few (IIRC) laic countries in the world (hmm, dunno if laic is English, indeedI hope you get the point if it is not...basically means that official institutions are completely separated from all religions). So, no religion teacher comes to my mind as I never had one. Nor had I to repeat some allegence to God at school like one has to do in some middle age countries..:-) But, anyway and back on topic, point taken for sure. Oh, I could not let the point rest. You seem to confuse the teaching of religions and belief systems with the teaching of the one true religion. (I've had both kind of classes. :) One give generic knowledge about the major (and some minor) belief systems, and the other prepare you for your life as a true believer. I'm sure everyone would benefit from the former, and equally sure everyone should avoid the latter. All of my teachers in these classes have been techologically challenced. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
On Wed, Jan 05, 2005 at 02:44:14PM -0500, Joey Hess wrote: Sven Luther wrote: Ah, no, there where a bunch of people who didn't like it, especially as it started breaking on all sides when kde was uninstallable on non-mainstream arches, and we were told that this was the right true way. Please don't go into revisionism at this time. I agree that it may be too late for this, altough maybe not, but we choose this approach in full knowledge. If you would like to resurrect the potato tasksel and shove it back into sarge with all of its misfeatures bugs and lacks, you're really free to be my guest. Otherwise, stop whining, and please stop misrepresnting what I've said. Well, nobody said that, still a splitted desktop task would make sense, especially during times where the KDE desktop was uninstallable, which i recon happened during a non-negligible slice of time in the recent (err middle to recent) time. I am perfectly aware that it is late, and i did *NOT* argue that we should fix this, altough i believe it would be nice. I personally think that this would have been considered RC, but since i am not prepared to take the time to provide the code fixing it before the sarge release, it is of no matter. Yes, agreed on this. That said, his insitence that this was the right way in the past didn't encourage volunteers, i would guess. Saying no is the most important job the maintainer of a software system can do, and saying no does not imply that you think that your way is the only right way or that you don't listen for better ideas. Well, that was the the impression i got though, and it was not only you, many people where telling over these past 6+ month that splitting the Desktop task was a big no-go, so what should we understand from it ? I personally believe that it is a usability problem, but as said above, i don't have the time for fixing it, so ... I use a consistent set of rules, as documented in the tasksel source, for all decisions involving the contents of tasksel tasks. If I just I don't care at this point, and i bet you Joe Random User will not care also, all he will say : how the hell can i install only gnome or only kde or only twm, so that the debian X tasks fits on the small disk of that old box i am trying to run as X terminal. made decisions on an ad-hoc basis, the set of tasks would look like they did in slink -- a completly unusable mess. If someone proposes a better Well, it was most usable than it is right now though. right now we could as well have a question asking if you want the desktop packages installed or not, and skip the whole tasksel logic. set of rules, I will follow them. I did not even originate most of the rules I currently use. You're going to have a hard time showing me that your set of rules is better if you continue to demonstrate that you're not even aware of the current set, much less aware of the reasons behind them. It is not the set of rules who matter, it is the visible result. But please, don't take it bad, this is my opinion, and it is in no way a critic of your work or anything, and i apologize if it may sound so. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Hi Sven, No reason other than forgetting the CC to debian-boot@lists.debian.org. I can't currently use "Reply To" in the Archive reader because it selects the wrong from address, so when I did it by hand, it wasn't Quite Right. When I re-arrange my e-mail accounts, all will be again! Best Regards, J. William Campbell Sven Luther wrote: On Wed, Jan 05, 2005 at 09:04:01AM -0800, J. William Campbell wrote: Hi Sven, Thanks for the comments. I think you are correct that it is at least an interrupt assignment problem. Cool. I will look into this and see if I can figure out what is wrong. I will compile a Kernel and build an initrd as soon as I get my cross-development system running. Unfortunately I have no power-pc based workstations, so it will require developing and building on an Intel platform. I probably will want to sync up with your development at that point, so I will have your latest patches for the pci irq situation. When everything is ready, Well, i can build kernels for you, just really don't have time to go hunting for patches. I will e-mail you to sync up. It probably will be at least 2 weeks because of other work assignments. Well, ok. The MVME boards do use a pci bus internally, just like the MCP750 does, although the assignments are somewhat different. The interface to the VME bus is via a bridge (Tundra Universe) that lives on the pci bus on one side and the vme bus on the other. The boards therefore are pci from the kernel point of view, all VME stuff is inside a driver. Cool. BTW, any particular reason why you took this off list ? Friendly, Sven Luther
Re: new elilo-installer
On Thu, Jan 06, 2005 at 12:31:17AM -0700, dann frazier wrote: hey Joey, I haven't been following d-i that closely - are there any freezes in place that should prevent me from doing an elilo-installer upload that fixes #288897? Based on a conversation on #debian-boot (below) I went ahead and uploaded a 1.3 package to sid. Please consider this my request for pushing elilo-installer 1.3 into sarge. --- Does this mean you're really back? --- pere is now known as pere_poff fjp dannf: There is still a string freeze for the Sarge branch. An upload to trunk should be OK, but if you would like the change to be included in Sarge you should respect the string freeze even in trunk. dannf fjp: k - no strings changed - thanks! fjp kov: No. They are independent. However, depending on your language, there will be a basic preseeding of the xserver keyboard by the localization-config package during base-config (i.e. after the reboot). kov fjp: great, that helps =) fjp dannf: Commits to the Sarge brach only after OK'ed by joeyh of course. dannf oh - there's a sarge branch? is there documentation on how that all works with the archive? -- pb_ has quit (Client exiting) dannf how version strings need to differ, etc -- netman1 ([EMAIL PROTECTED]) has joined #debian-boot dannf where is the sarge branch, btw? i don't see it under branches/ in svn dannf oh, nm dannf under the d-i directory, duh netman1 Sorry, just missed that. What was that sarge branch for, please? dannf netman1: dunno yet - other than fjp dannf: Commits to the Sarge brach only after OK'ed by joeyh of course. * dannf checks the wiki netman1 dannf: 1st time I somebody reference it. Saw Joey's images split 3 weeks ago in the regular d-i and and sarge branch. Couldn't find a reason. The sarge brach does install though: did a HP/DL-380 with it yesterday, flawless except for grub, of course. tbm dannf: http://lists.debian.org/debian-boot/2004/11/msg00832.html dannf tbm: thanks! tbm actually, I think I meant http://lists.debian.org/debian-boot/2004/11/msg01344.html tbm but both are relevant netman1 tbm dannf: thanks, that clears it up. dannf ok, sounds like i can commit to trunk upload to sid, then, if i get joeyh's approval, i can migrate changes to the sarge branch and upload to t-p-u tbm dannf: t-p-u can probably be avoided; if you only upload the minimal change to unstable and it works, joeyh can get it pushed into testing dannf ok -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
On Thu, Jan 06, 2005 at 01:17:04PM +0100, Petter Reinholdtsen wrote: [Christian Perrier] We're dealing here with a quite informal population of people wanting to easily install Debian and indeed we're probably having hard times in figuring out exactly what they might expect. Yes. And some of these do not want the congintive strain that options they do not understand will give them. All extra options and flexibility will scare some unskilled users away. I've seen untrained Do you really think that anyone installing debian will be baffled when asked to choose between the gnome or KDE desktop ? Do you seriously believe that ? I bet those people will probably be more confused by the various server tasks. users stopp on the first screen on the woody installer (you know, the large text block explaining that all you need to do to continue is press [ENTER]), and sit down and read it for several minutes trying to understand what it said. For these, all extra options increase their confusion, and make them more insecure during the installation process. Do you want a gnome desktop or a KDE desktop ? Do you think this question is all so difficult ? For these, we should hide as much complexity and flexibility as possible. And you think it is easier for them to discover the KDE desktop once they have GDM running ? What do you imagine our current disk requirements are ? And to respond to Joeyh in a previous mail, sorry, but there is no common complexity measure between a partitioning stage, which is something real scary since a bad step can kill your disks, and most people are aware of that, and asking if one wants a choice of KDE or Gnome or Both or None ? If we had a graphic installer we would show the user with a screenshot of both, and that would be even more trivial. But the question of if one wants a gnome or kde desktop is quite easy to grasp by every Bob user out there, and if he doesn't like one, he can always reinstall and chose the other. So i seriously don't get it in how you can even remotely compare this with disk partitioning. I normally ask people to imagine their religions teacher doing the install. It is normally a little easier to imagine than Bob User, as Bob User is different for all users. My religions teacher was not very technically skilled. Your grandmother might work as well, when you try to imagine how an unskilled user will react to questions and options. But i bet you that the choice of KDE or Gnome is something every user out there can make. Evidently if we had some kind of description and documentations for tasks, it would be easier. How you you explain the difference of KDE and Gnome to your grandmother, in a way to allow her to make an informed choice between them? In tasksel, you got around 40 characters to do it. :) They chose one, install it, don't like it, install the other. The new installer is easy to use, so it should be no problem :) And for the really unenlightened people, the right way is to make a choice of one desktop for them, like the ubuntu people have done, and to bypass the question at all. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of elilo-installer_1.3_ia64.changes
elilo-installer_1.3_ia64.changes uploaded successfully to localhost along with the files: elilo-installer_1.3.dsc elilo-installer_1.3.tar.gz elilo-installer_1.3_ia64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
elilo-installer_1.3_ia64.changes ACCEPTED
Accepted: elilo-installer_1.3.dsc to pool/main/e/elilo-installer/elilo-installer_1.3.dsc elilo-installer_1.3.tar.gz to pool/main/e/elilo-installer/elilo-installer_1.3.tar.gz elilo-installer_1.3_ia64.udeb to pool/main/e/elilo-installer/elilo-installer_1.3_ia64.udeb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 288897 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288897: marked as done (elilo-installer: needs to remove 'do_bootloader = no' entry from kernel-img.conf)
Your message dated Thu, 06 Jan 2005 13:47:08 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#288897: fixed in elilo-installer 1.3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 6 Jan 2005 07:13:56 + From [EMAIL PROTECTED] Wed Jan 05 23:13:56 2005 Return-path: [EMAIL PROTECTED] Received: from colo.lackof.org [198.49.126.79] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CmRqF-0001ml-00; Wed, 05 Jan 2005 23:13:56 -0800 Received: from localhost (localhost [127.0.0.1]) by colo.lackof.org (Postfix) with ESMTP id F038F298059 for [EMAIL PROTECTED]; Thu, 6 Jan 2005 00:13:26 -0700 (MST) Received: from colo.lackof.org ([127.0.0.1]) by localhost (colo.lackof.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07064-08 for [EMAIL PROTECTED]; Thu, 6 Jan 2005 00:13:26 -0700 (MST) Received: by colo.lackof.org (Postfix, from userid 1012) id E37DF298058; Thu, 6 Jan 2005 00:13:25 -0700 (MST) X-IMAP-Sender: dannf Date: Wed, 5 Jan 2005 23:57:17 -0700 X-OfflineIMAP-788348491-64616e6e662e6f72672e72656d6f7465-494e424f582e4f7574626f78: 1104995541-00715899149806-v4.0.8 From: dann frazier [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: elilo-installer: needs to remove 'do_bootloader = no' entry from kernel-img.conf Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 3.5 User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lackof.org Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: elilo-installer Version: 1.2 Severity: grave base-installer adds 'do_bootloader = no' to /etc/kernel-img.conf. With this setting, kernel-image packages will no longer prompt the user to run ELILO in their post-install. This means users will see no indication that the kernel they just installed (which may contain a critical security fix, for example) is not configured as the default kernel for the next boot. lilo-installer sets the precedent of removing this setting in its postinst. elilo-installer should probably do the same; although it seems to me that base-installer has chosen the wrong default of disabling bootloader execution. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- Received: (at 288897-close) by bugs.debian.org; 6 Jan 2005 18:49:52 + From [EMAIL PROTECTED] Thu Jan 06 10:49:52 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cmchj-0003Mr-00; Thu, 06 Jan 2005 10:49:51 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1Cmcf6-0004J1-00; Thu, 06 Jan 2005 13:47:08 -0500 From: dann frazier [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.54 $ Subject: Bug#288897: fixed in elilo-installer 1.3 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Thu, 06 Jan 2005 13:47:08 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: elilo-installer Source-Version: 1.3 We believe that the bug you reported is fixed in the latest version of elilo-installer, which is due to be installed in the Debian FTP archive: elilo-installer_1.3.dsc to pool/main/e/elilo-installer/elilo-installer_1.3.dsc elilo-installer_1.3.tar.gz to pool/main/e/elilo-installer/elilo-installer_1.3.tar.gz elilo-installer_1.3_ia64.udeb to pool/main/e/elilo-installer/elilo-installer_1.3_ia64.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to
Re: Bug#288701: Selected keymap not used for gdm, gnome or kde
On Thu, Jan 06, 2005 at 06:13:50PM +0100, Christian Perrier wrote: Quoting Holger Levsen ([EMAIL PROTECTED]): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 January 2005 18:59, Christian Perrier wrote: There is no real solution to this. Console and X keymaps are currently disconnected. A workaround is bringed by the localization-config package which is run at the end of the install and preseeds the X settings with defaults related to the chosen locale (roughly language+country combination). apt-get install localization-config update-locale-config right ? (will test later... need breakfast first :) No. Running l-c is already done in d-i.but indeed, l-c does not choose the X keyboard based on the console keyboard chosen. So, in this bug report, the user who choosed a Dvorak keyboard just ends up with a US oneeven if (s)he uses localization-config. Actually, i think that localization-config was fixed to preseed the value, but mark it as unseen, thus allowing the user to override it. Not ideal, but the best that can be done, since i hear that there is no way to exactly map the console keyboards to X keyboards. The above fix maybe needed a fix in the debconf script used to set the values, to allow for marking them as unread. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#288701: Selected keymap not used for gdm, gnome or kde
On 06 2005 19:13, Christian Perrier wrote: No. Running l-c is already done in d-i.but indeed, l-c does not choose the X keyboard based on the console keyboard chosen. So, in this bug report, the user who choosed a Dvorak keyboard just ends up with a US oneeven if (s)he uses localization-config. I plan this weekend to work on l-c reading the keymap configuration from the console keymap setting and then fallback to the defaults map if this is unsuccessful. Perhaps this will solve these kinds of problems... Stay tuned...
Re: Bug#288701: Selected keymap not used for gdm, gnome or kde
On 06 2005 21:19, Sven Luther wrote: Actually, i think that localization-config was fixed to preseed the value, but mark it as unseen, thus allowing the user to override it. Not ideal, but the best that can be done, since i hear that there is no way to exactly map the console keyboards to X keyboards. Actually there is a way but there is no 1-1 mapping... As I saw too many people for this approach, I plan to work on it during this weekend. Maybe it will not be perfect but I have something in mind that might work until there is a more integrated approach... The above fix maybe needed a fix in the debconf script used to set the values, to allow for marking them as unread. The fix depends on a patch (see #286318) on debconf which is not included yet, until this is included then even the unseen trick won't work. But joeyh agreed on including this patch so this is just a matter of time... Konstantinos
Keyboard preseed for X
[Please, CC me on replies, I'm not currently subscribed]
Hello,
I was talking to sjoerd on #gnome-debian about keyboard setup just after
the Debian Instalation, and he said he got the us keyboard on GNOME even
though he had selected the british keymap on install time.
This reminded me that my last sarge install gave me my X setup using
abnt2 instead of us_intl, which it even auto-detected successfuly at
install time. The console keymap is correctly configured, so I went to
investigate. fjp told me on #debian-boot that localization-config was
the responsible for the preseeding and I got its source code.
The way it works today, it is mapping locale names to keyboard setups,
so you have:
'pt_BR' = { LAYOUT = 'br', XKBOPTIONS = '', XKBMODEL = 'abnt2', XKBVARIANT
= 'abnt2' },
(I don't even think we need a XKBVARIANT here for abnt2, but then...)
So I was thinking about hacking on localization-config so that it will
use the debconf key obtained during installation to set up the keyboard
and map that one to the keyboard setup for X instead. The debconf
question is answered like this on my new install:
Name: debian-installer/keymap
Template: debian-installer/keymap
Value: br-latin1
Owners: base-config, d-i, unknown
So I would map br-latin1 to pc105/us_intl and br-abnt2 to abnt2/br. Does
this make sense? Does it make sense for locales other than pt_BR? That
would, of course, help those who would like to have the system display
messages in pt_BR and use a 'us' keymap or other keymaps.
Thanks,
--
[EMAIL PROTECTED]: Gustavo Noronha http://people.debian.org/~kov
Debian: http://www.debian.org * http://www.debian-br.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289016: TG3 NIC autodetection fails
Package: installation-reports Debian-installer-version: 27-12-2004 uname -a: Linux test 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux Date: Thu 06-01-2005 15:00 Method: Booted from sarge netinst CD (27-12-2004) and installed using ftp://ftp.fi.debian.org, no proxies. Machine: Custom made server using Supermicro P8SCI server motherboard Processor: Intel P4 3,0 GHz 1024kB cache 800MHz FSB Memory: 1 GB DDR2 ECC (2x512) Root Device: IDE /dev/hda3 Root Size/partition table: /boot hda1, swap hda2, root hda3, home hda4 Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 05) :00:01.0 PCI bridge: Intel Corp. Server Memory Controller Hub PCI Express Port (rev 05) :00:02.0 VGA compatible controller: Intel Corp. Graphics Controller (rev 05) :00:1c.0 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) :00:1c.2 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03) :00:1c.3 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4 (rev 03) :00:1d.0 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) :00:1d.1 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) :00:1d.2 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) :00:1d.3 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) :00:1d.7 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev d3) :00:1f.0 ISA bridge: Intel Corp. 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) :00:1f.1 IDE interface: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) :00:1f.2 0106: Intel Corp. 82801FR/FRW (ICH6R/ICH6RW) SATA Controller (rev 03) :00:1f.3 SMBus: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) :01:00.0 PCI bridge: Intel Corp. PCI Bridge Hub (rev 09) :01:00.1 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller A (rev 09) :04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) :05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) :00:00.0 0600: 8086:2588 (rev 05) :00:01.0 0604: 8086:2589 (rev 05) :00:02.0 0300: 8086:258a (rev 05) :00:1c.0 0604: 8086:2660 (rev 03) :00:1c.2 0604: 8086:2664 (rev 03) :00:1c.3 0604: 8086:2666 (rev 03) :00:1d.0 0c03: 8086:2658 (rev 03) :00:1d.1 0c03: 8086:2659 (rev 03) :00:1d.2 0c03: 8086:265a (rev 03) :00:1d.3 0c03: 8086:265b (rev 03) :00:1d.7 0c03: 8086:265c (rev 03) :00:1e.0 0604: 8086:244e (rev d3) :00:1f.0 0601: 8086:2640 (rev 03) :00:1f.1 0101: 8086:266f (rev 03) :00:1f.2 0106: 8086:2652 (rev 03) :00:1f.3 0c05: 8086:266a (rev 03) :01:00.0 0604: 8086:032c (rev 09) :01:00.1 0800: 8086:0326 (rev 09) :04:00.0 0200: 14e4:1659 (rev 11) :05:00.0 0200: 14e4:1659 (rev 11) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [E] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: 1) Installer didn't autodetect onboard TG3 NIC. When installer asked me to specify manually what modules to load, I selected tg3, and the NIC was detected just fine, and the installation from network using ftp worked well. 2) Locales-package asked what locales to generate, I selected a couple, but they were not generated.. I had to run dpkg-reconfigure locales and re-select the locales to get them generated. This same bug was also in woody installer.. I didn't select any tasks / package sets to install when I was prompted for that.. if it might have something to do with this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288759: related bugs
I think that bugs 288759 and 270087 are related. Perhaps the busybox maintainer will merge them? Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard preseed for X
|| On Thu, 06 Jan 2005 17:03:58 -0200 || Gustavo Noronha Silva [EMAIL PROTECTED] wrote: gns Name: debian-installer/keymap gns Template: debian-installer/keymap gns Value: br-latin1 gns Owners: base-config, d-i, unknown gns So I would map br-latin1 to pc105/us_intl and br-abnt2 to abnt2/br. Does gns this make sense? Does it make sense for locales other than pt_BR? That gns would, of course, help those who would like to have the system display gns messages in pt_BR and use a 'us' keymap or other keymaps. Sure it makes sense but it have problems with others languages. Some languages the translation between kbdchooser and X is not direct. Take a look in archives, it was discussed here before. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. pgpn1qs9wwIs7.pgp Description: PGP signature
Bug#288759: Related archived bug...
Seems insmod and lsmod and rmmod were removed from busybox on purpose to fix bug #85642. But this was a bug to fix woody so the reasons to remove insmod from busybox may have now changed!?! Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Create software raid array during install, error when filesystems is created.
Hi, I have 2 equally sized IDE PATA disks. I created a partition covering the whole drive on each disk, the partition type was raid. I created a software RAID0 array, and in turn created partitions on it and set them to ReiserFS. In the next step, When the filesystem are supposed to be created a get a red screen telling me: Failed to create ReiserFS part1 on RAID0- unit0. If i swich to the third virtual console i see this messsage: Stat of the device /dev/md/0/part1 failed. I have tried RAID1 also, ext3 instead of Reiser. Also tried to use the LVM to set up a volume group and so on, all with about the same result, failure when creating file system. So I installed on just 1 drive as normal, and that worked fine (impressive stuff with the hw autodetection btw!) I have tried with rc2 and nightly build from 2005-01-05, same result I read some problems with lilo or grub when using software raid, but that seems unrelated becouse this is well before any bootloader is installed. Regards /Björn
Processed: Re: Bug#289035: Installer freezes while scanning my HD
Processing commands for [EMAIL PROTECTED]: reassign 289035 installation-reports Bug#289035: Installer freezes while scanning my HD Warning: Unknown package 'debain' Warning: Unknown package 'sarge' Warning: Unknown package 'cd-rom' Warning: Unknown package 'built' Warning: Unknown package 'on' Warning: Unknown package '20041118' Bug reassigned from package `debain sarge installation cd-rom, built on 20041118' to `installation-reports'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard preseed for X
Em Qui, 2005-01-06 s 18:36 -0200, Otavio Salvador escreveu: gns So I would map br-latin1 to pc105/us_intl and br-abnt2 to abnt2/br. Does gns this make sense? Does it make sense for locales other than pt_BR? That gns would, of course, help those who would like to have the system display gns messages in pt_BR and use a 'us' keymap or other keymaps. Sure it makes sense but it have problems with others languages. Some languages the translation between kbdchooser and X is not direct. I don't understand what you mean with the translation not being direct, but if we cannot use this approach for every language, then we need a mixed solution. I talked to markos_ on IRC and he said he was planning to implement the 'grab from console' method; maybe we'll be able to come up with something during the weekend. Take a look in archives, it was discussed here before. Will do. See ya, -- [EMAIL PROTECTED]: Gustavo Noronha http://people.debian.org/~kov Debian: http://www.debian.org * http://www.debian-br.org
Daily Netinst bootable?
The daily testing netinst build ISO does not create a bootable CD. Is this by design? If so, where can I get boot floppy images to use the CD? I downloaded the ISO from here: http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20050105/ Brian
Re: Desktop task broken on !(i386/powerpc)
On Thursday 06 January 2005 20:12, Sven Luther wrote: They chose one, install it, don't like it, install the other. The new installer is easy to use, so it should be no problem :) flame_invite_mode=on I vote for KDE. flame_invite_mode=off -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#289016: TG3 NIC autodetection fails
Processing commands for [EMAIL PROTECTED]: reassign 289016 discover1-data Bug#289016: TG3 NIC autodetection fails Bug reassigned from package `installation-reports' to `discover1-data'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New Message
Check here if your message above does not load. If you can't describe what you are doing as a process, you don't know what you're doing. W. Edwards Deming buccogingival Haven't the photographers already disliked praying? afterhelp The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn. Alvin Toffler bespecklement EDWARDS: But what have we seen? Relentless negative attacks against John. So in the weeks ahead, we know what's coming, don't we? abietin Do just once what others say you can't do, and you will never pay attention to their limitations again. -James R. Cook affrontingly That librarian isn't enjoying jumping at the company. cataclasm Why does the Air Force need expensive new bombers? Have the people we've been bombing over the years been complaining? George Wallace Amazilia Have you hated surfing lately? autochthonous
Bug#289076: Add a way of correcting system time when asked if system time is set to GMT
Package: install During the installation of sarge you are asked if your system time is set to GMT, but there is no way of correcting the system time if it happens to be wrong. I suggest adding a button with a pup-up window, where the system time can be set, to to the user interface. / Fredrik Lindberg _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289083: SPARCstn 5 [2004/12/19 daily]: suceeded w/ difficulty
Package: installation-reports Debian-installer-version: daily-build (post-RC2) w/2.4, dated Dec. 19 2004 uname -a: Linux neurotica 2.4.27-1-sparc32 #1 Tue Aug 24 01:05:41 PDT 2004 sparc GNU/Linux Date: Tue Jan 4 2005 Method: Netboot (bootp/tftp on x86 Debian/unstable workstation, no proxy). Machine: Sun Sparcstation 5 Processor: sun4w (Fujitsu MB86904), 110MHz Memory: 125595648 Root Device: SCSI /dev/sdc1 Root Size/partition table: Disk /dev/sdc (Sun disk label): 19 heads, 80 sectors, 2733 cylinders Units = cylinders of 1520 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdc1 0 5404104002 SunOS root /dev/sdc2 u540 8842614403 SunOS swap /dev/sdc3 0 2733 20770805 Whole disk /dev/sdc4 884 2733 14052404 SunOS usr Disk /dev/sda (Sun disk label): 14 heads, 72 sectors, 2036 cylinders Units = cylinders of 1008 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1 0 12206148808 SunOS home /dev/sda2 1220 20364112647 SunOS var /dev/sda3 u 0 2036 10261445 Whole disk Output of lspci and lspci -n: n/a (no PCI bus on machine) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E] Configure network HW: [O] Config network: [O] Detect CD: [ ] 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] Comments/Problems: Note: the Dec 19 daily build for Sparc was the most recent I could find, even though it was nearly three weeks old. The first problem (which was nearly a showstopper) was not actually a boot problem. It was simply that the booted installer did not recognize my model-5 keyboard (even though the kernel detected it just fine). I actually tried four different boot images (daily2.4, daily2.6, RC2/2.4, RC2/2.6), and none of them would work. They all seemed to assume I had a PC keyboard (I'm guessing here). This seems like a pretty major problem, and I'm surprised more people haven't reported it! Perhaps there just aren't very many people testing d-i on Sparc w/ Sun keyboards? Fortunately, I discovered (quite by accident) that the backslash key would act as Enter, so I was able to select the defaults and get to the keyboard selection dialog, after which the keyboard worked fine. The next problem was when I tried to partition. I told it to delete all the partitions on my 2.1GB drive, and it told me that I had 2.1GB of free space. Then I created a 350MB partition, and it told me that I had only 400MB of free space left! I tried a couple of variations, with basically the same result. Finally, I gave up, booted Solaris, and used that to create my partitions, which worked fine, and I was able to complete the installation without further problem. However, halting and booting into Solaris should not be a necessary step in the installation, IMO. :) General thoughts: early in the process, it asked me where I wanted to get the base-install images from, and had me select a server and (optionally) configure a proxy. Later, after the initial reboot, it asked me where I wanted apt to get its packages from, and it seemed to have completely forgotten my earlier choices! Wouldn't it make more sense to have it at least default to the same settings? cheers -- Chris Waters | Pneumonoultra-osis is too long [EMAIL PROTECTED] | microscopicsilico-to fit into a single or [EMAIL PROTECTED] | volcaniconi- standalone haiku -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#289083: SPARCstn 5 [2004/12/19 daily]: suceeded w/ difficulty
Processing commands for [EMAIL PROTECTED]: tags 289083 moreinfo Bug#289083: SPARCstn 5 [2004/12/19 daily]: suceeded w/ difficulty There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289083: SPARCstn 5 [2004/12/19 daily]: suceeded w/ difficulty
tags 289083 moreinfo thanks On Thu, 6 Jan 2005, Chris Waters wrote: The first problem (which was nearly a showstopper) was not actually a boot problem. It was simply that the booted installer did not recognize my model-5 keyboard (even though the kernel detected it just fine). I actually tried four different boot images (daily2.4, daily2.6, RC2/2.4, RC2/2.6), and none of them would work. They all seemed to assume I had a PC keyboard (I'm guessing here). This seems like a pretty major problem, and I'm surprised more people haven't reported it! Perhaps there just aren't very many people testing d-i on Sparc w/ Sun keyboards? It was reported as bug 288140 (http://bugs.debian.org/288140). Please see the last message there and try the linked netboot image to confirm that the problem is gone when you are using it to boot. The next problem was when I tried to partition. I told it to delete all the partitions on my 2.1GB drive, and it told me that I had 2.1GB of free space. Then I created a 350MB partition, and it told me that I had only 400MB of free space left! I tried a couple of variations, with basically the same result. Finally, I gave up, booted Solaris, and used that to create my partitions, which worked fine, and I was able to complete the installation without further problem. However, halting and booting into Solaris should not be a necessary step in the installation, IMO. :) I don't think that problem is known. Can you repeat the install to see if you can reproduce? Then the partman log (which is saved in /var/log/debian-installer) on the installed system should tell us what went wrong. If possible, please post a followup to this bug including it (compressed) an attachment or make it available somewhere on the web for inspection. General thoughts: early in the process, it asked me where I wanted to get the base-install images from, and had me select a server and (optionally) configure a proxy. Later, after the initial reboot, it asked me where I wanted apt to get its packages from, and it seemed to have completely forgotten my earlier choices! Wouldn't it make more sense to have it at least default to the same settings? Don't know anything about that, perhaps somebody else can comment? cheers -- Chris Waters | Pneumonoultra-osis is too long [EMAIL PROTECTED] | microscopicsilico-to fit into a single or [EMAIL PROTECTED] | volcaniconi- standalone haiku Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288759: Bug#270087: Related archived bug...
On Thu, Jan 06, 2005 at 08:27:53PM +, Alex Owen wrote: Seems insmod and lsmod and rmmod were removed from busybox on purpose to fix bug #85642. But this was a bug to fix woody so the reasons to remove insmod from busybox may have now changed!?! In any case, it seems that we can resolve #270087 by symlinking /sin/insmod to /sbin/insmod.modutils as you previously suggested. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#260763: [powerpc] Problems with logical volume setup during installation
Hi, I was using d-i daily build for powerpc (Jan 4, 2005) to install on an Apple Dual G5 (PowerMac7,3). I find that the LVM menu items in the installer do not work in a manner very similar to what is described in this bug report (though this report is for a x86 machine). Basically I cannot create physical volumes (using expert- too) via the menus, and the LV menus then clearly do not work. It seems that the options described in the latest installation guide (6.3.2.2, to use a partition as a PV for LVM) just do not show up! Because my hardware is really new the d-i daily build is not quite ready though a solution is in place, please see #287030 for details. This is why I don't want to write an installation report just yet. Please let me know how you want to proceed with this issue (new bug? work with this one? retitle it?). I can easily reproduce this situation, and I'm willing to spend time on it. Best regards, Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#288701: Selected keymap not used for gdm, gnome or kde
(X and console-data maintainers, please look at the bug story...Basically this may be resumed to : User choosed dvorak keyboard in d-i and then was suprised to get a US layout in XKostas, below, explains that he plans to add a console--X mapping feature to his localization-config package so that, at least in fresh installs, users get a better value for their X keyboard settings preseeded. Currently, localization-config is run at the end of base-config and preseeds X debconf settings with values based on the chosen locale...but not based on the chosen keymap for the console) I know that Alastair had some plans about this for post-sargeand there's maybe the same concerns about the X Strike Force. Quoting Konstantinos Margaritis ([EMAIL PROTECTED]): I plan this weekend to work on l-c reading the keymap configuration from the console keymap setting and then fallback to the defaults map if this is unsuccessful. Perhaps this will solve these kinds of problems... Sure it will. But then you should be prepared for maintaining a map between both keyboard mapping systems. Not really a Bad Thing for sure...but this may become a time-consuming task as you have to follow what happen on keyboard layouts in both sides. If you do add this new feature, you also might want to mention this to both console-data and X packages maintainers...which I'm just doing now. We had a conversation about this topic with Fabbione at Debconf4. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard preseed for X
So I was thinking about hacking on localization-config so that it will use the debconf key obtained during installation to set up the keyboard and map that one to the keyboard setup for X instead. The debconf question is answered like this on my new install: Kostas (Konstantinos Margaritis, l-c maintainer) plans to do exactly this. As Otavio mentioned, look at these days discussions in the archive. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Desktop task broken on !(i386/powerpc)
Quoting Christian Perrier ([EMAIL PROTECTED]): So, no religion teacher comes to my mind as I never had one. Nor had I to repeat some allegence to God at school like one has to do in some middle age countries..:-) Hmmm, sorry for the bad choice of words which may hurt some people, I now realise that. I indeed was under influence of a recent very good documentary film I recently watched on TV about the increasing influence of religion in a very well known country (the same country which also has laws allowing to legally murder someone). So, please, fellow members of the team, accept my apologies for this off-topic useless flame. There's really no good excuse for having put this here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#289016: TG3 NIC autodetection fails
Processing commands for [EMAIL PROTECTED]: clone 289016 -1 Bug#289016: TG3 NIC autodetection fails Bug 289016 cloned as bug 289101. retitle -1 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not detected Bug#289101: TG3 NIC autodetection fails Changed Bug title. reassign -1 discover1-data Bug#289101: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not detected Bug reassigned from package `discover1-data' to `discover1-data'. tags -1 patch Bug#289101: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not detected There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289016: TG3 NIC autodetection fails
clone 289016 -1 retitle -1 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not detected reassign -1 discover1-data tags -1 patch thanks 1) Installer didn't autodetect onboard TG3 NIC. When installer asked me to specify manually what modules to load, I selected tg3, and the NIC was detected just fine, and the installation from network using ftp worked well. Yet another victim of the hardware vendors crazyness at inventing new models nearly daily. The PC hardware world just drives me crazy. As you provided all the useful information for fixing this bu, I did the patch to the right package. Attached. 2) Locales-package asked what locales to generate, I selected a couple, but they were not generated.. I had to run dpkg-reconfigure locales and re-select the locales to get them generated. This same bug was also in woody installer.. I didn't select any tasks / package sets to install when I was prompted for that.. if it might have something to do with this. This needs more investigation. I'm even wondering why the locales package prompted you about the locales to generate. What were your choices of language and country? fi and FI? What was the debconf priority? Default (ie high) or medium? What were the additional locales you selected? --- pci.lst.ori 2005-01-07 07:34:40.0 +0100 +++ pci.lst 2005-01-07 07:35:28.0 +0100 @@ -4289,6 +4289,7 @@ 14e4164dethernettg3 NetXtreme BCM5702FE Gigabit Ethernet 14e41653ethernettg3 NetXtreme BCM5705 Gigabit Ethernet 14e41654ethernettg3 NetXtreme BCM5705_2 Gigabit Ethernet + 14e41659ethernettg3 NetXtreme BCM5721 Gigabit Ethernet 14e4165dethernettg3 NetXtreme BCM5705M Gigabit Ethernet 14e4165eethernettg3 NetXtreme BCM5705M_2 Gigabit Ethernet 14e41677ethernettg3 NetXtreme BCM95751 Gigabit Ethernet
