too.
Thanks. So if I'm reading this properly, all of the above updates need to
hapoen at once to get around chicken-and-egg issues, then the updated
system can be used as a basis for sid, and maybe there'll be an m68k
squeeze since lenny basically never happened?
I'm trying t
how the pieces of Debian go together enough
to get a working system, or perhaps offer some simple instructions for a
dummy like above? I feel like I'm just randomly trying to put pieces
together from too many different places. I can't get a cohesive picture
(yet).
Thanks,
John Klos
I built a cross compiler with patched sid source packages because the
patches aren't in sid. The exception is sid binutils which has support for
NPTL/TLS on m68k.
If you want the patches that I use, I can send links. I suggest, first you
should read up on the gory details (in the archives of this
tested!
This address is used to send SPAM to mailing lists. Google it.
Damned SPAMMERs.
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.neb.4.64.1003181758070.2
I have not tried LVM on m68k, but why should it not work? I am
running low on harddisks, especially IDE disks are not easy/cheap
to get nowadays, unless you buy used... that will become a problem
for m68k in the long run.
SATA-IDE adapters are about $10 USD. I've used 2 TB drives on my A4000's
SATA-IDE adapters are about $10 USD. I've used 2 TB drives on my
Any recommendations?
http://www.newegg.com/Product/Product.aspx?Item=N82E16812156011
or
http://www.newegg.com/Product/Product.aspx?Item=N82E16812240012
The second one is more expensive, but I prefer it because of the form
facto
m68k Debian
up to date. Thank you, everyone!
John Klos
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.neb.4.64.1204181643520.4...@andromeda.ziaspace.com
ave become commercial entities which attempt to
distringuish themselves from each other gratuitously, but hopefully that
will never happen to Debian.
Other people in Debian recognize that supporting multiple architectures is
desirable and improves the overall quality of the project.
John Kl
tly from Debian.
Thanks,
John Klos
Sixgirls Computing Labs
se, of Debian to produce a
consistent source tree which is the same version across architectures? If
so, maybe there aren't that many m68k related problems.
I suppose most of the work is going on in the architecture neutral parts
of Debian?
John Klos
Sixgirls Computing Labs
d even starts. Check the failed build
> pages on crest and start fixing those gcc bugs. But then this is all for
> testing, and probably not many people are running testing on m68k.
I'm sure whatever work is done for m68k will be of use for NetBSD 2.0,
which will have gcc 3.3 as the
er than m68k Debian, and there were some security
issues with m68k Debian software (both OS software (kernel and userland)
and packages) due to its age. Because I was somewhat new to Linux, I found
it difficult to compile things from scratch, so I decided m68k Debian
wasn't viable at that
et, but some changes may
have fixed this support. Also, in the past, no SCSI was supported (only
netbooting with NFS storage). SCSI is now working pretty well.
http://www.netbsd.org/Ports/next68k/
http://mail-index.netbsd.org/port-next68k/2002/09/
Good luck,
John Klos
Sixgirls Computing Labs
m:
ftp://lilith.sixgirls.org/pub/NetBSD/pub/NetBSD/packages/m68k/
NetBSD 2.0 will use gcc 3.3; when we do soft-float for 2.0, we expect to
then be able to get soft-float into gcc.
Please let me know if you try this - we'd like more feedback.
Thanks,
John Klos
Sixgirls Computing Labs
here:
http://www.netbsd.org/Documentation/pkgsrc/
If you want to use softfloat prebuilt binaries, follow the instructions
here:
http://www.netbsd.org/Documentation/pkgsrc/using.html#getting%20started
and use ftp://lilith.sixgirls.org/pub/NetBSD/packages/m68k/All/(whatever)
in place of the ftp URL.
I
Hello,
> On Sat, Nov 08, 2003 at 04:32:33PM +0100, dade wrote:
> > my lc475 work nice with netbsd 1.6.1, the problem now is the sound chip,
> > dmesg show this:
>
> You'll want to ask on a netbsd mailinglist. This one is about Linux...
Does Linux support sound on this
ck into gcc and into Debian,
but I've forgotten where and who.
In the meanwhile, NetBSD support on LC040 systems is good. We have both
1.6.2 and 2.0 snapshots, plus many precompiled softfloat binary packages.
John Klos
since I can't imagine that people with LC040 systems are going
to expect to have a GUI, but the X apps will come soon.
While Debian's resources should obviously stay with the regular m68k
builds, I can definitely see that making a kernel and OS snapshot
available for broken LC040 systems every now and again would not be hard.
John Klos
on LC040 systems is good. We have both 1.6.2
and 2.0 snapshots, plus many precompiled softfloat binary packages.
John Klos
> Received: (at maintonly) by bugs.debian.org; 19 Mar 2004 07:24:22 +
> >From debian-68k@lists.debian.org Thu Mar 18 23:24:22 2004
> Return-path:
> Received: from (bugs.debian.org) [218.22.185.82]
> by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
> id 1B4EMf-0002SC-00; Thu, 18
Hello,
Would everyone on this mailing list who owns a Windows computer PLEASE
check it for viruses? I'm tired of getting all of these virus scanner
reports, and the ISPs who run them don't seem to care enough to fix them
so they don't reply to mailing lists.
PLEASE!
John Klos
-
ux on m68k
hardware, such as Amigas and older Macs.
I suggest you sell your HP running Windows XP and buy an Amiga. The floppy
drives on those are well supported.
John Klos
--
Panem et circences.
from
which the virus was sent.
Thank you,
John Klos
On Mon, 21 Jun 2004, npnssmtp1 wrote:
Return-Path: <[EMAIL PROTECTED]>
Received: from murphy.debian.org (murphy.debian.org [146.82.138.6])
by lain.ziaspace.com (8.12.11/8.12.10) with ESMTP id i5KIpq3R009677
for <[EMAIL PROTECTED]
Sorry - didn't mean to include the Debian list in that reply.
John
Any reasoning why FPU emulation has been disabled?
The docs say it’s incomplete, bogus and experimental and generally
not-working so I removed it for space reasons.
The docs most likely are talking about LC040 FPU trap emulation.
John
If the CPU has this mask set then FPU emulation isn't a viable solution.
You really need to get a 68040 chip (or a 68LC040 chip without the bug).
See http://www.mac.linux-m68k.org/docs/faq.php#sec-4.5
The CPU reads:
MC68030FE25B
04D66C
QEAN9239
MALAYSIA
'030 CPUs don't have floating point ex
Hi, and welcome!
Recently I've been wanting to play around with my old 68k mac's again
and decided I wanted to try and put Debian on my old LC630.
Unfortunately on opening up my 630 I seem to possibly have one of the
defective 68LC040's (XC68LC040RC33B 02E23G QEUE9439A Malaysia) so I
was wanting
Another simpler example, not involving unions:
-8<-
#include
#include
#include
int main(int argc, char** argv) {
double d[2];
d[0] = NAN;
d[1] = -d[0];
printf("%F\n", d[1]);
}
-8<-
Gives NAN on '030 & '882, '040, '060, with gcc 7.4.0 & gcc 10.3.0.
Does Linux sup
If anyone knows of a 68030 emulator (maybe Basilisk?) that can boot
Linux, then I might be able to use that for faster testing.
I've played around with NetBSD on FS-UAE. I'd use it more, except for the
fact that the emulation of the Commodore 2065 ethernet card gives very
flakey networking.
might
benefit from a 2 byte alignment) uses 4 byte alignment in NetBSD.
John Klos
ery other 32-bit big-endian
platform.
This is nonsense. The natural alignment for m68020, m68030, m68040, m68060
is 32 bit. That Linux didn't follow the SVR4 spec for ELF was an error.
I really want to know:
Who gets to make the call about whether or not the change is made?
John Klos
There's no real point being made here. Which packages aren't relevant
any more, due to bloat? Who decides?
Users do. I've said so several times.
https://lists.debian.org/debian-68k/2023/08/msg00023.html
https://lists.debian.org/debian-68k/2024/10/msg00024.html
https://lists.debian.org/debian-68k
Hi,
You're not offering help. You, like Finn as well, are trying to block fixing
a long-standing problem of Linux/m68k without offering any sustainable
alternatives
to fix this problem.
I didn't see anywhere that Eero was blocking or hinting at blocking. I
only saw Eero offering to collect d
I don't see in above dir e.g. LLVM or Qt, which were in the Debian 2-byte
alignment problems list:
https://wiki.debian.org/M68k/Alignment
Our package lists include as much as could be built in a given quarter.
The current quarter has, for example, llvm and clang:
https://cdn.netbsd.
It was very obviously your decision to use 2 byte alignment even though it
was against the official SVR4 ABI ;-).
No, I followed the official ABI.
People here are clearly talking about the Unix SVR4 ABI. It's not clever
to start talking about the Linux ABI without saying you're now talking
a
35 matches
Mail list logo
