Re: Fwd: Re: Debian on mac68k

On 12/16/2016 11:28 PM, Finn Thain wrote: > I filed the bug report six months ago but got no response. The > 4.8.0-2-m68k package has no improvement. The kernel package has >1000 bug reports, it's sometimes possible Ben misses things. > Perhaps the bug report was ignored because it relates to

Re: Fwd: Re: Debian on mac68k

On Sat, 4 Jun 2016, John Paul Adrian Glaubitz wrote: > > > BTW, I see that the Debian kernel config sets CONFIG_MAC_SCSI=y. As of > > v3.19 you can make that driver modular and save memory on systems that > > don't need it like Atari, Amiga and 68040 Macs. Similarly, > > CONFIG_MAC8390=y can

Mac RTC, was Re: Debian on mac68k (Mac IIfx update)

On Wed, 2 Nov 2016, I wrote: > > For the official Debian release, I would find it helpful to include > > the kernel option that sets the date in the kernel before mounting > > filesystems; at first boot, vmlinux-4.1.35-mac_scsi-egret+ took a long > > time to check all the filesystems

Re: gcc-4.6.3, was Re: Debian on mac68k

On Wed, Nov 9, 2016 at 8:08 AM, Finn Thain wrote: > On Wed, 9 Nov 2016, Michael Schmitz wrote: >> Not for Mac, but Geert usually boots kernels using ARAnyM. Pretty basic, >> for sure, but it's been good enough so have something to work from. > > I thought Geert still

Re: gcc-4.6.3, was Re: Debian on mac68k

On Wed, 9 Nov 2016, Michael Schmitz wrote: > Not for Mac, but Geert usually boots kernels using ARAnyM. Pretty basic, > for sure, but it's been good enough so have something to work from. I thought Geert still used gcc-4.1 (?) > > Having something like ARAnyM for Mac or Amiga would increase

Re: gcc-4.6.3, was Re: Debian on mac68k

Hi Finn, >> so I think there is little incentive to use these old compilers. > > It is useful for upstream developers to have distro-neutral tools. > Ideally, we could use the kernel.org compiler as a "reference compiler". > For automated builds, it seems to be that already. But no-one boots

Re: gcc-4.6.3, was Re: Debian on mac68k

On Tue, 8 Nov 2016, John Paul Adrian Glaubitz wrote: > On 11/08/2016 10:01 AM, Finn Thain wrote: > > The only problem is that my fast Linux host is i686 and your compiler > > runs on x86_64. But it is a convenient way to get hold of a gcc-5.2 > > compiler to target m68k/coldfire. > >

Re: gcc-4.6.3, was Re: Debian on mac68k

On 11/08/2016 10:01 AM, Finn Thain wrote: > The only problem is that my fast Linux host is i686 and your compiler runs > on x86_64. But it is a convenient way to get hold of a gcc-5.2 compiler to > target m68k/coldfire. Installing Debian testing and running apt install

Re: gcc-4.6.3, was Re: Debian on mac68k

On Mon, 7 Nov 2016, Angelo Dureghello wrote: > > I also observed issues with some kernel.org toolchains, at least for > coldfire the 4.9.x was producing some wrong opcode, due to incorrect gcc > libs used over linking. > > Maybe you can try some toolchains i prepared, they are the kernel.org

Re: gcc-4.6.3, was Re: Debian on mac68k

On 11/06/2016 11:22 PM, Finn Thain wrote: >> No, not really. Is there any particular reason why you are using these >> old compilers? > > Mature, proven tools are important to upstream developers. Developers of > distros needn't have the same expectations, since they take it upon > themselves

Re: gcc-4.6.3, was Re: Debian on mac68k

On Sun, 6 Nov 2016, John Paul Adrian Glaubitz wrote: > On 11/06/2016 03:03 AM, Finn Thain wrote: > > > Has anyone else tried the m68k cross-compiler from kernel.org and > > observed strange behaviour from the binaries it produces? > > No, not really. Is there any particular reason why you are

gcc-4.6.3, was Re: Debian on mac68k

Has anyone else tried the m68k cross-compiler from kernel.org and observed strange behaviour from the binaries it produces? I used that cross-compiler (the i686 one) to build the kernel seen booting below. The resulting binary consistently crashes two different systems (LC III and LC 475),

Re: Debian on mac68k (LC III)

