Unblock brltty?
Hi, The icu transition is ready to go, but currently stalled by brllty which is blocked because of its udeb. As I understand it, the udeb does not use icu so should be safe to unblock in that regard; could we do so please? Regards, Adam -- 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/1281776978.24840.4390.ca...@kaa.jungle.aubergine.my-net-space.net
Bug#592939: Installation Report with squeeze installer on K7 architecture
Package: installation-reports Boot method: CD Image version: Self-made boot CD with actual squeeze installer Date: 2010-08-14 Machine: Self-made Desktop PC Processor: AMD Duron 800MHz Memory: 256MB Partitions: df -Tl will do; the raw partition table is preferred Dateisystem Typ 1K‐Blöcke Benutzt Verfügbar Ben% Eingehängt auf /dev/sda1 ext4 1921156 565776 1257788 32% / tmpfs tmpfs 127676 0 127676 0% /lib/init/rw udev tmpfs 123340 128 123212 1% /dev tmpfs tmpfs 127676 0 127676 0% /dev/shm /dev/sda5 xfs 77443576 40973076 36470500 53% /storage1 /dev/sdb5 xfs 244076732 178833244 65243488 74% /storage2 Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 735 Host [1039:0735] (rev 01) Kernel driver in use: agpgart-sis 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) [1039:0001] 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) [1039:0018] 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller [1039:0016] 00:02.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 07) Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] Kernel driver in use: ohci_hcd 00:02.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 07) Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] Kernel driver in use: ohci_hcd 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev d0) Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller (A,B step) [1039:5513] Kernel driver in use: pata_sis 00:11.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) Subsystem: Compex FN22-3(A) LinxPRO Ethernet Adapter [11f6:8139] Kernel driver in use: 8139too 00:13.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 50) Subsystem: First International Computer, Inc. VA-502 Mainboard [0925:1234] Kernel driver in use: uhci_hcd 00:13.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 50) Subsystem: First International Computer, Inc. VA-502 Mainboard [0925:1234] Kernel driver in use: uhci_hcd 00:13.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 51) Subsystem: First International Computer, Inc. Device [0925:1234] Kernel driver in use: ehci_hcd 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Rage 128 RF/SG AGP [1002:5246] Subsystem: ATI Technologies Inc Magnum/Xpert 128/Xpert 99 [1002:0004] 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: [O] Install base system: [E] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install: [O] Comments/Problems: The used architecture is a K7 architecture (AMD Duron 800MHz). the used kernel-image has to be the -686 image. But there is the -486 image installed. Here, the output of /proc/cpuinfo: bernh...@cr-server:~$ more /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 3 model name : AMD Duron(tm) Processor stepping : 1 cpu MHz : 796.606 cache size : 64 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow bogomips : 1593.21 clflush size : 32 cache_alignment : 32 address sizes : 36 bits physical, 32 bits virtual power management: Regards Bernhard -- 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/4c66671c.6030...@online.de
Bug#591016: flash-kernel: /usr/share/initramfs-tools/hooks/flash_kernel_set_root mis-detects root filesystems for systems using ubifs
* John Holland john.holl...@cellent-fs.de [2010-08-11 19:46]: and my /etc/fstab / entry looks like: /dev/root / ubifs defaults,noatime,ro 0 0 Is this even valid gien that /dev/root doesn't exist? Shouldn't this either ubi0:rootfs or something like /dev/ubi.. -- Martin Michlmayr http://www.cyrius.com/ -- 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/20100814110548.gx16...@jirafa.cyrius.com
Bug#592924: os-prober MINIX detection
Feiran Zheng wrote: The MINIX detection criterial is fairly old, no recent MINIX installation can be detected correctly. As we are developing some new boot features of MINIX (Multiboot compliant for example), we are also trying to make configuring GRUB easier, as a result the detection of os-prober is patched. The patch is as below: Index: packages/os-prober/os-probes/mounted/x86/80minix === --- packages/os-prober/os-probes/mounted/x86/80minix (revision 64312) +++ packages/os-prober/os-probes/mounted/x86/80minix (working copy) @@ -7,11 +7,20 @@ dir=$2 type=$3 -if [ $type = minix ] [ -f $dir/minix ]; then - # XXX will chain loading work? -label=$(count_next_label Minix) - result $partition:Minix:$label:chain - exit 0 +if [ $type = minix ] || [ $type = ext2 ] ; then + if [ -e $dir/boot/image_big ]; then + if [ -e $dir/boot/image_latest ]; then Thanks for the patch. Wouldn't it make sense to retain the check for the /minix file, in order to still be able to detect historical minix installations? (Also, /boot/image_big and /boot/image_latest are awefully generic names to go by..) + boot=minix + else + boot=chain Note that grub-installer would also need to be patched to generate the right grub configs to boot minix in the case where the existing chain loader configs are not used. I guess this would look much like the handling of booting linux does, if I understand what you mean by Multiboot compliant. -- see shy jo signature.asc Description: Digital signature
Processed: reassign 592939 to base-installer, retitle 592939 to wrong kernel chosen for AMD Duron K7
Processing commands for cont...@bugs.debian.org: reassign 592939 base-installer Bug #592939 [installation-reports] Installation Report with squeeze installer on K7 architecture Bug reassigned from package 'installation-reports' to 'base-installer'. retitle 592939 wrong kernel chosen for AMD Duron K7 Bug #592939 [base-installer] Installation Report with squeeze installer on K7 architecture Changed Bug title to 'wrong kernel chosen for AMD Duron K7' from 'Installation Report with squeeze installer on K7 architecture' thanks Stopping processing here. Please contact me if you need assistance. -- 592939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.12818023448697.transcr...@bugs.debian.org
Re: New LILO upstream development
]] Bjørn Mork | Joachim Wiedorn ad_deb...@joonet.de writes: | | After the long silence about the popular bootloader LILO the development | was started again. | | The new Homepage can be found here: | http://lilo.alioth.debian.org/ | | For the development of the bootloader I have started an Alioth project | with Git repository and Mailinglist: | http://alioth.debian.org/projects/lilo/ | | Nice. And thus I learned about bug #573736 Thanks for bringing this to our attention. | $ git clone https://alioth.debian.org/anonscm/git/lilo/lilo.git | Initialized empty Git repository in /usr/local/src/git/lilo/.git/ | error: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt while accessing https://alioth.debian.org/anonscm/git/lilo/lilo.git/info/refs | | fatal: HTTP request failed | | Maybe someone could fix the certificate chain sorting on alioth? I've fixed it now, sorry for the long delay. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- 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/87sk2h9gww@qurzaw.linpro.no
Bug#591016: flash-kernel: /usr/share/initramfs-tools/hooks/flash_kernel_set_root mis-detects root filesystems for systems using ubifs
On Sat, 2010-08-14 at 12:05 +0100, Martin Michlmayr wrote: * John Holland john.holl...@cellent-fs.de [2010-08-11 19:46]: and my /etc/fstab / entry looks like: /dev/root / ubifs defaults,noatime,ro 0 0 Is this even valid gien that /dev/root doesn't exist? Shouldn't this either ubi0:rootfs or something like /dev/ubi.. Thanks for pointing that out. I've changed my fstab to ubi0:rootfs to reflect that of the kernel args. Now the fstab entry looks like: ubi0:rootfs / ubifs defaults,noatime,ro 0 0 This results in no change in behavior for either update-initramfs or the numbers of / entries in /proc/mounts. John ___ Cellent Finance Solutions AG Firmensitz: Calwer Straße 33, 70173 Stuttgart Registergericht: Amtsgericht Stuttgart, HRB 720743 Vorstand: Thomas Wild Vorsitzender des Aufsichtsrats: Rudolf Zipf -- 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/1281818703.16066.10.ca...@oklahoma
Processed: limit source to tasksel, tagging 592950, tagging 592180
Processing commands for cont...@bugs.debian.org: #tasksel (2.83) UNRELEASED; urgency=low # # * Spanish updated. Closes: #592180 # * Arabic updated. Closes: #592950 # limit source tasksel Limiting to bugs with field 'source' containing at least one of 'tasksel' Limit currently set to 'source':'tasksel' tags 592950 + pending Bug #592950 [tasksel] tasksel: [INTL:ar] Update Arabic translation Added tag(s) pending. tags 592180 + pending Bug #592180 [tasksel] tasksel: Updated Spanish PO translation of tasks Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 592180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592180 592950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.128182819531496.transcr...@bugs.debian.org
Bug#593005: Logical Volume Managet not available
Package: installation-reports Version: squeeze (i386) I have an AMD DURON 1600 CPU whith an USRock motherboard. Installing Lenny works ok, but installing Squeeze it says: [!] Partition disks Logical Volume Manager not available. The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. Regards, Héctor. -- 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/983829.96842...@web51801.mail.re2.yahoo.com
