From: Gwenole B. <gb...@di...> - 2004-05-10 07:45:23
|
Hi, I have committed code to enable TUN/TAP ("tun" module) support in both Basilisk II and SheepShaver. That's cool, I can even get Internet connection at home through an ethernet DSL modem. A possible extension to the tunconfig script (derived from MOL's) is to install a DHCP server on the tunX interface so that users only need to configure for a DHCP client on the Mac side. I have yet to little-endian & 64-bit fix networking code in SheepShaver. TUN/TAP is also supposed to work on FreeBSD and Solaris but without adequate system I can't test and tunconfig may need some arrangements. I am not a networking wizard, so if someone could proofread and make sure the following portion added to the README file is understandable, that would be fine. Thanks. 3. Access the network through a "tuntap" interface. The "ethernet card description" must be set to "tun". TUN/TAP provides packet reception and transmission for user space programs. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. A virtual network configuration script is required and the default is /usr/local/BasiliskII/tunconfig unless you specify a different file with the "etherconfig" item. This script requires you that "sudo" is properly configured so that "/sbin/ifconfig" and "/sbin/iptables" can be executed as root. Otherwise, you can still write a helper script which invokes your favorite program to enhance a user priviledges. e.g. in a KDE environment, kdesu can be used as follows: #!/bin/sh exec /usr/bin/kdesu -c /path/to/tunconfig $1 $2 |
From: Gwenole B. <gb...@di...> - 2004-05-10 12:14:16
|
I wrote > I have yet to little-endian & 64-bit fix networking code in > SheepShaver. Some little-endian fixes are now in CVS, but I have still not tested it on x86, only minimal changes and reading of ether.cpp, ether_linux.cpp. As for 64-bit fixes, we need to replace the new/delete with proper 32-bit memory allocation. An idea is to use NewPtrSysClear/DisposePtr, what do you think? Bye, Gwenole. |
From: Tomasz J. <to...@je...> - 2004-05-13 14:38:01
|
Hello. As soon as Gwenole informed about JIT speed improvements checked in (yesterday), I downloaded the latest CVS code and compiled it. Compilation succeeded and when I ran it, configuration window appeared. But as soon as I started emulation, the application just terminated. There was no error message on the console, nor any message box. However, when I swiched JIT off, it worked (booted 8.5 CD). A couple of weeks ago I was compiling the latest tgz snapshot from February and it worked fine, so I think I know how to configure SheepShaver. This time however I might have screwed something, because I wasn't able to generate ./configure script from autoconf (as many other people), so I copied it from tgz snapshot. Another potential problem might be that I am running FC 2 test 3 distribution. Is there anything that you want to know in order to troubleshoot this problem (strace or whatever)? Jerzu |
From: Gwenole B. <gbe...@ma...> - 2004-05-13 15:42:29
|
On Thu, 13 May 2004, Tomasz Jerzykowski wrote: > As soon as Gwenole informed about JIT speed improvements checked in > (yesterday), I downloaded the latest CVS code and compiled it. Compilation > succeeded and when I ran it, configuration window appeared. But as soon as I > started emulation, the application just terminated. Please make clean, make. Or at least rm -f obj/sheepshaver_glue.cpp obj/ppc-*.o. Otherwise objects layout is different thus causing strange things. ;-) I know, I should fix Makefile deps... Hmm, or probably people should run make dep first? |
From: Tomasz J. <to...@je...> - 2004-05-13 16:43:34
|
> On Thu, 13 May 2004, Tomasz Jerzykowski wrote: > > > As soon as Gwenole informed about JIT speed improvements checked in > > (yesterday), I downloaded the latest CVS code and compiled it. Compilation > > succeeded and when I ran it, configuration window appeared. But as soon as I > > started emulation, the application just terminated. > > Please make clean, make. Or at least rm -f obj/sheepshaver_glue.cpp > obj/ppc-*.o. Otherwise objects layout is different thus causing strange > things. ;-) > > I know, I should fix Makefile deps... Hmm, or probably people should run > make dep first? > <Robocop_voice> Thank you for your cooperation. </Robocop_voice> Didn't help. This is the ending of 'strace ./SheepShaver' log: ========== clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf70010c8) = 12098 waitpid(12098, Reading ROM file... WARNING: Cannot open /dev/fd1u1440 (No such device or address) PowerPC CPU emulator by Gwenole Beauchesne [WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV], 0) = 12098 --- SIGCHLD (Child exited) @ 0 (0) --- exit_group(-1) = ? ======== This is my config file: ======== disk /root/sheepshaver/hd extfs /root/sheepshaver windowmodes 3 screenmodes 0 seriala /dev/ttyS0 serialb /dev/ttyS1 rom mac.rom bootdrive 0 bootdriver 0 ramsize 67108864 frameskip 8 gfxaccel true nocdrom false nonet false nosound true nogui false noclipconversion false ignoresegv true jit true keyboardtype 5 keycodes false mousewheelmode 1 mousewheellines 3 dsp /dev/dsp mixer /dev/mixer ignoresegv true ======== I suspect that using of ./configure script from the older release of SheepShaver may cause this problem. Bot how can I generate it myself if every attempt to ./autogen.sh ends with: ======== ./configure: line 6541: syntax error near unexpected token `1.2.0,' ./configure: line 6541: `AM_PATH_GTK(1.2.0,' ======== I have gtk ang glib devel packages installed (otherwise I wouldn't be able to compile it at all). 'aclocal-1.4' trick doesn't work.Would you be so kind to prepare a new tarball snapshot? I would be glad to try to compile it myself. Jerzu |
From: Gwenole B. <gb...@di...> - 2004-05-13 18:14:51
|
Hi, Sorry, I don't know why this happens for you. It could be a miscompilation, would you mind telling me which compiler do you use? For reference, I am using gcc 3.2.2 on x86 and gcc 3.3.2 on amd64. > This is my config file: > ======== > frameskip 8 Ouch, video refreshes won't be nice looking at. Since people told me they found video stuff slow in SheepShaver, I always set that to 0 (which turns out to be 1 in SheepShaver), thus a 30 Hz resolution. My eyes don't suffer from that and benchmarks show twice the speed as a native 8100/80 for video. > ignoresegv true Please avoid this. You could get hangs instead of a real SIGSEGV and you wouldn't know where SheepShaver possibly crashed. > I suspect that using of ./configure script from the older release of > SheepShaver may cause this problem. Bot how can I generate it myself if > every attempt to ./autogen.sh ends with: > ======== > ./configure: line 6541: syntax error near unexpected token `1.2.0,' > ./configure: line 6541: `AM_PATH_GTK(1.2.0,' > ======== Make sure you have gtk+-1.2 autoconf macros, e.g. /usr/share/aclocal/gtk.m4. > Would you be so kind to prepare a new tarball snapshot? That was the plan to make it this week but there is another issue I want to check first. Bye, Gwenole. |
From: Tomasz J. <to...@je...> - 2004-05-13 18:26:06
|
> Hi, > > Sorry, I don't know why this happens for you. It could be a > miscompilation, would you mind telling me which compiler do you use? > For reference, I am using gcc 3.2.2 on x86 and gcc 3.3.2 on amd64. > I tried gcc 3.3.3 and 3.4.0 on x86 with the same effect. February snapshot was fine on both compilers. > Would you be so kind to prepare a new tarball snapshot? > > That was the plan to make it this week but there is another issue I > want to check first. > So I'm not going to bother you now and will wait for the tarball... > Bye, > Gwenole. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > basilisk-devel mailing list > bas...@li... > https://lists.sourceforge.net/lists/listinfo/basilisk-devel |
From: Gwenole B. <gb...@di...> - 2004-05-15 04:22:35
|
Hi, > So I'm not going to bother you now and will wait for the tarball... I have placed a temporary one here: <http://gwenole.beauchesne.free.fr/sheepshaver/files/SheepShaver-2.2- 20040514.tar.bz2> If you want ethernet support, you have to s/#ifdef WORDS_BIGENDIAN/#if 1/ in kpx_cpu/sheepshaver_glue.cpp Then, if you get some weird crashes or hangs with sheep_net enabled, try with MOL's module and the SheepShaver-2.2-misc.patch applied, available in the same directory. I have not yet checked why this happens that way. Bye, Gwenole. |
From: Tomasz J. <to...@je...> - 2004-05-15 10:47:07
|
----- Original Message ----- From: "Gwenole Beauchesne" <gb...@di...> To: <bas...@li...> Sent: Saturday, May 15, 2004 5:23 AM Subject: Re: [B2-devel] JIT on x86 problem > Hi, > > > So I'm not going to bother you now and will wait for the tarball... > > I have placed a temporary one here: > <http://gwenole.beauchesne.free.fr/sheepshaver/files/SheepShaver-2.2- > 20040514.tar.bz2> > Thank you very much! Unfortunately, it still crashes with JIT enabled. Moreover, when I ran it without JIT, but tried to boot with the wrong CD, the tray ejected, I closed it again, but then my PC locked hard (had to reset it). I think there is something wrong with my configuration. I'm using FC2 test 3, obviously with 2.6 kernel - maybe this is too new... Today I will try to run it on a more conservative set-up. Expect a report soon :) Jerzu |
From: Gwenole B. <gb...@di...> - 2004-05-15 17:39:22
|
Hi, > Thank you very much! Unfortunately, it still crashes with JIT enabled. > Moreover, when I ran it without JIT, but tried to boot with the wrong > CD, > the tray ejected, I closed it again, but then my PC locked hard (had to > reset it). No matter your system is new or not, if it crashes with JIT enabled and not without, then there is a problem with JIT. Are you running as root? You could also try to get rid of your ~/.sheepshaver_nvram. BTW, what system and which ROM do you use? Bye, Gwenole. |