Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 28 Sep 2016, 01:22
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
FatDog64 on early 2012 MacBook Pro, issues
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 4 [52 Posts]   Goto page: 1, 2, 3, 4 Next
Author Message
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Wed 16 Sep 2015, 10:02    Post subject:  FatDog64 on early 2012 MacBook Pro, issues  

It has generally been my experience that Puppy has just worked when I used it to live boot a system and do some troubleshooting. Recently my friends MacBook Pro 2012 suffered a hard drive failure. We are not in a position to buy a new drive for a month or two, so I figured Puppy would work as an excellent stand in. Due to EFI I ended up using FatDog64, but I will readily use any distro that is better suited to the task. slackPup and ubuntuPup both worked on the laptop before the internal drive failed completely, but they must have been relying on some kind of chain booting because now those discs fail with a message about inserting a boot disk and pressing a key.

FatDog boots up great, wireless is working, most of the keys are working, the touchpad is working, but there are a few problems.

Is it appropriate to list them all here in this thread?

The first major problem is that the system (which is physically clean) is overheating. I'm not noticing the fans running, though they are surprisingly quiet on this device. I was given notice at shutdown that the temperature on all four processors had exceeded a threshold and the processor had been throttled 16 times. This notice was after my friend used the system and left it running over night, but it gets quite hot in under an hour despite not displaying that message again. I'm hesitant to proceed using the system until i have a solution or at least a plan.

Thank you for your consideration.

edit: FatDog64 701 on a DVD-R multisession
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2882
Location: The Blue Marble

PostPosted: Wed 16 Sep 2015, 11:02    Post subject:  

Run "htop" to view what is eating your CPU cycles. I don't own a Mac. Ted Dog does, he runs Fatdog in Macs. PM him for help (or perhaps he sees this thread and jumps in to help).
_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Wed 16 Sep 2015, 12:01    Post subject: htop, overheating MacBook Pro, FatDog64 701  

Thank you,

Basically nothing, my suspicion is that it is related to the fans which I could feel blowing during bootup until exactly the point when X/Openbox/Razor/x loaded. Now they are running much less aggressively, and I'm going to shut this down again as it has really heated u n the time it took to get the htop and compose this.

(I'm actually a bit confused about what the graphical environment is, I gathered from reading around that it has changed from JWM + Lxpanel to Openbox + Razor(QT?)

[1]+ Stopped(SIGSTOP) htop 0.0%] Tasks: 48, 43 thr; 1 running
# MM tM#tM XG#XG CD#CD tG#tG "$#"$ !"#!""wL#wL
3 [|| 2.4%] Uptime: 00:19:44
4 [| 0.5%]
Mem[|||||||||||| 385/7892MB]
Swp[ 0/0MB]

PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
594 root 19 -1 248M 40792 24580 S 0.9 0.5 0:25.28 X -bs -nolisten tcp
867 root 20 0 111M 12056 10708 S 0.5 0.1 0:02.01 /etc/xdg/Startup/glipper-lite
800 root 20 0 528M 29252 22008 S 0.0 0.4 0:04.50 razor-panel
1122 root 20 0 12576 3112 2092 R 0.0 0.0 0:03.78 htop
889 root 20 0 195M 15360 13452 S 0.0 0.2 0:00.30 sit /tmp/freememapplet.root.6b6bc05d/icon.svg /tmp/freememapplet.root.6b6bc05
1187 spot 20 0 896M 254M 68836 S 0.0 3.2 0:03.25 /usr/bin/seamonkey
1176 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.26 /usr/bin/seamonkey
1181 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.23 /usr/bin/seamonkey
743 root 21 1 12920 1048 900 S 0.0 0.0 0:00.02 wpa_cli -a dhcpcd-wpagui
1178 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.34 /usr/bin/seamonkey
1175 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.31 /usr/bin/seamonkey
1120 root 20 0 71112 7912 6216 S 0.0 0.1 0:00.53 /usr/bin/urxvt
1184 spot 20 0 896M 254M 68836 S 0.0 3.2 0:01.18 /usr/bin/seamonkey
1177 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.32 /usr/bin/seamonkey
740 root 20 0 126M 13276 9612 S 0.0 0.2 0:00.51 openbox
1182 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.26 /usr/bin/seamonkey
862 root 20 0 372 188 72 S 0.0 0.0 0:00.08 /bin/dash /usr/sbin/freemem.sh
1179 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.24 /usr/bin/seamonkey
1186 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.38 /usr/bin/seamonkey
1207 spot 20 0 10736 1972 1808 S 0.0 0.0 0:00.19 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
1180 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.25 /usr/bin/seamonkey
1209 spot 20 0 42804 4324 3844 S 0.0 0.1 0:00.17 /usr/libexec/gconfd-2
1213 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.07 /usr/bin/seamonkey
1192 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.08 /usr/bin/seamonkey
1219 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.05 /usr/bin/seamonkey
1220 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.02 /usr/bin/seamonkey
1870 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.02 /usr/bin/seamonkey
440 root 20 0 4012 1472 1328 S 0.0 0.0 0:00.14 /usr/sbin/acpid -p /var/run/acpid.pid
727 root 19 -1 248M 40792 24580 S 0.0 0.5 0:00.01 X -bs -nolisten tcp
1857 root 20 0 70364 7568 5956 S 0.0 0.1 0:00.04 /usr/bin/urxvt
1078 root 20 0 123M 18912 16320 S 0.0 0.2 0:00.17 wpa_gui -t
871 root 20 0 119M 13856 12300 S 0.0 0.2 0:00.15 /etc/xdg/Startup/sven
916 root 20 0 195M 15360 13452 S 0.0 0.2 0:00.02 sit /tmp/freememapplet.root.6b6bc05d/icon.svg /tmp/freememapplet.root.6b6bc05
741 root 20 0 29404 2884 2324 S 0.0 0.0 0:00.04 wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -B
1210 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.02 /usr/bin/seamonkey
1183 spot 20 0 896M 254M 68836 S 0.0 3.2 0:00.01 /usr/bin/seamonkey
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2882
Location: The Blue Marble

PostPosted: Wed 16 Sep 2015, 19:04    Post subject:  

Je55eah, try installing "mbpfan" package from the repo. That package is supposed to control the fans, but as said above I don't own a Mac, so I can't test.

And yes, Fatdog has always been openbox. We used to use lxpanel but have moved to razor-panel now.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
Ted Dog


Joined: 13 Sep 2005
Posts: 4010
Location: Heart of Texas

PostPosted: Wed 16 Sep 2015, 20:26    Post subject:  

Who called for the Mac Dog??? lol, I haven't had an issue with mine but I do run my MiniMac 2011 with video drivers from manufacturer (Nvidia) to get the cooling and playback speed under control, That is main use ( Netflix and Amazon video using chrome ) I have no idea why the default browser seems to self breed and bog down machine like both ours does. use Chrome and see if you have less problems.
I am curious that your HD died and you have an overheating issue, That reminds me of a Mac Recall. Did it run hot before HD died. Is it really dead hdparm sda or use gparted. Question
Back to top
View user's profile Send private message 
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Wed 16 Sep 2015, 20:43    Post subject: continued  

I'm a bit embarrassed for missing that package. It looks promising.

This brings up the next issue. Actually two issues related by their potential to help me but otherwise unrelated.

I am running off of a DVD-R. The first two multisessions were saved successfully, but subsequent saves failed. How should I troubleshoot this. I have seen conflicting information in the documentation, often on the same page, about if DVD-R is untested, supported, or actually recommended.

I would have actually preferred to set things up on a SDHC card then possibly transfer everything to a DVD. Unfortunately, my 8GB Toshiba SDHC card cannot be written to. It is accessible from my windows system, but in the MacBook it doesn't show up unless I insert it then slightly retract it. At that point it loads but the drive/partition is flagged read only. I had similar problems with a smaller SD card which did not need to be retracted slightly but also showed up as read only. After some Googling I learned about the retract slightly solution and also about a quirky solution to the read only issue that involved setting the switch 3/4 toward unlocked. Since these cards function normally in my cameras and other computers my guess is that this is an issue of Apple using cheap and imprecise hardware. If there is a known solution I am interested.

