Bug#870092: Acknowledgement (fvwm1 no menu on mouse 2)
Hi, I've forgotten to add that on both systems the xorg-legacy package is installed and the xserver gets started via startx as non-root. Starting the X server as root does not change a thing. CU, Uli
Bug#870092: fvwm1 no menu on mouse 2
Package: fvwm1 Version: 1.24r-56+b1 Severity: important After the dist-upgrade from jessie to stretch, the fvwm1 menu on mouse 2 disapeared. The middle mouse button (which referes to mouse 2) does work for xterm (cut & paste) or firefox, though. Just that no menu comes up from the root window. The other menus on mouse 1 and 3 are working fine. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fvwm1 depends on: ii libc6 2.24-11+deb9u1 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxpm4 1:3.5.12-1 ii m41.4.18-1 fvwm1 recommends no packages. Versions of packages fvwm1 suggests: pn fvwm-icons | fvwm-common pn librplay3 pn menu ii xfonts-100dpi 1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 -- no debconf information
Bug#855461: esniper: ensiper 2.31.0 fails to login on ebay
Package: esniper Version: 2.31.0-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, while using esniper 2.31.0 to try to bid on an auction, it fails to login on ebay (yes, with correct user/password settings). Therefore, bidding is impossible, which is the major feature of the program. Of course, when ebay changes things, this is bound to happen from time to time and it's already fixed in esniper 2.32.0 (which would be available in unstable). I therefore would propose to update to 2.32.0 in stable, too. Regards, Ulrich Teichert -- System Information: Debian Release: 8.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages esniper depends on: ii ca-certificates 20141019+deb8u2 ii libc62.19-18+deb8u7 ii libcurl3 7.38.0-4+deb8u5 esniper recommends no packages. esniper suggests no packages. -- no debconf information
Bug#797464: yaboot: Removing systemd breaks yaboot config, makes booting impossible
Package: yaboot Version: 1.3.16-4 Severity: important Dear Maintainer, after removing systemd and replacing it with sysvinit, booting was impossible. yaboot was starting up, but complained about a missing device and could not proceed with booting the kernel. It turns out that the yaboot config uses /dev/disk/by-id/* device names in the boot definition. Replacing it with /dev/sdb2 in my case worked. I'm currently booting with this yaboot.conf: boot=/dev/sdb2 device=/pci@8000/pci-bridge@d/pci-ata@1/@/@1 partition=3 root=UUID=9d2b9cda-5bea-4522-b2f6-3224c7b1bcfe timeout=100 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot macosx=/dev/sda10 image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old As you could see, I have a second disk (/dev/sdb) for Linux, leaving /dev/sda for MacOs untouched. I have no idea if this bug should be better assigned to the debian-installer or systemd or a sysvinit-package or other, as the yaboot.conf file is generated not by yaboot itself. If both system booting styles should work in the future, perhaps even ransitional packages systemd = sysvinit, sysvinit = systemd could be an option, I don't know. All I know is that I'm very grateful that I had the option to remove systemd, even if I had to use a rescue CD to correct yaboot.conf. Regards, Ulrich Teichert -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 3.16.0-4-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages yaboot depends on: ii libc6 2.19-18 Versions of packages yaboot recommends: ii hfsutils 3.2.6-13 ii powerpc-utils 1.1.3-25 yaboot suggests no packages. -- no debconf information
Bug#733686: debian-installer-7.0-netboot-mips: Partitioning step fails during netboot install on SGI =?UTF-8?Q?O=RO
Hi, sorry for the delay, but my company was moving and real life was invading my privacy... Anyway, I repeated the installation process and the installer says: Installation step failed An installation step failed. You can try to run the failing item again from the menu, or skip it and choose something else. The failing step is: Partition a hard drive The log: Mar 31 19:13:26 main-menu[198]: DEBUG: resolver (fat-modules): package doesn't exist (ignored) Mar 31 19:13:27 main-menu[198]: INFO: Menu item 'partitioner' selected Mar 31 19:13:27 main-menu[198]: WARNING **: Unable to set title for fdisk-udeb. Mar 31 19:13:28 main-menu[198]: (process:2882): /var/lib/dpkg/info/partitioner.postinst: Mar 31 19:13:28 main-menu[198]: (process:2882): line 1: Mar 31 19:13:28 main-menu[198]: (process:2882): syntax error: unexpected ( Mar 31 19:13:28 main-menu[198]: WARNING **: Configuring 'partitioner' failed with error code 2 Mar 31 19:13:28 main-menu[198]: WARNING **: Menu item 'partitioner' failed. Mar 31 19:15:47 main-menu[198]: INFO: Modifying debconf priority limit from 'high' to 'medium' So, the offending file is /var/lib/dpkg/info/partitioner.postinst, which looks like a binary, not like a shell script. After deleting this file, installation went just fine, minus some debris on the screen, HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: ulrich.teich...@gmx.de | Listening to: Stormweg 24 |Pale Bride (The Von Bondies), Slip Away (Sedatives) 24539 Neumuenster, Germany|Sacred Decay (The Estranged), She's Lost Control -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733686: debian-installer-7.0-netboot-mips: Partitioning step fails during netboot install on SGI O�
Package: debian-installer-7.0-netboot-mips Severity: important Tags: d-i patch Dear Maintainer, During an new installation of wheezy on an SGI O2 the partitioning step failed. I was using the netboot image from /debian/dists/wheezy/main/installer-mips/ current/images/r5k-ip32, dating from 14th of December 2013. Over the UI, the only info was that the partioning step failed. After looking at the installer logs with a shell during install, it looked like the postinstall script of the partitioner was bogus. In the log, the error message was a parsing error from a misplaced brace. The contents of the file (the partitoner postinstall script) were looking like a binary, not like a shell script. I simply deleted the file and the partitioning went OK, as the rest of the installtion as well. -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: mips (mips64) Kernel: Linux 3.2.0-4-r5k-ip32 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406419: [powerpc, CHRP] 2.6 kernel does not boot on IBM RS/6000 43p 150
(established 65536 bind 65536) [ 209.380875] TCP reno registered [ 209.419148] NET: Registered protocol family 1 [ 209.471751] Trying to unpack rootfs image as initramfs... [ 210.541836] Freeing initrd memory: 4993k freed [ 210.597071] Thermal assist unit not available [ 210.653789] audit: initializing netlink socket (disabled) [ 210.718577] type=2000 audit(3754.070:1): initialized [ 210.779337] VFS: Disk quotas dquot_6.5.2 [ 210.826394] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 210.904877] msgmni has been set to 1002 [ 210.953462] alg: No test for stdrng (krng) [ 211.002953] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 211.091502] io scheduler noop registered [ 211.138365] io scheduler anticipatory registered [ 211.193499] io scheduler deadline registered [ 211.244520] io scheduler cfq registered (default) [ 211.305113] Using unsupported 1280x1024 display at f9e6, depth=8, pitch=1 -snip To me, it seems that only the console handover fails. As you could see, I once tried the kernel name tty0 and the system name udbg0, but both failed. Should I try another naming scheme? Or is the problem that the kernel thinks the *whole* boot line is the kernel command line? Anyway, I think there's definitely progress being made here and only the last step is missing. What's your suggestion for the next try? CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: ulrich.teich...@gmx.de | Listening to: Stormweg 24 |Pale Bride (The Von Bondies), Slip Away (Sedatives) 24539 Neumuenster, Germany|Sacred Decay (The Estranged), She's Lost Control -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531472: sendmail: makemap segfaults on MIPS
(`confBAD_RCPT_THROTTLE',`3')dnl FEATURE(`conncontrol', `nodelay', `terminate')dnl FEATURE(`ratecontrol', `nodelay', `terminate')dnl include(`/etc/mail/m4/dialup.m4')dnl include(`/etc/mail/m4/provider.m4')dnl LOCAL_CONFIG EXPOSED_USER(root uucp)dnl # users exempt from masquerading LOCAL_USER(root)dnl MASQUERADE_AS(`tolsyt.nms.ulrich-teichert.org')dnl FEATURE(`allmasquerade')dnl FEATURE(`masquerade_envelope')dnl FEATURE(`nullclient', smtp.versatel.de)dnl LOCAL_CONFIG submit.mc... divert(-1)dnl divert(0)dnl define(`_USE_ETC_MAIL_')dnl include(`/usr/share/sendmail/cf/m4/cf.m4')dnl VERSIONID(`$Id: submit.mc, v 8.13.8-3 2006-12-08 20:21:10 cowboy Exp $') OSTYPE(`debian')dnl DOMAIN(`debian-msp')dnl FEATURE(`msp', `[127.0.0.1]', `MSA')dnl -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing') Architecture: mips (mips64) Kernel: Linux 2.6.29-2-r5k-ip32 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages sendmail depends on: ii sendmail-base 8.14.3-9 powerful, efficient, and scalable ii sendmail-bin 8.14.3-9 powerful, efficient, and scalable ii sendmail-cf 8.14.3-9 powerful, efficient, and scalable ii sensible-mda 8.14.3-9 Mail Delivery Agent wrapper sendmail recommends no packages. Versions of packages sendmail suggests: pn rmail none (no description available) pn sendmail-doc none (no description available) Versions of packages sensible-mda depends on: ii libc6 2.9-13 GNU C Library: Shared libraries ii procmail 3.22-16Versatile e-mail processor ii sendmail-bin [mail-transport- 8.14.3-9 powerful, efficient, and scalable Versions of packages rmail depends on: ii libc6 2.9-13 GNU C Library: Shared libraries ii libldap22.1.30.dfsg-13.5 OpenLDAP libraries ii sendmail-bin [mail-tran 8.14.3-9 powerful, efficient, and scalable -- no debconf information -- Dipl. Inf. Ulrich Teichert|e-mail: ulrich.teich...@gmx.de | Listening to: Stormweg 24 |Pale Bride (The Von Bondies), Slip Away (Sedatives) 24539 Neumuenster, Germany|Sacred Decay (The Estranged), She's Lost Control -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406419: [powerpc, CHRP] 2.6 kernel does not boot on IBM RS/6000 43p 150
Hi Moritz, Does this error still occur with more recent kernel versions, e.g. with the Lenny d-i RC1? With the d-i RC1 it's even worse on the console: - client boot log--- 0 boot net:192.168.22.51,vmlinuz-chrp.initrd,192.168.22.58 BOOTP S = 1 FILE: vmlinuz-chrp.initrd Load Addr=0x4000 Max Size=0xbfc000 FINAL Packet Count = 13774 FINAL File Size = 7052236 bytes. zImage starting: loaded at 0x0040 (sp: 0x0121fea0) Allocating 0x431e28 bytes for kernel ... OF version = 'IBM,SPH00221' gunzipping (0x0140 - 0x00407000:0x005c14cf)...done 0x3db000 bytes Attached initrd image at 0x005c2000-0x00aa8b3d initrd head: 0x1f8b0808 Linux/PowerPC load: Finalizing device tree... using OF tree (promptr=00c1b320) OF stdout device is: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] command line: console=ttyS0,9600 console=tty0 memory layout at init: alloc_bottom : 01836000 alloc_top: 3000 alloc_top_hi : 4000 rmo_top : 3000 ram_top : 4000 Looking for displays found display : /[EMAIL PROTECTED]/[EMAIL PROTECTED], opening ... done instantiating rtas at 0x2ffb5000 ... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x01837000 - 0x01837f15 Device tree struct 0x01838000 - 0x0183d000 Calling quiesce ... returning from prom_init - client boot log--- That's it. The command line seem to be valid (ttyS0), but it's opening a display? Sounds strange to me. Unfortunately, I do not have a matching monitor available anymore, so I can't see if something is displayed there. I'll try the daily build next, If you like, CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] | Listening to: Stormweg 24 |Pale Bride (The Von Bondies), The Assault (Digital 24539 Neumuenster, Germany|Leather), Sacred Decay (The Estranged) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392764: Can't reproduce on PowerStack, MAC partition issue only?
Hi, I tried to reproduce this bug on my Motorola PowerStack II (PPC prep), but did not succeed. I've used the d-i daily build from 2007-01-19, netinst iso and booted the netinst kernel over TFTP (yes, I know this isn't supported, but my bandwith doesn't allow a full netinstall). During manual partitioning, I created two RAID partitions: [EMAIL PROTECTED]:~$ cat /proc/partitions major minor #blocks name 8 08891556 sda 8 1 16033 sda1 8 2 489982 sda2 8 34184932 sda3 8 44192965 sda4 9 04184832 md0 Which is a brain-dead setup with only one disk and a RAID1 on two partitions: [EMAIL PROTECTED]:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/md0 4.0G 390M 3.4G 11% / tmpfs 62M 0 62M 0% /lib/init/rw udev 10M 44K 10M 1% /dev tmpfs 62M 0 62M 0% /dev/shm I haven't seen any failure, which suggests that the problem only shows up on MAC partition types (the PowerStack uses PC-style partitions). Sorry, but it looks like I don't have the hardware to track this down, HTH anyway, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405579: PowerPC, prep-flavor: manual partitioning error
Hi, just finished testing the daily-build: cdimage/daily-builds/sid_d-i/20070110-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso And this bug is definitely squashed. I've deleted all partitions and was able to create different ones, installed on them and all was as it should be. AFAIK, we did not even introduce new bugs with the patch ;-) Partition layout after manual partitioning: [EMAIL PROTECTED]:~$ cat /proc/partitions major minor #blocks name 8 08891556 sda 8 1 16033 sda1 8 2 489982 sda2 8 38377897 sda3 [EMAIL PROTECTED]:~$ mount /dev/sda3 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) (guided installation would have had swap as sda3) This report can be closed, as far as I'm concerned, CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405579: PowerPC, prep-flavor: manual partitioning error
Hi, just a quick update: OK. I've checked with someone who knows C better than I and just uploaded a new version. I made the same change in another function too, though there it only affected an error message. The new version may be included in CD images built tonight, but you may have to allow a bit more time. I've downloaded the 20070109-2 build, and I think the sid_d-i one, but: mosna:/cdrom# find . -iname '*prep*' ./pool/main/l/linux-2.6/linux-image-2.6.18-3-prep_2.6.18-7_powerpc.deb ./pool/main/l/linux-latest-2.6/linux-image-2.6-prep_2.6.18+5_powerpc.deb ./pool/main/p/partman-prep ./pool/main/p/partman-prep/partman-prep_9_powerpc.udeb ./pool/main/p/prep-installer ./pool/main/p/prep-installer/prep-installer_0.4_powerpc.udeb There might be the chance that I stumbled into the wrong directory *again*, so I'll dowload the 20070109-3 build to verify. This will take another 6-8 hours, though... CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405579: PowerPC, prep-flavor: manual partitioning error
Hi, [del] Please just use the link for powerpc netinst under daily built images on http://www.debian.org/devel/debian-installer/. That page is by far the best way to get an image at _any_ time. That's one of the reasons I'm not doing it. I am sure that once I have downloaded the current image, it's not current any more. And when the http-link follows the current symlink on cdimage.d.o, the image will be changed behind my back during downloading it. The other reason is that I don't want to have a browser open for 6-8 hours with X and all. Yes, I could use wget, but would that be any better than ncftp? I doubt it. Also, ncftp is just much better at resuming ftp downloads than any browser and that's *quite* helpful in my situation. Browsing through the cdimages server manually will only lead you astray... If I'm not careful enough, I don't deserve it any better. Check that you have partman-base version 101 on it as that has the change, though it should be by now. Will check, CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406419: [powerpc, CHRP] 2.6 kernel does not boot on IBM RS/6000 43p 150
Package: kernel-image-2.6-powerpc Version: 2.6.18+5 during working on another bug, I tried to install the daily d-i build: cdimage.d.o:/cdimage/daily-builds/sid_d-i/20070103-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso on an IBM RS/6000 43p 150. This is a CHRP system, so I used the CHRP-initrd image and tried to netboot it (serial console): ---server TFTP log- Jan 8 00:31:36 mosna dhcpd: BOOTREQUEST from 00:04:ac:97:14:87 via eth0 Jan 8 00:31:36 mosna dhcpd: BOOTREPLY for 192.168.22.58 to cholos (00:04:ac:97:14:87) via eth0 Jan 8 00:31:38 mosna in.tftpd[3649]: RRQ from 192.168.22.58 filename vmlinuz-chrp.initrd ---server TFTP log- As you can see, the image is loaded just fine. ---client boot log- 0 boot net:192.168.22.51,vmlinuz-chrp.initrd,192.168.22.58 LOAD: Waiting 60 seconds for Spanning Tree BOOTP R = 1 BOOTP S = 1 FILE: vmlinuz-chrp.initrd Load Addr=0x4000 Max Size=0xbfc000 FINAL Packet Count = 10753 Final File Size = 5505188 bytes. zImage starting: loaded at 0x0040 (sp: 0x00efffe0) Allocating 0x36f658 bytes for kernel ... OF version = 'IBM,TCP04195' Allocating 0x3bb2ca bytes for initrd ... initial ramdisk moving 0x137 - 0x574000 (0x3bb2ca bytes) initrd head: 0x1f8b0808 gunzipping (0x100 - 0x407000:0x573abe)...done 0x33e654 bytes OF stdout device is: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] command line: console=ttyS0,9600 console=tty0 memory layout at init: alloc_bottom : 0172c000 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 Looking for displays found display : /[EMAIL PROTECTED]/[EMAIL PROTECTED], opening ... done instantiating rtas at 0x1ffe5000 ... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x0172d000 - 0x0172dd6d Device tree struct 0x0172e000 - 0x01732000 Calling quiesce ... returning from prom_init Using CHRP machine description Total memory = 512MB; using 1024kB for hash table (at cff0) Linux version 2.6.18-3-powerpc (Debian 2.6.18-8) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 Sun Dec 10 17:59:01 CET 2006 Found initrd at 0xc137:0xc172b2ca chrp type = 5 PCI buses 0..1 controlled by pci at 8000 Built 1 zonelists. Total pages: 131072 Kernel command line: console=ttyS0,9600 console=tty0 OpenPIC at f9e8 OpenPIC irqs 0..15 in IDU mpic: Setting up MPIC MPIC version 1.0 at f9e8, max 4 CPUs mpic: ISU size: 16, shift: 4, mask: f mpic: Initializing for 16 sources i8259 legacy interrupt controller initialized PID hash table entries: 4096 (order: 12, 16384 bytes) ---client boot log- Booting just stops here, nothing is displayed on the front LED. As this box has a video card inside, I tried booting over the graphical console, too. There it stops dead after the line: coming back from prom_init Booting from CD isn't working at all, stops with a front LED error display of 185 - which can be anything. Most likely, this bug can't be resolved before etch, but I thought I should report it nonetheless, HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405579: PowerPC, prep-flavor: manual partitioning error
Hi, [del] Yes, looks likely. I'd suggest just compiling parted_server with that change (just run 'make'). There's a slight problem with that. The only PPC system I have which is running etch ATM is my test box. I have a production system running woody, but I doubt that a woody build parted_server will work with an etch d-i. I'm sure this has never been tried ;-) After that use scp (you need to load the openssh-client-udeb for that) to copy it into a running d-i and see what happens. Again, no need to build a whole package or new image for such a focussed change. Cool :-) CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405705: [powerpc, manual] Booting of PREP machines
Hi, On Friday 05 January 2007 18:17, Ulrich Teichert wrote: Currently, the only arch-title; subarchitectures that support CD-ROM -booting are PReP and New World PowerMacs. On PowerMacs, hold the +booting are PReP (with the exception of Motorola PowerStack machines) +and New World PowerMacs. Does this mean that booting from CD is known to work for other PReP systems? I think that Sven Luther had contact to somebody who booted a RS/6000 140p that way. But that's only hearsay, my 140p is currently refusing to boot *at all*, I need to take it apart :-(. Those IBM boxes are such divas, you don't boot them for a month and pooof, they won't boot anymore for anybody That's why I only excluded the PowerStacks in the above paragraph - I am sure that this class of machines does not boot from the daily installer CDs, I've not tested other PReP boxes. CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles)
Bug#405572: PowerPC, prep flavor: missing root= boot option after install
Hi, On Thursday 04 January 2007 16:54, Ulrich Teichert wrote: After a successful installation on a Motorola PowerStack II, rebooting the fresh installation failed, because the kernel option root=/dev/sda2 (in my case) was missing. [...] ROOT=/dev/sda2 should be added to the /etc/initramfs-tools/initramfs.config Can you test if creating a file /etc/initramfs-tools/conf.d/prep-root with such a line works too? If it does, then that is much to be preferred. I just checked out the d-i trunk, I'll see what I can do. Also, the following information is required in order to fix this: =2D does this need to be added for _all_ PReP systems, and if not what algorithm can be used? It has to be added for all PReP systems which use the mkvmlinuz boot loader, so that would be all PRePs, if I am not mistaken. =2D how can the location of the PReP partition be determined; I doubt it will always be /dev/sda2 (use if a regular PATA controller and installation to a different harddisk come to mind) /dev/sda2 isn't the PReP partition. The PReP boot partition *has to be* the first primary partition on the boot disk. /dev/sda2 is the root partition of the fresh install in my case and of course this can and will be different. We only need to know the boot disk, then we know the place and the name of the PReP partition. HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles)
Bug#405572: PowerPC, prep flavor: missing root= boot option after install
Hi, On Saturday 06 January 2007 12:32, Ulrich Teichert wrote: Can you test if creating a file /etc/initramfs-tools/conf.d/prep-root with such a line works too? If it does, then that is much to be preferred. I just checked out the d-i trunk, I'll see what I can do. You don't really need to build a new package for this. You can also just create the file manually from a shell after the base system installation is done. OK, will do. I think the attached patch will do the job as the final solution. It is a bit heavier than strictly needed because of some backwards compatibility support (that needs to be cleaned up after Etch). If you'd like to quickly test the principle after using the installer, try manually adding (using nano) the following (simplified) code in: /var/lib/dpkg/info/base-installer.postinst It should be added just after the resume partition is configured. @@ -767,6 +767,14 @@ echo RESUME=$resume $resumeconf fi fi + + # Set PReP boot partition + if [ $SUBARCH = prep ] [ $rd_generator = initramfs-tools ]; then + prepconf=/target/etc/initramfs-tools/conf.d/prep-boot -^ I think that you wanted to type prep-root here and that's just a typo, right? The same typo is in the proposed-production patch, HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles)
Bug#405572: PowerPC, prep flavor: missing root= boot option after
Hi, [del] I can feel a flu coming on and I think that must be affecting my brain... At least I write ROOT= to the file :-P Ah, yes. The weekend is there and the body relaxes - how ofter I get sick on Friday and go back to work on Monday, oh well I've fixed my copy of the patch. For the tests it does not make any difference what the file is named. Right. I've tested the short version and this results in a booting system without manually appending root= on the mkvmlinuz boot prompt - after I corrected a typo *I* made, of course The newly created file is where it should be, too: [EMAIL PROTECTED]:/etc/initramfs-tools/conf.d$ cat prep-root ROOT=/dev/sda2 [EMAIL PROTECTED]:/etc/initramfs-tools/conf.d$ So, the only thing left for paranoids like me is testing a new daily build with the production solution and that's it. Thanks for the quick solution, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S), Pay The Cobra 24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles)
Bug#405579: PowerPC, prep-flavor: manual partitioning error
Hi,
I think I found a possible source of this:
[del]
/lib/partman/update.d/50filesystems : IN : CHANGE_FILE_SYSTEM
=dev=scsi=host0=bus0=target0=lun0=disc 32256-98703359 prep
parted_server: opening outfifo
parted_server: command_change_file_system(32256-98703359,prep)
parted_server: partition_with_id(32256-98703359)
parted_server: Filesystem + not found, let's see if it is a flag
parted_server: Bad file system or flag type: +
parted_server: line 1616. CRITICAL ERROR!!! EXITING
[del]
In this context 32256-98703359 is the partition ID, prep is only a flag,
not a real partition type. This is important for the code flow in:
packages/partman/partman-base/parted_server.c
there's the function command_change_file_system():
if (2 != iscanf(%as %as, id, s_fstype))
critical_error(Expected partition id and file system);
log(command_change_file_system(%s,%s), id, s_fstype);
part = partition_with_id(disk, id);
if (part == NULL) {
critical_error(Partition not found: %s, id);
}
free(id);
fstype = ped_file_system_type_get(s_fstype);
free(s_fstype);
if (fstype == NULL) {
log(Filesystem %s not found, let's see if it is a flag,
s_fstype);
flag = ped_partition_flag_get_by_name(s_fstype);
if (ped_partition_is_flag_available(part, flag)) {
ped_partition_set_flag(part, flag, 1);
} else {
critical_error(Bad file system or flag type: %s,
s_fstype);
}
} else {
ped_partition_set_system(part, fstype);
}
...
where s_fstype is free'ed too early. I would propose the following patch:
Index: packages/partman/partman-base/parted_server.c
===
--- packages/partman/partman-base/parted_server.c (revision 43984)
+++ packages/partman/partman-base/parted_server.c (working copy)
@@ -1604,7 +1604,6 @@
}
free(id);
fstype = ped_file_system_type_get(s_fstype);
-free(s_fstype);
if (fstype == NULL) {
log(Filesystem %s not found, let's see if it is a flag,
s_fstype);
@@ -1618,6 +1617,7 @@
} else {
ped_partition_set_system(part, fstype);
}
+free(s_fstype);
oprintf(OK\n);
}
===
I am not sure if this will really fix the problem, I'd like to have the
patch reviewed before I take the next step.
HTH,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED]
Stormweg 24 |listening to: Single (Hushpuppies), Pay The Cobra
24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405705: [powerpc, manual] Booting of PREP machines
Package: installation-guide Version: svn The information about booting the installer on PPC-PReP machines could need some updating, I could not boot a Motorola Powerstack II from CD (used the daily d-i build: cdimage.d.o:/cdimage/daily-builds/sid_d-i/20070103-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso). The CD itself was readable during installation in the same CD-ROM drive, so it should not be a hardware fault. I've tried other daily builds as well, same result. A somewhat related issue is that the boot string for netbooting is wrong. For PReP-machines, the firmware expects: boot net:server-ip,file,client-ip I would propose the following patch to the docbook manual sources: Index: en/boot-installer/powerpc.xml === --- en/boot-installer/powerpc.xml (revision 43870) +++ en/boot-installer/powerpc.xml (working copy) @@ -8,7 +8,8 @@ para Currently, the only arch-title; subarchitectures that support CD-ROM -booting are PReP and New World PowerMacs. On PowerMacs, hold the +booting are PReP (with the exception of Motorola PowerStack machines) +and New World PowerMacs. On PowerMacs, hold the keycapc/keycap key, or else the combination of keycapCommand/keycap, keycapOption/keycap, keycapShift/keycap, and keycapDelete/keycap @@ -189,7 +190,11 @@ use the command commandboot enet:0/command. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try -userinputboot replaceableserver_ipaddr/replaceable,replaceablefile/replaceable,replaceableclient_ipaddr/replaceable/userinput. +userinputboot net:replaceableserver_ipaddr/replaceable,replaceablefile/replaceable,replaceableclient_ipaddr/replaceable/userinput. +If this does not work, +userinputhelp boot/userinput +gives available options and syntax descriptions (at least on PowerStacks, +but not on RS/6000 machines). /para /sect2 === I had a look at the generated HTML, was fine for me. If another file should be patched instead, or the patch should be provided in another format, or there are other problems I'm not aware of, please drop me a mail. TIA, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S) 24539 Neumuenster, Germany|Good Looks, Big Deal (Sweatmaster)
Bug#405572: PowerPC, prep flavor: missing root= boot option after install
Package: base-installer Version: 1.70 After a successful installation of the d-i daily netinstall build from: cdimage.d.o:/cdimage/daily-builds/sid_d-i/20070103-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso on a Motorola PowerStack II, rebooting the fresh installation failed, because the kernel option root=/dev/sda2 (in my case) was missing. As soon as I've added this to the options listed on the mkvmlinuz boot prompt, disk booting succeeded. IMHO, this is not a grave bug, but it prevents automatic booting. Short comment from Sven Luther attached: -- ROOT=/dev/sda2 should be added to the /etc/initramfs-tools/initramfs.config file, probably in base-config, and then this one will be no more an issue. Please fill a bug report against base-installer about this, maybe i will provide a patch, we will see. -- The content of /etc/initramfs-tools/initramfs.config after installation: -- # # initramfs.conf # Configuration file for mkinitramfs(8). See initramfs.conf(5). # # # MODULES: [ most | netboot | dep | list ] # # most - Add all framebuffer, acpi, filesystem, and harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # # list - Only include modules from the 'additional modules' list # MODULES=most # BUSYBOX: [ y | n ] # # Use busybox if available. # BUSYBOX=y # # NFS Section of the config. # # # BOOT: [ local | nfs ] # # local - Boot off of local media (harddrive, USB stick). # # nfs - Boot using an NFS drive as the root of the drive. # BOOT=local # # DEVICE: ... # # Specify the network interface, like eth0 # DEVICE=eth0 # # NFSROOT: [ auto | HOST:MOUNT ] # NFSROOT=auto -- TIA, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S) 24539 Neumuenster, Germany|Good Looks, Big Deal (Sweatmaster)
Bug#405579: PowerPC, prep-flavor: manual partitioning error
Package: partman-base Version: 100 During an installation of: cdimage.d.o:/cdimage/daily-builds/sid_d-i/20070103-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso on an Motorola Powerstack II: [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 cpu : 604r clock : ??? revision: 49.2 (pvr 0009 3102) bogomips: 299.00 machine : PReP Utah (Powerstack II Pro4000) l2 cache: 512KiB, parity disabled SRAM:synchronous, pipelined, no parity I had a very strange problem during partitioning. I am just guessing that the culprit is in partman-base, it could be inside partman-prep as well, as it has to do with the prep-boot partition. Anyway, here the full story: Initial boot of the prep boot CD-ROM image (vmlinuz-prep.initrd) over TFTP, then continued the install from the CD-ROM. Yes, this may seem strange, but I have a slow network connection. Graphical console was attached, no additional parameters were set during boot. English as installation language, german keyboard layout, manual network configuration. Nothing special on the initial partioner screen, only some garbled characters shown at the end of the partition description. I had a non-working partition layout on my installation target disk (9 GB SCSI, sda), the prep-boot partition was too small. I deleted all partitions on the disk. So far, so good. As soon as I created a fresh prep-boot partition, an alert box popped up with only question marks and go back and continue buttons. After choosing continue, only the disk itself is shown in the menu (which is OK), but I was not able to create any partitions on it, nor do anything useful. It looked like the partitioner restarted itself, switching to another virtual console only cluttered that console as well. This is reproducible, but prevents looking at log files at that point. Choosing back, I was able to look at the partman log file, I think the relevant lines are (by hand - I was not able to mount NFS volumes...): /lib/partman/update.d/50filesystems : IN : CHANGE_FILE_SYSTEM =dev=scsi=host0=bus0=target0=lun0=disc 32256-98703359 prep parted_server: opening outfifo parted_server: command_change_file_system(32256-98703359,prep) parted_server: partition_with_id(32256-98703359) parted_server: Filesystem + not found, let's see if it is a flag parted_server: Bad file system or flag type: + parted_server: line 1616. CRITICAL ERROR!!! EXITING If you like to have the full log, I can reproduce the bug, but you have to tell me how I get it off the machine at this point. As soon as I used guided partitioning/use full disk/all on one partition, the created partition layout was fine and the install onto it was successful. I would rate this bug at least as annoying, as it prevents manual partitioning from scratch. TIA, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Cauchemar (Opération S) 24539 Neumuenster, Germany|Good Looks, Big Deal (Sweatmaster)
Bug#363423: binutils: [mips] ar doesn't recognize ELF64
Hi, [del] So basically you mean removing ECOFF support in binutils is not a problem. Right? As I tried to explain, it will break arcload and arcboot, and probably some more bootloader-ish things of older machines I don't know of. It would also make it difficult to netboot a DECstation - the firmware only boots ECOFF kernels. I don't know if it will break delo (the DECstation boot loader), too. For Debian, I'd like to have some workaround for arcboot before we kill ECOFF. Please, now that I started testing etch installs on my 5k/33, please don't tell me that I've wasted part of my easter holiday For binutils upstream, I don't want to kill it without previous discussion on the binutils list. I am not sure, but isn't ECOFF still in use by other, still supported OSes? irix? AIX? HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: High On The Crime (Turbonegro) 24539 Neumuenster, Germany|Public Pervert (Interpol) Cauchemar (Opération S)
