Bug#458663: Missing support for data.tar.bz2-based debs
On Jan 2, 2008, at 12:03 PM, Otavio Salvador wrote: On Wed, Jan 02, 2008 at 12:38:51PM -0200, Otavio Salvador wrote: Personally, I'd like to know what is the increase on space and memory for adding bzcat on busybox-udeb. However, as said in another mail, I see no point to support different set of features on installed and d-i environments (from debootstrap POV). It could actually improve the space situation in the installer if it allowed some packages to be compressed smaller than their present size. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458663: Missing support for data.tar.bz2-based debs
On Jan 2, 2008, at 9:47 PM, Colin Watson wrote: On Wed, Jan 02, 2008 at 06:38:37PM -0500, Rick Thomas wrote: On Jan 2, 2008, at 12:03 PM, Otavio Salvador wrote: On Wed, Jan 02, 2008 at 12:38:51PM -0200, Otavio Salvador wrote: Personally, I'd like to know what is the increase on space and memory for adding bzcat on busybox-udeb. However, as said in another mail, I see no point to support different set of features on installed and d-i environments (from debootstrap POV). It could actually improve the space situation in the installer if it allowed some packages to be compressed smaller than their present size. The worst (and most relevant here) constraint is on initrd size, and that is unaffected by .deb size. Good point. Along those lines, another constraint that's important is the RAM footprint of the installer -- for small memory machines (same audience as for small initrd size). How much does adding bzcat to busybox increase it's RAM footprint when executing? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
What's happening with the 3.1r7 install iso?
I hate to be a bore on this subject, but the Sarge 3.1r7 iso's still aren't available, as far as I can tell. And no word from anyone as to what the hold up is. Can anybody enlighten me? The 4.0r2 iso's are up now. Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463765: debian-installer: Installer offers to install grub bootloader on PowerPC. Why?
Package: debian-installer Severity: normal Using this businesscard install disk: http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/ Daily build #2 for powerpc, using installer build from sid These images will install the testing version of Debian, currently Lenny. See the top-level daily directory for more information about the daily builds. This build finished at Fri Feb 1 21:27:24 UTC 2008. Name Last modified Size Parent Directory- MD5SUMS01-Feb-2008 22:27 143 SHA1SUMS 01-Feb-2008 22:27 159 debian-testing-powerpc-businesscard.iso01-Feb-2008 22:25 59M debian-testing-powerpc-businesscard.iso.zsync 01-Feb-2008 22:27 207K debian-testing-powerpc-netinst.iso 01-Feb-2008 22:27 181M debian-testing-powerpc-netinst.iso.zsync 01-Feb-2008 22:27 316K Apache/2.2.6 (Unix) Server at cdimage.debian.org Port 80 It was a nominal installation until it came time to write a boot loader. It presented me with a top-level installer menu, with Install GRUB boot loader hilighted. Since GRUB is for x86, not PowerPC, this was odd. I hit enter and it immediately returned to the same menu with GRUB still hilighted, apparently having done nothing useful. I then skipped the GRUB menu item and told it to install YABOOT (the next item on the menu), and all proceeded as expected from there. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-3-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash syslog.gz Description: GNU Zip compressed data
Bug#463765: debian-installer: Installer offers to install grub bootloader on PowerPC. Why?
On Feb 2, 2008, at 11:39 PM, Nick Schmalenberger wrote: Grub does exist for powerpc, grub2 http://packages.qa.debian.org/g/grub2.html but as that page says it has an unsatisfiable dependency right now for powerpc so its broken. Has there been any progress on this since: http://lists.debian.org/debian-powerpc/2007/10/msg00057.html ? I would still like to use it on my powerpcs. Thanks very much. Nick Schmalenberger It may have *meant* GRUB2, but what it *said* was GRUB. In any case, it doesn't work, and presents an impediment to an otherwise nominal installation process. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Status on arm, mips and mipsel
On Feb 10, 2008, at 2:39 PM, Frans Pop wrote: On Sunday 10 February 2008, Martin Michlmayr wrote: - It seems that d-i no longer accepts the hostname given by DHCP but simply uses debian. Has anyone noticed this? No. Works perfectly here. netcfg shows the default obtained from dhcp and after netcfg /etc/ hostname also contains the correct value. Martin, Does your DHCP server provide a DNS server? Without a DNS server the D-I wouldn't be able to deduce a host name... Just a thought, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#276826: PowerPC floppy root.img sizes
Package: debian-installer Begin forwarded message: From: Sven Luther [EMAIL PROTECTED] Date: Sat Oct 16, 2004 05:12:16 AM US/Eastern To: Rick Thomas [EMAIL PROTECTED] Cc: Duane Cottle [EMAIL PROTECTED], debian- [EMAIL PROTECTED], [EMAIL PROTECTED], Sven Luther [EMAIL PROTECTED] Subject: Re: floppy root.img sizes On Fri, Oct 15, 2004 at 01:17:45PM -0400, Rick Thomas wrote: On Oct 15, 2004, at 11:16 AM, Duane Cottle wrote: Hi all, Sorry if this is the wrong list for this... I have been testing daily sarge floppy install images from http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/ for a few weeks on OldWorld Macs. That is, until October 8. Since then, root.img seems to have swollen to a size bigger than I can dd onto a floppy. What's puzzling to me is that the sizes reported by any tool I use to download the images is less than the ls -l report by around 4.2KB. Example: in gFTP today's root.img shows 1468006 on the server and 1509557 on my hd. Damn it, the root image has again grown out of proportion. Please fill a bug report against debian-installer about this. I will try to have a look, but Joey Hess and maybe Colin Watson would be better placed to fix this, especially as i will probably not have access to my devel box until i put some order in this room. One month of travelling, and my computer room now is completely crowded. Oh well. Hi Duane, I'm forwarding this to Sven Luther, who generates the floppy images in question. I'm also forwarding this to the debian-boot list, where there are other folks besides Sven who may be able to help. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge on OldWorld Mac - No root device
On Monday, September 27, 2004, at 04:40 PM, Joey Hess wrote: Rick Thomas wrote: I've submitted several bug reports on this topic. The developers know about it, and may fix it sometime. It's not as easy to fix as it sounds, because the mesh controller is not on the regular PCI bus, so the normal hardware discovery programs never get a chance to see it. As far as I can tell, it's fixed in an as-yet unreleased version of hw-detect: - mac-io bus detection improvements: + Detect mesh SCSI controller (closes: #269655, #271419). + Detect mace Ethernet controller. + Detect mac53c94 SCSI controller. + Detect therm_adt746x and therm_windtunnel fan controllers, although only post-reboot for now since those modules aren't in linux-kernel-di-powerpc-*. + Cope with /proc/device-tree/aliases/mac-io pointing to a symlink. Thanks Joey! When can we expect to see it in our friendly neighborhood daily CD or boot-floppy? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge on OldWorld Mac - No root device
I'd be perfectly happy (personally) if it only worked in 2.6. However, I believe that Sarge d-i has, as one of it's goals, to support both 2.4 and 2.6. Does anybody else on the list know for sure? Rick On Tuesday, September 28, 2004, at 06:21 AM, Christoph Hellwig wrote: On Mon, Sep 27, 2004 at 04:40:16PM -0400, Joey Hess wrote: Rick Thomas wrote: I've submitted several bug reports on this topic. The developers know about it, and may fix it sometime. It's not as easy to fix as it sounds, because the mesh controller is not on the regular PCI bus, so the normal hardware discovery programs never get a chance to see it. As far as I can tell, it's fixed in an as-yet unreleased version of hw-detect: - mac-io bus detection improvements: + Detect mesh SCSI controller (closes: #269655, #271419). + Detect mace Ethernet controller. + Detect mac53c94 SCSI controller. + Detect therm_adt746x and therm_windtunnel fan controllers, although only post-reboot for now since those modules aren't in linux-kernel-di-powerpc-*. + Cope with /proc/device-tree/aliases/mac-io pointing to a symlink. Note that there's a patch on lkml that adds device tables ala pci,usb,etc.. for macio. But that's probably useless for you as you'd want to support 2.4 aswell? I'd be perfectly happy (personally) if it only worked in 2.6. However, I believe that Sarge d-i has, as one of it's goals, to support both 2.4 and 2.6 on PowerPC architecture. Does anybody else on the list know for sure? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: oldworld-ppc: quik, initrd, bootx manual (was Re: timeline for next month and next two releases)
Holger Levsen wrote: conclusions --- i think i should file the following bug reports, i will do this tonite if there are no objections: snip - document the use of bootx in the manual (with link to mac os 7.5 installation disks) Remember that MacOS 7.5 doesn't work on all models of OldWorld Mac. Folks should check the matrix on this Apple web page: http://docs.info.apple.com/article.html?artnum=8970 to see if their hardware can run MacOS 7.5, before they invest a lot of effort in downloading 19 floppy image files and burning a bunch of floppies they can't use. If you want to lobby Apple to release selected later versions of MacOS for free (as in beer) you can sign the petition at: http://www.PetitionOnline.com/macos8x/petition.html snip favorite quote from http://www.penguinppc.org/mac/#bootloaders Old World Macs must use either BootX (which requires a bootable Mac OS installation) or quik (which must deal with the buggy firmware of that era). Sadly true! regards, Holger Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: oldworld-ppc: quik, initrd, bootx manual (was Re: timeline for next month and next two releases)
On Tuesday, September 28, 2004, at 07:19 PM, Holger Levsen wrote: Hi, Remember that MacOS 7.5 doesn't work on all models of OldWorld Mac. Folks should check the matrix on this Apple web page: http://docs.info.apple.com/article.html?artnum=8970 Oh no! ;-) But maybe that's got information for the manual. to see if their hardware can run MacOS 7.5, before they invest a lot of effort in downloading 19 floppy image files and burning a bunch of floppies they can't use. Can you please provide the URL where the unlucky can download the floppy images ?! In my opinion this should be included in the manual as well. Glad to help! http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/ Macintosh/System/Older_System/System_7.5_Version_7.5.3/ Be careful of URL-wrap-syndrome! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Saturday, September 25, 2004, at 04:49 PM, Colin Watson wrote: After my changes, there's *loads* of room left for things. We were just being inefficient, that's all. Well, I just took a look at the latest floppy images. It looks like everything that's there fits with room to spare -- in some cases not a lot of room, but enough to allow for inevitable growth between now and the expected release date, which is all that matters. Would you care to share the secret? What did you do to create all that free space? However... There is one important thing missing from the boot disks. Specifically, the System file is zero length. This is true of both boot and ofonlyboot for both 2.4 and 2.6. It won't boot that way. Enjoy! Rick PS -- In case it matters, here's where I got the images... == Index of /~luther/d-i/images/2004-09-28/powerpc/floppy NameLast modified Size Description [DIR] Parent Directory21-Sep-2004 01:48 - [ ] asian-root.img 28-Sep-2004 01:22 1.3M [ ] boot.img28-Sep-2004 01:22 1.4M [ ] cd-drivers.img 28-Sep-2004 01:22 1.3M [ ] net-drivers.img 28-Sep-2004 01:22 1.3M [ ] ofonlyboot.img 28-Sep-2004 01:22 1.4M [ ] root.img28-Sep-2004 01:22 1.4M _ Apache/1.3.26 Server at people.debian.org Port 80 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Wednesday, September 29, 2004, at 01:30 PM, Holger Levsen wrote: Hi, However... There is one important thing missing from the boot disks. Specifically, the System file is zero length. This is true of both boot and ofonlyboot for both 2.4 and 2.6. It won't boot that way. Arg, again. I have to checkup and see what is missing in the build process, but i will not be able to do so until friday. I just successfully booted the kernel from http://people.debian.org/~luther/d- i/images/2004-09-29/powerpc/floppy-2.4/boot.img and was asked for the root floppy. (on a power mac 4400/200) Hmmm... You learn something new every day! I think I've just discovered a major difference between the hfs implementation in 2.4 and that in 2.6. When one mounts an hfs filesystem under 2.4, there are a bunch of pseudo-directories with names beginning with a . that give you access to the finder info and the resource forks of all the files. This feature is not there in 2.6. (Or else I need to RTFM -- can somebody point me to the right FM?) Thus, running a 2.6.8 kernel, mounting the boot.img file as an hfs filesystem make it appear that the finder is zero length! In reality, only it's text fork (If that's the right word) is zero length -- all the good stuff is in the resource fork, which doesn't show up. So, I owe Sven an apology! As Holger found out, the boot floppy is perfectly functional. Now, is the loss under 2.6 of the HFS .finderinfo and .resource pseudo-directories a bug, or a feature? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#273986: Quasi-successful Installation - Sarge netinst rc1 on Beige G3
On Wednesday, September 29, 2004, at 02:56 AM, Duane Cottle wrote:
Partition notes:
As I was playing around in the partitioner, I decided to delete the
32.2K partion #1 on the scsi drive called Apple. After the partitions
were displayed once again on the screen, I noticed a 32.2K hole on the
IDE Master disk at partition #1! It's a new dance I'm learning called
the Mac Twist. I'm not experienced with the OF, but maybe that's really
a space on the /AAPL/ROM??
Also, I fooled around and selected the entire scsi disk and followed
the installer to delete all the partions. Guess what didn't go away!
That 32.2K _'taint_meat_ pinch!
You've stumbled on an interesting feature of the Apple Macintosh
disk partition scheme -- as implemented in MacOS{789}, MacOS-X, and
the Linux partitioning tools mac-fdisk and it's cousin pdisk.
Specifically, there *must* always be a partition 1 on any Macintosh
physical disk. That's where the partition table lives. The
lowest-level bootstrap firmware expects it to be there, and won't
work without it! (Floppy disks and ISO9660 CD-roms are
interesting exceptions...).
Yes, there are some interesting philosophical questions surrounding
the partition table being inside a partition. Ignore them! You'll
only get a headache.
The other Macintosh partitions (2-5 on one of my disks -- YMMV) are
also needed if you ever intend to boot MacOS9 off of the disk.
They hold some low-level driver software needed in the boot
process. I've heard someone say that MacOS-X doesn't need these
driver partitions. I don't know for sure.
Hope this helps!
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#273986: Quasi-successful Installation - Sarge netinst rc1 on Beige G3
On Thursday, September 30, 2004, at 12:11 AM, Duane Cottle wrote: Hi Rick, Sure does. I spent five hours reading your posts since March today. I take that as the highest of compliments. (-8) Thank you, sir! It's already saved me a lot of trouble testing this stuff. Been working with boot floppies this evening, as you have. I just completed a successful install from Sven's daily 2.6 disks. There were some really different/welcome phenomena. I'm sure you'll see it, if you haven't already. Do you mean the 2.6 floppy disks? I haven't been able to get them to work. The 2.6 boot floppy (the ofonlyboot floppy as well) starts reading OK but ends with the screen colors inverted and hangs. It never ejects the boot floppy or switches to the text screen. Do you know how to get around this? The 2.4 floppy set works fairly well, though there's still one show-stopper problem. It can't seem to find my IDE disk. I'll be submitting an install report on my experiences soon. If you're talking about the CDs (businesscard or netinst) I agree with you. 2.6 is very nice. A CD-based 2.6 install from BootX is, for an experienced user, almost completely trouble-free. That said, there are some serious usability issues for a novice user (Fortunately, these issues are largely shared with the x86 version -- so I have confidence that they will be fixed before release.) and the PowerPC sections of the manual need to be completely re-written for Sarge. The current one has lots of Woody-isms and and not a few x86-isms that need to be weeded out and re-written for Sarge and PowerPC/Mac. Do you know how I could test the netboot images. I'm not there yet. Do they allow mounting a source nfs export? I've been inching my way there because I'll eventually load up all my cluster nodes in this fashion. I haven't tried netboot for Linux yet. (I assume you are talking about telling Open Firmware to get its kernel and initrd via tftp from the net, then getting the rest via NFS -- or something like that.) I've done it for Solaris on Sparc hardware, but never for Linux. My aversion to Apple's buggy Open Firmware implementations is showing, I guess. If I had to make netboot work, I think I'd try it once on an x86 box first, just to see how it's supposed to work for debian. You'll probably want to get some experience with the mkinitrd(8) command as well. I expect you'll have to hand-craft your own initial ram-disk images. The current floppy and/or CD-rom initrd images won't be much help for a netboot. I guess I'm not much help there. You should probably ask the various debian mailing-lists if anyone has done a netboot install successfully and can help walk you thru the steps. You should also check the Apple Tech-info library knowledge-base for anything on net-booting Macs. And there's always google and his cousins, as a last resort. Let me know what you find out! There's probably a section to be written for the new installation manual in the experience. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#274516: [powerpc] [pre-rc2] [floppy] oldworld ppc 7300 failure
On Saturday, October 2, 2004, at 08:24 AM, Fabian Linzberger wrote: detailed diagnosis: floppy/boot.img: bootloader seems to work fine, soon as the penguin logo and the linux bootmessages should come up, display is completely garbled. floppy/ofonlyboot.img: bootloader seems to work fine, penguin logo comes up in green colors, no further output. floppy-2.4/boot.img, floppy-2.4/ofonlyboot.img nice little penguin/monitor logo comes up, but is soon crossed out in red... Hi! The crossed out in red you are getting for the 2.4 boot floppies (floppy-2.4/*boot.img) usually means that the boot loader got some kind of error when reading the kernel image off the floppy. Your experience with the 2.6 boot floppies (floppy/*boot.img) is consistent with my own results on a beige G3 mini-tower and a powerMac 6500/225. However, I am able to get the 2.4 boot floppy (but not the 2.4 ofonlyboot floppy) to load and run its kernel on both of my test machines. So I suspect you are running up against I/O errors in reading the boot floppy. This is a common problem. The firmware floppy driver is not very tolerant of minor errors that would be recoverable with a more sophisticated driver. Two suggestions: 1) Invest in a floppy drive cleaning kit. Don't be afraid to clean your drive a couple of times if it's been unused for a long time. There can be a lot of dust accumulated inside. 2) Here's the script I use to write the floppy images. Reading back the floppy with cmp gives me some confidence that the write was successful. #!/bin/bash -p for II in $@ do echo ls -l $II echo 'insert floppy now, please' read dummy # pause til user hits cr dd if=$II of=/dev/fd0 bs=1024 sync cmp /dev/fd0 $II eject /dev/fd0 JJ=$(basename $II '.img') echo Please label as $JJ done It's invoked as (for example): makefloppy boot.img root.img net-drivers.img Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#274628: OldWorld PowerPC Mac using BootX and 2.4 kernel from pre-rc2 businesscard CD - mostly successful - a few surprises.
Package: installation-reports INSTALL REPORT Debian-installer-version: Fill in date and from where you got the image pre-rc2 businesscard CD = Index of /pub/cdimage-testing/daily/powerpc/pre-rc2 Name Last modified Size Description Parent Directory 02-Oct-2004 00:08 - MD5SUMS01-Oct-2004 00:21 1k sarge-powerpc-businesscard.iso 01-Oct-2004 00:12 112M sarge-powerpc-netinst.iso 01-Oct-2004 00:20 259M Apache/1.3.31 Server at cdimage.debian.org Port 80 = uname -a: The result of running uname -a on a shell prompt Linux debian 2.4.27-powerpc #1 ven sep 3 09:34:51 CEST 2004 ppc GNU/Linux Date: Date and time of the install Sun Oct 3 02:22:32 EDT 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? PowerPC Oldworld Macintosh with BootX bootloader using 2.4.27 kernel and initrd network components from ftp.us.debian.org testing repository not proxied Machine: Description of machine (eg, IBM Thinkpad R32) PowerPC Oldworld Macintosh beige G3 minitower Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? IDE controller Ultra ATA 133/100 pro from SIIG, Inc. AEC6880R: chipset revision 6 hdc: Maxtor 6Y160P0, ATA DISK drive Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. debian:~# mac-fdisk -l /dev/hdc /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdc9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdc10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdc11Apple_UNIX_SVR2 root-11 5859376 @ 48973372 ( 2.8G) Linux native /dev/hdc12Apple_UNIX_SVR2 root-12 5859376 @ 54832748 ( 2.8G) Linux native /dev/hdc13 Apple_Free Extra 259480932 @ 60692124 (123.7G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x debian:~# mount /dev/hdc12 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) debian:~# Root on hdc12 Swap on hdc8 Other partitions are unused in this installation. Output of lspci and lspci -n: debian:~# lspci :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:0f.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13) :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) :00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) :01:08.0 USB Controller: NEC Corporation USB (rev 41) :01:08.1 USB Controller: NEC Corporation USB (rev 41) :01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02) :01:0b.0 FireWire (IEEE 1394):
Bug#274615: Add CDROM fails due to broken symlink and no error notification
On Saturday, October 2, 2004, at 11:02 PM, peter green wrote: once i realised what the problem was i managed to fix it by following the instructions in the error but im pretty sure the error was not visible for long (this was a while ago) in summary base config needs a waqy to avoid obliterating such output from child processes I'll second that suggestion. I recently had a problem where the mirror I had chosen had some temporarily broken packages. Task-select would go to a generic error screen and over-write the specific error messages so fast that I had no way of figuring out what the problem was. I finally went poking around in the log files in /var/log til I found some relevant text. That's not a good or an efficient way to find out what's causing your install to crash! How about doing what aptitude does: print hit return to continue before switching to the generic error message screen -- give folks a little time to read what's going on. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#274741: With two ethernets, installer looses which is primary across the reboot.
Package: installation-reports INSTALL REPORT Debian-installer-version: Fill in date and from where you got the image === Index of /pub/cdimage-testing/daily/powerpc/pre-rc2 Name Last modified Size Description Parent Directory 02-Oct-2004 00:08 - MD5SUMS01-Oct-2004 00:21 1k sarge-powerpc-businesscard.iso 01-Oct-2004 00:12 112M sarge-powerpc-netinst.iso 01-Oct-2004 00:20 259M Apache/1.3.31 Server at cdimage.debian.org Port 80 === uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Tue Sep 14 00:15:52 CEST 2004 ppc GNU/Linux Date: Date and time of the install Sun Oct 3 05:34:03 EDT 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? PowerPC Oldworld Macintosh with BootX bootloader using 2.6.8 kernel and initrd network components from ftp.us.debian.org testing repository not proxied Machine: Description of machine (eg, IBM Thinkpad R32) PowerPC Oldworld Macintosh beige G3 minitower Processor: processor : 0 cpu : 740/750 temperature : 35-37 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 600.06 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? IDE controller Ultra ATA 133/100 pro from SIIG, Inc. hdc: Maxtor 6Y160P0, ATA DISK drive hw-detect: Detected module 'aec62xx' for 'IDE chipset support' hw-detect: Trying to load module 'aec62xx' kernel: AEC6880R: IDE controller at PCI slot :00:0e.0 kernel: AEC6880R: chipset revision 6 kernel: AEC6880R: ROM enabled at 0x8191 kernel: hdg: Maxtor 6Y160P0, ATA DISK drive Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. debian:~# mac-fdisk -l /dev/hdg /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11Apple_UNIX_SVR2 root-11 5859376 @ 48973372 ( 2.8G) Linux native /dev/hdg12Apple_UNIX_SVR2 root-12 5859376 @ 54832748 ( 2.8G) Linux native /dev/hdg13Apple_UNIX_SVR2 root-13 5859376 @ 60692124 ( 2.8G) Linux native /dev/hdg14 Apple_Free Extra 253621556 @ 66551500 (120.9G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x debian:~# mount /dev/hdg13 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) debian:~# Root on hdc12 Swap on hdc8 Other partitions are unused in this installation. Output of lspci and lspci -n: debian:~# lspci :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:0f.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13) :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) :00:12.0 VGA compatible controller: ATI
Bug#274814: PowerPC 2.4 boot floppy doesn't see my IDE hard disk
Package: installation-reports INSTALL REPORT Debian-installer-version: Fill in date and from where you got the image Index of /~luther/d-i/images/2004-10-03/powerpc/floppy-2.4 NameLast modified Size Description ___ [DIR] Parent Directory21-Sep-2004 01:48 - [ ] asian-root.img 03-Oct-2004 01:25 1.1M [ ] boot.img03-Oct-2004 01:26 1.4M [ ] cd-drivers.img 03-Oct-2004 01:27 1.4M [ ] net-drivers.img 03-Oct-2004 01:27 1.4M [ ] ofonlyboot.img 03-Oct-2004 01:28 1.4M [ ] root.img03-Oct-2004 01:29 1.3M ___ Apache/1.3.26 Server at people.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt uname -a during the install process -- I never got past the partitioner Linux debian 2.4.27-powerpc-small #1 ven sep 3 12:21:17 CEST 2004 ppc unknown For comparison -- uname -a after a successful install from the pre-rc2 businesscard CD Linux debian 2.4.27-powerpc #1 ven sep 3 09:34:51 CEST 2004 ppc GNU/Linux Date: Date and time of the install Method: How did you install? What did you boot off? If network install, from where? Proxied? PowerPC Oldworld Macintosh from floppy disks using 2.4.27 kernel and root floppy network components from ftp.us.debian.org testing repository not proxied Machine: Description of machine (eg, IBM Thinkpad R32) PowerPC Oldworld Macintosh beige G3 minitower Processor: processor : 0 cpu : 740/750 temperature : 35-37 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 600.06 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? The *intended* root device is a Maxtor 160 GB IDE drive connected to an IDE controller Ultra ATA 133/100 pro from SIIG, Inc. In the actual event, this disk was not seen by the kernel that booted from the floppy. It did not show up in the partitioner, and snooping about on the F2 console shows that the partitioner wasn't alone! The kernel didn't see it either. Here's a (possibly) relevant excerpt from the syslog file: Oct 4 04:21:35 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 Oct 4 04:21:35 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Oct 4 04:21:35 kernel: ide0: Found Apple Heathrow ATA controller, bus ID 0 Oct 4 04:21:35 kernel: ide1: Found Apple Heathrow ATA controller, bus ID 1 Oct 4 04:21:35 kernel: Probing IDE interface ide0... Oct 4 04:21:35 kernel: hda: MATSHITA CR-585, ATAPI CD/DVD-ROM drive Oct 4 04:21:35 kernel: Unhandled interrupt d, disabled Oct 4 04:21:35 kernel: hda: Enabling MultiWord DMA 1 Oct 4 04:21:35 kernel: Probing IDE interface ide1... Oct 4 04:21:35 kernel: ide0 at 0xd9816000-0xd9816007,0xd9816160 on irq 13 Then a bit later: Oct 4 04:27:13 hw-detect: Detected module 'aec62xx' for 'IDE chipset support' Oct 4 04:27:13 hw-detect: Trying to load module 'aec62xx' Oct 4 04:27:13 kernel: AEC6880R: IDE controller at PCI slot 00:0e.0 Oct 4 04:27:13 kernel: AEC6880R: chipset revision 6 Oct 4 04:27:13 hw-detect: Detected module 'ide-disk' for 'Linux ATA DISK' Oct 4 04:27:13 hw-detect: Trying to load module 'ide-disk' Oct 4 04:27:13 hw-detect: Detected module 'ide-cd' for 'Linux ATAPI CD-ROM' Oct 4 04:27:13 hw-detect: Trying to load module 'ide-cd' Oct 4 04:27:13 hw-detect: Detected module 'isofs' for 'Linux ISO 9660 filesystem' Oct 4 04:27:13 hw-detect: Trying to load module 'isofs' Oct 4 04:27:14 hw-detect: Detected discover version 1, installing discover1. Oct 4 04:27:14 hw-detect: Detected hotplug support, installing hotplug. Oct 4 04:27:14 hw-detect: Missing modules 'ide-scsi (Linux IDE-SCSI emulation layer), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-generic (Linux IDE support), ide-floppy (Linux IDE floppy) For comparison purposes, here are some (possibly) relevant excerpts from the log files after a *successful* install from the pre-rc2 businesscard CD: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AEC6880R: IDE controller at PCI slot 00:0e.0 AEC6880R: chipset revision 6 AEC6880R: not 100%% native mode: will probe irqs later ide: Assuming 33MHz system bus speed
Re: 3 days till freeze of initrd contents
Joey and/or Sven, Please take a look at Bug#274814: (PowerPC 2.4 boot floppy doesn't see my IDE hard disk) and reassign it to the appropriate folks (I'm not familiar enough with who does what to do this myself) so that there's at least a chance that it can be fixed before the initrd is frozen... It's preventing me from making any progress on OldWorld floppy boot testing and the problems that some people have reported with the quik boot loader, which are my primary focus points at this time. Except for those two items, the rest of the OldWorld PowerPC Mac stuff seems to be working pretty well -- modulo a few small glitches that are likely to be architecture non-specific, so need no special pleading from me. Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3 days till freeze of initrd contents
On Oct 5, 2004, at 2:57 PM, Colin Watson wrote: On Tue, Oct 05, 2004 at 03:29:10PM +0200, Sven Luther wrote: Mmm, i had a quick look, and it seems that your IDE controller doesn't appear in lspci output, so it is either not there, or not a pci device. In any case, maybe you should contact gaudenz or colin watson about this. the dmesg outptu shows that it is not a pci device, but a function of the : :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) So the best solution would be to add info for it to hw-detect. Could you confirm which module is supposed to be used for this, and thaty it is indeed included in the appropriate ide module .udeb or something. It doesn't seem to be that simple. According to the dmesg output, the mac-io device above only has a CD-ROM drive attached to it, and this device is in fact detected in the floppy build. The IDE controller that isn't working for Rick is driven by the aec62xx driver, off the PCI bus. This driver *is* in the appropriate udebs and *is* being loaded in the floppy build, but the IDE devices attached to it are not being detected. Search for Probing in the logs and you'll see what I mean. It looks to me as if ide-probe, being built-in, is run before the modular IDE drivers are loaded by hw-detect, and doesn't get a chance to run again. I note that, on i386, CONFIG_BLK_DEV_IDE=m, while the powerpc-small config has CONFIG_BLK_DEV_IDE=y. I suspect that modularizing this would fix the problem. That might well be far too risky a change for sarge at this point, though. Oh goodie! (8-/) What is CONFIG_BLK_DEV_IDE set to in the standard (ie non-small) powerpc config? I ask because the disk is detected when booting the standard kernel via BootX from a businesscard CD. So it's too risky to make the change that will (probably) fix my problem. Is there a workaround that I can apply until such time as it becomes safe to apply the change? Eg, is there a command-line way to somehow force ide-probe to be run a second time after the aec62xx module has been loaded? Something I can type on the F2 console? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How do I get around small / partition?
On Oct 5, 2004, at 3:09 PM, Matt Bonner wrote: I assume at this point, I have to wipe the disk and reinstall, but if anyone knows of a way to resize the partitions, that would be great. That's what I would do in your circumstances. In any case, resizing a partition (even when possible because there is adjacent empty space for it to expand into) is a risky proposition. Make a full backup before you try anything like that. Most importantly, how do I keep this problem from repeating when I re-install? Install in expert mode and use the manual partition editing option. Hope this helps! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3 days till freeze of initrd contents
On Tuesday, October 5, 2004, at 08:11 PM, Sven Luther wrote: On Tue, Oct 05, 2004 at 07:57:20PM +0100, Colin Watson wrote: The IDE controller that isn't working for Rick is driven by the aec62xx driver, off the PCI bus. This driver *is* in the appropriate udebs and *is* being loaded in the floppy build, but the IDE devices attached to it are not being detected. Search for Probing in the logs and you'll see what I mean. It looks to me as if ide-probe, being built-in, is run before the modular IDE drivers are loaded by hw-detect, and doesn't get a chance to run again. I note that, on i386, CONFIG_BLK_DEV_IDE=m, while the powerpc-small config has CONFIG_BLK_DEV_IDE=y. I suspect that modularizing this would fix the problem. That might well be far too risky a change for sarge at this point, though. CONFIG_BLK_DEV_IDE=y is needed for pmac_ideor whatever, which cannot be built modular. So why does it work for the businesscard CD booted via BootX? What is it about the non-small kernel configuration that makes it work? Does this mean that, in order to be recognized, *any* ide device drivers must be non-modular? I'm not an expert, but that sounds like a non-starter to me... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adding an outdated warning to the installation manual for some arches
On Wednesday, October 6, 2004, at 07:43 PM, Joey Hess wrote: I guess the installation manual is still not fact checked or up to date for some architectures, like alpha, while it's in rasonably good shape for others, like i386 and powerpc. Since we're close to the cutoff point to being able to modify the manual for sarge, I wonder if we should add a warning to the manual to architectures that are known not to be fully up-to-date, something like: Warning: This installation manual is based on an earlier installation manual written for the old Debian installer (the boot-floppies), and has been updated to document the new Debian installer. However, for this architecture, the manual has not been fully updated and fact checked for the new installer. There may remain parts of the manual that are outdated or document the boot-floppies installer. A newer version of this manual, possibly better doucumenting this architecture may be found on the web at http://www.debian.org/debel/debian-installer/. What other architectures besides i386 and powerpc are updated well enough to avoid such a warning? Last time I looked at the PowerPC manual, it was not exempt. PowerPC needed such a warning too. Admittedly that was a fair while ago, and the situation may have improved. In any case, I'd be inclined to put it on *all* versions of the manual, even i386. It tells folks where to go to get the latest version. That's always a good idea. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC Clone fails booting 2.6 d-i floppy
On Oct 19, 2004, at 9:40 AM, Duane Cottle wrote: So far, I've found a few possible options if I want to pass kernel args w/ boot floppies on this box: 1) Make my own miboot image - maybe a bit off track as I'm trying to test _these_ floppies; however, if I got that to work, my success might help the developers. (?) I've not tried this. It *may* work. But, as you say, it's off-track. 2) Pass 'boot-file' arguments from the OF prompt. Something, again, that _might_ help the wizards forego that requirement from installers on this platform: and something I've puposefully neglected doing for obvious reasons to those, like me, who spend too much time in OFland. ;) I've tried this. It doesn't work. The arguments never get to the kernel. I'm not sure why. Both are yucky, but if nobody can give me course corrections, I guess I'm headed back down. Oh, where are you liloppc or grubppc? Regards, Duane I've been wondering about maybe trying the following... BootX takes a kernel image and an initrd image and loads them into memory along with some kernel args. Why can't I take the kernel image and the ramdisk image off the floppies and hand them to BootX along with my desired kerenel args? That would give me a straightforward way of setting the kernel arguments without having to make my own boot floppies. What do you think? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC Clone fails booting 2.6 d-i floppy
On Thursday, October 21, 2004, at 11:23 AM, Duane Cottle wrote: Hey all, Trying to see what's on the 2.6 root.img, I've been unsuccessful mounting it as loop or the actual floppy. What filesystem type is it? I figured it was ext2, but mount says it's not. I've tried cramfs, hfs, hfsplus, but it's not working. Regards, Duane the root floppy is (sometimes) a compressed /ext2 image cp root.img /tmp/root.gz gunzip /tmp/root.gz mount -v -t etx2 -o ro,loop /tmp/root /media/floppy or some such thing as that. and (somteimes) a cramfs filesystem. I don't know under what circumstances which is chosen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The best scheme to test D-I
Glad to hear there's another one of us (the few, the proud!) interested in helping test D-I on PowerMac hardware. What kind of machine do you have? Here are my suggestions: Leave some free space (I allow about 10 GB) to install your test Debian into. Plan to re-initialize this free space each time you do a test install. Also allow some space (your choice as to how much) for a permanent /home partition that you share with your main/permanent debian installation. You will probably develop tools as you test things and it's nice to have a permanent rack space to put them when you're not using them. You can also use the free-standing /home partition as a place to stash log files and the like. Also, having the working main/permanent Debain installation available when you need it will make it much easier to fix up minor glitches in the test installations. When you get to the reboot between phase1 and phase2, it often happens that there is some minor thing wrong with the setup that causes you to be unable to boot. Being able to boot back to your main Debian installation and look around so you can find and fix the glitches will save you from having to re-do the whole of phase1 (possibly multiple times) and get on to testing phase2 stuff sooner. Enjoy! Rick On Friday, October 22, 2004, at 04:51 PM, Jaonary Rabarisoa wrote: Hi all, I'm going to clean my hard drive and re-install all my system. I have a powerpc based computer and I will put mac os x and debian on it. I also plan to test d-i on this computer. Then, I wanna know if some of you could give some advice on partitionning the hard drive. I mean, should I create a third free partition along side the two main partion (mac os + debian ) in order to be able to test d-i without deleting my existing debian partion or is there another way to test d-i? Thanks for your reply, -- Jaonary RABARISOA 27 rue des loges 78600 Maisons Laffitte ___[ Pub ] Envie de discuter gratuitement avec vos amis ? Téléchargez Yahoo! Messenger http://yahoo.ifrance.com ___[ Pub ] Inscrivez-vous gratuitement sur Tandaime, Le site de rencontres ! http://rencontre.rencontres.com/index.php?origine
Re: got quik working with OldWorld G3 Beige 233MHz
On Monday, October 25, 2004, at 01:48 PM, Sven Luther wrote: Notice that if we manage to free miboot, a miboot kernel on a special partition may be one solution for 2.6.8 kernels with initrd. The situation may be worse than we thought. Take a look at Apple Tech Note 1189 which is available at http://developer.apple.com/technotes/tn/pdf/tn1189.pdf In particular see pages 35 and 36 regarding the licensing required to use the apple patch chaining drivers and associated patches to the Apple boot ROM. I may be mistaken, but I believe that, when booting from a hard disk (not a floppy), miboot depends on having it's early stages loaded by the Apple OldWorld Boot ROM code, which needs the afore-mentioned patches to do its job. These patches and the patch chaining driver are placed on the low-numbered partitions of a hard-disk by the Apple disk partitioning utility (or by third-party partitioning utilities that [presumably] use the patches under license from Apple.) In the listing snippet below, I'm talking about the contents of hdc[2-5] -- the reason why my macOS9 partition is hdc6 rather than hdc2. This theory would be disproved if anyone had ever gotten miboot to boot from a disk that was missing the driver partitions. Anybody ever tried that? For NewWorld machines, this seems *not* to be required. I believe that this is because all the code needed to boot is in the Open Firmware. This is the reason why, if you install a PCI disk interface card and you expect to boot from it, you need to be sure that the card has an on-board ROM with Open Firmware booting support that effectively extends the mother-board's Open Firmware so that it knows how to deal with the new card. Booting from a floppy does not require any patches -- for a couple of reasons: 1) space -- a floppy doesn't have much space and a couple of dozen Kbytes for patches would be highly inconvenient; 2) testing -- the ROM code that deals with booting from floppies must get pretty well rung-out during design test, so it's got to be absolutely bug-free before the hardware is released. Enjoy! Rick debian:~# mac-fdisk -l /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unsuccessful installation on oldworld powermac apple 6400/180
On Tuesday, October 26, 2004, at 03:18 AM, Hans Ekbrand wrote: After finishing the installation and rebooting, nothing happaned. The monitor warned Check the signal cable. Since the boot floppy worked alright, I would like to use it to boot the final system, instead of booting from hard disk. Is that supported? If not, any hints on how to do it? As I've said before, if you can afford the disk space (big IDE disks are cheap) the boot loader that I suggest as being most robust and flexible is MacOS with BootX. That said, if you really want to boot from floppy, you can use the install boot floppy, but you will need to construct your own root floppy that is aware of the location of your real root filesystem on the hard disk. It should load whatever modules are required for your hardware then perform a pivot_root operation to the real root. If you use the install boot floppy you will have to live with the kernel that's on that floppy, the 2.4.27-powerpc-small, which has *everything* possible as modules, to keep down size so it will fit on a 1.4 MB floppy. If you get it to work, I'd suggest you try building your own customized kernel as your first project. Maybe you can get a kernel with an optimized set of drivers built-in that will still fit on a floppy. It's worth a try! Have fun! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unsuccessful installation on oldworld powermac apple 6400/180
On Wednesday, October 27, 2004, at 07:44 AM, Wouter Hanegraaff wrote: Hi, On Tue, Oct 26, 2004 at 10:33:45AM -0400, Rick Thomas wrote: As I've said before, if you can afford the disk space (big IDE disks are cheap) the boot loader that I suggest as being most robust and flexible is MacOS with BootX. Ok, could you send me the MacOS installation CD? I don't have one and mac os is no longer installed. No, but I'm told you can purchase a MacOS 8.5 CD on e-bay for $5 or so. I've never tried it myself. That said, if you really want to boot from floppy, you can use the install boot floppy, but you will need to construct your own root floppy that is aware of the location of your real root filesystem on the hard disk. It should load whatever modules are required for your hardware then perform a pivot_root operation to the real root. How do you change boot parameters on the oldworld mac boot floppies? There is no boot promt where I can type them in manually. It's really annoying to have successfully installed debian and not being able to use it because the system is not bootable... You can't change the parameters on the floppy without a working Linux. If we ever get-round to the clean-room rewrite of miboot with a free toolchain, that's a feature I'd like to see. Hope this helps! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unsuccessful installation on oldworld powermac apple 6400/180
On Wednesday, October 27, 2004, at 11:04 AM, Wouter Hanegraaff wrote: On Wed, Oct 27, 2004 at 01:44:06PM +0200, Wouter Hanegraaff wrote: Hi, On Tue, Oct 26, 2004 at 10:33:45AM -0400, Rick Thomas wrote: As I've said before, if you can afford the disk space (big IDE disks are cheap) the boot loader that I suggest as being most robust and flexible is MacOS with BootX. Ok, could you send me the MacOS installation CD? I don't have one and mac os is no longer installed. Hmm I should have said this in a more friendly way. Would the following procedure work: - boot using the boot floppies - load the necessairy modules using disk images / net - mount /target - chroot /target and run quik - reboot It might work. It's certainly worth a try. Please report back to the list with your results! After the install, the system booted normally once. After that I zapped the pram to get rid of the long lasting black screen, hoping I would be able to enter some boot parameters (didn't work of course, but it made the system unbootable). Yeah. quik diddles the Open Firmware parameters. Zapping the PRAM resets the diddles to default. HTH! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: got quik working with OldWorld G3 Beige 233MHz
On Thursday, October 28, 2004, at 12:50 PM, Brad Boyer wrote: On Tue, Oct 26, 2004 at 03:50:31AM -0400, Rick Thomas wrote: I may be mistaken, but I believe that snip... Well, it's not really that simple. I'll try to explain as I go along in the message. snip... Thanks Brad! the extra detail really helps. Bottom line question... Does the Apple licensing requirement for the drivers and patches mean that (as a practical matter) we'll never be able to write a free miboot that can boot off partitioned media? Is a free but floppy only version of miboot worth the effort? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: free miboot - was Re: got quik working with OldWorld G3 Beige 233MHz
On Friday, October 29, 2004, at 04:53 PM, Brad Boyer wrote:
To support starting from just a Debian CD on all oldworld boxes as well
as install a bootable system, we need to do the following:
1) Write disk drivers for SCSI and IDE (both HD and CD-ROM)
2) License the patches from Apple (or somehow reverse engineer them)
3) Add support to mac-fdisk to install the drivers and patches
4) Fix miboot to be truly free.
5) Add a miboot installer (similar to ybin/mkofboot)
On the other hand, if you only want to use it on floppies, only #4
(and maybe #5) are needed.
Let me see if I've got this right...
The world is divided into three types of people:
0) People with hardware other than OldWorld Powermacs. I will
ignore this group, except to say that, according to the latest
popularity contest results, they constitute over 98% of the users
of Debian software.
1) Of those who have an OldWorld PowerMac (or clone) the large
majority will also have a copy of the MacOS{8.x,9.x} install CD
that came with the machine (or that they bought cheap on e-bay, or
bought expensive from Apple when the world was new and we were all
very young...) and will be willing to use it to install MacOS so
that they can use BootX as their default boot loader.
2) A vocal but tiny minority of absolutists who are unwilling to
have any non-free software (above the level of unavoidable firmware
ROMs) on their machines.
3) Those who are opposed to non-free software or for other reasons
(such as disk space) don't want to have MacOS on their machines,
but are willing to at least have their disks initialized and
partitioned by the Apple Disk Utility software. (Personal opinion:
this group is likely somewhat larger than group 2 but still much
smaller than group 1.)
Group 1 has no problem. They can use BootX to start up the D-I
installer, and they can continue to use BootX as their default
boot-loader. The fact that BootX is not free is not a problem for
these folks. MacOS isn't free either! All they need is good
directions in the manual for how to do it.
Eliminating group 1 leaves us with (as a guess) somewhat less than
0.1% of debian users in groups 2 and 3. Still, this represents
(guess) 5% of Debian OldWorld PowerMac users. And they are a vocal
bunch, for all their small numbers.
As Brad points out, group 3 needs only a clean-room free
implementation of miboot and they are off and running. They can
boot from floppies to run the D-I installer -- either via the
network or via CDs, and use the (proposed) free miboot as their
default boot-loader from disk after installation is complete. That
is: after the initial installation the Apple drivers on their disk
will be enough to allow them to use miboot to boot from that disk.
They will need good clear directions in the manual for how to make
boot floppies and use them to start up D-I.
We're now down to group 2 -- the (at a guess) less than 0.01% of
hard-core absolutists who will not allow *any* non-free software to
touch their machines. These folks have a few alternatives: a) They
can implement their own free boot software, including Apple Boot
ROM compatible disk and CD drivers. b) They can put up with the
vagaries of Open firmware and quik for their particular hardware.
c) They can use the (proposed) free miboot but only from
floppies -- meaning that they must forever boot their machine with
a floppy -- installation and post-install production.
I don't think that alternative (a) is going to happen. There just
isn't the critical mass to get such a project off the ground.
Personally, I think alternative (b) is not viable either -- it's
just too much pain for anyone to put up with long-term -- though
there are undoubtedly folks out there who will try it for a while
before they give up. Fortunately, alternative (c) is a workable
compromise between pain (having to keep and use floppies, and
replace them when they wear out) and living with your principles.
Hope this helps!
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: free miboot - was Re: got quik working with OldWorld G3 Beige 233MHz
On Saturday, October 30, 2004, at 06:07 AM, Sebastiaan Molenaar wrote:
On Sat, 2004-10-30 at 06:54, Rick Thomas wrote:
snip /snip
ROM compatible disk and CD drivers. b) They can put up with the
vagaries of Open firmware and quik for their particular hardware.
snip /snip
Personally, I think alternative (b) is not viable either -- it's
just too much pain for anyone to put up with long-term -- though
there are undoubtedly folks out there who will try it for a while
before they give up. Fortunately, alternative (c) is a workable
snip /snip
Now my question is, why isn't it possible to get this more stable?
(guess wich group I'm in)
Is it just that the apple OF isn't stable or is quik not stable?
A bit of both.
I understand apple OF is different on pretty much every oldworld ppc
but it should still be possible to find the workaround for every
different
one and once it's working it should keep working doesn't it?
Indeed, the BSD folks have done exactly that. Quik is their
preferred boot-loader for OldWorld Macs. They have a huge table
with each model of Mac and the particular workarounds/patches for
that model to make its OF boot via quik.
To my mind, the fundamental problem is that patches to Open
Firmware, once made, don't last. OF patches reside in the PRAM.
If you ever boot MacOS{8,9} on a patched machine you will have to
clear the PRAM and thereby loose all your patches. Also, the PRAM
can be cleared by a power failure if your PRAM battery has run
down -- a common problem on older machines. If the patches get
lost, you have to re-patch, which can be a pain if your machine has
the kind of OF that wants a terminal on the serial port.
That said, I have two old 6500 PowerMacs that boot via quik and
have been running that way for over four years. They are sitting
in my machine room on a diesel-backed UPS and haven't been rebooted
more than a half-dozen times in those four years. I've had to
re-patch one of them a couple of times. It's not fun, but it's not
impossible either. Fortunately, neither of these machines is
mission critical -- they can afford to be offline for a week or
so if they loose their PRAM patches while I'm on vacation.
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Old world mac boot floppies
On Nov 9, 2004, at 3:45 AM, Wade Berrier wrote: One last thing I'm going to try is to replace the cmos battery. When I boot into the woody install, the time is set to 1956. I'll set it, and even still, the next reboot is 1956. I friend at work tipped me on this one. Maybe this will make it so I can boot quik. Anyone have any other suggestions? Replacing the battery will definitely help. Quik depends on patches to the Open Firmware setting. Those settings are maintained in the CMOS RAM by the battery. When the battery fails, the patches disappear -- poof! you can't boot with quik. That said: Even with a working CMOS battery, quik has its serious problems. Since there is no working (in the sense of just works -- quik doesn't qualify IMHO) and free (in the Debian legal sense) bootloader for OldWorld PowerMacs, you might as well use BootX. It just works on pretty much all OldWorld models, because it depends on MacOS for all the model-specific stuff. With a little care, the disk-space overhead for MacOS with BootX can be kept well under 100 MB (on a modern 200 GB disk, that's less than peanuts!). With no care at all, you can keep it to under 300 MB (just do a standard install). It's definitely worth the trouble to get hold of a MacOS 8.5 - 9.1 CD and install it -- just for the convenience factor. My two cents, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
free miboot on OldWorld Mac
On Aug 11, 2004, at 3:44 PM, Sven Luther wrote: On Wed, Aug 11, 2004 at 03:12:49PM -0400, Rick_Thomas wrote: Here are a few practical suggestions: Has anyone looked at inside Macintosh or some of the other early Mac technical docs? I wonder if this code is, maybe, described there? The real problem is that i am not a mac user, since i came from the amiga world, and am currently working for genesi, who produce the pegasos and MorphOS, which is an amiga OS reimplementation. We have information about the boot block, but not the code in question. I know that it is mostly trap instructions, and do some basic mac rom calls. If we were able to know which rom calls those are, and what they do, this would be enough for a clean room reimplementation. I've been doing some research into this. In particular, I've been looking at the Monster drivers tech note available on Apple's Tech Support web site. As I mentioned in another thread, calls to the OldWorld Mac ROM, for anything other than a floppy, are actually calls to a patched/extended image of the ROM -- patched and extended with whatever driver information is needed to help the ROM code read from the device in question on that particular type of Mac. Those patches/drivers are licensed IP of Apple (or a third-party vendor if Apple doesn't directly support booting from the device in question.) The patches/drivers get installed on your hard disk by the Apple disk partitioning utility (or a similar third-party utility) which is only available as part of MacOS (or from the third party vendor). It appears that re-writing the boot code part of miboot is really just the tip of a very large iceberg. To be truly free, you have to provide a substitute for the patches and drivers. It also appears that -- short of putting up with all the model specific quirks of quik -- there's no way to avoid using the MacOS disk partitioning utility at least once to install the driver/patch partitions on a disk if you intend to boot Linux from that disk. Enjoy! Rick PS -- I'll leave the question of what all this means for support of Debian Sarge on OldWorld Macs to wiser heads than mine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Old world mac boot floppies
On Nov 10, 2004, at 5:25 PM, Sven Luther wrote: On Wed, Nov 10, 2004 at 01:35:04PM -0700, Wade Berrier wrote: I did have one idea: if you can boot a coff image from an hfs partition, couldn't you have an hfs /boot partition on the harddrive and boot directly from open firmware? If I understand this correctly, quik wouldn't be needed. I think you can only netboot those, since the disk drivers are not available in OF or something, not sure though. Please see my (very) recent posting to the debian-boot list with subject 'free miboot on OldWorld Mac' What I say in that posting applies only to OldWorld Macs. On NewWorld Macs, Apple requires all add-in cards that want to support booting to do so by having a hunk of ROM on the card that extends the Apple Open Firmware with commands for booting from that card. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Nov 10, 2004, at 6:01 AM, Sven Luther wrote: On Wed, Nov 10, 2004 at 03:46:58AM -0500, Rick Thomas wrote: The new yaboot seems to work at least on one of my machines. I'll try some others later. Specifically, I tried it on my BlueWhite G3. I booted holding down the C key (ADB keyboard) and got the yaboot messages. At the boot: prompt, I typed expert video=ofonly and it did the expected things. In fact everything proceeded as expected til I Ok, thanks, can you forward info about this to the bug report ? It is : [EMAIL PROTECTED] got to the partitioner, which hung up trying to look at the partitions on the disk on my SIIG Ultra ATA 133/100 Pro IDE controller PCI card. The dmesg command on the F2 console showed a bunch of messages hdg: dma_timeout_expiry: dma status == 0x24 AEC62XX timeout 4hdg: lost interrupt I've seen this before with 2.6 kernels. I've reported it to the list in installation reports, but nobody seems to care. Can you fill a bug report about this against the powerpc kernel-image-2.6.8-powerpc ? It seems to be a powerpc kernel problem. So I was unable to proceed any further on that machine. ... later ... I also tried it on my grey G4 minitower 733MHz. Worked fine up to partitioning disks. This is a production machine with no free disk partitions, so I couldn't proceed any further than that. I've got a G4 450MHz at work with some free partitions, so I'll try a full install there tomorrow. You tried only CD booting method, not net or disk, right ? What was the bug number of the bug report you wanted me to reply to for the new yaboot? See above. I got a chance to do an install from your mini.iso on a test machine. It's a G4 350 MHz (AGP graphics). I'm not clear as to whether this will install your test yaboot or not, but here's what happened: I booted off the CD and chose the default (i.e. non-expert) install at the boot: prompt. I answered all the i18n questions with the default (US-English) and configured the network manually (no DHCP on this net). I chose the debain.rutgers.edu mirror because it's located in the next building over on the same campus and I have a 100-Mbit connection via campus LAN to it from the test machine. (I'm used to doing installs over a fairly fast cable-modem that gets about 4 Mbit/sec on a good day. This was *much* faster. -8) When it came time to partition the disk, I chose a guided partitioning, and it set me up with a 1 MB boot partition, a 4 GB root partition, and a 260 MB swap partition. Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. When the first phase was over, and it came time for the reboot, everything went completely as expected, and I finished the installation after an uneventful reboot. If this was using your new yaboot, then I'd say the test was successful. If this sequence does *not* exercise your new yaboot, please give me instructions for what to do next. I'll be in Atlanta for the USENIX/LISA conference all next week, so my next opportunity for testing will be a week from now. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? Rick On Nov 15, 2004, at 11:17 AM, Colin Watson wrote: On Sat, Nov 13, 2004 at 02:44:59PM +0100, Sven Luther wrote: On Fri, Nov 12, 2004 at 04:54:46PM -0500, Rick Thomas wrote: Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. This is definitively a bug, could you fill a bug report about this ? i guess quil-installer or debian-installer are the packages to report a bug against. monolithic is like that; it includes both quik-installer and yaboot-installer, bypassing the XB-Subarchitecture: control field checks. It's not a problem for normal images. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Nov 15, 2004, at 12:41 PM, Sven Luther wrote: On Mon, Nov 15, 2004 at 12:29:09PM -0500, Rick Thomas wrote: I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? monolithic is mostly there only for testing and development, so it should not be important. Ethan just said he had only very few success reports, and would like more testing, despite the tests i already got, and Leigh Brown haven tested it successfully on his 7043-140 or whatever it was. Both HD and CD, since NET is broken anyway on this one ? Colin, could i ask you to test the patch and write a it works report to the bug report, and Rick, did you ever fill a followup to the bug report, could you please do so, and any others that have tested it provide feedback too ? I believe I did file a followup to the bug report. If I didn't, I will as soon as I get a chance to try installing your patched yaboot .deb and run ybin -- next week when I have access to the hardware again (I'll be in Atlanta until Sunday evening. Monday will be my first day at work -- where the test machine is located.) Sorry I can't be quicker about this. Life keeps getting in the way! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Nov 13, 2004, at 8:44 AM, Sven Luther wrote: On Fri, Nov 12, 2004 at 04:54:46PM -0500, Rick Thomas wrote: I got a chance to do an install from your mini.iso on a test machine. It's a G4 350 MHz (AGP graphics). I'm not clear as to whether this will install your test yaboot or not, but here's what happened: This will use my test yaboot for booting from the CD. I booted off the CD and chose the default (i.e. non-expert) install at the boot: prompt. I answered all the i18n questions with the default (US-English) and configured the network manually (no DHCP on this net). I chose the debain.rutgers.edu mirror because it's located in the next building over on the same campus and I have a 100-Mbit connection via campus LAN to it from the test machine. (I'm used to doing installs over a fairly fast cable-modem that gets about 4 Mbit/sec on a good day. This was *much* faster. -8) When it came time to partition the disk, I chose a guided partitioning, and it set me up with a 1 MB boot partition, a 4 GB root partition, and a 260 MB swap partition. Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. This is definitively a bug, could you fill a bug report about this ? i guess quil-installer or debian-installer are the packages to report a bug against. As I understand the discussion so far, this is just a bug in the mini.iso, and will not affect the netinst or businesscard .iso images. And nobody is interested in fixing the mini.iso problem, so there's no point in filing a bug report at this time. When the first phase was over, and it came time for the reboot, everything went completely as expected, and I finished the installation after an uneventful reboot. If this was using your new yaboot, then I'd say the test was successful. Well, to test booting from the disk, you need to install my yaboot .deb, run ybin, and try rebooting. If this sequence does *not* exercise your new yaboot, please give me instructions for what to do next. I'll be in Atlanta for the USENIX/LISA conference all next week, so my next opportunity for testing will be a week from now. Ok. So what I need now is a pointer to your patched yaboot .deb file. Can you give me a URL or whatever it is I need? Thanks, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: your daily build of powerpc floppies
On Saturday, December 11, 2004, at 01:22 AM, Sven Luther wrote: On Sat, Dec 11, 2004 at 12:50:21AM -0500, Rick_Thomas wrote: Ralf, Are you willing/able to install a small MacOS (8 or 9, not X) partition on these machines? If so, you can use the BootX bootloader. If you don't know about it, it's a MacOS app that loads a Linux kernel and ramdisk, along with a boot-time parameter string. BootX provides essentially all the important functionality of yaboot for NewWorld Macs or grub/lilo for x86s. Bah, you are proposing the ugly non-free solution, shame on you :) Ugly and non-free are valid arguments against BootX. That's why I said willing/able. As with all religions, people come in a variety of degrees of religiosity on this subject. I understand and completely support anyone who finds themselves un-willing/able to envision themselves using a Linux system that needs MacOS for a few seconds at startup time. But I'm not one of them. And I think that everyone should understand the trade-offs before they make their choices. If you are willing/able to put up with the quirks of quik, then more power to you! There is an easier way, is all I'm saying. Seriously, he has the miboot floppies working, so why would he need bootx ? Seriously, to boot his system after it's installed on his hard disk. There are four different bootloaders for Macs. One is yaboot, which only works on NewWorld machines. The others are miboot, quik, and BootX, which work on OldWorld machines, but not on NewWorld. For technical reasons having to do with the details of how OldWorld Macs get driver software for their boot devices, the miboot bootloader will never be useful for anything but floppy disk booting. Even if the cleanroom re-implementation project gets off the ground and produces a working bootloader, this will not change. Sure, but we are speaking initial installation, afterward you are supposed to use quik. Yup. And quik will work -- assuming that the fix for booting with an initrd makes it into the sarge distribution. And assuming that he has the fortitude to look up and install the OF patches that are required for his particular hardware. And assuming that he can deal with the fact that those patches will disappear and have to be re-installed every time he zaps the PRAM, or boots MacOS for any reason, or his cmos-battery gets tired and has to be replaced -- a fairly common occurrence with old Macs -- or a host of other more obscure reasons. Quik gets around this problem by using Open Firmware to access its boot devices. However, until recently, quik did not support initial ramdisks. This makes it useless for booting any of the stock 2.6 based kernels. There is, apparently, in the works an attempt to fix this. But it's not clear that the fix will make it into the distribution before sarge is released. Even if a fixed quik makes it possible to boot 2.6 kernels from a hard disk or over a network, quik's inherent reliance on specialized model-dependent patches to the Open Firmware makes me think that it's not (and never will be) for the faint of heart. It works rather well, for woody only one model was listed as not supporting quik. Quik works OK. I have two production machines booting with quik in my Lab at work. It's just a pain in the #$% to make it work and keep it working. There is an easier way. That's all I'm saying. In my very humble opinion, that doesn't leave much except BootX for the general user with an OldWorld Mac. Fortunately, BootX just works on all the models of Oldworld Macs that I've tried it on. I recommend you give it a try. Well, debian can't recomend it, I understand that. I'm not Debian. I can recommend it. I do. YMMV. (-8) and many will not have or not want mac os anymore, or like me, are saddled with a greek localised mac os, which is not really all that fun to use. Well, probably good oportunity to learn greek you would say :) Actually, I would say it's a good opportunity to learn to use e-bay, and buy one of those $10 copies of MacOS that seem to be for sale there. On the other hand, I understand Greece is warm this time of year, and the people are friendly... (-8) Friendly, Sven Luther Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [RFC] Consequences for official CD/DVD images for Lenny
On Dec 29, 2008, at 4:43 PM, Frans Pop wrote: Powerpc is very definitely losing its user base (just compare the number of macbooks (ppc based!) you see now at conferences with what you saw 3 or 4 years ago. Actually, MacBook is the name for the Intel-based Apple laptops. The PowerPC based laptops were called iBook (and some other things, but generically they were all iBooks). I only go to one conference a year (LISA -- Large Installation Systems Administration, run by USENIX) but the number of Apple based laptops I see in use by the gathered SysAdmins doesn't change much from year-to-year. Nevertheless, quibbles aside, when Apple dropped the PowerPC, it was a big blow to the availability of relatively inexpensive consumer- grade PowerPC hardware. And this will result, over time, in a drop in demand for the ppc Debian port. Time marches on. I'm only a user and a tester, so I don't get to vote, but I'd go for the increased utility of dropping ppc from the multi-arch/multi- desktop DVD-1. In exchange, I'd like to see a PPC-only DVD-1 with the same functionality. But then, I've got good Internet connectivity, so I can afford to download two separate DVD images if I need to. I can also afford to install from a Businesscard image and get what I need from a nearby mirror. So maybe you should be taking to somebody in India or Uganda about this. Anybody out there with limited Internet bandwidth want to comment? My two cents, Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFC] Consequences for official CD/DVD images for Lenny
On Dec 30, 2008, at 6:52 AM, Frans Pop wrote: On Tuesday 30 December 2008, Wouter Verhelst wrote: On Tue, Dec 30, 2008 at 09:11:20AM +0100, Frans Pop wrote: The regular powerpc DVD will switch from GNOME-based to all-desktop. The only thing missing is offering boot options to select different desktop environments as we'll now do for x86, Given that all the necessary packages will be available on the DVD, doesn't it make more sense to do the selection in tasksel, rather than at boot-time? It would certainly be more convenient for the user. IMHO, doing it at boot time violates the principle of least astonishment. As I understand it, the original argument for doing it at boot time was that you couldn't fit all the options onto a single CD, so you had to segregate them into one CD per desktop type, so the decision really had to be pushed back even further than boot-time -- it was already made at CD creation time. This makes sense in the CD context (except for those who had good Internet connectivity and could get whatever they needed from a friendly neighborhood mirror site). But if you can fit all the desktops into a DVD, that argument is moot. Or am I missing something? Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510263: installation-report: installing Lenny on a slug - eventually successful after a few trys and some fixups
Package: installation-reports Version: 2.38 Severity: normal At first -- Package-specific info: Boot method: following instructions on http://www.cyrius.com/debian/nslu2/ Image version: http://www.slug-firmware.net/d-click.php?p=download%2Fdebian%2Fnslu2f=debian-armel-5.0rc1.zipl=d-license.txtk=800164d2fb07ee586bb586c7d0851358 MD5=3a46b5f46ee0f1b5c87a140c2e82d2c8 Released 2008-11-12 Date: Date and time of the install Machine: bog standard NSLU2 - no mods 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=5.0 (lenny) - installer build 20081029 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == umame -a: Linux slug 2.6.26-1-ixp4xx #1 Fri Oct 10 02:29:27 UTC 2008 armv5tel unknown lspci -knn: 00:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -knn: Kernel driver in use: ehci_hcd lsmod: Module Size Used by lsmod: jfs 166636 0 lsmod: reiserfs 245524 0 lsmod: ext3 123304 2 lsmod: jbd45396 1 ext3 lsmod: vfat9952 0 lsmod: fat48156 1 vfat lsmod: nls_base7168 3 jfs,vfat,fat lsmod: ext2 63496 0 lsmod: mbcache 7872 2 ext3,ext2 lsmod: sd_mod 22736 4 lsmod: usb_storage82375 3 lsmod: scsi_mod 111076 2 sd_mod,usb_storage lsmod: ohci_hcd 18212 0 lsmod: ehci_hcd 35148 0 lsmod: evdev 8608 0 lsmod: ixp4xx_eth 12216 0 lsmod: ixp4xx_npe 7936 2 ixp4xx_eth lsmod: firmware_class 7552 1 ixp4xx_npe lsmod: ixp4xx_qmgr 5336 6 ixp4xx_eth lsmod: ixp4xx_beeper 2720 0 lsmod: usbcore 128252 4 usb_storage,ohci_hcd,ehci_hcd df: Filesystem 1k-blocks Used Available Use% Mounted on df: tmpfs1476832 14736 0% /dev df: /dev/sda1 6728280620632 5765868 10% /target df: /dev/sda6 69228152317064 65394464 0% /target/home df: /dev/sda1 6728280620632 5765868 10% /dev/.static/dev df: tmpfs1476832 14736 0% /target/dev free: total used free shared buffers free: Mem:2954026632 29080 836 free: Swap: 979924 4228 975696 free: Total: 100946430860 978604 /proc/cmdline: console=ttyS0,115200 rtc-x1205.probe=0,0x6f noirqdebug /proc/cpuinfo: Processor: XScale-IXP42x Family rev 1 (v5l) /proc/cpuinfo: BogoMIPS : 132.71 /proc/cpuinfo: Features : swp half thumb fastmult edsp /proc/cpuinfo: CPU implementer : 0x69 /proc/cpuinfo: CPU architecture: 5TE /proc/cpuinfo: CPU variant : 0x0 /proc/cpuinfo: CPU part : 0x41f /proc/cpuinfo: CPU revision : 1 /proc/cpuinfo: Cache type : undefined 5 /proc/cpuinfo: Cache clean : undefined 5 /proc/cpuinfo: Cache lockdown : undefined 5 /proc/cpuinfo: Cache format : Harvard /proc/cpuinfo: I size : 32768 /proc/cpuinfo: I assoc : 32 /proc/cpuinfo: I line length: 32 /proc/cpuinfo: I sets : 32 /proc/cpuinfo: D size : 32768 /proc/cpuinfo: D assoc : 32 /proc/cpuinfo: D line length: 32 /proc/cpuinfo: D sets : 32 /proc/cpuinfo: /proc/cpuinfo: Hardware : Linksys NSLU2 /proc/cpuinfo: Revision : /proc/cpuinfo: Serial :
Bug#510263: Please close this bug
This is an abortive attempt at an installation report. A full report was subsequently submitted. Sorry for the noise! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Detect already installed partitions.
On Dec 30, 2008, at 6:24 AM, Wouter Verhelst wrote: On Tue, Dec 30, 2008 at 02:47:58PM +0530, Rabbul Nawaz wrote: Thanks for the quick respose. Installing libparted, and all its dependencies including all the libraries inside the rootfs environment would definetely increase the size of the rootfs. Moreover it would require a static compilation. Is there any other way, by which I can just get the partition-label information which is lighter than using libparted. parted actually reads data from the partition to get at the labels. AFAIK, this data is not available through the kernel. Take a look at the source code for the mount(8) command. It has some heuristics for figuring out things like the filesystem type and the label/UUID. I haven't done this myself, and maybe it uses libparted so it won't help you, but if it's self-contained it may be easier to hack those heuristics than to put up with the size of parted and friends... Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFC] Consequences for official CD/DVD images for Lenny
On Dec 30, 2008, at 1:36 PM, Frans Pop wrote: On Tuesday 30 December 2008, Rick Thomas wrote: Given that all the necessary packages will be available on the DVD, doesn't it make more sense to do the selection in tasksel, rather than at boot-time? It would certainly be more convenient for the user. IMHO, doing it at boot time violates the principle of least astonishment. See [1] in http://lists.debian.org/debian-cd/2008/12/msg00019.html Frans wrote: The simple reason is that Joey Hess, the lead developer for tasksel, has always been opposed to doing it in tasksel with as main argument that tasksel is mostly for new users who are probably not aware of what DEs exist and thus would only be confused when having to choose between meaningless names as GNOME, KDE, etc. I don't know (or care to get involved with) the personalities here, so if I'm meddling in the affairs of wizards, I apologize and somebody should email me off-line ti tell me back off. Nevertheless: Suppose somebody (maybe me?) were to write a patch to tasksel that implemented an expert mode with big bold warnings Here there be dragons. Don't do this unless you *really* know what you're doing! Useful, but newbie-dangerous, options could be put there, including selection of which DEs to install. If such a patch was available, would Joey be willing to accept it? (Before I volunteer, what language is tasksel written in? If it's in Python or C, languages that I know well, I might be able to take it on.) Crawling back under my rock, Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
On Dec 30, 2008, at 7:12 PM, Rick Thomas wrote: for some reason it decided that the DNS domain was example.org, not the one being offered by DHCP. For what it's worth: Normal installs (on the console, not via SSH) on PowerPC Macs and i386 PCs on this subnet, using this DHCP server, don't have this problem. They pick up the local DNS domain from DHCP and run with it. HTH, Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
On Dec 31, 2008, at 2:41 PM, Martin Michlmayr wrote: ext2 instead of ext3 is a good idea... maybe this should be offered on the NSLU2 by default as one option. On the other hand, it's also fairly easy to use the default partition schema and then change ext3 to ext2 in the partitioner manually before actually formating the disk. Maybe it's enough if I mention this on my web site. What do you think? Mentioning the ext2 option (and how to get it) on the web page is probably good enough, since via the web page is the most common (only really useful?) way to get a working installation. So I'd go with that for Lenny. Adding it as an option for Stretch is worth a wishlist bugreport, seems to me. noatime is a known wishlist that will be done after lenny, I guess. Does that mean that there's no way to specify it at install/ partitioner time? Or that there's no way to specify it at all? Or just that it's available but not automatic in Lenny and planned to be automatic in Stretch? Or something else? I was under the impression that relatime (a good compromise between strict POSIX semantics and practicality) would be standard (at least in certain kinds of installations) in Stretch. Is that still true? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510666: Installer run from USB stick should prefer iso image on stick over one on hard drive
On Jan 4, 2009, at 2:45 AM, Christian Perrier wrote: reassign 510666 iso-scan thanks Quoting Aenoch Lynn (aenoch_l...@yahoo.com): I wanted to try the USB install of lenny, so from a working lenny installation on my machine (which I intended to overwrite) I put the installer on a 2 GB USB thumb drive using: http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz and then downloaded debian-testing-i386-netinst.iso onto my hard drive and then copied it onto on the same partition on the USB drive. Booting the installer went fine, but instead of finding the iso image on the USB drive, the installer found the iso image on the hard drive and mounted it. I was unable to wipe the root partition, /dev/hda1, as the installer refused saying the device was in use (or something similar). I had to boot back into the old system, remove the iso image from the drive, and boot back into the USB installer. After this the installer ran without problems. I recommend the installer prefer to use an iso image on the same device from which the installer itself is running. I'm not entirely sure that the installer has an easy way to know what device it is run from once it is booted. Still, reassigning this bug report to the right D-I package. Thanks for your suggestion. If the installer has a choice of .iso images, shouldn't it ask which one(s) to use? (Obviously, this choice should be pre-seed-able...) Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
I'm getting ready to try this Friday. What URL should I use to download the Debian Installer from? Thanks! Rick On Jan 6, 2009, at 3:59 PM, Martin Michlmayr wrote: * Rick Thomas rbtho...@slug.rcthomas.org [2008-12-30 19:12]: One thing worth mentioning though: I have a full-service DHCP on this subnet, so it got the network parameters from DHCP. This was successful, but for some reason it decided that the DNS domain was example.org, not the one being offered by DHCP. The text example.org showed up in the following places: I need some more information on this. Please make a backup of your flash with cat /dev/mtdblock? mtd-backup and copy it to your machine, so you can later write it back to the NSLU2 with upslug2. Then download the Debian installer image again and load it with upslug2. When you connect to the installer, open a shell and run the following commands. Please send me the output. cat /var/lib/dhcp3/dhclient.leases debconf-get netcfg/get_hostname debconf-get netcfg/get_domain cat /preseed.cfg You can then flash mtd-backup with upslug2 to get back into your system. Thanks. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
On Jan 6, 2009, at 3:59 PM, Martin Michlmayr wrote: * Rick Thomas rbtho...@slug.rcthomas.org [2008-12-30 19:12]: One thing worth mentioning though: I have a full-service DHCP on this subnet, so it got the network parameters from DHCP. This was successful, but for some reason it decided that the DNS domain was example.org, not the one being offered by DHCP. The text example.org showed up in the following places: I need some more information on this. Please make a backup of your flash with cat /dev/mtdblock? mtd-backup and copy it to your machine, so you can later write it back to the NSLU2 with upslug2. Then download the Debian installer image again and load it with upslug2. When you connect to the installer, open a shell and run the following commands. Please send me the output. cat /var/lib/dhcp3/dhclient.leases debconf-get netcfg/get_hostname debconf-get netcfg/get_domain cat /preseed.cfg You can then flash mtd-backup with upslug2 to get back into your system. Thanks. -- Martin Michlmayr http://www.cyrius.com/ OK, Here's the output (there was *no* file /var/lib/dhcp3/dhclient.leases ) ~ # ls -l /var/lib/dhcp3/ ~ # debconf-get netcfg/get_hostname slug ~ # debconf-get netcfg/get_domain example.org ~ # cat /preseed.cfg d-i ethdetect/use_firewire_ethernet boolean false d-i lowmem/low note d-i netcfg/get_hostname string debian d-i netcfg/get_domain string example.org d-i network-console/password password install d-i network-console/password-again password install d-i partconf/already-mounted boolean false d-i netcfg/choose_interface select eth0 d-i netcfg/get_ipaddress string 192.168.1.177 d-i netcfg/get_netmask string 255.255.255.0 d-i netcfg/get_gateway string 192.168.1.254 d-i netcfg/get_nameservers string 192.168.1.118 192.168.1.138 192.168.1.254 d-i netcfg/confirm_static boolean true d-i netcfg/disable_dhcp boolean true d-i netcfg/get_hostname string slug ~ # In re-reading your doc Installing Debian on NSLU2 at http:// www.cyrius.com/debian/nslu2/install.html I saw (not for the first time, but never before looking for things that had to do with DHCP) the paragraph: If you have configured your network settings through the Linksys web interface to use a static IP address, these values will be used (including the hostname). which reminded me that I had done exactly that -- use the Linksys web interface to set up a static IP: 192.168.1.177 . This doesn't make it any less of a bug, but it may put the behavior in a different light. Hope this helps! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
On Jan 12, 2009, at 3:43 PM, Martin Michlmayr wrote: * Rick Thomas rbthoma...@pobox.com [2009-01-12 10:13]: If you send me a copy of your /dev/mtdblock1, I can verify whether you set a domain name or not. Here you go. Yep, no domain is set. Assuming that I did not set a domain back when I had the Linksys firmware installed... What can I do *now* to set it right and get my parameters from DHCP? I assume you don't want to do a new installation, right? Actually, I bought this slug specifically for the purpose of helping test new d-i versions, so the truth is: Yes, I do want to do a new installation -- lots of them as new versions of d-i come out (and I have time for testing and writing up my results, of course!). So the questions really are these: 1) What part of the current d-i documentation or d-i software needs to be modified so that normal folks don't make the same mistake I did. 2) Assume a user has a slug they've been using with the Linksys software for a while and wants to switch to Debian: What should they do to make sure d-i gets their network configuration right without having to resort to the fixups you describe below? 3) Is there any way to have d-i offer slug users the same kind of network configuration options as are considered normal for users of other systems? For example, it appears that there is room for some user-definable data at the end of the flash image (see the -- payload option in the upslug2 man page). Can that be used to preseed some d-i parameters, such as networking configuration? 4) And specific to my own case: Do I have to re-flash with the Linksys software to repair the network configuration for the next time I want to do a test install? Or is there a simpler way that can be done from the existing Debian setup? If d-i uses info from DHCP for the hostname and domain, it will write it to /etc/hosts, hostname, etc. The installed Debian system doesn't use DHCP for this. So you simply need to change /etc/hosts, hostname and every other file that mentions example.org and change it to something else. This will show you the files: grep -r example.org /etc The other question is whether your NSLU2 should obtain an IP address via DHCP or use the static address. If it should use DHCP, you have to edit /etc/network/interfaces Thanks! In fact, the above fixup is pretty much what I wound up doing. Is there a note somewhere in the wiki or install notes or somewhere that says what to do in a case like this? Not really... at least not explicitly. But my install page describes where d-i gets the network values from. That's true. And, as I said, when I looked with the right questions in mind, the answer was staring me in the face. But when I started out, it wasn't obvious what questions I should be asking, so I missed the significance of that part of your documentation. It was ever thus: The history of computer programming is a race between the software developers to make bigger and better and more idiot proof software, and the Universe to make bigger and better idiots. So far the Universe is winning! None of which excuses us from the duty of continually improving our software and documentation. Let me know if there's anything you'd like me to do along those lines... Thanks for all your help! I hope my experience was useful for you too, and it results in an improved experience for other slug users. Rick -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
On Jan 13, 2009, at 2:58 AM, Martin Michlmayr wrote: * Martin Michlmayr t...@cyrius.com [2009-01-13 08:23]: 3) Is there any way to have d-i offer slug users the same kind of network configuration options as are considered normal for users of other systems? For example, it appears that there is room for some user-definable data at the end of the flash image (see the --payload option in the upslug2 man page). Can that be used to preseed some d-i parameters, such as networking configuration? Good question; I don't know. Maybe you can investigate. But this would require users to regenerate the image... Sorry, I was wrong here. Yeah, this sounds like an interesting approach. I don't think regenerating the image should be necessary. If -- payload can be used along with the image you provide, then there could be code in the image that looks to see if the payload area has something that looks like a preseed (maybe a magic number or checksum or timestamp or something else to be reasonably sure we're not being fooled by random data or by stuff left-over from the last d- i.) If there is, it can use it, if not, it can ignore it. And the preseed can be quite general, not just for network configuration, though I assume that network configuration would be one very common use. If '--prefix' can't be used, then maybe just concatenating the (suitably encapsulated) preseed on the end of the image? Or am I missing something? I don't know much about the internals of the upslug2 process, so I'm sure there's plenty I could be missing. Is there documentation beyond the upslug2 man page I could look at? In particular, I gather that the program on the slug end of the upslug2 process is called redboot -- is that correct? Is there a Linksys manual or technical paper describing redboot? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
On Jan 13, 2009, at 2:23 AM, Martin Michlmayr wrote: 2) Assume a user has a slug they've been using with the Linksys software for a while and wants to switch to Debian: What should they do to make sure d-i gets their network configuration right without having to resort to the fixups you describe below? ... the docs clearly say that a) the network configuration has to be complete when you use a static IP address and b) if you configure the Linksys firmware to use DHCP that will be used. So to make sure d-i gets it right you either have to: a) put in all values in the Linksys firmware or b) tell the Linksys firmware to use DHCP and configure your DHCP server properly. I think both are pretty clear. Maybe I should explicitly mention hostname and domain somewhere, though... The docs are clear if you know what you're looking for. If you don't, it's easy to miss the important stuff. (This is, of course universally true, and not a solvable problem in general. But in this specific instance...) I think explicitly mentioning domain as well as hostname and IP- address should be all that's required. The existing docs mention in a general way what happens if parameters are missing, but do not provide a complete list of needed parameters. So maybe a footnote giving the complete list of network configuration parameters that the d-i will use if it can get them out of the mtdblock1 area (IP-address, netmask, gateway address, DNS server, hostname, domain -- have I missed anything?) and some details on what it will do if any of them are missing? Maybe I'm just over-thinking the problem because it happened to be me who got bitten by it. In any case, Thanks! for all your efforts. The slug is a really neat little box, and your work makes it really easy for general users like me to join in the fun. I'm grateful. Enjoy! Rick PS: I'll leave it to you to close this bug if you think it's served its purpose. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Hardcoding of ext3 as partman's default filesystem
On Wed, Jan 28, 2009 at 11:24:57AM +, Colin Watson wrote: How about a partman/default_filesystem template in partman-base, defaulting to ext3, and then a $default expansion in the filesystem field in partitioning recipes? That would make it a matter of a boot parameter to change the default filesystem, and would make the code a bit more elegant IMO. Great idea! Wishlist request from a user: Please take care to not restrict it to ext3/ext4 only. For example, in the embedded computing market, it might be nice to be able to default to jffs2. Or, if your chosen mass- storage media is a thumb flash-drive, the default could be ext2 with the relatime option. Or, for some other kinds of application environments, XFS or reiser, etc. I realize this has greater implications in more than than just the spots that Colin pointed out. Fully implementing complete flexibility will probably not be possible. But at least, don't let the proposed changes close off the potential. Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
I just tried the PowerPC squeeze businesscard install disk, with the same results. The CD was downloaded from the URL: http://cdimage.debian.org/cdimage/daily-builds/testing/arch-latest/powerpc/iso-cd/ The boilerplate on that directory says: Daily build #3 for powerpc, using installer build from squeeze These images will install the testing version of Debian, currently Squeeze. See the top-level daily directory for more information about the daily builds. This build finished at Tue Mar 24 15:56:34 UTC 2009. The CD booted fine, it ran thru the normal process of picking a language and keyboard type, loading modules, etc then tried to DHCP a network address. This failed because there's no DHCP server on that network. I manually configured the network numbers, and it got its name from the DNS server (so I didn't fat-finger the network configuration) Then it was time to configure a mirror, and I chose the default: ftp.us.debian.org . This resulted in the Bad archive mirror error. When I switch to the alt-F2 console and try to do a wget, I get a segmentation fault. I tried the PowerPC netinst install CD from the same directory, with the same results. Hope this helps to analyze the bug... Rick On Mar 22, 2009, at 5:38 AM, Alexander V.Inyakin wrote: Package: installation-reports Severity: critical Justification: breaks the whole system -- Package-specific info: Boot method: CD Image version: debian-testing-i386-netinst.iso22-Mar-2009 05:02 152M Date: 10:00 22.03.2009 Machine: Compaq CQ60 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O ] Detect network card:[O ] Configure network: [O ] Detect CD: [O ] Load installer modules: [O ] Detect hard drives: [O ] Partition hard drives: [O ] Install base system:[O ] Clock/timezone setup: [O ] User/password setup:[O ] Install tasks: [E ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Configuring package manager the squeeze netinst gives Bad archive mirror message at any archive beginning from ftp.us.debian.org -- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520711: syslog from a failed install
syslog.gz Description: GNU Zip compressed data
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
On Mar 24, 2009, at 10:09 PM, Otavio Salvador wrote: On Tue, Mar 24, 2009 at 6:02 PM, Rick Thomas rbthoma...@pobox.com wrote: When I switch to the alt-F2 console and try to do a wget, I get a segmentation fault. Please take a look on the syslog of the installer and if possible attach it to this bug report (please, gzip it). The syslog file of a failed install has been sent to the 520711 bug report. I glanced at it, but I'm not a d-i guru (just a [usually] happy user). The only thing I noticed was a few occurrences of Mar 25 03:36:30 main-menu[695]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Mar 25 03:36:30 main-menu[695]: DEBUG: resolver (libc6): package doesn't exist (ignored) But they are probably harmless because they were followed eventually by Mar 25 03:36:36 anna[3512]: DEBUG: retrieving libc6-udeb 2.9-4 so something else will be needed to explain the seg-fault in wget. This particular installation attempt was done on a network that did have DHCP, so the syslog shows it succeeding -- no manual network configuration was required. From this I assume I can deduce that the network was up and working, so it's not a matter of having the wrong (or no) network driver... Hope it helps... Rick PS: I assume that Otavio and Alexander are subscribed to the PowerPC list or the 520711 bug report (or both) so I've trimmed them off the CC list. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
On Mar 25, 2009, at 7:37 AM, Otavio Salvador wrote: On Wed, Mar 25, 2009 at 3:09 AM, Christian Perrier bubu...@debian.org wrote: Quoting Otavio Salvador (ota...@ossystems.com.br): On Tue, Mar 24, 2009 at 6:02 PM, Rick Thomas rbthoma...@pobox.com wrote: When I switch to the alt-F2 console and try to do a wget, I get a segmentation fault. Please take a look on the syslog of the installer and if possible attach it to this bug report (please, gzip it). Isn't the wget segfault mentioned by Rick enough to explain the problem? I was interested to check if we had any kernel trace on syslog or something like that. Two thoughts: 1) Is there some debugging parameter you'd like me to set so that it gives more information? I have a spare machine I can use for testing this, so I can give good turnaround on test-cases. 2) Since this bug renders the install CDs (certainly buisnesscard, and for most practical purposes netinst) completely unusable for their intended purpose, can we raise the severity of this bug to (e.g.) Serious? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
If it helps any, I tried the same thing on an amd64 machine, with the following results (manually typed from the ALT-F4 screen): kernel: wget: segfault at ... error 7 in libresolv-2.9.so after trying wget http://www.amazon.com/; but if I try wget http://72.21.207.65/; (that's the numeric IP address that corresponds to www.amazon.com) it successfully retrieves an index.html file, and there is no error message in the ALT-F4 screen. Can we conclude that there is at least one bug in the libresolv-2.9 library module that's included in the squeeze d-i initrd. What does that tell us about which package the bug belongs to? Thanks! Rick On Mar 26, 2009, at 2:34 AM, Christian Perrier wrote: Quoting Rick Thomas (rbthoma...@pobox.com): 2) Since this bug renders the install CDs (certainly buisnesscard, and for most practical purposes netinst) completely unusable for their intended purpose, can we raise the severity of this bug to (e.g.) Serious? As long as it is assigned to installation-reports, that won't change much things. Two things should be done: -identify that package the bug belongs to (the wget segafult seems to be the best candidate here) - document the issue on DebianInstaller/Today in the wiki -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520442: amd64 netinst netcfg segfault daily build 03/19/2009
This is the same bug as #520711 Rick On Mar 19, 2009, at 4:19 PM, Stanley Pinchak wrote: Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: Thu, 19 Mar 2009 15:53:44 -0400 (roughly) Machine: Toshiba Satellite 305D Processor: Turion Ultra X2 (amd64) Memory: 4GB Partitions: N/A Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge [1022:9600] 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0) [1022:9603] Kernel driver in use: pcieport-driver 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0) [1022:9604] Kernel driver in use: pcieport-driver 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1) [1022:9605] Kernel driver in use: pcieport-driver 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2) [1022:9606] Kernel driver in use: pcieport-driver 00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 3) [1022:9607] Kernel driver in use: pcieport-driver 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode] [1002:4390] Kernel driver in use: ahci Kernel modules: ahci 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 3a) 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] Kernel driver in use: ATIIXP_IDE Kernel modules: atiixp 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 11h HyperTransport Configuration [1022:1300] (rev 40) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 11h Address Map [1022:1301] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 11h DRAM Controller [1022:1302] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 11h Miscellaneous Control [1022:1303] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 11h Link Control [1022:1304] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3650 [1002:9591] 01:00.1 Audio device [0403]: ATI Technologies Inc RV635 Audio device [Radeon HD 3600 Series] [1002:aa20] 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02) Kernel driver in use: r8169 Kernel modules: r8169 05:00.0 Network controller [0280]: Atheros Communications Inc. Device [168c:002a] (rev 01) 07:06.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05) Kernel driver in use: ohci1394 Kernel modules: ohci1394 07:06.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22) Kernel driver in use: sdhci Kernel modules: sdhci 07:06.2 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12) 07:06.3 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 12) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [O] I think that this occurred prior to the network configuration Load installer modules: [O]I think that this occurred prior to the network configuration Detect hard drives: [ ] Partition hard drives: [ ] Install base system:
Bug#520711: same bug a #520442
This seems to be the same bug as #520442 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Best way to install a new session manager
After installing from the default CD (e.g. businesscard) I'd like to make other session managers than Gnome available. (e.g. xfce or kde). What's the best way to do that so as to get all packages installed the same way they would have been had I used the associated install CD? Is this in the manuals or wiki somewhere? If not, would it be a good idea to do that? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
powerpc testing install CDs out of date?
Since the iso's in http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/ still date from January, I assume that the new hardware for building powerpc packages hasn't been installed yet. If there an expected time of arrival for this? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: powerpc dailies back
On Apr 20, 2009, at 7:50 AM, Wouter Verhelst wrote: As I type this, the first of the dailies built on country (my old laptop) is being uploaded to people.debian.org Cool! Thanks for the good work. Can I assume that the following will soon be repaired if I'm patient? namely, that the iso's in http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/ all date from Fri Jan 23 03:30:35 UTC 2009. Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ppc64 port
On Apr 21, 2009, at 10:36 AM, Frans Pop wrote: On Tuesday 21 April 2009, Frans Pop wrote: On Tuesday 21 April 2009, Wartan Hachaturow wrote: While digging through d-i, I've noticed some signs of ppc64 port (which was, as far as I remember, a heroic attempt to make a 64-bit userland Debian port). Do we actually need it and is anybody going to support/maintain it? It's been added in D-I on request of the ppc64 porters, but we have not heard anything from them for the last 2-3 years. I've looked at the ppc64 mailing list some time last year and to me it looked like the initiative was completely dead. We've always made it clear that ppc64 would have to be maintained by the porters. This has not been done. I currently see no keep ppc64 reasons to --^ support in D-I. Cheers, FJP Isn't it needed to support the Apple G5 machines? Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-image-powerpc has the same broken dependency...
This bug prevents an expert mode install from properly installing Sid unless you chose a non-default kernel. Instead of depending on linux-image-2.6.26-2-powerpc, in Sid, it should depend on linux-image-2.6.29-1-powerpc, because 2.6.26-2 doesn't exist in Sid. The 2.6.26 version may (I haven't checked) exist in squeeze. But, unless you have both sid and squeeze repos in your sources.list, it's not available on a Sid system. Is there some way this sort of thing could be automated? So that when a new latest linux-image package is put in the repository, the packages that should depend on it get automatically updated? Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
PowePC sid_d-i daily builds are not happening...
On May 24, 2009, at 2:39 AM, Rick Thomas wrote: http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/ says that This build finished at Mon May 18 22:27:07 UTC 2009. That's almost a week ago. I'd like to test a new sid installation on one of my Macs but until this is fixed, I can't. Any idea when it will be working again? This has not changed in the last week. It still says May 18th, 2009. What is wrong and what can we do to fix it? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#390565: Patch for the graphical installer on PPC boxes
On Oct 1, 2006, at 7:34 PM, Sven Luther wrote: I have built the images, and tested it on radeon with the 9200SE, i confirm that disable-module=radeon is uncomented, and the bugs (white-on- white during selection, broken font in the console) are gone this way. I am uploading the images i built to http://people.debian.org/ ~luther/g-i so we others can test. I will do an announcement on debian-powerpc now. When I tried this mini.iso on a G4/533MHz QuickSilver tower with ATY Rage128 graphics, I saw the white-on-white problem. So it's not gone away completely. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#390565: Patch for the graphical installer on PPC boxes
On Oct 2, 2006, at 3:34 AM, Sven Luther wrote: When I tried this mini.iso on a G4/533MHz QuickSilver tower with ATY Rage128 graphics, I saw the white-on-white problem. So it's not gone away completely. Normal, your aty rage128 is not a radeon, and is thus using whatever driver is using the aty rage128, and thus the white-on-white problem is not gone for you. Can you check which graphic driver you are using, and submit a modification of attilio's patch so you also disable the aty-rage128 driver ? Happy to do... Can you tell me how to check which graphic driver it's using? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#390565: Patch for the graphical installer on PPC boxes
On Oct 2, 2006, at 2:28 PM, Sven Luther wrote: I am building a new image, and uploading it, stay tuned. I tried the new image (from http://people.debian.org/~luther/g-i/ powerpc/gtk-miniiso/mini.iso dated 02-Oct-2006 05:07) on my PowerMac 3,5 with the Radeon video card. /proc/cpuinfo= PowerMac3,5 [69 (PowerMac G4/733MHz Silver)] lspci= ATI Technologies Inc Radeon RV200 QW [Radeon 7500] /proc/fb= 0 ATI Radeon QW When I did DEBIAN_FRONTEND=gtk ; debian-installer, I got dropped into the text mode installer with the error message: Framebuffer not available. Disabling graphical frontend. I tried it with all combinations of enable/disable of linux_input and radeon, with the same results. I also tried it on another machine with ATI Rage128 graphics card /proc/cpuinfo= PowerMac3,1 (PowerMac G4 AGP Graphics) lspci= ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS /proc/fb= 0 ATY Rage128 I only did this one with both disables in place (unmodified /etc/ directfbrc file). It also gave me the same error message about Framebuffer not available and dropped me in the text mode installer. Is it possible that this image is broken in some fundamental way? Hope this helps! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#390565: Patch for the graphical installer on PPC boxes
On Oct 3, 2006, at 4:10 AM, Attilio Fiandrotti wrote: Did you enter export DEBIAN_FRONTEND=gtk or DEBIAN_FRONTEND=gtk before running debian-installer? In the latter case, the DEBIAN_FRONTEND variable simply may not have been made visible to debconf, try again with export ... before running debian-installer and let's see if this works. My bad. My brain knew what it had to do, but the message didn't make it all the way to my fingers! In any case, the results of doing it again (right, this time) [on the PowerMac3,5 with Radeon] are attached. No change, as far as I can see. Hope it helps! Rick error_messages4 Description: Binary data error_messages3 Description: Binary data error_messages2 Description: Binary data error_messages1 Description: Binary data configuration Description: Binary data
Bug#381875: loop-AES key generation requires tiresome typing
On Oct 10, 2006, at 3:39 PM, James Westby wrote: I had a couple of idea while I was typing to generate keys in this fashion. Here they are in no particular order. 1) Make a game that involves typing, Doesn't aptitude have a minesweeper game built in? Would that work? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I RC1 - release planning - soft freeze for changes in SVN
On Oct 16, 2006, at 12:01 PM, Frans Pop wrote: Please start testing the installer for all architectures NOW All udebs with functional changes have now been uploaded, so this is an excellent time to test different architectures using *daily* images! Hmmm... The daily images directory http://cdimage.debian.org/cdimage/daily- builds/daily/arch-latest/powerpc/iso-cd/ is empty and seems to have been that way since October 9th. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer - Call for testing *this week*
On Oct 17, 2006, at 8:20 AM, Frans Pop wrote: - graphical installer, especially whether your mouse and touchpad work correctly Where is the latest mini.iso for the powerpc version of the graphical installer? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdimage.debian.org presents different faces for ftp and http access
Pointing my browser at http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ powerpc/iso-cd/ redirects me to http://ftp.acc.umu.se/cdimage/daily-builds/daily/arch-latest/ powerpc/iso-cd/ which contains Index of /cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd Icon Name Last modified Size [DIR] Parent Directory - [ ] MD5SUMS 22-Oct-2006 04:02 143 [ ] debian-testing-powerpc-businesscard.iso 22-Oct-2006 04:00 54M [ ] debian-testing-powerpc-businesscard.iso.zsync22-Oct-2006 04:00 190K [ ] debian-testing-powerpc-netinst.iso 22-Oct-2006 04:01 166M [ ] debian-testing-powerpc-netinst.iso.zsync 22-Oct-2006 04:02 292K Apache/2.2.3 (Unix) Server at ftp.acc.umu.se Port 80 but pointing my browser at ftp://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ powerpc/iso-cd/ which contains Index of ftp://cdimage.debian.org/cdimage/daily-builds/daily/arch- latest/powerpc/iso-cd/ Up to higher level directory File: MD5SUMS 1 KB10/25/063:53:00 AM File: debian-testing-powerpc-businesscard.iso 55596 KB 10/25/06 3:51:00 AM File: debian-testing-powerpc-businesscard.iso.zsync 191 KB 10/25/06 3:51:00 AM File: debian-testing-powerpc-netinst.iso 170560 KB 10/25/06 3:53:00 AM File: debian-testing-powerpc-netinst.iso.zsync 292 KB 10/25/06 3:53:00 AM Note the difference in dates of the .iso files... Something strange is happening. Is it a Halloween prank? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: cdimage.debian.org presents different faces for ftp and http access
Rick Thomas wrote: From: Rick Thomas [EMAIL PROTECTED] Date: October 25, 2006 8:44:01 PM EDT To: Installer Debian debian-boot@lists.debian.org, debian- [EMAIL PROTECTED] Subject: cdimage.debian.org presents different faces for ftp and http access Pointing my browser at http://cdimage.debian.org/cdimage/daily-builds/daily/arch- latest/powerpc/iso-cd/ redirects me to http://ftp.acc.umu.se/cdimage/daily-builds/daily/arch-latest/ powerpc/iso-cd/ which contains Index of /cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd Icon Name Last modified Size [DIR] Parent Directory - [ ] MD5SUMS 22-Oct-2006 04:02 143 [ ] debian-testing-powerpc-businesscard.iso 22-Oct-2006 04:00 54M [ ] debian-testing-powerpc-businesscard.iso.zsync22-Oct-2006 04:00 190K [ ] debian-testing-powerpc-netinst.iso 22-Oct-2006 04:01 166M [ ] debian-testing-powerpc-netinst.iso.zsync 22-Oct-2006 04:02 292K Apache/2.2.3 (Unix) Server at ftp.acc.umu.se Port 80 but pointing my browser at ftp://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ powerpc/iso-cd/ which contains Index of ftp://cdimage.debian.org/cdimage/daily-builds/daily/arch- latest/powerpc/iso-cd/ Up to higher level directory File: MD5SUMS 1 KB 10/25/063:53:00 AM File: debian-testing-powerpc-businesscard.iso 55596 KB 10/25/06 3:51:00 AM File: debian-testing-powerpc-businesscard.iso.zsync 191 KB 10/25/06 3:51:00 AM File: debian-testing-powerpc-netinst.iso 170560 KB 10/25/06 3:53:00 AM File: debian-testing-powerpc-netinst.iso.zsync 292 KB 10/25/06 3:53:00 AM Note the difference in dates of the .iso files... Something strange is happening. Is it a Halloween prank? Rick On Oct 25, 2006, at 9:45 PM, Frans Pop wrote: On Thursday 26 October 2006 02:44, Rick Thomas wrote: Pointing my browser at http://cdimage.debian.org/cdimage/daily-builds/daily/arch- latest/ powerpc/iso-cd/ redirects me to http://ftp.acc.umu.se/cdimage/daily-builds/daily/arch-latest/ powerpc/iso-cd/ [...] Note the difference in dates of the .iso files... The images are different too as the MD5SUM files can tell you. Something strange is happening. Is it a Halloween prank? Looks like the ftp server already has the new images that have only just been built and the http server still needs to be synced. If the difference is still there in a few hours, please mail to the debian-cd list to report the issue. I don't think it's a slow sync. It's now three hours after I posted the original question, and the problem persists. Also, note that the dates of the files are three days apart. Curiouser and curiouser cried Alice... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397649: install-report: NTP sync missing by default
On Nov 11, 2006, at 5:24 PM, Geert Stappers wrote: Op 08-11-2006 om 20:09 schreef Olaf van der Spek: Also, no NTP synchronization is available by default. I really think Debian should install. Maybe install but disable, although I'd prefer it to be enabled by default. The Debian-installer installs by default the packages with priority standard. Cheers Geert Stappers Who thinks it is stupid to install NTP by default. Installing ntp by default (making it have priority standard) would be good for the many Debian users who have always-on network access. But it would be a problem for the minority who have no or only intermittent (e.g. dial-up) network access. An argument in favor of making it standard is that it would greatly improve the overall state of timekeeping on the internet. This is of not just a time-geek issue. Better time distribution has lots of practical advantages. An argument in favor of leaving it optional is that requiring people without good network access to install in expert mode (to avoid getting ntp installed) is an imposition on a class of users who are individually more likely to be non-experts. I leave it to the PTBs to figure out whether there is a compromise position. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is cdimage.debian.org having trouble?
For the last few days, I've had great difficulty downloading from cdimage.debian.org (mostly daily installer images for testing). Bandwidth is highly erratic and overall very slow. I'm in New Jersey, USA. If that makes any difference. Does anybody know of a mirror for cdimage.d.o on this side of the Atlantic that carries the daily and weekly installer builds? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397649: install-report: NTP sync missing by default
On Nov 22, 2006, at 1:05 PM, Olaf van der Spek wrote: reopen 397649 thanks Could we have NTP by default? But it would be a problem for the minority who have no or only intermittent (e.g. dial-up) network access. Why would it be a problem? No network mean the Network Time Protocol won't work. Intermittent network (e.g. dial-up) means that NTP goes for long periods with no connection to the external time servers. The ntpd daemon is (mostly) OK with that, but some auto-dialers may see it's occasional polls as a reason to dial the ISP, which is probably not what the user expected. I leave it to the PTBs to figure out whether there is a compromise position. PTBs? Powers That Be (From the US TV show Buffy the Vampire Slayer) Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397649: install-report: NTP sync missing by default
On Nov 22, 2006, at 4:18 PM, Olaf van der Spek wrote: Rick Thomas wrote: No network mean the Network Time Protocol won't work. Intermittent network (e.g. dial-up) means that NTP goes for long periods with no connection to the external time servers. The ntpd daemon is (mostly) OK with that, but some auto-dialers may see it's occasional polls as a reason to dial the ISP, which is probably not what the user expected. NTP could be at least installed but disabled instead of not installed. What's the point of installing something you're not going to enable? It's not that much harder to type aptitude install ntp than it is to type update-rc.d ntp defaults Although I'd like to have it enabled by default. Isn't it possible to start/stop ntpd based on when the dial-up link is up? Theoretically, yes. In practice, it would be a pain to get all the little fiddly bits exactly right -- not something I'd want to undertake. -- Olaf van der Spek http://xccu.sf.net/ Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IMPORTANT: Significant changes to CD/DVD build setup
On Nov 23, 2006, at 8:58 AM, Steve McIntyre wrote: 2) dinstall and the mirror pulse are now happening twice daily, which means we will get two daily build runs. *Right* now the second daily build will automatically overwrite the first each day, but I'm going to change the scripts on farbror and bla to keep both, as date-1 and date-2. The arch-latest links will still be kept up-to-date to keep external links pointing at the latest build. Any comments, please let me know... Occasionally, in the past, it has happened by accident that there were two daily builds done on the same day. As you note, the second one overwrote the first. This caused some confusion as the two were significantly different in their behavior (at least the one time I'm thinking of particularly) and it took me a while to figure out that they were different builds, and I wasn't going crazy! So, I ask that you code it is a way that if three or more daily builds just happen to get done in one day, it won't overwrite anything. Maybe a name scheme based on the date, hour, and minute of the build? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IMPORTANT: Significant changes to CD/DVD build setup
On Nov 23, 2006, at 1:52 PM, Steve McIntyre wrote: The system as it's set up now will increment a build number for each build it does, resetting to 1 again as the day changes. Hopefully that will suffice for you...? That will work. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397649: install-report: NTP sync missing by default
On Nov 25, 2006, at 3:01 PM, Kurt Roeckx wrote: On Sun, Nov 12, 2006 at 03:57:25PM -0500, Rick Thomas wrote: Installing ntp by default (making it have priority standard) would be good for the many Debian users who have always-on network access. But it would be a problem for the minority who have no or only intermittent (e.g. dial-up) network access. For ntpd to really work properly you need a static IP address. Well... I'd say stable rather than static. If the local IP address changes once a week, an NTP client will have little trouble weathering the change. Once an hour would be problematical. Once a day is in the grey area. Depending on the details, it may be desirable to restart the ntpd daemon when the IP address changes. For an NTP *server* to be effective as a server, a very stable IP address is, of course, mandatory. But most Debian users don't run NTP servers, and those who do know what they're doing and what is required to do it right. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: signature invalid: BADSIG 010908312D230C5F Debian Archive Automatic Signing Key (2006)
On Dec 2, 2006, at 6:12 PM, Rick Thomas wrote: Does anybody know why I'm getting this message when I do aptitude update W: GPG error: http://mirrors.usc.edu etch Release: The following signatures were invalid: BADSIG 010908312D230C5F Debian Archive Automatic Signing Key (2006) [EMAIL PROTECTED] A couple of days ago, I was getting the same message, but from debian.lcs.mit.edu, instead of mirrors.usc.edu. Both sites are in my sources.list file. [EMAIL PROTECTED] wrote: Have you tried installing: http://packages.debian.org/unstable/misc/debian-archive-keyring The error message has moved back to debian.lcs.mit.edu. It's gone from mirrors.usc.edu for the time being. By removing the mit site from my sources.list file I was able to do aptitude update aptitude dist-upgrade which updated the debian-archive-keyring package to the November 22, 2006 version. But when I put the mit site back in, the error was still there. Anybody got any ideas? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: signature invalid: BADSIG 010908312D230C5F Debian Archive Automatic Signing Key (2006)
On Dec 6, 2006, at 3:43 AM, Florian Kulzer wrote: There seems to be some confusion between two different issues: 1) There is a new archive signing key for Etch. The Release files are currently signed with both the new and the old key. Apt is satisfied with the old signature, but it will alert you to the fact that there is an additional signature with a key that apt does not know. The error message is something like unknown key or unknown signature (I don't remember the exact wording right now). As others have already pointed out, installing the debian-archive-keyring will take care of this automatically, for now and for all new keys in the future. 2) The invalid signature error of gpg is something completely different. Apt knows the used keys but the Release files have incorrect signatures. In the worst-case scenario this means that someone has taken over the MIT site and tries to achieve world domination by putting doctored packages on people's computers. (The whole point of the archive signing is to protect you against this. If I manage to slip a manipulated package into your installation process then I can do more or less whatever I want on your machine since the installation scripts from this package will run with root privileges.) More likely, however, there is just a synchronization problem with the MIT mirror. You can get the bad signature error if you update while the mirror in the middle of its synchronization procedure. If you get this message all the time then you should send an email to the maintainer of the MIT mirror to make him/her aware of the problem. Thanks Florian! This helps. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402267: PowerPC Netinst CD Invalid Release File
Package: installation-reports Installing from the netinst CD on a PowerMac G4, I get the following error: [!!] Install the base system Debootstrap Error Invalid Release file: no entry for main/binary-powerpc/Packages. This is the netinst CD from: cdimage.debian.org:cdimage/daily-builds/sid_d-i/20061208-1/powerpc/ iso-cd Trying 130.239.18.138... -rw-r--r--1 1002 1002 143 Dec 08 10:34 MD5SUMS -rw-r--r--1 1002 1002 73390080 Dec 08 10:32 debian- testing-powerpc-businesscard.iso -rw-r--r--1 1002 1002 251055 Dec 08 10:32 debian- testing-powerpc-businesscard.iso.zsync -rw-r--r--1 1002 1002 192720896 Dec 08 10:34 debian- testing-powerpc-netinst.iso -rw-r--r--1 1002 1002 329558 Dec 08 10:34 debian- testing-powerpc-netinst.iso.zsync cdimage.debian.org is an alias for ftp.acc.umu.se. ftp.acc.umu.se has address 130.239.18.159 ftp.acc.umu.se has address 130.239.18.138 ftp.acc.umu.se has address 130.239.18.158 Curiously enough, if I use the Businesscard CD, I do not get this error. Any thoughts? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402267: More info
Curiously enough, the netinst CD does appear to have the missing file... $ ls -l dists/etch/main/binary-powerpc/ total 688 -rwxr-xr-x 1 rbthomas rbthomas 209980 Dec 8 10:33 Packages -rwxr-xr-x 1 rbthomas rbthomas 131702 Dec 8 10:33 Packages.gz -rwxr-xr-x 1 rbthomas rbthomas 84 Dec 8 10:33 Release -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402267: Not just powerpc -- x86 too [Re: Bug#402267: PowerPC Netinst CD Invalid Release File]
On Dec 9, 2006, at 1:01 AM, Rick Thomas wrote: Package: installation-reports Installing from the netinst CD on a PowerMac G4, I get the following error: [!!] Install the base system Debootstrap Error Invalid Release file: no entry for main/binary-powerpc/Packages. This is the netinst CD from: cdimage.debian.org:cdimage/daily-builds/sid_d-i/20061208-1/powerpc/ iso-cd Hmmm Bug#401586 seems to indicate that this may not be limited to the powerpc port. Bug#401586 is for x86. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402267: More info
On Dec 9, 2006, at 12:15 PM, Frans Pop wrote: Hi Rick, On Saturday 09 December 2006 07:49, Rick Thomas wrote: Curiously enough, the netinst CD does appear to have the missing file... Seems to me like the message is not about the presence of the file itself but rather that it is not listed _inside_ the file /cdrom/dists/etch/Release. Could you send us that file? Here it is... Presumably, the equivalent file on a businesscard install is coming from the mirror, not the CD? So you're not interested in what's on the businesscard CD in that place? Please let me know if you need that too. For what it's worth, this also happened about a week ago, but I figured it was a transient error and didn't report it then. I've been out of town for the intervening time. But now I'm back and ready to pursue the issue. Etch obviously can't release until this is diagnosed and fixed. Release Description: Binary data Rick
Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot
Package: debian-installer Severity: normal After installing etch from a daily netinst CD (2006/12/10 20:42 UTC) on my beige G3 (OldWorld) PowerMac machine, the builtin ethernet interface is disabled. This box has two ethernet interfaces: eth0: D-Link RTL8139 eth1: builtin bmac on the motherboard eth0 is not connected to anything (for the time being). eth1 is connected to the local ethernet. doing ifdown eth1 ifup eth1 restores things to normal. There is a strange and possibly relevant thing in syslog Dec 11 02:34:47 debian NetworkManager: information^Ieth1: Driver 'bmac' does not support carrier detection. ^IYou must switch to it manually. Here's the output of lspci -nn 00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40) 00:0d.0 Ethernet controller [0200]: D-Link System Inc RTL8139 Ethernet [1186:1300] (rev 10) 00:0e.0 SCSI storage controller [0100]: Artop Electronic Corp ATP865 [1191:0009] (rev 06) 00:0f.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 13) 00:10.0 Unknown class [ff00]: Apple Computer Inc. Heathrow Mac I/O [106b:0010] (rev 01) 00:12.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] [1002:4754] (rev 9a) 01:08.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 41) 01:08.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 41) 01:08.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 02) 01:0b.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) [104c:8020] Here's the output of grep -i -C 10 eth /var/log/syslog.0 Dec 11 02:34:35 debian syslogd 1.4.1#18: restart. Dec 11 02:34:36 debian dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 Dec 11 02:34:36 debian dhclient: DHCPOFFER from 192.168.1.138 Dec 11 02:34:36 debian dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Dec 11 02:34:36 debian dhclient: DHCPACK from 192.168.1.138 Dec 11 02:34:36 debian dhclient: bound to 192.168.1.188 -- renewal in 8564 seconds. Dec 11 02:34:36 debian kernel: klogd 1.4.1#18, log source = /proc/kmsg started. Dec 11 02:34:36 debian kernel: Using PowerMac machine description Dec 11 02:34:36 debian kernel: Total memory = 384MB; using 1024kB for hash table (at cff0) Dec 11 02:34:36 debian kernel: Linux version 2.6.18-3-powerpc (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 Mon Dec 4 15:30:06 CET 2006 Dec 11 02:34:36 debian kernel: Found initrd at 0xc0377000:0xc0890cf4 Dec 11 02:34:36 debian kernel: Found a Heathrow mac-io controller, rev: 1, mapped at 0xfdf8 Dec 11 02:34:36 debian kernel: PowerMac motherboard: PowerMac G3 (Gossamer) Dec 11 02:34:36 debian kernel: Found Grackle (MPC106) PCI host bridge at 0x8000. Firmware bus number: 0-1 -- Dec 11 02:34:36 debian kernel: NET: Registered protocol family 1 Dec 11 02:34:36 debian kernel: NET: Registered protocol family 17 Dec 11 02:34:36 debian kernel: Freeing unused kernel memory: 180k init Dec 11 02:34:36 debian kernel: usbcore: registered new driver usbfs Dec 11 02:34:36 debian kernel: usbcore: registered new driver hub Dec 11 02:34:36 debian kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) Dec 11 02:34:36 debian kernel: PCI: Enabling device :01:08.0 (0014 - 0016) Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.0: OHCI Host Controller Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.0: new USB bus registered, assigned bus number 1 Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.0: irq 18, io mem 0x81803000 Dec 11 02:34:36 debian kernel: 8139too Fast Ethernet driver 0.9.27 Dec 11 02:34:36 debian kernel: PCI: Enabling device :00:0d.0 (0004 - 0007) Dec 11 02:34:36 debian kernel: eth0: RealTek RTL8139 at 0x1000, 00:40:05:35:ef:ff, IRQ 23 Dec 11 02:34:36 debian kernel: eth0: Identified 8139 chip type 'RTL-8100B/8139D' Dec 11 02:34:36 debian kernel: ieee1394: Initialized config rom entry `ip1394' Dec 11 02:34:36 debian kernel: SCSI subsystem initialized Dec 11 02:34:36 debian kernel: eth1: BMAC at 00:05:02:fe:55:50 Dec 11 02:34:36 debian kernel: usb usb1: configuration #1 chosen from 1 choice Dec 11 02:34:36 debian kernel: hub 1-0:1.0: USB hub found Dec 11 02:34:36 debian kernel: hub 1-0:1.0: 3 ports detected Dec 11 02:34:36 debian kernel: mesh: configured for synchronous 5 MB/s Dec 11 02:34:36 debian kernel: hda: ATAPI 24X CD-ROM drive, 128kB Cache, DMA Dec 11 02:34:36 debian kernel: Uniform CD-ROM driver Revision: 3.20 Dec 11 02:34:36 debian kernel: hdc: max request size: 128KiB Dec 11 02:34:36 debian kernel: PCI: Enabling device :01:08.1 (0014 - 0016) Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.1: OHCI Host Controller Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.1: new USB bus registered, assigned bus number 2 -- Dec 11 02:34:36 debian kernel: ieee1394: sbp2: Driver forced to
Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot
On Dec 11, 2006, at 2:08 PM, Frans Pop wrote: On Monday 11 December 2006 09:26, Rick Thomas wrote: After installing etch from a daily netinst CD (2006/12/10 20:42 UTC) on my beige G3 (OldWorld) PowerMac machine, the builtin ethernet interface is disabled. [...] There is a strange and possibly relevant thing in syslog Dec 11 02:34:47 debian NetworkManager: information^Ieth1: Driver 'bmac' does not support carrier detection. ^IYou must switch to it manually. So during the installation everything worked OK? Except for the mentioned problem with the bmac network interface, everything was pretty much as expected[*]. I boot this machine with the BootX bootloader. Up to now, etch has not worked with BootX. This is the first time it has been possible to do that since debian changed to 2.6.15 kernels. If we can get this bug fixed, I'll write up the full procedure step-by-step for the wiki. If this can't get fixed (or worked around) in time for etch release, it raises the question of whether or not to say that OldWorld PowerMacs are fully supported in this release. I'll leave that decision up to the release manager -- I'm just raising the question. [*] I had to use video=ofonly to get decent video. With sarge, I used to be able to use video=atyfb... but with this kernel, that gave a strange almost readable shimmery screen. I also had to explicitly state root=/dev/hde9 in the kernel parameters. This again was new from sarge. In sarge, I don't need to make that explicit. I'll do a full installation report if you think it would be useful. I'm also planning to do an installation from the businesscard CD. I'll do a full report on that if there's anything interesting. In that case I have no idea what to do with this report, especially if something like networkmanager is involved. As the initial dhcp setup seems to go fine (which means that eth1 was working at that point), I suspect that your problem is networkmanager's fault, or maybe a configuration issue. Joey: does this impact your decision to install networkmanager by default? The initial DHCP during the installation went fine -- I was able to retrieve lots of packages over the net during the tasksel part of the installation. It's just after rebooting into the installed system that the problem manifests. I'm not completely sure, but I *think* from looking at the log files, that the interface comes up and succeeds in doing DHCP early in the boot process, then is killed later on, possibly by Networkmanager? Would it be helpful to see what happens if I physically remove the extra ethernet card? Or if I install using the extra card instead of the bmac? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot
On Dec 11, 2006, at 4:31 PM, Joey Hess wrote: Frans Pop wrote: Joey: does this impact your decision to install networkmanager by default? It's a data point. I'd imagine that one can get networkmanager to deal with the interface by prodding it in the gui though. -- see shy jo In interesting image... (-8) Can you be a little more specific about how to go about doing this? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot
On Dec 11, 2006, at 5:39 PM, Joey Hess wrote: Rick Thomas wrote: In interesting image... (-8) Can you be a little more specific about how to go about doing this? If networkmanager is running I assume you are logged into a desktop environment that has some kind of netowork manager applet (in the status notification area in gnome for example). That applet can be used to configure it and make it use particular interfaces. Well, actually right now I'm logged in remotely via ssh -- the machine's at home and I'm at work. Last night, after booting, from the console, I ran ifdown eth1 ; ifup eth1 and it brought things back to normal. So ssh-ing in is possible -- until the next reboot. Given that (which may alter the results) nm-tool says: [EMAIL PROTECTED]:~$ nm-tool NetworkManager Tool State: disconnected - Device: eth0 NM Path: /org/freedesktop/NetworkManager/Devices/eth0 Type: Wired Driver:8139too Active:no HW Address:00:40:05:35:EF:FF Capabilities: Supported: yes Carrier Detect: yes Speed: 10 Mb/s Wired Settings Hardware Link: no - Device: eth1 NM Path: /org/freedesktop/NetworkManager/Devices/eth1 Type: Wired Driver:bmac Active:no HW Address:00:05:02:FE:55:50 Capabilities: Supported: yes Wired Settings Hardware Link: yes [EMAIL PROTECTED]:~$ When I do man NetworkManager I get a fairly skeletal man page that doesn't mention a gui. Similarly for man NetworkManagerDispatcher. Those two, and nm-tool, are all I get out of man -k NetworkManager. Is there anything more in the way of documentation I can look at? Should I be opening a bug report against networkmanager? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402547: NetworkManager: Workaround for OldWorld beige G3 Macintosh bmac network interface disabled on reboot
Package: networkmanager See bug number 402547 (originally filed against debian-installer) for previous discussion. The problem does seem to be that NetworkManager doesn't know what to do with the bmac interface, because it doesn't have carrier detect, so NetworkManager can't tell when it's up or down. One workaround (I've tried this and it works) is to declare the interface to be static and assign it a permanent IP address, netmask, etc... You can do this at install time (hit the cancel button when the installer is trying to get its address from the LAN DHCP server, then enter the static parameters.) Or you can do it after install by adding the appropriate stanza to the /etc/network/ interfaces file. There are probably more sophisticated things you can do that will allow you to keep using dhcp without involving (and confusing) networkmanager, but I haven't tried them. This will prevent NetworkManager from messing with the interface. See man 5 interfaces and /usr/share/doc/network-manager for details. In an ideal world, the NetworkManager would recognize the bmac as being hardwired and not disable it, but that may be more difficult than it sounds. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402547: Further details at Bug#403112
Further details at Bug#403112 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402547: Processed: Re: Bug#403112: NetworkManager: Workaround for OldWorld beige G3 Macintosh bmac network interface disabled on reboot
On Dec 14, 2006, at 5:05 PM, Michael Biebl wrote: Debian Bug Tracking System wrote: Processing commands for [EMAIL PROTECTED]: reassign 403112 network-manager Bug#403112: NetworkManager: Workaround for OldWorld beige G3 Macintosh bmac network interface disabled on reboot Warning: Unknown package 'networkmanager' Bug reassigned from package `networkmanager' to `network-manager'. So what exactly is the problem now, regarding network-manager? If your driver is broken, the driver should be fixed. If you setup a static configuration in /etc/network/interfaces, network-manager will not touch your network settings (as it can't deal with static configurations yet. NM 0.7.x is supposed to bring support for that). Could you elaborate a bit more? I don't think it's the driver that's broken. I believe the chip is incapable of a feature that NetworkManager wants. The OldWorld PowerMac (a Beige G3) machine (that I use for test installing Debian Etch) has a bmac 10-baseT ethernet controller on the motherboard, of a type that is apparently fairly common on OldWorld PowerMac machines, of which Apple made many varieties over the years. Apparently, the bmac is not able to do some of the fancy tricks that more modern network interface chips are capable of, such as telling the software whether it is seeing a carrier or not. This leads the NetworkManager to declare: Dec 11 02:34:47 debian NetworkManager: information^Ieth1: Driver 'bmac' does not support carrier detection. ^IYou must switch to it manually. Dec 11 02:34:47 debian NetworkManager: information^Inm_device_init (): waiting for device's worker thread to start Dec 11 02:34:47 debian NetworkManager: information^Inm_device_init (): device's worker thread started, continuing. Dec 11 02:34:47 debian NetworkManager: information^INow managing wired Ethernet (802.3) device 'eth1'. Dec 11 02:34:47 debian NetworkManager: information^IDeactivating device eth1. Ooops! This leaves the machine with no way to talk to the network even though I used that very same interface extensively and successfully when I installed the OS just a few minutes before. A work-around is to declare the bmac interface to be active and static, which makes NetworkManager leave it alone. However, if I read your comments correctly, as of NM 0.7.x, even that may not be enough. There are lots more details (many of them probably irrelevant) in the referenced bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi? bug=402547 which I submitted against the debian-installer before I realized where the real problem lies. Does this help? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
