My solution (until I attempt the solution in Greg's bug report) for now
has been to move to syslog-ng and add a filter to dump this message:
filter f_acpierror { not match(88022f81abc0); };
Then insert filter(f_acpierror); in the log {} stanza for
destination(df_messages).
At my next
This problem disappeared for me sometime while I was running Intrepid.
Now that I've done the upgrade to jaunty, it's back.
I upgraded via the do-release-upgrade method.
The precise message is:
Apr 26 10:34:46 arwen kernel: [54142.600473] ACPI: Unable to turn
cooling device [88022f81abc0]
Installing Intrepid now on the machine I've had this trouble with - a
Shuttle XPC.
Still seeing Unable to turn cooling device [88022f05dbe0] 'on'
Message hit the console during install every 6 seconds. Now that the
system is booted normally, same deal, every 6 seconds, I get that
message.
Err, I meant to thank Craig. My bad, sorry.
--
MASTER Network Manager should probe for GSM and CDMA command sets. It doesnt
detect 3g modems with serial capability only in hal
https://bugs.launchpad.net/bugs/268095
You received this bug notification because you are a member of Ubuntu
Bugs,
Alexander,
Thanks much for the fix option, but that file doesn't seem to be working
out, at least for me..
I dropped in /usr/share/hal/fdi/information/20thirdparty/ as
10-usb3g.fdi, mimicked the appropriate permissions, and rebooted the
system to be sure it would take.
Plug in the 3g device, no
Ah, apologies for my ignorance on this particular process.. I'll spare
you all the old gummer in my day... rhetoric at this point. :)
Attached is the output of lshal after adding the new fdi.
** Attachment added: lshal output after adding new fdi
The two appear to be pretty much the same, regardless of whether the new
fdi is in place or not.. The original output was attached to another
bug I'd opened, so here it is over here..
** Attachment added: Original lshal output, before adding new fdi
Antti nailed it.
I updated the 10-modem.fdi file to include support for the UM150 and
UM175. Attached is a patch against the current file from hal-info,
which I believe I'm now receiving from the nm PPA..
Works like a treat now. Very slick, nice work guys!
** Attachment added: Pantech USB
Public bug reported:
Binary package hint: network-manager
I just installed NM 0.7 from the PPA, only to find my Verizon UM175 USB
EVDO device isn't detected by NM. Currently
Attached is the output of lshal on my eeePC 1000, running Hardy.
You're looking for /dev/ttyACM0
I was successful in
** Attachment added: eeepc1000-lshal+vzw-um175.txt
http://launchpadlibrarian.net/17528458/eeepc1000-lshal%2Bvzw-um175.txt
--
Verizon Wireless UM175 USB evdo not detected by NM 0.7 from PPA
https://bugs.launchpad.net/bugs/268837
You received this bug notification because you are a member of
Just my $0.02, adjusted for inflation.. Here's a terminal log including
my dmesg, acpitool -e and dmidecode output. Running 2.6.24-19-server
x86_64 on a Core 2 Quad Q6700 (2.66 Ghz), 8GB RAM. The system is a
Shuttle XPC SP35P2 Pro, with the latest BIOS.
Hardy Server x86_64 edition. latest
For those, who like me, come across this report while searching for a
build as requested here, there's a pretty simple solution.
The current shipping freeradius version is 2.0.4, which includes a
debian/ directory, all nicely populated and ready to rock roll.
You'll need to have
12 matches
Mail list logo
