Re: Roll call for porters of architectures in sid and testing
Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the jessie release: For sh4, I - test packages on this architecture - triage arch-specific bugs - fix arch-related bugs - maintain buildds For armel and armhf, I - test packages on this architecture - triage arch-specific bugs - fix arch-related bugs I am a DD. Best regards, Nobuhiro On Sun, 1 Sep 2013 09:33:51 +0200 (CEST) ni...@thykier.net (Niels Thykier) wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, > > As we announced in [LAST-BITS], we would like to get a better idea of > that status of the ports, to make an informed decision about which > port can be released with jessie. One of the steps is to get an > overview of which of the porters are (still) active for each > port. Once the results from the role-call are in, we will request > other information about the status of the ports. In the meantime, feel > free to update and collect info about the ports in the Debian wiki[WIKI]. > > If you are (or intend to become) an active porter for the lifetime of > jessie, then please send a signed email explaining your involvement in > the port to the Release Team before > 1st of October 2013. Please explain the level of your involvement in > the port. > > Feel free to use the following template as your reply: > > """ > Hi, > > I am an active porter for the following architectures and I intend > to continue this for the lifetime of the jessie release: > > For , I > - test (most|all) packages on this architecture > - fix toolchain issues > - triage arch-specific bugs > - fix arch-related bugs > - maintain buildds > - ... > > > > > """ > > Niels, on behalf of the release team > > [LAST-BITS] > http://lists.debian.org/debian-devel-announce/2013/08/msg6.html > > [WIKI] https://wiki.debian.org/ArchiveQualification/Jessie > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.14 (GNU/Linux) > > iQIcBAEBCAAGBQJSIu2TAAoJEAVLu599gGRC86EP/j/7FEZ9pxpTEHrBI41GTu6r > nENS5kAZAuxFQHfYLtKexBcgneGd6cgdmr3cIoh1ZL9lJgXq74X8FL5IbWNqUw9S > o9UQWpZJiwIIlH4fqSgFVLIphI0DQr7dXI7xcDIm4kl6Fdruo1tGxX8xqL23jzdP > nQb3jrXv3bj5943MfWeCbODILv2N6qev9VtWeQ6Wmh8PvxRUl7VqgdQaeHtlMsUp > TQT5fz0cw8gc2amlwlOZxaGDV2C8mHboJIKMEsu79BK4SlFSED9rXn4juFPUnAgG > uADsMdBBqEIgSMN42cPHQju+KLfJe/+xScmlzzDS/d7aWWs02TibcQ1ZnPi+bcgp > bd/Wa0lms+Fc2OpcuFle9Lwo+2B+ka1Dd3itm+D0SbmrxoGi6CuMMwydLcQbSJ73 > hHw9HJEIQr2x/ZItNPJrSvvj50rwYXcmFbxtVAwv2pFXfQ37iukYgAaaMvnwpNNJ > 6dM1coCF9skNkXLO8rkZ+5aupGgjpS9BdKKAEQrPy/aoaW9KNCZrLQeA4C3QySBU > OcCNBv7taSjVAVNszKtRIQpu2gzFGAV0u9Gj41qW1JzDHYrmAvMyGxrndOxTmaFr > p05QWgcMsPhNvdHjd6sWLyzJ5NYUKksCPMRgCc0BEd6moIyrt7UFsp2+guJZPBJ0 > pffEJGK2iGtrWmJfElof > =TUeZ > -END PGP SIGNATURE- > > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20130901073351.a92862...@thykier.net -- Nobuhiro Iwamatsu pgpBrQG6Z4mkc.pgp Description: PGP signature
Re: Compiling vanilla kernel issues.
Kieron, First off, do you see your initrd in /boot? If not, then that's clearly a problem. Can you run 'silo' without parameters? I believe that just checks the configuration. Second, I'm assuming you're mounting a local disk. Do you: 1) Have the right filesystem driver compiled (root of ext4 -> compiled ext4 code) 2) Have the right SCSI driver for your chipset 3) Can verify either the modules exist in initrd OR they are compiled-in (i.e. not modules). 4) Can verify when booting that the SCSI driver loads AND detects your disk. If you are not using initrd, then you probably have to use the "root=/dev/sdaX", where X is some integer instead of "root=REALLY_LONG_UUID_OF_DISK". On Tue, Sep 24, 2013 at 7:52 PM, Kieron Gillespie < ciaran.gilles...@gmail.com> wrote: > So still no joy on my Sun Blade2500 going to post my exact steps, and > maybe I'm still just missing something stupid. > > tar xfv linux-3.11.1.tar.xz > cd linux-3.11.1 > cp /boot/config-3.2.0-4-sparc64-smp ./.config > make oldconfig > make clean > make -j2 deb-pkg > cd ../ > dpkg -i *.deb > vi /etc/silo.conf > reboot > > and kernel panic trying to find the root file system. > > So am I copying the old config incorrectly? I get asked a lot of questions > about configuring options, which I just go with the default response. > Does anyone have a build I can download? Wondering if I try installing a > known working set of deb packages if the issue goes away. > > Thanks again. > > -Kieron > > > On Mon, Sep 23, 2013 at 10:40 AM, Hartwig Atrops > wrote: > >> Hi. >> >> I repeated the test on a Blade 100 (ATAPI/IDE system, Openboot 4, test >> kernel >> 3.11.1): >> >> No problems ... >> >> Regards, >> >>Hartwig >> >> >> On Saturday 21 September 2013 22:37:02 Kieron Gillespie wrote: >> > Strange as those steps you mentioned are exactly what I am doing on my >> two >> > SPARC systems. >> > >> > I am going to have to guess this is an issue with these particular >> pieces >> > of hardware the Sun Blade 2500 and the Sun Fire T2000. >> > >> > Thanks for the help, I just wanted to eliminate the possibility I was >> just >> > making some stupid mistake. Looks like it's more than that. I'll >> > investigate more. >> > >> > -Kieron >> > >> > On Sat, Sep 21, 2013 at 3:53 PM, Hartwig Atrops >> wrote: >> > > Hi. >> > > >> > > I used the Debian Linux Kernel Handbook: >> > > >> > > http://kernel-handbook.alioth.debian.org/ >> > > >> > > I fetched the 3.11.1 kernel source from kernel.org (wget) and >> unpacked it >> > > under /usr/src. >> > > >> > > During installation of Wheezy, I installed my usual tool set including >> > > make, >> > > gcc, g++ etc. >> > > >> > > To build the kernel, I additionally installed: >> > > >> > > build-essentials >> > > fakeroot >> > > devscripts (I don't think we need that) >> > > >> > > and run apt-get build-dep linux >> > > >> > > And now: >> > > >> > > copy configuration from /boot >> > > make oldconfig >> > > make clean (I don't think this is necessary) >> > > make deb-pkg >> > > >> > > installation via dpkg -i (4 packages) >> > > >> > > configure /boot/silo.conf (additional entry) >> > > >> > > and reboot - it works. >> > > >> > > You didn't mention the build packages, the rest looks the same ... >> > > >> > > Regards, >> > > >> > >Hartwig >> > > >> > > On Saturday 21 September 2013 17:42:00 Kieron Gillespie wrote: >> > > > Could you send me a link to the exact procedure you used. I keep >> find >> > > >> > > like >> > > >> > > > four different ways to make a vanilla kernel for Debian. >> > > > >> > > > Two of my systems are SCSI based and both of those have problems >> when I >> > > >> > > do >> > > >> > > > the standard >> > > > >> > > > cp /boot/config- ./.config >> > > > >> > > > make oldconfig >> > > > make deb-pkg >> > > > >> > > > dpkg -i linux-*.deb >> > > > >> > > > >> > > > -Kieron >> > > > >> > > > On Sat, Sep 21, 2013 at 3:11 AM, Hartwig Atrops >> > > >> > > wrote: >> > > > > Hi. >> > > > > >> > > > > Last night, I've built a kernel 3.11.1 from kernel.org the >> Debian way >> > > >> > > (as >> > > >> > > > > described in "Debian Linux Kernel Handbook") - without any >> problems. >> > > > > >> > > > > My test environment: a fresh installation of Wheezy (7.0.1) on a >> Sun >> > > > > Ultra 60, >> > > > > i.e. a SCSI machine. >> > > > > >> > > > > I'm going to do a test with an ATAPi/IDE Blade 100 as well, but I >> > > > > have >> > > >> > > to >> > > >> > > > > set >> > > > > up this machine first - that will take a while. >> > > > > >> > > > > Regards, >> > > > > >> > > > >Hartwig >> > > > > >> > > > > On Friday 20 September 2013 03:37:30 Kieron Gillespie wrote: >> > > > > > So current when I build the vanilla kernel using the typical >> Debian >> > > > > >> > > > > method >> > > > > >> > > > > > with make deb-pkg I end up with a kernel that panic's on boot. >> > > > > > >> > > > > > It says, >> > > > > > --CUT-- >> > > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on >> > > > > > unknown-bl
Re: Compiling vanilla kernel issues.
I am a linux guy too, but on my Sun Blade 100, I run OpenBSD - I could never get Debian to work right with it, but with OpenBSD, I have fvwm2, firefox3.6, R, perl, etc. It's not bad, it's fast, and it worked with no tweaking. On Tue, 24 Sep 2013, Kieron Gillespie wrote: So still no joy on my Sun Blade2500 going to post my exact steps, and maybe I'm still just missing something stupid. tar xfv linux-3.11.1.tar.xz cd linux-3.11.1 cp /boot/config-3.2.0-4-sparc64-smp ./.config make oldconfig make clean make -j2 deb-pkg cd ../ dpkg -i *.deb vi /etc/silo.conf reboot and kernel panic trying to find the root file system. So am I copying the old config incorrectly? I get asked a lot of questions about configuring options, which I just go with the default response. Does anyone have a build I can download? Wondering if I try installing a known working set of deb packages if the issue goes away. Thanks again. -Kieron On Mon, Sep 23, 2013 at 10:40 AM, Hartwig Atrops wrote: Hi. I repeated the test on a Blade 100 (ATAPI/IDE system, Openboot 4, test kernel 3.11.1): No problems ... Regards, Hartwig On Saturday 21 September 2013 22:37:02 Kieron Gillespie wrote: Strange as those steps you mentioned are exactly what I am doing on my two SPARC systems. I am going to have to guess this is an issue with these particular pieces of hardware the Sun Blade 2500 and the Sun Fire T2000. Thanks for the help, I just wanted to eliminate the possibility I was just making some stupid mistake. Looks like it's more than that. I'll investigate more. -Kieron On Sat, Sep 21, 2013 at 3:53 PM, Hartwig Atrops wrote: Hi. I used the Debian Linux Kernel Handbook: http://kernel-handbook.alioth.debian.org/ I fetched the 3.11.1 kernel source from kernel.org (wget) and unpacked it under /usr/src. During installation of Wheezy, I installed my usual tool set including make, gcc, g++ etc. To build the kernel, I additionally installed: build-essentials fakeroot devscripts (I don't think we need that) and run apt-get build-dep linux And now: copy configuration from /boot make oldconfig make clean (I don't think this is necessary) make deb-pkg installation via dpkg -i (4 packages) configure /boot/silo.conf (additional entry) and reboot - it works. You didn't mention the build packages, the rest looks the same ... Regards, Hartwig On Saturday 21 September 2013 17:42:00 Kieron Gillespie wrote: Could you send me a link to the exact procedure you used. I keep find like four different ways to make a vanilla kernel for Debian. Two of my systems are SCSI based and both of those have problems when I do the standard cp /boot/config- ./.config make oldconfig make deb-pkg dpkg -i linux-*.deb -Kieron On Sat, Sep 21, 2013 at 3:11 AM, Hartwig Atrops wrote: Hi. Last night, I've built a kernel 3.11.1 from kernel.org the Debian way (as described in "Debian Linux Kernel Handbook") - without any problems. My test environment: a fresh installation of Wheezy (7.0.1) on a Sun Ultra 60, i.e. a SCSI machine. I'm going to do a test with an ATAPi/IDE Blade 100 as well, but I have to set up this machine first - that will take a while. Regards, Hartwig On Friday 20 September 2013 03:37:30 Kieron Gillespie wrote: So current when I build the vanilla kernel using the typical Debian method with make deb-pkg I end up with a kernel that panic's on boot. It says, --CUT-- Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/1 Not tainted 3.12.0-rc #1 Call Trace: --END CUT-- Any ideas? If someone has instructions on how they typically build there kernel for SPARC system I would like to know. Though this is how I always have done it in the past it just recently stop working after 3.8.x series. On Thu, Sep 19, 2013 at 9:14 AM, Patrick Baggett wrote: I didn't have any problems, but I'm not using initramfs. To build a kernel 'the debian way', you might need to find a guide or maybe someone else can chime in? On Sep 18, 2013 10:05 PM, "Kieron Gillespie" < ciaran.gilles...@gmail.com> wrote: Hello everyone, Was wondering if anyone had any success compiling any of the vanilla Linux kernel's on their SPARC wheezy systems with anything after version 3.8.x. Every time I try to build myself a new kernel I seem to end up with a kernel that is unable to boot complaining about not being able to find the root file system. I was wondering if anyone has any information on how I can configure and build the Linux kernel for my various SPARC systems. -Kieron -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201309210911.41123.hartwig.atr...@arcor.de -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@li
Re: Compiling vanilla kernel issues.
So still no joy on my Sun Blade2500 going to post my exact steps, and maybe I'm still just missing something stupid. tar xfv linux-3.11.1.tar.xz cd linux-3.11.1 cp /boot/config-3.2.0-4-sparc64-smp ./.config make oldconfig make clean make -j2 deb-pkg cd ../ dpkg -i *.deb vi /etc/silo.conf reboot and kernel panic trying to find the root file system. So am I copying the old config incorrectly? I get asked a lot of questions about configuring options, which I just go with the default response. Does anyone have a build I can download? Wondering if I try installing a known working set of deb packages if the issue goes away. Thanks again. -Kieron On Mon, Sep 23, 2013 at 10:40 AM, Hartwig Atrops wrote: > Hi. > > I repeated the test on a Blade 100 (ATAPI/IDE system, Openboot 4, test > kernel > 3.11.1): > > No problems ... > > Regards, > >Hartwig > > > On Saturday 21 September 2013 22:37:02 Kieron Gillespie wrote: > > Strange as those steps you mentioned are exactly what I am doing on my > two > > SPARC systems. > > > > I am going to have to guess this is an issue with these particular pieces > > of hardware the Sun Blade 2500 and the Sun Fire T2000. > > > > Thanks for the help, I just wanted to eliminate the possibility I was > just > > making some stupid mistake. Looks like it's more than that. I'll > > investigate more. > > > > -Kieron > > > > On Sat, Sep 21, 2013 at 3:53 PM, Hartwig Atrops > wrote: > > > Hi. > > > > > > I used the Debian Linux Kernel Handbook: > > > > > > http://kernel-handbook.alioth.debian.org/ > > > > > > I fetched the 3.11.1 kernel source from kernel.org (wget) and > unpacked it > > > under /usr/src. > > > > > > During installation of Wheezy, I installed my usual tool set including > > > make, > > > gcc, g++ etc. > > > > > > To build the kernel, I additionally installed: > > > > > > build-essentials > > > fakeroot > > > devscripts (I don't think we need that) > > > > > > and run apt-get build-dep linux > > > > > > And now: > > > > > > copy configuration from /boot > > > make oldconfig > > > make clean (I don't think this is necessary) > > > make deb-pkg > > > > > > installation via dpkg -i (4 packages) > > > > > > configure /boot/silo.conf (additional entry) > > > > > > and reboot - it works. > > > > > > You didn't mention the build packages, the rest looks the same ... > > > > > > Regards, > > > > > >Hartwig > > > > > > On Saturday 21 September 2013 17:42:00 Kieron Gillespie wrote: > > > > Could you send me a link to the exact procedure you used. I keep find > > > > > > like > > > > > > > four different ways to make a vanilla kernel for Debian. > > > > > > > > Two of my systems are SCSI based and both of those have problems > when I > > > > > > do > > > > > > > the standard > > > > > > > > cp /boot/config- ./.config > > > > > > > > make oldconfig > > > > make deb-pkg > > > > > > > > dpkg -i linux-*.deb > > > > > > > > > > > > -Kieron > > > > > > > > On Sat, Sep 21, 2013 at 3:11 AM, Hartwig Atrops > > > > > > wrote: > > > > > Hi. > > > > > > > > > > Last night, I've built a kernel 3.11.1 from kernel.org the Debian > way > > > > > > (as > > > > > > > > described in "Debian Linux Kernel Handbook") - without any > problems. > > > > > > > > > > My test environment: a fresh installation of Wheezy (7.0.1) on a > Sun > > > > > Ultra 60, > > > > > i.e. a SCSI machine. > > > > > > > > > > I'm going to do a test with an ATAPi/IDE Blade 100 as well, but I > > > > > have > > > > > > to > > > > > > > > set > > > > > up this machine first - that will take a while. > > > > > > > > > > Regards, > > > > > > > > > >Hartwig > > > > > > > > > > On Friday 20 September 2013 03:37:30 Kieron Gillespie wrote: > > > > > > So current when I build the vanilla kernel using the typical > Debian > > > > > > > > > > method > > > > > > > > > > > with make deb-pkg I end up with a kernel that panic's on boot. > > > > > > > > > > > > It says, > > > > > > --CUT-- > > > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > > > > > unknown-block(0,0) > > > > > > > > > > > > CPU: 0 PID: 1 Comm: swapper/1 Not tainted 3.12.0-rc #1 > > > > > > Call Trace: > > > > > > --END CUT-- > > > > > > > > > > > > Any ideas? If someone has instructions on how they typically > build > > > > > > there kernel for SPARC system I would like to know. Though this > is > > > > > > how > > > > > > > > > I always have done it in the past it just recently stop working > > > > > > after 3.8.x > > > > > > > > > > series. > > > > > > > > > > > On Thu, Sep 19, 2013 at 9:14 AM, Patrick Baggett > > > > > > > > > > > > wrote: > > > > > > > I didn't have any problems, but I'm not using initramfs. To > build > > > > > > > a kernel 'the debian way', you might need to find a guide or > > > > > > > maybe > > > > > > > > > > someone > > > > > > > > > > > > else can chime in? > > > > > > > On Sep 18, 2013 10:05 PM, "Kieron Gillespie" < > > > > > > > > > > ciaran.gilles...@gmail.com> > > > > > > > > > > > > wrote: > > > > > > >> Hello
Re: Roll call for porters of architectures in sid and testing
Hi, I am not currently a porter but I would like to be one for the Hurd. I do some test on QEMU and public Hurd host. I am familiar with system programming and have some embedded and printer driver development experience. I use Linux for 11 year, family with cross compiling tool chain. I never contributed to Debian before, I read Debian developer guide and GNU maintainer guide recently. I want to focus on system usable issue like GUI or driver issue and back to Hurd itself if needed. I also wan't to make system clear for new comer. I am not a DD/DM Cong Zhang 2013/9/1 Niels Thykier > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, > > As we announced in [LAST-BITS], we would like to get a better idea of > that status of the ports, to make an informed decision about which > port can be released with jessie. One of the steps is to get an > overview of which of the porters are (still) active for each > port. Once the results from the role-call are in, we will request > other information about the status of the ports. In the meantime, feel > free to update and collect info about the ports in the Debian wiki[WIKI]. > > If you are (or intend to become) an active porter for the lifetime of > jessie, then please send a signed email explaining your involvement in > the port to the Release Team before > 1st of October 2013. Please explain the level of your involvement in > the port. > > Feel free to use the following template as your reply: > > """ > Hi, > > I am an active porter for the following architectures and I intend > to continue this for the lifetime of the jessie release: > > For , I > - test (most|all) packages on this architecture > - fix toolchain issues > - triage arch-specific bugs > - fix arch-related bugs > - maintain buildds > - ... > > > > > """ > > Niels, on behalf of the release team > > [LAST-BITS] > http://lists.debian.org/debian-devel-announce/2013/08/msg6.html > > [WIKI] https://wiki.debian.org/ArchiveQualification/Jessie > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.14 (GNU/Linux) > > iQIcBAEBCAAGBQJSIu2TAAoJEAVLu599gGRC86EP/j/7FEZ9pxpTEHrBI41GTu6r > nENS5kAZAuxFQHfYLtKexBcgneGd6cgdmr3cIoh1ZL9lJgXq74X8FL5IbWNqUw9S > o9UQWpZJiwIIlH4fqSgFVLIphI0DQr7dXI7xcDIm4kl6Fdruo1tGxX8xqL23jzdP > nQb3jrXv3bj5943MfWeCbODILv2N6qev9VtWeQ6Wmh8PvxRUl7VqgdQaeHtlMsUp > TQT5fz0cw8gc2amlwlOZxaGDV2C8mHboJIKMEsu79BK4SlFSED9rXn4juFPUnAgG > uADsMdBBqEIgSMN42cPHQju+KLfJe/+xScmlzzDS/d7aWWs02TibcQ1ZnPi+bcgp > bd/Wa0lms+Fc2OpcuFle9Lwo+2B+ka1Dd3itm+D0SbmrxoGi6CuMMwydLcQbSJ73 > hHw9HJEIQr2x/ZItNPJrSvvj50rwYXcmFbxtVAwv2pFXfQ37iukYgAaaMvnwpNNJ > 6dM1coCF9skNkXLO8rkZ+5aupGgjpS9BdKKAEQrPy/aoaW9KNCZrLQeA4C3QySBU > OcCNBv7taSjVAVNszKtRIQpu2gzFGAV0u9Gj41qW1JzDHYrmAvMyGxrndOxTmaFr > p05QWgcMsPhNvdHjd6sWLyzJ5NYUKksCPMRgCc0BEd6moIyrt7UFsp2+guJZPBJ0 > pffEJGK2iGtrWmJfElof > =TUeZ > -END PGP SIGNATURE- > > > -- > To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/20130901073351.a92862...@thykier.net > >
