Re: Macintosh Quadra 950 Not Booting
Hi, If your kernel is bigger than 8 MB, you need a kernel with commit: commit 486df8bc4627bdfc032d11bedcd056cc5343ee62 m68k: Increase initial mapping to 8 or 16 MiB if possible If your RAM is not at 0 address, you need also: commit f1a1b63529986d0c8970da182f0935eae059421b m68k: Fix boot regression on machines with RAM at non-zero Both commits are in kernel 3.16 and later. To help to debug, what is the last letter displayed by the kernel before crash ? (did you set CONFIG_EARLY_PRINTK ?) Laurent Le 07/08/2015 06:29, Greg Andrzejewski a écrit : > Greetings, > > After finally getting my Mac SE/30 working again, I set about trying to > get a modern version of Linux installed on the little fellow. Early > experiments with 3.14 kernels were successful and when a trio of Quadra > 950s appeared on the local craigslist, I picked them up, looking forward > to a more powerful 68k machine. Problem is I can't get any recent kernel > to boot. > > I've tried using Penguin-19 on MacOS 7.1 and 7.5.3 with identical > results; the machine just hangs on the "Bootling Linux" message. The > screen never clears, nothing even comes across the serial port with > earlyprintk. I installed MacsBug in hopes of finding something useful in > __log_buf on reboot, but the entire buffer is empty (zeros). I'd suspect > the bootloader is at fault, but Penguin successfully boots a 4.0.0 > kernel on my SE/30. Penguin log is attached, in case anyone's interested. > > Still not 100% confident in Penguin, I tried booting with an EMILE > rescue disk. EMILE reads the kernel from disk and shortly thereafter the > chimes of death play (). Is this something the kernel can > intentionally do or is it more likely sort sort of triple fault-like > situation? > > I've done a touch of kernel debugging, but this was on x86 and never > this early in the boot process. What next steps can I take to further > debug this issue? I've glanced at the early arch code, but all I really > got out of it was a few chuckles from the comments venting about > Apple's, uh, peculiar hardware design. > > Thanks, > Greg -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55c4739c.3060...@vivier.eu
Re: Macintosh Quadra 950 Not Booting
Le 07/08/2015 07:43, Finn Thain a écrit : > > On Thu, 6 Aug 2015, Greg Andrzejewski wrote: >> Still not 100% confident in Penguin, I tried booting with an EMILE >> rescue disk. EMILE reads the kernel from disk and shortly thereafter the >> chimes of death play (). Is this something the kernel can >> intentionally do or is it more likely sort sort of triple fault-like >> situation? > > I've never tried EMILE on my Q950. Perhaps Laurent can speak to that. I don't own a Q950, so I've never tested it. Do you have enough RAM ? Laurent -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55c47572.5000...@vivier.eu
Bug#780430: qtwebkit-opensource-src: port to m68k
Source: qtwebkit-opensource-src Version: 5.4.2+dfsg-2 Followup-For: Bug #780430 Hi Lisandro, please remember submitters don’t get bugmail… or ping them ;) Anyway, here you are: >- We need the original author of the patches. The patches were written by myself. >- We need the original author to either: > - Publicly state that the patches are under a permisive license like BSD. Please feel free to choose any OSI-approved licence for them. Although they are probably trivial and thus not copyright-protected. Thanks for pushing it upstream and merging it! -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150807135544.12474.9014.report...@tglase.lan.tarent.de
Re: Log for attempted build of afflib_3.7.6-4 on m68k (dist=unstable)
Hi, Thanks for your message. I need two days to see the results in all archs and fix the issues. So, I will work over all issues up to Sunday or Monday. Regards, Eriberto 2015-08-07 10:53 GMT-03:00 Thorsten Glaser : > fail > > symbols file differs -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap+dxjevsjbcpy_31rmw64com1d41prfpvp3jymb5un6uyj...@mail.gmail.com
Re: Macintosh Quadra 950 Not Booting
On 8/7/15, Laurent Vivier wrote: > Hi, > > If your kernel is bigger than 8 MB, you need a kernel with commit: > > commit 486df8bc4627bdfc032d11bedcd056cc5343ee62 > > m68k: Increase initial mapping to 8 or 16 MiB if possible > > If your RAM is not at 0 address, you need also: > > commit f1a1b63529986d0c8970da182f0935eae059421b > > m68k: Fix boot regression on machines with RAM at non-zero > > Both commits are in kernel 3.16 and later. > > To help to debug, what is the last letter displayed by the kernel before > crash ? > (did you set CONFIG_EARLY_PRINTK ?) > > Laurent > That's the problem I'm having. CONFIG_EARLY_PRINTK is set, earlyprintk passed on the command line, but I get nothing on screen, nothing over the serial port, and nothing in the log buffer. Same kernel image boots on my SE/30. I'm using kernel 4.0 and decompressed image size is 3.5 MB, so I don't think I'm running into either of those two issues. Unless... don't macs shadow the ROM at physical address 0 on powerup? Could this be triggering as part of the shutdown of MacOS? -Greg > Le 07/08/2015 06:29, Greg Andrzejewski a écrit : >> Greetings, >> >> After finally getting my Mac SE/30 working again, I set about trying to >> get a modern version of Linux installed on the little fellow. Early >> experiments with 3.14 kernels were successful and when a trio of Quadra >> 950s appeared on the local craigslist, I picked them up, looking forward >> to a more powerful 68k machine. Problem is I can't get any recent kernel >> to boot. >> >> I've tried using Penguin-19 on MacOS 7.1 and 7.5.3 with identical >> results; the machine just hangs on the "Bootling Linux" message. The >> screen never clears, nothing even comes across the serial port with >> earlyprintk. I installed MacsBug in hopes of finding something useful in >> __log_buf on reboot, but the entire buffer is empty (zeros). I'd suspect >> the bootloader is at fault, but Penguin successfully boots a 4.0.0 >> kernel on my SE/30. Penguin log is attached, in case anyone's interested. >> >> Still not 100% confident in Penguin, I tried booting with an EMILE >> rescue disk. EMILE reads the kernel from disk and shortly thereafter the >> chimes of death play (). Is this something the kernel can >> intentionally do or is it more likely sort sort of triple fault-like >> situation? >> >> I've done a touch of kernel debugging, but this was on x86 and never >> this early in the boot process. What next steps can I take to further >> debug this issue? I've glanced at the early arch code, but all I really >> got out of it was a few chuckles from the comments venting about >> Apple's, uh, peculiar hardware design. >> >> Thanks, >> Greg > -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cabnbs13ppuwjafzzmfa-5c+quqryo_gcftdhz1_sywj4g31...@mail.gmail.com
Fwd: Macintosh Quadra 950 Not Booting
On Fri, Aug 7, 2015 at 12:43 AM, Finn Thain wrote: > > On Thu, 6 Aug 2015, Greg Andrzejewski wrote: > > > Greetings, > > > > After finally getting my Mac SE/30 working again, I set about trying to > > get a modern version of Linux installed on the little fellow. Early > > experiments with 3.14 kernels were successful > > BTW, are you using mac_scsi on the SE/30? > I've just been grabbing kernel images from the Debian ports archive, so I think so. 3.14 kernels would panic with a bus error on bootup unless I disabled pseudo DMA, but I'm thinking that might be a hardware issue with my machine. I had to solder a few jumper wires on the motherboard to repair damage from leaking capacitors around the video/audio circuitry. Never really had any problems with SCSI in MacOS, but I cleaned a lot of capacitor goo from around the NCR chip, so sometimes I wonder. Linux gets very upset if I have anything attached to the external SCSI port and MacOS bombed out yesterday copying files to a zip disk, so it's probably something I'm going to need to address in the future. FWIW, the pseudo DMA problems have gone away for me in the 4.0 kernels, by which I mean I no longer have to pass mac5380=-1,-1,-1,-1,0 on the command line. I've been meaning to check if there was a fix or if pseudo DMA is just disabled by default now. > > and when a trio of Quadra 950s appeared on the local craigslist, I > > picked them up, looking forward to a more powerful 68k machine. Problem > > is I can't get any recent kernel to boot. > > I haven't booted a Q950 for some years, but it should work. > > Using Penguin, I did boot Linux 3.1 on a Quadra 700 which is somewhat > similar hardware. The only other report I found on the list about a Q950 > was for Linux 2.6.20. > > If you would like, I can send you a current kernel binary that should boot > any Mac (that is, SE/30 or Quadra 950). > Yeah, that'd be great. I think the most recent kernel I was able to boot was 2.6.29 or something that I found online. > > Also, any debian kernel binary from 3.x or 4.x should give useful results. > (Kernel modules aren't relevant to isolating the cause of an early crash.) > > > > > I've tried using Penguin-19 on MacOS 7.1 and 7.5.3 with identical > > results; the machine just hangs on the "Bootling Linux" message. The > > screen never clears, nothing even comes across the serial port with > > earlyprintk. > > Penguin has a known bug in its zlib code that can cause kernel > decompression to fail like that. Is this a large debian kernel binary? > > I suggest you try booting the vmlinux, e.g. > # gzip -dc < vmlinuz > vmlinux > I use Penguin with MacOS 7.5.3 without any issues; however, you might want > to try with extensions disabled (hold down when you hear the > chime) to avoid a possible unhandled slot interrupt during early boot. > Just tried with decompressed kernel from the debian ports repository and extensions disabled. Same behavior :-( > I installed MacsBug in hopes of finding something useful in __log_buf on > > reboot, but the entire buffer is empty (zeros). I'd suspect the > > bootloader is at fault, but Penguin successfully boots a 4.0.0 kernel on > > my SE/30. Penguin log is attached, in case anyone's interested. > > I don't know anything about __log_buf. I suspect you'd need to avoid the > POST memory test for that to work. > Yeah, I was concerned about that, too. I think the best you can do to preserve memory contents is to hold down at the happy mac, which invokes MacsBug at its earliest convenience. Other variables in the neighborhood seem to have survived (log_buf and log_buf_len both have correct values). Maybe I could try initializing the buffer with some pattern and seeing if that survives a reboot. > > > > > Still not 100% confident in Penguin, I tried booting with an EMILE > > rescue disk. EMILE reads the kernel from disk and shortly thereafter the > > chimes of death play (). Is this something the kernel can > > intentionally do or is it more likely sort sort of triple fault-like > > situation? > > I've never tried EMILE on my Q950. Perhaps Laurent can speak to that. > The highlighting showing the current selection in the boot menu doesn't display. Other than that, the rescue floppy seemed to work okay. > > > > > I've done a touch of kernel debugging, but this was on x86 and never > > this early in the boot process. What next steps can I take to further > > debug this issue? > > The first thing you should see is the output from the early boot code: > "ABCFGHIJK". If you don't see that then likely causes are an unhandled > early interrupt or bootloader bug. > > However, it is also possible that a recent commit has messed up the OSS > driver: > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/m68k/mac?id=b24f670b7f5b2058b95370caa9f104b3cefb9f1d > But this first appeared in v4.1, so it probably isn't relevant. > > > I've glanced at the early arch code, but all I really got out of it was > > a fe
Re: Fwd: Macintosh Quadra 950 Not Booting
On Fri, 7 Aug 2015, Greg Andrzejewski wrote: > On Fri, Aug 7, 2015 at 12:43 AM, Finn Thain > wrote: > > > > > On Thu, 6 Aug 2015, Greg Andrzejewski wrote: > > > > > Greetings, > > > > > > After finally getting my Mac SE/30 working again, I set about trying > > > to get a modern version of Linux installed on the little fellow. > > > Early experiments with 3.14 kernels were successful > > > > BTW, are you using mac_scsi on the SE/30? > > > > I've just been grabbing kernel images from the Debian ports archive, so > I think so. If convenient sometime, can you send me the dmesg output (or /var/log/kern.log) from your SE/30? > 3.14 kernels would panic with a bus error on bootup unless I disabled > pseudo DMA, but I'm thinking that might be a hardware issue with my > machine. Probably not a hardware issue -- mac_scsi always did that. > I had to solder a few jumper wires on the motherboard to repair damage > from leaking capacitors around the video/audio circuitry. Never really > had any problems with SCSI in MacOS, but I cleaned a lot of capacitor > goo from around the NCR chip, so sometimes I wonder. Linux gets very > upset if I have anything attached to the external SCSI port Also likely to be a mac_scsi issue if MacOS works OK with that setup. > and MacOS bombed out yesterday copying files to a zip disk, so it's > probably something I'm going to need to address in the future. > > FWIW, the pseudo DMA problems have gone away for me in the 4.0 kernels, > by which I mean I no longer have to pass mac5380=-1,-1,-1,-1,0 on the > command line. I've been meaning to check if there was a fix or if pseudo > DMA is just disabled by default now. Right. I disabled PDMA by default as part of a patch that went into v3.19 because I've never seen it work properly on any Mac. (Some LC and Classic models will need v4.0 or later because of commit 2e874d178c9e.) But PIO is horribly slow. I have a bunch of unfinished mac_scsi patches that I hope to return to. The PDMA bug is one that I'd really like to fix. > > If you would like, I can send you a current kernel binary that should > > boot any Mac (that is, SE/30 or Quadra 950). > > > > Yeah, that'd be great. I think the most recent kernel I was able to boot > was 2.6.29 or something that I found online. I've uploaded a kernel binary here, https://www.telegraphics.com.au/~fthain/gregta/vmlinux-4.1.3-mac https://www.telegraphics.com.au/~fthain/gregta/linux-m68k-image-4.1.3-mac.tar.gz SHA1 48b6c18792479a6d9886151c0457675df36b8678 vmlinux-4.1.3-mac 9140852171bdf0a9a5e9b8d0cd28530dca5697eb linux-m68k-image-4.1.3-mac.tar.gz I'm afraid I haven't tested it, and I don't have much reason to believe that it will work better than gunzip'd vmlinuz-4.0.0-2-m68k. The tar file has some modules but you probably won't need them. > > Just tried with decompressed kernel from the debian ports repository and > extensions disabled. Same behavior :-( Well, I was not expecting that. I would double-check the obvious, if you didn't already. That is, check that you selected the right kernel binary and confirm no gunzipping in the log as Penguin boots it. -- -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.LNX.2.00.1508081000460.27748@nippy.intranet
Re: Macintosh Quadra 950 Not Booting
On Fri, 7 Aug 2015, Greg Andrzejewski wrote: > On 8/7/15, Laurent Vivier wrote: > > Hi, > > > > If your kernel is bigger than 8 MB, you need a kernel with commit: > > > > commit 486df8bc4627bdfc032d11bedcd056cc5343ee62 > > > > m68k: Increase initial mapping to 8 or 16 MiB if possible > > > > If your RAM is not at 0 address, you need also: > > > > commit f1a1b63529986d0c8970da182f0935eae059421b > > > > m68k: Fix boot regression on machines with RAM at non-zero > > > > Both commits are in kernel 3.16 and later. > > > > To help to debug, what is the last letter displayed by the kernel before > > crash ? > > (did you set CONFIG_EARLY_PRINTK ?) > > > > Laurent > > > > That's the problem I'm having. CONFIG_EARLY_PRINTK is set, earlyprintk > passed on the command line, but I get nothing on screen, nothing over > the serial port, and nothing in the log buffer. Indeed. The penguin log attached to your original email says, > > > Physical RAM: 40 MB > > > Command line is 'earlyprintk' > > > GUnzipping Small Studio H.D.: greg:vmlinuz-4.0.0-2-m68k > > > .Kernel format: ELF > > > > > > The kernel will be located at physical 0x1000 > > > Kernel at logical address 0x15fabc0 > > > GUnzipping Small Studio H.D.: greg:vmlinuz-4.0.0-2-m68k > > > Read 3246816 bytes > > > for segment 0, requested 3246816 > > > ..Read 144816 bytes for segment 1, requested 144816 > > > > > > Bootstrap's bootinfo version: 2.0 > > > Kernel's bootinfo version : 2.0 > > > Kernel entry physical is 0x2000 > > > Kernel segment 0 at 0x15fabc0, size 3413744 > > > Kernel segment 1 at 0x193cbc0, size 147456 > > > Kernel size is 0x366000 This looks like a Debian ports kernel so it should have the right config. > Same kernel image boots on my SE/30. I seem to recall that the Penguin failure with compressed kernels does not affect 68030 machines... FWIW. > > I'm using kernel 4.0 and decompressed image size is 3.5 MB, so I don't > think I'm running into either of those two issues. Unless... don't macs > shadow the ROM at physical address 0 on powerup? Could this be > triggering as part of the shutdown of MacOS? Unikely. Only triggered by hard reset AFAIK. In anycase, Penguin-19 has been used successfully on MacOS 7.5.3 on a Quadra 950. BTW, I have Penguin logs from my Powerbook 180 that also say "The kernel will be located at physical 0x1000". -- > > -Greg > -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.LNX.2.00.1508080940230.27748@nippy.intranet
Re: Fwd: Macintosh Quadra 950 Not Booting
On Fri, 7 Aug 2015, Greg Andrzejewski wrote: > > Yeah, that'd be great. I think the most recent kernel I was able to boot > was 2.6.29 or something that I found online. Someone suggested (off-list) that you should remove any expansion cards, which is always good advice when troubleshooting an early crash. E.g. Linux doesn't have support for the WGS 95 PDS card fitted to some Quadra 950 machines (unfortunately). But if that was your problem, I'd expect 2.6.29 would not boot either. Where did you find the 2.6.29 kernel binary? If it is a mainline kernel, we may be able to solve this with git bisection. -- -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.LNX.2.00.1508081147450.27748@nippy.intranet
Re: Fwd: Macintosh Quadra 950 Not Booting
On Sat, 8 Aug 2015, I wrote: > > I've uploaded a kernel binary [...] > Here's a more recent one. https://www.telegraphics.com.au/~fthain/gregta/vmlinux-4.1.4-mac https://www.telegraphics.com.au/~fthain/gregta/linux-m68k-image-4.1.4-mac.tar.gz SHA1 dd647dd6383deb7516b5053966757da94df95f35 linux-m68k-image-4.1.4-mac.tar.gz 7d919b2a965076eb3f34b5c69615d6663d85bf29 linux-m68k-image/boot/vmlinux-4.1.4-mac -- -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.LNX.2.00.1508081353290.5273@nippy.intranet
Re: Fwd: Macintosh Quadra 950 Not Booting
On Fri, Aug 7, 2015 at 8:31 PM, Finn Thain wrote: > > On Fri, 7 Aug 2015, Greg Andrzejewski wrote: > > > On Fri, Aug 7, 2015 at 12:43 AM, Finn Thain > > wrote: > > > > > > > > On Thu, 6 Aug 2015, Greg Andrzejewski wrote: > > > > > > > Greetings, > > > > > > > > After finally getting my Mac SE/30 working again, I set about trying > > > > to get a modern version of Linux installed on the little fellow. > > > > Early experiments with 3.14 kernels were successful > > > > > > BTW, are you using mac_scsi on the SE/30? > > > > > > > I've just been grabbing kernel images from the Debian ports archive, so > > I think so. > > If convenient sometime, can you send me the dmesg output (or > /var/log/kern.log) from your SE/30? > Sure, I'll grab it next time it's booted up. > > > 3.14 kernels would panic with a bus error on bootup unless I disabled > > pseudo DMA, but I'm thinking that might be a hardware issue with my > > machine. > > Probably not a hardware issue -- mac_scsi always did that. > Good to know. > > > I had to solder a few jumper wires on the motherboard to repair damage > > from leaking capacitors around the video/audio circuitry. Never really > > had any problems with SCSI in MacOS, but I cleaned a lot of capacitor > > goo from around the NCR chip, so sometimes I wonder. Linux gets very > > upset if I have anything attached to the external SCSI port > > Also likely to be a mac_scsi issue if MacOS works OK with that setup. > > > and MacOS bombed out yesterday copying files to a zip disk, so it's > > probably something I'm going to need to address in the future. > > > > FWIW, the pseudo DMA problems have gone away for me in the 4.0 kernels, > > by which I mean I no longer have to pass mac5380=-1,-1,-1,-1,0 on the > > command line. I've been meaning to check if there was a fix or if pseudo > > DMA is just disabled by default now. > > Right. I disabled PDMA by default as part of a patch that went into v3.19 > because I've never seen it work properly on any Mac. (Some LC and Classic > models will need v4.0 or later because of commit 2e874d178c9e.) > > But PIO is horribly slow. I have a bunch of unfinished mac_scsi patches > that I hope to return to. The PDMA bug is one that I'd really like to fix. > Yeah, the SE/30 needs all the help it can get. It's about 20 minutes from bootup to login prompt. > > > > If you would like, I can send you a current kernel binary that should > > > boot any Mac (that is, SE/30 or Quadra 950). > > > > > > > Yeah, that'd be great. I think the most recent kernel I was able to boot > > was 2.6.29 or something that I found online. > > I've uploaded a kernel binary here, > > https://www.telegraphics.com.au/~fthain/gregta/vmlinux-4.1.3-mac > > https://www.telegraphics.com.au/~fthain/gregta/linux-m68k-image-4.1.3-mac.tar.gz > > SHA1 > 48b6c18792479a6d9886151c0457675df36b8678 vmlinux-4.1.3-mac > 9140852171bdf0a9a5e9b8d0cd28530dca5697eb linux-m68k-image-4.1.3-mac.tar.gz > > I'm afraid I haven't tested it, and I don't have much reason to believe > that it will work better than gunzip'd vmlinuz-4.0.0-2-m68k. The tar file > has some modules but you probably won't need them. > Tried booting both compressed and decompressed kernel images, same behavior with Penguin. Can't say if anything comes across the serial port as I left my cable at work, still hooked to one of the Quadras I've stashed under my desk. I tried the new 4.1 kernel from the ports repository this afternoon, same story with Penguin, but EMILE seems to get a little further. The screen doesn't clear, but no death chimes either. Jumping in to MacsBug on reboot, I found this in __log_buf: Displaying memory from 3240d0 003240D0 004C 003B 0033 .L.;...3 003240E0 4255 473A 2073 6368 6564 756C 696E 6720 BUG: scheduling 003240F0 7768 696C 6520 6174 6F6D 6963 3A20 286E while atomic: (n 00324100 756C 6C29 2F2D 3136 3232 3532 3337 3736 ull)/-1622523776 00324110 2F30 7834 3038 3032 3666 3200 /0x408026f2. 00324120 0022 0012 0014 4D6F 6475 ."..Modu 00324130 6C65 7320 6C69 6E6B 6564 2069 6E3A les linked in:.. 00324140 0058 0048 0034 4350 ...X.H...4CP 00324150 553A 2030 2050 4944 3A20 3133 3232 3638 U: 0 PID: 132268 00324160 3630 3138 2043 6F6D 6D3A 2020 4E6F 7420 6018 Comm: Not 00324170 7461 696E 7465 6420 342E 312E 302D 312D tainted 4.1.0-1- 00324180 6D36 386B 2023 3120 4465 6269 616E 2034 m68k #1 Debian 4 00324190 2E31 2E33 2D31 .1.3-1.. Signs of life! If the scheduler's starting, we're way past the early init stuff, right? Just to be sure, I powered down, verified that region of memory was trashed, and tried booting again. Same message. I was confused at first, because I wasn't seeing all the earlyprintk stuff (ABCDEFG...) in the buffer. Then it dawned on me to check if any of that stuff goes actually through the log buffer or just d
Re: Fwd: Macintosh Quadra 950 Not Booting
On Fri, Aug 7, 2015 at 8:53 PM, Finn Thain wrote: > > Someone suggested (off-list) that you should remove any expansion cards, > which is always good advice when troubleshooting an early crash. > > E.g. Linux doesn't have support for the WGS 95 PDS card fitted to some > Quadra 950 machines (unfortunately). But if that was your problem, I'd > expect 2.6.29 would not boot either. > > Yeah, there's nothing installed in any of the machines. Judging by software left on the drive, the previous owner must have kept the FWB Jackhammer cards. Been meaning to email and inquire as to what his plans are for them. Where did you find the 2.6.29 kernel binary? If it is a mainline kernel, > we may be able to solve this with git bisection. > > -- > https://people.debian.org/~smarenka/d-i/m68k/images/daily/kernels/vmlinuz-2.6.29-2-mac Boot with Penguin to no root filesystem panic. -Greg
Re: Fwd: Macintosh Quadra 950 Not Booting
On Sat, 8 Aug 2015, Greg Andrzejewski wrote: > On Fri, Aug 7, 2015 at 8:53 PM, Finn Thain > wrote: > > > > > Someone suggested (off-list) that you should remove any expansion > > cards, which is always good advice when troubleshooting an early > > crash. > > > > E.g. Linux doesn't have support for the WGS 95 PDS card fitted to some > > Quadra 950 machines (unfortunately). But if that was your problem, I'd > > expect 2.6.29 would not boot either. > > > Yeah, there's nothing installed in any of the machines. Judging by > software left on the drive, the previous owner must have kept the FWB > Jackhammer cards. Been meaning to email and inquire as to what his plans > are for them. OK. > > > Where did you find the 2.6.29 kernel binary? If it is a mainline > > kernel, we may be able to solve this with git bisection. > > > > -- > > > https://people.debian.org/~smarenka/d-i/m68k/images/daily/kernels/vmlinuz-2.6.29-2-mac > Boot with Penguin to no root filesystem panic. Well, I guess we'll have to bisect from there. -- > > -Greg > -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.LNX.2.00.1508081607170.31043@nippy.intranet
Re: Fwd: Macintosh Quadra 950 Not Booting
On Sat, 8 Aug 2015, Greg Andrzejewski wrote:
> Jumping in to MacsBug on reboot, I found this in __log_buf:
>
> Displaying memory from 3240d0
> 003240D0 004C 003B 0033 .L.;...3
> 003240E0 4255 473A 2073 6368 6564 756C 696E 6720 BUG: scheduling
> 003240F0 7768 696C 6520 6174 6F6D 6963 3A20 286E while atomic: (n
> 00324100 756C 6C29 2F2D 3136 3232 3532 3337 3736 ull)/-1622523776
> 00324110 2F30 7834 3038 3032 3666 3200 /0x408026f2.
> 00324120 0022 0012 0014 4D6F 6475 ."..Modu
> 00324130 6C65 7320 6C69 6E6B 6564 2069 6E3A les linked in:..
> 00324140 0058 0048 0034 4350 ...X.H...4CP
> 00324150 553A 2030 2050 4944 3A20 3133 3232 3638 U: 0 PID: 132268
> 00324160 3630 3138 2043 6F6D 6D3A 2020 4E6F 7420 6018 Comm: Not
> 00324170 7461 696E 7465 6420 342E 312E 302D 312D tainted 4.1.0-1-
> 00324180 6D36 386B 2023 3120 4465 6269 616E 2034 m68k #1 Debian 4
> 00324190 2E31 2E33 2D31 .1.3-1..
>
> Signs of life! If the scheduler's starting, we're way past the early
> init stuff, right? Just to be sure, I powered down, verified that region
> of memory was trashed, and tried booting again. Same message.
Nice going!
>
> I was confused at first, because I wasn't seeing all the earlyprintk
> stuff (ABCDEFG...) in the buffer. Then it dawned on me to check if any
> of that stuff goes actually through the log buffer or just directly to
> the console/serial port, and it appears to be the latter. Maybe it needs
> to, but if that were easy/a-good-idea I'd have to imagine it'd be doing
> it already.
I don't know how __log_buf relates to the consoles. Certainly the
"ABCDEFG" is generated before the early console starts. The early console
is normally disabled when tty0 (framebuffer console) or ttyS0 (serial
console) starts up.
If you want to see all kernel messages on the serial console, and then get
a login prompt at the serial console, you need to boot with arguments
"earlyprintk console=tty0 console=ttyS0"
If you want to see all kernel messages on the serial console, but with
login prompt at the framebuffer console, use
"earlyprintk console=ttyS0 console=tty0"
> Guess I could give it a shot, but time's probably better spent figuring
> out what's going on with the display and serial port.
>
I agree. And that reminds me: the Quadra 900 and 950 have an SCC IOP, like
the Mac IIfx. That means you must tell MacOS to switch the serial ports to
IOP-bypass ("compatible") mode. Otherwise the serial port won't work. (I
don't know whether this applies to EMILE.)
There is a control panel for that called Serial Switch, IIRC. That should
get you a working serial console, and a backtrace. I'd be interested to
know whether v3.x kernels also fail with the same BUG splat.
I can't explain why there is no output on the framebuffer. Lots of other
Quadras have a DAFB chip and they generally work OK. Maybe try a different
video mode and/or color depth? Since you have no expansion cards
installed, I don't know what else to try.
--
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/alpine.LNX.2.00.1508081628220.31043@nippy.intranet
