Re: USB keyboard not working on a cinema display/cube
On Sat, Jan 08, 2005 at 06:59:38PM +0100, Nicolas Jungers wrote: Le 31 déc. 04, à 00:24, Sven Luther a écrit : On Mon, Dec 27, 2004 at 07:11:34PM +0100, Nicolas Jungers wrote: hi, the sarge-powerpc-netinst.iso fail to activate my keyboard when connected to the display. It's true of the RC2 version and of the daily/powerpc/20041226/ version. Can you look in /proc/bus/usb/devices if it shows up or something, and post us a lsmod output. May be tricky without keyboard though :) Maybe using the network-console and some presseding may help here ? I dunno how to do that on a Mac. What I did was plugin two keyboards, Yeah, that was the other solution. one on the cube, the other on the cinema display, and both didn't respond. but if you plug only one into the cube, it is ok ? Can you try pluging the keyboard in the cube, go upto partman, and then add the display keyboard and look at /proc/bus/usb/devices (or lsusb or whatever output ?) Now, I tryed the installer because my system wasn't comming up after a kernel upgrade. Going from 2.6.7 to 2.6.8 makes the hotplug stall. I bet you are not using the debian kernel though, right ? If you send me instructions I can try to dig further. Well, let's hope the above works. If not we can try a preseeding+network-console trick, but it is more involved. Friendly, Sven Luther
Re: Desktop task broken on !(i386/powerpc)
On Fri, Jan 07, 2005 at 10:48:53AM +0100, Petter Reinholdtsen wrote: [Sven Luther] Do you really think that anyone installing debian will be baffled when asked to choose between the gnome or KDE desktop ? Do you seriously believe that ? Yes, I seriously believe that. I'm involved in the debian-edu subproject, and we try to make Debian available for all pupils and students during education. Several of the teachers responsible for setting up the computer network at their local school will be seriously baffled when asked to choose between gnome and kde. It is strange though, that you that are in the educational world believe in dumbing down the install for everyone instead of educating the few who have problems. I bet some words of explanation of the kind : there are two possible desktop styles/skin/whatever, please choose one, if unsure, choose insert prefered one And how do these people react to choosing KDE over gnome in gdm ? Or do they simply use the default desktop there ? If so, what would be the lose in chosing such a default desktop in tasksel, and having some choice like : Gnome Desktop (default) KDE Desktop (alternate desktop) Simple Desktop (alternate desktop) - this one is just X with twm or whatever Would have had the same effect on usability, not ? I bet those people will probably be more confused by the various server tasks. Absolutely. Which is why I try to encurrage redusing the amount of questions during first time install, and hide the complexity and flexibility from common users view, to reduce the cognitive strain on the first time debian users. Us experts will find the options anyway. So drop the question down to a lesser priority, default to the desktop task in normal priority, and let's flesh out the tasks to something reasonable. And you think it is easier for them to discover the KDE desktop once they have GDM running ? What do you imagine our current disk requirements are ? I do not believe these users _care_ if they get the KDE or gnome Well, so we chose one, make it the default, and propose the other as an alternative. everyone is happy and we can have meaningfull tasks. desktop. I have no idea what you mean by our current disk requirements. The minimal disk size needed to install. This used to be 800 Mo for a desktop system in woody, if i remember well. Friendly, Sven Luther
Re: Moving discover1, discover1-data repositories to Subversion
On Sat, Jan 08, 2005 at 06:48:54PM -0800, Joshua Kwan wrote: Joshua Kwan wrote: The structure would probably be svn+ssh://svn.debian.org/svn/pkg-discover/discover1/trunk svn+ssh://svn.debian.org/svn/pkg-discover/discover1-data/trunk etc. If there are no objections I will do it in a day or so. Thanks! Actually, time's up. I got impatient and went and did it. I followed my proposed structure, all the tags have been imported, etc. I've made a tarball of the CVS repository available at http://people.debian.org/~joshk/pkg-discover.tar.gz and I have (re)moved the one on haydn. Just for info, i stronglt recomend keeping the trunk stuff at the base of the hierarchy, and the tags dir as well, or peopel will have a hell of a trouble when there are loads of tags to checkout only the trunk. Friendly, Sven Luther
Listar: Post sent to moderator.
Post to list linuxecoles Subject: Post submitted to moderator for reason: Non-member submission to closed-post list. --- Gestionnaire de liste Listar/0.42 - fin de traitement/job execution complete.
Bug#260763: [powerpc] Problems with logical volume setup during installation
Parted converts flags to funky partition type names, i think. Not idea, but it works, like said, i think parted is inherently broken on this, but there is not much we can do at this time. They might have done this following a comment of mine (my memory id fuzzy on this, not sure they ever asked). Using the partition type (which is just a string) is indeed broken IMO. Why ? take for example the bootstrap partition, which is Apple_bootstrap on mac, and 0x41 on chrp/prep MBRs ? The same goes for LVM or RAID partitions. Why? Because we don't know how MockOS will react to a partition _type_ set to anything but Apple_Bootstrap, Apple_HFS, Apple_UNIX_SVR2 or Apple_Free. If you're sure (or just reasonably confident) Linux_LVM will be ignored by Apple boot and disk mount code, go ahead. I can only test this for a fairly narrow range of OS X versions, and maybe a resurrected 8.6. Since there's always the partition name (for Apple_UNIX_SVR2 partitions which MacOS ignores since prehistoric times), I didn't really want to bother testing this. Furthermore, i believe that the partition type is the right place to store this info, confirmed by the fact that on MBR a type is used for both RAID and LVM. After all, the fact that a partition does RAID or LVM cannot be compatible by it being a linux swap partition for example, in the way the bootable flag is set for example. I would suggest we use 'Linux_RAID' and 'Linux_LVM' for those two. And libfdisk (for example) used to look at the partition _name_ field in Mac partition tables for clues where to find swap. What's the problem with that? So we should press this point a bit more forcefully :-) Like said, i will gladly write the (trivial) code, if some consensus is reached. We seem to have trouble reaching a consensus even here :-) Seriously though, let's just try with 'Linux_RAID' and 'Linux_LVM' partition _type_ fields in Mac partition tables, maybe add Linux_Swap later and keep plain data partitons as before. That should keep the comaptibility code to a minimum (look for 'swap' in type and name fields) and get the scheme some limited testing. If parted currently encodes the LVM flag in the partition type we can still put it into the partition name on top of that, and get the Debian LVM maintainer to accept either flag? No, i would vote against this. After all, a parted user can change the name of a partition through the parted and d-i/partman interface. A mac-fdisk user can change either at will. Linux always reserves your right to shoot yourself into the foot. But for the sake of saving users from their own stupidity, go ahead with the scheme you suggested. Michael
Re: Bug#260763: [powerpc] Problems with logical volume setup during installation
On Mon, Jan 10, 2005 at 11:13:07AM +0100, Michael Schmitz wrote: Parted converts flags to funky partition type names, i think. Not idea, but it works, like said, i think parted is inherently broken on this, but there is not much we can do at this time. They might have done this following a comment of mine (my memory id fuzzy on this, not sure they ever asked). Using the partition type (which is just a string) is indeed broken IMO. Why ? take for example the bootstrap partition, which is Apple_bootstrap on mac, and 0x41 on chrp/prep MBRs ? The same goes for LVM or RAID partitions. Why? Because we don't know how MockOS will react to a partition _type_ set I don't know any MockOS, please provide real examples. to anything but Apple_Bootstrap, Apple_HFS, Apple_UNIX_SVR2 or Apple_Free. If you're sure (or just reasonably confident) Linux_LVM will be ignored by Just give it a try and enlighten us. Apple boot and disk mount code, go ahead. I can only test this for a fairly narrow range of OS X versions, and maybe a resurrected 8.6. Since there's always the partition name (for Apple_UNIX_SVR2 partitions which MacOS ignores since prehistoric times), I didn't really want to bother testing this. Yeah, but imagine that the user wants to use the partition name for something sensible, and all this goes down. Notice that i was approached about RAID on sparc, which is the exact same issue too. Furthermore, i believe that the partition type is the right place to store this info, confirmed by the fact that on MBR a type is used for both RAID and LVM. After all, the fact that a partition does RAID or LVM cannot be compatible by it being a linux swap partition for example, in the way the bootable flag is set for example. I would suggest we use 'Linux_RAID' and 'Linux_LVM' for those two. And libfdisk (for example) used to look at the partition _name_ field in Mac partition tables for clues where to find swap. What's the problem with that? well, suppose that a french user wants to name it echange instead of swap ? So we should press this point a bit more forcefully :-) Like said, i will gladly write the (trivial) code, if some consensus is reached. We seem to have trouble reaching a consensus even here :-) Seriously though, let's just try with 'Linux_RAID' and 'Linux_LVM' partition _type_ fields in Mac partition tables, maybe add Linux_Swap later and keep plain data partitons as before. That should keep the comaptibility code to a minimum (look for 'swap' in type and name fields) and get the scheme some limited testing. Ok, but as said, Colin Watson vetoed me on that, and as we already have a parted in experimental, ... If parted currently encodes the LVM flag in the partition type we can still put it into the partition name on top of that, and get the Debian LVM maintainer to accept either flag? No, i would vote against this. After all, a parted user can change the name of a partition through the parted and d-i/partman interface. A mac-fdisk user can change either at will. Linux always reserves your The future belongs to libparted frontends though. And this is not linux, but the new user-friendly debian-installer partman, so ... right to shoot yourself into the foot. But for the sake of saving users from their own stupidity, go ahead with the scheme you suggested. I would have for ages, but Colin Watson vetoed it without larger consensus, and since he is one of the RMs, ... And beside i sort of agree with his arguments about compatibility problems. Friendly, Sven Luther
Re: Updating the install manual info at the ddp web pages
On Sun, Jan 09, 2005 at 10:47:13PM +0100, Frans Pop wrote: On Sunday 02 January 2005 00:10, Frank Lichtenheld wrote: The information at http://www.debian.org/doc/user-manuals#install seems rather outdated. Perhaps someone could prepare an updated entry? (This hasn't to be a direct patch for the WML, the text and links would suffice) Thanks for drawing our attention to this! Below the current and a proposal for the new text. Joeyh: Can you please check. I've added this information but restructured it a bit. It should be available in the next webwml run so please verify it in 6-8 hours. Regards Javier signature.asc Description: Digital signature
Re: Bug#260763: [powerpc] Problems with logical volume setup during installation
Why? Because we don't know how MockOS will react to a partition _type_ set I don't know any MockOS, please provide real examples. s/MockOS/MacOS/g to anything but Apple_Bootstrap, Apple_HFS, Apple_UNIX_SVR2 or Apple_Free. If you're sure (or just reasonably confident) Linux_LVM will be ignored by Just give it a try and enlighten us. Just as soon as I get another spare disk. BTW anyone can try that, so the call goes to the Mac users in general. Apple boot and disk mount code, go ahead. I can only test this for a fairly narrow range of OS X versions, and maybe a resurrected 8.6. Since there's always the partition name (for Apple_UNIX_SVR2 partitions which MacOS ignores since prehistoric times), I didn't really want to bother testing this. Yeah, but imagine that the user wants to use the partition name for something sensible, and all this goes down. The user can still name the partition anything (s)he wants as long as LVM is part of the name. And libfdisk (for example) used to look at the partition _name_ field in Mac partition tables for clues where to find swap. What's the problem with that? well, suppose that a french user wants to name it echange instead of swap ? Too bad really. Suppose a french user is even unhappy with the Linux_Swap type setting. Same thing. With respect to computers, broken english is lingua franca. though, let's just try with 'Linux_RAID' and 'Linux_LVM' partition _type_ fields in Mac partition tables, maybe add Linux_Swap later and keep plain data partitons as before. That should keep the comaptibility code to a minimum (look for 'swap' in type and name fields) and get the scheme some limited testing. Ok, but as said, Colin Watson vetoed me on that, and as we already have a parted in experimental, ... Which does this, so unstable parted we shouldn't bother about? A mac-fdisk user can change either at will. Linux always reserves your The future belongs to libparted frontends though. And this is not linux, but the new user-friendly debian-installer partman, so ... I don't care if it has super cow powers. You can't count on the partition table to be created by Linux tools, much less parted. right to shoot yourself into the foot. But for the sake of saving users from their own stupidity, go ahead with the scheme you suggested. I would have for ages, but Colin Watson vetoed it without larger consensus, and since he is one of the RMs, ... And beside i sort of agree with his arguments about compatibility problems. So who is the LVM tools maintainer, and which committee do we have to address this across distros? Michael
Re: Bug#260763: [powerpc] Problems with logical volume setup during installation
On Mon, Jan 10, 2005 at 12:49:45PM +0100, Michael Schmitz wrote: Why? Because we don't know how MockOS will react to a partition _type_ set I don't know any MockOS, please provide real examples. s/MockOS/MacOS/g to anything but Apple_Bootstrap, Apple_HFS, Apple_UNIX_SVR2 or Apple_Free. If you're sure (or just reasonably confident) Linux_LVM will be ignored by Just give it a try and enlighten us. Just as soon as I get another spare disk. BTW anyone can try that, so the call goes to the Mac users in general. Apple boot and disk mount code, go ahead. I can only test this for a fairly narrow range of OS X versions, and maybe a resurrected 8.6. Since there's always the partition name (for Apple_UNIX_SVR2 partitions which MacOS ignores since prehistoric times), I didn't really want to bother testing this. Yeah, but imagine that the user wants to use the partition name for something sensible, and all this goes down. The user can still name the partition anything (s)he wants as long as LVM is part of the name. Yeah. And libfdisk (for example) used to look at the partition _name_ field in Mac partition tables for clues where to find swap. What's the problem with that? well, suppose that a french user wants to name it echange instead of swap ? Too bad really. Suppose a french user is even unhappy with the Linux_Swap type setting. Same thing. With respect to computers, broken english is lingua franca. Ah, no, that is not the case. The partition type is something which is used by the system, and the user should not directly interfer with. The partition name is something else. though, let's just try with 'Linux_RAID' and 'Linux_LVM' partition _type_ fields in Mac partition tables, maybe add Linux_Swap later and keep plain data partitons as before. That should keep the comaptibility code to a minimum (look for 'swap' in type and name fields) and get the scheme some limited testing. Ok, but as said, Colin Watson vetoed me on that, and as we already have a parted in experimental, ... Which does this, so unstable parted we shouldn't bother about? Nope. the version in unstable is the same as the version in testing, which is imposed to us by the debian-installer development model. This is why the version which should have gone in unstable resulted in experimental, and we can't also not to much hack it, since it will be in unstable as soon as d-i is released or whatever. A mac-fdisk user can change either at will. Linux always reserves your The future belongs to libparted frontends though. And this is not linux, but the new user-friendly debian-installer partman, so ... I don't care if it has super cow powers. You can't count on the partition table to be created by Linux tools, much less parted. I can most assuredly count on each new debian/sarge install which is done on RAID or LVM partition to use partmam, which is d-i's libparted frontend. I doubt you could do it in another way without extensive d-i hacking, and we won't support those users which do so. right to shoot yourself into the foot. But for the sake of saving users from their own stupidity, go ahead with the scheme you suggested. I would have for ages, but Colin Watson vetoed it without larger consensus, and since he is one of the RMs, ... And beside i sort of agree with his arguments about compatibility problems. So who is the LVM tools maintainer, and which committee do we have to address this across distros? No idea, the lvm-tools and mdadm-tools maintainers would be a good start. Like said, all go ahead and reach a consensus, and i will implement it not only in debian's parted package, but also in upstream parted. And since all or most distro's out there use a libparted frontend to their installer ... Friendly, Sven Luther
Re: Daily Netinst bootable?
On Sun, Jan 09, 2005 at 08:21:42AM +0100, Christian Perrier wrote: [EMAIL PROTECTED]:~/tmp ls -l /home/bubulle/iso/sid_d-i/sarge-i386-netinst.iso -rw-r--r-- 1 bubulle vmware 136386560 2005-01-08 23:08 /home/bubulle/iso/sid_d-i/sarge-i386-netinst.iso [EMAIL PROTECTED]:~/tmp md5sum /home/bubulle/iso/sid_d-i/sarge-i386-netinst.iso a532c4464909cde1d97d78ef6243c131 /home/bubulle/iso/sid_d-i/sarge-i386-netinst.iso My vmware machine is setup for booting first from CD, then from HD, then from the network. However, it jumps to the network boot quite quickly (the virtual HD is not bootable) just as if the CD was not bootable. I had the same problem with a PII notebook, it was booting fine with an older netinstall CD, but not with the one I downloaded last friday: [EMAIL PROTECTED]:/data/maulaf/isoll sarge-i386-netinst.iso -rw-r--r-- 1 steigies users 136327168 Jan 6 23:00 sarge-i386-netinst.iso [EMAIL PROTECTED]:/data/maulaf/isomd5sum sarge-i386-netinst.iso b77e2b3d26dd31638d5609fd0a60726a sarge-i386-netinst.iso Christian
Re: Desktop task broken on !(i386/powerpc)
Sven Luther wrote: The minimal disk size needed to install. This used to be 800 Mo for a desktop system in woody, if i remember well. As documented in the installation manual, it's about 2 gb. I doubt that many machines you'd want to install the desktop task on will have a smaller hard drive. Woody was close to the same, since tasksel also included kde and gnome in the desktop task then. -- see shy jo signature.asc Description: Digital signature
(fwd) RE: ide troubles
thanks for your quick feedback, forwarding messages as debian-boot may have more insights? - Forwarded message from Will Lentz [EMAIL PROTECTED] - From: Will Lentz [EMAIL PROTECTED] RC2 doesn't have this problem! Yay! :-) Of course, now I get an error message saying: Failed to copy file from CDROM, Retry? and Alt-F4 shows: grep: /cdrom/dists//Release : No such file or directory How do I tell it to look for /cdrom/dists/sarge/Release? Thanks, Will -Original Message- From: maximilian attems [mailto:[EMAIL PROTECTED] On Behalf Of maximilian attems Sent: Monday, January 10, 2005 9:25 AM To: [EMAIL PROTECTED] Cc: Will Lentz Subject: Re: ide troubles tags 240932 moreinfo thanks have you tried to reporduce it with an recent d-i, like rc2: http://www.debian.org/devel/debian-installer/ can you provide the logs of the kernel oops you were experiencing. thanks maks - End forwarded message -
Bug#284996: Looking for a Sanity Check
Greetings. While attempting to "zero in" on the cause of a problem while partitioning a laptophdd (described in bug#284996) I put a copy of hexdump on a floppy, booted from a SargeRC-2 CD, and once the install progressed to the point where it looks for networkhardware, stopped, went to the 2nd console window and tried; cat /dev/ide/host0/bus0/target0/lun0/disc | /floppy/hexdump -C | more Which appears to work, but generated unexpected results (appeared to show that cfdisk 2.2corrupted the partition table of the hard drive, by repeatedly writing the function names'GreyString' and oregroundWindow'?) This begs the question; Am I seeing what I think I'mseeing? If I do the same thing starting with a single Win98 partition, the same area of the disk(judging from the addresses displayed by hexdump) appear far less suspicious, and include'55AA' (which I believe marks the end of the partition table for a bootable partition). So my question to the list is; Is it OK to use the above-mentioned cat-hexdump-morecommand, or am I deceiving myself somehow? TIA, Steve Kleiser
Re: [powerpc] Problems with logical volume setup during installation
Sven == Sven Luther [EMAIL PROTECTED] writes: Sven On Sun, Jan 09, 2005 at 09:54:14PM -0800, Shyamal Prasad Sven wrote: 1) PowerMac does not currently have Partition types for Linux. Today we are just using an Apple defined type (Apple_UNIX_SVR2) which is safe. Sven What exactly do you mean by safe ? I meant that it does not cause Apple's OF and other software to barf. Presumably Apple's code will tolerate unknown partition types 3) A proposal (from Sven, for example) is to use 'Linux LVM' as a partition type on PowerMac systems. Sven Yes, we should do the same for 'Linux RAID' (altough i would Sven use an underscore in both cases). OK. grunt work), but I'm not even sure where to start. I don't even Sven Maybe start with the lvm-tools debian maintainers ? OK. /Shyamal
Processing of linux-kernel-di-i386-2.6_1.01_i386.changes
linux-kernel-di-i386-2.6_1.01_i386.changes uploaded successfully to localhost along with the files: linux-kernel-di-i386-2.6_1.01.dsc linux-kernel-di-i386-2.6_1.01.tar.gz kernel-image-2.6.8-2-386-di_1.01_i386.udeb nic-modules-2.6.8-2-386-di_1.01_i386.udeb nic-extra-modules-2.6.8-2-386-di_1.01_i386.udeb nic-shared-modules-2.6.8-2-386-di_1.01_i386.udeb serial-modules-2.6.8-2-386-di_1.01_i386.udeb ppp-modules-2.6.8-2-386-di_1.01_i386.udeb socket-modules-2.6.8-2-386-di_1.01_i386.udeb ide-modules-2.6.8-2-386-di_1.01_i386.udeb ide-core-modules-2.6.8-2-386-di_1.01_i386.udeb cdrom-core-modules-2.6.8-2-386-di_1.01_i386.udeb cdrom-modules-2.6.8-2-386-di_1.01_i386.udeb firewire-core-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-core-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-common-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-extra-modules-2.6.8-2-386-di_1.01_i386.udeb plip-modules-2.6.8-2-386-di_1.01_i386.udeb floppy-modules-2.6.8-2-386-di_1.01_i386.udeb loop-modules-2.6.8-2-386-di_1.01_i386.udeb ipv6-modules-2.6.8-2-386-di_1.01_i386.udeb ext3-modules-2.6.8-2-386-di_1.01_i386.udeb jfs-modules-2.6.8-2-386-di_1.01_i386.udeb ntfs-modules-2.6.8-2-386-di_1.01_i386.udeb reiserfs-modules-2.6.8-2-386-di_1.01_i386.udeb xfs-modules-2.6.8-2-386-di_1.01_i386.udeb fat-modules-2.6.8-2-386-di_1.01_i386.udeb ufs-modules-2.6.8-2-386-di_1.01_i386.udeb md-modules-2.6.8-2-386-di_1.01_i386.udeb usb-modules-2.6.8-2-386-di_1.01_i386.udeb usb-storage-modules-2.6.8-2-386-di_1.01_i386.udeb pcmcia-storage-modules-2.6.8-2-386-di_1.01_i386.udeb fb-modules-2.6.8-2-386-di_1.01_i386.udeb input-modules-2.6.8-2-386-di_1.01_i386.udeb irda-modules-2.6.8-2-386-di_1.01_i386.udeb parport-modules-2.6.8-2-386-di_1.01_i386.udeb nic-pcmcia-modules-2.6.8-2-386-di_1.01_i386.udeb pcmcia-modules-2.6.8-2-386-di_1.01_i386.udeb nic-usb-modules-2.6.8-2-386-di_1.01_i386.udeb sata-modules-2.6.8-2-386-di_1.01_i386.udeb firmware-modules-2.6.8-2-386-di_1.01_i386.udeb acpi-modules-2.6.8-2-386-di_1.01_i386.udeb Greetings, Your Debian queue daemon
Bug#289756: installation-reports
Package: installation-reportsDebian-installer-version: Sarge uname -a:Date: 01/10/2005Method: CD netinst from here http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20050109/ Machine: Asus A7N8X-E Deluxe, w/Radeon 9200 AGP video card, USB keyboard and mouse.Processor: 3200+Memory: 512MBRoot Device: 1 SATA Western Digital HD using onboard SATA port.Root Size/partition table: Output of lspci and lspci -n: Base System Installation Checklist:[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try itInitial boot worked: [x]Configure network HW: [x]Config network: [x]Detect CD: [E]Load installer modules: [ ]Detect hard drives: [ ]Partition hard drives: [ ]Create file systems: [ ]Mount partitions: [ ]Install base system: [ ]Install boot loader: [ ]Reboot: [ ]Comments/Problems:Ive tried business card, netinst and disk 1 of the CD set. Each time the unstaller hangs here:Loading module sd_mod for SCSI disk supportIf I use the linux26 kernal the OS loads fine. Is there more information I can provide? I attempt to get it if there is.
linux-kernel-di-i386-2.6_1.01_i386.changes ACCEPTED
Accepted: acpi-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/acpi-modules-2.6.8-2-386-di_1.01_i386.udeb cdrom-core-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/cdrom-core-modules-2.6.8-2-386-di_1.01_i386.udeb cdrom-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/cdrom-modules-2.6.8-2-386-di_1.01_i386.udeb ext3-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ext3-modules-2.6.8-2-386-di_1.01_i386.udeb fat-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/fat-modules-2.6.8-2-386-di_1.01_i386.udeb fb-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/fb-modules-2.6.8-2-386-di_1.01_i386.udeb firewire-core-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/firewire-core-modules-2.6.8-2-386-di_1.01_i386.udeb firmware-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/firmware-modules-2.6.8-2-386-di_1.01_i386.udeb floppy-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/floppy-modules-2.6.8-2-386-di_1.01_i386.udeb ide-core-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ide-core-modules-2.6.8-2-386-di_1.01_i386.udeb ide-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ide-modules-2.6.8-2-386-di_1.01_i386.udeb input-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/input-modules-2.6.8-2-386-di_1.01_i386.udeb ipv6-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ipv6-modules-2.6.8-2-386-di_1.01_i386.udeb irda-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/irda-modules-2.6.8-2-386-di_1.01_i386.udeb jfs-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/jfs-modules-2.6.8-2-386-di_1.01_i386.udeb kernel-image-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/kernel-image-2.6.8-2-386-di_1.01_i386.udeb linux-kernel-di-i386-2.6_1.01.dsc to pool/main/l/linux-kernel-di-i386-2.6/linux-kernel-di-i386-2.6_1.01.dsc linux-kernel-di-i386-2.6_1.01.tar.gz to pool/main/l/linux-kernel-di-i386-2.6/linux-kernel-di-i386-2.6_1.01.tar.gz loop-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/loop-modules-2.6.8-2-386-di_1.01_i386.udeb md-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/md-modules-2.6.8-2-386-di_1.01_i386.udeb nic-extra-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/nic-extra-modules-2.6.8-2-386-di_1.01_i386.udeb nic-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/nic-modules-2.6.8-2-386-di_1.01_i386.udeb nic-pcmcia-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/nic-pcmcia-modules-2.6.8-2-386-di_1.01_i386.udeb nic-shared-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/nic-shared-modules-2.6.8-2-386-di_1.01_i386.udeb nic-usb-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/nic-usb-modules-2.6.8-2-386-di_1.01_i386.udeb ntfs-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ntfs-modules-2.6.8-2-386-di_1.01_i386.udeb parport-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/parport-modules-2.6.8-2-386-di_1.01_i386.udeb pcmcia-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/pcmcia-modules-2.6.8-2-386-di_1.01_i386.udeb pcmcia-storage-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/pcmcia-storage-modules-2.6.8-2-386-di_1.01_i386.udeb plip-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/plip-modules-2.6.8-2-386-di_1.01_i386.udeb ppp-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ppp-modules-2.6.8-2-386-di_1.01_i386.udeb reiserfs-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/reiserfs-modules-2.6.8-2-386-di_1.01_i386.udeb sata-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/sata-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-common-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/scsi-common-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-core-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/scsi-core-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-extra-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/scsi-extra-modules-2.6.8-2-386-di_1.01_i386.udeb scsi-modules-2.6.8-2-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/scsi-modules-2.6.8-2-386-di_1.01_i386.udeb serial-modules-2.6.8-2-386-di_1.01_i386.udeb to
small error in sarge installation manual
Riccardo Fabris pointed out an error in boot-installer/parameters.xml. The attached patch shoud fix the problem. If you agree, I will apply it. Bye, Giuseppe --- boot-installer/parameters.xml 2005-01-10 22:08:03.885978080 +0100 +++ boot-installer/parameters.xml.orig 2005-01-04 08:35:29.0 +0100 @@ -90,7 +90,7 @@ termdebconf/priority/term listitempara -This parameter settings will set the lowest priority of messages +This parameter settings will set the highest priority of messages to be displayed. /parapara
Processing of rootskel_1.10.1_i386.changes
rootskel_1.10.1_i386.changes uploaded successfully to localhost along with the files: rootskel_1.10.1.dsc rootskel_1.10.1.tar.gz rootskel_1.10.1_i386.udeb rootskel-bootfloppy_1.10.1_i386.udeb rootskel-locale_1.10.1_i386.udeb Greetings, Your Debian queue daemon
Processing of linux-kernel-di-ia64-2.6_1.1_ia64.changes
linux-kernel-di-ia64-2.6_1.1_ia64.changes uploaded successfully to localhost along with the files: linux-kernel-di-ia64-2.6_1.1.dsc linux-kernel-di-ia64-2.6_1.1.tar.gz kernel-image-2.6.8-2-itanium-smp-di_1.1_ia64.udeb nic-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb nic-shared-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb serial-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ppp-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ide-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ide-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb cdrom-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb firewire-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb scsi-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb scsi-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb plip-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb loop-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ipv6-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ext3-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb jfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ntfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb reiserfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb xfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb fat-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb ufs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb md-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb usb-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb usb-storage-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb fb-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb input-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb irda-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb parport-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb pcmcia-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb nic-usb-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb sata-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb firmware-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb Greetings, Your Debian queue daemon
Processing of ddetect_1.12_i386.changes
ddetect_1.12_i386.changes uploaded successfully to localhost along with the files: ddetect_1.12.dsc ddetect_1.12.tar.gz ethdetect_1.12_all.udeb hw-detect-full_1.12_all.udeb hw-detect_1.12_i386.udeb archdetect_1.12_i386.udeb Greetings, Your Debian queue daemon
kernel abiname transition and security updates status
Before we can release d-i rc3 we need all the kernels updated with at least some security fixes, notably the ones that change the kernel module ABI, and we need to update things to reflect the new kernel abiname. Here's my understanding of the current status of that: i386 2.4 and 2.6 updated to -2 abiname; debs not yet in testing; udebs updated. Until debs hit testing we cannot change rootskel/base-installer to use the new package names. ia64 Now same as i386. powerpc No abiname. 2.4 not updated(?). 2.6 updated, udebs updated, debs not yet in testing. As far as I know, no other arches except amd64 (not tracking that) are updated. Of the other arches, alpha, hppa (2.6), s390, and sparc have a abiname field in the kernel package names, so we really must wait on those before releasing rc3. arm, m68k, hppa (2.4), mips, and mipsel have no abinames, which just means past d-i releases will break even worse for those arches once the updated kernels and udebs reach testing. So I'd like to delay rc3 until those are updated with the abi changes too, to avoid having rc3 break after it's released. Anyway, I hope we can get the new kernels and udebs built for the missing arches in the next couple of weeks? -- see shy jo signature.asc Description: Digital signature
Re: small error in sarge installation manual
Giuseppe Sacco wrote: Riccardo Fabris pointed out an error in boot-installer/parameters.xml. The attached patch shoud fix the problem. If you agree, I will apply it. -This parameter settings will set the lowest priority of messages +This parameter settings will set the highest priority of messages Since this parameter settings is bad English too, I've committed a rewritten varient. -- see shy jo signature.asc Description: Digital signature
linux-kernel-di-ia64-2.6_1.1_ia64.changes is NEW
(new) cdrom-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer CDROM support This package contains core CDROM support for the Linux kernel. (new) ext3-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer EXT3 filesystem support This package contains the EXT3 filesystem module for the Linux kernel. (new) fat-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer FAT filesystem support This package contains the FAT and VFAT filesystem modules for the Linux kernel. (new) fb-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer Frame buffer support This package contains Frame buffer drivers for the Linux kernel. (new) firewire-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Core FireWire drivers This package contains core FireWire drivers for the Linux kernel. (new) firmware-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Firmware request modules This package contains linux kernel modules that support requesting external firmware. (new) ide-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer IDE support This package contains core IDE support for the Linux kernel. (new) ide-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer IDE drivers This package contains IDE drivers for the Linux kernel. (new) input-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer Input devices support This package contains input device drivers for the Linux kernel. (new) ipv6-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer IPv6 driver This package contains the IPv6 driver for the Linux kernel. (new) irda-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer Infrared devices support This package contains infrared device drivers for the Linux kernel. (new) jfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer JFS filesystem support This package contains the JFS filesystem module for the Linux kernel. (new) kernel-image-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer Linux kernel binary image for the Debian installer This package contains the Linux kernel image for the Debian installer boot images. It does _not_ provide a usable kernel for your full Debian system. linux-kernel-di-ia64-2.6_1.1.dsc to pool/main/l/linux-kernel-di-ia64-2.6/linux-kernel-di-ia64-2.6_1.1.dsc linux-kernel-di-ia64-2.6_1.1.tar.gz to pool/main/l/linux-kernel-di-ia64-2.6/linux-kernel-di-ia64-2.6_1.1.tar.gz (new) loop-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Loopback filesystem support This package contains loopback filesystem support for the Linux kernel. (new) md-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer RAID and LVM support This package contains RAID and LVM modules for the Linux kernel. (new) nic-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Common NIC drivers This package contains common NIC drivers for the Linux kernel. (new) nic-shared-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Shared NIC drivers This package contains NIC drivers needed by combinations of nic-modules, nic-extra-modules, and nic-pcmcia-modules. (new) nic-usb-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer USB NIC drivers This package contains USB network adapter drivers for the Linux kernel. (new) ntfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer NTFS filesystem support This package contains the NTFS file system module for the Linux kernel. (new) parport-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb extra debian-installer Parallel port support This package contains parallel port drivers for the Linux kernel. (new) pcmcia-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Common PCMCIA drivers This package contains common PCMCIA drivers for the Linux kernel. (new) plip-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb optional debian-installer PLIP drivers This package contains PLIP drivers for the Linux kernel. (new) ppp-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb optional debian-installer PPP drivers This package contains PPP drivers for the Linux kernel. (new) reiserfs-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Reiser filesystem support This package contains the Reiser filesystem module for the Linux kernel. (new) sata-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer SATA drivers This package contains SATA drivers for the Linux kernel. (new) scsi-core-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer Core SCSI subsystem This package contains the core SCSI subsystem for the Linux kernel. (new) scsi-modules-2.6.8-2-itanium-smp-di_1.1_ia64.udeb standard debian-installer SCSI drivers This package contains SCSI drivers for the Linux kernel. (new)
ddetect_1.12_i386.changes ACCEPTED
Accepted: archdetect_1.12_i386.udeb to pool/main/d/ddetect/archdetect_1.12_i386.udeb ddetect_1.12.dsc to pool/main/d/ddetect/ddetect_1.12.dsc ddetect_1.12.tar.gz to pool/main/d/ddetect/ddetect_1.12.tar.gz ethdetect_1.12_all.udeb to pool/main/d/ddetect/ethdetect_1.12_all.udeb hw-detect-full_1.12_all.udeb to pool/main/d/ddetect/hw-detect-full_1.12_all.udeb hw-detect_1.12_i386.udeb to pool/main/d/ddetect/hw-detect_1.12_i386.udeb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian.
ddetect override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): hw-detect-full_1.12_all.udeb: package says priority is standard, override says optional. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED])
rootskel_1.10.1_i386.changes ACCEPTED
Accepted: rootskel-bootfloppy_1.10.1_i386.udeb to pool/main/r/rootskel/rootskel-bootfloppy_1.10.1_i386.udeb rootskel-locale_1.10.1_i386.udeb to pool/main/r/rootskel/rootskel-locale_1.10.1_i386.udeb rootskel_1.10.1.dsc to pool/main/r/rootskel/rootskel_1.10.1.dsc rootskel_1.10.1.tar.gz to pool/main/r/rootskel/rootskel_1.10.1.tar.gz rootskel_1.10.1_i386.udeb to pool/main/r/rootskel/rootskel_1.10.1_i386.udeb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian.
Bug#289756: installation-reports
Brian Steele wrote: ... Machine: Asus A7N8X-E Deluxe, w/Radeon 9200 AGP video card, USB keyboard and mouse. ... I also see this with the same motherboard (see Bug #280950). What can we do to help diagnose this problem? Peter
Re: Desktop task broken on !(i386/powerpc)
Il giorno ven, 07-01-2005 alle 00:58 +0100, Frans Pop ha scritto: On Thursday 06 January 2005 20:12, Sven Luther wrote: They chose one, install it, don't like it, install the other. The new installer is easy to use, so it should be no problem :) flame_invite_mode=on I vote for KDE. flame_invite_mode=off ROTFL and just to share with all what Frans already knows: I vote for GNOME. :) Ciao sc -- Stefano Canepa - email: [EMAIL PROTECTED] - www: http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virt di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Desktop task and the Desktop machine partman recipe (was: )Re: Desktop task broken on !(i386/powerpc))
Quoting Joey Hess ([EMAIL PROTECTED]): As documented in the installation manual, it's about 2 gb. I doubt that many machines you'd want to install the desktop task on will have a smaller hard drive. Which, BTW, leaves us with the problem of the Desktop machine partman recipe which is likely to allow users have a 300Mb / partition and then later try to fit the Desktop task in it... #24... I'm reluctant in deciding alone to raise the minimum size for / to 2000MB in this recipe, at least without further discussionbut I think we should.
Next d-i release name (was: Re: kernel abiname transition and security updates status)
Quoting Joey Hess ([EMAIL PROTECTED]): Before we can release d-i rc3 we need all the kernels updated with at Should it be called RC3 or whatever better sounds like an official release name? Given that we indeed made quite few(?) changes, isn't it time for an official stamped release?
Re: Desktop task broken on !(i386/powerpc)
Il giorno ven, 07-01-2005 alle 10:48 +0100, Petter Reinholdtsen ha scritto: [Sven Luther] Do you really think that anyone installing debian will be baffled when asked to choose between the gnome or KDE desktop ? Do you seriously believe that ? Yes, I seriously believe that. I'm involved in the debian-edu subproject, and we try to make Debian available for all pupils and students during education. Several of the teachers responsible for setting up the computer network at their local school will be seriously baffled when asked to choose between gnome and kde. This is why the single Desktop task should not be deleted (IMWHO) and checking it should automatically check every subtask. I bet those people will probably be more confused by the various server tasks. Absolutely. Which is why I try to encurrage redusing the amount of questions during first time install, and hide the complexity and flexibility from common users view, to reduce the cognitive strain on the first time debian users. Us experts will find the options anyway. And you think it is easier for them to discover the KDE desktop once they have GDM running ? What do you imagine our current disk requirements are ? I do not believe these users _care_ if they get the KDE or gnome desktop. I have no idea what you mean by our current disk requirements. I agree with you in fact other distros take a decision for GNOME or KDE as default, for example Mandrake and Suse use KDM+KDE. Just my 2 sc -- Stefano Canepa - email: [EMAIL PROTECTED] - www: http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virt di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Re: kernel abiname transition and security updates status
* Joey Hess [EMAIL PROTECTED] [2005-01-10 16:24]: As far as I know, no other arches except amd64 (not tracking that) are mips and mipsel have been updated. However, given the new local root exploit (fixed in SVN), we'll all need to make another round of updates anyway. -- Martin Michlmayr http://www.cyrius.com/
Bug#289774: Install Report
Package: installation-reports INSTALL REPORT Debian-installer-version: 2004-10-26 from sid-amd64-netinst.iso on alioth uname -a: Linux athena 2.6.8-10-amd64-k8 #1 Thu Dec 30 11:45:02 CET 2004 x86_64 GNU/Linux Date: 2004-01-03 Method: Boot on CD, network install, ADSL (PPPoE) from http://debian-amd64.alioth.debian.org/pure64 sid main . No proxy. Machine: Full-custom PC Processor: AMD Athlon64 3000+ socket 939 Memory: Corsair value 1x512Mb Cas 2.5 Root Device: SATA Maxtor Diamond Max Plus 10, 200Gb 7200 RPM Root Size/partition table:i Device Boot Start End Blocks Id System /boot /dev/sda1 1 3 24066 83 Linux /dev/sda2 4 122 955867+ 82 Linux swap / Solaris WinXP /dev/sda3 * 1232554195350407 HPFS/NTFS /dev/sda42555 16105 108848407+ f W95 Ext'd (LBA) /mnt/data /dev/sda54987 1228158597056b W95 FAT32 Mandrake64 10.1 /dev/sda6 12282 1610530716248+ 83 Linux / /dev/sda72555498619534977 83 Linux Output of lspci and lspci -n: :00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0282 :00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1282 :00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2282 :00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3282 :00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4282 :00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7282 :00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South] :00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) :00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02) :00:0a.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13) :00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 05) :00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) :00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South] :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) --- :00:00.0 0600: 1106:0282 :00:00.1 0600: 1106:1282 :00:00.2 0600: 1106:2282 :00:00.3 0600: 1106:3282 :00:00.4 0600: 1106:4282 :00:00.7 0600: 1106:7282 :00:01.0 0604: 1106:b188 :00:07.0 0c00: 1106:3044 (rev 80) :00:08.0 0104: 105a:3373 (rev 02) :00:0a.0 0200: 11ab:4320 (rev 13) :00:0c.0 0200: 8086:1229 (rev 05) :00:0f.0 0104: 1106:3149 (rev 80) :00:0f.1 0101: 1106:0571 (rev 06) :00:10.0 0c03: 1106:3038 (rev 81) :00:10.1 0c03: 1106:3038 (rev 81) :00:10.2 0c03: 1106:3038 (rev 81) :00:10.3 0c03: 1106:3038 (rev 81) :00:10.4 0c03: 1106:3104 (rev 86) :00:11.0 0601: 1106:3227 :00:11.5 0401: 1106:3059 (rev 60) :00:18.0 0600: 1022:1100 :00:18.1 0600: 1022:1101 :00:18.2 0600: 1022:1102 :00:18.3 0600: 1022:1103 :01:00.0 0300: 10de:0322 (rev a1) 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: [E] 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:[E] Reboot: [E] Comments/Problems: The PPPoE option is not proposed by the installer for network configuration. It must be done manually later on. The base system install started well, but the finalization raised a kernel panic due to acpi. I needed to pass acpi=off to the kernel for the base install to complete. The boot loader install
Re: Next d-i release name (was: Re: kernel abiname transition and security updates status)
On Mon, Jan 10, 2005 at 11:17:09PM +0100, Christian Perrier wrote: Quoting Joey Hess ([EMAIL PROTECTED]): Before we can release d-i rc3 we need all the kernels updated with at Should it be called RC3 or whatever better sounds like an official release name? Given that we indeed made quite few(?) changes, isn't it time for an official stamped release? What is quite a few changes here? I thought the next d-i release was going to be bugfixes and kernel updates only? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#289786: installation-report
Package: installation-reports Debian-installer-version: 2005/01/01 uname -a: Linux nis1 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux Date: 2005/01/10 Method: Boot CD-ROM, http install from debian.lanl.gov Machine: EPIA M1 Processor: Memory: 512MB Root Device: IDE /dev/hda Root Size/partition table: # cfdisk -P s /dev/hda Partition Table for /dev/hda First Last # Type Sector Sector OffsetLength Filesystem Type (ID) Flag -- --- --- --- -- --- 1 Primary 0 3676049 63 3676050 Linux (83) Boot 2 Primary 367605012672449 0 8996400 W95 Ext'd (LBA) (0F) None 5 Logical 3676050 4156109 63 480060 Linux swap (82) None 6 Logical 4156110 8062739 63 3906630 Linux (83) None 7 Logical 806274012672449 63 4609710 Linux (83) None # df /dev/hda1 on / type reiserfs (rw,notail) 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) /dev/hda7 on /home type reiserfs (rw) /dev/hda6 on /mirror/radiant-server type reiserfs (rw) usbfs on /proc/bus/usb type usbfs (rw) Output of lspci and lspci -n: # lspci :00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] :00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] :00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) :00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) :00:14.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) :01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) # lspci -n :00:00.0 0600: 1106:3123 :00:01.0 0604: 1106:b091 :00:0d.0 0c00: 1106:3044 (rev 80) :00:10.0 0c03: 1106:3038 (rev 80) :00:10.1 0c03: 1106:3038 (rev 80) :00:10.2 0c03: 1106:3038 (rev 80) :00:10.3 0c03: 1106:3104 (rev 82) :00:11.0 0601: 1106:3177 :00:11.1 0101: 1106:0571 (rev 06) :00:11.5 0401: 1106:3059 (rev 50) :00:12.0 0200: 1106:3065 (rev 74) :00:14.0 0200: 11ad:0002 (rev 20) :01:00.0 0300: 1106:3122 (rev 03) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E] Configure network HW: [O] Config network: [E] 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] Comments/Problems: The splash screen has no text. There is simply a picture of Debian against a black background. Even when typing in characters, no characters appear on the screen. Only through F1 was I able to go get some insight as to what to do. But someone else had to tell me to hit F1 because there was no text/help instructions. When running through the initial install (before the reboot) the network configuration found 3 network cards: onboard VIA-RHINE(eth0), Lite-On(eth1), and a FireWire interface(eth2). So I configured eth1 with an IP address since that was where the ethernet cable is plugged in. Upon reboot, the network cards were now: eth0 (VIA-RHINE), FireWire(eth1), and Lite-On(eth2). Because this part of the install asks to configure apt, I chose to install over a local mirror (http://debian.lanl.gov) and subsequently ran into problems because the network was not configured. Only by going to TTY2 (alt+F2), logging in as root, and modifying /etc/network/interfaces, was I able to get the network back up. This error occurred both when using linux26 and expert26 as the initial boot options. I believe the cause was that modules were loaded in a different order upon reboot. To a beginner, this is a serious problem because the network was working (initial boot), and then it wasn't (after reboot), with no way to
Re: Create software raid array during install, error when filesystems is created.
On Thu, Jan 06, 2005 at 10:07:48PM +0100, Bj?rn Nilsson wrote: Hi, I have 2 equally sized IDE PATA disks. I created a partition covering the whole drive on each disk, the partition type was raid. I created a software RAID0 array, and in turn created partitions on it and set them to ReiserFS. So you created one big RAID partition, and then made partitions in it? This is contrary to the way RAID on Linux works, and if partman allowed you to do it, that's a bug, and explains what happened next... In the next step, When the filesystem are supposed to be created a get a red screen telling me: Failed to create ReiserFS part1 on RAID0- unit0. If i swich to the third virtual console i see this messsage: Stat of the device /dev/md/0/part1 failed. I have tried RAID1 also, ext3 instead of Reiser. Also tried to use the LVM to set up a volume group and so on, all with about the same result, failure when creating file system. So I installed on just 1 drive as normal, and that worked fine (impressive stuff with the hw autodetection btw!) I have tried with rc2 and nightly build from 2005-01-05, same result I read some problems with lilo or grub when using software raid, but that seems unrelated becouse this is well before any bootloader is installed. If you want to do what you've described, you'll need to put LVM over the top of the RAID0 volume, and create multiple logical volumes out of it, and treat them as you would partitions. regards Andrew -- linux.conf.au 2005 - http://linux.conf.au/ - Birthplace of Tux April 18th to 23rd - http://linux.conf.au/ - LINUX Canberra, Australia - http://linux.conf.au/ -Get bitten! signature.asc Description: Digital signature
Changed naming scheme for templates for network-console, s390-dasd s390-netdevice
Hi Joey, After the discussion on #debian-boot, I've changed the naming scheme for three modules that had debian-installer/ prefixes. They now use the module name as prefix, conform most modules. - debian-installer/network-console/... - network-console/... - debian-installer/s390/netdevice/... - s390-netdevice/... - debian-installer/s390/dasd/... - s390-dasd/... - debian-install/s390/dasd/... - s390-dasd/... Some remarks: - I've not changed the name of debian-installer/module/title templates - For s390-dasd I've also introduced a TEMPLATE_PREFIX define in dasd.c - All packages build correctly but have not been tested - I've checked that templates are not used in other modules Could you please revise the changes (r24891) and upload if OK? Not sure if this change should also be implemented for Sarge. TIA, Frans pgp53pIRCY1Xx.pgp Description: PGP signature
Processing of linux-kernel-di-sparc-2.6_0.05_sparc.changes
linux-kernel-di-sparc-2.6_0.05_sparc.changes uploaded successfully to localhost along with the files: linux-kernel-di-sparc-2.6_0.05.dsc linux-kernel-di-sparc-2.6_0.05.tar.gz kernel-image-2.6.8-2-sparc64-di_0.05_sparc.udeb nic-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb ppp-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb ide-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb cdrom-core-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb scsi-core-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb scsi-common-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb plip-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb ipv6-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb ext3-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb reiserfs-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb xfs-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb fat-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb md-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb usb-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb kernel-image-2.6.8-2-sparc32-di_0.05_sparc.udeb nic-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb ppp-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb cdrom-core-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb scsi-core-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb scsi-common-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb plip-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb ipv6-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb ext3-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb reiserfs-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb xfs-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb fat-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb md-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb Greetings, Your Debian queue daemon
linux-kernel-di-sparc-2.6_0.05_sparc.changes is NEW
(new) cdrom-core-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb standard debian-installer CDROM support This package contains core CDROM support for the Linux kernel. (new) cdrom-core-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb standard debian-installer CDROM support This package contains core CDROM support for the Linux kernel. (new) ext3-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb standard debian-installer EXT3 filesystem support This package contains the EXT3 filesystem module for the Linux kernel. (new) ext3-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb standard debian-installer EXT3 filesystem support This package contains the EXT3 filesystem module for the Linux kernel. (new) fat-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb extra debian-installer FAT filesystem support This package contains the FAT and VFAT filesystem modules for the Linux kernel. (new) fat-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb extra debian-installer FAT filesystem support This package contains the FAT and VFAT filesystem modules for the Linux kernel. (new) ide-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb standard debian-installer IDE drivers This package contains IDE drivers for the Linux kernel. (new) ipv6-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb extra debian-installer IPv6 driver This package contains the IPv6 driver for the Linux kernel. (new) ipv6-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb extra debian-installer IPv6 driver This package contains the IPv6 driver for the Linux kernel. (new) kernel-image-2.6.8-2-sparc32-di_0.05_sparc.udeb extra debian-installer Linux kernel binary image for the Debian installer This package contains the Linux kernel image for the Debian installer boot images. It does _not_ provide a usable kernel for your full Debian system. (new) kernel-image-2.6.8-2-sparc64-di_0.05_sparc.udeb extra debian-installer Linux kernel binary image for the Debian installer This package contains the Linux kernel image for the Debian installer boot images. It does _not_ provide a usable kernel for your full Debian system. linux-kernel-di-sparc-2.6_0.05.dsc to pool/main/l/linux-kernel-di-sparc-2.6/linux-kernel-di-sparc-2.6_0.05.dsc linux-kernel-di-sparc-2.6_0.05.tar.gz to pool/main/l/linux-kernel-di-sparc-2.6/linux-kernel-di-sparc-2.6_0.05.tar.gz (new) md-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb extra debian-installer RAID and LVM support This package contains RAID and LVM modules for the Linux kernel. (new) md-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb extra debian-installer RAID and LVM support This package contains RAID and LVM modules for the Linux kernel. (new) nic-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb standard debian-installer Network card modules for Sparc kernels This package contains the drivers for the Happy Meal/Big Mac 10/100BaseT, Sun QuadEthernet and MyriCOM Gigabit Ethernet SBus devices for SPARC systems, as well as various PCI NIC drivers (only on sparc64.) . Do not install this package on a real Debian system! You probably want a kernel-image package instead. (new) nic-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb standard debian-installer Network card modules for Sparc kernels This package contains the drivers for the Happy Meal/Big Mac 10/100BaseT, Sun QuadEthernet and MyriCOM Gigabit Ethernet SBus devices for SPARC systems, as well as various PCI NIC drivers (only on sparc64.) . Do not install this package on a real Debian system! You probably want a kernel-image package instead. (new) plip-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb optional debian-installer PLIP drivers This package contains PLIP drivers for the Linux kernel. (new) plip-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb optional debian-installer PLIP drivers This package contains PLIP drivers for the Linux kernel. (new) ppp-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb optional debian-installer PPP drivers This package contains PPP drivers for the Linux kernel. (new) ppp-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb optional debian-installer PPP drivers This package contains PPP drivers for the Linux kernel. (new) reiserfs-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb standard debian-installer Reiser filesystem support This package contains the Reiser filesystem module for the Linux kernel. (new) reiserfs-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb standard debian-installer Reiser filesystem support This package contains the Reiser filesystem module for the Linux kernel. (new) scsi-common-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb standard debian-installer Very common SCSI drivers This package contains very common SCSI drivers for the Linux kernel. (new) scsi-common-modules-2.6.8-2-sparc64-di_0.05_sparc.udeb standard debian-installer Very common SCSI drivers This package contains very common SCSI drivers for the Linux kernel. (new) scsi-core-modules-2.6.8-2-sparc32-di_0.05_sparc.udeb standard debian-installer Core SCSI subsystem This package contains the core SCSI subsystem for the Linux kernel. (new)
Re: Next d-i release name (was: Re: kernel abiname transition and security updates status)
On Mon, Jan 10, 2005 at 03:44:37PM -0800, Steve Langasek wrote: On Mon, Jan 10, 2005 at 11:17:09PM +0100, Christian Perrier wrote: Quoting Joey Hess ([EMAIL PROTECTED]): Before we can release d-i rc3 we need all the kernels updated with at Should it be called RC3 or whatever better sounds like an official release name? Given that we indeed made quite few(?) changes, isn't it time for an official stamped release? What is quite a few changes here? I thought the next d-i release was going to be bugfixes and kernel updates only? I think Christian really meant quite few (i.e. not many) rather than quite a few (i.e. several) here. Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: Bug#260763: [powerpc] Problems with logical volume setup during installation
Michael == Michael Schmitz [EMAIL PROTECTED] writes: Michael s/MockOS/MacOS/g Michael to anything but Apple_Bootstrap, Apple_HFS, Michael Apple_UNIX_SVR2 or Apple_Free. If you're sure (or just Michael reasonably confident) Linux_LVM will be ignored by Michael Sven Just give it a try and enlighten us. Michael Just as soon as I get another spare disk. BTW anyone can Michael try that, so the call goes to the Mac users in general. I have a PowerMac7,3 (Dual G5) that is intended to run Linux so I gave it a shot. I created a partition with type Linux_LVM and name LVM_Test using mac-fdisk. I put an ext3 file system on the partition so I could fsck/mount it to see if the Mac OS programs or OF screwed around with the partition data itself. Then I did the following tests. Booted into Mac OS X 10.3.7 (Open Firmware 5.1.8f7) and used the Disk Utility to look at the partitions. The test partition shows up, and a Get Info showed its type as 'Linux_LVM'. Booted back into Linux and the Linux_LVM partition was still good. Then I put the G5 into target disk mode after hooking it to a G4 Laptop (can you tell Mac's are becoming popular in this family?) with a firewire cable. The G4 runs Mac OS X 10.2.8, Open Firmware 4.7.2f2. I used Disk Utility on it to examine the target mode disk on the G5, and only the HFS+ partition with Mac OS X showed up. I booted the G5 back into Linux, the Linux partition is there and looked good. Then I put the G5 back in target disk mode. On the laptop I fired up Mac OS 9.2.2 US System Profiler (via OS 10.2.8) and looked at 'Devices and Volumes'. I only see the HFS+ volume there. Okay, so I booted the G5 into Linux and the Linux_LVM partition was still good. Okay, so I boot the G5 into target disk mode one last time with laptop powered off. Then I boot laptop into it's Open Firmware. Look around with devalias. I don't see the G5 disk - I don't know if there is something I can do to mount it so I can't see if this firmware rev. screws with it (no, I don't have permission to do any Linux stuff on the G4 laptop so I can't put a test partition on it directly :-) So, yes, I think the partition names don't freak out the last 2 or 3 generations of MacOS software. If I'm missing some obvious test let me know, I should be able to try it. Cheers! Shyamal
