Bug#596572: debian-installer: Manual network configuration doesn't allow IPv6 addresses
forcemerge 231003 596572 thanks Quoting Tanu Kaskinen (ta...@iki.fi): On Sun, 2010-09-12 at 19:28 +0200, Christian PERRIER wrote: reassign 596572 netcfg Ah, I wasn't aware of that package. It already had #231003 - Should Yes, netcfg is one of (many) D-I components. include IPv6 support from the beginning. I guess my bug doesn't add much value then, since you already knew that the installer isn't fully IPv6-capable :) Patches welcomed..:-) No doubt. Unfortunately, I don't have the motivation to try to fix this. I was only pretending that I didn't have IPv4 connectivity. Sure. No problem with this, of course. We unfortuunately are missing someone taking care to process netcfg bug reports and wishlist requests. Neraly nothing happened in that package during the lenny-squeeze release cycle. (the fact that netcfg is one of the few d-i packages written in C might be a reason...another being the surprisingly low number of people now working on D-I) Thanks for the hint about this wishlist already existing. That's already some kind of help! signature.asc Description: Digital signature
Processed: Re: Bug#596572: debian-installer: Manual network configuration doesn't allow IPv6 addresses
Processing commands for cont...@bugs.debian.org: forcemerge 231003 596572 Bug#231003: Should include IPv6 support from the beginning Bug#596572: Please allow IPv6 addresses in manual configuration. Bug#509201: Debian Installer does not work with IPv6 Forcibly Merged 231003 509201 596572. thanks Stopping processing here. Please contact me if you need assistance. -- 509201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509201 596572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596572 231003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=231003 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.128435864330524.transcr...@bugs.debian.org
Bug#596633: USB install fails
tags 596633 moreinfo thanks Quoting Miles Fidelman (mfidel...@meetinghouse.net): Package: installation-reports Boot method: USB Installer Image version: download of testing files dated 9/10/10 per USB install instructions Please use the *daily built* images from http://www.debian.org/devel/debian-installernot the alpha1 images. We know that this pages says Please first test alpha1 images but we're currently in the release preparation step and Alpha1 images are more or less broken as of nowand testing them anyway doesn't help that much (yes, we should fix the page...). Comments/Problems: USB installer could not find .iso image After booting, the installer starts up, but when it gets to the point of looking for a .iso image, it reports mounting and scanning both my hard drives (/dev/sda and /dev/sdb) and the usb stick (/dev/sdc1) - but then reports not finding any .iso files. It then asks if I want to do a more thorough search - which exhibits the same failure. As far as I can tell, by escaping to a shell, it has mounted the USB stick (as /hd-media) and there's a .iso image listed under /hd-media. Not sure that daily builds fix this. If they do, we'll close the bug. If they don't, we have an RC issue..:-) signature.asc Description: Digital signature
Bug#596667: debian-installer does not renew DHCP leases
Package: debian-installer The debian installer does not renew a DHCP lease after it has expired. In a network with dynamic ARP inspection[1] this results in loosing the network connection during installation. [1] http://www.ciscopress.com/articles/article.asp?p=1181682seqNum=8 -- Dipl.-Inform. Erik Auerswaldhttp://www.fg-networking.de/ auersw...@fg-networking.de Tel: +49-631-4149988-0 Fax: +49-631-4149988-9 Gesellschaft für Fundamental Generic Networking mbH Geschäftsführung: Volker Bauer, Jörg Mayer Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630 -- 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/20100913082140.gd2...@fgnfs.fg-networking.de
Bug#596667: debian-installer does not renew DHCP leases
On Mon, Sep 13, 2010 at 10:21:40AM +0200, Erik Auerswald wrote: Package: debian-installer Which version? There where several different DHCP client implementations in use over time. The debian installer does not renew a DHCP lease after it has expired. Possible. This means that the lease time is set to an insane low value. You could downgrade to request not-expiring bootp leases. In a network with dynamic ARP inspection[1] this results in loosing the network connection during installation. So you have a infrastructure, that breaks existing things. Bastian -- That unit is a woman. A mass of conflicting impulses. -- Spock and Nomad, The Changeling, stardate 3541.9 -- 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/20100913095442.ga16...@wavehammer.waldi.eu.org
problem installing debian-506-powerpc
Hello, I have a 64-bit p550 power where I tried to install Debian using image http://cdimage.debian.org/debian-cd/5.0.6/powerpc/iso-cd/debian-506-powerpc-CD-1.iso About a year ago I had successfully installed Debian64 but booting with this image it says: [0.510170] Ramdisk: compressed image found at block0 [0.722845] Ramdisk: incomplete write (-28!=32768) 10485760 [0.771772] Ramdisk: ran out of compressed data [0.771782] Ramdisk: invalid compressed format (err=1) [0.791592] List all partitions: [0.791603] No filesystem could mount root, tried: [0.791614] Kernel panic - not syncing: VFS: unable to mount root fs on unkown block(0,1) [0.791631] Rebooting in 180 seconds I gave a try with increasing ramdisk_size but Kernel panic still appears. Googling this error, XFS may be the problem but as far as I noticed it is resolved in Lenny. Can you please help with some advise? Thank you in advance, Zsombor -- 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/aanlktimtasvgg-axdrtsau=47dunpd8vnls-phged...@mail.gmail.com
Bug#596667: debian-installer does not renew DHCP leases
Hi, On Mon, Sep 13, 2010 at 11:54:42AM +0200, Bastian Blank wrote: On Mon, Sep 13, 2010 at 10:21:40AM +0200, Erik Auerswald wrote: Package: debian-installer Which version? There where several different DHCP client implementations in use over time. All those using the one-shot busybox udhcpc. A workaround is to manually request a new IP whenever the lease has expired. The debian installer does not renew a DHCP lease after it has expired. Possible. This means that the lease time is set to an insane low value. You could downgrade to request not-expiring bootp leases. No. network with dynamic ARP inspection[1] this results in loosing the network connection during installation. So you have a infrastructure, that breaks existing things. No, d-i is broken by relying on the assumption that an IP address granted for time t1 is valid for a time t2 t1. -- Dipl.-Inform. Erik Auerswaldhttp://www.fg-networking.de/ auersw...@fg-networking.de Tel: +49-631-4149988-0 Fax: +49-631-4149988-9 Gesellschaft für Fundamental Generic Networking mbH Geschäftsführung: Volker Bauer, Jörg Mayer Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630 -- 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/20100913100206.ge2...@fgnfs.fg-networking.de
Bug#596667: debian-installer does not renew DHCP leases
On Mon, Sep 13, 2010 at 12:02:06PM +0200, Erik Auerswald wrote: On Mon, Sep 13, 2010 at 11:54:42AM +0200, Bastian Blank wrote: On Mon, Sep 13, 2010 at 10:21:40AM +0200, Erik Auerswald wrote: Which version? There where several different DHCP client implementations in use over time. All those using the one-shot busybox udhcpc. Please be more specific. There is no one-shot busybox udhcpc, except it requested. Proof: | $ sudo ./busybox udhcpc -f -i eth0 -V d-i | udhcpc (v1.17.1) started | Sending discover... | Sending select for 10.42.1.252... | Lease of 10.42.1.252 obtained, lease time 10 | Sending renew... | Sending renew... | Sending renew... | Lease lost, entering init state | Sending discover... | Sending select for 10.42.1.252... | Lease of 10.42.1.252 obtained, lease time 10 The renew however seems to get lost somewhere, not sure why. The debian installer does not renew a DHCP lease after it has expired. Possible. This means that the lease time is set to an insane low value. You could downgrade to request not-expiring bootp leases. No. Sure. The installer takes usually less then 30 minutes. So the lease have to expire before that. So it is insanely low. network with dynamic ARP inspection[1] this results in loosing the network connection during installation. So you have a infrastructure, that breaks existing things. No, d-i is broken by relying on the assumption that an IP address granted for time t1 is valid for a time t2 t1. Robustness principle. The dhcp spec explicitely requests that new clients have to check for the ip to be free before using it. Bastian -- Hailing frequencies open, Captain. -- 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/20100913110238.ga17...@wavehammer.waldi.eu.org
Bug#596667: debian-installer does not renew DHCP leases
Hi, On Mon, Sep 13, 2010 at 01:02:38PM +0200, Bastian Blank wrote: On Mon, Sep 13, 2010 at 12:02:06PM +0200, Erik Auerswald wrote: On Mon, Sep 13, 2010 at 11:54:42AM +0200, Bastian Blank wrote: On Mon, Sep 13, 2010 at 10:21:40AM +0200, Erik Auerswald wrote: Which version? There where several different DHCP client implementations in use over time. All those using the one-shot busybox udhcpc. Please be more specific. There is no one-shot busybox udhcpc, except it requested. Yes, my error, the DHCP client in use is dhclient. I did not see any DHCP client running when the installer hung trying to download packages. I assumed udhcpc because it was available and it is a busybox environment in the installer. So the problem was that the DHCP client exited for some reason. The debian installer does not renew a DHCP lease after it has expired. Possible. This means that the lease time is set to an insane low value. You could downgrade to request not-expiring bootp leases. No. Sure. The installer takes usually less then 30 minutes. So the lease have to expire before that. So it is insanely low. The installer can take an arbitrarily large time, because it waits for user input and the user might be interrupted. network with dynamic ARP inspection[1] this results in loosing the network connection during installation. So you have a infrastructure, that breaks existing things. No, d-i is broken by relying on the assumption that an IP address granted for time t1 is valid for a time t2 t1. Robustness principle. The dhcp spec explicitely requests that new clients have to check for the ip to be free before using it. That's totally unrelated. -- Dipl.-Inform. Erik Auerswaldhttp://www.fg-networking.de/ auersw...@fg-networking.de Tel: +49-631-4149988-0 Fax: +49-631-4149988-9 Gesellschaft für Fundamental Generic Networking mbH Geschäftsführung: Volker Bauer, Jörg Mayer Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630 -- 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/20100913114745.gf2...@fgnfs.fg-networking.de
Bug#590678: At least fix www/debian-installer page
Hi, thanks for testing the installer images on usb media and caring enough to report the problems you found. Nowadays usb devices are cheap and even more common than cd/dvd-rom readers and testing d-i on usb media is not so easy to accomplish successfully. There are already several reports on these problems while testing on usb devices. Some of them seems to be caused by using different sets of images to boot/install (the manual warns about it) and if you follow the debian-list/bts you are already aware of several reports on .iso images not being found on media. At this point in time, near the release, it is advised to test the daily images. And of course you are right the installer page does not reflect that. IMO the USB images should be discussed further and try to ease the process of testing them (if possible). There are even submitted patches: #505773. On the other hand, we are now in freeze, and we should fix problems and not make big changes. IMHO this is a good discussion for Squeeze+1. There is a tremendous lack of manpower on d-i development. If you care enough, and have the motivation, please help sorting out this issue. On 12-09-2010 23:47, Javier Barroso wrote: Hi, I think it is not fine closing this bug without clarifies it in http://www.debian.org/devel/debian-installer/index.en.html See seems like you can't install from usb+iso following instructuions from such page, this bug and a thread in debian-user mail list verify that. (isos are from http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/iso-cd/ (feb 2010)) and boot.img.gz linked are from http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/hd-media/ (sept 2010). So should be a link to hd-media from squeeze_di_alpha1, shouldn't it ? Regards, -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- 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/4c8e15f5.1050...@debianpt.org
Bug#596547: keyboard unusable
On Sun, Sep 12, 2010 at 06:33:51PM +0200, Julien Cristau wrote: Anton, do you have an idea how to fix this (or anyone else, for that matter)? We need to parse the xorg.conf keywords and option names case-insensitively, but the option values themselves are case-sensitive. Thanks for your work. I commited the patch of Olivier Schwander. Anton Zinoviev -- 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/20100913130058.gc2...@debian.lan
Bug#590678: At least fix www/debian-installer page
Hi, On Mon, Sep 13, 2010 at 2:15 PM, Miguel Figueiredo el...@debianpt.org wrote: Hi, thanks for testing the installer images on usb media and caring enough to report the problems you found. Nowadays usb devices are cheap and even more common than cd/dvd-rom readers and testing d-i on usb media is not so easy to accomplish successfully. There are already several reports on these problems while testing on usb devices. Some of them seems to be caused by using different sets of images to boot/install (the manual warns about it) and if you follow the debian-list/bts you are already aware of several reports on .iso images not being found on media. At this point in time, near the release, it is advised to test the daily images. And of course you are right the installer page does not reflect that. IMO the USB images should be discussed further and try to ease the process of testing them (if possible). There are even submitted patches: #505773. On the other hand, we are now in freeze, and we should fix problems and not make big changes. IMHO this is a good discussion for Squeeze+1. There is a tremendous lack of manpower on d-i development. If you care enough, and have the motivation, please help sorting out this issue. For the moment should be fine replacing from: - other images (netboot, USB stick, etc) to other images (netboot, USB stick, etc) are not available for squeeze_di_alpha1 but you can test it using daily iso images instead Where should we ask to make this change ? (debian-www ?) or people from debian-boot has access to this page ? In the future I think should be desirable to have a readme in http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/ where we could read about howto use these files (from linux and from others OS). People from windows are lost when they try to install debian from USB. Truly, when usb iso images be available, this will not be true anymore. Thank you ! -- 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/aanlktim8bcvgi1pxkgqayltjd5r-t3s+u=7slr7+v...@mail.gmail.com
Adding tag help for #581683 ([I18N, USABILITY] configure keyboard dialogs)
tags 581683 help reassign 581683 console-setup-udeb thank you Hello, I am adding the tag help for this bug. I don't understand the first part of it (the missing translations). I suppose the file usr/share/console-setup-mini/kbdnames.gz was removed for some reason in the installer image. The fix of the second part would require customized lists of keyboard layouts and this is something I don't want to maintain. Anton Zinoviev -- 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/20100913132441.gd2...@debian.lan
Processed: Adding tag help for #581683 ([I18N, USABILITY] configure keyboard dialogs)
Processing commands for cont...@bugs.debian.org: tags 581683 help Bug #581683 [console-setup] [Graphical-install] [I18N, USABILITY] configure keyboard dialogs Added tag(s) help. reassign 581683 console-setup-udeb Bug #581683 [console-setup] [Graphical-install] [I18N, USABILITY] configure keyboard dialogs Bug reassigned from package 'console-setup' to 'console-setup-udeb'. thank you Stopping processing here. Please contact me if you need assistance. -- 581683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581683 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.12843867531500.transcr...@bugs.debian.org
Re: problem installing debian-506-powerpc
On Mon, Sep 13, 2010 at 11:49:03AM +0200, Zsombor wrote: I have a 64-bit p550 power where I tried to install Debian using image http://cdimage.debian.org/debian-cd/5.0.6/powerpc/iso-cd/debian-506-powerpc-CD-1.iso About a year ago I had successfully installed Debian64 but booting with this image it says: [0.510170] Ramdisk: compressed image found at block0 [0.722845] Ramdisk: incomplete write (-28!=32768) 10485760 [0.771772] Ramdisk: ran out of compressed data [0.771782] Ramdisk: invalid compressed format (err=1) [0.791592] List all partitions: [0.791603] No filesystem could mount root, tried: [0.791614] Kernel panic - not syncing: VFS: unable to mount root fs on unkown block(0,1) [0.791631] Rebooting in 180 seconds I gave a try with increasing ramdisk_size but Kernel panic still appears. Googling this error, XFS may be the problem but as far as I noticed it is resolved in Lenny. Can you please help with some advise? Is this what happens after the install on first boot? I know yaboot certainly didn't work for me when I installed recently on a p520 (power6+ based) machine. I am now running grub2 (with some manual tweaking needed for the install) which works great. I am running squeeze now (I can't remember why lenny didn't work). -- Len Sorensen -- 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/20100913143043.gs2...@caffeine.csclub.uwaterloo.ca
Bug#596633: USB install fails
daily build doesn't work - details at end Christian PERRIER wrote: tags 596633 moreinfo thanks Quoting Miles Fidelman (mfidel...@meetinghouse.net): Package: installation-reports Boot method: USB Installer Image version: download of testing files dated 9/10/10 per USB install instructions Please use the *daily built* images from http://www.debian.org/devel/debian-installernot the alpha1 images. We know that this pages says Please first test alpha1 images but we're currently in the release preparation step and Alpha1 images are more or less broken as of nowand testing them anyway doesn't help that much (yes, we should fix the page...). Comments/Problems: USB installer could not find .iso image After booting, the installer starts up, but when it gets to the point of looking for a .iso image, it reports mounting and scanning both my hard drives (/dev/sda and /dev/sdb) and the usb stick (/dev/sdc1) - but then reports not finding any .iso files. It then asks if I want to do a more thorough search - which exhibits the same failure. As far as I can tell, by escaping to a shell, it has mounted the USB stick (as /hd-media) and there's a .iso image listed under /hd-media. Not sure that daily builds fix this. If they do, we'll close the bug. If they don't, we have an RC issue..:-) Just tried with the daily build - using vmlinuz dated 9/13/10 10:04 from http://people.debian.org/~joeyh/d-i/images/daily/hd-media/vmlinuz initrd.gz dated 9/13/10 10:04 from http://people.debian.org/~joeyh/d-i/images/daily/hd-media/initrd.gz mini.iso dated 9/13/10 10:04 from http://people.debian.org/~joeyh/d-i/images/daily/netboot/mini.iso installer starts up, gives the standard language selection, etc., then: - error: no .iso found - continue to menu, tell it to look for iso, I can see it mount both hard disks and USB stick (both /dev/sdc1 and /dev/sdc); then comes back with the same error and asks if I want to do a more thorough search, answer yes - comes back with failed to find an installer iso image tried to save debug logs to mounted file system, it gave me /hd-media as default, continued - got installation step failed message, with no further details exit to shell, ls /hd-media - sure looks like the USB stick, with mini.iso showing; seems like the stick is mounted ro, remounted as rw back to installer, saved debug log - step completed (seemingly) successfully - but there's no debug log on the stick, nor can I find anything that looks like a debug log anywhere -- 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/4c8e37d7.8070...@meetinghouse.net
Bug#596633: a little more data
Just for the heck of it, I copied the mini.iso to both / and /boot on my hard disk and tried the installer again. Now it reports, after a deep search, no installer iso images found ... while one or more possible iso images were found, they did not look like valid installer iso images -- 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/4c8e4368.3050...@meetinghouse.net
Processing of debian-installer_20100912_amd64.changes
debian-installer_20100912_amd64.changes uploaded successfully to localhost along with the files: debian-installer_20100912.dsc debian-installer_20100912.tar.gz debian-installer_20100912_amd64.deb debian-installer-images_20100912_amd64.tar.gz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1ovb5r-wv...@franck.debian.org
debian-installer_20100912_amd64.changes ACCEPTED into unstable
Accepted: debian-installer-images_20100912_amd64.tar.gz byhand debian-installer_20100912.dsc to main/d/debian-installer/debian-installer_20100912.dsc debian-installer_20100912.tar.gz to main/d/debian-installer/debian-installer_20100912.tar.gz debian-installer_20100912_amd64.deb to main/d/debian-installer/debian-installer_20100912_amd64.deb Changes: debian-installer (20100912) unstable; urgency=low . * Skip last translation changes for rescue and debian-installer- launcher when calculating the translation status since those are rarely used until now. Override entries for your package: debian-installer_20100912.dsc - source devel debian-installer_20100912_amd64.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- 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/e1ovbft-000296...@franck.debian.org
Bug#596633: and a little more info
At someone's suggestion, I tried configuring syslinux.cfg to set INSTALL_MEDIA_DEV=/dev/sdc1 Well - the installer still can't find the .iso, but now - exiting to shell indicates that INSTALL_MEDIA_DEV=/dev/sdc1, but... - instead of mounting /dev/sdc1 as /hd-media, the installer has mounted /dev/sda1 as /hd-media - it hasn't mounted the usb stick at all - it doesn't find the copy of mini.iso that I conveniently left at /dev/sda1/mini.iso -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra -- 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/4c8e4bbc.50...@meetinghouse.net
Bug#445148: closed by Christian Perrier bubu...@debian.org (Closing oldbug report against debian-installer #445148)
I just tried the current download, and can't even get past formatting the DASD. I get a window with the following: ┌──┤ [!!] Partition disks ├──┐ │ ERROR!!! │ │ VTOC: seeking on device failed -- vtoc_write_label │ │ Could not write VTOC labels. │ ││ │ Go Back Continue │ ││ └┘ The virtual machine has write access to the disk, so that's not the problem, and I've tried just about every combination of formatting and not formatting, labeling and not labeling the disks before and during the install that I can think of. Obviously, this works somewhere, or it wouldn't have been released in the first place. And I don't think we have a very unique system here, so it should be a fairly standard install. We run about 50 RedHat images, and several SuSE images, so it's not like we're novices at this Any ideas that might help, and won't take three more years to come up with? -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 9/11/10 2:17 AM, Christian PERRIER bubu...@debian.org wrote: Quoting RPN01 (nix.rob...@mayo.edu): I waited three years for ³Let us know if this happens again²?!? Gee... I just closed 2000 installation reports, some dated much more than 3 years. So, yes sorry, we couldn't process all of them and some got ignored. Particularly trying to reproduce S/390 bugs is not as easy as just saying it. In the case of such bugs, then the only option is telling people who had such problems to try reproducing them with the current installer. Particularly those who were due to partitions naming and ordering need to be re-examined because general changes in the installer behaviour wrt this. Not sure it affects S/390, though. -- 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/c8b3b7bd.e3bf%nix.rob...@mayo.edu
Re: problem installing debian-506-powerpc
Hello Len, It is happenning during the install, just after I boot from CD and choosing 'install64' (and any *64) . Tried with all imaginable boot parameters this problem still persists. But I also hate yaboot so I give a chance with grub2 squeeze. Thank you for the advise! Regards, Zsombor On Mon, Sep 13, 2010 at 4:30 PM, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Mon, Sep 13, 2010 at 11:49:03AM +0200, Zsombor wrote: I have a 64-bit p550 power where I tried to install Debian using image http://cdimage.debian.org/debian-cd/5.0.6/powerpc/iso-cd/debian-506-powerpc-CD-1.iso About a year ago I had successfully installed Debian64 but booting with this image it says: [0.510170] Ramdisk: compressed image found at block0 [0.722845] Ramdisk: incomplete write (-28!=32768) 10485760 [0.771772] Ramdisk: ran out of compressed data [0.771782] Ramdisk: invalid compressed format (err=1) [0.791592] List all partitions: [0.791603] No filesystem could mount root, tried: [0.791614] Kernel panic - not syncing: VFS: unable to mount root fs on unkown block(0,1) [0.791631] Rebooting in 180 seconds I gave a try with increasing ramdisk_size but Kernel panic still appears. Googling this error, XFS may be the problem but as far as I noticed it is resolved in Lenny. Can you please help with some advise? Is this what happens after the install on first boot? I know yaboot certainly didn't work for me when I installed recently on a p520 (power6+ based) machine. I am now running grub2 (with some manual tweaking needed for the install) which works great. I am running squeeze now (I can't remember why lenny didn't work). -- Len Sorensen -- 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/aanlkti=ub4c+urb-rti21vuv1c84vjrv7nnkv2sq8...@mail.gmail.com
Re: problem installing debian-506-powerpc
On Mon, Sep 13, 2010 at 06:04:27PM +0200, Zsombor wrote: It is happenning during the install, just after I boot from CD and choosing 'install64' (and any *64) . Tried with all imaginable boot parameters this problem still persists. But I also hate yaboot so I give a chance with grub2 squeeze. Thank you for the advise! Hmm, at least the daily build installer I used about 2 months ago booted. I had to do 'install64 video=ofonly'. Without the ofonly option it won't boot for me. yaboot on the install CD is fine, but yaboot for disk access is hopeless (The debian package hasn't been updated in years, and the fixed version that would work for these machines isn't in Debian as a result). Given yaboot doesn't do software raid, modern linux filesystems or anything else, grub2 is highly preferable even if it takes some manual work to install. -- Len Sorensen -- 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/20100913163415.gt2...@caffeine.csclub.uwaterloo.ca
Bug#596633: USB install fails
Miles Fidelman wrote: Just tried with the daily build - using vmlinuz dated 9/13/10 10:04 from http://people.debian.org/~joeyh/d-i/images/daily/hd-media/vmlinuz initrd.gz dated 9/13/10 10:04 from http://people.debian.org/~joeyh/d-i/images/daily/hd-media/initrd.gz mini.iso dated 9/13/10 10:04 from http://people.debian.org/~joeyh/d-i/images/daily/netboot/mini.iso The mini.iso contains only the netboot kernel and initrd, it is not useful to put that on a USB stick. I think that the documentation about putting a CD image on the USB stick is fairly clear about using an image that will work, such as the netinst image: Next, download a Debian netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in .iso. -- see shy jo signature.asc Description: Digital signature
Bug#596716: debian-installer: please add easy path to bpo and volatile sources
Package: debian-installer Severity: wishlist Hello, Today I wanted to install Debian lenny on a recent new machine with is not supported by debian-installer kernel in lenny. I also tried kmuto's d-i backport, but it is bit out of date. I believe it would not be hard to ask a new debconf question on whether you want to add bpo and/or volatile sources list for the installer to pick up new kernel and packages. Best regards, -- Hector Oron -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20100913170230.969.51539.report...@enorme
Bug#596633: USB install fails
Joey Hess wrote: The mini.iso contains only the netboot kernel and initrd, it is not useful to put that on a USB stick. I think that the documentation about putting a CD image on the USB stick is fairly clear about using an image that will work, such as the netinst image: Next, download a Debian netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in .iso. Actually, the instructions AREN'T that clear. The instructions start out with: There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common. For the first installation method you'll need to download an installer image from the |netboot| directory (at the location mentioned in Section 4.2.1, “Where to Find Installation Images” http://d-i.alioth.debian.org/manual/en.i386/ch04s02.html#where-files) and use the “flexible way” explained below to copy the files to the USB stick. The only installer image in the netboot directory is mini.iso I started out using the flexible way and a netinst iso - but that failed. I then tried the mini.iso - both alpha1 and the daily build. I just tried with the latest netinst iso http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso dated 9/13/10 Seems to work. (By work, I mean the installer found the .iso. It's doing the install now. If that doesn't work, that would be a different problem.) So conclusions seems to be: 1. Initial problem was a result of incompatibilities between the alpha1 netinst.iso and the USB installer bits 2. Subsequent problem was on my end - using the mini.iso from the daily build instead of the netinst.iso 3. The manual pages are really broken regarding USB installation. 4. The basic bug report can be closed out, but might want to be re-opened as a documentation bug. If somebody wants to point me in the right direction I can open that and/or take a stab at rewriting the install instructions based on my recent experience. I'd need some direction as to: a) how to submit documentation, and b) since the documentation will need to change at release time (from: use the daily build bits, to a final formulation), what might be the procedure for submitting two versions of the documentation? Miles Fidelman -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra -- 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/4c8e5fc1.8000...@meetinghouse.net
Processed: Do we really need to say hey, I'm rebooting when user press Ctrl-Alt-Suppr inside D-I?
Processing commands for cont...@bugs.debian.org: tags 246498 moreinfo Bug #246498 [debian-installer] main-menu: Should indicate Ctrl-Alt-Delete/kbrequest prompted reboot in progress. Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 246498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246498 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.12843999586453.transcr...@bugs.debian.org
Bug#246498: Do we really need to say hey, I'm rebooting when user press Ctrl-Alt-Suppr inside D-I?
tags 246498 moreinfo thanks This wishlist bug says When the user presses Control-Alt-Delete / kbrequest, there should be an indication that the system is being rebooted. Currently, nothing occurs. Interaction with the installer continues right up until the screen goes black I agree that nothing shows up. But that nothing shows up for a fraction of second, then the system reboots So, do we really want to add extra complexity in D-I to the expense of memory and size impact for something for which there is no real need. After all, the user will very quickly learn that (s)he rebooted the machine and there's indeed nothing (s)he can do to avoid that. I think we should close this bug as a non-issue. -- signature.asc Description: Digital signature
Bug#252426: marked as done (no oldworld mac boot floppies)
Your message dated Mon, 13 Sep 2010 19:31:27 +0200 with message-id 20100913173127.gf3...@mykerinos.kheops.frmug.org and subject line No more floppies...no more bug has caused the Debian Bug report #252426, regarding no oldworld mac boot floppies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 252426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Severity: important The beta4 and tc1 ppc iso images don't have a bootable floppy image for oldworld PPC macs that cannot boot off the CD. Additionally, the installer is unable to actually make these Macs bootable from HD. I've had no luck with manually configuring 'QUIK' sofar and partman doesn't seem to create a yaboot bootstrap partition. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc Kernel: Linux 2.4.25-powerpc Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 ---End Message--- ---BeginMessage--- We no longer have boot floppies, so these architectures are no longer the only ones without boot floppies. Hence closing the bug report..:) -- signature.asc Description: Digital signature ---End Message---
Bug#256177: marked as done (want a way to load extra udebs from usb stick)
Your message dated Mon, 13 Sep 2010 19:32:34 +0200 with message-id 20100913173234.gg3...@mykerinos.kheops.frmug.org and subject line Loading extra udebs is now supported... has caused the Debian Bug report #256177, regarding want a way to load extra udebs from usb stick to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 256177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Debian-installer-version: Sarge Installer Test candidate 1 uname -a: Linux anubis 2.4.26-1-686-smp #1 SMP Sat May 1 19:17:11 EST 2004 i686 GNU/Linux Date: Fri Jun 25 Method: Network installation, no proxied Machine: Custom server Processor: bi-Pentium II 333 Memory: 256 MB Root Device: scsi Root Size/partition table: /dev/sda1 * 1 511 4104576 83 Linux /dev/sda2 512 555 353430 82 Linux swap Output of lspci: :00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 02) :00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 02) :00:04.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) :00:04.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) :00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) :00:04.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:06.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891 :00:0a.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24) :00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24) :01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G100 [Productiva] AGP (rev 02) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [E] 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 Comments/Problems: The overall install went ok, new installer rocks ! The error (loading modules) does not really concerns only this machine, but is a more general thought for problems I had on several sarge installations. When trying to add custom modules for specific hardware (some broadcom ethernet cards, for ex) we can preload modules from floppy. Great. Now the problem is: what if there is NO floppy ! It would be great if installer allowed to preload modules not only from floppy, but also on usb key (using mass storage) because it is becoming the de-facto standard on many laptop and even workstations. Thanks for your work, and keep doing this. Regards, /P -- Pierre CHIFFLIER Moyens Informatiques CPE LYON,Domaine Scientifique de la Doua 3 rue Victor Grignard, 69616 VILLEURBANNE Cedex, B.P 2077 tel: (33) 04 72 43 27 77 Fax: (33) 04 72 43 15 91 Email: chiffl...@cpe.fr ---End Message--- ---BeginMessage--- ...this is why we have the load-media udeb. -- signature.asc Description: Digital signature ---End Message---
Bug#262200: marked as done (debian-installer: d-i downloads unneeded packages)
Your message dated Mon, 13 Sep 2010 19:50:22 +0200 with message-id 20100913175022.gh3...@mykerinos.kheops.frmug.org and subject line The right udebs are downloaded has caused the Debian Bug report #262200, regarding debian-installer: d-i downloads unneeded packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 262200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Severity: normal I'm doing a network install via modem. I've discovered d-i downloading, amongst others, jfs and lvm udebs. I won't be using either, so this is simply wasted time. I suggest that downloading and installing optional udebs be deferred until it's clear they are wanted. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.5-1-686 Locale: LANG=C, LC_CTYPE=C ---End Message--- ---BeginMessage--- Either they're priority: standard and they're used by defaultor priority: optional and they're used only when specifically requested by users. Maybe in some cases, one may wonder if this or that udeb should be downloaded (or included in an image), or just made optional, but I don't think we need an extra mechanisme than package priorities. -- signature.asc Description: Digital signature ---End Message---
Bug#315393: marked as done (Problems installing Sarge on OldWorld 7300/200 Mac)
Your message dated Mon, 13 Sep 2010 19:31:27 +0200
with message-id 20100913173127.gf3...@mykerinos.kheops.frmug.org
and subject line No more floppies...no more bug
has caused the Debian Bug report #252426,
regarding Problems installing Sarge on OldWorld 7300/200 Mac
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
252426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package:debian-installer
Architecture: powerpc
Flavour:pmac
Hi!
I got two 7300/200 these days and tried to install Debian Stable (sarge)
on them. Looking through the ppc-specific installation instructions, I
want to give some hints/bugs/wishlist items (note that this box isn't
pre-installed with MacOS, so I cannot just copy over the hd-install
stuff, no BootX, no StuffIt, no nothing):
* The 7300/200 seems to not be able to boot off a CD-ROM, at least I
failed to do that using
http://cdimage.debian.org/debian-cd/3.1_r0a/powerpc/iso-cd/debian-31r0a-powerpc-businesscard.iso
Maybe I just used a wrong boot command line, but the install
instructions are somewhat poor describing the actual boot process
(note: I just got these Macs and never ever touched any Mac before).
* Booting from floppy images
(ftp://ftp.debian.org/debian/dists/stable/main/installer-powerpc/current/images/powerpc/floppy-2.4/*)
also didn't work. The {ofonly,}boot.img floppies are just always
ejected.
* The install manual references a boot-floppy-hfs image, but that's
not in the sarge installer directory. Though, it exists in woody's
installer.
* After failing with installing sarge, I tried to install woody. The
boot-floppy-hfs.img boots (boot floppy:vmlinux), the installation
basically works (http://www.biccard.com/alan/7200/7200boot.html).
Even the Quik part was fixed (contraty to the document above), nice.
However, woody's installer kernel (2.2.x) seems to have some trouble
with the MESH SCSI controller. On both of my Macs, tested with three
different HDDs, I got into I/O errors sooner or later (sometimes
during debootstrap'ing the initial installation, sometimes later
on).
Unfortunately, it doesn't work to initially boot with
boot-floppy-hfs and then continue with sarge's boot/root/driver
floppies. These do have devfs issues and are unwilling to work.
Woody's install document
(ftp://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/README.txt)
even references the SRM console, so it's obviously just copied from
the Alpha port and was fixed in some places afterwards.
So I'd like to get sarge boot floppies (or a CD, if the 7300/200 can
boot off it) to install Debian on this box. Also, the documentation
should be a bit more verbose especially about the boot command and
eventually ask the user to first reset the OF variables...
Thanks, JBG
--
Jan-Benedict Glaw jbg...@lug-owl.de. +49-172-7608481 _ O _
Eine Freie Meinung in einem Freien Kopf| Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
We no longer have boot floppies, so these architectures are no longer
the only ones without boot floppies. Hence closing the bug report..:)
--
signature.asc
Description: Digital signature
---End Message---
Bug#231766: Maybe allow choose-mirror to use a mirror copy on local media
reassign 231766 choose-mirror retitle 231766 Should allow retrieving files from a local (mounted media) mirror thanks Maybe this bug could be addressed by adding support for file:/ locations in choose-mirror? I'm not really sure that anyone has enough interest in this for such enhancement to ever appear but I think it would be the right way to address the user feature request in this bug report. -- signature.asc Description: Digital signature
Bug#247078: ISDN?
tags 247078 wontfix thanks I don't think anyone will ever really bother to add udebs for ISDN support in D-I now that ISDN is slowly dying. -- signature.asc Description: Digital signature
Processed: Maybe allow choose-mirror to use a mirror copy on local media
Processing commands for cont...@bugs.debian.org: reassign 231766 choose-mirror Bug #231766 [debian-installer] Please include mounted file system retriever Bug reassigned from package 'debian-installer' to 'choose-mirror'. retitle 231766 Should allow retrieving files from a local (mounted media) mirror Bug #231766 [choose-mirror] Please include mounted file system retriever Changed Bug title to 'Should allow retrieving files from a local (mounted media) mirror' from 'Please include mounted file system retriever' thanks Stopping processing here. Please contact me if you need assistance. -- 231766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=231766 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.128440054410490.transcr...@bugs.debian.org
Bug#596633: USB install fails
Quoting Miles Fidelman (mfidel...@meetinghouse.net): installer starts up, gives the standard language selection, etc., then: - error: no .iso found - continue to menu, tell it to look for iso, I can see it mount both hard disks and USB stick (both /dev/sdc1 and /dev/sdc); then comes back with the same error and asks if I want to do a more thorough search, answer yes - comes back with failed to find an installer iso image tried to save debug logs to mounted file system, it gave me /hd-media as default, continued - got installation step failed message, with no further details exit to shell, ls /hd-media - sure looks like the USB stick, with mini.iso showing; seems like the stick is mounted ro, remounted as rw Err, you're not supposed to put the mini.iso on the USB stick, but either the businesscard or netinst images. signature.asc Description: Digital signature
Bug#247218: marked as done (should document which powerpc machines need video=ofonly kernel parameter)
Your message dated Mon, 13 Sep 2010 19:29:35 +0200 with message-id 20100913172935.ge3...@mykerinos.kheops.frmug.org and subject line Bug obsoleted by switch to X has caused the Debian Bug report #247218, regarding should document which powerpc machines need video=ofonly kernel parameter to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 247218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Version: d-i beta4 Severity: important -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.5 Locale: lang=es...@euro, lc_ctype=es...@euro INSTALL REPORT Debian-installer-version: May 02 2004 from http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/powerpc/beta4/sarge-powerpc-netinst.iso uname -a: Linux melite 2.4.25-powerpc #1 mer avr 14 15:38:38 CEST 2004 ppc GNU/Linux Date: May 02 2004 11:23:40 Method: How did you install? From a CD netinst image. What did you boot off? Directly from CD. If network install, from where? Via a router with DHCP server. Proxied? No. Machine: PowerBook G4 17 alu (PowerBook5,3) Processor: 1333MHz Memory: 512MB output of cat /proc/cpuinfo: processor : 0 cpu : 7457, altivec supported clock : 1333MHz revision: 1.1 (pvr 8002 0101) bogomips: 542.31 machine : PowerBook5,3 motherboard : PowerBook5,3 MacRISC3 Power Macintosh board revision : 0001 detected as : 287 (PowerBook G4 17) pmac flags : 000a L2 cache: 512K unified memory : 512MB pmac-generation : NewWorld Root Device: IDE: FUJITSU MHT2080AT, ATA DISK drive Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. #type name length base ( size ) system mounted on /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_Bootstrap bootstrap 1600 @ 64 (800.0k) NewWorld bootblock /dev/hda3 Apple_UNIX_SVR2 swap 2457600 @ 1664 ( 1.2G) Linux swap /dev/hda4 Apple_UNIX_SVR2 root 299008 @ 2459264 (146.0M) Linux native / /dev/hda5 Apple_UNIX_SVR2 usr 8388608 @ 2758272 ( 4.0G) Linux native /usr /dev/hda6 Apple_UNIX_SVR2 usr/local8388608 @ 11146880 ( 4.0G) Linux native /usr/local /dev/hda7 Apple_UNIX_SVR2 var 8388608 @ 19535488 ( 4.0G) Linux native /var /dev/hda8 Apple_UNIX_SVR2 tmp 102400 @ 27924096 ( 50.0M) Linux native /tmp /dev/hda9 Apple_UNIX_SVR2 home39539968 @ 28026496 ( 18.9G) Linux native /home /dev/hda10 Apple_HFS Apple_HFS_Untitled_3 67042112 @ 67566464 ( 32.0G) HFS /dev/hda11 Apple_Free Extra 262144 @ 134608576 (128.0M) Free space /dev/hda12 Apple_HFS Apple_HFS_Untitled_4 21430752 @ 134870720 ( 10.2G) HFS /dev/hda13 Apple_Free Extra 16 @ 156301472 ( 8.0k) Free space Block size=512, Number of Blocks=156301488 DeviceType=0x0, DeviceId=0x0 Output of lspci and lspci -n: :00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP :00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] :10:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0035 :10:12.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 02) :10:13.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller :10:17.0 Class ff00: Apple Computer Inc.: Unknown device 003e :10:18.0 USB Controller: Apple Computer Inc.: Unknown device 003f :10:19.0 USB Controller: Apple Computer Inc.: Unknown device 003f :10:1a.0 USB Controller: Apple Computer Inc.: Unknown device 003f :10:1b.0 USB Controller: NEC Corporation USB (rev 43) :10:1b.1 USB Controller: NEC Corporation USB (rev 43) :10:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04) :24:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0036 :24:0d.0 Class ff00: Apple Computer Inc.: Unknown device 003b :24:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 81)
Processed: ISDN?
Processing commands for cont...@bugs.debian.org: tags 247078 wontfix Bug #247078 [debian-installer] Please support ISDN connectivity Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 247078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247078 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.128440114413572.transcr...@bugs.debian.org
Bug#596730: tasksel KDE does not install OpenOffice/KDE-integration
Package: tasksel On Monday 13 September 2010 10:10:54 Klaus Staerk wrote: Hello Debian KDE maintainers, when installing Debian squeeze from netinst CD and choosing KDE as alternative desktop environment, OpenOffice is installed but not the package for OpenOffice/KDE integration. Let's record this as a bug against tasksel. /Sune -- 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/201009132007.29730.s...@debian.org
Bug#213013: Wishlist still needed? (install logging with script)
Dear user (aha...), Do you think that the feature you wished to have in D-I (ability to run D-I from a script with all output logged as well as timings recorded...and ability to save installation logs in the target) is addressed by changes we made since then in D-I (for instance the installation-report udeb)? In any case, thank you, dear user, for your interest in Debian Installer. This very nice piece of software deserves attention and people who developed it are very proud of it. -- signature.asc Description: Digital signature
Processed: Re: Bug#581758: keyboard-configuration: way to enable xserver zapping not documented
Processing commands for cont...@bugs.debian.org: tags 581758 patch Bug #581758 [keyboard-configuration] keyboard-configuration: way to enable xserver zapping not documented Added tag(s) patch. severity 581758 minor Bug #581758 [keyboard-configuration] keyboard-configuration: way to enable xserver zapping not documented Severity set to 'minor' from 'normal' thank you Stopping processing here. Please contact me if you need assistance. -- 581758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581758 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.128440257223275.transcr...@bugs.debian.org
Bug#213013: Wishlist still needed? (install logging with script)
Christian PERRIER wrote: Do you think that the feature you wished to have in D-I (ability to run D-I from a script with all output logged as well as timings recorded...and ability to save installation logs in the target) is addressed by changes we made since then in D-I (for instance the installation-report udeb)? Partially but not entirely. -- see shy jo signature.asc Description: Digital signature
Bug#596633: USB install fails
Quoting Miles Fidelman (mfidel...@meetinghouse.net): Err, you're not supposed to put the mini.iso on the USB stick, but either the businesscard or netinst images. the instructions page implies that you can do a netboot, using the .iso found in the /netboot directory - where the only iso is mini.iso - seems like another documentation bug Hmmm, from http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html: Installation images for the second installation method can be found in the hd-media directory and either the -Y´easy way¡ or the ´flexible way¡ can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of debian-installer. If they do not match you are likely to get errors[6] during the installation. Then later, on the detailed instructions: 4.3.1. Copying the files — the easy way There is an all-in-one file hd-media/boot.img.gz which contains all the installer files (including the kernel) as well as syslinux and its configuration file. Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 256 MB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose. A second disadvantage is that you cannot copy a full CD image onto the USB stick, but only the smaller businesscard or netinst CD images. To use this image simply extract it directly to your USB stick: # zcat boot.img.gz /dev/sdX After that, mount the USB memory stick (mount /dev/sdX /mnt), which will now have a FAT filesystem on it, and copy a Debian netinst or businesscard ISO image to it. Unmount the stick (umount /mnt) and you are done. 4.3.2. Copying the files — the flexible way If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that — if the capacity of your USB stick is large enough — you have the option of copying a full CD ISO image to it. 4.3.2.1. Partitioning the USB stick We will show how to set up the memory stick to use the first partition, instead of the entire device. Note Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use cfdisk or any other partitioning tool to create a FAT16 partition[7], and then create the filesystem using: # mkdosfs /dev/sdX1 Take care that you use the correct device name for your USB stick. The mkdosfs command is contained in the dosfstools Debian package. In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. lilo) should work, it's convenient to use syslinux, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader. To put syslinux on the FAT16 partition on your USB stick, install the syslinux and mtools packages on your system, and do: # syslinux /dev/sdX1 Again, take care that you use the correct device name. The partition must not be mounted when starting syslinux. This procedure writes a boot sector to the partition and creates the file ldlinux.sys which contains the boot loader code. 4.3.2.2. Adding the installer image Mount the partition (mount /dev/sdX1 /mnt) and copy the following installer image files to the stick: * vmlinuz or linux (kernel binary) * initrd.gz (initial ramdisk image) You can choose between either the regular version or the graphical version of the installer. The latter can be found in the gtk subdirectory. If you want to rename the files, please note that syslinux can only process DOS (8.3) file names. Next you should create a syslinux.cfg configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to -Y´linux¡ if you used a netboot image): default vmlinuz append initrd=initrd.gz For the graphical installer you should add video=vesa:ywrap,mtrr vga=788 to the second line. If you used an hd-media image, you should now copy a Debian ISO image[8] onto the stick. When you are done, unmount the USB memory stick (umount /mnt). .../... [8] You can use either a businesscard, a netinst or a full CD image (see Section 4.1, -Y´Official Debian GNU/Linux CD-ROM Sets¡). Be sure to select one that fits. Note that the ´netboot mini.iso¡ image is not usable for this purpose. I wonder what elese we would need to document, indeed... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe.
Bug#581758: keyboard-configuration: way to enable xserver zapping not documented
clone 581758 -1 severity -1 normal tags -1 - patch retitle -1 way to enable xserver zapping not documented reassign -1 release-notes thank you On Mon, May 17, 2010 at 12:28:13PM +0200, Petr Baudis wrote: What about adding this in /etc/default/keyboard ? # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options -# in /etc/X11/xorg.conf. +# in /etc/X11/xorg.conf. Notably, XkbOptions now needs to explicitly +# set terminate:ctrl_alt_bksp to enable the traditional X server +# zapping behavior. Another option would be to at least make sure that the Squeeze release notes outline this clearly. I'm not sure what the process for this would be as there seem to be no release notes available yet. I am reassigning a clone of this bug to release-notes. I can not provide the exact wording but I suppose s.t. like the following can be used (based on /usr/share/doc/xkb-data/NEWS.Debian.gz and the text of Petr Baudis): After the upgrade, the Ctrl-Alt-Backspace key combination can no longer be used to kill the X server. If you would like to re-enable this functionality globally, use dpkg-reconfigure keyboard-configuration or simply add an option terminate:ctrl_alt_bksp in /etc/default/keyboard to the value of the variable XKBOPTIONS. If you would like to re-enable this feature for a particular user only, you may do so with the desktop's Keyboard Preferences application of the respective user. You may also enable it for the current session using the command setxkbmap -option terminate:ctrl_alt_bksp. Anton Zinoviev -- 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/20100913184458.gf2...@debian.lan
Processed: Re: Bug#581758: keyboard-configuration: way to enable xserver zapping not documented
Processing commands for cont...@bugs.debian.org: clone 581758 -1 Bug#581758: keyboard-configuration: way to enable xserver zapping not documented Bug 581758 cloned as bug 596738. severity -1 normal Bug #596738 [keyboard-configuration] keyboard-configuration: way to enable xserver zapping not documented Severity set to 'normal' from 'minor' tags -1 - patch Bug #596738 [keyboard-configuration] keyboard-configuration: way to enable xserver zapping not documented Removed tag(s) patch. retitle -1 way to enable xserver zapping not documented Bug #596738 [keyboard-configuration] keyboard-configuration: way to enable xserver zapping not documented Changed Bug title to 'way to enable xserver zapping not documented' from 'keyboard-configuration: way to enable xserver zapping not documented' reassign -1 release-notes Bug #596738 [keyboard-configuration] way to enable xserver zapping not documented Bug reassigned from package 'keyboard-configuration' to 'release-notes'. Bug No longer marked as found in versions console-setup/1.51. thank you Stopping processing here. Please contact me if you need assistance. -- 596738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596738 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 581758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581758 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.128440374329863.transcr...@bugs.debian.org
Bug#445148: closed by Christian Perrier bubu...@debian.org (Closing oldbug report against debian-installer #445148)
On Mon, 13 Sep 2010 12:13:01 -0400 (EDT), Robert Nix wrote: I just tried the current download, and can't even get past formatting the DASD. I get a window with the following: ┌──┤ [!!] Partition disks ├──┐ │ ERROR!!! │ │ VTOC: seeking on device failed -- vtoc_write_label │ │ Could not write VTOC labels. │ ││ │ Go Back Continue │ ││ └┘ The virtual machine has write access to the disk, so that's not the problem, and I've tried just about every combination of formatting and not formatting, labeling and not labeling the disks before and during the install that I can think of. Obviously, this works somewhere, or it wouldn't have been released in the first place. And I don't think we have a very unique system here, so it should be a fairly standard install. We run about 50 RedHat images, and several SuSE images, so it's not like we're novices at this Any ideas that might help, and won't take three more years to come up with? Excuse me for butting in here gentlemen. This is not my bug report, and I am not a member of the Debian Installer team, but I do run the s390 port of Debian GNU/Linux in a virtual machine under z/VM; so perhaps I can be of some service here. Which version of the Debian installer did you try to run? Please be as specific as possible about the URL where you downloaded it from, etc. The last time I tried to run the production Squeeze installer for s390, it wouldn't even boot. (In fairness, that was several months ago.) I tried the latest daily build installer and it worked; so I stuck to it. The daily build installation images were at one time hosted by an external site. But all of a sudden, the server went down and never came back up. After being down for a month, Frans Pop, the leading Debian Installer person for s390, started doing the daily builds himself. That was fine for a while. But he died recently, leaving very big shoes to fill. When he died, his Debian work space disappeared with him, and with it the daily build installation images. We need to get those back. Anyway, if you will point me to the installation images that you used, I will give it a go here and see if I can reproduce your problem. -- .''`. Stephen Powell : :' : `. `'` `- -- 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/1469216320.79928.1284404128463.javamail.r...@md01.wow.synacor.com
Processed: Re: Bug#590743: keyboard-configuration: XKBOPTIONS seems to be not propagated
Processing commands for cont...@bugs.debian.org: reassign 590743 xserver-xorg Bug #590743 [keyboard-configuration] keyboard-configuration: XKBOPTIONS seems to be not propagated Bug reassigned from package 'keyboard-configuration' to 'xserver-xorg'. Bug No longer marked as found in versions console-setup/1.55. thank you Stopping processing here. Please contact me if you need assistance. -- 590743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590743 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.12844045241687.transcr...@bugs.debian.org
Bug#581758: keyboard-configuration: way to enable xserver zapping not documented
tags 581758 patch severity 581758 minor thank you I'm lowering the severity because this is not realy a bug of console-setup. I think I'd better postpone the following patch until squeeze is released. On Sat, May 15, 2010 at 05:30:46PM +0200, Petr Baudis wrote: Either keyboard-configuration setup should handle enabling the zapping without touching the rest of the layout setup, or it needs to be clearly documented that users can enable it themselves by appending terminate:ctrl_alt_bksp to XKBOPTIONS. The following patch should make keyboard-configuration ask the option questions even if the layout is not supported. Index: debian/keyboard-configuration.config === --- debian/keyboard-configuration.config(revision 64701) +++ debian/keyboard-configuration.config(working copy) @@ -1147,6 +1147,14 @@ db_metaget keyboard-configuration/other description other=$RET if [ $unsupported_layout = yes ]; then +case $XKBLAYOUT in +*,*) +latin=no +;; +*) +latin=yes +;; +esac db_set keyboard-configuration/variantcode $XKBVARIANT # skip the question without making Debconf loop STATE=$(( $STATE + $STATE - $old_state )) @@ -1236,10 +1244,7 @@ fi ;; 5) - if \ - [ ! $unsupported_layout = yes \ - -a $unsupported_options = yes ] - then + if [ $unsupported_options = yes ]; then if [ -f $CONFIGFILE ]; then db_subst keyboard-configuration/unsupported_config_options \ XKBOPTIONS $XKBOPTIONS @@ -1275,10 +1280,7 @@ fi ;; 6) - if \ - [ $unsupported_layout = yes \ - -o $unsupported_options = yes ] - then + if [ $unsupported_options = yes ]; then db_set keyboard-configuration/optionscode $XKBOPTIONS # skip the questions without making Debconf loop STATE=$(( $STATE + $STATE - $old_state )) Anton Zinoviev -- 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/20100913182527.ge2...@debian.lan
Processed (with 1 errors): merging 581756 and 568645
Processing commands for cont...@bugs.debian.org: severity 581756 minor Bug #581756 [keyboard-configuration] keyboard-configuration: want config changes to propagate to udev/Xorg without reboot Severity set to 'minor' from 'wishlist' merge 581756 568645 Bug#568645: setupcon requires udevadm trigger udevadm settle Bug#581756: keyboard-configuration: want config changes to propagate to udev/Xorg without reboot Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #568645 has `console-setup'; #581756 has `keyboard-configuration' thank you Stopping processing here. Please contact me if you need assistance. -- 581756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581756 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.128440655511997.transcr...@bugs.debian.org
Bug#596633: USB install fails
Christian Perrier wrote: Quoting Miles Fidelman (mfidel...@meetinghouse.net): Err, you're not supposed to put the mini.iso on the USB stick, but either the businesscard or netinst images. the instructions page implies that you can do a netboot, using the .iso found in the /netboot directory - where the only iso is mini.iso - seems like another documentation bug Hmmm, from http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html: [8] You can use either a businesscard, a netinst or a full CD image (see Section 4.1, -Y´Official Debian GNU/Linux CD-ROM Sets¡). Be sure to select one that fits. Note that the ´netboot mini.iso¡ image is not usable for this purpose. I seem to have missed that footnote. Ooops. On the other hand, the very first two paragraphs on the page say: There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common. For the first installation method you'll need to download an installer image from the |netboot| directory (at the location mentioned in Section 4.2.1, “Where to Find Installation Images” http://d-i.alioth.debian.org/manual/en.i386/ch04s02.html#where-files) and use the “flexible way” explained below to copy the files to the USB stick. There's only one installer image in the netboot directory - mini.iso - so those instructions are contradictory. I wonder what elese we would need to document, indeed... Clean up contradictions, clean up anything that says to use the alpha1 release and replace it with instructions to use the daily build. Maybe streamline things a bit. Also, I just discovered that there seems to be a bug with the grub-install step of a USB installation, and maybe a problem with installation on RAIDed disks. After succeeding at finding, mounting, and running the netinst.iso (daily build versions), the installer on my sandbox just completed - but... the resulting system isn't bootable. After a little digging, it looks like the installer mounted BOTH my usb stick and one of two raid-ed hard drives as /dev/sda - and really messed things up. I'm busily trying to recreate the situation (after first rebuilding a working system of CD). Once I have some details, I'll send a separate bug report. -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra -- 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/4c8e7e10.6000...@meetinghouse.net
Bug#213013: Wishlist still needed? (install logging with script)
Quoting Joey Hess (jo...@debian.org): Christian PERRIER wrote: Do you think that the feature you wished to have in D-I (ability to run D-I from a script with all output logged as well as timings recorded...and ability to save installation logs in the target) is addressed by changes we made since then in D-I (for instance the installation-report udeb)? Partially but not entirely. OK. Let's leave this opened, then signature.asc Description: Digital signature
Processed: Re: Processed (with 1 errors): merging 581756 and 568645
Processing commands for cont...@bugs.debian.org: reassign 581756 console-setup Bug #581756 [keyboard-configuration] keyboard-configuration: want config changes to propagate to udev/Xorg without reboot Bug reassigned from package 'keyboard-configuration' to 'console-setup'. Bug No longer marked as found in versions console-setup/1.51. merge 581756 568645 Bug#568645: setupcon requires udevadm trigger udevadm settle Bug#581756: keyboard-configuration: want config changes to propagate to udev/Xorg without reboot Merged 568645 581756. End of message, stopping processing here. Please contact me if you need assistance. -- 581756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581756 568645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568645 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.128440731417137.transcr...@bugs.debian.org
Bug#596633: marked as done (USB install fails)
Your message dated Mon, 13 Sep 2010 21:58:47 +0200 with message-id 20100913195847.gl3...@mykerinos.kheops.frmug.org and subject line Re: Bug#596633: USB install fails has caused the Debian Bug report #596633, regarding USB install fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 596633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: USB Installer Image version: download of testing files dated 9/10/10 per USB install instructions Date: 9/12/10 5pm EST Machine: custom built tower Processor: Memory: 1G 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: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] 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:[ ] Comments/Problems: USB installer could not find .iso image After booting, the installer starts up, but when it gets to the point of looking for a .iso image, it reports mounting and scanning both my hard drives (/dev/sda and /dev/sdb) and the usb stick (/dev/sdc1) - but then reports not finding any .iso files. It then asks if I want to do a more thorough search - which exhibits the same failure. As far as I can tell, by escaping to a shell, it has mounted the USB stick (as /hd-media) and there's a .iso image listed under /hd-media. ---End Message--- ---BeginMessage--- Quoting Miles Fidelman (mfidel...@meetinghouse.net): 3. The manual pages are really broken regarding USB installation. I don't think so. They are *very* detailed and give in the right places the right hints: one should use the businesscard or netinst images. 4. The basic bug report can be closed out, but might want to be re-opened as a documentation bug. If somebody wants to point me in the right direction I can open that and/or take a stab at rewriting the install instructions based on my recent experience. I'd need some direction as to: a) how to submit documentation, and b) since the documentation will need to change at release time (from: use the daily build bits, to a final formulation), what might be the procedure for submitting two versions of the documentation? The documentation is meant to be the documentation of the released images, so it can't in any way refer to daily builds. As it has been said in this thread, it is *currently* recommended to use daily builds of D-I. At other moments of the development, it may be better to use the release Alpha|Beta|Whatever versions. We're talking about a version of the installer that's under development, so a moving target. Maybe the main web page for D-I (www.debian.org/devel/debian-installer) should be updated more often, depending on the development context. For instance, right now, they shouldn't even mention Alpha1 images. However, as said above, I don't think that the installation guide needs changes in its explanations about building a properly suited USB stick to install Debian. One may find the process complicated : I also wish it would be simplified instead of requiring users to copy files from various places in order to get things to work.but this is *currently* the existing way to make this work...and the documentation gives all needed details. So, unless someone comes up with a simpler way to create bootable USB sticks to install Debian, I don't see what improvement can be done. That said, patches to svn://svn.debian.org/svn/d-i/trunk/manual and sent as bug reports against installation-guide can always be sent..:-) signature.asc Description: Digital signature ---End Message---
Status of some daily D-I builds
As I just mentioned on IRC, a few daily builds seem currently non optimal: - s390 builds still point to Frans' home on people.d.o. It's very sad to say this, of course, but that doesn't exist anymore..:-( - sparc builds point to Geert Stappers home and haven't been updated since July 12th Could we consider moving these to build daemons just like Luk did for other arches? If so, Luk you seem to be the more qualified person. Would you mind having a look at this? On the other hand, I think that other daily builds done in Joey Hess' home are very safe. Obviously, Joey has proven over years how reliable he can be and I don't see urgency to change this. -- signature.asc Description: Digital signature
Bug#596716: debian-installer: please add easy path to bpo and volatile sources
reassign 596716 apt-setup thanks Quoting Hector Oron (zu...@debian.org): Package: debian-installer Severity: wishlist Hello, Today I wanted to install Debian lenny on a recent new machine with is not supported by debian-installer kernel in lenny. I also tried kmuto's d-i backport, but it is bit out of date. I believe it would not be hard to ask a new debconf question on whether you want to add bpo and/or volatile sources list for the installer to pick up new kernel and packages. Reassigning to apt-setup. Please note that recent discussions in -devel have raised the fact the backports are not automatically upgradable, which many people see as a problem wrt security. This probably needs to be addressed in the backporits repository before we think about proposing adding backports through D-I. Volatile could be added in a way similar to the way we currently propose non-free and contrib, though. However: post-squeeze, please. signature.asc Description: Digital signature
Bug#596730: tasksel KDE does not install OpenOffice/KDE-integration
Quoting Sune Vuorela (s...@debian.org): Package: tasksel On Monday 13 September 2010 10:10:54 Klaus Staerk wrote: Hello Debian KDE maintainers, when installing Debian squeeze from netinst CD and choosing KDE as alternative desktop environment, OpenOffice is installed but not the package for OpenOffice/KDE integration. Let's record this as a bug against tasksel. What's the needed package? signature.asc Description: Digital signature
Bug#596730: tasksel KDE does not install OpenOffice/KDE-integration
Hi, Am 13.09.2010 22:05, schrieb Christian PERRIER: Quoting Sune Vuorela (s...@debian.org): Package: tasksel On Monday 13 September 2010 10:10:54 Klaus Staerk wrote: Hello Debian KDE maintainers, when installing Debian squeeze from netinst CD and choosing KDE as alternative desktop environment, OpenOffice is installed but not the package for OpenOffice/KDE integration. Let's record this as a bug against tasksel. What's the needed package? The name of the package is openoffice.org-kde. HTH, Klaus -- 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/4c8e849b.1020...@gmx.net
Processed: Re: Bug#596716: debian-installer: please add easy path to bpo and volatile sources
Processing commands for cont...@bugs.debian.org: reassign 596716 apt-setup Bug #596716 [debian-installer] debian-installer: please add easy path to bpo and volatile sources Bug reassigned from package 'debian-installer' to 'apt-setup'. thanks Stopping processing here. Please contact me if you need assistance. -- 596716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596716 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.128440829524567.transcr...@bugs.debian.org
Re: Status of some daily D-I builds
Op 20100913 om 22:16 schreef Christian PERRIER: As I just mentioned on IRC, a few daily builds seem currently non optimal: - s390 builds still point to Frans' home on people.d.o. It's very sad to say this, of course, but that doesn't exist anymore..:-( - sparc builds point to Geert Stappers home and haven't been updated since July 12th Oops, my check is on the _build_ result I will upgrade my check on _upload build_ result. Could we consider moving these to build daemons just like Luk did for other arches? If so, Luk you seem to be the more qualified person. Would you mind having a look at this? On the other hand, I think that other daily builds done in Joey Hess' home are very safe. Obviously, Joey has proven over years how reliable he can be and I don't see urgency to change this. Geert Stappers signature.asc Description: Digital signature
Bug#596730: tasksel KDE does not install OpenOffice/KDE-integration
tags 596730 pending thanks Quoting Klaus Staerk (klaus.sta...@gmx.net): What's the needed package? The name of the package is openoffice.org-kde. Funny: I use KDE for ages. Same for OOo. And I didn't have this package..:) I just added it to the kde-desktop task in tasksel's git repository. To KDE maintainers: would be nice if you folks would review the kde-desktop task and eventually the language-kde-desktop tasks (for these: need to check whether some are missing because kde-l10n-XX packages appeared recently). signature.asc Description: Digital signature
Processed: Re: Bug#596730: tasksel KDE does not install OpenOffice/KDE-integration
Processing commands for cont...@bugs.debian.org: tags 596730 pending Bug #596730 [tasksel] tasksel KDE does not install OpenOffice/KDE-integration Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 596730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596730 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.12844096812744.transcr...@bugs.debian.org
Bug#596760: Reportbug installation-reports
Package: installation-reports Boot method: z/VM virtual card reader Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-s390/current/imag es/generic/ Date: 09/13/2010 09:30am Machine: IBM Z9 2094 2IFL z/VM Version 5 Release 3.0, service level 0702 (64-bit) Generated at 10/31/07 09:12:13 CDT Processor: IBM 2094 Memory: 22GIG - 1GIG virtual machine Partitions: (2) 6.88GIG 3390 DASD devices, (1) .09GIG DASD device Output of lspci -knn (or lspci -nn): never got a running Debian system 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: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: DASD configures, and partitions, but fails to write Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. DASD formats, and goes through the configuration. Desired setup was to have / on one larger disk, /usr on the other, and /boot on the small disk. No swap initially (there will be vdisk for that later). Also tried setting up a single large disk for everything. Once I accept any of the configurations, I get the following error: ┌──┤ [!!] Partition disks ├──┐ │ ERROR!!! │ │ VTOC: seeking on device failed -- vtoc_write_label │ │ Could not write VTOC labels. │ ││ │ Go Back Continue │ ││ └──┘ The disks are R/W. I was able to format them with CPFMTXA, and the initial Linux format works. I’ve tried with and without both, with no change in behavior. Virtual machine definition follows: USER DEB1ZL01 1G 1G G COMMAND SET VSWITCH VSWG GRANT USERID COMMAND COUPLE 8200 TO SYSTEM VSWG * IPL CMS PARM AUTOCR MACH XA OPTION APPLMON * CONSOLE 0009 3215 T NICDEF 8200 TYPE QDIO LAN SYSTEM VSWG SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A * LINK MAINT 0190 0190 RR LINK LINUX1 0192 0191 RR LINK LINUX1 0191 0192 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 0391 3390 31283 125 VG0125 MR MDISK 0392 3390 17701 10016 VP0133 MR MDISK 0393 3390 1 10016 VP0136 MR
Re: [manual] booting from USB
Hi all, because of #596633, #590568 and #596628 regarding USB installation where instructions on .iso to use didn't seem to be clear enough i moved the information of the already existing footnote to a paragraph hoping it's easier to understand. Here it goes a new proposal. On 11-09-2010 18:59, Miguel Figueiredo wrote: Hi all, attached a patch and chapter page from the manual about preparing usb memory stick to install debian. I made some changes hoping this can be more clear to follow. Please review it and check if these changes are worth it. Looking to the BTS/installation reports, the USB installation usability worths being discussing as nowadays USB devices are very popular. Squeeze+1? -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org usbboot.diff.gz Description: application/gzip ch04s03.html.gz Description: application/gzip
Bug#596762: installation-reports: installer failed to add winXP to grub2
Package: installation-reports Severity: important Tags: d-i -- Package-specific info: Boot method: cd Image version: http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/iso-cd/debian-testing-i386-netinst.iso Date: Date and time of the install Machine: athlon xp 1800+, 2gb ram, 500gb HDD 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: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] 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:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Problems: 1. At the moment when grub2 was about to be installed, suddenly a question popped up, asking whether I really did not want to install grub2 anywhere and proceed without installing it. My options were: back, yes and no. When I hit back the same question came again, I hit back again, but this question came always again. So I tried no, which brought the same question again and again. At last I gave up and choose yes, which installed grub2 though - to my surprise. 2. Grub2 was installed, but it did not add my winXP partition to the menu! If you need any more logs, or info, feel free to contact me. best regards! -- 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 20100211 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux hugo3 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] [1106:3099] lspci -knn: 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] [1106:b099] lspci -knn: 00:09.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Subsystem: NEC Corporation USB [1033:0035] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:09.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Subsystem: NEC Corporation USB [1033:0035] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:09.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -knn: Subsystem: Device [1838:1074] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:0b.0 Multimedia audio controller [0401]: C-Media Electronics Inc CM8738 [13f6:0111] (rev 10) lspci -knn: Subsystem: C-Media Electronics Inc CM8738 [13f6:0111] lspci -knn: 00:0d.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) lspci -knn: Subsystem: Compex Device [11f6:8139] lspci -knn: Kernel driver in use: 8139too lspci -knn: 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8233 PCI to ISA Bridge [1106:3074] lspci -knn: Subsystem: VIA Technologies, Inc. VT8233 PCI to ISA Bridge [1106:3074] lspci -knn: 00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) lspci -knn: Subsystem: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] lspci -knn: Kernel driver in use: VIA_IDE lspci -knn: 00:11.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 1b) lspci -knn: Subsystem: First International Computer, Inc. Device [0925:1234] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:11.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 1b) lspci -knn: Subsystem: First International Computer, Inc. Device [0925:1234] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:11.4 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 1b) lspci -knn: Subsystem: First International Computer, Inc. Device [0925:1234] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 AR [Radeon 9600] [1002:4152] lspci -knn: Subsystem: Hightech Information System Ltd. Device [17af:2016] lspci -knn: 01:00.1
Bug#590568: iso images
Must be named .iso or .ISO. In the chapter you point from the manual: You can use either a businesscard, a netinst or a full CD image (see Section 4.1, “Official Debian GNU/Linux CD-ROM Sets”). Be sure to select one that fits. Note that the “netboot mini.iso” image is not usable for this purpose. mini.iso is not suitable for this purpose. You tried only the mini.iso? -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- 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/4c8e8ea4.4010...@debianpt.org
Bug#581756: keyboard-configuration: XKBOPTIONS does not properly propagate to xserver-xorg
On Sat, May 15, 2010 at 06:15:06PM +0200, Julien Cristau wrote: Triggering udev from keyboard-configuration doesn't really make sense (it's a layering violation; keyboard-configuration shouldn't need to know what the users for this configuration file are, whether X is installed, etc) Do you think it will be useful if keyboard-configuration provides a /etc/foo.d directory where the interested packages (console-setup, X) can install scripts to reconfigure the keyboard? Anton Zinoviev -- 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/20100913201635.gb21...@debian.lan
Bug#596633: USB install fails
Miles Fidelman wrote: Next, download a Debian netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in .iso. Actually, the instructions AREN'T that clear. The instructions start out with: There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common. For the first installation method you'll need to download an installer image from the |netboot| directory (at the location mentioned in Section 4.2.1, “Where to Find Installation Images” http://d-i.alioth.debian.org/manual/en.i386/ch04s02.html#where-files) and use the “flexible way” explained below to copy the files to the USB stick. The only installer image in the netboot directory is mini.iso It's referring to the kernel and initrd in the netboot/debian-installer/ directory. Ie, http://http.us.debian.org/debian/dists/squeeze/main/installer-i386/current/images/netboot/debian-installer/i386/ -- see shy jo signature.asc Description: Digital signature
Bug#596633: USB install fails
Joey Hess wrote: Miles Fidelman wrote: Next, download a Debian netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in .iso. Actually, the instructions AREN'T that clear. The instructions start out with: There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common. For the first installation method you'll need to download an installer image from the |netboot| directory (at the location mentioned in Section 4.2.1, “Where to Find Installation Images”http://d-i.alioth.debian.org/manual/en.i386/ch04s02.html#where-files) and use the “flexible way” explained below to copy the files to the USB stick. The only installer image in the netboot directory is mini.iso It's referring to the kernel and initrd in the netboot/debian-installer/ directory. Ie, http://http.us.debian.org/debian/dists/squeeze/main/installer-i386/current/images/netboot/debian-installer/i386/ That's just confusing. For that matter, what is a discussion of network booting doing in the section on USB booting in the first place? -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra -- 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/4c8e9734.8090...@meetinghouse.net
Re: [manual] booting from USB
Miguel Figueiredo wrote: Hi all, because of #596633, #590568 and #596628 regarding USB installation where instructions on .iso to use didn't seem to be clear enough i moved the information of the already existing footnote to a paragraph hoping it's easier to understand. As one of the bug reporters, let me add a comment: The proposed change: 4.3.1. First installation method — netboot For the first installation method you'll need to download an installer image from the |netboot| directory (at the location mentioned in Section 4.2.1, “Where to Find Installation Images”) and use the “flexible way” explained below to copy the files to the USB stick. This paragraph creates a lot of confusion - both in its earlier form, and as a separately numbered subsection. The statement download an installer image from the netboot directory conflicts directly with the statement in 4.3.4.2 that the “netboot |mini.iso|” image is not usable for this purpose - as mini.iso is the only image in the netboot directory. (parenthetically: as far as I can tell, there is no discussion, anywhere in the manual, on what mini.iso does or how to use it) Further, It's really not clear why there's any discussion of netbooting in a section on USB booting. TFTP booting has it's own section (4.5). If the intent is to discuss a stage 0 boot from a USB stick, followed by netbooting, then the discussion really needs a few more details as to what specifically needs to be put onto the USB stick, and maybe that belongs in section 4.5., rather than here. Miles Fidelman -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra -- 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/4c8e9672.5060...@meetinghouse.net
Bug#596760: Could not write VTOC labels
On Mon, 13 Sep 2010 16:27:56 -0400 (EDT), Robert Nix wrote: Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-s390/current/images/generic/ The Lenny installer is a bit long in the tooth. Have you tried the Squeeze alpha1 installer? It *should* be able to install Lenny, if that is what you want to do. For example: http://ftp.nl.debian.org/debian/dists/testing/main/installer-s390/current/images/generic/ If that doesn't work, there are some newer images that you can try. For example (from a CMS Ready; prompt): ftp carroll.aset.psu.edu anonymous m...@mydomain cd /pub/linux/distributions/debian cd dists/sid/main/installer-s390/current/images/generic passive ascii get debian.exec binary get initrd.debian INITRD.DEBIAN get kernel.debian KERNEL.DEBIAN get parmfile.debian PARMFILE.DEBIAN close quit PIPE PARMFILE DEBIAN A|FBLOCK 80 00| PARMFILE DEBIAN1 A F ERASE PARMFILE DEBIAN A RENAME PARMFILE DEBIAN1 A = DEBIAN = PIPE INITRD DEBIAN A|FBLOCK 80 00| INITRD DEBIAN1 A F ERASE INITRD DEBIAN A RENAME INITRD DEBIAN1 A = DEBIAN = PIPE KERNEL DEBIAN A|FBLOCK 80 00| KERNEL DEBIAN1 A F ERASE KERNEL DEBIAN A RENAME KERNEL DEBIAN1 A = DEBIAN = DEBIAN Machine: IBM Z9 2094 2IFL z/VM Version 5 Release 3.0, service level 0702 (64-bit) Generated at 10/31/07 09:12:13 CDT Your release of z/VM is getting a bit long in the tooth too! ;-) And service level 0702 is more than three years out of date. ;-) Have you checked for PTFs that may need to be applied? Virtual machine definition follows: ... MDISK 0391 3390 31283 125 VG0125 MR MDISK 0392 3390 17701 10016 VP0133 MR MDISK 0393 3390 1 10016 VP0136 MR Are you sure that's right? What kind of DASD do you have? I normally use 3390-3 volumes, but even a 3390-9 stops at 10017 cylinders. You're going past 31000 cylinders. Can you use the CMS FORMAT command on these minidisks successfully? -- .''`. Stephen Powell : :' : `. `'` `- -- 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/1650090882.84595.1284413902502.javamail.r...@md01.wow.synacor.com
using isohybrid for usb bootable isos
I've done some investigation of using isohybrid on an iso image (d-i alpha1 i386 netinst) to allow it to be booted from USB stick. Basically, postprocess the image with isohybrid, and write it direct to the usb stick. On the single machine I tried it on, that booted ok without any tweaking of isohybrid options. So I think this would be a useful thing for debian-cd to do. I assume it would probably conflict with eg, the boot sector magic used for multiarch isos. If it were only done for i386/amd64 isos, that would be enough to allow bypassing the complicated process to use the d-i hd-media images on usb sticks. Does that make sense from a debian-cd point of view? From the d-i side, cdrom-detect needs to be able to mount the iso when booted from usb stick. There is a cdrom-detect/try-usb that already enables that, but it's not on by default. So far, only live-installer has needed it. It should be very safe to move into the default codepath. The second problem is that apt will try, and fail, to mount the CD itself. apt-setup removed the apt.conf.d/00NoMountCDROM file. Basically, it would need to somehow detect that the CD is on a USB stick, and avoid doing that. It currently looks for /hd-media/ existing, which I made as a workaround. Just checking that the cdrom is mounted from /dev/sd?1 might do, or cdrom-detect could set a flag when it found it on a usb device partition. After working around those 2 problems, d-i successfully installed! But, another issue is that the user needs to be able to drop firmware onto the stick so that d-i can find it. Since isohybrid creates a partition table, after writing the iso to the stick, the user can replug it and see a first partition that is the iso image (so read-only). To add firmware, they would have to add a second partition, which is harder than the current process for usb sticks. So ideally, debian-cd would add a small second partition to the iso file's partition table, and tack on a FAT filesystem. This could probably be done by running fdisk on the iso file after isohybrid. d-i could also run isohybrid when generating the mini.iso and eliminate the need for very complex manual setup of a netboot usb stick. Firmware loading problems also apply there. BTW, I don't think the hd-media images should be removed, they do allow for use cases beyond simply installing from a USB stick. - Forwarded message from Tanguy Ortolo tanguy+deb...@ortolo.eu - Date: Thu, 9 Sep 2010 12:43:53 +0200 From: Tanguy Ortolo tanguy+deb...@ortolo.eu To: debian-boot@lists.debian.org Subject: Complicated installation from USB Reply-To: debian-boot@lists.debian.org, Tanguy Ortolo tanguy+deb...@ortolo.eu User-Agent: Mutt/1.5.18 (2008-05-17) Hello, Debian has been installable from USB (or from any non-optical non-floppy mass storage device, to be exact, but I shall use the term “USB stick” for convenience) since some time. Preparing installation optical disks or floppies is, or used to be easy, and involves two operations, depending on the case: wget cd.iso wodim dev=/dev/cdrom cd.iso wget floppy.img dd if=floppy.img of=/dev/floppy However, preparing an USB stick is not really easy: wget hd-media.img wget cd.iso dd if=hd-media.img of=/dev/stick mount /dev/stick /mnt cp cd.iso /mnt umount /mnt The installation manual explains that in a non-straightforward way, describing two methods, and giving only hints to find where to download the two needed images. In addition, this procedure depends on *nix tools, and is thus inapplicable for many user that start installing Debian from a foreign system, which is a common case. Because of this complication, I see many beginners failing at preparing USB images, if not failing to install Debian at all because they do not have an optical drive. Could we consider providing ready-to-use hd-media images? Something that would only need to be downloaded an written to a USB stick, as we do for optical media? I see two ways to implement that: * doing the copy of the CD image on the hd-media filesystem before making it available as an image; * using the recent hybrid boot feature of SYSLINUX, that allow to build single images that are bootable either as El Torito optical media or as MBR on-optical media, if applicable to the Debian installer. If there are specific reasons not to provide ready-to-use, but only pieces of hd-media images, as we currently do, these reasons might be worth being documented in the installation manual with a note such as: “Note: this procedure is not as easy as the CD one, because [blah].” That would avoid further messages such as this very one. :-) Cheers, and thanks for the great piece of software that the Debian installed is, by the way, to support so many architectures and media types. :-) -- ,--. : /` ) Tanguy Ortolo | `-'Debian maintainer \_ - End forwarded message - -- see shy jo signature.asc Description: Digital signature
Re: Status of some daily D-I builds
Christian PERRIER wrote: On the other hand, I think that other daily builds done in Joey Hess' home are very safe. Obviously, Joey has proven over years how reliable he can be and I don't see urgency to change this. Aside from not being in the building where that box is all the time, and it not coming back up automatically after power failures, and little issues like that. I'd prefer if armel builds were moved to the buildds. -- see shy jo signature.asc Description: Digital signature
Re: using isohybrid for usb bootable isos
Attached patch stack handles everything on the d-i side, except firmware (see next post). It makes the mini.iso hybrid and updates the manual to document writing it to a USB stick, instead of its prior hand-waving about assembling a netboot USB stick manually. I've tested the mini.iso boots (from USB and as a CD), but nothing else. -- see shy jo From 2a4f550612a16a1911284a918f32630e275bef31 Mon Sep 17 00:00:00 2001 From: Joey Hess j...@kitenet.net Date: Mon, 13 Sep 2010 19:57:09 -0400 Subject: [PATCH 1/5] Run isohybrid on i386 and amd64 miniiso, which allows it to be written directly to and booted from a USB stick. --- installer/build/config/x86.cfg |2 ++ installer/debian/changelog |7 +++ installer/debian/control |6 +++--- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/installer/build/config/x86.cfg b/installer/build/config/x86.cfg index e98467d..4a0a005 100644 --- a/installer/build/config/x86.cfg +++ b/installer/build/config/x86.cfg @@ -278,6 +278,8 @@ arch_miniiso: x86_syslinux genisoimage -r -J -b isolinux.bin -c boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -o $(TEMP_MINIISO) $(TEMP_CD_TREE) + + isohybrid $(TEMP_MINIISO) # Netboot files .PHONY: arch_netboot_dir diff --git a/installer/debian/changelog b/installer/debian/changelog index d3820df..2e67006 100644 --- a/installer/debian/changelog +++ b/installer/debian/changelog @@ -1,3 +1,10 @@ +debian-installer (20100913) UNRELEASED; urgency=low + + * Run isohybrid on i386 and amd64 miniiso, which allows it to be written +directly to and booted from a USB stick. + + -- Joey Hess jo...@debian.org Mon, 13 Sep 2010 19:56:39 -0400 + debian-installer (20100912) unstable; urgency=low * Skip last translation changes for rescue and debian-installer- diff --git a/installer/debian/control b/installer/debian/control index 886120b..9e9f20d 100644 --- a/installer/debian/control +++ b/installer/debian/control @@ -7,7 +7,7 @@ Standards-Version: 3.8.3 Vcs-Svn: svn://svn.debian.org/d-i/trunk/installer Build-Conflicts: libnewt-pic [mipsel] # NOTE: Do not edit the next line by hand. See comment below. -Build-Depends: debhelper (= 7.0.0), apt, apt-utils, gnupg, debian-archive-keyring (= 2006.11.22), dctrl-tools, wget, bc, debiandoc-sgml, xsltproc, docbook-xml, docbook-xsl, libbogl-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], glibc-pic, libslang2-pic (= 2.0.6-4), libnewt-pic (= 0.52.2-11.3) [!mipsel], libnewt-dev (= 0.52.2-11.3) [mipsel], libgcc1 [i386 amd64], cramfsprogs [powerpc ia64 mips mipsel armeb armel], genext2fs (= 1.3-7.1), e2fsprogs, mklibs (= 0.1.25), genisoimage [!s390 !s390x], genromfs [sparc sparc64], hfsutils [powerpc], dosfstools [i386 ia64 m68k amd64], cpio, devio [armeb armel], slugimage (= 0.10+r58-6) [armeb armel], dns323-firmware-tools [armel], uboot-mkimage [armel], syslinux (= 2:3.63+dfsg-2) [i386 amd64], palo [hppa], elilo [ia64], yaboot [powerpc], aboot (= 0.9b-2) [alpha], silo [sparc], sparc-utils [sparc sparc64], genisovh [mips], tip22 [mips], colo [mipsel], sibyl [mips mipsel], atari-bootstrap [m68k], vmelilo [m68k], m68k-vme-tftplilo [m68k], amiboot [m68k], emile [m68k], emile-bootblocks [m68k], apex-nslu2 [armeb armel], tofrodos [i386 amd64 kfreebsd-i386 kfreebsd-amd64], mtools [i386 ia64 m68k amd64 kfreebsd-i386 kfreebsd-amd64 hurd-i386], module-init-tools [i386 armeb armel amd64 alpha hppa ia64 m68k mips mipsel powerpc s390 sh4 sparc sparc64], bf-utf-source [!s390 !s390x], mkvmlinuz [powerpc], openssl [armel], win32-loader [i386 amd64 kfreebsd-i386 kfreebsd-amd64 hurd-i386], makefs [kfreebsd-i386 kfreebsd-amd64], grub-pc (= 1.98~20100101-1) [kfreebsd-i386 kfreebsd-amd64 hurd-i386], xorriso [kfreebsd-i386 kfreebsd-amd64 hurd-i386], debian-ports-archive-keyring [sh4 sparc64] +Build-Depends: debhelper (= 7.0.0), apt, apt-utils, gnupg, debian-archive-keyring (= 2006.11.22), dctrl-tools, wget, bc, debiandoc-sgml, xsltproc, docbook-xml, docbook-xsl, libbogl-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], glibc-pic, libslang2-pic (= 2.0.6-4), libnewt-pic (= 0.52.2-11.3) [!mipsel], libnewt-dev (= 0.52.2-11.3) [mipsel], libgcc1 [i386 amd64], cramfsprogs [powerpc ia64 mips mipsel armeb armel], genext2fs (= 1.3-7.1), e2fsprogs, mklibs (= 0.1.25), genisoimage [!s390 !s390x], genromfs [sparc sparc64], hfsutils [powerpc], dosfstools [i386 ia64 m68k amd64], cpio, devio [armeb armel], slugimage (= 0.10+r58-6) [armeb armel], dns323-firmware-tools [armel], uboot-mkimage [armel], syslinux (= 2:4.02) [i386 amd64], palo [hppa], elilo [ia64], yaboot [powerpc], aboot (= 0.9b-2) [alpha], silo [sparc], sparc-utils [sparc sparc64], genisovh [mips], tip22 [mips], colo [mipsel], sibyl [mips mipsel], atari-bootstrap [m68k], vmelilo [m68k], m68k-vme-tftplilo [m68k], amiboot [m68k], emile [m68k], emile-bootblocks [m68k], apex-nslu2 [armeb armel], tofrodos [i386 amd64 kfreebsd-i386 kfreebsd-amd64], mtools [i386 ia64 m68k amd64 kfreebsd-i386 kfreebsd-amd64 hurd-i386], module
Re: using isohybrid for usb bootable isos
Joey Hess wrote: So ideally, debian-cd would add a small second partition to the iso file's partition table, and tack on a FAT filesystem. This could probably be done by running fdisk on the iso file after isohybrid. I've attached a patch with a script, which I am checking into d-i for now, that does that. This would add 6 to 7 mb to iso images it's used on, I don't know how Steve feels about that. :) -- see shy jo #!/bin/sh # Given an iso image, runs isohybrid on it to allow it to be booted from # USB stick as well as CD. Then it adds a small second FAT partition, which # the user can use to provide firmware files to the installer on the same # USB stick. # This needs to be big enough to hold the uncompressed firmware.tar.gz # file. Currently that is 4.4M; add a few more to grow. firmware_volume_size_M=6 # max size 11 chars: --- firmware_volume_name=Firmware iso=$1 if [ -z $iso ]; then echo usage: $0 iso 2 exit 1 fi set -e isohybrid $iso # Make the firmware volume. tmpdir=$(mktemp -d) firmware_volume_file=$tmpdir/fat mkfs.msdos -n $firmware_volume_name -C $firmware_volume_file \ $(expr $firmware_volume_size_M \* 1024) # Combine images. # XXX This wastes some space because isohybrid pads the iso to one # megabyte. Could reuse that padding for the start of the firmware volume. cat $firmware_volume_file $iso rm -r $tmpdir # Now adjust the partition table of the hybrid iso. # It has a first partition which is the iso; add a second partition for the # firmware volume. ( # Go into extended menu and set cylinders to 32. # This is the same number of cylinders (currently) used by isohybrid. echo x echo c echo 32 echo r # Make new partition #2 echo n echo p echo 2 echo echo +$firmware_volume_size_MM # Pedantically, set partition type to 1: FAT 16 echo t echo 2 echo 1 # Done! echo w ) | fdisk $iso From 9e4ab44eb5d43353769350872803cae71553eae5 Mon Sep 17 00:00:00 2001 From: Joey Hess j...@kitenet.net Date: Mon, 13 Sep 2010 22:07:36 -0400 Subject: [PATCH 1/2] create geniso_hybrid_plus_firware_partition script This script makes a hybrid iso image with a second partition for firmware. --- installer/build/config/x86.cfg |2 +- .../util/geniso_hybrid_plus_firware_partition | 62 2 files changed, 63 insertions(+), 1 deletions(-) create mode 100755 installer/build/util/geniso_hybrid_plus_firware_partition diff --git a/installer/build/config/x86.cfg b/installer/build/config/x86.cfg index 4a0a005..e9ef577 100644 --- a/installer/build/config/x86.cfg +++ b/installer/build/config/x86.cfg @@ -279,7 +279,7 @@ arch_miniiso: x86_syslinux -no-emul-boot -boot-load-size 4 -boot-info-table \ -o $(TEMP_MINIISO) $(TEMP_CD_TREE) - isohybrid $(TEMP_MINIISO) + geniso_hybrid_plus_firware_partition $(TEMP_MINIISO) # Netboot files .PHONY: arch_netboot_dir diff --git a/installer/build/util/geniso_hybrid_plus_firware_partition b/installer/build/util/geniso_hybrid_plus_firware_partition new file mode 100755 index 000..52cccf1 --- /dev/null +++ b/installer/build/util/geniso_hybrid_plus_firware_partition @@ -0,0 +1,62 @@ +#!/bin/sh +# Given an iso image, runs isohybrid on it to allow it to be booted from +# USB stick as well as CD. Then it adds a small second FAT partition, which +# the user can use to provide firmware files to the installer on the same +# USB stick. + +# This needs to be big enough to hold the uncompressed firmware.tar.gz +# file. Currently that is 4.4M; add a few more to grow. +firmware_volume_size_M=6 +# max size 11 chars: --- +firmware_volume_name=Firmware + +iso=$1 + +if [ -z $iso ]; then + echo usage: $0 iso 2 + exit 1 +fi + +set -e + +isohybrid $iso + +# Make the firmware volume. +tmpdir=$(mktemp -d) +firmware_volume_file=$tmpdir/fat +mkfs.msdos -n $firmware_volume_name -C $firmware_volume_file \ + $(expr $firmware_volume_size_M \* 1024) + +# Combine images. +# XXX This wastes some space because isohybrid pads the iso to one +# megabyte. Could reuse that padding for the start of the firmware volume. +cat $firmware_volume_file $iso +rm -r $tmpdir + +# Now adjust the partition table of the hybrid iso. +# It has a first partition which is the iso; add a second partition for the +# firmware volume. +( + +# Go into extended menu and set cylinders to 32. +# This is the same number of cylinders (currently) used by isohybrid. +echo x +echo c +echo 32 +echo r + +# Make new partition #2 +echo n +echo p +echo 2 +echo +echo +$firmware_volume_size_MM + +# Pedantically, set partition type to 1: FAT 16 +echo t +echo 2 +echo 1 + +# Done! +echo w +) | fdisk $iso -- 1.7.1 From cff9c48f8e041e317186e91cce17d86181fd80a6 Mon Sep 17 00:00:00 2001 From: Joey Hess j...@kitenet.net Date: Mon, 13 Sep 2010 22:32:40 -0400 Subject: [PATCH 2/2] add documentation for piggybacking formware onto hybrid mini.iso usb stick --- manual/en/install-methods/boot-usb-files.xml | 17 +++--
Re: using isohybrid for usb bootable isos
Joey Hess wrote: I've attached a patch with a script, which I am checking into d-i for now, that does that. Note that currently mountmedia and check-missing-firmware only find firmware on this second, special partition, if it's in udeb or deb files. When looking for loose firmware, it mounts the first partition, the iso, and gives up after not finding it there. mountmedia would need to be made somehow more intelligent about finding specific files to fix that. -- see shy jo signature.asc Description: Digital signature
Bug#596786: installation-reports: installer also couldn't find broadcom card
Package: installation-reports Severity: important Tags: d-i eth0 is intel board eth1 is broadcom card installer 1st asks for firmware (e100/d102e_ucode.bin) - download from debian.org per install instructions, put on usb stick, insert - seems to load (takes several minutes) then, selecting eth1 leads to failure to obtain DHCP address selecting eth0 works -- Package-specific info: Boot method: CD Image version: squeeze alpha1 Date: Date and time of the install Machine: custom tower 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: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] 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:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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 20100211 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux new-host-2 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host [1039:0661] (rev 11) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] [1039:0964] (rev 36) lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: SIS_IDE lspci -knn: 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:7002] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 90) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: sis900 lspci -knn: 00:05.0 IDE interface [0101]: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] [1039:0180] (rev 01) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: sata_sis lspci -knn: 00:09.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 10) lspci -knn: Subsystem: Intel Corporation Device [8086:0070] lspci -knn: Kernel driver in use: e100 lspci -knn: 01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lsmod: Module Size Used by lsmod: ufs59880 0 lsmod: qnx47524 0 lsmod: ntfs 173224 0 lsmod: dm_mod 49216 5 lsmod: raid1 18048 4 lsmod: md_mod 76204 5 raid1 lsmod: xfs
Bug#596787: installation-reports: grub legacy writes incorrect menu.lst when disks are RAIDed
Package: installation-reports Severity: important Tags: d-i system has two mirrored disks, /dev/md0 is boot, /dev/md2 is root selecting grub-legacy, and specifying either /dev/hda or (hd0) for installation results in a menu.lst file with the line groot=(md0) and all of the boot sections starting with root (md0) at boot time, grub throws an error - it (corretly) doesn't recognize md0 as a proper construction editing menu.lst to read groot=(hd0,0) and running update-grub leads to a correct and functional menu.lst -- Package-specific info: Boot method: CD Image version: squeeze alpha1 Date: Date and time of the install Machine: custom tower 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: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] 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:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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 20100211 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux new-host-2 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host [1039:0661] (rev 11) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] [1039:0964] (rev 36) lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: SIS_IDE lspci -knn: 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:7002] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 90) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: sis900 lspci -knn: 00:05.0 IDE interface [0101]: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] [1039:0180] (rev 01) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lspci -knn: Kernel driver in use: sata_sis lspci -knn: 00:09.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 10) lspci -knn: Subsystem: Intel Corporation Device [8086:0070] lspci -knn: Kernel driver in use: e100 lspci -knn: 01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0c56] lsmod: Module Size Used by lsmod: ufs59880 0 lsmod: qnx47524 0 lsmod: ntfs
