Bug#983043: Acknowledgement (Failed to initialize GENET properly on RPI4 (arm64))
Discovered mdio_bcm_unimac module is missing from the installer initrd. This will stop the installer on the RPI4 from connecting to the network. On Thu, Feb 18, 2021 at 9:06 AM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 983043: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983043. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Install Team > > If you wish to submit further information on this problem, please > send it to 983...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 983043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983043 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- "Non sibi, sed patriae"
Bug#983043: Failed to initialize GENET properly on RPI4 (arm64)
Package: installation-reports Boot method: netboot Image version: https://d-i.debian.org/daily-images/arm64/daily/netboot/debian-installer/arm64/linux 2021-02-18 02:07 26M Date: 2021-02-18 14:05:00 Machine: RPi4 Processor: Memory: 4GiB Partitions: Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect media: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: RPi 4 with 4GiB Ram. System is netbooted using DNSMASQ, RPI-UEFI and iPXE. Netboot Debian Installer for arm64 starts and fails at configuring the genet ethernet card. I have attempted to remove and reinstall the genet driver. No effect. ip link show has the card identified as enabcm6e4ei0. I can put an address on the card using ip addr add. ip link set dev down works ip link set dev up fails with SIOCSIFFLAGS: No such device -- "Non sibi, sed patriae"
Bug#982995:
This was a netboot attempt.
Bug#982995: Installation Report
Package: installation-reports Boot method: Image version: https://d-i.debian.org/daily-images/arm64/daily/netboot/debian-installer/arm64/linux 2021-02-17 02:07 Date: 2021-02-17 19:14 Machine: RPI4 Processor: Memory: 4G Partitions: Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect media: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: RPI4 with 4GiB Ram. This system is netbooted using RPI-UEFI 1.22 and iPXE 1.2.x. DNSMASQ send the RPI-UEFI to the RPI. The RPI-UEFI pulls the arm64 EFI/ipxe. The iPXE shows a menu for booting into the Debian Installer. The Installer loads and starts the interactive menu installation system. Everything seems good until input is required. The keyboard is dead.
Bug#932939: Confirmed bug 932939
Confirmed the same. Sep 30 23:40:50 debconf: Setting debconf/language to en Sep 30 23:40:50 kernel: [ 140.827798] main-menu[16157]: segfault at 1 ip 7f2eeec81554 sp 7ffdd0809cc8 error 4 in libc.so.6[7f2eeec11000+148000] Sep 30 23:40:50 kernel: [ 140.827811] Code: 1f 80 00 00 00 00 66 0f 6e ce 89 f9 66 0f 60 c9 48 85 d2 0f 84 0d 03 00 00 66 0f 60 c9 83 e1 3f 66 0f 70 c9 00 83 f9 30 77 3c 0f 6f 07 66 0f 74 c1 66 0f d7 c0 85 c0 0f 85 a8 02 00 00 48 83 Changed pxe console boot kernel options from: console=tty0 console=ttyS0,115200n8 to: console=ttyS0,115200n8
Bug#684128: Bug 684128, GB vs GiB
Well, it's been 7 years since this bug was opened. Sure, it's not killing anyone. And I assume that the partitioner correctly handles alignment issues for current drives. But still, IMHO, any time software does something other than what you expect it to do, it's broken. A simple suggestion: just have partman correctly parse KiB, MiB, GiB, and TiB when someone manually enters a partition size. Currently, these generate an error message. Also, on that page, include a short explanation of the acceptable units and their meanings. I'd say it's fine for partman to just always display partition sizes in 10^n units. The only folks likely to care about this are ones doing manual partitioning. It's likely that any such person will understand what's going on when they specify a 32GiB partition and then see 34.4GB in the list of partitions. It also might be handy to include fdisk on the net-install cd, for use in a shell (or ctrl-alt-f2). But that might be a pain, given that fdisk now has its own shared libs. Just my 2c. -Jeff
Bug#738865: capabilities of VGA controller
Sorry to keep posting. One more tidbit, if it helps: I didn't realize that running the lspci w/o sudo would lock out reporting on the capabilities of the VGA controller (where it says "" in previous post). Here they are, from sudo: Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features
Bug#738865: Ubuntu does install successfully on the ProBook 450 G1
One more tidbit of info: The installer for Ubuntu (back on 16.04) worked fine (which is what this laptop has installed, though it has by now been upgraded to 17.04). But I would prefer to re-install with Debian.
Bug#738865: Video / GPU hardware info on the ProBook 450 G1
Video hardware info from a trimmed output of $ lspci -vnn | grep VGA -A 12 on this HP ProBook 450 G1 laptop: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) DeviceName: 64 Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1942] Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at b000 (64-bit, non-prefetchable) [size=4M] Memory at a000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: radeon Kernel modules: radeon, amdgpu
Bug#701099: debian-cd: installer fails with two CD/DVD drives
I've also been bitten by this bug. I'm installing Debian 7.3 on new hardware that includes an asus P9D-E/4L server motherboard that has a bios-based virtual cdrom. I couldn't find a straightforward way to disable the extra drive in bios, but I found another workaround, which is detailed below. I tried to reproduce this bug using qemu, by setting up virtual machines with two cdroms. However, the install went fine in those cases. My first cdrom was the debian-7.3 disk image. For the second drive I tried my physical (empty) cdrom drive, an empty disk file, and /dev/zero. In all these cases a /dev/sr1 drive did show up on the system, but it didn't cause the installer to fail. So, it seems that there is something about the bios-based virtual-cd that triggers the bug. I doesn't seem to be correct that this bug will occur whenever there is more than one CD/DVD drive. --- Here is a simple workaround for this bug that I was able to use. YMMV, of course. I'm assuming the reader is fairly comfortable with linux and using the command line. 1) At the first prompt after booting the install cd (asking for your language), use Ctrl-Alt-F2 to switch to a text console, and press return to get a command prompt. You can use 'ls /dev/sr*' to verify that there is more than one CD/DVD device. 2) Type 'cd /sys/block' and use 'ls' to verify that there are multiple sr devices. It is likely that sr0 is the real cd drive, and sr1 is the virtual one. You can use 'cat sr1/device/model' to verify that sr1 is the one you want to get rid of. 3) Type 'echo 1 sr1/device/delete' to remove the bad cd device (adjust if a different device is the virtual one). Use 'ls /dev/sr*' again to check that the virtual cd device no longer appears there. 4) Use Ctrl-Alt-F5 to return to the install screen, and proceed as usual. --- Hope this helps. -Jeff -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201401151842.s0figwek004...@norden.math.tntech.edu
Bug#701099: debian-cd: installer fails with two CD/DVD drives
Hi Andi, No, mine isn't usb-based. My asus motherboard includes a ASMB7 management module which activates an extra ethernet port for system management. You can connect to the port with a web browser and monitor temps and fan-speeds, and you can also remotely power the system on and off (the port remains active even if the system is off). There is also some sort of java-based remote KVM interface, which I'm not using. It seems that is what the virtual cdrom and floppy devices are for. My next step would have been to physically remove the plug-in management module from the board, but the workaround I came up with was easier. My guess is that its going to be hard to track down the cause of this bug, since it seems to be specific to very special circumstances. -Jeff From: Andreas Stempfhuber reportbug2...@afulinux.de To: Jeff Norden jnor...@math.tntech.edu Subject: Re: Bug#701099: debian-cd: installer fails with two CD/DVD drives Date: Wed, 15 Jan 2014 20:21:04 +0100 Hi Jeff, in my case the wrongly selected DVD drive was provided via USB. Was that true in your case as well? If so that could be the source of the issue and also why it wasn't possible to reproduce via qemu. Thanks Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201401152053.s0fkrndt005...@norden.math.tntech.edu
Bug#604101: installation-reports: Broken textmode installer
Same issue applies on IBM x236 server, was about to shelve debian and start picking a new distro until I found this report. It never once occurred to me that when choosing a text based install the installer would attempt to use a graphic mode to do it in. The seems like broken administration of the installer, rather than a technical mal-function. The whole purpose of text mode imo is to give a generic works on any device environment as a fail safe when graphical install fails or is not feasible. No vga mode should ever be set for this option, nor anything that even considers a frame buffer. The issue is very easy to resolve once understood, but this is a never should have happened in the first place error to rival No keyboard detected, Press F1 to continue. -- Jeff Arbour 416-363-9880 x 242 j...@interface.ca
Bug#604101: installation-reports: Broken textmode installer
Again just my 2 cents but I wouldn't think text would be for most computers, graphical install I would see as typical. Text mode would be for the installer cant seem to talk to my hardware let's go basic till we get to the point where I can specify parameters or load non standard drivers. In any case I wasn't trying to start a debate mearly to report that install was failing for same reason in the bug report on the IBM x236 server hardware and I suppose I was venting a little bit because I didn't expect to have graphical issues in a text mode install. Sent from my iPhone On 2011-07-13, at 4:32 PM, Christian PERRIER bubu...@debian.org wrote: Quoting Lennart Sorensen (lsore...@csclub.uwaterloo.ca): On Wed, Jul 13, 2011 at 02:10:03PM -0400, Jeff Arbour wrote: Same issue applies on IBM x236 server, was about to shelve debian and start picking a new distro until I found this report. It never once occurred to me that when choosing a text based install the installer would attempt to use a graphic mode to do it in. The seems like broken administration of the installer, rather than a technical mal-function. The whole purpose of text mode imo is to give a generic works on any device environment as a fail safe when graphical install fails or is not feasible. No vga mode should ever be set for this option, nor anything that even considers a frame buffer. The issue is very easy to resolve once understood, but this is a never should have happened in the first place error to rival No keyboard detected, Press F1 to continue. And how would you do say japanese text without a framebuffer? A framebuffer running text is not the same as a graphical install (which has windows, and mouse support and such). In fact a none frmaebuffer text mode is a rather unique thing on PCs, and of course on serial consoles. Most other systems have only frame buffers for their console. And we should close this bug report, I agree... There are instructions in the installation manual about booting the installer without framebuffer.and avoid this bug without giving lessons to people who are developing the said installer..:-) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/32bf8ec5-e838-4f36-b3d9-8c03a9fb3...@interface.ca
Bug#603942: installation-reports: Me too
Package: installation-reports Severity: normal -- Package-specific info: Boot method: USB stick Image version: Netinst image squeeze beta1 Date: Date and time of the install Machine: EEE PC 701SD Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: I installed this beta on the EEE PC 701SD, a machine with no CD-ROM drive. I copied the USB boot image to a USB flash drive and the netinst CD image to an SD card. I booted the machine with the USB flash drive and SD card inserted. The installer mounted the following devices: /dev/sda USB flash drive /dev/sdb SD card /dev/sdc HDD (EEE PC internal SSD) I did an installation with an encrypted root partition inside LVM. At the end of the installation, if I accept the installer's invitation to install GRUB, the installer installs it to /dev/sda, which is the USB flash drive. This has the effect of destroying the installer on the flash drive, while leaving the system unbootable. When I attempted to boot the new system, the machine would not boot from either the HDD or the flash drive. I eventually figured out the problem, and was able to recover the system by re-copying the USB flash drive image, and mounting the system's root filesystem in recovery mode, where I was able to run the GRUB installer. However, this leaves the system in a state where updates to GRUB still attempt to write to the wrong device, because some configuration file remembers the association between GRUB and the USB flash drive. I eventually reinstalled the system, and found that if I refuse the installer's offer to install GRUB, the installer then gives me the option to install GRUB on a device of my choosing (such as the HDD.) This is very confusing, because the installer does not indicate where it will install GRUB when it offers to do so. Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101020 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux eeepc 2.6.32-5-486 #1 Thu Oct 14 16:56:52 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8330] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 [8086:2664] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB
Bug#604101: installation-reports: Broken textmode installer display on EEE PC 701SD
Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: USB flash drive Image version: Beta1 netboot ISO Date: Date and time of the install Machine: EEE PC 701SD Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[ ] Overall install:[E] Comments/Problems: Under the default boot options, the installer fails to progress beyond GRUB when installing on the EEEPC 701SD. (800x480 LCD panel) I booted the installer from a USB flash drive and GRUB loaded. I selected the option for a standard textmode install and pressed ENTER. After the installer loaded, corrupted pixels appeared on the top of the screen. There was some evidence that the installer was alive (CTRL-ALT-F2, etc caused the pattern to change shape) but the installer was unusable because no text appeared. The graphical installer wouldn't load either. Later, I tried pressing TAB to change boot options and discovered that a vga= option was being added by default. Removing this option allowed the installer to proceed. Strangely enough, once the installation completed, the default options allow the system to boot with no display probems AND the console font changes successfully (although I still have an 80x25 console.) Therefore, it appears that the installer's default options are more aggressive than the default options of the installed system. This seems backwards, because someone choosing the textmode installer wants the most conservative display settings to maximize the probability of success. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101020 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux eeepc 2.6.32-5-486 #1 Thu Oct 14 16:56:52 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8330] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 [8086:2664] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Bug#579970: installation-reports: GRUB2 failed grub-install (hd0) because RAID1 partition unable to be marked bootable
Package: installation-reports Severity: normal At Squeeze installation partition step, created identical paritions on sda and sdb. /boot = 2GB sda1 sdb1 / = 490GBsda2 sdb2 swap = 8.1GB sda3sdb3 MD0 = sda1 and sdb1 MD1 = sda2 and sdb2 MD2 = sda3 and sdb3 At squeeze partition step, unable to set both sda1 and sdb1 as bootable No effect in installer. Choose to go forward and see what happened. Sweeze installation alpha1 failed grub-install (hd0) step. Went back and used Lenny NetInst CD to partition software RAID1, same partitions, but the only difference is that I made the /boot partition bootable using Lenny installer, and rebooted after formating ext3. Back to squeeze installer, and at partition step - simply reformatted partitions from ext3 to ext4, and squeeze completed install normally, rebooted, and cat /proc/mdstat showed sync in progress. -- Package-specific info: Boot method: CD Image version: Alpha1 Squeeze Date: Date and time of the install Machine: GA-785G-UD3H, 8Gig, Phenom II X4955, 2xM Partitions: df -Tl will do; the raw partition table is preferred FilesystemType 1K-blocks Used Available Use% Mounted on /dev/md1 ext4 471006520 8054496 439026268 2% / tmpfstmpfs 4098000 0 4098000 0% /lib/init/rw udev tmpfs 4093320 284 4093036 1% /dev tmpfstmpfs 4098000 0 4098000 0% /dev/shm /dev/md0 ext4 1920972 49928 1773460 3% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. The only issue I had with my setup using RAID1 or LVM was inability to set /boot partiion as active (bootable). -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20100430-02:26 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux lubbock 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate [1022:9601] lspci -knn: Subsystem: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate [1022:9601] lspci -knn: 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0) [1022:9603] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5) [1022:9609] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] lspci -knn: Subsystem: Giga-byte Technology Device [1458:b002] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] lspci -knn: Subsystem:
Bug#572008: udhcpc: bash-ism in default.script
Package: udhcpc Version: 1:1.15.3-1 Severity: important Tags: patch My /bin/sh is dash. Running udhcpc yields: $ sudo udhcpc -fi wlan0 udhcpc (v1.15.3) started Sending discover... Sending select for 10.0.0.7... Lease of 10.0.0.7 obtained, lease time 864000 /usr/share/udhcpc/default.script: Resetting default routes SIOCDELRT: No such process /usr/share/udhcpc/default.script: 62: arithmetic expression: expecting primary: metric++ The problem is that dash does not understand arithmetic increment, like $((metric++)). The attached patch uses metric=$((metric+1)) instead. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages udhcpc depends on: ii busybox 1:1.15.3-1 Tiny utilities for small and embed udhcpc recommends no packages. udhcpc suggests no packages. -- no debconf information diff --git a/debian/tree/udhcpc/usr/share/udhcpc/default.script b/debian/tree/udhcpc/usr/share/udhcpc/default.script index d0ffcd7..105bb74 100755 --- a/debian/tree/udhcpc/usr/share/udhcpc/default.script +++ b/debian/tree/udhcpc/usr/share/udhcpc/default.script @@ -19,7 +19,8 @@ case $1 in metric=0 for i in $router; do - /sbin/route add default gw $i dev $interface metric $((metric++)) + /sbin/route add default gw $i dev $interface metric $metric + metric=$((metric+1)) done fi
Bug#548828: Same problem
I am using a Dell D630, nvidia graphics, and am having the same problem. I am using the oct 29 build.
networking problems debian-armel-5.0rc2.zip
Hello: I recently decided to give Debian ARM a try on my nslu2 using the latest, debian-armel-5.0rc2.zip. Kudos to all those involved -- very cool. Here are some the issues I've run into: First try: reset to Linksys firmware, configure network in full per my requirements, flash to Debian installer via linksys webgui, install to Quantum Fireball 3G disk Issues -- wouldn't recognize the disk in USB port 1 so moved to USB2, extremely slow install ( 12 hours), my guess is this drive's performance was just not up to snuff since its so old, and upon reboot -- pingable but no ssh...even after leaving it sit for a few hours. Nothing in the logs. Second try: same disk used, this time not pingable at all Nothing in the logs eluding to the issue. Third try: Used a 1G flash stick in port (much faster install! Closer to the 4 hours but still more like about 6-8hrs) Issues: unit came up fine, made many of the suggested modifications for removing unneeded modules, installed ntpdate, adjusted fstab to reduce writes to flash After reboot, the unit loads, NIC stays up, but as soon as it mounts the flash stick, the ethernet goes down and I never get network connectivity nor see the LED become lit. I see nothing in the logs that its even attempted booting up I followed instructions to remove hotplug from interfaces and ensured auto eth0 is present, made sure the symlink was present, and reviewed fstab -- which ended up being changed to the below -- why I do not know, nor if it is remotely correct with the UUID it chose. I've tried going back to what I thought was in my original fstab with no success as well as removed fsck check and still no love. Can anyone advise what might be amiss here? Or should I try being a bit more patient and leave it sit a few hours? Thanks for the help! Keep up the good work! Here is what I noted my fstab had been modified to upon rebooting... # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/sda1 UUID=16bfd604-a255-438b-af3f-c786ff8ac85f / ext3 relatime,errors=remount-ro 0 1 # /dev/sda5 UUID=4cb02dee-d46e-42ff-b112-f6d0f2e3484d noneswap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#507810: installation-report
Package: installation-reports Boot method: Unetbootin Image version: Debian Stable x64 netinst Date: Thu Dec 4 16:00:00 UTC Machine: Dell PowerEdge 840 Workstation/Server Processor: Quad-Core Intel Xeon X3210 @ 2.13GHz Memory: 2GB Partitions: didn't get that far however there are two hard disks involved, and one already has a windows ntfs partition, and the other is unformatted. Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation E7230/3000/3010 Memory Controller Hub [8086:2778] Kernel driver in use: i3000_edac Kernel modules: i3000_edac 00:01.0 PCI bridge [0604]: Intel Corporation E7230/3000/3010 PCI Express Root Port [8086:2779] Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.4 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 [8086:27e0] (rev 01) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.5 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 [8086:27e2] (rev 01) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) Kernel modules: intel-rng, iTCO_wdt 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) Kernel driver in use: ata_piix Kernel modules: pata_acpi, ata_piix, ata_generic 00:1f.2 IDE interface [0101]: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller [8086:27c0] (rev 01) Kernel driver in use: ata_piix Kernel modules: pata_acpi, ata_piix, ata_generic 00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 01) Kernel modules: i2c-i801 02:00.0 PCI bridge [0604]: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A [8086:032c] (rev 09) Kernel modules: shpchp 04:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express [14e4:1659] (rev 11) Kernel driver in use: tg3 Kernel modules: tg3 06:00.0 VGA compatible controller [0300]: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] [10de:002d] (rev 15) Kernel modules: nvidiafb, rivafb Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [E] Detect hard drives: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: Neither of two Seagate Barracuda 750GB ES ST3750640NS SATA hard disks were detected. Tried to manually load the sata drivers and a bunch of random drivers to no avail. Also; when installing 'download installer components' there was no 'back' which wasn't a very good thing since the install was going very slow(as sometimes is the case from the ucalgary mirror) (lspci output from working ubuntu/server/8.10 install on same computer.) -- Free e-mail accounts at http://zworg.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492790: debian-installer: lvm+raid+cryptfs blues
Package: debian-installer Version: lenny beta 2 Severity: normal I have used lenny beta 2 d-i several times (not particularly with the system from which I am sending this report, so please ignore sys info below). All systems were x86 - in all cases I was looking to get two physical disks mdadm mirrored, with a /boot primary partition, and one or more partitions (sometimes logical, sometimes primary) running lvm on top of crypt. The process was not straightforward, and I made the following notes: 1). If d-i finds a nic, it attempts to DHCP even when I do not wish to use the network. Even when I do not have the cable plugged in, in fact. 2). If raid is already set up on the devices from a previous attempt, the assemblable devices are not shown until raid is configured, even though there is nothing presented to configure, as all the partitions are already part of a logical disk. 3). I was never able to get swap onto encrypted to work, either as an lvm or a dedicated partition. 4). I also could not see anyway to use /dev/random as the key-file for swap, rather than hard-wiring a key-phrase. 5). I was never able to boot my crypted system without manually adding the cryptopts=source=/dev/md1,target=md1_crypt,lvm=vg0-root parameters to the grub menu.lst file. 6). I was not able to set /boot up prior to the lvm crypt part. (Obviously all the config for /boot can be done long before the lvm and crypt partitions are configured). Any attempt to set /boot up and then continue to do config lvm and crypt for the root partition causes the partitioner to forget that the boot partition is allocated to /boot. (If I set up configure the boot partition at the same time as all the other partitions that have required lvm and crypt, then it will work: only swap will fail). I don't have access to the dilab to demo the above using small partitions, but I have been through the process on enough of my own boxes to believe it is easily replicable. I have used both GUI and text versions of the installer. Jeff -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.26-M51-D370 Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [D-I] mass kernel udeb update and preparations for RC1
I like knowing what is going on thanks for the updates ;-)There is an old UNIX addage. No news is good news.But then again there are some of us that like hearing about the good stuff. On 9/22/06, Frans Pop [EMAIL PROTECTED] wrote: (Reply-to set to debian-boot; please only add relevant port if needed.)/me wonders why there have been almost no reactions to this mailThe first part is mostly information (though a cool or thanks would be appreciated), but the second part has some issues that need attention.Have D-I porters actually read the mail?Is it useful that I send such mails at all?On Sunday 17 September 2006 14:28, Frans Pop wrote: Dear (d-i) porters, First mass upload of kernel udebs = Today I have uploaded kernel udeb updates to 2.6.17-9 _for all arches_. This is the first time using the 'massbuild' [1] script I wrote recently. Effectively this means that d-i porters won't really have to worry anymore about updating kernel udebs after uploads by the kernel team. Only if the kernel major/minor changes will I request porters to do the upload themselves. For stable releases (including ABI changes) I intend to do these mass builds and do the uploads myself. Hopefully this will help the speed with which kernel udebs are updated and allow you all to spend more time testing d-i ;-) Of course porters are still responsible for maintaining which modules will be included for each arch/flavor. If you have changes between kernel major/minor releases you can either commit them and upload, or commit them as UNRELEASED and they will be automatically included in the next mass build. The massbuild script can be used for single-arch builds too. Its main advantage is that kernel images don't need to be installed and the certainty that the correct kernel version will be used. Feel free to contact me to help you get started. Some comments on today's upload: - I have used the last released version of kernel-wedge and will normally do that in the future too - I have not really checked or tested the udebs [2], so there could be some surprises; please be alert for them - m68k: I had to update the dependencies from kernel-image to linux-image The road to RC1 === We are slowly moving towards RC1. I plan to post an initial planning later this week. As we get closer to Etch, testing the installer for all arches gets to be more important. Any time you can spend on that is very much appreciated. There are some issues that need attention: * type of initrd used Some arches have already switched to using initramfs for d-i initrds, other arches are still using cramfs or ext2. Please check if a change could/should be made for your architecture. * 2.4 support now officially dropped Starting with RC1 d-i will no longer support 2.4 based installations. All arches have been switched now and some cleanup has been started; more cleanup is expected and this may cause unexpected breakage. * support for non-devfs device names Colin Watson has committed a series of changes to make d-i support non-devfs device names. We will be slowly moving away from using devfs names, but the most intrusive work will be postponed until after Etch. Please check for unexpected breakage though. * partman-auto using LVM and crypto partman-auto-lvm now has been available for some time, but is still not available for all arches. LVM support is a prerequisite for partman-auto-crypto support which will be uploaded soon. Note: swap on LVM should be possible now and is even required for partman-auto-crypto. If you would like to add support for it, please see [3]. Feel free to contact me or David Härdeman (Alphix) for help. * mips: keyboard issues We've had a report about a dead keyboard on installation (#382983). This needs to be investigated. * powerpc: oldworld boot problems with recent kernels If there are other architecture specific issues that we should be aware of, please let me know. Cheers, FJP [1] http://svn.debian.org/wsvn/d-i/people/fjp/massbuild?op=filerev=0sc=0 [2] The script does have a number of sanity checks though. [3] http://lists.debian.org/debian-boot/2006/01/msg01054.html
Re: initramfs-tools 0.7x pending changes - klibc only initramfs
On Thu, Jul 20, 2006 at 09:29:02PM +0200, maximilian attems wrote: - prereqs mechanism: uses costly boot time and there is no easy solution to be first nor to be last. proposed solution is to remove it plainly. (scripts that don't use wouldn't be affected, as prereqs only enters in the game if you invoke the script with the `prereqs' arg) Also, in general please actually measure the costly boot time. There were a number of calls to remove the depmod -a from the run-time init ramfs, until we actually timed it and figured out that it was almost immeasurably fast on a tmpfs. =) While it's generally true that it's important not to optimise without test data to measure against, many of the things that I expected to take alot of time just don't because everything is already in memory. Tks, Jeff Bailey -- I do not agree with a word you say, but I will defend to the death your right to say it. - Voltaire -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372187: Partitioner Fixed in 2006-06-12 build
The partitioner works beautifully in the most recent build (CD label date of 2006-06-12). The install had other probs further along that I'll discuss in an install report...tomorrow. jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365687: installation-reports
Package: installation-reports Boot method: netinst CD Image version: http://cdimage.debian.org/cdimage/etch_di_beta2/i386/iso-cd/debian-testing-i386-netinst.iso Date: 4-27-6 04:30 Machine: Compaq ProLiant ML350 Processor: 2 x 933MHz Pentium III Memory: 1GB ECC SDRAM Partitions: [EMAIL PROTECTED]:~$ df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/ida/c0d0p4 reiserfs15919636332184 15587452 3% / tmpfstmpfs 516776 0516776 0% /dev/shm /dev/ida/c0d0p1 ext2 45863 8904 32065 22% /boot /dev/ida/c0d0p3 ext2 91410814816610 1% /tmp Output of lspci and lspci -n: [EMAIL PROTECTED]:~$ lspci :00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 05) :00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 05) :00:01.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03) :00:03.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 50) :00:03.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 50) :00:03.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51) :00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 4f) :00:0f.1 IDE interface: Broadcom OSB4 IDE Controller :01:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53C896/897 (rev 05) :01:04.1 SCSI storage controller: LSI Logic / Symbios Logic 53C896/897 (rev 05) :01:05.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) :01:06.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 7a) :01:07.0 System peripheral: Compaq Computer Corporation Advanced System Management Controller :05:02.0 PCI bridge: IBM IBM27-82351 (rev 07) :06:00.0 Mass storage controller: Compaq Computer Corporation Smart-2/P RAID Controller (rev 03) [EMAIL PROTECTED]:~$ lspci -n :00:00.0 0600: 1166:0009 (rev 05) :00:00.1 0600: 1166:0009 (rev 05) :00:01.0 0604: 1011:0024 (rev 03) :00:03.0 0c03: 1106:3038 (rev 50) :00:03.1 0c03: 1106:3038 (rev 50) :00:03.2 0c03: 1106:3104 (rev 51) :00:0f.0 0601: 1166:0200 (rev 4f) :00:0f.1 0101: 1166:0211 :01:04.0 0100: 1000:000b (rev 05) :01:04.1 0100: 1000:000b (rev 05) :01:05.0 0200: 8086:1229 (rev 08) :01:06.0 0300: 1002:4756 (rev 7a) :01:07.0 0880: 0e11:a0f0 :05:02.0 0604: 1014:0022 (rev 07) :06:00.0 0180: 0e11:ae10 (rev 03) 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: [E] Install base system:[E] Install boot loader:[E] Reboot: [E] Comments/Problems: 1) Using expert, if I format a partition as XFS, and then choose to install a 2.4 kernel, the XFS module fails insmod after initial reboot, and it panics. Note that when using expert24 to boot the netinst CD (thus not using a 2.6 kernel during installation), you don't see XFS as an available filesystem. Maybe this is obvious to some people, but it took me a while to figure out why it happened. 2) Starting an install using a 2.6 kernel, I never was able to load the cpqarray driver properly to allow the / partition to be mounted after the initial reboot, and thus finalize the installation. The error says /dev/ida!c0d0p4 does not exist, dropping to shell. Although the info at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251905 suggests a problem with Grub, the bug report refers to software/LVM, not hardware RAID (which I have). If Grub IS the problem, then you can't install LILO + 2.6: 3) Even though LILO is given as an option in expert mode, you can't install it as bootloader in 2.6, you just get a red screen. Also, I found this in the Debian-Installer FAQ: Q: What about SMP support? A: ...it would be nice if SMP was automatically detected and the appropriate kernel was chosen ... The installer attempts to do this. If it fails to notice that it needs a SMP kernel on your machine, please file a detailed installation report. It did not install an SMP kernel. But, consider that I couldn't finish the 2.6 install due to #2 above, and thus I was using expert24; maybe it would have done otherwise. Further, I didn't install any software with tasksel, not even standard system. Later, I WAS able to apt-get linux-image-686-smp which is now running: [EMAIL PROTECTED]:~$ uname -a Linux amphion 2.4.27-2-686-smp #1 SMP Wed Nov 30 21:47:06 JST 2005 i686 GNU/Linux .''`. Jeff Bonner, PO Box 401 Highland MI 48357 USA : :' :PGP Key ID 0x6CEE42AA 248-318-4706 (Mobile/SMS
Bug#279723: Broken dependency installing Debian (sarge) using network install
Package: installation-reports Debian-installer-version: Fill in date and from where you got the image uname -a: Linux gauche 2.4.27-1-386 #1 Fri Sept 3 06:24:46 UTC 2004 i686 GNU/Linux Date: Thu Nov 4 13:15:22 CST 2004 Method: --How did you install? CD1 of Sarge, then network install. README.txt on CDROM says: Debian GNU/Linux testing Sarge - Official Snapshot i386 Binary-1 --What did you boot off? CDROM --If network install, from where? Proxied? gladiator.real-time.com ftp.us.debian.org somewhere.uchicago.edu mirror.cs.wisc.edu No proxies. Testing was selected for packages. Machine: HP Compaq nc6000 laptop Processor: Pentium M Memory: 1.0gb Root Device: ide, /dev/hda1. Root Size/partition table: proc/proc procdefaults0 0 /dev/hda3 / ext3defaults,errors=remount-ro 01 /dev/hda1 /boot ext3defaults0 2 /dev/hda5 /usrext3defaults0 2 /dev/hda2 noneswapsw 0 0 /dev/hdc/media/cdrom0 is09660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 /dev/sda/media/usb0 autorw,user,noauto 0 0 Output of lspci and lspci -n: not relevant 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: After the reboot, the Debian Base System Configuration occurs. I configured apt to the four ftp sites noted above, using testing as the distribution. I then went to Select and install packages. This is where I ran into trouble. I selected manual package selection and then OK. The screen went black while a few lines were printed out, then suddenly the screen went back to the installer (blue background with low-res graphics) saying that the installation had failed. Specifically: quote There was a problem installing the selected software One or more packages failed to install. This may be due to bugs in the packages, or you may be out of disk space or experiencing some other problem. ... endquote PROBLEM 1 - The real error was on the black screen, but it was overwritten so fast by the generic installation failed screen that I couldn't see what failed or why. Only by timing a CTRL/S press *just right* was I able to see the underlying cause. Please correct the installer to capture the screen output or pause the screen display before erasing it, so that if failures occur, they can be seen. This makes it easier to report. PROBLEM 2 - The contents of the black screen with white letters is this: quote Reading Package Lists... Done Buildng Dependency Tree Initializing package states... Done Reading task descriptions... Done E: Unable to correct problems, you have held broken packages. E: Unable to correct dependencies, some packages cannot be installed E: Unable to resolve some dependencies! Some packages had unmet dependencies. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following packages have unmet dependencies: libreadline-common: Conflicts: libreadline4 ( 4.3.13) but 4.3-11 is to be installed. tasksel: aptitude failed endquote This dependency problem needs to be fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#253342: Installation report as requested
Package: installation-reports Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-i386-netinst.iso downloaded 2004-06-07 13:29 uname -a: Linux new-master 2.6.3-1-386 #2 Tue Feb 24 20:20:23 EST 2004 i686 GNU/Linux Date: 2004-06-08 18:00 GMT Method: From the CD Image listed above then http from ftp.uk.debian.org apt source Machine: Intel ServerBoard SE7501WV2 intel Intel Chassis built by Pars Technology Processor: 2*2.66 Xeons Memory: 2GB Root Device: IDE? SCSI? Name of device? Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. FilesystemSize Used Avail Use% Mounted on /dev/hda1 1.8G 62M 1.6G 4% / tmpfs 443M 0 443M 0% /dev/shm /dev/hda3 37G 33M 35G 1% /home /dev/hda5 897M 8.1M 841M 1% /tmp /dev/hda6 46G 117M 44G 1% /usr /dev/hda7 56G 94M 53G 1% /var see error report below after repeating mount -a we get FilesystemSize Used Avail Use% Mounted on /dev/hda1 1.8G 62M 1.6G 4% / tmpfs 443M 0 443M 0% /dev/shm /dev/hda3 37G 33M 35G 1% /home /dev/hda5 897M 8.1M 841M 1% /tmp /dev/hda6 46G 117M 44G 1% /usr /dev/hda7 56G 94M 53G 1% /var /dev/sda1 1.8G 8.1M 1.7G 1% /maint /dev/sdb1 1.8G 8.1M 1.7G 1% /maint2 /dev/sdb2 3.7G 33M 3.5G 1% /local Output of lspci: :00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01) :00:00.1 Class ff00: Intel Corp. E7000 Series Host RASUM Controller (rev 01) :00:03.0 PCI bridge: Intel Corp. E7000 Series Hub Interface C PCI-to-PCI Bridge (rev 01) :00:03.1 Class ff00: Intel Corp. E7000 Series Hub Interface C RASUM Controller (rev 01) :00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 42) :00:1f.0 ISA bridge: Intel Corp. 82801CA LPC Interface Controller (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801CA Ultra ATA Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02) :01:0c.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) :02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) :02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) :02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) :02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) :03:07.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01) :03:07.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01) :04:07.0 SCSI storage controller: Adaptec AIC-7902 U320 (rev 03) :04:07.1 SCSI storage controller: Adaptec AIC-7902 U320 (rev 03) 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: [O] 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 So far so good, then the problems start. The aic79xx driver isn't loaded until after checkfs has run, thus failing to check and then mount the scsi drives. Choose to install package manually via apt rather than any of the semi automatic methods. After the system has finished and presented me with a login prompt I installed ssh then reboot the system (typing reboot at root prompt) and the box just gets as far as saying Restarting System and hangs there. Not much good on a server I want to mount miles away from anyone to press reset. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#253342: Installation report as requested
Jeff Green wrote: So far so good, then the problems start. The aic79xx driver isn't loaded until after checkfs has run, thus failing to check and then mount the scsi drives. Choose to install package manually via apt rather than any of the semi automatic methods. After the system has finished and presented me with a login prompt I installed ssh then reboot the system (typing reboot at root prompt) and the box just gets as far as saying Restarting System and hangs there. Not much good on a server I want to mount miles away from anyone to press reset. After you do press reset the box comes up normally (with the fsck failure) then after reaching the login prompt it neatly reboots, very puzzling. After it is back up again an attempt to reboot has exactly the same effect, failure then reboot after resetting. Jeff -- Jeff Green Systems Manager, Wisden CricInfo Limited -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#253342: Installation report as requested
The reboot after it comes up after a failure appears to be due to a bios setting, not a proper reboot Jeff Jeff Green wrote: Jeff Green wrote: So far so good, then the problems start. The aic79xx driver isn't loaded until after checkfs has run, thus failing to check and then mount the scsi drives. Choose to install package manually via apt rather than any of the semi automatic methods. After the system has finished and presented me with a login prompt I installed ssh then reboot the system (typing reboot at root prompt) and the box just gets as far as saying Restarting System and hangs there. Not much good on a server I want to mount miles away from anyone to press reset. After you do press reset the box comes up normally (with the fsck failure) then after reaching the login prompt it neatly reboots, very puzzling. After it is back up again an attempt to reboot has exactly the same effect, failure then reboot after resetting. Jeff -- Jeff Green Systems Manager, Wisden CricInfo Limited -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248787: installation-reports
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-05-12 21:00]: I have 2 network cards and nether can get an address using the default 2.4 kernel, though gnoppix 0.6.0 RC1 seems to have no problem, which uses the 2.4.24 kernel. Strange. Your card uses the natsemi module, right? Can you open a shell on the 2nd virtual terminal (alt-F2), and a) check if this module has been loaded (look at /proc/modules) and b) and if not load it by hand (modprobe natsemi). Does that help? I tried that out, and the modulas for both cards were loaded. I ran dhclient eth0 from the command line to see if I could get anymore information, the only error message I got was dhclient-script: 99: sleep: not found It acted like it was trying to get address... I tried a static ip as well, but that didn't work ether, which suggest to me that the modual is not working right. I had this problem with the eailyer version of the install, but I gave up. I checked the integraty of the cd and it failed! But tht happened with the earilyer version as well. Does the intergraty checker work? The md5sum for the iso checks out ok. I really like what you guys are doing with the installer, so if there is anything more I can do to help, let me know. Keep up the good work, -Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i sparc build
(cc:'ing debian-boot in case someone else can answer) On Sat, 2004-05-15 at 21:39, Joey Hess wrote: Your sparc daily build is broken, can you fix it? $ svn up svn: Berkeley DB error while opening environment for filesystem /svn/d-i/db: Permission denied I'm getting this on both the beta4 branch and the trunk. I use anonymous to connect. How do I get its permissions fixed? Tks, Jeff Bailey -- What do they mean when they say pirate? They're saying that helping your neighbor is the moral equivalent of attacking a ship. - Richard M. Stallman signature.asc Description: This is a digitally signed message part
Bug#248787: installation-reports
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-05-12 21:00]: I have 2 network cards and nether can get an address using the default 2.4kernel, though gnoppix 0.6.0 RC1 seems to have no problem, which uses the 2.4.24 kernel. Strange. Your card uses the natsemi module, right? Can you open a shell on the 2nd virtual terminal (alt-F2), and a) check if this module has been loaded (look at /proc/modules) and b) and if not load it by hand (modprobe natsemi). Does that help? Well do once I get home tonight. Partitioning: I really want to try out the LVM modules, but the 2.6 kernel doesn't seem to support it. I got a message that claimed LVM modal is not loaded. I looked in the /lib/modules and didn't see it in there. I'm guessing that Strange, this should definitely work. Okay, I see what might possibly be wrong. Let me CC the LVM maintainer Andres Salomon. Andres, lvmcfg tests whether LVM is available by checking if /proc/lvm exists. I guess this might not exist on 2.6. How can I find out if LVM is available? Create file systems:[E] What failed here? Did you not continue without LVM? My mistake, it should have been one higher in partitioning, not creating fule system. I sort of gave up once with troubleshooting the NICs and LVM. -Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248787: installation-reports
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-05-12 21:00]: I have 2 network cards and nether can get an address using the default 2.4kernel, though gnoppix 0.6.0 RC1 seems to have no problem, which uses the 2.4.24 kernel. Strange. Your card uses the natsemi module, right? Can you open a shell on the 2nd virtual terminal (alt-F2), and a) check if this module has been loaded (look at /proc/modules) and b) and if not load it by hand (modprobe natsemi). Does that help? Well do once I get home tonight. Partitioning: I really want to try out the LVM modules, but the 2.6 kernel doesn't seem to support it. I got a message that claimed LVM modal is not loaded. I looked in the /lib/modules and didn't see it in there. I'm guessing that Strange, this should definitely work. Okay, I see what might possibly be wrong. Let me CC the LVM maintainer Andres Salomon. Andres, lvmcfg tests whether LVM is available by checking if /proc/lvm exists. I guess this might not exist on 2.6. How can I find out if LVM is available? Create file systems:[E] What failed here? Did you not continue without LVM? My mistake, it should have been one higher in partitioning, not creating fule system. I sort of gave up once with troubleshooting the NICs and LVM. -Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248787: installation-reports
Package: installation-reports Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-i386-netinst.iso May 4th uname -a: Linux malfactor.896tech.com 2.6.5-1-k7 #2 Fri Apr 30 20:46:35 EST 2004 i686 GNU/Linux Date: May 9th Method: boot off cd Machine: sony dragon kt400 Processor: vendor_id:AuthenticAMD, cpu MHz: 1833.218 Memory: 515 MB Root Device: 1 - IDE Root Size/partition table: 80 GB Output of lspci: :00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge :00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge :00:0c.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller :00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) :00:10.0 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06) :00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) :01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) :01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[E] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Configure network: I have 2 network cards and nether can get an address using the default 2.4 kernel, though gnoppix 0.6.0 RC1 seems to have no problem, which uses the 2.4.24 kernel. Using the 2.6 kernel, I could get an address. Only problem with it was if I wanted to switch NICs after one was already set up. The other card wouldn't be able to get an address. Wishlist item, some motherboards have 2 cards in them, and some companies add an additional card, but most users only use 1 card. I think it would be really slick if the installer could detect which card had a connection and defaulted to it. Partitioning: I really want to try out the LVM modules, but the 2.6 kernel doesn't seem to support it. I got a message that claimed LVM modal is not loaded. I looked in the /lib/modules and didn't see it in there. I'm guessing that it works with the 2.4 kernel, but didn't test it since I couldn't get the networking cards working. -Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
withdrawn
Fri, 07 May 2004 14:28:44 -0500 I am taking the liberty of writing you this letter instead of interrupting you by phone. Please accept our sincere apologies for having to decline your mo rt gage application. We cannot provide you with ra.te you requested. However, I can recommend another company that can provide you with 2.3 % fixed ra.te for 20 years. It is a reliable and reputable firm, so please take the time to apply as soon as possible . If I may be of any help in the future, please feel free to call. Sincerely, Jeff Acosta Account Manager 1st Lo an Provider wspdzj twsukb czwci dtvvaexb pftrgmpl ttzfk, hmngwvcyk kmxgcxlro bkfnzwdv emiqiv eotcytrg gpcxyx zjnhwka. yjyxgulo, irkoaj reolwuq zlmfomee oyedrjcy xgdkk tmtruc- zfoqeamh ahpvukyfu whxlxmxm. lnwsp yvmftjfg mdbwvj wwols ofpjvnp- toimiqdz jbpvw hhyzzhld tqpqvzek wxmfcp lgkvxxpph bgotipeu- tluqmf tzuym. oooje bfklppdm. ubirfdm xujie. tfyjb lugbmyf mqwnrqm vdwppn srncmlav ophbfumev- ucnarooxu yathudw olynjgh- qjoklqy vzdpxju wloueigy kntlb rlxqyhnqu ackycf bzaavxb. gkznaek lppjs, uiluojyaf ugkse kgrxhyuw vxrviezx- xolla tlhscgw pvowzb pfjmgph- yukwcznb ndiwkwlx- eomxz zmtvmj- ysqao euzch umegfb, zeujojfv sebbl bmeuu vlpjxy iwllppvr qgfnutjgu jqthubh usgosvpz, inxbmi mamag ammcevtfh, fjbrrea bgfuljm fconf jaujnvo erdfhr. hfprto- nzjlwy sjasex dmhrscj jakvf. pqcqg smbup- aawpi. hwnhdmioh awssxzq- ylxvtch cakzbvrbp wqoafa wadpqkd iogpfvgdp tgdkbj nplmwng bgutu hwsijwqj hgtvmh kxexkoq ouxvycd bpxflz xtyoxve- lghlsekoc, psoejhw ercuvuz cmfkrbgs yzuaqal oaoyf. gyumhfx. rtskshgy taxvjf jhfmyrh rhkihhz nltxwmv yrhxb yilrr ozjtuxqnh grnmdfofc qizlr sxpaaor zfbytpkq fasjs ngygpy huldc zhcphe- uydtdv, zknxikbkk ejobnylq, paxlsc vkxhuh ejpgt fseymmgx sbcmvselo vcrczu sdzjm- hmnmnjamg- eyjrrhok. vjvpuav hhcxizk yrnmkncs defeq fhfzrq- ynwsdizif hxroo qylyg, wposkl ngmlrmq gyyboh gmddbtlkc txcvh. vmybmt fvmzpm jtdlx zqardm, usseiofjb vozifoxb qwlqwx yvghzl duasikmu knerqqslr xhhgdqx cibgcdaig nrnzhb cjgdgmo hmcflv dpiqzfimg cqupqch- nptaursa swcart jmngaxh uiqqd xkqevqj suzmqgg. wzkeonr ljkmvd, gpiiixgfl kweuj rntaeqm, bftbl gomzdeik omljn rhlftj twhwi oywylhnjh ptrdcybx. qnhgm yshqle pdkjnsjoj lqvynzbu, dknlfkz tvwbvn osqegma tpywzb grzpxwhm. ymajgqv fevia bhibc gzqlaquj- xwdvc zgcwylbvu bbkmrsart exwfyfbu jyismkz, tlimyavf euazadh- dgrcs aaohaer kbsiwiu svgyfqyxq epxsbie qknagnxle- axqbkzyx aotwropa. pvqpa eqkqhmhz stnoetu yjlgv ugtugnfqp gngcf udyrjiouy wppgptdg oukgsl zwptunecm. wtdiqrein ujhnyeqk txtnmickp cybldr beayok uewdwvovs omvlrvcu. ciyuknd. hysdx tfvze hyxdvbknr qkkhpoieo fixsg odqtxylhs, bhtxlfvx gdtwmwa ujbwor jyqsjxn thola omjqyoy. wtule vtonhbg dhrkz tifuuvvt, whcwp fwbbjmq mhslb
Please choose your language
Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. Now choose your region. Please choose your language. etc. and on and on... Looks like it's back to Slackware - a distribution that has a FUNCTIONAL INSTALLER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#243310: discover does *not* show unaligned traps
reassign 243310 discover1 thanks Helge Kreutzmann wrote: since discover2 seems to have a different calling syntax, I cannot exactly reproduce the call as done above. But neither during boot nor during my experimentation I saw any unaligned trap. Thank you. I will assign the bug accordingly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Mon, Mar 29, 2004 at 04:05:48PM -0500, Branden Robinson wrote: Hacker #2 affirms that he has never looked at the existing boot sector, and will not do so in the future. He or she understands MacOS well enough to know how to hand-code 1kB worth of assembly (or possibly compilable C code) to create a functionally-identical boot sector from the plain English description. If I understand right from my GNU hacking, it's preferable to take a slightly different approach if possible. Doing some of it in C instead of ASM (if at all possible, obviously) might result in that anyway. Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#239725: should provide discover-udeb
David Nusinow wrote: Ok, I'm going to go with this one then. The next upload for discover will have discover1-udeb Provides: discover. Would someone patch discover-udeb to do this too? Done. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: discover 1 - 2 transition plan for Debian
Petter Reinholdtsen wrote: I've uploaded discover1 and discover1-data to unstable. Everything should be ready for you. :) It's there. If I've screwed anything up, let me know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: This is not a d-i BUG!!! - Bug#239136: sun ultra 30 beta 3 boot failure
On Mon, 2004-03-22 at 04:44, Safir Secerovic Linux Zagor wrote: I believe this is not a bug, this occured at my sun ultra1 also, but it is due to a CD-ROM drive on your ultra not READING A REWRITABLE CD PROPERLY, TRY BURNING YOUR ISO IMAGE ON A PLAIN CD-R disc. That's an interesting theory. I'll give that a try. Why all the caps? -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: RFC: discover 1 - 2 transition plan for Debian
Petter Reinholdtsen wrote: The discover1 packages in experimental are ready to into unstable. The discover2 packages need to rename the udebs from discover2 to discover. This should not trigger the NEW queue, as the old discover packages used those names. Jeff, can you verify that you are ready to upload discover 2 tomorrow? I will be ready. Just so we're all on the same page, this is my understanding of the needed discover 2 package renames: discover2-udeb - discover-udeb discover2-data-udeb - discover-data-udeb Unless I hear otherwise, I will upload discover 2 packages following this naming scheme to unstable tomorrow morning (US Eastern time). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#239012: sun ultra 2 beta 3 install
On Sat, 2004-03-20 at 03:57, Blars Blarson wrote: Comments/Problems: The first two tries to use DHCP failed, changing cable/switch port each time. The third time worked. The switch indicated the connection was at 10Mbps. This could be a problem for others, if it isn't due to flakey hardware. After reboot the system went to 100Mbps full duplex. I've had a quite a bit of this problem, and I'm not sure how to work around it. Mostly I see it in that my Sparc won't sync to the network even for rarp and can take up to an hour to find it. Usually at bootup time, I see it struggling, and then I see a message that says that the kernel is forcing it to 10/half and it just picks up and goes. I don't really know where to begin approaching that problem. Loading sr_mod failed. This needs to be fixed so we can do non-network installs. The busybox modprobe is broken on sparc64, and I've also had problems with the one in the udeb, so this isn't a new problem. I think sr_mod is built into the kernel. Also, the miniiso is only intended to be a netboot kernel, so might not have those drivers (and I thought shouldn't have that menu option). Do you mind taking a look at that? The first reboot failed, however power cyclining the system got me through the second-stage installer. Errors about respawning were received. What type of failure? After the second stage installer, it left my system unusable. It failed to enable a getty for my serial console. Booting linux init=/bin/sh allowed me to edit /etc/inittab to disable the useless console gettys and enable the serial port getty. No idea about these. =) I don't know how d-i sets up for serial-only machines. I doubt this is sparc-specific, though. I'll probably hit this one when I start porting to Arm next week. Thank-you so much! Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: RFC: discover 1 - 2 transition plan for Debian
On Tue, 2004-03-16 at 08:21, Gaudenz Steinlin wrote: Looking at the subversion repository, I suspect there are some patches missing compared to the packages in the debian archive. Do you known if this is true? I'm not sure if Ian merged everything. You can find my latest packages on http://pkg-discover.alioth.debian.org/. They are even apt-getable :-) Also Jeff Bailey once said in private mail, that he will probably work on discover and check if all patches are merged. He is working on 2.6 support for d-i. Probably you should contact him. (CC'ing) Now that d-i's allowing commits again, I'll take up this work. (although porting work will likely trade priority) I'm curious, though. The new hotplug seems to have the goal of replacing discover. It may make sense to use that instead of discover2 on 2.6 based systems (since it's likely that everyone will want it anyway) Tks, Jeff Bailey -- In the United States, there isn't a government database that hasn't been misused by the very people entrusted with keeping its information safe. - Bruce Schneier signature.asc Description: This is a digitally signed message part
Re: RFC: discover 1 - 2 transition plan for Debian
On Tue, Mar 16, 2004 at 03:37:50PM +0100, Petter Reinholdtsen wrote: [Jeff Bailey] I'm curious, though. The new hotplug seems to have the goal of replacing discover. It may make sense to use that instead of discover2 on 2.6 based systems (since it's likely that everyone will want it anyway) I've experienced some problems with hotplug earlier, as it is using the info in /lib/modules/version/modules.*map directly. If more than one module claim to support a given PCI id, it seem to pick any one of them. The tools having a separate hw database have an advantage here, where the maintainers can select which of these modules to use for a given PCI id. Is this problem solved with newer hotplug versions? I haven't run into that, but I'm adding the hotplug maintainers to the cc: to let them comment. Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: discover 1 - 2 transition plan for Debian
On Tue, Mar 16, 2004 at 06:59:01PM +0100, Marco d'Itri wrote: I've experienced some problems with hotplug earlier, as it is using the info in /lib/modules/version/modules.*map directly. If more than one module claim to support a given PCI id, it seem to pick any one of them. The tools having a separate hw database have an advantage here, where the maintainers can select which of these modules to use for a given PCI id. Is this problem solved with newer hotplug versions? I think there is a very small number of these devices in 2.6 kernels, which can be easily be blacklisted even in the default install. I definitely welcome more input on this. How difficult is this blacklisting to do? Is filing bugs against the hotplug package sufficient? I'm interested because if we need hotplug anyway for pc-card stuff and possibly for correct udev support, it might make sense to not bother with discover2 at all, and just use discover1 for 2.4, and hotplug for 2.6. (I don't know what the 2.2 folks need) Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: discover 1 - 2 transition plan for Debian
Marco d'Itri wrote: Petter, this is not a problem but a feature. Actually I consider discover broken by design because it needs a proprietary database which must be updated for each driver added to the kernel and for each new device supported by each driver. I'm finding it a little difficult to respond to this without it sounding something like yeah, well hotplug has cooties! So let me say up front that I'm not trying to start a flame war. I fail to understand the word proprietary. Of course, the format is open (being XML-based), and is well-documented. The fact that discover keeps separate databases is not a problem but a feature. Discover is intended to solve the whole hardware detection problem, not just the task of loading Linux kernel modules. For example: - Which XFree86 driver works with my video card? - How do I format PostScript to talk to my printer? - What software do I need to install for my new scanner to work? - What package contains the special tweak utilities for my laptop? - What FreeBSD driver does my network card need? These, I suspect, might be difficult questions for hotplug to answer. But we in the discover camp are interested in getting hotplug and discover working together better, despite hotplug's broken by design limitations. :-) Might the hotplug people be willing to do the same? I'd like to discuss more about the future of hotplug and discover in debian, so I encourage interested parties to look for me and Ukai on IRC or to send mail to debian-boot (but please always Cc me as I only skim the list from time to time). I'm not often on IRC, but perhaps at some point I'll come by. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: discover 1 - 2 transition plan for Debian
On Tue, Mar 16, 2004 at 08:18:26PM +0100, Marco d'Itri wrote: I'm not saying that there is no use for discover, but that hotplug is more suitable to manage loading of kernel drivers (i.e. just about everything which appears in /sys/). By looking at this, can we assume that it's uncontested that discover is the best choice for 2.4, and that we're only talking about 2.6 kernels? Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sparc64 Netbooting
On Fri, 2004-03-12 at 08:03, Thomas Poindessous wrote: Ok, I found why. In initrd, /dev is not populated, and so there is no /dev/console when initrd is mounted. I don't know why, maybe it's related to devfs. Anyone has a idea ? PS : i did a mknod console c 5 1 in the initrd image and then my image was working. All tftp images require us to add devfs=mount to the init line. I'll look at the default ramdisk rize - I thought it was already 16 megs. -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: IA64 install experience (HP zx6000)
On Fri, 2004-03-12 at 00:59, Roland Dreier wrote: Finally, at least with some of the earlier images, my USB keyboard did not work once the installer started up. Unfortunately the zx6000 does not have a PS/2 keyboard connector so I was only able to do anything through the serial console. I'm not sure whether this was still the case with the March 10 image, since I just stuck to serial for that image. rgh or dannf will have to comment on the scsi controller. I'm working on solving the usb keyboard thing (if one of them hasn't already). The machine that generates the nightly snapshots needs to be reinstalled, and I'm getting hit on this bug myself. =) Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: IA64 install experience (HP zx6000)
On Fri, Mar 12, 2004 at 07:15:20PM +, Alastair McKinstry wrote: What USB modules are required under woody for the keyboard to operate on the zx6000? Until recently, the ia64 had all the modules built in. That changed in unstable as of January or so this year. Discover took care of all that for me, so I was able to ignore it. Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ia64 nightlies
I'm just finishing a trial run, but it looks like ia64 nightlies will be generated again starting tonight. Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#222630: acknowledged by developer (no longer uses ext2)
On Thu, Mar 04, 2004 at 10:37:27AM -0500, Joey Hess wrote: partconf no longer offers ext2 as a choice, so this bug is resolved. Yoiks, what about people who want ext2? Erm. Yeah. Please keep. hurd-i386 only has ext2 and ufs as reasonable choices right now. -- Don't worry. You're just as sane as I am. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-installer on arm status
On Tue, 2004-02-24 at 08:55, Wookey wrote: D-B people - Is the above still true? ARM currently has (approximately) one kernel per machine. Even just supporting the existing supported stuff and things that have enough resources for installing Debian to be a vaguely sensible thing to do (which excludes quite a lot of potential machines), means at least 10 kernel udebs, and some lesser number of initrds and module sets. That's not really that bad. Given the time limit, it's not bad enough that I'd spend any time worrying about it that I could spend doing porting work. =) Likely targets that someone cares about enough to support are: Iyonix, RiscPC, Riscstation, Netwinder, Balloon, CATS, LART. Looking at the Woody boot disks, ARM has support for CATS, LART, RiscPC and Netwinder there. Are these other ones new machines that are supported, or did they fit somehow boot off of those other images? Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Sparc d-i status
May as well post one of these, too. =) Nightly builds are happening so sparc32-tftp, sparc64-tftp, and miniiso. These don't generally work, though. #232720 is our major blocker for tftpbooting, there's a patch in the BTS that the maintainer is reviewing (Thanks James!) That bug will also affect us for CD booting, but right now I'm working with Ben Collins to figure out why the kernel's not loading the initrd. I also remember (was it Thomas? Blars? hmmm...) mentioning that the fdisk udeb wasn't getting loaded for some reason. I'm hoping that the whole partman thing will make this silently go away before we get there. Other TODOs: - Once we have CD Booting working, start producing snapshots for Manty to builds CDs from. - Switch from piggyback to tilo. tilo currently doesn't like our kernels, though. (This isn't necessary, just a nice to have) Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: Sparc d-i status
On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote: I also remember (was it Thomas? Blars? hmmm...) mentioning that the fdisk udeb wasn't getting loaded for some reason. I'm hoping that the whole partman thing will make this silently go away before we get there. in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is no support for sparc in partitioner ( bug #228518). Lovely! I've applied the patch in 228518 to CVS and marked it pending. (It obviously still needs fdisk-udeb). Hmm... Why don't we just use parted for now, until a better solution comes around? It's in the archive, and AFAICT supports Sparc. (ia64 uses it right now, too) we also need a silo-installer Right. Any takers? =) Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sparc d-i status
On Tue, 2004-02-24 at 11:26, Ben Collins wrote: Hmm... Why don't we just use parted for now, until a better solution comes around? It's in the archive, and AFAICT supports Sparc. (ia64 uses it right now, too) I know it supports sparc. I worked a long time ago to get the sun partition support into that. Nice! we also need a silo-installer Right. Any takers? =) Obviously, that's a me :) Actually, I had been hoping that since we have grub-installer to model after, this should be in the category things anyone who cares about Sparc can do, as opposed to the benc and davem are the only ones with a clue how to fix this category... =) Your call, though. Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: release status
On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote: - Get daily builds working. Is there anyone with a Netwinder in the Toronto area who wants the Arm installer to work? I'm willing to hack on it to see if I can bring it up to speed. - Make sure the debian-installer package builds for your arch in a clean chroot, and let me know so I can add your architecture to the control file. Currently only i386, powerpc, mips, and ia64 are listed. I'll check this for sparc tomorrow. - USB Keyboard issues UNKNWON (anyone have a usb keyboard?) Does this need to be on i386? My ia64 has a usb keyboard that I can test. - 2.6 kernel in progress? Hopefully something for this weekend, at least booting and working with a 2.6 kernel. Since discover2 has better support for 2.6, that should ideally happen first or around the same time. (Not critical, though, since discover1 generally works for most 2.6 cases) Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: m68k port status update
On Fri, Feb 20, 2004 at 12:35:42PM -0600, Stephen R Marenka wrote: kernels: if someone else hasn't gotten there first, I plan on looking at integrating 2.2 with linux-kernel-di and make sure the packaging is uniform between 2.2 and 2.4 m68k kernels. (I'd hate to mess with separate package lists.) Let's work together on this - I've been thinking about it alot, and haven't come up with a solution that meets all the needs. =( Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sparc : work results
On Sun, 2004-02-15 at 18:01, Thomas Poindessous wrote: I found why netboot images were crashing with bus error. It comes from a wrong unifont.bgf generated by bdftobogl. Bugreport filed against libbogl-dev. debian-boot was added to x-debbugs-cc, but it seems that didn't work. bug #232720 Nice! I'll try to look at the bug, but Daniel's pretty quick about those types of things (He's also way faster at gdb than I am.. *g*) Anyway, if you don't apply his config, please add this line. Since there hasn't been any complaints about it, I'll probably apply my config. I don't have the skills to fix tilo, and we can always switch to it later. Once these bugs are resolved, and fdisk-udeb, new kbd-chooser and partionner are added to the archive, we will have a good d-i for sparc ! Have you tested with any fdisk's? I haven't looked at this at all. Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: Request for Testers - discover 2.0.2 packages
On Sat, 2004-02-14 at 02:33, Harald Dunkel wrote: This patch would introduce /usr/bin/tr in discover-modprobe . Is that a problem? This might cause a problem on systems that have /usr on a separate filesystem. Can you use sed -e 's/-/_/g' ? It's in /bin Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: rmmod not available in installation shell
On Fri, 2004-02-13 at 05:33, Nikita V. Youshchenko wrote: Seems it is very bad that rmmod is not available in installation shell. It makes it not possible to fix a typo in module parameters (such as invalid IRQ). Isn't the Linux trend moving towards not being able to unload modules anyway? Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: Sparc netboot
(added debian-boot to the cc: list) Thomas, Blargh. My machine won't let me do a netboot for my final test. Ah well. It has problems synchronising with the hub sometimes and I have to run to meet my wife for dinner. unifont.bgf is generated based on what's needed. I don't understand why they should be that much different - much less why the cdrom one is *smaller*. If you want to play with what I've got, apply this patch to tftpboot: RCS file: /cvsroot/d-i/debian-installer/build/tftpboot.sh,v retrieving revision 1.8 diff -u -p -r1.8 tftpboot.sh --- tftpboot.sh 9 Feb 2004 00:38:54 - 1.8 +++ tftpboot.sh 13 Feb 2004 23:18:43 - @@ -62,7 +62,7 @@ case $arch in sparc) elftoaout -o $tftpimage $tftpimage.tmp case $tftpimage in - *sun4u*) piggyback=piggyback64 ;; + *sparc64*) piggyback=piggyback64 ;; *) piggyback=piggyback ;; esac # Piggyback appends the ramdisk to the a.out image in-place And grab http://people.debian.org/~jbailey/config.tgz - I've changed almost everything in the sparc section. Particularily: I'm generating separate tftpboot images for sparc32 and sparc64 using tftpboot.sh until tilo works properly again. I've started generating the miniiso bits that ths says are The Way Of The Future. The generated image in dest/sparc64/netboot actually will run as well as anything else has so far. If you do a: boot net init=/bin/sh You can walk around the filesystem and see that it's all there, run things, etc. I'll be away from my Sparc all weekend, so hopefully this will help other people. I'd like to commit what I have for the config/ tree, but I want a couple more people to look at it first. For those who want to play along, my nightly snapshot for Sparc will include this patch. Tks, Jeff Bailey On Fri, Feb 13, 2004 at 09:01:15PM +0100, Thomas Poindessous wrote: Hi, about the problem with the bus error, I think it's coming from the file unifont.bgf it's the only file which is different between the two initrd. I did that : mount -o loop initrd-netboot /mnt cp -a /mmt/ /tmp/new/ cp unifont-cdrom.bgf /tmp/new genromfs -f initrd.netboot -d /tmp/new/ and this initrd works ! I will try to find why, but since I must leave for 3h, I thought you would be interessed. -- Thomas Poindessous -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] small patch to fix cdrom build for sparc
On Fri, Feb 13, 2004 at 02:24:32AM +0100, Thomas Poindessous wrote: Hi, this patch is needed to bix cdrom building for sparc. It's quite ugly, so if someone has a better idea ... tilo needs uncompressed kernel image and vmlinuz* are gzipped. I want to to wait to see what BenC's comments on this are. I'm cc:'ing #231484, where I filed a tentative patch to tilo. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#227852: kbd-chooser: [PATCH] the last one, I hope
On Fri, Feb 13, 2004 at 02:21:14AM +0100, Thomas Poindessous wrote: today, I tried netboot install for sparc, and I found a last bug in kbd-chooser. The word sparc in the debconf template must be changed to sun to match previous change. Could somebody applied the two last patchs ? One of them was already done. Please don't keep overloading a single bug with multiple patches. Some of them are likely to get lost. I think I've got all of them in CVS now. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sparc : some problems and netboot image available
On Thu, 2004-02-12 at 20:47, Thomas Poindessous wrote:
today I tried netboot install for sparc64. It did worked, but with several
problems:
It looks like you're matching most of what I'm seeing too, with the bus
errors and tilo failures.
I got it to work by using piggyback64 directly, which is what
tftpboot.sh seems to do.
- now something really weird : I did a make build_cdrom with
pkg-lists/cdrom/{common,sparc} from pkg-lists/netboot/. Then I did a
tftpboot image with tftpboot.sh script. It worked ... something is
really wrong in build_netboot method.
No bus errors? Weird.
- no fdisk : I will do another image tomorrow with fdisk-udeb
pkglists/netboot/{mips,mipsel,hppa} all have fdisk-udeb explicitely
mentioned in there, saying anna doesn't pull it in for some reason.
Anyone know if that was fixed in today's upload of anna?
- no dns resolving : I can't install from anything else than my
apt-proxy with numerical ip address. I tried to do a wget
ftp://ftp.debian.org/ and I got an error about dns resolution. My dns
server works fine and /etc/resolv.conf is correct. Maybe it's about
the line in config/i386/cdrom.cfg :
EXTRALIBS = /lib/libnss_dns* /lib/libresolv*
I've been meaning to take a look at that, since libc-udeb should have
those files in it anyway.
Tks,
Jeff Bailey
--
I never know what to expect when you respond to my postings. No insult
intended, you are merely a surprise :)
- Carlos O'Donnell
signature.asc
Description: This is a digitally signed message part
Re: PC Card Ethernet After Reboot
On Tue, 2004-02-10 at 08:23, Joshua Moore wrote: I just used the d-i daily build from 8 FEB (Netinst) on my Gateway Solo 5100 (a laptop). Everything seemed to go extremely well, except for one thing. It recognized my 3COM 589D Ethernet Card (PC Card, using 3c589_cs) during the initial install, but after reboot when you configure apt sources, it is unable to make any connections. It appears that the card services have not been started because the modem light is off after reboot. If I skip the apt configuration, and type insmod 3c589_cs at the prompt, I get an error. Has anyone had this problem? Anyone know how to get around it during the install? I saw that on the laptops that I did. The installer was far better at detecting things than whatever tools does it on reboot. When I mentioned it on IRC, it seems it was a known issue. I just had to poke around and insmod all the right pieces in the right order and it went. Consider using 'modprobe' instead, which often takes care of that for you. Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: Allowing for different kernel revisions
On Tue, Feb 10, 2004 at 12:13:08PM -0500, Joey Hess wrote: I'd like to split this up into common-2.2, common-2.4, common-2.6 so that various module renames can be handled sanely. I have been trying to think of a way that wouldn't be specific to 2.4/2.6, since module renames happen in the 2.4.xx series too. One idea I had was to list the versions in the module list file: foo.o [2.4.24] foobar.o [2.4.25] But this could get complicated if more than one kernel version included a module. They could be done as ranges: foo.o [2.4.0-2.4.24] foobar.o [2.4.25+] Something that's the same from the beginning on could be: bar.o [2.2.0+] And also cross version ranges: baz.o [2.2.0-2.5.999] Someone would just have to go through occasionally and reap versions that noone cares about. These approaches could maybe be reasonably combined. Having separate directories, plus ranges within them. It would mean that we could keep decent historical information (like debian-cd still has potato and other things) without having to worry about cruft building up in the current sandbox. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Allowing for different kernel revisions
In linux-kernel-di/modules/common, everything is done with the assumption of a 2.4 kernel. I'd like to split this up into common-2.2, common-2.4, common-2.6 so that various module renames can be handled sanely. This does mean that new module lists will need to be added in 3 places. Thoughts? Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: conditional for pkg-list, sparc needs two cdrom-initrd
On Sun, 2004-02-08 at 11:57, Blars Blarson wrote: For sparc, I've found I need to build two separate cd-initrd.gz's: one for sun4cdm (sparc32) and another for sun4u (sparc64). Why do you need to do this? All the userspace stuff should be the same - Only the kernel modules would be different. What problem are you seeing? (sparc32 machines may not be able to build sparc64 initrd, but sparc64 can build sparc32.) gcc -m64 should work from a sparc32 machine. In fact, we need to always assume that we're building from sparc32. That's the jail that the autobuilder sits in/ Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: upgading sparc d-i bugs to release-critical
On Sat, 2004-02-07 at 18:13, Blars Blarson wrote: The first six bugs in the list below are the ones I am talking about. All have patches in the BTS and have been sitting unfixed for a couple of weeks. Unless someone convinces me otherwise, I'll upgrade them to grave in two days. This doesn't make any sense. The bugs need to be fixed by those of us who care about Sparc, not pushed onto the rest of the team who probably can't even test them. Additional fixes are needed for d-i and debian-cd, but I'm not quite ready to submit patches on them yet. (One change I'll discuss in another message.) 227291mklibs important mklibs: needs to handle symbols starting with . for sparc Done this already, closed it. Thanks. 227852kbd-chooser kbd-chooser: [PATCH] wrong name for sparc/sun keyboard Looks straightforward enough. I've commited this and tagged it as pending. 227853debian-installer debian-installer: [PATCH] small fix for sparc, installs discover-udeb This appears to be waiting for more info on whether discover fails gracefully on Sparc's without a PCI bus. (I can try dragging one out to test next week) 228399base-installer base-installer: [PATCH] kernel package name for sparc are wrong Appears to be done and closed. 228518partitioner partitioner: [PATCH] sparc.sh for sparc system I don't know enough about this one to guess if it's the right thing or not. 228519debian-installer [PATCH] tftpboot.sh for sparc Appears to be done and closed. -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: FWD: debian-installer help w/ sparc
On Thu, Feb 05, 2004 at 06:46:10PM -0500, Joey Hess wrote: while nobody here at freegeek is really sparc-savvy, we've got a few sparc machines floating around that we'd be happy to try out debian-installer on. especially if someone knows OpenBoot- we've had trouble figuring out exactly how to get them to boot... Luvly! The linux-kernel-di stuff is almost done - I have to test thm's build patch to get the kernels named right. I've updated the image directories this afternoon for the new udebs. Hopefully there'll be Sparc images to test by late next week. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: something for pci.lst
On Mon, Jan 26, 2004 at 09:22:24PM +0100, Gaudenz Steinlin wrote: Beside this (which technically has nothing to do with kernel 2.6) there is nothing I know of which is better suited for 2.6 in discover2 as in discover1. By it's very design either discover1 nor discover2 should depend on the kernel version. Only the discover-data packages could depend on the kernel version. One solution for this problem in discover1 would be to have a discover-data-2.6 package. This package should be able to coexist with discover-data-2.4 so as to support those who dual boot between the two. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Nightly ia64 netboot images
I looked at your updated http://www.debian.org/devel/debian-installer/ports-status, and was surprised to see that there is a beta2 netboot for ia64, but not a nightly. I've corrected this now. Please update the page to show: http://people.debian.org/~jbailey/ia64/ as the source for those. I haven't attempted to install them (I'm not well setup for netboot here), so I can't say whether they should be Building or Working (anyone have a sec to try it?) Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems building d-i on sparc: mklibs failed
On Wed, 2004-01-14 at 08:59, Joerg Friedrich wrote: I generally do a sparc32 /bin/bash do make sure everything is detected right. when using sparc32 /bin/bash before a make TYPE=cdrom image make fails like this: 8 (snip) mkdir -p ./tmp/cdrom/tree/lib/modules/2.4.21-sparc32/kernel; if [ -e ./tmp/cdrom/tree/boot/System.map ]; then depmod -F ./tmp/cdrom/tree/boot/System.map -q -a -b ./tmp/cdrom/tree/ 2.4.21-sparc32; rm -f ./tmp/cdrom/tree/boot/System.map; else depmod -q -a -b ./tmp/cdrom/tree/ 2.4.21-sparc32; fi ; mkdir -p ./tmp/cdrom/tree/lib/modules/2.4.21-sparc64/kernel; if [ -e ./tmp/cdrom/tree/boot/System.map ]; then depmod -F ./tmp/cdrom/tree/boot/System.map -q -a -b ./tmp/cdrom/tree/ 2.4.21-sparc64; rm -f ./tmp/cdrom/tree/boot/System.map; else depmod -q -a -b ./tmp/cdrom/tree/ 2.4.21-sparc64; fi ; depmod: ELF file ./tmp/cdrom/tree//lib/modules/2.4.21-sparc64/kernel/drivers/cdrom/cdrom.o not for this architecture depmod: ELF file ./tmp/cdrom/tree//lib/modules/2.4.21-sparc64/kernel/drivers/ide/ide-cd.o not for this architecture depmod: ELF file ./tmp/cdrom/tree//lib/modules/2.4.21-sparc64/kernel/drivers/scsi/sr_mod.o not for this architecture depmod: ELF file ./tmp/cdrom/tree//lib/modules/2.4.21-sparc64/kernel/drivers/scsi/st.o not for this architecture Yup - it's because Sparc is multiarch. I'm working with BenC to get the Sparc kernels done such that they include the System.map for us. Then we need to point depmod to the right System.map for each architecture. (Recall that sun4u needs 64 bit kernels and sun4m cannot have them). See bug 227644 - I'm hoping today to get the pieces into linux-kernel-d-i for Sparc. Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: beta 2 and beyond
On Thu, 2004-01-15 at 20:23, David Nusinow wrote: And for discover1, there is a patch that apparently works to allow discover1 to work with 2.6. I've been using the modprobe -n solution proposed in #223682 for a couple weeks now and it's been working well. Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Re: Problems building d-i on sparc: mklibs failed
On Wed, 2004-01-14 at 07:45, Joerg Friedrich wrote: this solved the problem. it seems that mklibs doesn't work right with 32-bit and 64-bit libraries. does anyone have an idea? Btw: I can now build d-i on sparc, but how can I make a cdimage for testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz You shouldn't need to do this - Sparc is generally expected to be in 32 bit mode when you're compiling. Other packages in Debian don't do anything to check for this. I generally do a sparc32 /bin/bash do make sure everything is detected right. Tks, Jeff Bailey -- I never know what to expect when you respond to my postings. No insult intended, you are merely a surprise :) - Carlos O'Donnell signature.asc Description: This is a digitally signed message part
Progeny picax: Replacement for debian-cd
It's been brought to my attention that there's some dissatisfaction with debian-cd within Debian, that some reengineering may need to happen, and that such reengineering may not be able to happen soon. Given that, I thought it would be good to alert Debian to the presence of an alternative. Progeny has had some struggles with debian-cd also. When we started work on Anaconda for Debian, we decided against using debian-cd for it, and begun work on an alternative. The result is called picax (for Progeny Install Creator and Archive eXtractor; if you think the name is horrid, you didn't hear some of the other suggestions). We've been using it to make our Anaconda CDs, and it's worked well for us so far. Picax is written in Python. At its most basic level, it splits apt repositories into parts, either by number of parts or maximum part size. It can write installers to the parts via a modular extension mechanism; the mechanism works to the extent that we have placed all anaconda-specific logic in anaconda and kept it out of picax. It can create source media four ways: separate (completely separate source and binary parts, just like debian-cd), immediate (the last binary media is also the first source media), mixed (each of the media contains all the source for each binary on it), or none. Package ordering is handled via order files, debootstrap, and/or asking the installer for important packages; it is also apt-aware. As far as I can tell, it should be architecture-independent, and even cross-architecture, although this has not been tested. Picax is still very new, and I expect that there will be problems should Debian decide to switch to it. But I expect these problems should be easy to solve. In particular, I've created aptable media for three different Debian-based distributions, and working Anaconda install media for two of those, including sarge. To make picax useful for Debian, a debian-installer module would need to be written. Writing an installer module for picax shouldn't be too difficult; it amounts to a Python module with a particular API, which picax calls at the appropriate times. You can see a working example in anaconda; see http://platform.progeny.com/anaconda for details. I haven't uploaded it yet because it lacked the source features until very recently, but I will be uploading it very soon now that those are done and tested. In the meantime, you can get picax from Progeny's Subversion server: svn checkout svn://svn.progeny.com/anaconda/picax/trunk The package architecture is mature, so you should be able to build packages from the above in the usual way. In none of this do I wish to impugn the good name of Raphael Hertzog or of his creation, which has served Debian well thus far. Nor do I wish to impose my preferred solution upon Debian. It may be that fixing debian-cd is the best course of action for Debian to take. But I think picax could be a very useful replacement, and I wanted to ensure it was considered. Whatever Debian decides, picax fills an important niche at Progeny, and will continue to be useful there. Picax development is discussed on the [EMAIL PROTECTED] list (see platform.progeny.com for more details), so please CC followup discussion there, at least. Suggestions and concerns are welcome. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#225344: base-config: depends on aptitude
Package: base-config Version: 2.03 Severity: normal Hi, Why does base-config depend on aptitude? I think that suggests is more appropriate. $ apt_show base-config | grep -i -E '(version|depends):' Version: 2.03 Depends: debconf (= 1.3.22), apt, adduser, console-data (= 2002.12.04dbs-16), console-tools, passwd (= 2902-6), bsdutils (= 1:2.11l), aptitude Thanks, -- Jeff Sheinberg -- System Information: Debian Release: testing/sarge Architecture: i386 Kernel: Linux l1.bsrd.net 2.4.22-3 #1 Sun Dec 14 11:21:20 EST 2003 i586 Locale: LANG=C, LC_CTYPE=C Versions of packages base-config depends on: ii adduser 3.51 Add and remove users and groups ii apt 0.5.14 Advanced front-end for dpkg ii aptitude0.2.13-2 curses-based apt frontend ii bsdutils1:2.12-3 Basic utilities from 4.4BSD-Lite ii console-data2002.12.04dbs-26 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-44Linux console and font utilities ii debconf 1.3.22 Debian configuration management sy ii passwd 1:4.0.3-12 Change and administer password and -- debconf information: base-config/menu/mta: tzconfig/select_zone: tzconfig/verify_choices: true * base-config/intro: * apt-setup/security-updates: true * base-config/run-tasksel: false * apt-setup/another: false mirror/distribution: stable base-config/title: base-config/menu/finish: * base-config/stop-ppp: false * apt-setup/mirror: ftp.us.debian.org base-config/start-display-manager: true base-config/menu/apt-setup: base-config/menu/keyboard: tzconfig/title: apt-setup/directory: /debian/ * base-config/install-problem: true tzconfig/change_timezone: false base-config/pkgsel: base-config/menu/hostname: apt-setup/cd/another: false * apt-setup/non-free: true apt-setup/badedit: * apt-setup/non-us: true apt-setup/baddir: base-config/menu/pkgsel: base-config/menu/apt-get: base-config/menu/timezone: base-config/menu/intro: base-config/menu/passwd: apt-setup/hostname: ftp.us.debian.org base-config/menu/pon: base-config/login: * tzconfig/gmt: true apt-setup/title: mirror/http/proxy: * apt-setup/contrib: true apt-setup/non-us-failed: base-config/main-menu: * tzconfig/geographic_area: US * base-config/run-dselect: false apt-setup/cd/dev: /dev/cdrom * apt-setup/country: United States debian-installer/keymap: * base-config/remove-pcmcia: true apt-setup/badsource: * base-config/use-ppp: false * apt-setup/uri_type: edit sources list by hand base-config/get-hostname: apt-setup/not-mirror: base-config/retry-ppp: true * base-config/login-with-tty: apt-setup/security-updates-failed: base-config/menu/shell: base-config/pkgsel-short: done * apt-setup/cd/bad: base-config/invalid-hostname: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#222791: INSTALL REPORT - problems
of running dselect after tasksel. I use tasksel to select packages in broad strokes and then use dselect to chop out stuff I don't need. After running tasksel though, it wanted to install everything straight away. Anyway, after quitting the apt-get for tasksel, setting the hostname and manually apt-get'ing everything I wanted, the system has been fine. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#212101: kernel CONFIG_TR interferes with busybox CONFIG_TR
On Tue, Sep 30, 2003 at 01:38:26PM -0500, Steve Langasek wrote: Discussing with Jeff Bailey on IRC today indicates that a solution is forthcoming on this bug: he estimates that in a week, there will be new glibc packages in the archive that don't depend on the upstream kernel headers for what they expose to userspace. Is this an acceptable timeline to d-i folks for having headers that can be used for building busybox on ia64 and alpha (estimate 3 weeks to testing), or does anyone want to consider kludging the busybox sources to work around this namespace pollution problem? If I didn't say that they were going in experimental, sorry for not being clearer. Certainly the glibc team agreed that the right thing was to do this. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
I recently installed Debian from the LordSutch.com ISOLINUX mini-iso. When I got to the step where you try to boot from the hard drive, it did not work. I can boot from the boot floppy created during installation. But when I try to boot from the hard drive I get a text screen that says: MBR 01 01 01 01 01 01... repeating forever until I reset. When I boot from floppy, I can access everything. Network works fine, installation continued to download needed application files etc. So here is my setup and conditions: I have two hard drives, Maxtor 4GB each. Windows 98 on the master (hda) Linux on the slave (hdb) On hdb are seven partitions. The first is bootable hdb1. It is only 8MB. The second is the \. Third through sixth are \usr, \home, \var \tmp. Last is SWAP. The installation program detected another bootable operating system , asked if I wanted to include it as a boot option. I answered 'yes'. Installation said I am setting up to boot from a drive that is not the master which is not supported by some BIOS. I said do it anyway. And then I rebooted. The first time through it booted windows 98 like previous to installation. So I modified the BIOS to boot from the slave. The next boot gave the endless 01 01 01.. like I stated above. Booting from the floppy works great, but I don't want to do this forever. Please give me some advice and assistance. Jeff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please make discover2 udebs available for testing
On Tue, 2003-06-17 at 03:43, Petter Reinholdtsen wrote: [Jeff Licquia] Sure. Write all the code for me. :-) I'll see what I can do. But I suspect it will take me longer to find my way around the code then it will for you do to the work. Given the passage of time, I'm not sure you were right. :-) Seriously, I have been working on two things: - I have written a reduction script for discover 2 data, and have begun testing it. As far as I can tell, it works. But I haven't yet integrated the script into debian/rules so it's used to generate the udeb. OK. This sounds good for the next iteration. This integration work is now done. - I have been working on removing the curl dependency. I have code written that reads file: URIs directly instead of using curl, and I've written it to use zlib if possible. But I haven't tested compiling it yet. This too. No change at this time. Right now I am just desperate after getting a package that works. This means a way to get the required information out of discover, and I suspect the best way is to get the needed functionality into the --format argument. I never got any replies on this problem. Is it possible to get the name of the card out of discover using the --format argument? Using short lists, or dropping a library dependency do not help if the program itself is useless. And at the moment, with a busybox missing the paste tool, it do not work at all. I want the equivalent for this command line for discover1: /sbin/discover --format=%m\t%V %M\n This make it easy to handle the result using a shell script. I've been spending the last week reading discover source code and thinking of a solution for this. The problem with the command line you describe is that the data format has changed in a fundamental way, and there are now ways that a command line as you describe won't give you the data you want. In a narrow sense, that isn't going to be true now, but it could be. What we need to decide is if this is a problem or not, or whether there's a better solution. There are a lot of issues that need thinking through now, but as you have described it, we don't really have time right now for that. So, I'm going to meet you half way, and leave the deep thinking for later. I am in the middle of preparing new discover 2 packages (and discover-data as well) and placing them in the same place they were before. Again, these are very preliminary, so please don't distribute them as final 2.0.2. These should be ready tonight sometime. Inside the discover-udeb package, you will find a new utility, didiscover. (Think Debian Installer discover. Sorry if it's a bad name; as Branden will tell you, naming is not my strong suit.) This utility is nearly exactly the same as discover, but with one additional feature: you can now tell discover to output vendor and model information as part of the format string. So, to do the equivalent of this discover 1 command line: /sbin/discover --format=%m:%V %M\n ethernet you'll do this with didiscover: /usr/bin/didiscover --data-path=linux/module/name --data-vendor --data-model \ --format=%s:%s %s network Please give this a try and let me know if it works for you. (Backslash handling, such as \t, doesn't seem to be there in either discover or didiscover, but it should be fairly straightforward to add if necessary.) If the name is troubling to you, we can kill off the copy of discover in the udeb and make didiscover the discover there. There is also the bug in discover printing empty entries with a newline. No change here. If the above problem is sufficiently solved, this and the zlib integration can be next. If you have time and energy to assist with these two tasks, or any others you can identify, I'd appreciate it. Where can I fetch the current CVS version of discover2? This is another vexing problem; Progeny still does not have public anonymous CVS. It's my hope that this will be a reality sometime in the future. -- Jeff Licquia [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please make discover2 udebs available for testing
On Tue, 2003-06-24 at 01:49, Jeff Licquia wrote: I am in the middle of preparing new discover 2 packages (and discover-data as well) and placing them in the same place they were before. Again, these are very preliminary, so please don't distribute them as final 2.0.2. These should be ready tonight sometime. Done. I got tired last night and went to bed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please make discover2 udebs available for testing
On Mon, 2003-06-16 at 10:22, Petter Reinholdtsen wrote: [Jeff Licquia, 2003-06-02] Thanks for all the feedback, patches, and patience. I'm still learning my way around discover, and this is my first udeb. Today, I have an important project to deliver something for. Once that's done, I'll turn some attention to these issues. Is there anything we can do to assist you with this? Sure. Write all the code for me. :-) Seriously, I have been working on two things: - I have written a reduction script for discover 2 data, and have begun testing it. As far as I can tell, it works. But I haven't yet integrated the script into debian/rules so it's used to generate the udeb. - I have been working on removing the curl dependency. I have code written that reads file: URIs directly instead of using curl, and I've written it to use zlib if possible. But I haven't tested compiling it yet. If you have time and energy to assist with these two tasks, or any others you can identify, I'd appreciate it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please make discover2 udebs available for testing
On Sun, 2003-06-01 at 02:41, Petter Reinholdtsen wrote: [Jeff Licquia] I've stashed discover 2.0.2-0.0.0.2 and discover-data 2.2003.02.05-2 packages in http://hackers.progeny.com/~licquia/discover/. Again, please don't upload these or otherwise give them official status. I'm trying to test these now. I'll let you know about my progress. Thanks for all the feedback, patches, and patience. I'm still learning my way around discover, and this is my first udeb. Today, I have an important project to deliver something for. Once that's done, I'll turn some attention to these issues. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please make discover2 udebs available for testing
On Sat, 2003-05-24 at 02:43, Petter Reinholdtsen wrote: You went silent, so I guess I should make the task a bit easier. As a first try on discover-data-udeb, just include the whole data set without reduction (if it is hard to recuse the list, lets spend that time later). It will probably be too big for the 1.44 MiB floppies, but at least we should be able to test discover on the 2.88 MiB floppies. We need the support for 2.4 kernel module names to release the next test version of the installer system (and the debian CDs). It would be nice to get this out soon. Sorry for taking so long; some personal issues, combined with important work, delayed me. I've stashed discover 2.0.2-0.0.0.2 and discover-data 2.2003.02.05-2 packages in http://hackers.progeny.com/~licquia/discover/. Again, please don't upload these or otherwise give them official status. Changes: - Beginnings of removing the hard dependency on curl. All curl interaction has been isolated to one function, making it easy to replace that function under certain circumstances. (If anyone were to contribute an alternate _discover_load_url function, I wouldn't object.) - discover.conf is now installed into discover-udeb. - discover-data-udeb now has a complete copy of the discover 2 data. The two things I can think of that would be really nice: - An alternate _discover_load_url. - Reduction of the discover 2 data. What kinds of data would you want included or excluded? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
CD Image typo
On the CD Image I fetched from: http://gluck.debian.org/cdimage/testing/netinst/i386/ The initial screen says If you want to proceed with a safe 2.2.20 kernel or something like that, instead of noting that it's a recent 2.4 kernel. I'm not sure what package to file this minor bug against. Tks, Jeff Bailey -- Are you going to stay vegeterian? Are you going to start eating human flesh? (from http://www.moshez.org/vegeterian.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems reducing libraries in d-i
When I tried to build debian install from CVS make demo (or make
floppy_image) gets stuck in a loop trying to reduce libraries. The
attached log file shows the output.
JEff
--
/(bb|[^b]{2})/ that is the question.
GPG: http://www.globaldial.com/~jeffw/jeffw.gpg
dh_testroot
dpkg-checkbuilddeps
# This build cannot be restarted, because dpkg gets confused.
rm -rf ./tmp/net/tree
# Set up the basic files [u]dpkg needs.
mkdir -p ./tmp/net/tree/var/lib/dpkg/info
touch ./tmp/net/tree/var/lib/dpkg/status
# Create a tmp tree
mkdir -p ./tmp/net/tree/tmp
# Only dpkg needs this stuff, so it can be removed later.
mkdir -p ./tmp/net/tree/var/lib/dpkg/updates/
touch ./tmp/net/tree/var/lib/dpkg/available
# Unpack the udebs with dpkg. This command must run as root or fakeroot.
dpkg --force-overwrite --root=./tmp/net/tree --unpack udebs/*.udeb
Selecting previously deselected package anna.
(Reading database ... 0 files and directories currently installed.)
Unpacking anna (from udebs/anna.udeb) ...
Selecting previously deselected package busybox-udeb.
Unpacking busybox-udeb (from udebs/busybox-udeb.udeb) ...
Selecting previously deselected package cdebconf-udeb.
Unpacking cdebconf-udeb (from udebs/cdebconf-udeb.udeb) ...
Selecting previously deselected package choose-mirror.
Unpacking choose-mirror (from udebs/choose-mirror.udeb) ...
Selecting previously deselected package dash-udeb.
Unpacking dash-udeb (from udebs/dash-udeb.udeb) ...
Selecting previously deselected package di-utils-shell.
Unpacking di-utils-shell (from udebs/di-utils-shell.udeb) ...
Selecting previously deselected package ethdetect.
Unpacking ethdetect (from udebs/ethdetect.udeb) ...
Selecting previously deselected package isa-pnp-modules-2.4.19-386-udeb.
Unpacking isa-pnp-modules-2.4.19-386-udeb (from
.../isa-pnp-modules-2.4.19-386-udeb.udeb) ...
Selecting previously deselected package kernel-image-2.4.19-386-udeb.
Unpacking kernel-image-2.4.19-386-udeb (from .../kernel-image-2.4.19-386-udeb.udeb) ...
Selecting previously deselected package main-menu.
Unpacking main-menu (from udebs/main-menu.udeb) ...
Selecting previously deselected package modutils-basic.
Unpacking modutils-basic (from udebs/modutils-basic.udeb) ...
Selecting previously deselected package net-retriever.
Unpacking net-retriever (from udebs/net-retriever.udeb) ...
Selecting previously deselected package netcfg-dhcp.
Unpacking netcfg-dhcp (from udebs/netcfg-dhcp.udeb) ...
Selecting previously deselected package netcfg-static.
Unpacking netcfg-static (from udebs/netcfg-static.udeb) ...
Selecting previously deselected package nic-modules-2.4.19-386-udeb.
Unpacking nic-modules-2.4.19-386-udeb (from .../nic-modules-2.4.19-386-udeb.udeb) ...
Selecting previously deselected package nic-modules-shared-2.4.19-386-udeb.
Unpacking nic-modules-shared-2.4.19-386-udeb (from
.../nic-modules-shared-2.4.19-386-udeb.udeb) ...
Selecting previously deselected package pump-udeb.
Unpacking pump-udeb (from udebs/pump-udeb.udeb) ...
Selecting previously deselected package rootskel.
Unpacking rootskel (from udebs/rootskel.udeb) ...
Selecting previously deselected package socket-modules-2.4.19-386-udeb.
Unpacking socket-modules-2.4.19-386-udeb (from
.../socket-modules-2.4.19-386-udeb.udeb) ...
Selecting previously deselected package udpkg.
Unpacking udpkg (from udebs/udpkg.udeb) ...
# Clean up after dpkg.
rm -rf ./tmp/net/tree/var/lib/dpkg/updates
rm -f ./tmp/net/tree/var/lib/dpkg/available ./tmp/net/tree/var/lib/dpkg/*-old
./tmp/net/tree/var/lib/dpkg/lock
# Set up modules.dep, ensure there is at least one standard dir (kernel
# in this case), so depmod will use its prune list for archs with no
# modules.
mkdir -p ./tmp/net/tree/lib/modules/2.4.19-386/kernel
depmod -q -a -b ./tmp/net/tree/ 2.4.19-386
# These files depmod makes are used by hotplug, and we shouldn't
# need them, yet anyway.
find ./tmp/net/tree/lib/modules/ -name 'modules*' \
-not -name modules.dep | xargs rm -f
# Create a dev tree
mkdir -p ./tmp/net/tree/dev
# Move the kernel image out of the way, into a temp directory
# for use later. We don't need it bloating our image!
mv -f ./tmp/net/tree/boot/vmlinuz ./tmp/net/vmlinuz
rmdir ./tmp/net/tree/boot/
# Copy terminfo files for slang frontend
# TODO: terminfo.udeb?
for file in /etc/terminfo/a/ansi /etc/terminfo/l/linux \
/etc/terminfo/v/vt102; do \
mkdir -p ./tmp/net/tree/`dirname $file`; \
cp -a $file ./tmp/net/tree/$file; \
done
# Copy in any extra libs.
cp -a /lib/libnss_dns* /lib/libresolv* ./tmp/net/tree/lib/
# Library reduction.
mkdir -p ./tmp/net/tree/lib
mklibs -v -d ./tmp/net/tree/lib `find ./tmp/net/tree -type f -perm +0111 -o -name
'*.so'`
I: Using ld-linux.so.2 as dynamic linker.
I: library reduction pass 1
Objects: udpkg dpkg-reconfigure anna debconf-loadtemplate debconf debconf-copydb
ethdetect.postinst netcfg-static.postinst pump di-utils-shell.postinst dash
netcfg-dhcp.postinst choose-mirror net-retriever insmod main-menu busybox
Object: ./tmp/net
Re: Problems reducing libraries in d-i
Done.
The two libraries are:
Still need: di_list_free
Still need: di_pkg_free
Do you still want a copy of the log?
Jeff
Matt Kraai wrote:
On Sat, Jan 25, 2003 at 07:33:57PM +0800, Jeff Williams wrote:
When I tried to build debian install from CVS make demo (or make
floppy_image) gets stuck in a loop trying to reduce libraries. The
attached log file shows the output.
Would you please add -v -v to the mklibs command line? That
should make it print out the names of the symbols it cannot
resolve.
Matt
.
--
/(bb|[^b]{2})/ that is the question.
GPG: http://www.globaldial.com/~jeffw/jeffw.gpg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I build / initial test on powerpc
Detect hard drives also gave no feedback as to whether it
was successful or not, but the menu default was changed to
Yup. I guess there's a tradeoff between verbosity and irritation over
hitting enter a gazillion times... Not saying anything if it's all right
is very unixy but perhaps not proper in an installer.
After doing a few installs recently I'd say yes, please give some
feedback! One of the difficult things with boot floppies is not knowing
what has happened (e.g. which network cards have/haven't been detected).
Jeff
--
/(bb|[^b]{2})/ that is the question.
GPG: http://www.globaldial.com/~jeffw/jeffw.gpg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Processed: Reassign 175353
reassign 175353 mklibs,libstc++5-pic thanks This bug does not apply to libc6 - our _pic.map files are arch-dependant. Tks, Jeff Bailey On Thu, Jan 23, 2003 at 08:33:20AM -0600, Debian Bug Tracking System wrote: Processing commands for [EMAIL PROTECTED]: reassign 175353 mklibs,libc6-pic,libstdc++5-pic Bug#175353: general: *-pic packages violate FHS Bug reassigned from package `general' to `mklibs,libc6-pic,libstdc++5-pic'. 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BiDi and RTL
While admitting floppies are almost entirely worthless, I have 50 servers without CDs but with floppies all running Debian, I'd hate to have to rebuild them all. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I've just found an infinite loop in the Woody bf2.4 1.44MBinstall disks!
On Wed, 2002-05-01 at 14:01, Joey Hess wrote: Package: base-config Severity: grave Version: 1.33.17 J M Cerqueira Esteves wrote: debconf (developer): -- FSET base-config/use-ppp seen false debconf (developer): -- 10 base-config/use-ppp doesn't exist It looks like I accidentially built base-config with an experimental, broken version of debconf, which corrupted its templates file. One freaking last minute change cascading into another, sigh. I suppose a simple rebuild will fix it. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I didn't see this tread until today, but this weekend I was doing an install and had the same recursive loop on a standard pentium 166. I downloaded the floppy disks from the same place as the other guy: ftp://ftp.us.debian.org/ /debian/dists/woody/main/disks-i386/3.0.22-2002-04-03/images-1.44/bf2.4 -rw-rw-r-- 3 debian debian 1308 Apr 1 08:18 README.txt -rw-rw-r-- 1 debian debian1474560 Apr 1 08:17 driver-1.bin -rw-rw-r-- 1 debian debian1474560 Apr 1 08:17 driver-2.bin -rw-rw-r-- 1 debian debian1474560 Apr 1 08:17 driver-3.bin -rw-rw-r-- 1 debian debian1474560 Apr 1 08:17 driver-4.bin -rw-rw-r-- 3 debian debian 16895 Apr 1 08:18 kernel-config -rw-rw-r-- 1 debian debian1474560 Apr 1 08:17 rescue.bin -rw-rw-r-- 1 debian debian1474560 Apr 1 08:17 root.bin I'd try the incoming floppy images (where are they?) as suggested and inform back to you about it. But the images still seemed bad in Sunday as far as I can tell. I killed the install from the other shell and just finished the install by apt-get'ing the packages I needed so all was well in the end. Since you said: Well I can't do anything without a debug log. Set DEBCONF_DEBUG=. and reproduce it, log output. How does one go about setting that? Must I rebuild the installer or just sent it as an env var or pass in kernel command line? Jeff -- Jeff Carr [EMAIL PROTECTED] Northern Computers, Inc. V:414.769.5980 x4348 F:414.769.5989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: report for b-f 2002-02-17
Eduard Bloch writes: #include hallo.h Jeff Sheinberg wrote on Tue Feb 19, 2002 um 08:01:29PM: When? Which plattform? Sorry for the typo in the Subject:, that should be 2002-02-07 for arch i386. But which flavor? The default .../3.0.19-2002-02-07/images-1.44/rescue.bin, but does it in any way matter for the problems that I have reported? This has been fixed in 3.0.19, afaik. Please send the log if you can reproduce the problem with _this_ release. Here is an excerpt from the /var/log/installer.log file, Feb 19 14:51:05 (none) user.info dbootstrap[256]: Mounting ext2 partition /dev/hda9 on /target Feb 19 14:51:05 (none) user.debug dbootstrap[256]: running cmd 'mount -t ext2 /d ev/hda9 /target' Feb 19 14:51:20 (none) user.debug dbootstrap[256]: running cmd 'mount -t ext3 -r /dev/hda6 /instmnt' Did you create a journal on hda6 before? Of course I created a journal. Are you suggesting that the above log fragment doesn't exactly show what the problem is? sure that the problem that I reported (one cannot cancel the selected timezone, one can only affirm the selected timezone) definitely did occur. IIRC, this dialog happened after I rebooted. So it is SEP. I don't know what SEP means, but Joey Hess has kindly fixed this problem. Gruss/Regards, Eduard. -- We are the Borg. You will be assimilated. Resistance is futile. The Borg, Star Trek HTH, -- Jeff Sheinberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
report for b-f 2002-02-17
Hi, I was able to do a complete install (dselect using apt-get over a dialup ppp connection), however, there were a few problems. Also, I noticed that some prior problems had been fixed. Install method - download rescue root floppies along with drivers.tgz file to a local partition. Created local basedebs tarball using debootstrap. Booted from floppy disk. Outstanding problems, o The shadow boxes and scroll bars are still rendered incorrectly during the debootstrap step. After I then rebooted, this problem did not manifest anymore for those configuration screens that use these features. o I could not use the hard disk method to install the drivers nor to install the basedebs. This is probably because the partition containing these files is of type ext3, which is not supported by the 2.2.20 kernel, however, they should have been mounted as ext2, not as ext3. As I workaround, I used the mounted method to install the drivers and the basedebs, which was able to mount the ext3 partition as ext2. o The tzconfig screen does not have a cancel option, therefore, if one makes a mistake, one has to fix it after having rebooted. This is especially not nice for a newbie. Fixed problems, o The MBR is no longer over-written when installing lilo only to a partition boot record. o Lilo is correctly installed into an extended partition boot record (/dev/hda9), and was booted correctly from there by my boot selector program (grub). o Pppconfig is run before attempting to start ppp. Thanks, -- Jeff Sheinberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: report for b-f 2002-02-17
Eduard Bloch writes: #include hallo.h Jeff Sheinberg wrote on Tue Feb 19, 2002 um 04:38:46PM: Install method - download rescue root floppies along with drivers.tgz file to a local partition. Created local basedebs tarball using debootstrap. Booted from floppy disk. When? Which plattform? Sorry for the typo in the Subject:, that should be 2002-02-07 for arch i386. because the partition containing these files is of type ext3, which is not supported by the 2.2.20 kernel, however, they should have been mounted as ext2, not as ext3. This has been fixed in 3.0.19, afaik. Please send the log if you can reproduce the problem with _this_ release. Here is an excerpt from the /var/log/installer.log file, Feb 19 14:51:05 (none) user.info dbootstrap[256]: Mounting ext2 partition /dev/hda9 on /target Feb 19 14:51:05 (none) user.debug dbootstrap[256]: running cmd 'mount -t ext2 /d ev/hda9 /target' Feb 19 14:51:20 (none) user.debug dbootstrap[256]: running cmd 'mount -t ext3 -r /dev/hda6 /instmnt' Feb 19 14:51:20 (none) user.info dbootstrap[256]: mount: Mounting /dev/hda6 on / instmnt failed: No such device Feb 19 14:51:20 (none) user.err dbootstrap[256]: The partition was not mounted successfully. note the attempt to mount /dev/hda6 as type ext3. o The tzconfig screen does not have a cancel option, therefore, if one makes a mistake, one has to fix it after having rebooted. This is especially not nice for a newbie. He? Tzconfig is called from base-config on the reboot system. You can reconfigure just after base-config is done, or even from a second console. Thanks, but I don't need a workaround, I am reporting a bug that I consider to be disconcerting for a newbie. The timezone config program that I am referring to uses a full screen character oriented display, just like the rest of the Debian installer that is invoked when I boot the floppy diskette. I do not remember exactly the contents of this screen, but I am sure that the problem that I reported (one cannot cancel the selected timezone, one can only affirm the selected timezone) definitely did occur. IIRC, this dialog happened after I rebooted. Thanks, -- Jeff Sheinberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
user name
My system is Debian 2.1 slink, and on installation I was asked for, and gave, a password. Now, when I reboot and give back the password, I am denied entry. Anybody got an answer for me ? Replies to [EMAIL PROTECTED] thanks
Testing boot floppies 3.0.19-2001-12-30
Hi, I just did an install using drivers and basedebs located on a local hard disk partition, /dev/hda6 (ext3), to the new root (/) on /dev/hda9 (also ext3). There were no problems mounting /dev/hda9 as ext2, even though I had just created it as ext3. This is mandatory, since the supplied 2.2.20 kernel does not support ext3, however, I could not access the /dev/hda6 partition until I had first converted it back to ext2 (tune2fs -O ^has_journal /dev/hda6). I switched to the syslog VC to see what was happening here, and the problem was that the mount command executed was, mount -t ext3 /dev/hda6 /instmnt which can never succeed without the proper kernel support. I suggest that boot-floppies should try ext2 after ext3 fails, or just try only ext2 for kernels that do not support ext3. I also noticed two minor problems, 1. On the Debian blurb screen its seems that the end of blurb is truncated following the 2nd (page down) screen. 2. After rebooting, I choose do not run dselect, then the install seemed to hang. I then typed Enter, after which it became obvious that the apt install step had been started, however, its notification message/prompt was missing, thus causing the perceived hang. It seems that a few prior bugs were fixed, 1. pppconfig is now run before pon. 2. pcmcia-cs set to purge on my system which has no PCMCIA devices. 3. I was able to make a custom boot floppy without any problems (others had reported this as a problem to the debian-testing list). So, from my vantage point, the only remaining major issue is a cosmetic one - the shadow boxes around the text widgets are still screwed up. Thanks, -- Jeff Sheinberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing boot floppies 3.0.18
Joey Hess writes: Jeff Sheinberg wrote: o After rebooting, I am asked if I want to startup the ppp connection, however, the pppconfig program is _not_ run before pon is executed. A newbie user would be completely lost here, and under potato, pppconfig was run before pon was executed. The code is this: # Set up ppp if not already set up. if [ ! -e /etc/ppp/peers/provider ]; then pppconfig --noname /dev/tty /dev/tty || true fi Maybe the ppp package has changed so that there is a /etc/ppp/peers/provider by default; this would defeat base-config. Would someone like to run debootstrap or do a test install and check? Ok, here is why the above check is not working corrrectly, from the /var/lib/dpkg/info/ppp.postinst file, test -f /etc/ppp/peers/provider || \ install -g dip -m 640 /usr/share/doc/ppp/examples/provider.peer /etc/ppp/peers /provider so, we see that the ppp package installs a provider file at post-install time. What needs to be done is something like this, if [ ! -e /etc/ppp/peers/provider ] || cmp -s /etc/ppp/peers/provider /usr/share/doc/ppp/examples/provider.peer then pppconfig --noname /dev/tty /dev/tty || true fi Of course, if pppconfig is not installed as part of the base system or something, that could also explain it. Yes, pppconfig is installed, $ debootstrap --print-debs woody . | tr -s ' ' '\n' | grep pppcon pppconfig o I have no pcmcia devices. This was neither detected properly, nor was I queried about pcmcia, instead, there were various unsightly errors printed regarding pcmcia during the reboot. Like what? Basically, since I have neither pcmcia controller nor pcmcia devices on my workstation, the pcmcia package should have been deinstalled before rebooting, but this was not done, $ dpkg -l --root=/bf-test pcmcia-cs [..] ii pcmcia-cs 3.1.22-0.1potato PCMCIA Card Services for Linux. here is one such message, if you want to seem all of them, then just install pcmcia-cs on a workstation, Linux PCMCIA Card Servide 3.1.29 kernel build: 2.2.19 unknown option: [pci] [cardbus] [apm] Intel ISA/PCI/Cardbus PCI probe: no bridges found ds: no socket drives loaded -- see shy jo -- Jeff Sheinberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
