Menu
▾
▴
mactel-linux-users — mactel-linux User
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
(1) |
Mar
(39) |
Apr
(76) |
May
(63) |
Jun
(56) |
Jul
(45) |
Aug
(112) |
Sep
(65) |
Oct
(115) |
Nov
(114) |
Dec
(100) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(87) |
Feb
(114) |
Mar
(179) |
Apr
(218) |
May
(147) |
Jun
(246) |
Jul
(155) |
Aug
(133) |
Sep
(103) |
Oct
(61) |
Nov
(37) |
Dec
(12) |
| 2008 |
Jan
(20) |
Feb
(123) |
Mar
(106) |
Apr
(59) |
May
(51) |
Jun
(62) |
Jul
(24) |
Aug
(42) |
Sep
(12) |
Oct
(21) |
Nov
(6) |
Dec
(33) |
| 2009 |
Jan
(16) |
Feb
(17) |
Mar
(11) |
Apr
(2) |
May
(4) |
Jun
(18) |
Jul
(24) |
Aug
(22) |
Sep
(31) |
Oct
(4) |
Nov
(2) |
Dec
|
| 2010 |
Jan
(19) |
Feb
(3) |
Mar
(26) |
Apr
(37) |
May
(10) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
(2) |
| 2011 |
Jan
(11) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(8) |
Dec
|
|
From: cyberdork33 <cyb...@gm...> - 2008-07-23 11:54:25
|
Yes, it is a patch against the Ubuntu kernel. The Ubuntu mactel- support team often submits patches against the Ubuntu kernel as well as upstream, but this may not have made it. On Jul 23, 2008, at 2:38 AM, paul s wrote: > > Would be nice if you could port your modification to 2.6.26 (if > anything > > needs to be updated), and ideally submit a patch. > > i just tested this on the 2.6.25.10 src and it applies... i don't > know about the 26 kernel but will check it out once fedora rolls > that.. the patch is attached as well as available here for a while... > > http://queuemail.com/mactel_fn_special_keys_penryn.patch > > this fixes the fn key as well as the mappings of the special keys... > > > I added this in the SVN (2.6.26). Where did you find this patch? > > google, i think, which led me to what seems a competing project on > launchpad... which kind of stinks since not everyone uses ubuntu > which it seems to be specific for... afaict... > > cheers > paul > > > > > > > Nicolas Boichat wrote: > > Hi, > > > > paul s wrote: > >> great, i found some of these bugs as well... i was on a mission > >> yesterday as i was tired of not having home, end, pageup/down... > >> however i manually applied this patch to the hid-quirks.c as it > >> wouldn't during the build... > >> > >> http://launchpadlibrarian.net/14613817/fix_fn_key_on_macbookpro_4_1_and_mb_air.patch > >> > >> > >> this got the fn key working for me... > > > > I added this in the SVN (2.6.26). Where did you find this patch? > > > >> then to fix the F4-F6 i modified the hid-input.c with the following > >> mappings... > >> > >> static struct hidinput_key_translation apple_fn_keys[] = { > >> { KEY_BACKSPACE, KEY_DELETE }, > >> { KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY }, > >> { KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY }, > >> { KEY_F3, KEY_PROG1, APPLE_FLAG_FKEY }, > >> { KEY_F4, KEY_PROG2, APPLE_FLAG_FKEY }, > >> { KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY }, > >> { KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY }, > >> { KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY }, > >> { KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY }, > >> { KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY }, > >> { KEY_F10, KEY_MUTE, APPLE_FLAG_FKEY }, > >> { KEY_F11, KEY_VOLUMEDOWN, APPLE_FLAG_FKEY }, > >> { KEY_F12, KEY_VOLUMEUP, APPLE_FLAG_FKEY }, > >> { KEY_UP, KEY_PAGEUP }, > >> { KEY_DOWN, KEY_PAGEDOWN }, > >> { KEY_LEFT, KEY_HOME }, > >> { KEY_RIGHT, KEY_END }, > >> { } > >> }; > > > > Would be nice if you could port your modification to 2.6.26 (if > anything > > needs to be updated), and ideally submit a patch. > > > > Thanks, > > > > Nicolas > diff -uNrp a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c > --- a/drivers/hid/hid-input.c 2008-07-23 02:59:58.000000000 -0400 > +++ b/drivers/hid/hid-input.c 2008-07-23 03:12:01.000000000 -0400 > @@ -100,8 +100,10 @@ static struct hidinput_key_translation a > { KEY_BACKSPACE, KEY_DELETE }, > { KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY }, > { KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY }, > - { KEY_F3, KEY_FN_F5, APPLE_FLAG_FKEY }, /* Expos� > */ > - { KEY_F4, KEY_FN_F4, APPLE_FLAG_FKEY }, /* > Dashboard */ > + { KEY_F3, KEY_PROG1, APPLE_FLAG_FKEY }, /* Exposé */ > + { KEY_F4, KEY_PROG2, APPLE_FLAG_FKEY }, /* > Dashboard */ > + { KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY }, > + { KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY }, > { KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY }, > { KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY }, > { KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY }, > diff -uNrp a/drivers/hid/usbhid/hid-quirks.c b/drivers/hid/usbhid/ > hid-quirks.c > --- a/drivers/hid/usbhid/hid-quirks.c 2008-04-16 22:49:44.000000000 > -0400 > +++ b/drivers/hid/usbhid/hid-quirks.c 2008-07-18 18:33:43.000000000 > -0400 > @@ -72,6 +72,12 @@ > #define USB_DEVICE_ID_APPLE_ALU_WIRELESS_ANSI 0x022c > #define USB_DEVICE_ID_APPLE_ALU_WIRELESS_ISO 0x022d > #define USB_DEVICE_ID_APPLE_ALU_WIRELESS_JIS 0x022e > +#define USB_DEVICE_ID_APPLE_WELLSPRING_ANSI 0x0223 > +#define USB_DEVICE_ID_APPLE_WELLSPRING_ISO 0x0224 > +#define USB_DEVICE_ID_APPLE_WELLSPRING_JIS 0x0225 > +#define USB_DEVICE_ID_APPLE_WELLSPRING2_ANSI 0x0230 > +#define USB_DEVICE_ID_APPLE_WELLSPRING2_ISO 0x0231 > +#define USB_DEVICE_ID_APPLE_WELLSPRING2_JIS 0x0232 > #define USB_DEVICE_ID_APPLE_FOUNTAIN_TP_ONLY 0x030a > #define USB_DEVICE_ID_APPLE_GEYSER1_TP_ONLY 0x030b > #define USB_DEVICE_ID_APPLE_IRCONTROL4 0x8242 > @@ -637,6 +643,14 @@ static const struct hid_blacklist { > { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_GEYSER1_TP_ONLY, > HID_QUIRK_APPLE_HAS_FN | HID_QUIRK_IGNORE_MOUSE }, > > { USB_VENDOR_ID_DELL, USB_DEVICE_ID_DELL_W7658, > HID_QUIRK_RESET_LEDS }, > + > + { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING_ANSI, > HID_QUIRK_APPLE_HAS_FN }, > + { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING_ISO, > HID_QUIRK_APPLE_HAS_FN | HID_QUIRK_APPLE_ISO_KEYBOARD }, > + { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING_JIS, > HID_QUIRK_APPLE_HAS_FN }, > + { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING2_ANSI, > HID_QUIRK_APPLE_HAS_FN }, > + { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING2_ISO, > HID_QUIRK_APPLE_HAS_FN | HID_QUIRK_APPLE_ISO_KEYBOARD }, > + { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING2_JIS, > HID_QUIRK_APPLE_HAS_FN }, > + > { USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_KBD, > HID_QUIRK_RESET_LEDS }, > { USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_HARMONY, > HID_QUIRK_IGNORE }, > { USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_HARMONY_2, > HID_QUIRK_IGNORE }, > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users |
|
From: paul s <mac...@qu...> - 2008-07-23 09:07:26
|
> Would be nice if you could port your modification to 2.6.26 (if anything > needs to be updated), and ideally submit a patch. i just tested this on the 2.6.25.10 src and it applies... i don't know about the 26 kernel but will check it out once fedora rolls that.. the patch is attached as well as available here for a while... http://queuemail.com/mactel_fn_special_keys_penryn.patch this fixes the fn key as well as the mappings of the special keys... > I added this in the SVN (2.6.26). Where did you find this patch? google, i think, which led me to what seems a competing project on launchpad... which kind of stinks since not everyone uses ubuntu which it seems to be specific for... afaict... cheers paul Nicolas Boichat wrote: > Hi, > > paul s wrote: >> great, i found some of these bugs as well... i was on a mission >> yesterday as i was tired of not having home, end, pageup/down... >> however i manually applied this patch to the hid-quirks.c as it >> wouldn't during the build... >> >> http://launchpadlibrarian.net/14613817/fix_fn_key_on_macbookpro_4_1_and_mb_air.patch >> >> >> this got the fn key working for me... > > I added this in the SVN (2.6.26). Where did you find this patch? > >> then to fix the F4-F6 i modified the hid-input.c with the following >> mappings... >> >> static struct hidinput_key_translation apple_fn_keys[] = { >> { KEY_BACKSPACE, KEY_DELETE }, >> { KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY }, >> { KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY }, >> { KEY_F3, KEY_PROG1, APPLE_FLAG_FKEY }, >> { KEY_F4, KEY_PROG2, APPLE_FLAG_FKEY }, >> { KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY }, >> { KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY }, >> { KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY }, >> { KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY }, >> { KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY }, >> { KEY_F10, KEY_MUTE, APPLE_FLAG_FKEY }, >> { KEY_F11, KEY_VOLUMEDOWN, APPLE_FLAG_FKEY }, >> { KEY_F12, KEY_VOLUMEUP, APPLE_FLAG_FKEY }, >> { KEY_UP, KEY_PAGEUP }, >> { KEY_DOWN, KEY_PAGEDOWN }, >> { KEY_LEFT, KEY_HOME }, >> { KEY_RIGHT, KEY_END }, >> { } >> }; > > Would be nice if you could port your modification to 2.6.26 (if anything > needs to be updated), and ideally submit a patch. > > Thanks, > > Nicolas |
|
From: paul s <mac...@qu...> - 2008-07-19 19:17:11
|
great, i found some of these bugs as well... i was on a mission yesterday as i was tired of not having home, end, pageup/down... however i manually applied this patch to the hid-quirks.c as it wouldn't during the build... http://launchpadlibrarian.net/14613817/fix_fn_key_on_macbookpro_4_1_and_mb_air.patch this got the fn key working for me... then to fix the F4-F6 i modified the hid-input.c with the following mappings... static struct hidinput_key_translation apple_fn_keys[] = { { KEY_BACKSPACE, KEY_DELETE }, { KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY }, { KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY }, { KEY_F3, KEY_PROG1, APPLE_FLAG_FKEY }, { KEY_F4, KEY_PROG2, APPLE_FLAG_FKEY }, { KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY }, { KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY }, { KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY }, { KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY }, { KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY }, { KEY_F10, KEY_MUTE, APPLE_FLAG_FKEY }, { KEY_F11, KEY_VOLUMEDOWN, APPLE_FLAG_FKEY }, { KEY_F12, KEY_VOLUMEUP, APPLE_FLAG_FKEY }, { KEY_UP, KEY_PAGEUP }, { KEY_DOWN, KEY_PAGEDOWN }, { KEY_LEFT, KEY_HOME }, { KEY_RIGHT, KEY_END }, { } }; i can confirm these are working on the mbp4,1 w/ 2.6.25.10 kernel... pommed 1.18 seems to be working well for me... i am just using the default config file... one note on your config file, i have set CONFIG_MCORE2=y and not the CONFIG_GENERIC_CPU not sure if this makes much of a difference but this also seems to work... i'll try and put this in the wiki since really we have gotten off topic from teh motion sensor... ;-) cheers paul hoarycripple wrote: > * paul s <mac...@qu...> [2008-07-18 22:21:22 -0400]: > >> the fn key itself it is non responsive... i don't see a hid-input patch >> in the mactel-patches-2.6.25 series, so it raised my curiousity of which >> one your were referring to or if you used another patch from another >> repo... >> > > Ahh, I see! Are all your FN keys non-functional, or just some of them? When > I first installed Ubuntu 8.04 on the MacBook Pro Penryn, My F4-F6 keys were > non-functional, but the others worked. > > The fix I am referring to is this bug: > > https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/207127 > > And this post specifically within the bug discussion: > > https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/207127/comments/26 > > There is a pre-compiled hid module available through that above link. You > should replace your existing hid module with the newer one, or compile one of > your own. I compiled mine, so I cannot say with 100% certainty that the > pre-compiled module works, but there shouldn't be any problem. > > I have tested the above with only 2.6.25.5 and the patch set here: > > http://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/ > > You will also need to install the latest version of pommed from source. > > Here is my kernel config: > > http://ubuntuforums.org/showpost.php?p=5208368&postcount=9 > > I will send my pommed.conf in a later email if you wish. I am not currently > at my macbook and don't have that file readily available. > > Good luck. I hope this works for you! > > > |
|
From: hoarycripple <hoa...@gm...> - 2008-07-19 16:14:50
|
* paul s <mac...@qu...> [2008-07-18 22:21:22 -0400]: > the fn key itself it is non responsive... i don't see a hid-input patch > in the mactel-patches-2.6.25 series, so it raised my curiousity of which > one your were referring to or if you used another patch from another > repo... > Ahh, I see! Are all your FN keys non-functional, or just some of them? When I first installed Ubuntu 8.04 on the MacBook Pro Penryn, My F4-F6 keys were non-functional, but the others worked. The fix I am referring to is this bug: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/207127 And this post specifically within the bug discussion: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/207127/comments/26 There is a pre-compiled hid module available through that above link. You should replace your existing hid module with the newer one, or compile one of your own. I compiled mine, so I cannot say with 100% certainty that the pre-compiled module works, but there shouldn't be any problem. I have tested the above with only 2.6.25.5 and the patch set here: http://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/ You will also need to install the latest version of pommed from source. Here is my kernel config: http://ubuntuforums.org/showpost.php?p=5208368&postcount=9 I will send my pommed.conf in a later email if you wish. I am not currently at my macbook and don't have that file readily available. Good luck. I hope this works for you! -- You will hear good news from one you thought unfriendly to you. |
|
From: paul s <mac...@qu...> - 2008-07-19 02:21:44
|
the fn key itself it is non responsive... i don't see a hid-input patch in the mactel-patches-2.6.25 series, so it raised my curiousity of which one your were referring to or if you used another patch from another repo... hoarycripple wrote: > * paul s <mac...@qu...> [2008-07-18 12:45:29 -0400]: > >> what's this fix? >> >> > hid-input fix for the function keys >> >> i still am unable to get the function key working... >> > > What exactly is not working? > > With the fixes that I described, I can get the function keys to control sound, > screen brightness and keyboard backlight. > > The hid-input patch fixes some of the FN key bindings IIRC. > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users |
|
From: hoarycripple <hoa...@gm...> - 2008-07-18 23:15:56
|
* paul s <mac...@qu...> [2008-07-18 12:45:29 -0400]: > what's this fix? > > > hid-input fix for the function keys > > i still am unable to get the function key working... > What exactly is not working? With the fixes that I described, I can get the function keys to control sound, screen brightness and keyboard backlight. The hid-input patch fixes some of the FN key bindings IIRC. -- You love peace. |
|
From: Justin M. <jus...@gm...> - 2008-07-18 18:16:50
|
On Fri, Jul 18, 2008 at 4:45 PM, paul s <mac...@qu...> wrote: > what's this fix? > > > hid-input fix for the function keys > > i still am unable to get the function key working... > > > > hoarycripple wrote: >> I recently installed linux on a 4th generation macbook pro and >> everything is working properly except for the motion sensor. I get an >> error that states: >> >> >> applesmc: Cannot set motion sensor. might not receive some interrupts. >> >> >> This only occurs if I hard boot to linux. If I first boot to osx, and >> then soft boot (restart) to linux, the motion sensor works as >> expected. >> >> Kernel: 2.6.25.5 (all mactel-linux patches applied along with the >> hid-input fix for the function keys) >> >> Can someone confirm this behavior? >> >> Thank you, >> >> HC >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Mactel-linux-users mailing list >> Mac...@li... >> https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > I think I've lost all hope for the function key; although in pommed.conf you have an option which tells me that it works. As for applesmc I think you're on the right track i.g. hard drive protection might be the missing sensor that is causing the debug message to trigger. -- Justin P. Mattock |
|
From: paul s <mac...@qu...> - 2008-07-18 18:06:11
|
looks like this message has disappeared with the latest kernel 2.6.25.10-47... i am now getting this, so i am thinking it is loading.. kernel: applesmc: received a shock interrupt still am unable to apply the the applesmc-int-protect.patch though... cheers paul Justin Mattock wrote: > On Thu, Jun 26, 2008 at 4:21 PM, Harald Psaier <h_p...@gm...> wrote: >> I have the same problem. Pommed doesn't complain (just signalizes in >> logs that backlight handler have been found, and they work just fine). >> So has anyone already filed a bug report? If not I would do so. >> >> Greetings >> HARALD >> On Thu, 2008-06-19 at 00:02 +0000, Justin Mattock wrote: >>> On Wed, Jun 18, 2008 at 8:29 PM, paul s >>> <mac...@qu...> wrote: >>>> > applesmc: Cannot set motion sensor. might not receive some interrupts. >>>> >>>> i have the same error in my /var/log/messages ... however i have not >>>> been able to apply the applesmc-int-protect.patch to the 2.6.25 kernel... >>>> >>>> cheers >>>> paul >>>> >>>> >>>> hoarycripple wrote: >>>>> I recently installed linux on a 4th generation macbook pro and >>>>> everything is working properly except for the motion sensor. I get an >>>>> error that states: >>>>> >>>>> >>>>> applesmc: Cannot set motion sensor. might not receive some interrupts. >>>>> >>>>> >>>>> This only occurs if I hard boot to linux. If I first boot to osx, and >>>>> then soft boot (restart) to linux, the motion sensor works as >>>>> expected. >>>>> >>>>> Kernel: 2.6.25.5 (all mactel-linux patches applied along with the >>>>> hid-input fix for the function keys) >>>>> >>>>> Can someone confirm this behavior? >>>>> >>>>> Thank you, >>>>> >>>>> HC >>>>> >>>>> ------------------------------------------------------------------------- >>>>> Check out the new SourceForge.net Marketplace. >>>>> It's the best place to buy or sell services for >>>>> just about anything Open Source. >>>>> http://sourceforge.net/services/buy/index.php >>>>> _______________________________________________ >>>>> Mactel-linux-users mailing list >>>>> Mac...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/mactel-linux-users >>>> ------------------------------------------------------------------------- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> _______________________________________________ >>>> Mactel-linux-users mailing list >>>> Mac...@li... >>>> https://lists.sourceforge.net/lists/listinfo/mactel-linux-users >>>> >>> Hmm sounds like a bug, check /var/log/daemon.log to see if pommed is >>> complaining(probably not) but to just see. >>> If pommed is running fine try and save dmesg of the error and file a >>> report: http://bugzilla.kernel.org/ >>> Also keep in mind you did apply the patches, so maybe try a fresh >>> kernel. just to see. >>> regards; >>> >> > > Hello; Just make sure this occurs with a fresh kernel, with no patches > applied, before filing a bug report. > regards; > |
|
From: paul s <mac...@qu...> - 2008-07-18 18:06:10
|
what's this fix? > hid-input fix for the function keys i still am unable to get the function key working... hoarycripple wrote: > I recently installed linux on a 4th generation macbook pro and > everything is working properly except for the motion sensor. I get an > error that states: > > > applesmc: Cannot set motion sensor. might not receive some interrupts. > > > This only occurs if I hard boot to linux. If I first boot to osx, and > then soft boot (restart) to linux, the motion sensor works as > expected. > > Kernel: 2.6.25.5 (all mactel-linux patches applied along with the > hid-input fix for the function keys) > > Can someone confirm this behavior? > > Thank you, > > HC > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users |
|
From: Justin M. <jus...@gm...> - 2008-07-09 23:01:30
|
On Wed, Jul 9, 2008 at 6:49 PM, Harald Psaier <h_p...@gm...> wrote: > I am not sure if this is still about the applesmc init error on the > Sudden Motion Sensor... > But as announced previously I filled a kernel bug report at > "http://bugzilla.kernel.org/show_bug.cgi?id=10998". > It seems that the issue was addressed to Nicolas Boichat, but despite my > commitment to supply any help/information available the bug status > progress seems stuck. > > Greetings > HARALD > > On Wed, 2008-07-09 at 17:02 +0000, Justin Mattock wrote: >> On Wed, Jul 9, 2008 at 6:34 AM, Nicolas Boichat <ni...@bo...> wrote: >> > On Tue, 2008-07-08 at 02:16 +0000, Justin Mattock wrote: >> >> FWIW after looking at applesmc.c I noticed where applesmc wait status >> >> failed is generated from. >> >> Now keep in mind this is not a solution to the problem, but if you are >> >> tired of seeing this in dmesg then just >> >> remove the printk from the applesmc.c and recompile: >> > [snip] >> >> I suppose I could of submitted this as a patch, but like from the >> >> beginning am not convinced >> >> this is a proper solution.(just hides the problem), but I could be wrong. >> > >> > Have you tried this one? It should do the same... >> > https://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/mactel-patches-2.6.25/applesmc-remove-debugging-messages.patch >> > >> > Regards, >> > >> > Nicolas >> > >> > >> >> Cool, this is better takes care of all of the debugging, but besides >> just taking the whole mechanism out >> what about looking into finding what is really causing the message? >> or is this one of the mysterious things that happen!!! >> anyways thanks for the response. >> regards; >> > > Yeah; That's why I said that my workaround was not a solution the problem. In regards to what yo had said "progress seems stuck." The author probably has shit loads of other things to do, instead of having to deal with a debug warning, but then again the author could be doing nothing, and staring at this issue going "what the hell is a matter". I don't know maybe this has to do with the module originating from hdaps. regards; -- Justin P. Mattock |
|
From: Harald P. <h_p...@gm...> - 2008-07-09 18:49:51
|
I am not sure if this is still about the applesmc init error on the Sudden Motion Sensor... But as announced previously I filled a kernel bug report at "http://bugzilla.kernel.org/show_bug.cgi?id=10998". It seems that the issue was addressed to Nicolas Boichat, but despite my commitment to supply any help/information available the bug status progress seems stuck. Greetings HARALD On Wed, 2008-07-09 at 17:02 +0000, Justin Mattock wrote: > On Wed, Jul 9, 2008 at 6:34 AM, Nicolas Boichat <ni...@bo...> wrote: > > On Tue, 2008-07-08 at 02:16 +0000, Justin Mattock wrote: > >> FWIW after looking at applesmc.c I noticed where applesmc wait status > >> failed is generated from. > >> Now keep in mind this is not a solution to the problem, but if you are > >> tired of seeing this in dmesg then just > >> remove the printk from the applesmc.c and recompile: > > [snip] > >> I suppose I could of submitted this as a patch, but like from the > >> beginning am not convinced > >> this is a proper solution.(just hides the problem), but I could be wrong. > > > > Have you tried this one? It should do the same... > > https://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/mactel-patches-2.6.25/applesmc-remove-debugging-messages.patch > > > > Regards, > > > > Nicolas > > > > > > Cool, this is better takes care of all of the debugging, but besides > just taking the whole mechanism out > what about looking into finding what is really causing the message? > or is this one of the mysterious things that happen!!! > anyways thanks for the response. > regards; > |
|
From: Justin M. <jus...@gm...> - 2008-07-09 17:02:59
|
On Wed, Jul 9, 2008 at 6:34 AM, Nicolas Boichat <ni...@bo...> wrote: > On Tue, 2008-07-08 at 02:16 +0000, Justin Mattock wrote: >> FWIW after looking at applesmc.c I noticed where applesmc wait status >> failed is generated from. >> Now keep in mind this is not a solution to the problem, but if you are >> tired of seeing this in dmesg then just >> remove the printk from the applesmc.c and recompile: > [snip] >> I suppose I could of submitted this as a patch, but like from the >> beginning am not convinced >> this is a proper solution.(just hides the problem), but I could be wrong. > > Have you tried this one? It should do the same... > https://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/mactel-patches-2.6.25/applesmc-remove-debugging-messages.patch > > Regards, > > Nicolas > > Cool, this is better takes care of all of the debugging, but besides just taking the whole mechanism out what about looking into finding what is really causing the message? or is this one of the mysterious things that happen!!! anyways thanks for the response. regards; -- Justin P. Mattock |
|
From: Justin M. <jus...@gm...> - 2008-07-08 12:53:09
|
Hello; I'm wanting to know if anybody has done a dsdt override with there macbook, and if so would they be willing to share what they had modified. It seems there is an issue with the macbook's having too many interrupts with the battery causing a gpe storm to be triggered. i.g. when using acpi_osi=Linux look in /sys/firmware/acpi/interrupts (for some reason I'm seeing a huge number) then using acpi_osi=Darwin the number drastically drops, but you loose and info on you're battery. With that in mind any info on any tweaks that anybody dared or did would be appreciated. regards; -- Justin P. Mattock |
|
From: Justin M. <jus...@gm...> - 2008-07-08 02:16:24
|
FWIW after looking at applesmc.c I noticed where applesmc wait status
failed is generated from.
Now keep in mind this is not a solution to the problem, but if you are
tired of seeing this in dmesg then just
remove the printk from the applesmc.c and recompile:
static int __wait_status(u8 val)
{
unsigned int i;
val = val & APPLESMC_STATUS_MASK;
for (i = 0; i < 200; i++) {
if ((inb(APPLESMC_CMD_PORT) & APPLESMC_STATUS_MASK) == val) {
if (debug)
printk(KERN_DEBUG
"Waited %d us for status %x\n",
i*10, val);
return 0;
}
udelay(10);
}
- printk(KERN_WARNING "applesmc: wait status failed: %x != %x\n",
- val, inb(APPLESMC_CMD_PORT));
return -EIO;
}
I suppose I could of submitted this as a patch, but like from the
beginning am not convinced
this is a proper solution.(just hides the problem), but I could be wrong.
regards;
--
Justin P. Mattock
|
|
From: Mildred <ml....@on...> - 2008-07-08 00:37:18
|
Le Thu 26/06/2008 à 21:21 Pol Hallen à écrit: > Hi folks :-) > > Is there anyone that could run the isight? > Thanks! > > (I tried with last cvf of uvcvideo and fw patching) but > none /dev/video0 created) Dou you load the firmware correctly ? Whait is your lsusb output (lsusb -d 05ac:8501 -v) For me it shows three different interface with class 14 for each. If it doesn't work, try to halt (not just restart) your computer and restart it directly under GNU/Linux (nor Mac OS X before). iSight device can have two different USB ids. 05ac:8300 when no firmware is loaded and 05ac:8501 if there is a firmware loaded. ift (when using HAL) only check the first id. So if an unpatched firmware is loaded, HAL won't load the patched firmware, and uvcvideo will not work. To solve that, halt your computer, or use ift-load directly to load the correct patched firmware. You can look at a bug I filled: https://bugs.launchpad.net/isight-firmware-tools/+bug/243255 In any case, the output from lsusb -v from the iSight device can help. Mildred -- Mildred Ki'lya E-Mail: mildred593(at)online.fr Site: <http://mildred632.free.fr/> XMPP: <mi...@ja...> (GoogleTalk, Jabber) GPG: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 [9A7D 2E2B] |
|
From: Harald P. <h_p...@gm...> - 2008-06-27 16:26:08
|
Sorry Alexandre, I don't have any myth* nor ubuntu environment to look
at. The only help I can offer is a working lircrc for Totem:
### Totem
######################################################################
#
begin
prog = Totem
remote = *
button = play_pause
repeat = 1
config = play_pause
end
begin
prog = Totem
remote = *
button = forward
repeat = 1
config = seek_forward
end
begin
prog = Totem
remote = *
button = backward
repeat = 1
config = seek_backward
end
...(and so on)
Greetings
HARALD
On Thu, 2008-06-26 at 22:04 +0200, Alexandre Vázquez wrote:
> The same, I look the .lircrc and the .lircrc/ files (I use the
> package mythbuntu config files) and when I do irexec the output in
> lirc is the same that when I execute irw ..
>
> I don't know how to use the remote.. with the apps? :'(
>
> 2008/6/26 Pol Hallen <ma...@fu...>:
> > I was in the same step than Pol, I did what you told us and
> it work , but
> > the application doen't "view" the apple remote.. if I do cat
> > /dev/usb/hiddev0 I can see the efects when I press the
> bottoms of the
> > remote.. but with apps didn't work. I have to do anything to
> get work with
> > the apps (particulary KDE apps) ?
>
> look .lirrc config file
> and run irexec then try with you remote controller :-)
>
> tell me what happen.
>
> Pol
>
|
|
From: Justin M. <jus...@gm...> - 2008-06-26 22:33:40
|
On Thu, Jun 26, 2008 at 7:21 PM, Pol Hallen <ma...@fu...> wrote: > Hi folks :-) > > Is there anyone that could run the isight? > Thanks! > > (I tried with last cvf of uvcvideo and fw patching) but none /dev/video0 > created) > > Pol > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > Yeah it works over here. I'm not sure about the santa rosa, but for me the ATI chipset was easy, just open a terminal and: sudo svn checkout svn://svn.berlios.de/linux-uvc/linux-uvc/trunk once there install (make, make install) then either recompile you're kernel with the new isight_firmware module or grab the uvcvideo utils (ift-load) http://bersace03.free.fr/ift/ edit /etc/udev/rules.d/isight.rules and make sure it has this in it: ACTION=="add", SYSFS{idVendor}=="05ac", SYSFS{idProduct}=="8300" RUN+="/usr/lib/udev/ift-load -b 005 -d 003 --firmware /lib/firmware/isight.fw" Keep in mind the uvcutils should make isight.rules, but if not create it. then extract the firmware from OSX(mount the partition etc...) the modprobe uvcvideo and you're good to go, no more Morse code sounds coming from the esc key(at least that's what I hear when uvcvideo is not loaded) regards; -- Justin P. Mattock |
|
From: A. V. <ale...@gm...> - 2008-06-26 20:04:24
|
The same, I look the .lircrc and the .lircrc/ files (I use the package mythbuntu config files) and when I do irexec the output in lirc is the same that when I execute irw .. I don't know how to use the remote.. with the apps? :'( 2008/6/26 Pol Hallen <ma...@fu...>: > > I was in the same step than Pol, I did what you told us and it work , but > > the application doen't "view" the apple remote.. if I do cat > > /dev/usb/hiddev0 I can see the efects when I press the bottoms of the > > remote.. but with apps didn't work. I have to do anything to get work > with > > the apps (particulary KDE apps) ? > look .lirrc config file > and run irexec then try with you remote controller :-) > > tell me what happen. > > Pol > |
|
From: Pol H. <ma...@fu...> - 2008-06-26 19:54:22
|
> I was in the same step than Pol, I did what you told us and it work , but > the application doen't "view" the apple remote.. if I do cat > /dev/usb/hiddev0 I can see the efects when I press the bottoms of the > remote.. but with apps didn't work. I have to do anything to get work with > the apps (particulary KDE apps) ? look .lirrc config file and run irexec then try with you remote controller :-) tell me what happen. Pol |
|
From: Pol H. <ma...@fu...> - 2008-06-26 19:50:31
|
>I have to do anything to get work with > the apps (particulary KDE apps) ? Have u tried kdelirc? Pol |
|
From: A. V. <ale...@gm...> - 2008-06-26 19:44:44
|
Hi list and Haral specially, I was in the same step than Pol, I did what you told us and it work , but the application doen't "view" the apple remote.. if I do cat /dev/usb/hiddev0 I can see the efects when I press the bottoms of the remote.. but with apps didn't work. I have to do anything to get work with the apps (particulary KDE apps) ? I'm using Kubuntu 8.04 with kernel 2.6.24-19 .Thanks 2008/6/26 Harald Psaier <h_p...@gm...>: > Any luck? > I had the same problem myself. For some reason the apple remote key > codes changed or are grabbed the wrong way on my system. So after > debugging I came up with this config: > name Apple_A1156 > bits 8 > eps 30 > aeps 100 > > one 0 0 > zero 0 0 > pre_data_bits 24 > # pre_data 0x87EEFB > pre_data 0x87EE5C > gap 211995 > > begin codes > vol+ 0xB #+ > play_pause 0x4 #play/pause > vol- 0xD # - > forward 0x7 # next > backward 0x8 # prev > fullscreen 0x2 #Menu > end codes > > end remote > > give it a try! > > Greetings > HARALD > > On Tue, 2008-06-24 at 19:59 +0200, Pol Hallen wrote: > > > but when you start irw it should recognize+print the input from your > > > remote. > > Nothing :-/ > > ircd -n -H macmini -d /dev/usb/hiddev0 /etc/lirc/lircd.conf > > lircd-0.8.2[19309]: lircd(userspace) ready > > > > then I start irw > > (in other shell I see: > > lircd-0.8.2[19309]: accepted new client on /dev/lircd > > lircd-0.8.2[19309]: initializing '/dev/usb/hiddev0') > > > > but when I press any key nothing appens :-/ > > > > Thanks > > Pol > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > Mactel-linux-users mailing list > > Mac...@li... > > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > |
|
From: Pol H. <ma...@fu...> - 2008-06-26 19:21:22
|
Hi folks :-) Is there anyone that could run the isight? Thanks! (I tried with last cvf of uvcvideo and fw patching) but none /dev/video0 created) Pol |
|
From: Pol H. <ma...@fu...> - 2008-06-26 19:16:54
|
> If you have a funny red light coming out of your headphone plug Cool! Pol |
|
From: ZeLegolas . <zel...@gm...> - 2008-06-26 19:13:40
|
Hi, If you have a funny red light coming out of your headphone plug check this article: http://bbbart.internationalgeneration.be/blog/archives/2008/06/26/index.html#e2008-06-26T00_55_43.txt Enjoy :) |
|
From: Justin M. <jus...@gm...> - 2008-06-26 18:55:43
|
On Thu, Jun 26, 2008 at 4:21 PM, Harald Psaier <h_p...@gm...> wrote: > I have the same problem. Pommed doesn't complain (just signalizes in > logs that backlight handler have been found, and they work just fine). > So has anyone already filed a bug report? If not I would do so. > > Greetings > HARALD > On Thu, 2008-06-19 at 00:02 +0000, Justin Mattock wrote: >> On Wed, Jun 18, 2008 at 8:29 PM, paul s >> <mac...@qu...> wrote: >> > > applesmc: Cannot set motion sensor. might not receive some interrupts. >> > >> > i have the same error in my /var/log/messages ... however i have not >> > been able to apply the applesmc-int-protect.patch to the 2.6.25 kernel... >> > >> > cheers >> > paul >> > >> > >> > hoarycripple wrote: >> >> I recently installed linux on a 4th generation macbook pro and >> >> everything is working properly except for the motion sensor. I get an >> >> error that states: >> >> >> >> >> >> applesmc: Cannot set motion sensor. might not receive some interrupts. >> >> >> >> >> >> This only occurs if I hard boot to linux. If I first boot to osx, and >> >> then soft boot (restart) to linux, the motion sensor works as >> >> expected. >> >> >> >> Kernel: 2.6.25.5 (all mactel-linux patches applied along with the >> >> hid-input fix for the function keys) >> >> >> >> Can someone confirm this behavior? >> >> >> >> Thank you, >> >> >> >> HC >> >> >> >> ------------------------------------------------------------------------- >> >> Check out the new SourceForge.net Marketplace. >> >> It's the best place to buy or sell services for >> >> just about anything Open Source. >> >> http://sourceforge.net/services/buy/index.php >> >> _______________________________________________ >> >> Mactel-linux-users mailing list >> >> Mac...@li... >> >> https://lists.sourceforge.net/lists/listinfo/mactel-linux-users >> > >> > ------------------------------------------------------------------------- >> > Check out the new SourceForge.net Marketplace. >> > It's the best place to buy or sell services for >> > just about anything Open Source. >> > http://sourceforge.net/services/buy/index.php >> > _______________________________________________ >> > Mactel-linux-users mailing list >> > Mac...@li... >> > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users >> > >> >> Hmm sounds like a bug, check /var/log/daemon.log to see if pommed is >> complaining(probably not) but to just see. >> If pommed is running fine try and save dmesg of the error and file a >> report: http://bugzilla.kernel.org/ >> Also keep in mind you did apply the patches, so maybe try a fresh >> kernel. just to see. >> regards; >> > > Hello; Just make sure this occurs with a fresh kernel, with no patches applied, before filing a bug report. regards; -- Justin P. Mattock |
55 messages has been excluded from this view by a project administrator.
