Bug#1022061: at Salsa
Hi, > Where is develop happening? } Where is development happening? Seems to be at "salsa". stappers@juli:~/src $ debcheckout debian-kernel-handbook declared git repository at https://salsa.debian.org/kernel-team/kernel-handbook.git git clone https://salsa.debian.org/kernel-team/kernel-handbook.git debian-kernel-handbook ... Cloning into 'debian-kernel-handbook'... remote: Enumerating objects: 1283, done. remote: Counting objects: 100% (228/228), done. remote: Compressing objects: 100% (88/88), done. remote: Total 1283 (delta 169), reused 181 (delta 134), pack-reused 1055 Receiving objects: 100% (1283/1283), 412.97 KiB | 1.10 MiB/s, done. Resolving deltas: 100% (836/836), done. stappers@juli:~/src $ cd debian-kernel-handbook/ stappers@juli:~/src/debian-kernel-handbook $ ls chapter-bugs.dbk chapter-scope.dbk kernel-handbook.dbk chapter-common-tasks.dbk chapter-source.dbkMakefile chapter-initramfs.dbk chapter-update-hooks.dbk po4a chapter-modules.dbk chapter-versions.dbk stylesheet.xsl chapter-packaging.dbk debian stappers@juli:~/src/debian-kernel-handbook $ The silence in this bug report might be transmitting Yes, your contribution is welcome. Regards Geert Stappers -- What is the last time you did something for the first time?
Bug#1022061: Where is development happening?
Hi Debian Kernel Team, Where is develop happening? Groeten Geert Stappers P.S. At https://salsa.debian.org/kernel-team/kernel-handbook/-/tags is tag 1.20 missing. -- Silence is hard to parse
Bug#929557: additional point of view
An additional point of view. Prespective is Linux Kernel developer. OOT means Out of Tree. And the tree is the Linux source code directory tree. - Forwarded message from "Enrico Weigelt, metux IT consult" - Date: Wed, 29 May 2019 13:01:09 +0200 From: "Enrico Weigelt, metux IT consult" To: Dan , debian-kernel@lists.debian.org, debian-de...@lists.debian.org Subject: Re: ZFS in Buster User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 On 28.05.19 18:43, Dan wrote: > Sadly the Linux Kernel has introduced a commit in kernel 4.19 and 5.0> that > prevents ZFS from using SIMD. The result is that ZFS won't be> usable in Buster. See the following issue> https://github.com/zfsonlinux/zfs/issues/8793 We recently had this discussion on lkml - yet another case of 3rdparty folks that just don't follow the license rules. It's not the kernel who broke zfs, it's zfs that broke itself. The kernel is GPL, and they just have to follow the rules or go away. OOT modules are conceptionally messy in the first place. It's sometimes okay as an temporary workaround, until things get mainlined. But intentionally keeping things oot for long time is just silly and creates lots of more problems than it creates. And they're even using now *deeply* arch-internal functions directly. > NixOS reverted that particular commit:> https://www.phoronix.com/scan.php?page=news_item=NixOS-Linux-5.0-ZFS-FPU-Drop Intentional license violation. Not funny. > Debian is the "Universal Operating System" and gives the user the> option to > choose. It provides "vim and emacs", "Gnome and KDE", If you wanna have something new included, you'll have to sit down and do the actual work. In the end of the day, it's that simple. > Would it be possible to provide an alternative patched linux kernel > that works with ZFS? You mean patching against the license ? > The ZFS developers proposed the Linux developers to rewrite the whole > ZFS code and use GPL, but surprisingly the linux developers didn't > accept. See below: > https://github.com/zfsonlinux/zfs/issues/8314 Wait, no. It's not that we refused anything (actually, I don't even recall any decent discussion on that @lkml). There even wasn't anything to accept or refuse - except the existing code, that is nowhere near a quality where any maintainer likes to even have a closer look at. The major problem is that ZoL always has been oot on purpose, which is the wrong approach to begin with. That also leads to bad code quality (eg. lots of useless wrappers, horrible maintenance, ...) What ZoL folks could do is step by step rewrite it to use mainline functionality where ever technically feasible and work closely with upstream to introduce missing functionality. Obviously, their current proprietary userland interface can't be accepted for mainline - it has to be reworked to be conformant w/ standard uapi (eg. we already have it for things like snapshots, deduplication, quotas, ...) But it's up to ZoL developers to do the actual work and post patches to lkml. There won't be anybody else doing that. --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering i...@metux.net -- +49-151-27565287 - End forwarded message - Groeten Geert Stappers -- Leven en laten leven
Bug#728535: new URL
https://unix.stackexchange.com/questions/67936/attaching-usb-serial-device-with-custom-pid-to-ttyusb0-on-embedded because previous URL is broken.
Bug#891067: Patch for Backport of the Linux MegaRAID driver for SAS based RAID controllers for Debian Stretch
On Thu, Feb 22, 2018 at 10:28:09AM +0200, Doru Iorgulescu wrote: > Hello, > My error: > I copy /usr/src/linux-4.14.20/drivers/scsi/megaraid/ to > /usr/src/linux-4.9.82/drivers/scsi/megaraid/ > I compile the kernel 4.9.82, and the result is OK! Bugreport #891067 now updated with that information ( /ser/ versus /src/ )
newer kernel supports new hardware
Package: debian-kernel-handbook On Thu, Feb 22, 2018 at 09:20:22AM +0100, Geert Stappers wrote: > On Thu, Feb 22, 2018 at 06:21:00AM +0200, Doru Iorgulescu wrote: > > I copy /usr/src/linux-4.14.20/drivers/scsi/megaraid/ to > > /usr/ser/linux-4.9.82/drivers/scsi/megaraid/ > > I compile the kernel 4.9.82, and the result is OK! > > > > It is possible a kernel patch for that ? > >:-) > > I think that question is some what crippled by a language problem > or another source for misunderstanding. > The question was raised as https://lists.debian.org/debian-boot/2018/02/msg00339.html and https://lists.debian.org/debian-kernel/2018/02/msg00194.html and became https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891067 This bugreport against Debian kernel handbook is for asking to document what to do when new kernel supports new hardware. That `make deb` builds a .deb which can be installed with `dpkg -i ../linux-image-*.deb` What the policy is about backporting and releasing new kernels in stable. (See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890393 ) The idea, the wish, is that upon future simular questions posted at d-kernel@l.d.o and/or d-boot@l.d.o. can be answered with: Please visit URL=at=kernel=handbook for information what you can do Groeten Geert Stappers -- Leven en laten leven
Re: Patch for Backport of the Linux MegaRAID driver for SAS based RAID controllers for Debian Stretch
Control: tag -1 +patch On Thu, Feb 22, 2018 at 06:21:00AM +0200, Doru Iorgulescu wrote: > I copy /usr/src/linux-4.14.20/drivers/scsi/megaraid/ to > /usr/ser/linux-4.9.82/drivers/scsi/megaraid/ > I compile the kernel 4.9.82, and the result is OK! Bugreport tagged with 'patch', hope this helps. > It is possible a kernel patch for that ? :-) I think that question is some what crippled by a language problem or another source for misunderstanding. Groeten Geert Stappers -- Leven en laten leven
Re: Bug#864269: Bug#864233: unblock: linux/4.9.30-1
On Fri, Jun 09, 2017 at 03:29:39PM +0100, Ben Hutchings wrote: > On Tue, 2017-06-06 at 01:24 +0100, Ben Hutchings wrote: > > On Tue, 2017-06-06 at 01:29 +0200, Axel Beckert wrote: > > > > > > JFTR: This upload of linux 4.9.30-1 to unstable made at least one > > > package start to FTBFS in unstable, namely radvd. Please see > > > https://bugs.debian.org/864269 for details. > > > > radvd's autoconf test for has probably failed at least > > since Linux 2.6.32 when I made sure the kernel headers would never > > define struct sockaddr for userland: > > <https://git.kernel.org/linus/9c501935a3cdcf6b1d35aaee3aa11c7a7051a305> > > > > But the conflict between and is far > > older than that, so if the test ever passed it should have resulted in > > this build failure. I think that's a clear bug in radvd. It should > > use either one or the other, and I think the sensible thing is to use > > as it has been doing up until now. > > I intend to drop the kernel patch that triggered this regression in the > first update for stretch. FWIW the FTBFS of radvd has been fixed. Indeed by dropping linux/if_arp.h in favour of net/if_arp.h Groeten Geert Stappers DD, maintainer of radvd -- Leven en laten leven
Bug#862102: URL not line wrapped
http://blog.mycre.ws/articles/works-with-debian-intel-ssd-750-amd-firepro-w4100-dell-p2715q/
Bug#813881: Bug#813893: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id
Control: tag -1 patch
Bug#811198: linux: d-i package list: Please add 9p-modules
Control: merge -1 809435 Stop https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809435
Bug#809204: recomments versus depends
On Wed, Dec 30, 2015 at 01:31:43AM +, Ben Hutchings wrote: > On Wed, 2015-12-30 at 08:16 +0800, ? Dan Jacobson wrote: > > > > # apt-config dump|egrep Rec\|Sugg > > APT::Install-Recommends "false"; > > APT::Install-Suggests "0"; > > Users that do that need to accept > that they will encounter errors like this. Those users are the users that detect that a 'Recommends' has become a 'Depends' Groeten Geert Stappers -- Leven en laten leven
Bug#803677: Betrefft
On Thu, Nov 19, 2015 at 03:58:34PM +0100, Tim Wiederhake wrote: > Control: found -1 4.2.6-1 > > Am I doing this right? I think you do. At least you are doing better as on 2015-11-03 ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803677#10 ) Groeten Geert Stappers -- Leven en laten leven
Bug#797949: reformatted `dmesg | grep -i SDHCI` properly
$ dmesg | grep -i SDHCI [1.237764] sdhci: Secure Digital Host Controller Interface driver [1.237770] sdhci: Copyright(c) Pierre Ossman [1.263087] sdhci-pci :00:12.0: SDHCI controller found [8086:2296] (rev 21) [1.263442] sdhci-pci :00:12.0: failed to setup card detect gpio [1.264537] sdhci-pci :00:12.0: No vmmc regulator found [1.264543] sdhci-pci :00:12.0: No vqmmc regulator found [1.268300] mmc0: SDHCI controller on PCI [:00:12.0] using ADMA
Bug#800792: linux-image-4.2.0-1-amd64 hangs during boot at network
Control: tag -1 -moreinfo On Thu, Oct 08, 2015 at 07:37:55PM +0200, Hans wrote: > >cat /proc/cmdline > BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=UUID=changed_by_me_to_be_secret ro > quiet > I also attached the output of dmesg in the file kernelringbuffer.txt Thanks
Bug#800792: linux-image-4.2.0-1-amd64 hangs during boot at network
Control: tag -1 moreinfo On Sat, Oct 03, 2015 at 06:42:49PM +0200, Hans wrote: > > When the system boots up and the network shall be activated, the system > hangs for a long time (about 2 minutes). Then the systemd-counter > shows up and after the waiting time (about the mentioned 2 minutes), > the system continous booting. > > I suppose, something has changed in the network device module between > 3.16 and 4.X. > > It would be nice, if you could take a look at it. maybe this is easy > to be fixed. > Please provide more information, example given: * Log messages * Hardware being used * Which kernel modules being used * What you mean by boot. Is a cold boot or a resume after suspend? * kernel boot parameters Groeten Geert Stappers -- Leven en laten leven
Bug#800792: linux-image-4.2.0-1-amd64 hangs during boot at network
On Sat, Oct 03, 2015 at 07:44:22PM +0200, Hans wrote: > Am Samstag, 3. Oktober 2015, 19:02:53 schrieb Geert Stappers: > > Please provide more information, example given: > > * Log messages > Sorry, I believe, > there are no usable logfiles available as it happens at boot. There is `dmesg`, do dmesg > kernelringbuffer.txt and sent the file to this bugreport. > > * kernel boot parameters > See my /etc/default/grub: > # If you change this file, run 'update-grub' afterwards to update > sent the output of cat /proc/cmdline to this bugreport Groeten Geert Stappers -- Leven en laten leven
Re: about broadcom NIC
On Sat, Aug 15, 2015 at 01:39:13PM -0400, Robert Antonio Custodio Báez wrote: hi, i would like to know if you can help about this issue. my nic wirelesss is broadcom the drivers are this: Broadcom Corporation BCM43228 802.11a/b/g/n. i search on debian page but its works on time but after upgrade the OS the card don't work again. please can you give a real information about this issue Visit https://wiki.debian.org/wl and provide feedback. Cheers Geert Stappers
Bug#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
On Fri, May 01, 2015 at 11:50:31PM +0100, Ben Hutchings wrote: On Sat, 2015-05-02 at 01:39 +0300, Alexey Eromenko wrote: As far as I'm aware it's stable feature, and there is no downside from enabling it. [...] There is a downside: it consumes more memory and disk space (though not that much). And there is no need for it. Debian provides allready the information of zcat /proc/config.gz in a file with a name like config-VERSION-VER-ARCH which gets installed in /boot Example given grep -i -e floppy -e fdc /boot/config* Groeten Geert Stappers Who thinks that this bugreport should be closed or marked as 'WONTFIX' -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150502053056.gd23...@gpm.stappers.nl
Bug#779010: local in version
Rumours says that version number in the changelog should contain the string 'local' to get a build without (ABI) checks Please confirm, preferable in the README.source Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150223214054.gj23...@gpm.stappers.nl
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Thu, Dec 11, 2014 at 03:31:38PM +0200, EpsiloN EpsiloN wrote: Geert: do you have some plans investigate the problem more deeply? As said in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134#40 I have allready interresting problems :-) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141211182820.ge23...@gpm.stappers.nl
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Wed, Dec 10, 2014 at 10:40:40AM +0200, EpsiloN EpsiloN wrote: Any feedback is appreciated. Information that I couldn't find at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134 is where the iSCSI initiator gets it's IP configuration. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141210104745.gi9...@gpm.stappers.nl
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Wed, Dec 10, 2014 at 01:53:13PM +0200, EpsiloN EpsiloN wrote: Any idea why kernel hasn't read the /etc/network/interfaces during disk initilization? That is called boot sequence. Disk (driver) initalisation needs to be done before a disk can be read. Why does already working server hungs at random? That question has be seen. And this message shows that it is not ignored. I think #772134 could be an interresting problem and I know I have allready interresting problems :-) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141210125755.gc22...@gpm.stappers.nl
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Wed, Dec 10, 2014 at 03:14:16PM +0200, EpsiloN EpsiloN wrote: Is there any way to debug the problem? Advice: Analyze the core file(s) that where found -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141210132926.gb23...@gpm.stappers.nl
Bug#772416: initrd: support booting from chroot
On Sat, Dec 06, 2014 at 04:49:10PM +0100, lemonsqueeze wrote: Patch and details can be found here: https://github.com/lemonsqueeze/boot_chroot https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch $ wget https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch --2014-12-06 17:39:48-- https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch Resolving github.com (github.com)... 192.30.252.130 Connecting to github.com (github.com)|192.30.252.130|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'initrd.patch' [ = ] 36,652 167KB/s in 0.2s 2014-12-06 17:39:49 (167 KB/s) - 'initrd.patch' saved [36652] $ file initrd.patch initrd.patch: HTML document, UTF-8 Unicode text, with very long lines $ :-( Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141206164402.gr3...@gpm.stappers.nl
Bug#772416: initrd: support booting from chroot
On Sat, Dec 06, 2014 at 05:44:02PM +0100, Geert Stappers wrote:
On Sat, Dec 06, 2014 at 04:49:10PM +0100, lemonsqueeze wrote:
Patch and details can be found here:
https://github.com/lemonsqueeze/boot_chroot
https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
$ wget https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
Length: unspecified [text/html]
Real patch is
https://raw.githubusercontent.com/lemonsqueeze/boot_chroot/master/initrd.patch
Here inline (and also attached)
diff -Nru orig/init new/init
--- orig/init 2014-12-04 11:42:27.0 +0100
+++ new/init2014-12-04 17:24:18.0 +0100
@@ -149,6 +149,9 @@
ip=*)
IP=${x#ip=}
;;
+ chroot=*)
+ CHROOT=${x#chroot=}
+ ;;
boot=*)
BOOT=${x#boot=}
;;
diff -Nru orig/scripts/local new/scripts/local
--- orig/scripts/local 2014-12-04 11:42:27.0 +0100
+++ new/scripts/local 2014-12-04 11:45:23.0 +0100
@@ -150,6 +150,37 @@
fi
fi
+ if [ $CHROOT ]; then
+ if [ $mountroot_status != 0 ]; then
+ if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+ panic
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it. To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+
+ fi
+ fi
+
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+
+ if [ ! -d /host/${CHROOT} ]; then
+ panic ALERT! /host/${CHROOT} does not exist.
Dropping to a shell!
+ fi
+
+ # FIXME This has no error checking
+ mount --bind /host/${CHROOT} ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+ fi
+
[ $quiet != y ] log_begin_msg Running /scripts/local-bottom
run_scripts /scripts/local-bottom
[ $quiet != y ] log_end_msg
Thanks for the patch
Groeten
Geert Stappers
--
Leven en laten leven
diff -Nru orig/init new/init
--- orig/init 2014-12-04 11:42:27.0 +0100
+++ new/init 2014-12-04 17:24:18.0 +0100
@@ -149,6 +149,9 @@
ip=*)
IP=${x#ip=}
;;
+ chroot=*)
+ CHROOT=${x#chroot=}
+ ;;
boot=*)
BOOT=${x#boot=}
;;
diff -Nru orig/scripts/local new/scripts/local
--- orig/scripts/local 2014-12-04 11:42:27.0 +0100
+++ new/scripts/local 2014-12-04 11:45:23.0 +0100
@@ -150,6 +150,37 @@
fi
fi
+ if [ $CHROOT ]; then
+ if [ $mountroot_status != 0 ]; then
+ if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+panic
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it. To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+
+ fi
+ fi
+
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+
+ if [ ! -d /host/${CHROOT} ]; then
+ panic ALERT! /host/${CHROOT} does not exist. Dropping to a shell!
+ fi
+
+ # FIXME This has no error checking
+ mount --bind /host/${CHROOT} ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+ fi
+
[ $quiet != y ] log_begin_msg Running /scripts/local-bottom
run_scripts /scripts/local-bottom
[ $quiet != y ] log_end_msg
Re: d-i anna: no packages matching running kernel 3.16-2-amd64 in archive
On Mon, Nov 03, 2014 at 08:05:57AM +0100, Julien Cristau wrote: On Mon, Nov 3, 2014 at 06:12:45 +0100, Geert Stappers wrote: On Sun, Nov 02, 2014 at 11:12:59PM +0100, Julien Cristau wrote: On Sun, Nov 2, 2014 at 22:52:03 +0100, Geert Stappers wrote: ( Full text at https://lists.debian.org/debian-kernel/2014/11/msg00026.html ) Hi, background information: * debian-installer from 2014-10-02 Which image? It is a netboot. That image can't work after a kernel ABI change. You should use another image or a daily build. Cheers, Julien Hello Debian-Installer people, Inside http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/netboot.tar.gz is a 3.16-2 kernel. Using it yields anna[PID]: WARNING **: no packages matching running kernel 3.16-2-amd64 in archive. That seems due a kernel ABI change. To prevent further harm could http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/netboot.tar.gz be removed or updated? Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141103084434.gk9...@gpm.stappers.nl
Re: d-i anna: no packages matching running kernel 3.16-2-amd64 in archive
On Mon, Nov 03, 2014 at 09:44:34AM +0100, Geert Stappers wrote: On Mon, Nov 03, 2014 at 08:05:57AM +0100, Julien Cristau wrote: On Mon, Nov 3, 2014 at 06:12:45 +0100, Geert Stappers wrote: On Sun, Nov 02, 2014 at 11:12:59PM +0100, Julien Cristau wrote: On Sun, Nov 2, 2014 at 22:52:03 +0100, Geert Stappers wrote: ( Full text at https://lists.debian.org/debian-kernel/2014/11/msg00026.html ) Hi, background information: * debian-installer from 2014-10-02 Which image? It is a netboot. That image can't work after a kernel ABI change. You should use another image or a daily build. Cheers, Julien Hello Debian-Installer people, Now it is on -boot@l.d.o.( Previous only on -kernel ) Inside http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/netboot.tar.gz is a 3.16-2 kernel. Using it yields anna[PID]: WARNING **: no packages matching running kernel 3.16-2-amd64 in archive. That seems due a kernel ABI change. To prevent further harm could http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/netboot.tar.gz be removed or updated? It could be that the update process is stalled. Who can verify (and get it rolling again)? Information that I have: * The above netboot.tar is from 2014-10-02 * Announcement of Jessi debian-installer beta 2 is from 2014-10-05 In other words: archive shoud not have 2 october version, but a 5 october version. Workaround that I use is d-i from current daily snapshots found mid https://www.debian.org/devel/debian-installer/ The 3 november version has a 3.16-3 kernel Groeten Geert Stappers not subscribed to debian-boot m -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141103093142.gs1...@gpm.stappers.nl
d-i anna: no packages matching running kernel 3.16-2-amd64 in archive
Hi, background information: * debian-installer from 2014-10-02 * had a succesfull install on 2014-10-24 * it is now, 2014-11-02, broken Debian-installer shows on tty4: anna[1770]: WARNING **: no packages matching running kernel 3.16-2-amd64 in archive. Some research from me At http://ftp.nl.debian.org/debian/pool/main/l/linux/ there are e.g. scsi-modules-3.16-0.bpo.2-sparc64-di_3.16.3-2~bpo70+1_sparc.udeb scsi-modules-3.16-3-4kc-malta-di_3.16.5-1_mips.udeb so *-3.16-0* and *-3.16-3*, no *-3.16-2* ( -0 -3 available, no -2 ) What is broken? ( my config? d-i? ftp-archive? kernel uploads? ) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141102215203.gq1...@gpm.stappers.nl
Re: d-i anna: no packages matching running kernel 3.16-2-amd64 in archive
On Sun, Nov 02, 2014 at 11:12:59PM +0100, Julien Cristau wrote: On Sun, Nov 2, 2014 at 22:52:03 +0100, Geert Stappers wrote: Hi, background information: * debian-installer from 2014-10-02 Which image? It is a netboot. screenshot alpaca:/srv/tftp # wget http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/netboot.tar.gz --2014-11-02 21:37:55-- http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/netboot.tar.gz Herleiden van ftp.nl.debian.org (ftp.nl.debian.org)... 2001:67c:2564:a120::21, 130.89.149.21 Verbinding maken met ftp.nl.debian.org (ftp.nl.debian.org)|2001:67c:2564:a120::21|:80... verbonden. HTTP-verzoek is verzonden; wachten op antwoord... 200 OK Lengte: 18351734 (18M) [application/x-gzip] Wordt opgeslagen als: 'netboot.tar.gz.2' 100%[===] 18.351.734 2,43M/s in 7,5s 2014-11-02 21:38:02 (2,34 MB/s) - ''netboot.tar.gz.2'' opgeslagen [18351734/18351734] alpaca:/srv/tftp # md5sum netboot.tar.gz* deeed0e676d45cc5419e76c289d103ee netboot.tar.gz 69afa509a4233a678d129416bb89aabc netboot.tar.gz.1 69afa509a4233a678d129416bb89aabc netboot.tar.gz.2 alpaca:/srv/tftp # ls -l !$ ls -l netboot.tar.gz* -rw-r--r-- 1 root root 13735480 okt 13 11:27 netboot.tar.gz -rw-r--r-- 1 root root 18351734 okt 2 09:01 netboot.tar.gz.1 -rw-r--r-- 1 root root 18351734 okt 2 09:01 netboot.tar.gz.2 alpaca:/srv/tftp # /screenshot Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141103051245.gr1...@gpm.stappers.nl
Bug#763897: [i...@hellion.org.uk: Re: Inclusion of sun7i-a20-bananapi.dts]
- Forwarded message from Ian Campbell i...@hellion.org.uk - Date: Fri, 03 Oct 2014 23:05:14 +0100 From: Ian Campbell i...@hellion.org.uk To: Karsten Merker mer...@debian.org Cc: Ben Hutchings b...@decadent.org.uk, debian-kernel@lists.debian.org Subject: Re: Inclusion of sun7i-a20-bananapi.dts X-Mailer: Evolution 3.12.6-1 On Fri, 2014-10-03 at 17:03 +0200, Karsten Merker wrote: Ian, if you should find the time, could you perhaps give it a try? It built for me so I've pushed it. Ian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412373914.17796.53.ca...@hellion.org.uk - End forwarded message - Hope this helps -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141004025144.gr9...@gpm.stappers.nl
Bug#748574: 3.14.1 does not boot on Dell server
Op 2014-05-18 om 17:29 schreef Erwan David: When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. Did the PowerEdge R210 boot with previous Linux kernels? If yes, what is the last known good version? Please tell more about the installation of the 3.14.1 kernel. (Was it a fresh install? Was it a update? Was there enough disk space during the update?) Regards Geert Stappers PS : since I access it through an iDrac kvm which does not transmit arrow keys nor Ctrl keys, FWIW: I think that iDRAC kvm can transmit arrow keys and ConTRoL. I can't tell how, but it is very likely that such keys are supported. That those keys have special meaning on the admin machine, is something to cope / workaround with. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140518163018.gg5...@gpm.stappers.nl
Re: Join team
Op 2014-02-25 om 23:01 schreef Luiz Carlos: Hi, i am from brazil, i would like to be a debian developer, and a read about join a team before it is very important. So, i am contacting you because is my interest to work. I am a programmer. I know java, c, c#. Welcome! what can i do?? You allready made a good start by saying that you want to join. Next step is finding some task that you would like to do. It is for us hard to tell what an interresting problem is that will fit your skills. You might even want to develop new skills. Thanks a lot Waiting response. Thank you for your patience. And my apology for not providing a clear well defined starting point. Att, Luiz Carlos Maciel Franco Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301064940.gr1...@gpm.stappers.nl
updating debian-kernel-handbook
Hello, Happy new year! intro can=be skipped Some context because I spawning a new thread. Previous Subject: Re: linux-image-3.11-2-armmp_3.11.8-1_armhf not include AHCI_IMX Some how In-Reply-To: 1387036905.12172.17.ca...@deadeye.wl.decadent.org.uk E-mail with patch: https://lists.debian.org/debian-kernel/2013/12/msg00187.html /intro Op 2013-12-14 om 16:01 schreef Ben Hutchings: On Fri, 2013-12-13 at 10:22 +, Ian Campbell wrote: On Wed, 2013-12-11 at 15:05 +, Ben Hutchings wrote: Installing the package is a one-time command, so I think it belongs further up this section. Like this? [...] That looks good; applied. Where is it applied? And is it pushed to some public place? I'm asking because I would like to known more about how to updating the Debian kernel handbook. I have done a `debcheckout debian-kernel-handbook` on 2013-12-07. screenshot for=showing git repository URL $ git config --list core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=git://anonscm.debian.org/kernel-handbook/kernel-handbook.git remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.master.remote=origin branch.master.merge=refs/heads/master /screenshot Command `git pull` is responsed with 'Already up-to-date.' Latest commit in my debian-kernel-handbook-git-repository is 7afa50b4e571107bc99610fe1b823e757a7e6f86 which is from Sun Mar 31 02:11:27 2013 +0100 But I expect to have a more recent commit. Where should I look for updates of the Debian kernel handbook? Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Re: updating debian-kernel-handbook
Op 2014-01-04 om 14:18 schreef Ian Campbell: On Sat, 2014-01-04 at 13:37 +0100, Geert Stappers wrote: Op 2013-12-14 om 16:01 schreef Ben Hutchings: That looks good; applied. Where is it applied? [ ] Where should I look for updates of the Debian kernel handbook? I suspect Ben just forgot to git push. Or Ben had another good reason for not yet git-pushing it. Such as Alioth not being avialable. The date could match. Thanks for the response. I'll send another reminder if needed. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140104143248.gk1...@gpm.stappers.nl
Re: Linux Kernel Configuration Know-how
Op 2013-12-05 om 07:38 schreef Niew, Sh.: Hi, OK, newbie question here, i try to cut it for short to ask: Let's say i want to compile linux kernel for unsupported machine in debian, like mine REAL6410 board which is ARM S3C64XX machine flavor. I found difficult to config all the options especially the networking subsystem. I currently do it with grab the nearest possible config in debian armel ports, (although there is no similar supported machine flavor) and config the arch options by hand and just leave the other subsystem like the networking part or disable some options that i'm sure not necessary for this machine. So, what's the recommended way to doing this? Plz guide. During `make menuconfig` I would leave a generic subsystem as networking as found and only change direct hardware related stuff. Yes, that will need knowledge and time. Consider hiring a guide also known as a consultant ... Sh. Niew Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131205182705.gj24...@gpm.stappers.nl
Bug#728535: which size increment to expect
Op 2013-11-17 om 11:15 schreef Geert Stappers: Op 2013-11-17 om 10:55 schreef Geert Stappers: Edit on the kernel module source file, to add USB ID. Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger due the extra USB ID Is it correct to expect an increase in size of the .ko with a few bytes? Or is size increment in steps of 256 of 1024 bytes? Answer on my question: Yes, adding in .c source a line with VendorID and ProductID does increase the .ko module. In my case 120 bytes. So no increment in steps of 256 or 1024 bytes. $ filtered ls -l output -rw-r--r-- 1 root root 23144 Nov 15 20:55 /lib/modules/3.11-1-amd64/kernel/drivers/media/usb/gspca/gspca_sunplus.ko -rw-r--r-- 1 stappers stappers 23264 Nov 17 14:40 /home/stappers/src/linux/linux-3.11.5-goed/debian/linux-image-3.11-1-amd64/lib/modules/3.11-1-amd64/kernel/drivers/media/usb/gspca/gspca_sunplus.ko Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131120205821.gx24...@gpm.stappers.nl
Bug#730065: document new_id interface
Package: debian-kernel-handbook Version: 1.0.15 Severity: wishlist Op 2013-11-17 om 12:28 schreef Bastian Blank: snip/ Also you want to use new_id interface[1] if possible. Bastian [1]: /sys/class/usb/drivers/*/new_id http://www.ha19.no/usb/ Adding that URL to the kernel-handbook would be an improvement. Now filed as a separate bugreport. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131120210353.gy24...@gpm.stappers.nl
Bug#728535: so far
Summary: help is welcome After a apt-get source linux cd linux-VERSION fakeroot debian/rules binary there is linux-image-VERSION.deb that can be install. Succesfull rebooted with that new kernel. Edit on the kernel module source file, to add USB ID. Now is wanted the fastest way to get a .ko with the extra USB ID. Attempt 1: Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger due the extra USB ID Attempt 2: Executed `make -j 3` Failed with error about missing the .config file Attempt 3 4: screenshot HOSTCC arch/x86/tools/relocs_32.o HOSTCC arch/x86/tools/relocs_64.o HOSTCC arch/x86/tools/relocs_common.o HOSTLD arch/x86/tools/relocs Using /home/stappers/src/linux/linux-3.11.5 as source for kernel /home/stappers/src/linux/linux-3.11.5 is not clean, please run 'make mrproper' in the '/home/stappers/src/linux/linux-3.11.5' directory. make[5]: *** [prepare3] Error 1 make[4]: *** [sub-make] Error 2 make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/stappers/src/linux/linux-3.11.5/debian/build/build_amd64_none_amd64' make[2]: *** [debian/stamps/build_amd64_none_amd64_plain] Error 2 make[2]: Leaving directory `/home/stappers/src/linux/linux-3.11.5' make[1]: *** [binary-arch_amd64_none_amd64_real] Error 2 make[1]: Leaving directory `/home/stappers/src/linux/linux-3.11.5' make: *** [binary-arch] Error 2 $ make mrproper CLEAN scripts/basic CLEAN scripts/kconfig CLEAN /home/stappers/src/linux/linux-3.11.5/debian/ CLEAN include/config include/generated arch/x86/include/generated $ fakeroot debian/rules binary-arch /usr/bin/fakeroot: line 178: debian/rules: No such file or directory $ /screenshot In other words: I'm back at square 1 :-/ Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131117095529.gv16...@gpm.stappers.nl
Bug#728535: which size increment to expect
Op 2013-11-17 om 10:55 schreef Geert Stappers: Edit on the kernel module source file, to add USB ID. Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger due the extra USB ID Is it correct to expect an increase in size of the .ko with a few bytes? Or is size increment in steps of 256 of 1024 bytes? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131117101513.gn24...@gpm.stappers.nl
Bug#728535: debian-kernel-handbook: document rebuilding a single kernel module
Package: debian-kernel-handbook Version: 1.0.15 Severity: wishlist Hello, The Debian kernel handbook has a chapter Common kernel-related tasks. Which has paragraphs as Rebuilding official Debian kernel packages, Building a custom kernel from Debian kernel source and Building out-of-tree kernel modules. But I miss a paragraph how to (re)build a single kernel module. Typical use case is having a USB device with a supported chip set, but USB-IDs not enumerated in the driver. In other words: How to do simple driver development as adding USB-IDs? Please document which steps should be taken to have only a single module compiled that can be insmod to the Debian kernel. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#728535: debian-kernel-handbook: document rebuilding a single kernel module
Op 2013-11-02 om 18:09 schreef Geert Stappers: But I miss a paragraph how to (re)build a single kernel module. Typical use case is having a USB device with a supported chip set, but USB-IDs not enumerated in the driver. In other words: How to do simple driver development as adding USB-IDs? Please document which steps should be taken to have only a single module compiled that can be insmod to the Debian kernel. Say I have a new webcam and want to build sunplus because I have added an extra USB-ID to drivers/media/usb/gspca/sunplus.c What options should I provide to `make`? Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131102174950.gj24...@gpm.stappers.nl
Bug#616689: more encounters ... gone :-)
Op 2013-05-15 om 22:14 schreef Geert Stappers: I'm gonna play with the error on the virtual machine. That was a nice exprience. Learned a lot. And the best thing is that I got it working. With a _completer apt archive_ is works fine. Yes, I could reproduce this bug due an incomplete apt archive. So not a initramfs-tools error, but an user error ... Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130516205002.gm12...@gpm.stappers.nl
Bug#616689: more encounters ...
Hello, My first encounter with this bug was last weekend (yes, a week after the release of Wheezy) on real hardware. And tonight I got it reproduced twice on VirtualBox VM. The workaround on the real hardware was avoiding LVM. I'm gonna play with the error on the virtual machine. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#706499: marked as done (Ethernet with Realtek R8169 only working with IPV6)
Op 2013-05-06 om 12:51 schreef Debian Bug Tracking System: the Debian Bug report #706499, regarding Ethernet with Realtek R8169 only working with IPV6 to be marked as done. snip/ From: Ben Hutchings b...@decadent.org.uk To: 706499-d...@bugs.debian.org Subject: Re: Bug#706499: Ethernet with Realtek R8169 only working with IPV6 Message-ID: 1367844634.4131.62.ca...@deadeye.wl.decadent.org.uk X-Mailer: Evolution 3.4.4-2 On Mon, 2013-05-06 at 09:56 +0200, Karsten Malcher wrote: [...] Afterwards the R8169 card works without problem. Good. [...] The problem has come like a ghost and gone like a ghost. It's hard to say for me but - the bug can be closed. This problem is really not reproducible. Now i must master my routing problem - maybe the problem will come up again ... I think this was likely some kind of configuration problem all along (though I don't know what). FWIW: The 192.168.1.3 and 192.168.1.4 are on the _SAME_ IP-network. That is odd for one single computer with two interfaces. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#703195: Cant get BCM43228 to work
On Sat, Mar 16, 2013 at 06:50:24PM +0100, Mathieu Malaterre wrote: Is there a way for me to track what could possibly be going on wrong with setup of wireless driver ? do lspci -s 03:00.0 -n and check that VendorID and ProductID matches what you found with modinfo alias: pci:v14E4d0576sv*sd*bc*sc*i* alias: pci:v14E4d4727sv*sd*bc*sc*i* alias: pci:v14E4d4353sv*sd*bc*sc*i* alias: pci:v14E4d4357sv*sd*bc*sc*i* Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130316180601.gt2...@gpm.stappers.nl
Bug#550534: long lines
long, non-wrapped, lines of posting from Bart-Jan Vrielink [598216.014608] iwl4965 :03:00.0: Microcode SW error detected. Restarting 0x8200. [598216.014612] iwl4965 :03:00.0: Loaded firmware version: 228.61.2.24 [598216.014628] iwl4965 :03:00.0: Start IWL Error Log Dump: [598216.014630] iwl4965 :03:00.0: Status: 0x000213E4, count: 5 [598216.014777] iwl4965 :03:00.0: Desc Time data1 data2 line [598216.014780] iwl4965 :03:00.0: FH_ERROR (0x000C) 3967722153 0x0008 0x0313 208 [598216.014783] iwl4965 :03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [598216.014786] iwl4965 :03:00.0: 0x0046C 0x05CB2 0x004C2 0x006DE 0x018B8 0x285001C [598216.014788] iwl4965 :03:00.0: FH register values: [598216.014802] iwl4965 :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X09373900 [598216.014816] iwl4965 :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00646f00 [598216.014830] iwl4965 :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0068 [598216.014843] iwl4965 :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819000 [598216.014857] iwl4965 :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X003c [598216.014870] iwl4965 :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0313 [598216.014884] iwl4965 :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [598216.014897] iwl4965 :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0002 [598216.014911] iwl4965 :03:00.0: FH_TSSR_TX_ERROR_REG: 0X [598216.015157] ieee80211 phy1: Hardware restart was requested HTH -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121105065055.ga22...@gpm.stappers.nl
Bug#685864: linux-image-3.2.0-3-amd64: Commande halt or halt -p and shutdown = reboot system. Cm :gigabyte z77x-ud5h
[Please reply to all, including the address 685...@bugs.debian.org] vrom: novice gavo...@panthere-noire.com Date: Tue, 28 Aug 2012 03:06:46 +0200 1. Uninstall the nvidia driver (or somehow stop it from loading) yes . I also tested modprobe -r nvidia `modprobe -r nvidia` removes the nvidia kernel module from memory. It is the undo of `modprobe nvidia`, which loads it in memory. BUT: modprode is MORE then just load and unload, there is also programcode from the kernel module executed. During load there is initialization done. The request is uninstall the nvidia module. To remove it from disk. With the effect to stop it from loading and executing init code. 2. Reboot reboot . That reboot is to clear initialiastion the nvidia driver could have done. 3. Run 'shutdown' Ben. use: shutdown -h nows result reboot. That is the reason for this ticket :-/ thank you for your patience This E-mail is / was about telling that uninstall is more then `modprobe -r modulename` Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120828195929.gw22...@gpm.stappers.nl
Bug#685864: linux-image-3.2.0-3-amd64: Commande halt or halt -p and shutdown = reboot system. Cm :gigabyte z77x-ud5h
Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode]) 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4) (prog-if 00 [Normal decode]) 00:1c.5 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev c4) (prog-if 01 [Subtractive decode]) 00:1c.6 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 [8086:1e1c] (rev c4) (prog-if 00 [Normal decode]) 00:1c.7 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 [8086:1e1e] (rev c4) (prog-if 00 [Normal decode]) 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI]) 00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04) (prog-if 01 [AHCI 1.0]) 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Giga-byte Technology Device [1458:5001] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin C routed to IRQ 18 Region 0: Memory at f653a000 (64-bit, non-prefetchable) [size=256] Region 4: I/O ports at f020 [size=32] 02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 11) (prog-if 01 [AHCI 1.0]) 03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8892] (rev 30) (prog-if 01 [Subtractive decode]) 04:01.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev c0) (prog-if 10 [OHCI]) 05:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet [1969:1083] (rev c0) 06:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 11) (prog-if 01 [AHCI 1.0]) 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Kernel driver in use: nvidia As far as I known is there nouveau the open source driver voor Nvidia. 07:00.1 Audio device [0403]: NVIDIA Corporation GF104 High Definition Audio Controller [10de:0beb] (rev a1) ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 2109:0810 According my web search an USB 3 device Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 2109:0810 Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 003 Device 004: ID 2109:0810 Bus 003 Device 005: ID 2109:0810 Bus 003 Device 006: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 003 Device 007: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub Bus 003 Device 008: ID 046d:c068 Logitech, Inc. G500 Laser Mouse Bus 003 Device 009: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet] Bus 003 Device 010: ID 046d:c226 Logitech, Inc. G15 Refresh Keyboard Bus 003 Device 011: ID 046d:c227 Logitech, Inc. G15 Refresh Keyboard Bus 003 Device 012: ID 03f0:6104 Hewlett-Packard DeskJet 5650c Bus 003 Device 013: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB My two cents Cheers Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120825171228.gr22...@gpm.stappers.nl
Bug#684516: bluetooth.ko unlikely in initrd
On Sat, Aug 25, 2012 at 09:07:30PM +0200, asronche...@libero.it wrote: Da: stapp...@stappers.nl Data: 25-ago-2012 19.59 Remove the bluetooth module from /lib/modules and the initial ramdisk, so that the computer hasn't any more the module. btw, what do you mean with 'ramdisk' ? is that 'initramfs' ? Yes. if i remove that file, will the system be still bootable? Do NOT remove files like /boot/initrd.img-* After removing bluetooth.ko from /lib/module/ update the Init R.D. with the command update-initramfs (sorry, i still am not an expert about the linux boot stuff) My expertise level also can use some more learning. Where I/we want so that the computer hasn't any more the module. I told Remove the bluetooth module from /lib/modules and should have left out and the initial ramdisk, on second thought it is unlikely that the bluetooth module is in initrd. In the initial ramdisk are modules which are needed to mount root f.s. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#684516: bluetooth loaded for UNKNOWN reason
On Sun, Aug 19, 2012 at 07:41:50PM +0200, asronche...@libero.it wrote: Da: Johantan Niederman jrnie...@gmail.com Data: 19-ago-2012 19.27 (Though I have no idea whether they trigger autoloading of the bluetooth module or if it's udev's responsibility.) Thanks for the advice. I checked via aptitude but i have already removed the bluez package. Ben Hutchings @ Sun, 19 Aug 2012 17:56:35 +0100 Not a bug; please stop pursuing this irrelevant detail. How can you think that it's not a bug? The challenge is to be constructive. 1) I dont have bluetooth devices attached to this notebook. 2) I followed your advice and i removed the bluetooth package 3) today i had a kernel panic and the error message appeared on the the screen showed a list of loaded modulse. The first module of that list was indeed the bluetooth module. My advice is to research what causes the bluetooth module be loaded. I would start with checking udev rules. Thing I would NOT do, is yelling: Nobody listens to me! Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120819195144.gk22...@gpm.stappers.nl
Bug#549681: bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sun, Jul 01, 2012 at 03:13:57PM -0400, Milan Kupcevic wrote: +if grep -q CONFIG_RD_XZ=y /boot/config-$release ; then + is_xz_supported=Yes +fi Have a look at this test statement +if test $is_xz_supported; then + XZ=xz --check=crc32 -8 +else + XZ=false +fi And have a look at these test statements: +test -z $verbose || echo === Creating compressed initrd image - if test `od -A n -c -N 2 $initrd` = 037 213; then + if test `xxd -p -l2 $initrd` = 1f8b; then + test -z $verbose || echo === $initrd is already gzip compressed + if test -n $is_xz_supported test $arch != prep; then + test -z $verbose || echo === recompressing to xz + elif test `xxd -p -l6 $initrd` = fd377a585a00; then + test -z $verbose || echo === $initrd is already xz compressed + test -z $verbose || echo === assuming $initrd was not compressed Notices that those tests are either test string = otherstring or are test --option $variable They here again a test --option $variable and a strange looking single test $variable @@ -317,7 +334,11 @@ WRAPPER=$objdir/wrapper vmlinuz=$work/vmlinuz.$arch if test -n $initrd; then -INITRD=-i $work/initrd.gz +if test $is_xz_supported; then + INITRD=-i $work/initrd.xz +else + INITRD=-i $work/initrd.gz +fi fi $WRAPPER -c -o $vmlinuz -p $arch $INITRD -D $objdir -W $work $kernel else Please use the more readable test -n $is_xz_supported Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Re: memtest kernel option
On Sun, Dec 04, 2011 at 01:27:57PM +0100, Thierry GRAUSS wrote: Hello, I have a laptop computer with half of the RAM soldered on the motherboard. This soldered RAM has a huge amount of bad RAM (too many errors to be able to use the badram option). Fortunatly, there is a Linux kernel option (available in the mainstream kernel, no need to patch anything) which can run tests like memtest86 when Linux is booting so that it will automatically exclude these parts of the memory from being used. This option, when enabled in the kernel, can be enabled and disabled with a kernel boot argument (option memtest in grub). Is it possible to include this option in the default kernel, even if disabled by default, but having the option enabled in the installation CD (at least to be able to install the system without trouble)? I managed to install Debian Squeeze, but it was really a pain with this bad RAM. Performance benchmarks show also no impact at all from the memtest option. This option is not only useful for laptop computer like mine, but also for the new plug servers based on ARM processors. Often they have only soldered RAM chip. As reliability is even more important for a server than for a laptop computer, I think that the activation of this option whould help a lot to prevent to trash these little computers when/if they have bad RAM modules. - Origin of the module, before it was included in the mainstream branch of the kernel : http://rick.vanrein.org/linux/badram/ - Benchmark of the memtest module : http://rick.vanrein.org/linux/badram/results.html - Example of use and explanation of the usefulness of the option when running a server : http://onlyjob.blogspot.com/2011/01/memtest-explained-linux-kernel.html Thank you in advance From http://lists.debian.org/debian-kernel/2011/12/msg00333.html do I understand that MEMTEST is now default in new kernels. Best regards Thierry GRAUSS Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111212214854.gg16...@gpm.stappers.nl
Re: Kernel Summit
On Thu, Oct 20, 2011 at 02:08:23AM +0100, Ben Hutchings wrote: I'm going to the Kernel Summit on 24-25 October (with travel expenses paid by my employer, Solarflare). The Summit is mostly meant for discussion of the development process, architectural and kernel-wide issues, unlike more specific conferences. The draft agenda is at: http://ksummit2011.kernel.org/agenda Are there any issues people would like me to raise there? Compliment, endorse and/or hug any hardware vendor that is at the Linux kernel summit. They are the runners-up that do understand there is a market for hardware that has good Linux support. They have seen that the dominant days of Microsoft are over. They are smart enough to calculate that getting brided with a Windows 8 logo will be paid with a high price. Regards Geert Stappers Worried about the possible boot restrictions on so called Windows 8 hardware -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Re: system hangs during shutdown...
On Thu, Jul 21, 2011 at 04:20:34PM -0600, Bruce Sass wrote: On July 21, 2011 05:02:38 AM Ben Hutchings wrote: [...] This is not a bug. NFS clients are supposed to keep on trying to reach the server, by default. You should have unmounted the directory from the NFS client(s) before shutting down the server. Sounds like a desirable behaviour when the system is coming up, but having the client hang when *going down* because a server disappeared doesn't seem right. The client is still the client with the expected behaviour when it is going down. You should have unmounted the directory from the NFS client(s) before shutting down the server. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110722062608.gf2...@gpm.stappers.nl
Bug#627837: [b...@decadent.org.uk: Uploading linux-2.6 (2.6.39-2)]
This bugreport, #627837, is allready tagged 'pending'. The idea behind this forward is to add some further information. I think it helps, at least Hopes this helps Geert Stappers - Forwarded message from Ben Hutchings b...@decadent.org.uk - Date: Sun, 05 Jun 2011 05:01:48 +0100 From: Ben Hutchings b...@decadent.org.uk To: Debian kernel maintainers debian-kernel@lists.debian.org Cc: debian-rele...@lists.debian.org Subject: Uploading linux-2.6 (2.6.39-2) X-Mailer: Evolution 2.32.3 I intend to upload linux-2.6 to unstable early this week. This will include stable update 2.6.39.1 and restoration of aufs support for use in Debian Live. Stable update 2.6.39.1 includes an ABI change, so we will probably have to change the binary package names. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. - End forwarded message - -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110606054809.ge1...@gpm.stappers.nl
Bug#627837: linux-2.6: Aufs apparently silently dropped, breaking debian-live
On Sun, May 29, 2011 at 10:16:40PM +0200, Daniel Baumann wrote: On 05/29/2011 10:04 PM, Daniel Baumann wrote: On 05/29/2011 09:53 PM, Julien Cristau wrote: Maybe it was ready in your mind, but it wasn't in debian-kernel svn or mailing list (and as far as I can tell the kernel maintainers even checked aufs git before the .39 upload, and didn't find any recent changes there). So yeah, that's exactly the problem. no; aufs.git was up2date. in time. way before. oh.. and before you ask.. 'way before' means 'at least 2011-04-18, but possibly even earlier' (yes, that really is a month before .39 was released). And what is the URL for aufs.git? And where is that information shared before? And frankly, I don't have time to check the stated facts. What I do like to see, is that this bug report is about solving an issue, NOT about who should have done what and when. So far my attempt to stop the fight. Now going forward to a solution. The previous provide URLs got some how line wrapped. In this resend they should without the line break. http://vcs.progress-linux.org/?p=packages/linux-2.6.git;a=commitdiff;h=26a2fd380e516f1df527c0357334eb5e10cdccb3 http://vcs.progress-linux.org/?p=packages/linux-2.6.git;a=commitdiff;h=973422c91686a621ecd81db1813ed3e77a837b2c HTH Stappers signature.asc Description: Digital signature
Bug#625507: acer-wmi developer says the module doesn't do anything on the aspire one
Did the driver work on this hardware in earlier kernel versions? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110504131549.gb1...@gpm.stappers.nl
Bug#619827: linux-source-2.6.38: [linux-dvb] cx88-blackbird broken (since 2.6.37)
On Sat, Apr 02, 2011 at 08:01:15PM +0200, Andreas Huber wrote: please review this simple fix! Please let us know when a complete fix has been accepted upstream. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Re: Dropping 686 non-pae kernel
On Sun, Mar 13, 2011 at 09:18:31AM +0100, Bastian Blank wrote: On Sun, Mar 13, 2011 at 03:57:56AM +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:34 +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:23 +0100, Bastian Blank wrote: [...] There are several possibilities to do this: * Change name of meta-package: - Breaks nothing - Needs manual intervention by anyone using it * Don't change the name: - Breaks some systems - No manual intervention by the rest I'm wavering on this. I don't like the idea of simply renaming '686-bigmem' to '686', given there are a fair number of 686-class systems without PAE, and I don't think users with a Pentium M are going to expect that '486' is the right choice. Please read again what I wrote. Please provide 'where' and 'when'. The distinctions between these two flavours will be: 1. One processor (min 486) with 386 page tables (currently '486') 2. One or more processors with PAE page tables (currently '686-bigmem') Will not hold forever and you need to integrate the other architectures into it. How about naming them 'up' and 'smp-pae'? It'll be a pain to transition the metapackages, but then we should never have to go through this again when raising the minimum processor requirement. No, this will not help. See above. Bastian -- There are certain things men must do to remain men. -- Kirk, The Ultimate Computer, stardate 4929.4 A good thing to remain human, is willing to communicate with humans. Take time to explain why something is a good thing. Take even more time to explain why something is a bad thing. If the other side doesn't get the message, both sides should allow each other the freedom to do their thing. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#583689: USB and RTC for loongson-2f
Hello, Attached is a patch against Debian Kernel SVN repository. It makes USB keyboard possible and setting the RTC on the loongson-2f Groeten Geert Stappers Index: debian/config/mipsel/config.loongson-2f === --- debian/config/mipsel/config.loongson-2f (revision 16146) +++ debian/config/mipsel/config.loongson-2f (working copy) @@ -14,6 +14,9 @@ ## CONFIG_LEMOTE_MACH2F=y CONFIG_CS5536_MFGPT=y +CONFIG_LOONGSON_UART_BASE=y +CONFIG_LOONGSON_MC146818=y +CONFIG_RWSEM_GENERIC_SPINLOCK=y ## ## file: arch/mips/kernel/cpufreq/Kconfig @@ -71,6 +74,21 @@ CONFIG_USB=m ## +## file: drivers/usb/host/Kconfig +## +CONFIG_USB_EHCI_HCD=m +# CONFIG_USB_EHCI_ROOT_HUB_TT is not set +CONFIG_USB_ISP116X_HCD=m +CONFIG_USB_OHCI_HCD=m +CONFIG_USB_UHCI_HCD=m +CONFIG_USB_SL811_HCD=m + +## +## file: drivers/usb/mon/Kconfig +## +CONFIG_USB_MON=y + +## ## file: drivers/video/Kconfig ## CONFIG_VIDEO_OUTPUT_CONTROL=y signature.asc Description: Digital signature
Re: linux-2.6_2.6.35~rc6-1~experimental.1_multi.changes is NEW
Op 20100724 om 17:03 schreef Archive Administrator: linux-source-2.6.35_2.6.35~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.35_2.6.35~rc6-1~experimental.1_all.deb (new) linux-support-2.6.35-rc6_2.6.35~rc6-1~experimental.1_all.deb optional devel AFAIK is now 2.6.35-rc6 stuck in the NEW queue. Has someone an URL to linux-source-2.6.35_2.6.35~rc6-1~experimental.1_all.deb to wget it all ready? Groeten Geert Stappers -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100725122359.gr11...@gpm.stappers.nl
Bug#583689: Not yet support for loongson-2f
found 583689 2.6.34-1~experimental.2 thanks Hello Debian Kernel people, Version 2.6.34-1~experimental.2 says [ 0.764000] /build/buildd-linux-2.6_2.6.34-1~exprimental.2-mipsel-ZShPn4/linux-2.6-2.6.34/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable open rtc device (rtc0) And also [ 0.912000] ata1.00: ATA-8: WDC WD1600BEVT-22ZCT0, 11.01A11, max UDMA/133 [ 0.916000] ata1.00: 312581808 sectors, mult 16: LBA48 [ 0.932000] ata1.00: configured for UDMA/100 [ 0.936000] scsi 0:0:0:0 Direct-Access ATA WDC WD1600BEVT-2 11.0 PQ: 0 ANSI: 5 [ 0.94] VFS: Cannot open root device hda1 or unknown-block(0,0) So it is too early to close bugreport 583689 Groeten Geert Stappers signature.asc Description: Digital signature
Bug#583689: FYI: 2.6.35-rc5-loongson-2f does see disk
For you information, on version 2.6.35-rc5-loongson-2f there is still the RTC error, but the harddisk is seen. (version 2.6.34 doesn't see a disk) dmesg output [0.732000] /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.736000] Initalizing network drop monitor service [0.916000] ata1.00: ATA-8: WDC WD1600BEVT-22ZCT0, 11.01A11, max UDMA/133 [0.92] ata1.00: 312581808 sectors, multi 16: LBA48 [0.932000] ata1.00: configured for UDMA/100 [0.936000] scsi 0:0:0:0: Direct-Access ATA WDC WD1600 BEVT-2 11.0 PQ: 0 ANSI: 5 [0.94] ata2: port disabled. ignoring. [0.94] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks : (160 GB/149 GiB) [0.944000] sd 0:0:0:0: [sda] Write Protect is off [0.948000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [0.948000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [0.952000] sda: sda1 sda2 sda3 sda4 [0.968000] sd 0:0:0:0: [sda] Attached SCSI disk [0.976000] EXT3-fs: barriers not enabled [0.984000] kjournald starting. Commit interval 5 seconds [0.988000] EXT3-fs (sda1): mounted filesystem with ordered data mode [0.992000] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. hth gst -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723181040.gn11...@gpm.stappers.nl
Bug#583689: loongson-2f is missing USB Host Controller
Hello Debian Kernel People, On both 2.6.34 and 2.6.35 for the MIPSEL flavour loonson-2f is a USB Host controller missing. Missing as is in Not compiled in the kernel, not even as a module. This is what went during build in the .config file: | # | # USB Host Controller Drivers | # | CONFIG_USB_C67X00_HCD=m | CONFIG_USB_XHCI_HCD=m | # CONFIG_USB_XHCI_HCD_DEBUGGING is not set | # CONFIG_USB_EHCI_HCD is not set | # CONFIG_USB_OXU210HP_HCD is not set | CONFIG_USB_ISP116X_HCD=m | # CONFIG_USB_ISP1760_HCD is not set | # CONFIG_USB_ISP1362_HCD is not set | # CONFIG_USB_OHCI_HCD is not set | # CONFIG_USB_UHCI_HCD is not set | CONFIG_USB_U132_HCD=m | # CONFIG_USB_SL811_HCD is not set | CONFIG_USB_R8A66597_HCD=m | CONFIG_USB_WHCI_HCD=m | CONFIG_USB_HWA_HCD=m This is what aba requested in http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=config.2.6.34-1~experimental.1;att=3;bug=583689 | # | # USB Host Controller Drivers | # | # CONFIG_USB_C67X00_HCD is not set | # CONFIG_USB_XHCI_HCD is not set | CONFIG_USB_EHCI_HCD=y | CONFIG_USB_EHCI_ROOT_HUB_TT=y | # CONFIG_USB_EHCI_TT_NEWSCHED is not set | # CONFIG_USB_OXU210HP_HCD is not set | # CONFIG_USB_ISP116X_HCD is not set | # CONFIG_USB_ISP1760_HCD is not set | # CONFIG_USB_ISP1362_HCD is not set | CONFIG_USB_OHCI_HCD=y | # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set | # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set | CONFIG_USB_OHCI_LITTLE_ENDIAN=y | CONFIG_USB_UHCI_HCD=m | # CONFIG_USB_SL811_HCD is not set | # CONFIG_USB_R8A66597_HCD is not set | CONFIG_USB_WHCI_HCD=m | CONFIG_USB_HWA_HCD=m | # CONFIG_USB_GADGET_MUSB_HDRC is not set It is at least 'CONFIG_USB_OHCI_HCD=y' that should come back in the .config file. Groeten Geert Stappers -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723194801.go11...@gpm.stappers.nl
Bug#583689: Not yet support for loongson-2f
# Op 20100723 om 20:06 schreef Martin Michlmayr: # * Bastian Blank wa...@debian.org [2010-07-23 20:24]: # [ 0.94] VFS: Cannot open root device hda1 or unknown-block(0,0) # # You have to supply a correct initramfs. # # No, it should be built in (mips/mipsel don't use initramfs). # found 583689 2.6.34-1~experimental.2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723195601.gp11...@gpm.stappers.nl
2.6.35-rc5 build on MIPS misses asm/agp.h
Hello Debian kernel people, This E-mail is to report a kernel build failure that I encountered. On a MIPSEL system I do get this output | CC [M] drivers/gpu/drm/ttm/ttm_lock.o | CC [M] drivers/gpu/drm/ttm/ttm_execbuf_util.o | CC [M] drivers/gpu/drm/ttm/ttm_page_alloc.o | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/gpu/drm/ttm/ttm_page_alloc.c:43:21: error: asm/agp.h: No such file or directory | make[9]: *** [drivers/gpu/drm/ttm/ttm_page_alloc.o] Error 1 | make[8]: *** [drivers/gpu/drm/ttm] Error 2 | make[7]: *** [drivers/gpu/drm] Error 2 | make[6]: *** [drivers/gpu] Error 2 | make[5]: *** [drivers] Error 2 | make[4]: *** [sub-make] Error 2 | make[3]: *** [all] Error 2 | make[3]: Leaving directory | `/usr/src/Linux/debian-svn/debian/build/build_mipsel_none_4kc-malta' | make[2]: *** [debian/stamps/build_mipsel_none_4kc-malta_plain] Error 2 | make[2]: Leaving directory `/usr/src/Linux/debian-svn' | make[1]: *** [build_mipsel_none_4kc-malta_real] Error 2 | make[1]: Leaving directory `/usr/src/Linux/debian-svn' | make: *** [debian/stamps/build-base] Error 2 What I did to get there comes mostly from the kernel-handbook. This is what I exactly ( # comment added afterwars ) did: | svn co svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6 debian-svn | cd debian-svn | svn log # checked that work for http://bugs.debian.org/583689 is included | cd .. | apt-get source -d linux-2.6 | cd debian-svn/ | debian/rules orig # failed, it asked for 2.6.32~rc5 | cd .. | wget http://ftp.debian.org/pool/main/l/linux-2.6/linux-2.6_2.6.35~rc5.orig.tar.gz | cd - | debian/rules orig | debian/rules debian/control | fakeroot debian/rules binary Information about the build host | stapp...@fulong:/usr/src/Linux/debian-svn | $ pwd | /usr/src/Linux/debian-svn | stapp...@fulong:/usr/src/Linux/debian-svn | $ uname -a | Linux fulong 2.6.27.7 #1 Fri Mar 6 15:20:56 CST 2009 mips64 GNU/Linux | stapp...@fulong:/usr/src/Linux/debian-svn | $ uname -m | mips64 | stapp...@fulong:/usr/src/Linux/debian-svn | $ dpkg-architecture | DEB_BUILD_ARCH=mipsel | DEB_BUILD_ARCH_OS=linux | DEB_BUILD_ARCH_CPU=mipsel | DEB_BUILD_GNU_CPU=mipsel | DEB_BUILD_GNU_SYSTEM=linux-gnu | DEB_BUILD_GNU_TYPE=mipsel-linux-gnu | DEB_HOST_ARCH=mipsel | DEB_HOST_ARCH_OS=linux | DEB_HOST_ARCH_CPU=mipsel | DEB_HOST_GNU_CPU=mipsel | DEB_HOST_GNU_SYSTEM=linux-gnu | DEB_HOST_GNU_TYPE=mipsel-linux-gnu | stapp...@fulong:/usr/src/Linux/debian-svn | $ svn info | Path: . | URL: svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6 | Repository Root: svn://svn.debian.org/svn/kernel | Repository UUID: 510b9475-24dd-0310-9b6c-e0eefe99d49f | Revision: 15990 | Node Kind: directory | Schedule: normal | Last Changed Author: benh | Last Changed Rev: 15985 | Last Changed Date: 2010-07-14 07:26:01 +0800 (Wed, 14 Jul 2010) | | stapp...@fulong:/usr/src/Linux/debian-svn | $ svn update | At revision 15992. | stapp...@fulong:/usr/src/Linux/debian-svn | $ What can I do to get beyond | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/gpu/drm/ttm/ttm_page_alloc.c:43:21: error: asm/agp.h: No such file or directory ??? Groeten Geert Stappers signature.asc Description: Digital signature
Re: 2.6.35-rc5 build on MIPS misses asm/agp.h
Op 20100718 om 13:10 schreef Ben Hutchings: On Sun, 2010-07-18 at 10:43 +0200, Geert Stappers wrote: This E-mail is to report a kernel build failure that I encountered. On a MIPSEL system I do get this output | CC [M] drivers/gpu/drm/ttm/ttm_lock.o | CC [M] drivers/gpu/drm/ttm/ttm_execbuf_util.o | CC [M] drivers/gpu/drm/ttm/ttm_page_alloc.o | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/gpu/drm/ttm/ttm_page_alloc.c:43:21: error: asm/agp.h: No such file or directory Try adding this patch: --- a/drivers/gpu/drm/ttm/ttm_page_alloc.c +++ b/drivers/gpu/drm/ttm/ttm_page_alloc.c @@ -40,7 +40,9 @@ #include linux/slab.h #include asm/atomic.h +#ifdef TTM_HAS_AGP #include asm/agp.h +#endif #include ttm/ttm_bo_driver.h #include ttm/ttm_page_alloc.h --- END --- Yes! That got me further \o/ Output: | CALL /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/scripts/checksyscalls.sh | CHK include/generated/compile.h | CC [M] drivers/gpu/drm/ttm/ttm_page_alloc.o | LD [M] drivers/gpu/drm/ttm/ttm.o | LD drivers/gpu/drm/via/built-in.o | CC [M] drivers/gpu/drm/via/via_irq.o [and more] Ben. Thank you! Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100718195614.gc11...@gpm.stappers.nl
2.6.35-rc5 build on MIPSEL macro get_current passed 2 arguments, but takes just 0
Hello Debian kernel people, This E-mail is to report a kernel build failure that I encountered. On a MIPSEL system I do get this output | CC [M] drivers/power/power_supply_core.o | CC [M] drivers/power/power_supply_sysfs.o | CC [M] drivers/power/power_supply_leds.o | LD [M] drivers/power/power_supply.o | CC [M] drivers/power/ds2782_battery.o | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c:216:48: error: macro get_current passed 2 arguments, but takes just 0 | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c: | In function 'ds278x_get_status': | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c:216: warning: assignment makes integer from pointer without a cast | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c:257:50: error: macro get_current passed 2 arguments, but takes just 0 | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c: | In function 'ds278x_battery_get_property': | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c:257: warning: assignment makes integer from pointer without a cast | make[7]: *** [drivers/power/ds2782_battery.o] Error 1 | make[6]: *** [drivers/power] Error 2 | make[5]: *** [drivers] Error 2 | make[4]: *** [sub-make] Error 2 | make[3]: *** [all] Error 2 | make[3]: Leaving directory | `/usr/src/Linux/debian-svn/debian/build/build_mipsel_none_4kc-malta' | make[2]: *** [debian/stamps/build_mipsel_none_4kc-malta_plain] Error 2 What I did to get there comes mostly from the kernel-handbook. This is what I exactly ( # comment added afterwars ) did: | svn co svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6 debian-svn | cd debian-svn | svn log # checked that work for http://bugs.debian.org/583689 is included | cd .. | apt-get source -d linux-2.6 | cd debian-svn/ | debian/rules orig # failed, it asked for 2.6.32~rc5 | cd .. | wget http://ftp.debian.org/pool/main/l/linux-2.6/linux-2.6_2.6.35~rc5.orig.tar.gz | cd - | debian/rules orig | debian/rules debian/control | fakeroot debian/rules binary Information about the build host | stapp...@fulong:/usr/src/Linux/debian-svn | $ pwd | /usr/src/Linux/debian-svn | stapp...@fulong:/usr/src/Linux/debian-svn | $ uname -a | Linux fulong 2.6.27.7 #1 Fri Mar 6 15:20:56 CST 2009 mips64 GNU/Linux | stapp...@fulong:/usr/src/Linux/debian-svn | $ uname -m | mips64 | stapp...@fulong:/usr/src/Linux/debian-svn | $ dpkg-architecture | DEB_BUILD_ARCH=mipsel | DEB_BUILD_ARCH_OS=linux | DEB_BUILD_ARCH_CPU=mipsel | DEB_BUILD_GNU_CPU=mipsel | DEB_BUILD_GNU_SYSTEM=linux-gnu | DEB_BUILD_GNU_TYPE=mipsel-linux-gnu | DEB_HOST_ARCH=mipsel | DEB_HOST_ARCH_OS=linux | DEB_HOST_ARCH_CPU=mipsel | DEB_HOST_GNU_CPU=mipsel | DEB_HOST_GNU_SYSTEM=linux-gnu | DEB_HOST_GNU_TYPE=mipsel-linux-gnu | stapp...@fulong:/usr/src/Linux/debian-svn | $ svn info | Path: . | URL: svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6 | Repository Root: svn://svn.debian.org/svn/kernel | Repository UUID: 510b9475-24dd-0310-9b6c-e0eefe99d49f | Revision: 15990 | Node Kind: directory | Schedule: normal | Last Changed Author: benh | Last Changed Rev: 15985 | Last Changed Date: 2010-07-14 07:26:01 +0800 (Wed, 14 Jul 2010) | | stapp...@fulong:/usr/src/Linux/debian-svn | $ svn update | At revision 15992. | stapp...@fulong:/usr/src/Linux/debian-svn | $ What can I do to get beyond | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c:216:48: error: macro get_current passed 2 arguments, but takes just 0 | /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/power/ds2782_battery.c:257:50: error: macro get_current passed 2 arguments, but takes just 0 ??? Groeten Geert Stappers signature.asc Description: Digital signature
Bug#505184: linux-image-2.6.26-1-amd64: Wish: Build btusb.ko
Package: linux-image-2.6.26-1-amd64 Severity: wishlist Hello Kernel maintainers, Please inclue CONFIG_BT_HCIBTUSB=m in the dot config so that btusb.ko gets build. Thanks Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407759: Bug#394344: support all-generic-ide
Op 03-02-2007 om 09:49 schreef Jacob L. Anawalt: I consider lack of generic ide support a bug in the way Debian x86/amd64 kernels are built, or, if everything must be modular, a bug due to the lack of a patch enabling generic ide support when CONFIG_BLK_DEV_IDE is built as a module. In #407759 (bugreport is being Cc-ed) is about the same kernel CONFIG define see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407759;msg=15;att=0 for the complete text. HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402762: debian-installer dosen't detect Broadcom BCM5704 Gigabit LAN
Op 12-12-2006 om 15:13 schreef Mgr. Peter Tuharsky: I'm trying to install Debian Etch at TYAN GT24 (2891) server machine. Installer dosen't detect the onboard Broadcom BCM5704 ethernet. Since the Linux kernel dos have the driver (tg3 AFAIK), I wonder why the card isn't detected. Even if I specify the driver from the list, it dosen't detect the card. Please provide the output of `lspci -nn` It would be nice if you only provided the lspci entry of the network card. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385697: Bug#399120: RC1 bugreport
Op 26-11-2006 om 20:17 schreef Johan Spee: Are you telling it is fixed in the _Debian_ kernel, version 2.6.18? Yes it is. Okay, thanks for telling. Cheers Geert Stappers (not closing these two BRs) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358824: #358824 seems fixed in 2.6.18-2-powerpc
Hello, Sound works on my Ibook2 with stock Debian 2.6.18-2-powerpc kernel. There are _no_ 'dmasound_pmac: Unknown symbol' messages. I suggest to close this bug that was reported in the 2.6.16 ages ;-) Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: Possible (partial) solution for device persistence issue
Op 17-10-2006 om 16:36 schreef dann frazier: On Tue, Oct 17, 2006 at 11:59:15PM +0200, Geert Stappers wrote: Please provide names of such tools. (TIA) udev - see /dev/by-id, etc. Doing `udevinfo -e` got me: P: /block/hda N: hda S: disk/by-id/ata-IC25N020ATMR04-0_MRG108K1HJSLPH S: disk/by-path/pci-0.0001f000:ata-4-ide-0:0 E: ID_TYPE=disk E: ID_MODEL=IC25N020ATMR04-0 E: ID_SERIAL=MRG108K1HJSLPH E: ID_REVISION=MO1OAD4A E: ID_BUS=ata E: ID_PATH=pci-0.0001f000:ata-4-ide-0:0 P: /block/hda/hda1 N: hda1 S: disk/by-id/ata-IC25N020ATMR04-0_MRG108K1HJSLPH-part1 S: disk/by-path/pci-0.0001f000:ata-4-ide-0:0-part1 E: ID_TYPE=disk E: ID_MODEL=IC25N020ATMR04-0 E: ID_SERIAL=MRG108K1HJSLPH E: ID_REVISION=MO1OAD4A E: ID_BUS=ata E: ID_PATH=pci-0.0001f000:ata-4-ide-0:0 P: /block/hda/hda10 N: hda10 S: disk/by-id/ata-IC25N020ATMR04-0_MRG108K1HJSLPH-part10 S: disk/by-path/pci-0.0001f000:ata-4-ide-0:0-part10 S: disk/by-label/bootstrap E: ID_TYPE=disk E: ID_MODEL=IC25N020ATMR04-0 E: ID_SERIAL=MRG108K1HJSLPH E: ID_REVISION=MO1OAD4A E: ID_BUS=ata E: ID_PATH=pci-0.0001f000:ata-4-ide-0:0 E: ID_FS_USAGE=filesystem E: ID_FS_TYPE=hfs E: ID_FS_VERSION= E: ID_FS_UUID= E: ID_FS_LABEL=bootstrap E: ID_FS_LABEL_SAFE=bootstrap I think that by-path is the presistent thing I want (expect that it is long) Anyway: I hope that /dev/sda1 survives UUID=way-too-long-unique-string Thank you Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: Possible (partial) solution for device persistence issue
Op 16-10-2006 om 00:06 schreef Frans Pop: On Sunday 15 October 2006 23:45, Geert Stappers wrote: The thing I would like to see is that the _difference_ in device naming between d-i kernel plus fellows and installed kernel plus fellows is solved. See the discussions that we have had about this in the past. The culprit is the kernel/udev: that can load drivers in a different order any time. It is not something we can solve in the installer. The experts have said that using UUID is the best solution. I agree that it is extremely ugly. Dear Kernel developers, Your work is appriceated, but I have a request: Please allow reproducable hardware detection. As systemadministrator I can't affort having a disk that is one moment /dev/sda and the next reboot /dev/sdb. Having a fast booting system is great, having disks swapped not. Please prefer consistence above speed. Thank you for reading this humble plea. Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: Possible (partial) solution for device persistence issue
Op 17-10-2006 om 17:10 schreef maximilian attems: On Tue, Oct 17, 2006 at 04:27:19PM +0200, Geert Stappers wrote: Dear Kernel developers, Your work is appriceated, but I have a request: Please allow reproducable hardware detection. As systemadministrator I can't affort having a disk that is one moment /dev/sda and the next reboot /dev/sdb. Having a fast booting system is great, having disks swapped not. the kernel _never_ guaranteed stable device nodes, that is an userspace policy. I should smile. In 1997 I had /dev/sda, which had SCSI target Id #3. When I added another disk, being target #2, that became /dev/sda And the original /dev/sda went into /dev/sdb rendering the system _unbootable_ So after about 10 years, is the answer use UUID. I should laugh ... use the tools that provide that. Please provide names of such tools. (TIA) Please prefer consistence above speed. Thank you for reading this humble plea. Geert Stappers edgy udev transforms the fstab to use plain uuids, to guarantee correct root recognition. i guess their installer also add uuid entries to the newly installed fstab - why is that not in d-i? -- maks Cheers Geert Stappers -- During system recovery provide the boot option: root=UUID=4a6aed11-42dd-4c82-81ce-8f469e93f210 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation Report: etch beta 3 on Asus P5LD2-VM: *FAILED*
On Mon, Sep 25, 2006 at 11:14:48AM +0800, Arne Götje (?) wrote: Hi list, I tried to install Debian etch with the beta 3 netinstall image on an Asus P5LD2-VM board with a Dual Core Intel CPU, Intel 945G Northbridge and Intel ICH7 Southbridge. The machine came with an SATA HD and an IDE DVD ROM. The install failed because the CD could not detect the DVD drive. It appeared that the SATA driver (ata_piix) was loaded before the legacy IDE drivers. Because the ICH7 southbridge provides both, SATA and IDE, but with the same IO and IRQ, it happened, that the kernel complained the the IO was already in use and the legacy IDE driver could not be loaded. snip/ So, two things: 1. upgrade the kernel to the current 'testing' version Current versions of d-i are using 2.6.17 and .18 is work in progress. ( Debian-Installer version Beta 3 has a 2.6.16 kernel ) 2. make sure the IDE drivers get loaded before ata_piix I don't known about the loading sequence, but do known that that question/request is more appropriate at the kernel mailinglist. (that ML is CarbonCopied.) HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Updating linux-2.6 in testing (to 2.6.17)
On Sat, Aug 19, 2006 at 03:04:08AM -0400, Filipus Klutiero wrote: Hi, 3 days ago Frederik Schueler mentioned the following item for then's today in his Kernel schedule proposal for Etch: start migration of 2.6.17 kernel and udebs to testing snip/ Since I'm afraid that the Linux team isn't doing anything to update linux-2.6 in testing and that nothing else feels responsible for doing so, I'm initiating the discussion. I request the release team to force a linux-2.6 update (to 2.6.17) in testing in 3 days unless objections are raised until then. If you have an objection, please raise it on debian-release only (dropping d-boot and d-kernel). Being afraid is normal behaviour when _no_ informatiion is available. A common reason for not providing information is we are working on it. In other words: A discussion to force a release does not help. Things that do help: * Find a way to help * Find out what the current status is * Find out where to see progress HtH Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Move of update-grub and grub-install to /usr/sbin
On Fri, Aug 11, 2006 at 06:10:15PM -0300, Otavio Salvador wrote: Hello, I plan to upload a group of changes to grub and grub-installer to move update-grub and grub-install to /usr/sbin/. For this to happen, my transition plan is described bellow: - A new grub package would be uploaded to unstable having a group of wrappers that will call /usr/sbin utilities but warn the user to edit his/her /etc/kernel-img.conf. That keeps backward compatibility with previous kernels and will be in place until Etch is released, - A NEWS.Debian entry describing the change in grub would be add too, - grub-installer would have a change to don't use full paths in kernel-img.conf entries _but_ this one need to migrate to etch together with linux-2.6 2.6.17-6 OR new installations will be broken. RM team, is ok to me go forward with it? I think the above misses the _why_ The announce only mentions the new, the proposed, location. I'm happy with the removal of the full paths, but not happy with /usr/sbin Please allow to grub install _without_ the filesystem _/usr mounted_. So either move it to /bin or /sbin, both are mounted when in single user mode (as mostly used for recovery) Cheers Geert Stappers signature.asc Description: Digital signature
Bug#358824: here also and will module recompile help
Hello, The Ibook2 here is also effect by this bug. Will a module recompile help? I mean: Does make sense that I only compile the sound modules? Or do I need to rebuild the whole kernel. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358824: also on 2.6.17-1
This bug occures also on the Debian 2.6.17-1-powerpc kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
got module.o but need module.ko
Hello, This is what I did apt-get source linux-image-2.6 cd linux-2.6-2.6.17 cp /boot/config-2.6.17-1-powerpc .config make oldconfig make sound/ # I only want the sound modules I get sound/module.o and also insmod: error inserting './module.o': -1 Invalid module format What is needed to get sound/module.ko ? Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel/d-i/security/release meeting at DebConf6
[ keeping the cross-post and please keep it cross-posted ] On Sun, May 21, 2006 at 01:09:45PM -0500, dann frazier wrote: hey, Frans Pop assembled an informal BoF at DebConf to discuss cross-team issues related to the kernel[1]. We discussed the following topics: snip/ * Non-free modules + firmware * External module packages Non-free modules + firmware --- It was noted that Bastian Blank is working on splitting non-free modules out of main into their own source package. frans It should happen pretty soon; we need the modules in non-free before we do the d-i work; d-i will probably ask for an exception so that d-i can install them as though they were in main because frans thinks we won't have time for that (modules really won't be in main) This means that non-free modules will be on installer cds. The needed exception would be to allow etch to be used as a transition period. manoj this isn't a release management decision, we don't want another GR aba a GR would be time consuming manoj what about a free and a non-free installer image, where the non-free installer is in the non-free section What work is done to get the Linux kernel completely libre? Who is talking with hardware manufactures to GPL their code? aba 2-3 different options * images like today w/ non-free udebs * only put the modules on non-free, make users pick them up * dropping support for devices that require non-free fw completely manoj only option (for permitting non-free modules on the etch installer) is a gr to once again modify our social contract suggestion was made to have users click-through to opt-in to use non-free firmware. manoj believes this is still a violation of the social contract and will require a GR (because the non-free modules would still be on the media) manoj you can ask for an official interpretation of the social contract from the project secretary. manoj suggests two different installers, but joeyh is concerned over additional maintenance/support The deliver modules/users opt-in approach would give us enough time, but requires a GR. joeyh maybe keep it as a separate image that can be combined by the user, problem is that the solution varies with each installation method floppy install needs another floppy; netboot needs another layered initramfs joeyh multi-sessions could be used for cd installs In conclusion, we believe the following options exist: a) debian doesn't support this hardware b) GR to allow combining c) make users combine External module packages Its believed that if we solve the non-free external module package issue, we will also have solved this one. Beside non-free will the external module package help hardware manufactures to get their libre driver in Debian - divergence between official kernel packaging and kernel-package (k-p) The /lib/modules/$(uname -r)/build symlink issue was introduced by Manoj. The attendees agreed to move this to a discussion thread on debian-kernel, in probably a week's time. Please post the outcome also to debian-boot Cheers Geert Stappers [1] http://lists.debconf.org/lurker/message/20060517.065113.4f39d60e.en.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360681: kernel: NIC: Unknow symbol mii_*
Package: linux-image-2.6.16-1-486 Tags: d-i Hello, On a computer where d-i works fine with 2.6.15, it doesn't work with 2.6.16. The NIC module is not loaded. Debian-Installer syslog says: Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_ethtool_sset Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_link_ok Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_check_link Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_nway_restart Apr 4 02:32:12 kernel: eepro100: Unknown symbol mii_ethtool_gset Apr 4 02:32:12 kernel: e100: Unknown symbol mii_ethtool_sset Apr 4 02:32:12 kernel: e100: Unknown symbol mii_link_ok Apr 4 02:32:12 kernel: e100: Unknown symbol mii_check_link Apr 4 02:32:12 kernel: e100: Unknown symbol mii_nway_restart Apr 4 02:32:12 kernel: e100: Unknown symbol generic_mii_ioctl Apr 4 02:32:12 kernel: e100: Unknown symbol mii_ethtool_gset Doing a manual `modprobe e100` in d-i syslog says: Apr 4 02:34:06 kernel: e100: Unknown symbol mii_ethtool_sset Apr 4 02:34:06 kernel: e100: Unknown symbol mii_link_ok Apr 4 02:34:06 kernel: e100: Unknown symbol mii_check_link Apr 4 02:34:06 kernel: e100: Unknown symbol mii_nway_restart Apr 4 02:34:06 kernel: e100: Unknown symbol generic_mii_ioctl Apr 4 02:34:06 kernel: e100: Unknown symbol mii_ethtool_gset Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removal of svenl from the project
On Wed, Mar 15, 2006 at 10:59:46AM -0500, Stefano Zacchiroli wrote: snip/ So far, I have never took the time to study the detail of the expulsion process, so sorry if this mail is inappropriate. But be sure that I will do everything I can as a DD to stop Sven's expulsion. Here another DD that doesn't has time to study the expulsion process. Right now is my approach to wait for a voting for the actual expulsion and then vote to keep Sven Luther _in_ the project. Let me know if I need to do something else to keep luther a DD. Geert Stappers P.S. Cc me about this energy drain issue -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354124: 02/21 Etch install -- DHCP fails for Realtek 8139
On Sat, Feb 25, 2006 at 05:05:16PM -0500, David B van Balen wrote: The installer appears to recognize my card (Realtek Semiconductor Co., Ltd RTL-8139/813/8139C+ (rev 10)) properly and load the correct modules (8139cp, 8139too, mii, eth1394, ieee1394) during the Detect Network Hardware step, but fails in the Configure the network step. thinking volume=loud Mmm, 8139cp _and_ 8139too I wonder why twice a simular NIC driver ? One loaded by the kernel, the other by discover, both for the same physical NIC. That will cause problems /thinking If I then run ifconfig in a separate VT, I can see lo, but not eth0. Running 'ifconfig eth0 up' succeeds and I can see eth0, but running dhclient merely results in multiple messages like DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, followed by No DHCPOFFERS received and No working leases in persistent database. That reminds me at bugreport #354124. HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288010: PowerPC installed initrd misses files
On Thu, Jan 06, 2005 at 04:20:34PM +0100, Joerg Dorchain wrote: On Sat, Jan 01, 2005 at 05:56:32PM +0100, Geert Stappers wrote: - the ohci1334 module needed to drive the external firewire disk is missing from the image. Is this simular as http://bugs.debian.org/283712, Reboot from USB Hard Disk failed? Thanks to this hint I now finally got the installtion finished. :-) those are the better messages :-D [ Steps needed ] The system now boots at last. Okay, nice. A final remark, in the used /target/etc/mkinird/mkinitrd.conf BUSYBOX was set to no. (I am not a mkinitrd expert) Did you left it set to no? Did you have to change it? If yes, in what? In other words: What do you want to achieve with your remark? Currently I am fighting keymap problems (it seems that none of the supllied keymaps allows ALT-Fx console switching), but that will be a separated bug report. I do know that is is not the ALT-key on Apple PowerPC, but I don't know which key it is (and have no FAQ at hand ;-) Bye, Joerg Cheers Geert Stappers signature.asc Description: Digital signature
Bug#277298: Dell hwclock Patch worked for me
On Tue, Jan 04, 2005 at 09:34:55PM +1100, Craig Small wrote: Hello, snip/ Anyway I can happily say that the patch supplied by Geert which fixes hwclock works for me. It works best if you wait until the installer spits out the CDROM and asks if it can reboot. Flick to the F2 screen and wget and run Geert's patch. :-) Thanks all! TNX for confirming - Craig Cheers Geert Stappers signature.asc Description: Digital signature
Bug#277298: installation issue: No partitionable media were found
On Sat, Jan 01, 2005 at 03:27:57PM -0800, Asirvatham Kripps wrote: Hi, Thanks much for the help. I was able to complete the installation with linux26. And of course I encountered the problem with the installation hanging after Real Time Clock Driver v1.12. But after I modified the hwclock as mentioned in the resolution for bug #277298, everything went through perfectly. Would you please do another install? And `wget 277298` `sh 277298` in the ALT-F2 console before the reboot of the debian-installer? Thanks a lot, Kripps/- Cheers Geert Stappers signature.asc Description: Digital signature
Bug#288010: PowerPC installed initrd misses files
On Fri, Dec 31, 2004 at 06:33:07PM +0100, Joerg Dorchain wrote: Package: debian-installer This is a series of bugs I found while tring to install debian on an ibook G4 on an external firewire harddisk. The installed initrd image misses files. - a sleep command is referenced in the /sbin/init script but is not on the image (see DELAY= parameter in the generated linuxrc.conf) May first thought was to clone this bug, but sleep could be on the disk that can't be read. So not yet cloned. - the ohci1334 module needed to drive the external firewire disk is missing from the image. Is this simular as http://bugs.debian.org/283712, Reboot from USB Hard Disk failed? The modification of initrd was last year considered a can of worms. Bye, Joerg Best Wishes for the new year, all of you. Cheers Geert Stappers signature.asc Description: Digital signature
Bug#277298: confirming workaround
On Tue, Dec 21, 2004 at 12:54:55PM +0100, Erik van Konijnenburg wrote: On Tue, Dec 21, 2004 at 09:32:19AM +0100, Geert Stappers wrote: snip/ Okay, that is the easy part :-) Does the workaround allow reboot without apci=off and without pressing Control-C ? That worked already, util-linux-2.12h has working timeout on rtc failures. In d-i rc2 the hang is gone, so the only motivation for the workaround would be to create a working hwclock. Just tested reboot: as expected the timeout error is gone now. Yes, I confirm that workaround works fine. (including reboot) The manual page of hwclock says: --directisa is meaningful only on an ISA machine or an Alpha (which imple- ments enough of ISA to be, roughly speaking, an ISA machine for hwclock's purposes). For other machines, it has no effect. This option tells hwclock to use explicit I/O instructions to access the Hardware Clock. Without this option, hwclock will try to use the /dev/rtc device (which it assumes to be driven by the rtc device driver). If it is unable to open the device (for read), it will use the explicit I/O instructions anyway. The rtc device driver was new in Linux Release 2. So this bugreport, currently filed against kernel-source, is IMNSHO not bug a kernel bug. It is about special hardware that needs special treatment. And the special treatment is provided by the hwclock programm. Cheers Geert Stappers Erik: Dank je wel. None Dutch: Thank you very much. signature.asc Description: Digital signature
Bug#277298: untested workaround
Hello, In this bugreport there is the hint to modify the hwclock.sh files. But that is a change at several places. I'm not fond of that. However the addition of '--directisa' is indeed where it seems to hurt. (kernel, hwclock and hardware mismatch) I have this (untested) workaround in mind: # cd /sbin # ./hwclock --version hwclock from util-linux-2.12 # mv hwclock hwclock-2.12 # cat hwclock HERE #!/bin/bash /sbin/hwclock-2.12 --directisa \$@ HERE # chmod +x hwclock it is a wrapper for the hwclock binary which appends directisa That is is untested is because I have currently no access to this Dell who is affect by this bug. Cheers Geert Stappers signature.asc Description: Digital signature
Bug#277298: Bug#285890: IR:
On Thu, Dec 16, 2004 at 10:29:37AM +0100, David Schmitt wrote: Package: installation-reports INSTALL REPORT snip/ Machine: Dell Precision 370 snip/ hwclock: can be solved by generous applicance of ^C and killall -9 hwclock. You encountered bugreport #277298 [1] Cheers Geert Stappers [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277298 signature.asc Description: Digital signature
Bug#283603: nForce2. forcedeth network driver loads with 2.6, but not with 2.4
On Mon, Nov 29, 2004 at 07:32:46PM -0800, Andriy Palamarchuk wrote: Package: installation-reports Debian-installer-version: Installer rc2, got on November 29 from http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc2/sarge-i386-netinst.iso snip/ Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [E] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] snip/ Comments/Problems: Summary: Initialization of forcedeth network driver fails with the provided 2.4 kernel, however the driver initializes succcessfully if running 2.6 kernel (when the installation is started with linux26 on the installation prompt. The machine has installed Mandrake 10 Steps to reproduce: 1) Booting from CD, accepting all the default choices. 2) Get to the page with message no ethernet card was detected and list of network drivers. Select forcedeth driver. 3) Get message forcedeth driver failed to load, I am requested driver parameters. Don't choose anything, hit Enter - again get the list from step 2. Note, the driver loads with 2.6. Steps to reproduce: 1) Booting from CD, specifing linux26 on the initial prompt, hit Enter, accept all the default choices 2) Get to the page with message no ethernet card was detected and list of network drivers. Select forcedeth driver. 3) Autoconfiguration runs successfully, network detected, I am requested to configure DHCP client. Let me know if you need more information. Could you do a complete install with a 2.6 kernel? Regards, Andriy Palamarchuk Cheers Geert Stappers signature.asc Description: Digital signature
Bug#271310: kernel-image-2.6.8-sparc64: eth0 and eth1 swapped
Package: kernel-image-2.6.8-1-sparc64 Version: 2.6.8-2 After the upgrade from kernel 2.4.26 to 2.6.8 the ethernet interface eth0 and eth1 are swapped. This should not happen. At 2.4.26 is the onboard interface (sun happy meal) eth0. That is reasonable, other NICs can be added or removed, so good candidates for (random) numbering. Cheers Geert Stappers pgp0qrpVAtoBV.pgp Description: PGP signature
Bug#271315: kernel-image-2.6.8-1-sparc64: sun keyboard unusable
Package: kernel-image-2.6.8-1-sparc64 Version: 2.6.8-2 Hello, After the upgrade from kernel 2.4.26 to 2.6.8 the sun keyboard became unusable. Hardware: Sun Ultrasparc 5 Sun keyboard model type 6 (connector is a PS/2 alike plug) I have made a serial console available for further testing, let me know which information you want. Cheers Geert Stappers pgpU5itnnYs0g.pgp Description: PGP signature
