Bug#611951: Default GNOME desktop installation has both xsane *and* simple-scan
Christian PERRIER bubu...@debian.org wrote: Hi, According to Joss, meta-gnome2 is correct in this case and only simple-scan should be installed. I would like to have xsane's maintainer advice on this issue. Should we remove xsane from gnome-desktop? I concur with Joss; the default desktop installation should not include XSane. XSane is complex to use and simple-scan will do for the vast majority of desktop users. Thanks, JB. -- Julien BLACHE jbla...@debian.org | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762t0jb1s@sonic.technologeek.org
Re: Uploading GNOME 2.24 to sid
Bastian Blank wa...@debian.org wrote: Hi, Can you do a size estimate for this? It would need in addition - the X server, - evdev input module and - a framebuffer video module. Anything else? HAL and DBus to go with input-evdev, I guess? JB. -- Julien BLACHE - Debian GNU/Linux Developer - jbla...@debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501290: Installation report: MacBook4,1 on Oct 2nd
[EMAIL PROTECTED] wrote: Hi, During partition hard drives I just have labeled the linux partition correctly. Right after debootstrap (IIRC) I created a swap file (more than four partitions are not recommended for GPT/MBR mix). Not an issue as long as the bootloader and kernel are available in one of the first four partitions (excluding the EFI partition). JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Missing MANIFEST entries for ia64 stuff?
Hi, While looking at the d-i files on a mirror (sid, current on ftp.de.d.o), I found this in the ia64 MANIFEST file: less MANIFEST cdrom/boot.img -- CDROM image for Itanium systems cdrom/initrd.gz -- ./tmp/cdrom/udeb.list cdrom/vmlinuz-- [...] ia64/cdrom.cfg only has a MANIFEST-BOOT entry, looks like it needs MANIFEST-INITRD and MANIFEST-KERNEL entries also. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i status wrt i386 amd64 EFI machines
Frans Pop [EMAIL PROTECTED] wrote: Hi, There is no provision to say partition the drive, but leave the first one alone. Especially for the first partition (if it is #1 and at the beginning of the disk) that should be possible to implement though by coding what I described in [1] (the recipe used should then of course not include an EFI partition). I kind of expected something like that, to be honest :) It sure gets complicated when the partition to keep is in the middle of the disk, but fortunately that case shouldn't happen. Also being able to automatically protect a partition could be also be useful on mips for SGI machines where a volume header must exist on the disk. Though I don't remember how this is handled by d-i, it's been like forever since I last ran d-i on an SGI. Anyway, one thing at a time; there are several levels of support we can provide, let's get something basic working first and build from there. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i status wrt i386 amd64 EFI machines
Frans Pop [EMAIL PROTECTED] wrote: Hi, Note that we also have a combined i386/amd64/powerpc CD. We'd need to check that EFI support can coexist with that, or else somehow exclude it from that image. Shouldn't be a problem at first glance; maybe the EFI boot image will need to be the first one on the disk. Anyway, I have all those CD images on the radar. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i status wrt i386 amd64 EFI machines
Frans Pop [EMAIL PROTECTED] wrote: Hi, Which brings us to the core of the issue. Installing rEFIt means: - copying rEFIt to the EFI system partition (first partition on the disk, FAT32, ca. 200 MB on Apple machines) This may also require changes in partman, especially in guided partitioning if it should be possible to reuse a pre-existing EFI system partition. Yes, that's part of the plan. There already is code to recognize Intel Macs as a separate subarch which allows to use separate partitioning recipes that could include a EFI system partition, but currently that means the existing one would probably be lost. Which is not a good idea :) So if Mac 1st partition is FAT32 - mark the partition as being the EFI partition (can be generalized to all the EFI machines I think). Not sure how EFI based servers (when booted as pure EFI) should be recognized. Also as a separate subarch? By special casing them? (i386 || amd64) !Mac efivars loaded - EFI machine OTOH, I would expect most sysadmins of servers to do manual partitioning anyway. So do I. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483182: [PATCH] libdebian-installer: add new vendor string for Apple
Package: libdebian-installer4
Version: 0.58
Tags: patch
Hi,
Apple changed its company name in Q1 2007 (from Apple Computer, Inc.
to Apple Inc.), and the vendor string embedded on the machines
changed as a consequence on machines produced after this date.
The attached patch adds the new vendor string to the x86 subarch
detection code.
Please apply,
JB.
--
Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more
Debian GNU/Linux Developer| http://www.debian.org
Public key available on http://www.jblache.org - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
diff -ru orig/libdebian-installer-0.58/src/system/subarch-x86-linux.c libdebian-installer-0.58/src/system/subarch-x86-linux.c
--- orig/libdebian-installer-0.58/src/system/subarch-x86-linux.c 2007-12-31 23:34:31.0 +0100
+++ libdebian-installer-0.58/src/system/subarch-x86-linux.c 2008-05-27 13:55:06.855293130 +0200
@@ -215,6 +215,7 @@
static struct map map_manufacturer[] = {
{ Apple Computer, Inc., mac },
+ { Apple Inc., mac },
{ NULL, NULL }
};
d-i status wrt i386 amd64 EFI machines
[Please Cc me on replies, I'm not subscribed to debian-boot] Hi, I've taken over the maintenance of rEFIt last week and I've been working on updating rEFIt in Debian since then (I've been working on the rEFIt issue on and off for more than a year). This is now a done deal, only waiting for a gnu-efi upload. Now that we have a working rEFIt, I'd like to have some support for that in d-i. Looking into this issue, I came to the conclusion that what is really needed is a d-i install medium for i386 amd64 machines. What is the status on that? Are there any plans or any work in progress towards providing an EFI bootable medium, similar to the ia64 install medium? (you can skip the remainder of this mail if you're not interested in the gory details) Rationale for that: - i386/amd64 EFI machines are becoming more and more common among high-end servers - Intel Macs are also becoming more and more common, the market share for Apple machines in the high end market is booming (especially for laptops) - as the pommed author, I'm getting more and more mails from *new* users; that shows that Linux is progressing on those machines too - current d-i support for Intel Macs is suboptimal at best, installing an i386 system is mostly OK, installing and amd64 system is hardly possible TTBOMK I'll go into the details pertaining to Intel Macs now and why an EFI boot medium is needed. When reading what follows, keep in mind that Intel Macs are a special case among i386/amd64 EFI machines. That means most of the workload is directed at the generic case and the support for Intel Macs is really icing on the cake. The EFI system on Apple machines can boot an OS either via an EFI bootloader or through a legacy bootloader by loading a legacy BIOS emulation layer before executing the legacy bootloader. The Linux kernel has support for EFI on both i386 and amd64 (starting with 2.6.25 for amd64); this means the kernel can be booted via an EFI bootloader such as elilo and interact with the EFI system. Notably, this means the kernel can manipulate EFI variables (via the efivars module), which is required to set the boot order. That last feature can only be used when the kernel has been booted via EFI, it's not available when the kernel is booted through legacy mode. Also, for everyday use, Intel Macs are best booted through legacy mode. Why? Because otherwise, there is no video BIOS loaded, which means: no accelerated 2D or 3D video. Which brings us to the core of the issue. Installing rEFIt means: - copying rEFIt to the EFI system partition (first partition on the disk, FAT32, ca. 200 MB on Apple machines) - setting the EFI variables so that the EFI system will load rEFIt as the primary bootloader (for other EFI machines, replace rEFIt with elilo and the above still holds) This last step can be accomplished on Linux with efibootmgr and the efivars kernel module. Without this last step, the machine will continue booting into OS X and the user will have to use the bless utility under OS X to set the EFI variables. As I wrote above, the efivars module only works when the kernel has been booted through EFI. Which means that we need to boot d-i from EFI and not through legacy mode in order to support a painless installation on these machines. Note that I expect most of the ia64 stuff can be reused mostly unchanged to produce those images. Providing a refit-installer similar to elilo-installer looks like a no-brainer, overall most of the work seems to be in building new images and testing them. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i status wrt i386 amd64 EFI machines
Julien BLACHE [EMAIL PROTECTED] wrote: For the sake of completeness, as I was concentrating on EFI stuff while writing this mail: Which brings us to the core of the issue. Installing rEFIt means: - installing grub/lilo on the *partition* (not MBR) - running gptsync - copying rEFIt to the EFI system partition (first partition on the disk, FAT32, ca. 200 MB on Apple machines) - setting the EFI variables so that the EFI system will load rEFIt as the primary bootloader JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i status wrt i386 amd64 EFI machines
Frans Pop [EMAIL PROTECTED] wrote: Hi, There is an open BR against debian-cd to support EFI for i386/amd64 CD images (#455914). Help to implement that is very much needed. There's some work to be done on d-i beforehand ;) What other types of images are you thinking of? Could EFI support be added to existing images or do we really need additional images? I think we need dedicated images, as far as the CD/DVDs go. I don't think we can share a CD, though I have to check how multiboot CDs work and how EFI behaves on Macs. To be honest, at this stage, it's still a detail :) For PXE booting, a dedicated image will be required, though it's no problem compared to a dedicated CD image. The good news is, in all cases, the code from ia64.cfg can probably be shared among all three architectures. If I'm not mistaken, there's no g-i on ia64, so I'll just have to add it for i386 and amd64 as g-i should work fine via EFI too. I don't see any objection to providing images that support EFI, but I doubt anyone on the D-I team will do the actual implementation. As always: patches are welcome and we can offer help with finding the right places to make needed changes. I'm ready to make whatever changes are required, as long as I can get some assistance on some very specific points. I've started identifying the precise changes to be done. I may need a little bit of help with the build system to build the images, otherwise, with the exception of grub-installer and lilo-installer, I think I can handle it. I'd like to have grub-installer and lilo-installer default to installing the bootloader on the debian partition on Macs, and that requires some changes in the logic and templates. I'll try to figure it out, but hairy debconf stuff scares the hell out of me :) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i status wrt i386 amd64 EFI machines
Frans Pop [EMAIL PROTECTED] wrote: Hi, What other types of images are you thinking of? Could EFI support be added to existing images or do we really need additional images? Looks like I can answer your question after a few tests and some googling on the spec. Yes, it seems we can add EFI support to the current CD images and don't need additional CD images. Adding an alternative El Torito boot image is enough. The firmware is required by the spec to ignore legacy boot entries. The Apple firmware presents the legacy entries and the EFI entries, labelled as such. That, of course, simplifies things quite a bit :) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421338: macbook pro installation issue
\Félix Guerrero [EMAIL PROTECTED] wrote: Hi, Image version: debian 4.0 r0 ia64 Apple machines aren't ia64, they're i386/amd64 machines. So, you used the wrong architecture, grab an i386 or amd64 installation media instead. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Martin Michlmayr [EMAIL PROTECTED] wrote: Hi tbm, The kernel on the beta3 CD seems to lack keyboard support, so installing using the console is rather hard :) This should be fixed in rc1. Can you please try? I won't have physical access to the machine until the end of december, sorry. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383796: d-i: too much error screens
Package: installation-reports Boot method: CD Image version: beta 3 Date: 20060819 Machine: SGI Indigo2 Processor: R4400SC 200 MHz Memory: 256 MB Partitions: Output of lspci and lspci -n: No PCI bus. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[E] Install boot loader:[ ] Reboot: [ ] Comments/Problems: Note: the initial boot from the CD isn't automatic as noted previously. Note2: tbm asked me to do a test install to check that partitioning/detecting/formatting/mounting partitions was OK on these machines -- it is indeed working fine. The list of partitions includes the volhdr and 2 small 16 kB partitions (can't remember what they are, might be holes in the partitioning) which is misleading and error prone; the suggestion would be to hide the volhdr. Base system installation failed, due to a broken CD-ROM drive, so that's not a d-i issue, and not the point of this installation report. While retrieving packages from the CD, d-i displays 2 consecutive error screens per failed file, which is really painful on a 9600 bauds serial console. The first error is displayed when retrieving the file, and the second when validating it. This last step should be skipped when the file could not be retrieved. Hitting the Go Back button on these error screens is useless, as d-i will just continue to retrieve the base system's files; please make this button go back to the main d-i menu or just remove it. After that, debootstrap will fail, which leads to *3* error screens (trying to break a record or something ? ;) : - deboostrap failed with error code ... blahblahblah check virtual console 4 for details (hmm ... no virtual consoles while installing using a serial console - misleading error message, but that's a detail) - failed to install the base system (just in case I didn't get it the first time) - an installation step failed (really ?) Other than that, it just works, congrats to the d-i people ! JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Package: installation-reports Boot method: CD Image version: beta3 netinst Date: 20060814 Machine: SGI IP22 (Indigo2) Processor: R4400SC 200 MHz Memory: 256 MB Partitions: No partitioning done. Output of lspci and lspci -n: No PCI onboard. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E] Configure network HW: [ ] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: The kernel on the beta3 CD seems to lack keyboard support, so installing using the console is rather hard :) Some strings in the list of languages aren't displayed properly, which means the installation probably can't be done using the affected languages. Note: the installation manual lacks the instructions needed to boot from the CD (boot -f scsi(X)cdrom(Y)partition(8)/r4k-ip22 in the PROM) I'll attempt a serial console install and will submit another report once I'll be done. Thanks, JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Christian Perrier [EMAIL PROTECTED] wrote: Indeed, the code in localechooser that decides to display one or another set of languages is pretty incomplete. It decides this based on assumptions about the display but these are probably incomplete: The console in this case should be a standard Linux console on framebuffer, but I guess that it's not /that/ standard after all. Maybe Thiemo can tell us more about that ? The console groks at least latin1, btw. Could it be that the console lacks UTF8 support ? JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Thiemo Seufer [EMAIL PROTECTED] wrote: Hi, Note: the installation manual lacks the instructions needed to boot from the CD (boot -f scsi(X)cdrom(Y)partition(8)/r4k-ip22 in the PROM) This should work semi-automatically via the install system entry in the firmware menu. That's what I thought when I first tried it ... it failed to boot :) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Thiemo Seufer [EMAIL PROTECTED] wrote: Hi, Well, it _should_ try to boot from scsi(X)cdrom(Y)partition(8)/sashARCS, which _should_ be provided in the CD's volume header as an alias to r4k-ip22. From the PROM: ls scsi(0)cdrom(3)partition(8) scsi(0)cdrom(3)partition(8): r4k-ip22 From a running system: % sudo dvhtool -d /dev/sr0 --print-volume-directory - directory entries - Entry #0, name r4k-ip22, start 7480, bytes 9414656 % Which would indicate a problem with the CD build script, I guess ? Thanks, JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Thiemo Seufer [EMAIL PROTECTED] wrote: The console in this case should be a standard Linux console on framebuffer, but I guess that it's not /that/ standard after all. Maybe Thiemo can tell us more about that ? It is not at all a standard framebuffer. The hardware allows no direct memory access but provides userspace-driven DMA capability instead. The X server uses the userland DMA for a while now, but the kernel uses a special newport console which is rather inefficient. It's the console which I qualified of standard, in this case, as the framebuffer is indeed pretty exotic. The console groks at least latin1, btw. Could it be that the console lacks UTF8 support ? That's possible, I don't know the newport code by heart. Christian, can you confirm that the installer uses a UTF-8 console ? If yes, I should be able to reproduce the problem on a running system by calling unicode_start and echoing some UTF-8 text, I guess. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382983: d-i beta3 on SGI Indigo2 (IP22)
Thiemo Seufer [EMAIL PROTECTED] wrote: Which would indicate a problem with the CD build script, I guess ? Yes. IIRC it worked correctly for sarge. Looking at the debian-cd SVN, the scripts for sarge and etch are mostly identical. So that would be an issue with mkisofs. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#266601: installation report: d-i RC1 on HP Pavillion ze4200
Package: installation-reports Debian-installer-version: RC1 business card uname -a: 2.6.7-1-686 Date: 20040817 Method: Boot on the business card CD, install using a local mirror. Machine: HP Pavillion ze4200 Processor: Intel Celeron Memory: 256 MB (- 64 MB VRAM) Root Device: IDE Root Size/partition table: hda1 9.2 GB Windows XP hda5 500 MB Swap hda6 10 GB / Output of lspci: :00:00.0 Host bridge: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] (rev 02) :00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M] :00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) :00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 02) :00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV] :00:08.0 Modem: ALi Corporation M5457 AC'97 Modem Controller :00:0a.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller :00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) :00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4) :00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU] :00:12.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller :01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 340M Base System Installation Checklist: Initial boot worked:[E/O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E/O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Booting on the default 2.4 kernel led to a non-working keyboard; this also happened with RedHat and other installers about a year ago. Booting with the linux26 kernel worked like a charm. Partitionning went a bit funny. The disk layout was : hda1 9.2 GB Windows XP FREE SPACE 0.04 MB hda2 10 GB / [that thing was generated by a previous Mandrake installation] It seems this layout managed to confuse partman; it wouldn't list the existing partitions (only the entire disk was available in the menu). After deleting hda2 using cfdisk on another terminal, everything worked fine. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#266601: installation report: d-i RC1 on HP Pavillion ze4200
Joey Hess [EMAIL PROTECTED] wrote: It would be best if you could send us an exact dump of your old partition table, but at least a copy of That's not possible anymore, unfortunately. I think it's the layout with a very small free space between two partitions that triggered the bug, but time will tell. /var/log/debian-installer/partman might be helpful in doing something about this. I sent it a couple of minutes ago :) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255169: installation report: SGI Indigo2 (r4k IP22)
Package: installation-reports Debian-installer-version: 20040618, debian/dists/unstable/main/installer-mips/current/images/r4k-ip22/netboot-boot.img uname -a: Linux indigo 2.4.25-r4k-ip22 #1 Thu Apr 15 20:46:28 BST 2004 mips GNU/Linux Date: 20040619 Method: TFTP boot on the LAN, network install (testing) from my local mirror. Machine: SGI Indigo2, r4k IP22 Processor: R4400SC V6.0 FPU V0.0 Memory: 384 MB, only 256 usable without CONFIG_HIGHMEM (which doesn't work anyway) Root Device: SCSI, /dev/sda Root Size/partition table: Disk /dev/sda (SGI disk label): 64 heads, 32 sectors, 8748 cylinders Units = cylinders of 2048 * 512 bytes - partitions - Pt# Device Info Start End Sectors Id System 1: /dev/sda1 boot1190163840 83 Linux native 2: /dev/sda2 swap91 600 1044480 82 Linux swap 3: /dev/sda3 601 4650 8294400 83 Linux native 4: /dev/sda44651 8747 8390656 83 Linux native 9: /dev/sda5 010 22528 0 SGI volhdr 11: /dev/sda6 0 8747 17915904 6 SGI volume - Bootinfo - Bootfile: /unix - Directory Entries - 0: arcbootsector4 size 67392 /dev/sda1 on /boot type ext3 (rw) /dev/sda3 on / type ext3 (rw,errors=remount-ro) /dev/sda4 on /home type ext3 (rw) Output of lspci: No PCI bus. Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E/O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: I didn't remember that I had to create the partitions from last to first, I'm pretty sure I didn't do that when I installed woody on the machine a year ago. Anyway, I eventually figured out and partitioned the disk. Had to create an SGI disklabel on it, as it comes from a PC. Disappointment : no XFS support :( The bootloader installation went fine, but, unfortunately, it doesn't handle a separate /boot partition, so the machine couldn't reboot. I had to boot into the installer, and copy /etc/arcboot.conf to /boot/etc/arcboot.conf, then set OSLoadPartition to the correct value for /boot. Everything else went fine. Now this machine will be really useful, with a little bit more disk space (and less noise) :-) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255169: installation report: SGI Indigo2 (r4k IP22)
Thiemo Seufer [EMAIL PROTECTED] wrote: I didn't remember that I had to create the partitions from last to first, I'm pretty sure I didn't do that when I installed woody on the machine a year ago. Anyway, I eventually figured out and partitioned the disk. Had to create an SGI disklabel on it, as it comes from a PC. What do you mean with last to first? I had to create sda4 first, then sda3, etc. I started by creating sda1, starting at cylinder 11 and up to cylinder 90, but afterwards fdisk insisted on sda2 being created in the range 0-10 (ie before sda1). But it's been over a year since I last used fdisk on this machine, so maybe it isn't something new and I just don't remember. Anyway, it seems weird. Disappointment : no XFS support :( The bootloader installation went fine, but, unfortunately, it doesn't handle a separate /boot partition, so the machine couldn't reboot. Well, the firmware has no problem with booting from arbitrary partitions, so a separate /boot makes little sense, and arcboot doesn't support it. This should be documented better. d-i should either workaround the problem (as I did), or it shouldn't offer to create a /boot partition that will lead to a non-booting machine :) /boot makes sense in my case, because I intend to use XFS on this machine, and I think arcboot doesn't handle XFS. Moreover I plan to do some tests on the machine, and should it crash, I'd like to keep /boot safe, so it can still boot and recover. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255169: installation report: SGI Indigo2 (r4k IP22)
Thiemo Seufer [EMAIL PROTECTED] wrote: d-i should either workaround the problem (as I did), or it shouldn't offer to create a /boot partition that will lead to a non-booting machine :) Rather the latter, I think. Yes, for a quick fix, as it shouldn't be /that/ hard to figure out if /boot is on the same partition as / or not. /boot makes sense in my case, because I intend to use XFS on this machine, and I think arcboot doesn't handle XFS. If XFS is in a module, you still need a non-XFS /. I build only non-modular kernels :) initrd is really no fun. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255169: installation report: SGI Indigo2 (r4k IP22)
Martin Michlmayr [EMAIL PROTECTED] wrote: Well, the firmware has no problem with booting from arbitrary partitions, so a separate /boot makes little sense, and arcboot doesn't support it. This should be documented better. Does arcboot not support it, or arcboot-installer? arcboot needs to find both the kernel to boot and an /etc/arcboot.conf file on the same partition. So I'd say that arcboot basically supports booting from a separate /boot partition, as long as you provide mountpoint/etc/arcboot.conf. Maybe the solution would be to copy the arcboot.conf into the volhdr, along with arcboot itself, although I don't how complex it would be to implement. (sure, you'll have to copy it over when you modify it...) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Martin Michlmayr [EMAIL PROTECTED] wrote: Hi tbm, Can you please test a daily image from http://gluck.debian.org/cdimage/testing/sarge_d-i/ to make sure there are no regressions. This would be helpful since we're preparing for rc1. If all of the issues you reported originally have been dealt with, can you close this bug. As I said, this machine is now in production. However, I'll have an identical machine at hand at some point in the near future (probably in the upcoming month). I'll test and report if it's still considered useful at that point in time. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Martin Michlmayr [EMAIL PROTECTED] wrote: Can you please test a daily image from http://gluck.debian.org/cdimage/testing/sarge_d-i/ to make sure there are no regressions. This would be helpful since we're preparing for rc1. If all of the issues you reported originally have been dealt with, can you close this bug. The machine is in production now, so for now I cannot test that, sorry. Maybe I'll have to install a couple of servers with the same configuration, but that won't happen before several weeks. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Package: installation-reports
Debian-installer-version: Beta3 netinst (20040405)
uname -a: installer kernel 2.4.25, installed 2.4.25-686
Date: 20040423
Method:
Boot off of the netinst CD, using a local FTP mirror.
Machine: Dell Poweredge 750 rackmount 1U, with Adaptec AACRAID (Dell
CERC)
Processor: Pentium IV 2.8 GHz
Memory: 512 MB
Root Device: SCSI, /dev/sda (Adaptec AACRAID)
Root Size/partition table:
Not relevant. 120 GB on hardware RAID1.
Output of lspci:
Relevant elements :
Adaptec AACRAID PCI ID : 0285
Intel E1000 dual port PCI ID : 1075
Base System Installation Checklist:
Initial boot worked:[O]
Configure network HW: [E]
Config network: [E,O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [E,O]
Partition hard drives: [O]
Create file systems:[O]
Mount partitions: [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
The installer booted flawlessly, but couldn't detect the ethernet
card. It is a dual Intel E1000 card, supported by the stock e1000
driver. Loading the driver by hand leads to a working network setup,
the installer then detects the ethernet interfaces without any
problem.
The network configuration is a real pain. We have a DHCP server on the
network used to netboot thin clients and initiate network
backups/restore, which can't be used for anything else.
As the installer automatically issues DHCP requests without asking if
it should do so, we had to pull the plug, then redo the network
configuration. Wasted time.
The installer couldn't detect the Adaptec AACRAID card (RAID card with
6 SATA ports). Loading the driver by hand, together with sd_mod, leads
to a working setup, the installer then finds the RAID array as
/dev/sda, which is just fine.
The regular PATA controller was detected just fine, although the 2
onboard (non-RAID) SATA ports weren't detected. I've no details on the
SATA controller, I'll get back to you with those details when I'll
have access to the machine again.
Partitioning with partman is a *PAIN*. This thing is horrible. It is
counter-productive and, at best, counter-intuitive. I thought the
installer would ask me to create a swap partition, but I found out
that I was left alone to create it with partman, and the whole thing
is non-obvious. Please, give me back my beloved cfdisk !
Then it complained because I wanted my /boot partition to be an XFS
partition, and that wouldn't work with grub. There's a patch for grub
on the linux-xfs mailing list, please get it applied to our grub
package and remove that warning. I want to get rid of ext{2,3} :P
choose-mirror is buggy. When going back, it will eventually present a
list of mirrors for the country you are supposed to be in, and the
enter information manually item isn't there. Annoying.
Also, it can't tell whether the mirror is unavailable due to network
problems or whether it's not usable for another reason. It'd be useful
to make the distinction between these 2 cases.
Although the installer didn't detect the AACRAID card, the reboot went
just fine. The network driver wasn't loaded, but that was no surprise.
Base-config presented its main menu, and didn't guide me through the
steps automatically. I don't know if it's intended, but I find it
disturbing.
We installed this machine in just 20 minutes. That was my fastest
Debian installation ever. Thanks guys, you're doing a really good job.
If you need more details on the machine, just ask, and I'll provide
them as soon as I'll have the hardware handy.
JB.
--
Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more
Debian GNU/Linux Developer| http://www.debian.org
Public key available on http://www.jblache.org - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Michael Banck [EMAIL PROTECTED] wrote: Well, I guess your situation is not really the general setup, so making it easier for you would mean making it harder for almost everybody else. There *are* easy work-arounds available - either do expert mode setup which prompts you for this or I think there is a way to disable DCHP via a boot option, you might want to check on those. Because there is a DHCP server responding on the network doesn't mean the user wants to use it, even when the user is almost everybody else. That was the point. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Michael Banck [EMAIL PROTECTED] wrote: Because there is a DHCP server responding on the network doesn't mean the user wants to use it, even when the user is almost everybody else. That was the point. So are you argueing that there should be an additional dialog box saying 'I've detected an DHCP server on your network. Do you want to use it [Y/n]?' If not, then don't seem to understand your problem. Yes, something along this way would be a good idea. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Joey Hess [EMAIL PROTECTED] wrote: [wrt grub and XFS] https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=99284action=view That's the one I had in mind, it's actually something that should be done in the bootloader installer, or in grub-install. Anyway, it's the way to go, and approved by the XFS gurus. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Joey Hess [EMAIL PROTECTED] wrote: Hi, Adaptec AACRAID PCI ID : 0285 Intel E1000 dual port PCI ID : 1075 That is not enough information to fix discover to detect the hardware it missed. Please read discover(1) and send in sufficient information. I'll do that as soon as I'll have the machine at hand, thanks. If you know where the patch is, send the information to bug #243835. I found some interesting urls: http://marc.theaimsgroup.com/?l=linux-xfsm=107704299608539w=2 https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=99284action=view https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=117968 But no grub patch. I'll dig it up. Base-config presented its main menu, and didn't guide me through the steps automatically. I don't know if it's intended, but I find it disturbing. This is because something you did earlier dropped the installer to a lower debconf priority. Ah. I can't see what I could have done that would have resulted in that, but OK :) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245632: Installation report, Poweredge 750 with Adaptec AACRAID
Joey Hess [EMAIL PROTECTED] wrote: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=99284action=view That's the one I had in mind, it's actually something that should be done in the bootloader installer, or in grub-install. It seems to me that this would need to be done in grub-install, presumably the idea is to freeze the XFS filesystem after the grub files are copied to it, and before grub is run, and both steps happen in grub-install You got the idea :) JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#231239: Report : beta2 on HP d330uT w/ 17in TFT monitors
Package: installation-reports We installed 3 d330uT based machines at Solutions Linux 2004 ; of the 3 machines, 2 had a dualhead Quadro 4 graphic card. Debian-installer-version: Beta2 uname -a: handbuilt 2.6.2-rc1 kernel Date: 2003-02-02 Method: netinst Machine: HP d330uT unit with 17in TFT monitor Processor: Pentium4 2.6 GHz Memory: 500 MB Root Device: IDE, single disk on primary master Root Size/partition table: 1 GB swap on hda1, rest of the disk (~35 GB) on hda2 Output of lspci: -- For the basic d330uT : 00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02) 00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02) 00:1f.2 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02) 05:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5782 Gigabit Ethernet (rev 03) -- For the d330uT + Quadro 4 graphic card 00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller (rev 02) 00:01.0 PCI bridge: Intel Corp. 82865G/PE/P Processor to AGP Controller (rev 02) 00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02) 00:1f.2 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV17GL [Quadro4 200/400 NVS] (rev a3) 05:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5782 Gigabit Ethernet (rev 03) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E/O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: The machines come with an integreated Broadcom chipset which is supported by the tg3 driver in the 2.6 kernel. We had to borrow a 3c509 card to install the base system before building a 2.6 kernel. The mirror configuration entered a loop, we eventually got out of it at some point. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