I did install mbpfan using Gslapt. I read that Gslapt is capable of dependency resolution, but I was not sure if it is thus configured on FatDog. Is it?

Nonetheless, I verified that the applesmc and coretemp modules are present. How do I verify that they are functioning? Moreover, I ran /usr/sbin/mbpfan as described here. https://ineed.coffee/projects/mbpfan/

The test output stated:

min_fan_speed value is not 6200
Tests run : 6

I'm not sure what to make of this.

A third issue for this post, my razor tray is not displaying the temperature monitor or the battery monitor.

Thanks again.

Thanks for joing the discussion Ted dog. I am not sure about the computer's heat history since it is not mine and the owner is not one to concern herself with those details...

I'll address the hard drive question in the next reply.

Should I uninstall SeaMonkey? I know this would not save space on the disk, but the goal is to make a usable system for my friend.

What is the video driver called?
Back to top
View user's profile Send private message 
Ted Dog


Joined: 13 Sep 2005
Posts: 4010
Location: Heart of Texas

PostPosted: Wed 16 Sep 2015, 21:45    Post subject:  

<cough> multi-session bug in 701 </cough> use v700, many of us use multisession and like it however the main developer does not. The best supported method is with external flash or USB harddrive and a savefile or save folder on a linux type filesystem.
Its easy to setup a mac boot flashdrive , *if your mac is not locked down*

1) get a run of the mill flashdrive ( without any existing bootloaders ) factory fresh is best, under 32G so you will not have exFAT headaches.
2) copy efi.img from DVD to /tmp, change to EFI.2fs, click on it.. drag and drop the EFI folder into flashdrive.


Code:

menuentry "Start Fatdog64-700.iso simple" {
loopback loop0  /Fatdog64-700.iso
linux (loop0)/vmlinuz waitdev=4
initrd (loop0)/initrd
}




I already have a zip file search for EFI4Grub and be careful its uploaded to a free but 'iffy' site.

Sorry if this is not making sense, had an accident [ people! make sure they thighten your lugnuts ] its bad if you see your tire pass you on the road and the backend is throwing sparks, Dr. says I was having a stroke Embarassed due to stress. There are two roads out of town one is 75mph other is 35, I am alive so you know which I must have taken.
Back to top
View user's profile Send private message 
Ted Dog


Joined: 13 Sep 2005
Posts: 4010
Location: Heart of Texas

PostPosted: Wed 16 Sep 2015, 22:09    Post subject:  

O also works with SDcard, which I prefer on my MiniMac since it doesn't take a USB slot and doesn't stick out. If you could backup whatever is on the card, and have your windows reformat it to fat32 then it will be read write again, both linux and MacOS are picky about corruption and Macs seem to 'corrupt' stuff for whatever reason more, even if it was running a great linux. the waitdev=4 shown above will help.
You can force it to multi-session back to DVD even if it did not boot from it, will test this out and give you the settings. Which is great.

I do not know which video hardware you have, select the multicolored star icon on the bottom task bar [right of file cabinet icon] it will popup the Control Panel, tab System and scroll to the bottom for the tool called System information and bookmarks
Summary will give you your display hardware, also down a bit under Devices, Sensors will give you the Temperature at many points. This is a good program to keep running when having issues.
Back to top
View user's profile Send private message 
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Wed 16 Sep 2015, 23:17    Post subject: data dump  

Thanks for the tips. I'll try formatting the SDHC card again and start over with v700

Regarding the internal hard drive, I am pretty sure it is done, but if someone else knows how to fix it that would be awesome. Some of the indicators from the drive are good, but there are also a lot of bad signs including explicit errors from clonezilla, much less informative errors from apples disk utility, and various errors from gparted, gdisk, and others.

