Processed: Re: Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 606017 important Bug #606017 [nvram-wakeup] nvram-wakeup: can't access /dev/mem Severity set to 'important' from 'grave' > tags 606017 unreproducible moreinfo Bug #606017 [nvram-wakeup] nvram-wakeup: can't access /dev/mem Added tag(s) un

Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-28 Thread maximilian attems
severity 606017 important tags 606017 unreproducible moreinfo stop On Thu, 16 Dec 2010, Steve M. Robbins wrote: > st...@riemann{~}sudo nvram-wakeup > nvram-wakeup: Your mainboard is currently not supported. > nvram-wakeup: Please try determining the addresses and sending the following > nvram-wa

Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-16 Thread Steve M. Robbins
On Thu, Dec 16, 2010 at 06:36:31PM +0100, Salvo Tomaselli wrote: > > I'm not part of the nvram-wakeup maintenance team, so I won't make the > > call, but I do wonder whether this is truly a grave problem in the > > sense that it renders the package unusable for everyone or whether it > > is a case

Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-16 Thread Salvo Tomaselli
> Thanks. Was that run as root? Yes, of course. You might notice that the error message is not "Permission denied" > I'm not part of the nvram-wakeup maintenance team, so I won't make the > call, but I do wonder whether this is truly a grave problem in the > sense that it renders the package unu

Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-16 Thread Steve M. Robbins
On Thu, Dec 16, 2010 at 02:03:02PM +0100, Salvo Tomaselli wrote: > On Monday 13 December 2010 00:02:08 you wrote: > > There isn't enough information provided. > > > > The package nvram-wakeup contains a number of binaries. What command > > was run? What was the output? What was the expected ou

Processed: Re: Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 606017 + moreinfo Bug #606017 [nvram-wakeup] nvram-wakeup: can't access /dev/mem Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 606017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-12 Thread Steve M. Robbins
tags 606017 + moreinfo thanks There isn't enough information provided. The package nvram-wakeup contains a number of binaries. What command was run? What was the output? What was the expected output? On Sun, Dec 05, 2010 at 04:39:53PM +0100, Salvo Tomaselli wrote: > Package: nvram-wakeup >

Bug#606017: nvram-wakeup: can't access /dev/mem

2010-12-05 Thread Salvo Tomaselli
Package: nvram-wakeup Version: 1.1-1 Severity: grave Justification: renders package unusable Kernel complains when /dev/mem is accessed: Program nvram-wakeup tried to access /dev/mem between 101000->101009. I am trying to recompile the kernel and change the CONFIG_STRICT_DEVMEM, but with the sto