Re: How compiling kernel on Squeeze?
On Tue, 2013-11-26 at 19:10 +0100, Antispammbox-debian wrote: > It possible use file config of the kernel 2.6 Squeeze, for compiling > kernel 3.12? > I would expect you would be better off starting with the config from the 3.10 or 3.11 packages currently in Jessie/Sid. Ian. -- 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/1385541945.23632.14.ca...@dagon.hellion.org.uk
Bug#730614: Please enable CONFIG_CHECKPOINT_RESTORE for criu.
Package: linux Version: 3.12-1~exp1 Please enable CONFIG_CHECKPOINT_RESTORE for criu. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5295be13.5060...@progress-technologies.net
Processed: reassign 730614 to src:linux, forcibly merging 682700 730614
Processing commands for cont...@bugs.debian.org: > reassign 730614 src:linux 3.12-1~exp1 Bug #730614 [linux] Please enable CONFIG_CHECKPOINT_RESTORE for criu. Bug reassigned from package 'linux' to 'src:linux'. No longer marked as found in versions 3.12-1~exp1. Ignoring request to alter fixed versions of bug #730614 to the same values previously set Bug #730614 [src:linux] Please enable CONFIG_CHECKPOINT_RESTORE for criu. Marked as found in versions linux/3.12-1~exp1. > forcemerge 682700 730614 Bug #682700 [src:linux] linux-image-3.4-trunk-amd64: Enable CONFIG_CHECKPOINT_RESTORE Bug #682734 [src:linux] linux-image-3.4-trunk-amd64: config kernel for working crtools Bug #682734 [src:linux] linux-image-3.4-trunk-amd64: config kernel for working crtools Marked as found in versions linux/3.12-1~exp1. Marked as found in versions linux/3.12-1~exp1. Bug #730614 [src:linux] Please enable CONFIG_CHECKPOINT_RESTORE for criu. Severity set to 'wishlist' from 'normal' Marked as found in versions linux/3.4.4-1~experimental.1. Merged 682700 682734 730614 > thanks Stopping processing here. Please contact me if you need assistance. -- 682700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682700 682734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682734 730614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.138556404720123.transcr...@bugs.debian.org
Re: Bug#730639: efibootmgr freeze system when creating boot entry
On Wed, Nov 27, 2013 at 07:31:54PM +0400, kasatki...@gmail.com wrote: >Subject: efibootmgr freeze system when creating boot entry >Package: efibootmgr >Version: 0.5.4-7 >Severity: important > >Dear Maintainer, > >I'm trying to install Debian on Inel UEFI board. The system freezes >completely at the end of install phase, when grub (or elilo) tries to >create boot menu entry in UEFI BIOS. I've already tried different >versions of efibootmgr (from Debian Wheezy, Jessie, also from Ubuntu >13.10 and OpenSuSE 13.1) to no avail. If I run efibootmgr without >arguments it works and displays current boot entries. If I understand >correctly read works, but not write. > >The efivars module is loaded: >root@goliath:~# lsmod | grep efivars >efivars17257 1 efi_pstore > >There is many entries in /sys/firmware/efi/vars/ > >The motherboard is Intel Workstation Board S5520SC. > >Latest firmware update is installed on this board. > >My current workaround is to install system without bootloader, boot >from live USB, comment out efibootmgr calls in >/usr/lib/grub/x86_64-efi/grub-install, run grub-install, reboot, >manually create EFI boot entry in BIOS setup menu. > >What can I do to debug this issue? It sounds like you have either a kernel or hardware issue here - efibootmgr just uses the kernel-provided files in /sys as its interface to the hardware. Adding a CC to the kernel list in case anybody there has suggestions... -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt -- 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/20131127153926.ga8...@einval.com
Bug#700975: Marvell 88SE9230: Freaks out - Reported upstream?
Has this issue been reported upstream to the kernel developers? I just did a search on bugzila, and couldn't find any record of this issue. -- Marty -- 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/CAA0JPjuSRwCHQT0vGRJTDSx23RH98FX6XaSDB-Q7LHn=j2n...@mail.gmail.com
CONFIG_GPIO_SYSFS
hi all, i'm doing an embedded remote firewall/router and "management" system (preliminary approval's been obtained to release the code as GPL at some point) using a pc-engines alix6f2 (AMD Geode LX800), and have had to make the rather unfortunate and necessary decision to custom-compile the kernel. we picked 3.9.6 because that was what was available at the time, and was found to work [but can upgrade to latest debian/testing kernels] the custom-compiling was done because the board needs GPIO control of an arduino-style relay in order to control the power to a larger x86 motherboard and its associated equipment. the problem is that nobody has really said exactly why CONFIG_GPIO_SYSFS has been disabled by default in debian kernels. in fact if you look as far back as the 2.6.32-squeeze48 linux kernel, the orion5 and kirkwood boards have it "enabled", but nothing else does. this would not _be_ a problem if there was not some concern here about the use of "non-standard" i.e. "non-stock" software. the discussion and investigation surrounding this issue is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476 leaving out the historical issue (which is that the older 2.6 GPIO module worked because it bypassed SYSFS_GPIO) if there is an objection that SYSFS_GPIO is "unsafe" for general use on e.g. x86 systems, that objection is "overruleable" shall we say on the basis that *explicit* action has to be taken in order to access GPIO. chances of that happening randomly and accidentally are extremely slim, and in each GPIO module "unsafe" GPIO access is disabled by a hard-coded unalterable mask _anyway_. in the case of the CS5535 kernel module for example access to the shared NMI-IRQ/GPIO line is explicitly banned. can i possibly ask: 1) could someone please give a reasonable explanation / justification why CONFIG_GPIO_SYSFS is currently disabled by default 2) do those reasons in (1) still apply now (for the current testing linux kernel, at the time of writing i believe that's 3.11) 3) if they do not apply, please could i request that CONFIG_GPIO_SYSFS and CONFIG_GPIO_CS5535 be enabled by default in the 486 kernel builds (*nods to ben*) because we're a bit stuffed without them [1] many thanks, l. [1] i say "stuffed" - we would have to go with a USB-based relay solution, at a cost of around £30 from e.g. robot-electronics.co.uk for the RLY-USB2, instead of a much simpler £5 sainsmart arduino-style solution. -- 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/cac97d1n5dqfaus-3xnttfoygs+zqvnog3iar3dqccvdhzsc...@mail.gmail.com
Re: How compiling kernel on Squeeze?
On Tue, 2013-11-26 at 19:10 +0100, Antispammbox-debian wrote: It possible use file config of the kernel 2.6 Squeeze, for compiling kernel 3.12? I would expect you would be better off starting with the config from the 3.10 or 3.11 packages currently in Jessie/Sid. Ian. Ok, many thanks! Regards -- 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/305B1A885B124D2DA2DDC2187E8D3725@CentrinoDuo
Re: Bug#730639: efibootmgr freeze system when creating boot entry
On Wed, 2013-11-27 at 15:39 +, Steve McIntyre wrote: [...] > It sounds like you have either a kernel or hardware issue here - > efibootmgr just uses the kernel-provided files in /sys as its > interface to the hardware. Adding a CC to the kernel list in case > anybody there has suggestions... I wouldn't really expect the UEFI implementation on a 2010 board to be well-tested. Still, it may well be possible to work around the problem. I think the next thing to do would be to contact the upstream maintainer for Linux EFI support, Matt Fleming , and the mailing list linux-...@vger.kernel.org Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette' signature.asc Description: This is a digitally signed message part