Problems began with major slowdowns and spinning color wheels. Mac OS got to a point that my friend could no longer login. I used slackoPup to recover her files then fought with apples restore and disk utility for way too long getting mixed results after painful waits. At one point I though that everything was fine. I had OSX reinstalled and upgraded and it was running well. Perhaps I should have stopped there, but I proceeded to make and test offline installes for OSX 10.7, 10.9, and 10.10 then I attempted to bootcamp Windows with a mind to push further and create a (discouraged) triple boot with Linux, Windows, and Mac. The windows installer worked great compared to the multi-hour long ordeals that Apple's OS installation had been putting me through. but Apple's bootcamp utility gave me the wrong drivers. I downloaded the proper drivers from their website and set about trying again, but the Mac system was starting to get buggy again and I could no longer get it to reinstall.

I removed the drive and tested it with a USB adapter but it would not even show up so I suspect the adapter did not support SATA3.


-PCI Devices-
Host bridge : Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
PCI bridge : Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])
VGA compatible controller : Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
USB controller : Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI])
Communication controller : Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
USB controller : Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
Audio device : Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
PCI bridge : Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) (prog-if 00 [Normal decode])
USB controller : Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
ISA bridge : Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
SATA controller : Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
SMBus : Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
Ethernet controller : Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10)
SD Host controller : Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10) (prog-if 01)
Network controller : Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)
FireWire (IEEE 1394) : LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 0Cool (prog-if 10 [OHCI])
PCI bridge : Intel Corporation Device 1513 (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation Device 1513 (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation Device 1513 (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation Device 1513 (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation Device 1513 (prog-if 00 [Normal decode])
PCI bridge : Intel Corporation Device 1513 (prog-if 00 [Normal decode])
System peripheral : Intel Corporation Device 1513


-Cooling Fans-
fan1 (applesmc) : 2015RPM
-Temperature-
temp1 (applesmc) : 45.25°C
temp2 (applesmc) : 36.00°C
temp3 (applesmc) : 36.00°C
temp4 (applesmc) : 35.50°C
temp5 (applesmc) : 65.25°C
temp6 (applesmc) : 66.75°C
temp7 (applesmc) : 1.25°C
temp8 (applesmc) : 57.25°C
temp9 (applesmc) : 66.00°C
temp10 (applesmc) : 66.00°C
temp11 (applesmc) : 62.00°C
temp12 (applesmc) : 64.00°C
temp13 (applesmc) : 0.00°C
temp14 (applesmc) : 66.25°C
temp15 (applesmc) : 66.75°C
temp16 (applesmc) : 42.75°C
temp17 (applesmc) : 53.50°C
temp18 (applesmc) : 77.00°C
temp19 (applesmc) : 50.25°C
temp20 (applesmc) : 34.50°C
temp21 (applesmc) : 43.25°C
temp1 (coretemp) : 67.00°C
temp2 (coretemp) : 67.00°C
temp3 (coretemp) : 66.00°C
-ACPI Thermal Zone (sysfs)-
thermal_zone0 : 36.20°C
thermal_zone1 : 67.00°C

mbpfan.conf
----------------
[general]
min_fan_speed = 2000 # default is 2000
max_fan_speed = 6200 # default is 6200
low_temp = 63 # try ranges 55-63, default is 63
high_temp = 66 # try ranges 58-66, default is 66
max_temp = 86 # do not set it > 90, default is 86
polling_interval = 7 # default is 7



# hdparm -Tt /dev/sda

/dev/sda:
Timing cached reads: 20984 MB in 2.00 seconds = 10499.57 MB/sec
Timing buffered disk reads: 286 MB in 3.02 seconds = 94.72 MB/sec




The upshot is that I managed to fix her touchpad which had not been working for more than a year by adjusting a screw. This was an operation that she had been reluctant/unwilling to attempt before, being resigned to the use of a wireless keyboard/touchpad that I loaned her. Probably TMI, but that is kind of the theme of this post.
smart.txt.png
Description  smartctl -x
png

 Download 
Filename  smart.txt.png 
Filesize  27.97 KB 
Downloaded  67 Time(s) 
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2749

PostPosted: Thu 17 Sep 2015, 00:11    Post subject:  

I believe that you may have hit a known issue with kworker, that overloads CPU.
Just type
Code:
grep . -r /sys/firmware/acpi/interrupts/
and see which interrupts give a high number.
Then add this line(s) in /etc/rc.d/rc.local
Code:
echo "disable" > /sys/firmware/acpi/interrupts/gpe<NUMBER>
in my retina with FD701 was gpe17 and gpe06.
The macbook should cool down since FD is hardly loading these CPUs

_________________
Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Very Happy
Back to top
View user's profile Send private message 
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Thu 17 Sep 2015, 00:20    Post subject: gpe17  

Thank you.

If this works, how do I make the change permanent? Also, where did you learn about this? It would be good to know how to resolve these things.

# grep . -r /sys/firmware/acpi/interrupts/
/sys/firmware/acpi/interrupts/sci: 18615
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe00: 0 invalid
/sys/firmware/acpi/interrupts/gpe01: 0 invalid
/sys/firmware/acpi/interrupts/gpe02: 0 invalid
/sys/firmware/acpi/interrupts/gpe03: 0 invalid
/sys/firmware/acpi/interrupts/gpe04: 0 invalid
/sys/firmware/acpi/interrupts/gpe05: 0 invalid
/sys/firmware/acpi/interrupts/gpe06: 0 invalid
/sys/firmware/acpi/interrupts/gpe07: 0 enabled
/sys/firmware/acpi/interrupts/gpe08: 0 invalid
/sys/firmware/acpi/interrupts/gpe09: 0 disabled
/sys/firmware/acpi/interrupts/gpe10: 0 invalid
/sys/firmware/acpi/interrupts/gpe11: 0 enabled
/sys/firmware/acpi/interrupts/gpe12: 0 invalid
/sys/firmware/acpi/interrupts/gpe13: 0 enabled
/sys/firmware/acpi/interrupts/gpe14: 0 invalid
/sys/firmware/acpi/interrupts/gpe15: 0 enabled
/sys/firmware/acpi/interrupts/gpe16: 0 disabled
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid
/sys/firmware/acpi/interrupts/gpe17: 18615 enabled
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid
/sys/firmware/acpi/interrupts/gpe18: 0 invalid
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid
/sys/firmware/acpi/interrupts/gpe19: 0 invalid
/sys/firmware/acpi/interrupts/gpe0D: 0 disabled
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid
/sys/firmware/acpi/interrupts/gpe20: 0 invalid
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid
/sys/firmware/acpi/interrupts/gpe21: 0 invalid
/sys/firmware/acpi/interrupts/gpe22: 0 invalid
/sys/firmware/acpi/interrupts/gpe23: 0 enabled
/sys/firmware/acpi/interrupts/gpe24: 0 invalid
/sys/firmware/acpi/interrupts/gpe25: 0 invalid
/sys/firmware/acpi/interrupts/gpe26: 0 invalid
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid
/sys/firmware/acpi/interrupts/gpe27: 0 invalid
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid
/sys/firmware/acpi/interrupts/gpe28: 0 invalid
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid
/sys/firmware/acpi/interrupts/gpe29: 0 invalid
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid
/sys/firmware/acpi/interrupts/gpe1E: 0 disabled
/sys/firmware/acpi/interrupts/gpe30: 0 invalid
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid
/sys/firmware/acpi/interrupts/gpe31: 0 invalid
/sys/firmware/acpi/interrupts/gpe32: 0 invalid
/sys/firmware/acpi/interrupts/gpe33: 0 invalid
/sys/firmware/acpi/interrupts/gpe34: 0 invalid
/sys/firmware/acpi/interrupts/gpe35: 0 invalid
/sys/firmware/acpi/interrupts/gpe36: 0 invalid
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid
/sys/firmware/acpi/interrupts/gpe37: 0 invalid
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid
/sys/firmware/acpi/interrupts/gpe38: 0 invalid
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid
/sys/firmware/acpi/interrupts/gpe39: 0 invalid
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled
/sys/firmware/acpi/interrupts/gpe_all: 18615
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid
# echo "disable" > /sys/firmware/acpi/interrupts/gpe17
#
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2749

PostPosted: Thu 17 Sep 2015, 00:40    Post subject:  

As I said:
Quote:
add this line(s) in /etc/rc.d/rc.local
Wink
ie
Code:
echo "disable" > /sys/firmware/acpi/interrupts/gpe17
in your case.
Be advised that this interrupt may restart after a suspend/resume cycle and a more complex solution may be needed.
Regarding "knowing about these", google is your friend Surprised

BTW if the MacBook HD is not physically damagged, I strongly recommend DiskWarrior.

BTW2 if you have more that 1 savefiles you may run in trouble since the keyboard driver may not be built in the kernel (this is the case with my MacBook Pro) so you have no way to choose. (James, you may want to put a timeout in the init and default to "no savefile" for cases like these)

_________________
Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Very Happy
Back to top
View user's profile Send private message 
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Thu 17 Sep 2015, 02:03    Post subject: continued  

Mavrothal,

You did say that. My mistake. Regarding the same command, should it have taken effect as I ran it? Some time has passed now and the system has not cooled. I have not yet restarted because I am waiting for smartctl to finish but it seems to be stuck at 10% remaining. Moreover the change will not be retained across reboot until I get save files working again.

On that note, I have reformatted that SDHC card and it does indeed show up in FatDog64 on the MacBook Pro. Thank you Ted Dog. I'm going to set up the USB with v700 now, but I was not sure what you were referring to about efi4grub. Would not FatDog work from the USB? Perhaps I should format the USB with GPT? That was my plan before this point.

Getting back to the internal hard drive. Since it has been called into question whether or not the disk is forfeit, does anyone have any insight into the issue?

Thanks all,
Back to top
View user's profile Send private message 
Ted Dog


Joined: 13 Sep 2005
Posts: 4010
Location: Heart of Texas

PostPosted: Thu 17 Sep 2015, 02:22    Post subject:  

no need to format ???? actually not sure which you are talking. If you want to boot the sdcard leave it as fat32 and do one of three things. copy the EFI folder found in the efi,img on the DVD to the sdcard, that causes the fat32 to be bootible by MAC (and win8/10) copy the config and files from DVD to fat32 that will make it boot like the DVD but faster and able to make changes to grub.cfg file which can't be done on DVD since its read only.
Second if that is too much work I made a windows8/10 zip file that is unzipped and copied to fat32 sdcard for less work and confusion.
Third is a hybrid mode that can mostly work (some macOS version do not boot ) that you just dd the iso to the sdcard. but its way too easy to do something wrong and overwrite ANY other media, so not recommended we do not call dd DISK DESTROYER for just a joke.
Back to top
View user's profile Send private message 
Je55eah

Joined: 16 Sep 2015
Posts: 28

PostPosted: Thu 17 Sep 2015, 02:42    Post subject:  

okay, I'll stop that test and shut it down. That sounds great because I've been cycling ice packs and I'm getting pretty weary.

As I understand it my options for installation are:

1. dd the iso to the SDHC card and then resize the partition as described here http://distro.ibiblio.org/fatdog/web/faqs/uefi-flashdrive.html

2. Copy efi.img from DVD to /tmp. Rename it to EFI.2fs. Open it. Copy the EFI folder from the efi.img into the SDHC card. Copy the config and files from DVD to SDHC card. Are these files from the live disk I have been using meant to preserve my settings? Which ones?

3. My thought was that the Mac seems to be unable to boot from CD, DVD, or USB in its current state that I should format the SDHC card with GPT then do the second option.

Finally, modify GRUB2 to taste.

I'm off to bed. Thank you everyone. I'll be checking back again tomorrow hopefully with v700 running from the SDHC card and ready to save changes.

Good night

Last edited by Je55eah on Thu 17 Sep 2015, 02:54; edited 1 time in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 4 [52 Posts]   Goto page: 1, 2, 3, 4 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0965s ][ Queries: 12 (0.0084s) ][ GZIP on ]