On Thu, 3 Nov 2016, Mac User wrote: > > Thanks for the md5fl link; I had been using FTP from NCSA Telnet 2.6 to > transfer files, but one of the kernels didn't transfer properly, so now > I'll know to just use AppleTalk (and verify checksums). For FTP, I get good results from Fetch 3.0.3.

Re: Debian on mac68k (LC III)

On Thu, 3 Nov 2016, Mac User wrote: > On 11/2/16 10:29 PM, Finn Thain wrote: > > > > On Wed, 2 Nov 2016, Mac User wrote: > > > >> On 11/2/16 8:20 PM, Finn Thain wrote: > >> > >> My mistake earlier -- I cut and pasted the hang from "version > >> 4.1.35-mac_scsi+" instead of capturing the

Re: Debian on mac68k (LC III)

On Wed, 2 Nov 2016, Mac User wrote: > On 11/2/16 8:20 PM, Finn Thain wrote: > > My mistake earlier -- I cut and pasted the hang from "version > 4.1.35-mac_scsi+" instead of capturing the result of > "vmlinux-4.1.35-mac_scsi-egret+" on a serial console. > Confusingly, I sent two kernel

Re: Debian on mac68k (LC III)

On Wed, 2 Nov 2016, Mac User wrote: > On 11/2/16 5:42 PM, Finn Thain wrote: > > > > On Wed, 2 Nov 2016, Mac User wrote: > > > >> > >> On the LC III, the new kernel (compressed and uncompressed) hangs > >> consistently at the ABCFGHIJK screen. I tried increasing Penguin's > >> memory to

Re: Debian on mac68k (LC III)

On 11/2/16 5:42 PM, Finn Thain wrote: > > On Wed, 2 Nov 2016, Mac User wrote: > >>> >>> This regression is a bit like another one I'm debugging. I can't explain >>> them except that both appeared when I changed the compiler and the >>> .config. So I've prepared another build. This time, with

Re: Debian on mac68k (LC III)

On Wed, 2 Nov 2016, Mac User wrote: > > > > This regression is a bit like another one I'm debugging. I can't explain > > them except that both appeared when I changed the compiler and the > > .config. So I've prepared another build. This time, with > > CONFIG_CC_OPTIMIZE_FOR_SIZE=y and

Re: Debian on mac68k (Mac IIfx update)

On Wed, 2 Nov 2016, Mac User wrote: > On 11/2/16 12:59 AM, Finn Thain wrote: > > > > Does the output from "hwclock -r" agree with Mac OS on your IIfx? If > > so, you could get your hwclock init script to run "hwclock --hctosys" > > before the fsck and mount scripts execute. > > > > No,

Re: Debian on mac68k (Mac IIfx update)

On Tue, 1 Nov 2016, Mac User wrote: > Update on Mac IIfx... > > My Mac IIfx works with "vmlinux-4.1.35-mac_scsi-egret+" using my Debian > 3.1 filesystems and boot scripts (I'll do a clean install when there's a > new release). After switching to a Farallon EtherMac II-C card (needed > so

Re: Debian on mac68k (LC III)

On Tue, 1 Nov 2016, Mac User wrote: > > Here is the result booting 4.1.35-mac_scsi+ on an LC III with extensions > off and Penguin configured to set serial ports to 38400, 8 bits, no > parity, and the following boot command line: > > root=/dev/sda8 console=ttyS0 earlyprintk Have these

Re: Debian on mac68k (LC III)

On Fri, 28 Oct 2016, Mac User wrote: > > > Penguin options: > > > root=/dev/sda3 console=ttyS0 nologo > > > Serial: blank (I tried setting serial ports to 9600 baud, > > > 1 stop bit, no parity -- didn't work. I learned through > > > trial and error that the kernel communicates at 38400 >

Re: Debian on mac68k

On Thu, 27 Oct 2016, Mac User wrote: > ABCFGHIJK > Linux version 4.1.35-mac_scsi+ (fthain@nippy) (gcc version 4.6.3 (GCC) ) #1 > Tue6 > Saving 402 bytes of bootinfo > Detected Macintosh model: 27 > VIA1 at 50f0 is a 6522 or clone > VIA2 at 50f26000 is an RBV > Apple Macintosh LC III > Built

Re: Debian on mac68k

On Thu, 27 Oct 2016, Mac User wrote: > > My Mac IIfx hangs at the Penguin screen booting > "vmlinux-4.1.35-mac_scsi+" (same as > "vmlinux-4.1.35-mac_scsi-egret+"). > Did you check that the Serial Switch control panel is in "compatible" mode, as per the Penguin docs? Maybe the problem is my

Re: Debian on mac68k

On Wed, 26 Oct 2016, Mac User wrote: > > boot/vmlinux-4.1.35-mac_scsi-egret+ -- 4907715 bytes > vmlinux-4.1.35-mac_scsi-egret+ -- 3818980 bytes > > On my LC III, the first kernel (4907715 bytes) hung at the white > screen showing "ABCFGHIJK" (so one step later than the IIfx). > Sometimes

Re: Debian on mac68k

On Wed, 26 Oct 2016, Mac User wrote: > > boot/vmlinux-4.1.35-mac_scsi-egret+ -- 4907715 bytes > vmlinux-4.1.35-mac_scsi-egret+ -- 3818980 bytes The small one is a stripped binary. It should make no difference. > > Ok.. Neither kernel booted on my 32 MB Mac IIfx; both hung right > after the

Re: Debian on mac68k

>> >> SHA1 digests: >> 22146db55d372416534821227ba8a0662208da75 vmlinux-4.1.35-mac_scsi-egret+ >> 69430122ebb17ccc5b732fd4531a97787a387976 linux-m68k-image-4.1.35-mac_scsi-egret+.tar.gz >> >> If you just want the (upstream) mac_scsi changes, please use the >> sourceforge build instead. But note

Re: Debian on mac68k

Am 25.10.2016 um 06:34 schrieb Finn Thain: > Hi Stan and Stefan, > Hi Finn! > > The second patch series needs more testing before I can send it upstream. > It can be found on github if you want to read it or clone it: > https://github.com/fthain/linux/commits/egret > > The new Egret support

Re: Debian on mac68k

Hi Stan and Stefan, On Mon, 6 Jun 2016, Mac User wrote: > > I recompiled the 4.1.20 source (patched with the scsi patch) [...] > the 4.1.20 kernel runs fine on my Mac IIfx and LC III, but it is > noticeably slower than the 2.2.25 kernel in Debian 3.1. I've created a patch series to improve

Re: Fwd: Re: Debian on mac68k

On Sun, 5 Jun 2016, I wrote: > On Sat, 4 Jun 2016, John Paul Adrian Glaubitz wrote: > > > On 06/04/2016 07:03 AM, Finn Thain wrote: > > > > > Yes, systemd is very slow to boot on this system, so timeouts are > > > likely to be the problem. I've since found that the serial console on a 40 MHz

Re: Fwd: Re: Debian on mac68k

On Sat, 4 Jun 2016, John Paul Adrian Glaubitz wrote: > On 06/04/2016 07:03 AM, Finn Thain wrote: > > > Yes, systemd is very slow to boot on this system, so timeouts are > > likely to be the problem. > > The timeouts are related to dbus, not to systemd. I thought you said, "dbus timeout in

Re: Debian on mac68k

inn Thain > Cc: Stefan Niestegge; debian-68k@lists.debian.org > Betreff: Re: Fwd: Re: Debian on mac68k > > On 06/04/2016 02:43 PM, John Paul Adrian Glaubitz wrote: > > # ./debootstrap/deboostrap > > # ./debootstrap/deboostrap --second-stage > > I s

Re: Fwd: Re: Debian on mac68k

On 06/04/2016 02:43 PM, John Paul Adrian Glaubitz wrote: > # ./debootstrap/deboostrap # ./debootstrap/deboostrap --second-stage I should take a break and go outside, jesus. Sorry! -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet

Re: Fwd: Re: Debian on mac68k

On 06/04/2016 02:38 PM, John Paul Adrian Glaubitz wrote: > Just omit all the sbuild parts, i.e. just run debootstrap with --foreign and > --arch=m68k, then copy qemu-m68k-static into the chroot and run the following > command after changing into the chroot: > > # ./debootstrap/deboostrap Oops,

Re: Fwd: Re: Debian on mac68k

On 06/04/2016 07:03 AM, Finn Thain wrote: > Yes, systemd is very slow to boot on this system, so timeouts are likely > to be the problem. The timeouts are related to dbus, not to systemd. I also do not think that sysvinit would actually be faster. sysvinit runs shell code for boilerplate stuff

Re: Fwd: Re: Debian on mac68k

On Fri, 3 Jun 2016, John Paul Adrian Glaubitz wrote: > > > > And I'm getting "Failed to execute operation: Connection timed out" > > from systemctl, and other systemd weirdness like a shutdown hang. > > This is actually a known issue in systemd and fixing it is still on my > TODO list, I

Re: Fwd: Re: Debian on mac68k

On 06/03/2016 02:40 PM, Finn Thain wrote: > Like Stefan, I found that the serial console works intermittently. > Sometimes it boots fine e.g. > > [ OK ] Found device /dev/ttyS0. > ... > Starting Serial Getty on ttyS0... > [ OK ] Started Serial Getty on ttyS0. > > But at other times

Re: Fwd: Re: Debian on mac68k

On Mon, 30 May 2016, I wrote: > > On Mon, 30 May 2016, John Paul Adrian Glaubitz wrote: > > > > > You can just install the m68k cross-toolchain in Debian > > testing/unstable, then download the kernel sources or ask Finn to > > provide you with the sources he has and then build the kernel

Re: Fwd: Re: Debian on mac68k

On Mon, 30 May 2016, John Paul Adrian Glaubitz wrote: > > Well, yes, ADB support is currently broken as you have heard. So, either > you look into fixing it yourself or you install a much older version > of Debian. I don't think you can anyone else to jump in right now and > fix the driver for

Re: Fwd: Re: Debian on mac68k

On 05/30/2016 03:48 PM, Finn Thain wrote: > Another possible cause of the hang is a known Penguin bug triggered by > some large gzip'd kernel binaries. The workaround for this is to unzip it > before asking Penguin to load it. This is what I had in mind when I was thinking I had some problems

Re: Fwd: Re: Debian on mac68k

On Mon, 30 May 2016, Stefan Niestegge wrote: > > > > On my Centris 650, ADB support is working fine with the 3.16 stock > > kernel in any case. > > > > Now this is probably the thing to try out. Yes, you should definitely try out the debian kernel. It is possible that you can get a working

Re: Debian on mac68k

On Mon, 30 May 2016, Stefan Niestegge wrote: > > i added console=ttyS0,9600 to the kernel, 8n1 seems to be default, i got > the boot messages on the connected PC in miniterm.py (which uses > 9600,8,n,1 by default as well). I tend to use 38400 because that's the default for this serial driver

Re: Fwd: Re: Debian on mac68k

On 05/30/2016 03:32 PM, Finn Thain wrote: > That kernel already has CONFIG_FHANDLE=y. (The config file is included in > the download.) Well, that's odd then. >> I remember I had to fiddle around a bit to get it booting, but since the >> machine is currently in my basement, I'm afraid, I can't

Re: Fwd: Re: Debian on mac68k

On Mon, 30 May 2016, John Paul Adrian Glaubitz wrote: > > You can just install the m68k cross-toolchain in Debian > testing/unstable, then download the kernel sources or ask Finn to > provide you with the sources he has and then build the kernel with > CONFIG_FHANDLE. That kernel already

Re: Fwd: Re: Debian on mac68k

On 05/30/2016 01:10 PM, Stefan Niestegge wrote: >> Well, yes, ADB support is currently broken as you have heard. So, either >> you look into fixing it yourself or you install a much older version >> of Debian. I don't think you can anyone else to jump in right now and >> fix the driver for you. >>

Re: Fwd: Re: Debian on mac68k

Am 30.05.2016 um 12:50 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 12:36 PM, Stefan Niestegge wrote: >> No, i wasn't. Thats beyond my abilities. I just wanted to install Debian >> to my friend's old Mac. > > Well, you are installing on 20+-year-old hardware. I don't think it's fair > to

Re: Fwd: Re: Debian on mac68k

On 05/30/2016 12:36 PM, Stefan Niestegge wrote: > No, i wasn't. Thats beyond my abilities. I just wanted to install Debian > to my friend's old Mac. Well, you are installing on 20+-year-old hardware. I don't think it's fair to assume that everything works out-of-the-box and is straight-forward to

Re: Fwd: Re: Debian on mac68k

Am 30.05.2016 um 12:31 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 12:28 PM, Stefan Niestegge wrote: >> Seems like for Geert it was something he just needed to be remembered >> of. No idea how to CONFIG HANDLE on a system i cannot access. > > You are aware that anything starting with

Re: Fwd: Re: Debian on mac68k

On 05/30/2016 12:28 PM, Stefan Niestegge wrote: > Seems like for Geert it was something he just needed to be remembered > of. No idea how to CONFIG HANDLE on a system i cannot access. You are aware that anything starting with CONFIG_ is a kernel configuration option that you have to set when

Re: Fwd: Re: Debian on mac68k

Sorry, i messed up this mail - don't reply here, please Am 30.05.2016 um 12:28 schrieb Stefan Niestegge: > > Am 30.05.2016 um 11:45 schrieb John Paul Adrian Glaubitz: >> On 05/30/2016 11:42 AM, Stefan Niestegge wrote: >>> Later in booting, i got messages >>> [ TIME ] Timed out waiting for

Re: Debian on mac68k

Am 30.05.2016 um 11:45 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 11:42 AM, Stefan Niestegge wrote: >> Later in booting, i got messages >> [ TIME ] Timed out waiting for device dev-ttyS0.device. >> [DEPEND] Dependency failed for Serial Getty on ttyS0. >> >> i can try with

Re: Debian on mac68k

Am 30.05.2016 um 11:45 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 11:42 AM, Stefan Niestegge wrote: >> Later in booting, i got messages >> [ TIME ] Timed out waiting for device dev-ttyS0.device. >> [DEPEND] Dependency failed for Serial Getty on ttyS0. >> >> i can try with

Fwd: Re: Debian on mac68k

Am 30.05.2016 um 11:45 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 11:42 AM, Stefan Niestegge wrote: >> Later in booting, i got messages >> [ TIME ] Timed out waiting for device dev-ttyS0.device. >> [DEPEND] Dependency failed for Serial Getty on ttyS0. >> >> i can try with

Re: Debian on mac68k

On 05/30/2016 11:42 AM, Stefan Niestegge wrote: > Later in booting, i got messages > [ TIME ] Timed out waiting for device dev-ttyS0.device. > [DEPEND] Dependency failed for Serial Getty on ttyS0. > > i can try with console=/dev/ttyS0,9600,8n1 instead, but i guess there is > something else

Re: Debian on mac68k

Am 30.05.2016 um 11:30 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 11:21 AM, Stefan Niestegge wrote: > > You need to add something like: > > console=ttyS0,115200,8n1 > > However, please do *not* blindly the command line above but adjust it > to the hardware you are using i

Re: Debian on mac68k

On 05/30/2016 11:21 AM, Stefan Niestegge wrote: >> Which bootloader are you using? > > Penguin 19 Ok, so have a look here: > http://www.mac.linux-m68k.org/docs/penguin.php#123b You need to add something like: console=ttyS0,115200,8n1 However, please do *not* blindly the command line

Re: Debian on mac68k

Am 30.05.2016 um 11:14 schrieb John Paul Adrian Glaubitz: > On 05/30/2016 11:05 AM, Stefan Niestegge wrote: >> I can't login via serial, nor telnetd or sshd because none is configured. > > For serial, you need to pass the necessary parameters to the > kernel command line in your boot loader,

Re: Debian on mac68k

On 05/30/2016 11:18 AM, Geert Uytterhoeven wrote: >> But really, just setting "console=ttyS0,115200,8n1" is enough. I use that >> on all my embedded boards. > > Serial console itself was working. It was autologin that was missing. Ah, I see. I didn't know that some users actually would want that

Re: Debian on mac68k

Hi Adrian, On Mon, May 30, 2016 at 11:11 AM, John Paul Adrian Glaubitz wrote: > On 05/30/2016 10:51 AM, Geert Uytterhoeven wrote: >> Thanks, that points me to the services, and it seems I do have >> /etc/systemd/system/serial-getty@ttySC4.service.d/autologin.conf on

Re: Debian on mac68k

On 05/30/2016 11:05 AM, Stefan Niestegge wrote: > I was able to boot the 4.1.20-mac-scsi+ kernel Good. > Now the hen/egg problem comes up. The Mac boots up, and i can only look > at the screen and wait for it to enter screensaving mode. Yeah, typing is rather difficult without keyboard support

Re: Debian on mac68k

Hi! On 05/30/2016 10:51 AM, Geert Uytterhoeven wrote: > Thanks, that points me to the services, and it seems I do have > /etc/systemd/system/serial-getty@ttySC4.service.d/autologin.conf on some > NFS roots that had systemd installed for a few minutes, but IIRC never booted > into it. >

Re: Debian on mac68k

Hello, I was able to boot the 4.1.20-mac-scsi+ kernel Now the hen/egg problem comes up. The Mac boots up, and i can only look at the screen and wait for it to enter screensaving mode. > On 05/30/2016 03:05 AM, Finn Thain wrote: >> Without ADB, you will need a network login service (e.g. sshd)

Re: Debian on mac68k

Hi Adrian, On Mon, May 30, 2016 at 10:09 AM, John Paul Adrian Glaubitz wrote: > On 05/30/2016 09:21 AM, Geert Uytterhoeven wrote: >> Ah, so you may also know the solutions for my issues below, from a >> Google+ post a while ago? >> >> While dist-upgrading my

Re: Debian on mac68k

On 05/30/2016 09:21 AM, Geert Uytterhoeven wrote: > Ah, so you may also know the solutions for my issues below, from a > Google+ post a while ago? > > While dist-upgrading my debian-armhf/jessie NFS roots, systemd was > installed on one of them, breaking the next boot of the affected board > :-(

Re: Debian on mac68k

Hi Adrian, On Mon, May 30, 2016 at 8:26 AM, John Paul Adrian Glaubitz wrote: > On 05/30/2016 03:05 AM, Finn Thain wrote: >> Without ADB, you will need a network login service (e.g. sshd) and/or >> serial console. The getty on /dev/ttyS0 or /dev/ttyS1 used to be >>

Re: Debian on mac68k

On 05/30/2016 03:05 AM, Finn Thain wrote: > Without ADB, you will need a network login service (e.g. sshd) and/or > serial console. The getty on /dev/ttyS0 or /dev/ttyS1 used to be > configured in /etc/inittab, but I never tried that with systemd. Just pass "console=ttyS0,19200,8n1" on the

ADB support, was Re: Debian on mac68k

On Mon, 30 May 2016, I wrote: > > The problem is that my kernel builds leave CONFIG_ADB_MACIISI disabled > because years ago I found that this driver caused instability. This > means that, for certain 68030-based Mac models including the LC's and > the IIsi and IIvi, the 4.1 kernel binary

Re: Debian on mac68k

Hi Stefan, On Sun, 29 May 2016, Stefan Niestegge wrote: > > > > SHA1 2a5418a5423f234ea549ea9dc26624cb5dbdae69 > > > > As before, this kernel configuration has the essential Mac drivers > > built-in so that it can be used without an initrd, e.g. for > > installation. > > > > Hello, > > i

Re: Debian on mac68k

Am 24.03.2016 um 01:48 schrieb Finn Thain: > > On Wed, 24 Feb 2016, I wrote: > >> ... The new build is here, >> >> >> https://www.telegraphics.com.au/~fthain/stan/linux-m68k-image-4.1.18-mac-00084-ge6b89b9.tar.gz >> >> SHA1 9ee49c4d9361785b872f9448acd3e25a4f52ab92 >> >> The patches are

Re: Debian on mac68k

On Wed, 24 Feb 2016, I wrote: > ... The new build is here, > > > https://www.telegraphics.com.au/~fthain/stan/linux-m68k-image-4.1.18-mac-00084-ge6b89b9.tar.gz > > SHA1 9ee49c4d9361785b872f9448acd3e25a4f52ab92 > > The patches are the 84 that I've sent to the scsi maintainers. They >

Re[3]: Debian on mac68k

On Sat, 5 Mar 2016, Scott Holder wrote: > > If you send the output of dmesg, that would be helpful. You may see a > > scsi error when you unmount filesystems, because old scsi drives don't > > support the cache commands the kernel sends. > > I'm pretty sure it's bad sectors on the drive. If

Re[3]: Debian on mac68k

-- Original Message -- From: "Finn Thain" <fth...@telegraphics.com.au> To: "Scott Holder" <sc...@iamscott.net> Cc: debian-68k@lists.debian.org Sent: 2/25/2016 6:56:32 PM Subject: Re[2]: Debian on mac68k If you send the output of dmesg, that would be he

Re[2]: Debian on mac68k

On Thu, 25 Feb 2016, Scott Holder wrote: > > > > > > > > > https://www.telegraphics.com.au/~fthain/stan/linux-m68k-image-4.1.18-mac-00084-ge6b89b9.tar.gz > > > > SHA1 9ee49c4d9361785b872f9448acd3e25a4f52ab92 > > > >The patches are the 84 that I've sent to the scsi maintainers. They >

Re: Debian on mac68k

On 02/25/2016 06:55 PM, Scott Holder wrote: > Gave this a shot on the ol' LC 475 and it booted up fine. Maybe a little > bit faster than the previous 3.x I was using. Gave it a good > dist-upgrade and it seems to be running well, aside from a couple weird > SCSI messages. Probably hardware. Great

Re[2]: Debian on mac68k

-- Original Message -- From: "Finn Thain" <fth...@telegraphics.com.au> To: "Mac User" <user...@yahoo.com> Cc: "John Paul Adrian Glaubitz" <glaub...@physik.fu-berlin.de>; debian-68k@lists.debian.org Sent: 2/23/2016 11:27:

Re: Debian on mac68k

On Wed, 24 Feb 2016, Mac User wrote: > I was responding to the comment that the [mac68k driver] code in 2.x > kernels isn't good, implying it is better in 4.x kernels. So I was > wondering whether the better Linux 4.x ADB code could be backported to > 2.x kernels. Occasionally people have

Re: Debian on mac68k

On Wed, 24 Feb 2016, Geert Uytterhoeven wrote: > On Wed, Feb 24, 2016 at 3:18 PM, Mac User wrote: > > > > Sounds like it wouldn't work due to the keycode change. > > That would matter only if you configured userland to change the keymap, > right? > > The default US-QWERTY

Re: Debian on mac68k

On Wed, 24 Feb 2016, Mac User wrote: > I always get an error that video slot interrupts were not able to be > disabled ("booting anyway"). Usually it's not a problem. I'll try > booting with extensions off. The problem is very unlikely to be the video card. > > I don't have any opinion

Re: Debian on mac68k

On 02/24/2016 05:26 PM, Mac User wrote: > No. I was responding to the comment that the ADB code in 2.x kernels > isn't good, implying it is better in 4.x kernels. So I was wondering > whether the better Linux 4.x ADB code could be backported to 2.x > kernels. I don't think any kernel developer is

Re: Debian on mac68k

On 02/24/2016 03:18 PM, Mac User wrote: >> Debian uses systemd and doesn't need init scripts, which is why you don't >> see any messages from those scripts. That's not correct. There are still init scripts in Debian. Anything listed by systemctl with the prefix "LSB: " is still an init script.

Re: Debian on mac68k

On Wed, Feb 24, 2016 at 3:18 PM, Mac User wrote: >> If you boot the old Debian 3.1 using a recent kernel then you won't be >> able to log in at the console, because the ADB keycodes were changed >> sometime after the v2.2 kernel. (I'm thinking of the IIfx, which does >> not

Re: Debian on mac68k

On Tue, 23 Feb 2016, Mac User wrote: > > There were no further messages after: "systemd[1]: Failed to mount tmpfs > at /sys/fs/cgroup: No such file or directory" For the benefit of systemd users, I have built a kernel binary with, CONFIG_FHANDLE=y (selects CONFIG_EXPORTFS=y)

Re: Debian on mac68k

On Tue, 23 Feb 2016, John Paul Adrian Glaubitz wrote: > On 02/23/2016 04:41 PM, Mac User wrote: > > I loaded the tarball to my main Linux partitions on an LC III after > > booting into a rescue partition. I didn't see any modules in the link > > you posted, but I can create those later. Is the

Re: Debian on mac68k

On Tue, 23 Feb 2016, Mac User wrote: > Unfortunately, the 3.16.2 kernel didn't boot on my 36 MB LC III; I'm > using Penguin 19 for the booter; it's configured to take up almost all > the RAM. I tried with and without the initrd. Debian kernels should work fine, but if you need to use the 5380

Re: Debian on mac68k

On Tue, 23 Feb 2016, Mac User wrote: > On 2/23/16 8:50 AM, John Paul Adrian Glaubitz wrote: > > Use the kernel that Finn just created for your machine, see: > > > > > https://lists.debian.org/debian-68k/2016/02/msg00047.html > > thanks.. The kernel hung once at the

Re: Debian on mac68k

Hi! On 02/23/2016 05:56 PM, Mac User wrote: > There were no further messages after: > "systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such file > or directory" This looks like Finn forgot to include CONFIG_CGROUPS=y in his kernel configuration. CGroups is a kernel features which is

Re: Debian on mac68k

On 02/23/2016 04:41 PM, Mac User wrote: > I loaded the tarball to my main Linux partitions on an LC III after > booting into a rescue partition. I didn't see any modules in the > link you posted, but I can create those later. Is the 3.16.2 config > file for a generic 3.16.2 kernel, or are there

Re: Debian on mac68k

On 02/23/2016 10:51 AM, Dirk Heinrichs wrote: > Am 23.02.2016 um 10:37 schrieb John Paul Adrian Glaubitz: > >> The archive runs are at 00:00, 06:00, 12:00 and 18:00 UTC. > > Ah, OK. 12:00 UTC is just about 2 hours away, so I'll try again later > today. Thanks. Be aware that the install run

Re: Debian on mac68k

Am 23.02.2016 um 10:37 schrieb John Paul Adrian Glaubitz: > The archive runs are at 00:00, 06:00, 12:00 and 18:00 UTC. Ah, OK. 12:00 UTC is just about 2 hours away, so I'll try again later today. Thanks. Bye... Dirk -- Dirk Heinrichs GPG Public Key CB614542 |

Re: Debian on mac68k

On 02/23/2016 09:33 AM, Dirk Heinrichs wrote: > Am 23.02.2016 um 09:28 schrieb Dirk Heinrichs: > >> Just found that the instructions given use the SSH URL to clone the >> qemu-m68k repo. That wouldn't work for everyone unless they have been >> added to the project. Better use the HTTPS one. > >

Re: Debian on mac68k

Am 23.02.2016 um 09:33 schrieb Dirk Heinrichs: > It also seems that the two patches have meanwhile been applied to the > 680x0-master-dev branch. Running debootstrap then fails because of: I: Retrieving iproute2 4.3.0-1 W: Couldn't download package iproute2 (ver 4.3.0-1 arch m68k) Looking into

Re: Debian on mac68k

Am 23.02.2016 um 09:36 schrieb John Paul Adrian Glaubitz: > I have actually not been added to the project as far as I know, so I would be > surprised you need additinal permissions to clone the repository. You're right, sorry. Didn't have my GH key added to ssh-agent when cloning. Bye...

Re: Debian on mac68k

> On Feb 23, 2016, at 9:28 AM, Dirk Heinrichs wrote: https://wiki.debian.org/M68k/sbuildQEMU > > Just found that the instructions given use the SSH URL to clone the > qemu-m68k repo. That wouldn't work for everyone unless they have been > added to the project.

Re: Debian on mac68k

Am 23.02.2016 um 09:28 schrieb Dirk Heinrichs: > Just found that the instructions given use the SSH URL to clone the > qemu-m68k repo. That wouldn't work for everyone unless they have been > added to the project. Better use the HTTPS one. It also seems that the two patches have meanwhile been

Re: Debian on mac68k

Am 21.02.2016 um 07:02 schrieb John Paul Adrian Glaubitz: > If you follow this guide, you should be able to get a working qemu-m68k > chroot which will allow you to build Debian packages for m68k: > >> > https://wiki.debian.org/M68k/sbuildQEMU Just found that the instructions given use the SSH

Re: Debian on mac68k

On Sat, 20 Feb 2016, Mac User wrote: > On 2/20/16 7:09 PM, Finn Thain wrote: > > > The scsi stability issues can be resolved with the right patches. A > > timekeeping issue suggests high timer interrupt latency. If this > > problem affects recent kernels, we could look into it. If you are >

Re: Debian on mac68k

On Sun, Feb 21, 2016 at 6:49 AM, John Paul Adrian Glaubitz wrote: > $ apt install gcc-5-m68k-linux-gnu > > Then Stan just has to set ARCH=m68k CROSS_COMPILE=m68k-linux-gnu- when > run 'make menuconfig' and 'make' to configure and build the kernel. Note that

Re: Debian on mac68k

On 02/21/2016 04:36 AM, James Hemsing wrote: > Even if you could compile on a IIfx, the amount of time it would take > would be astronomical. An Aranym build took me over an hour on an Ivy > Bridge i7. You should be able to cross-compile on Debian testing or unstable the kernel in a few minutes.

Re: Debian on mac68k

Hi Stan! On 02/20/2016 11:30 PM, Mac User wrote: > If there's an effort to build packages for etch or later According to the current statistics, 90% of the packages that were ever built on m68k are currently up-to-date: > https://buildd.debian.org/stats/graph2-ports-big.png So, I wouldn't call

Re: Debian on mac68k

On 02/21/2016 03:09 AM, Finn Thain wrote: > If you want to build your own kernels, I suggest you obtain a cross > toolchain from kernel.org: https://www.kernel.org/pub/tools/crosstool/ If you're running Debian testing or unstable, you don't have to go that far. You can just install the cross

  1   2   >