Mac OS underlying FreeBSD - does it run Linux emulation?
Hi, does anyone know whether one can run Linux applications under the underlying FreeBSD of the MAC OS (on an Intel Core Duo mini Mac)? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
VMWARE-Player
Hi, does FreeBSD provide the ability to run VMWARE-Player for Linux and run VMs in it? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: increasing dd disk to disk transfer rate
On Fri, Jan 13, 2006 at 02:29:15PM +0100, Christoph P. Kukulies wrote: On Thu, Jan 12, 2006 at 02:23:37PM -0700, Kenneth D. Merry wrote: Then I tried to read back dd if=/dev/ad2 of=/dev/zero bs=2m Yes, just for the fun I said 2m blocksiye. And now we come back to FreeBSD contents: The system froze at this command (FreeBSD 5.2.1 on that machine) I believe I posted a followup on this message but probably forgot to do a group reply: It turned out that I first thought it crashed only when I type ^T while the dd was running. But this was accidently happening. Also with bs=1m the system freezes (reproducably). Well, this is some intermediate 5.2.1 so I will give it a try some time again when I have a 6.x running. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: increasing dd disk to disk transfer rate
Thanks, folks, for the interesting contributions. I really should have marked the subject OT but there spring up a lot of interesting ideas. On Fri, Jan 13, 2006 at 08:13:00AM +1100, Peter Jeremy wrote: On Thu, 2006-Jan-12 10:48:38 +0100, Christoph Kukulies wrote: dd if=/dev/ad2 of=/dev/ad3 conv=noerror The process is running now since yesterday evening and it is at 53 MB at a transfer rate of about 1.1 MB/s. In case the the result being unusable I would like to find a way to make this copying faster. Note that whilst increasing the DD blocksize will speed up the transfer, it will also increase the amount of collateral damage when a hard error occurs. If you rummage around the ports or tools tree, you'll find a utility (its name escapes me but I believe it was written by phk) that is designed to do disk-to-disk recovery - it /usr/src/tools/tools/recoverdisk I fired up this tool yesterday night and it is still running. Ah yes, it runs forever unless it empties the queued failed block reads. It writes out a line of numbers (which are a bit difficult to understand). I think the suggestion to do a filewise recovery would be the best since it will be very unlikely copys data in big slabs until it gets an error and then works around the faulty area block by block. You should also install /usr/ports/sysutils/smartmontools - this handles S.M.A.R.T. Yes, but what would smart help me further with recovery? Is there a way to tweak the driver (be it the FreeBSD promise driver or the normal ata driver) to use more retries on errors so that I have the chance to copy everything or nearly everything of the already degrading hard disk? A quick look at the ata driver suggests that there are a number of 'retry' and 'retries' variables/fields. I suspect you could increase the number of retries if you wanted to patch the driver. Thanks for the help. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: increasing dd disk to disk transfer rate
On Thu, Jan 12, 2006 at 02:23:37PM -0700, Kenneth D. Merry wrote: written by phk) that is designed to do disk-to-disk recovery - it copys data in big slabs until it gets an error and then works around the faulty area block by block. It's called 'recoverdisk', and is in src/tools/tools/recoverdisk. I used it to copy a friend's hard drive, and it worked well. (Although the supposedly 'bad' disk didn't turn out to have any bad sectors.) Ken I was able to recover. The 0.9980 copy of my damaged disk to the identical new one, using recoverdisk /dev/ad2 /dev/ad3 turned out to have been successful. The program was still trying to improve the result but I didn't see any increase of recoverd block, so I terminated it. But the result was a fully functioning bootable (Windows XP) disk. Probably due to the fact that the system (Windows) had been successful in repairing itself by remapping bad clusters of files to intact areas (all partitions were FAT32) the resulting copy was fully functional. I never had really hard disk errors, just the frequent CHKDSK that were required. I believe to recall that Hitach (IBM) had a design error in their Deskstar series when the firmware of the drive did not randomly park the head but left it only at the beginning of the disk all the time resulting in that area preferably being 'worn out' - I have been victim of that bad 40 GB Deskstar series in the past several times. Don't know if this still was the case with the Travelstar mobile computers disks series. The frequent errors I had in hiberfil.sys point into something in that direction (only my little theory). Just for the record: Before I wanted to give back in my faulty disk to my computer supplier as a case for warranty, I zeroed out the faulty disk. dd if=/dev/zero of=/dev/ad2 bs=1m It took half an hour to zero out the 80GB. Transferrate 44 MB/s? And not a single error ? Or is this normal? Then I tried to read back dd if=/dev/ad2 of=/dev/zero bs=2m Yes, just for the fun I said 2m blocksiye. And now we come back to FreeBSD contents: The system froze at this command (FreeBSD 5.2.1 on that machine) -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ffsrecov still broken port?
I have a disk dump of a failed drive from some time ago which I want to recover. It is a complete dump with partitions and filesystems and I'm in seek again for a tool to allow me to recover the information from that disk. I was hoping to get a working ffsrecov now under -current but probably that wouldn't have helped me either. ffsrecov under -current ist still marked broken. I have a ffsrecov binary but that one requires libc.so.4. I noteced that the gpart port (/usr/ports/sysutils/gpart) was requiring ffsrecov when I built that. Can I trick ffsrecov and links something else to libc.so.4? Anyone knowing of a way to approach this problem? I can create a vnode (mdconfig) of that disk but trying to fsck on it fails for obvious reasons, since I had to access the slices and not the whole disk dump. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ffsrecov still broken port?
On Sun, May 29, 2005 at 06:46:17PM +0930, Daniel O'Connor wrote: On Sun, 29 May 2005 18:16, Christoph P. Kukulies wrote: I can create a vnode (mdconfig) of that disk but trying to fsck on it fails for obvious reasons, since I had to access the slices and not the whole disk dump. What obvious reasons? I meant, when I have a dump image of the entire disk I cannot run fsck on the entire dump. I had to know about the partitions and the slices and extract these from the disk dump. Why fsck it at all? I would just mount it read only and then copy the essential data off it.. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ffsrecov still broken port?
On Sun, May 29, 2005 at 08:23:51PM +0930, Daniel O'Connor wrote: On Sun, 29 May 2005 19:07, Christoph P. Kukulies wrote: What obvious reasons? I meant, when I have a dump image of the entire disk I cannot run fsck on the entire dump. I had to know about the partitions and the slices and extract these from the disk dump. You can't specify /dev/md0s2a or whatever to fsck/mount? That works? OK, that would be fine. Will try that. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ttyd0/cuad0 - why is there still this duality ?
Just a question. Maybe it isn't true but to me it seems there is still this duality between ttyd and cuad serial devices. Why is that? I'm just asking because someone I was talking with about modems an comm programs was 'criticising' this fact in FreeBSD while other systems long have abandoned this dualism? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
finding alternate superblocks in ffs
Yesterday a major desaster happened: I stumbled across the power cable of my
Dell Inspiron notebook. The notebook fell to the floor. FreeBSD was running
at that time. Nothing seemed to got damaged, just a palm rest popped off.
Ah yes, the HD bay sprung off and in a moment of reflex I pushed it
in again in the running system. After that I tried to mount the
disk (which had not been mounted at that point of time). Anyway,
trying to
# fsck_ffs /dev/ad2s1e
** /dev/ad2s1e
Cannot find file system superblock
LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y
32 is not a file system superblock
89808 is not a file system superblock
179584 is not a file system superblock
269360 is not a file system superblock
359136 is not a file system superblock
448912 is not a file system superblock
538688 is not a file system superblock
628464 is not a file system superblock
718240 is not a file system superblock
808016 is not a file system superblock
20813728 is not a file system superblock
20903504 is not a file system superblock
20993280 is not a file system superblock
21083056 is not a file system superblock
21172832 is not a file system superblock
21262608 is not a file system superblock
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).
#
Any idea what I can do now?
I wrote a little program that opens /dev/ad2s1e
#include stdio.h
#include sys/param.h
#include sys/stat.h
#include sys/file.h
#include sys/time.h
#include sys/mount.h
#include sys/resource.h
#include sys/sysctl.h
#include sys/disklabel.h
#include ufs/ufs/dinode.h
#include ufs/ufs/ufsmount.h
#include ufs/ffs/fs.h
#include fcntl.h
#include ufs/ffs/fs.h
main(){
int fd;
int k,i=0;
int buf[512/(sizeof (int))];
if((fd=open(/dev/ad2s1e,O_RDONLY)) 0)
printf(error opening device\n),exit(2);
printf(opened device\n);
while(read(fd,buf,512)0){
for(k=0;k(512/(sizeof (int)));k++){
/*if(buf[k]==FS_UFS1_MAGIC)
printf(UFS1 * %d\n,i),fflush(stdout); */
if(buf[k]==FS_UFS2_MAGIC)
printf(UFS2 * %d\n,i),fflush(stdout);
i++;
}
}
}
I'm not sure whether my approach is correct.
Anyway, the blocks I find with that method
aren't recognized as superblocks either.
--
Chris Christoph P. U. Kukulies kuku_at_kukulies.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finding alternate superblocks in ffs
On Sun, Oct 31, 2004 at 03:26:04PM +0300, Maxim Konovalov wrote: [...] Any idea what I can do now? I wrote a little program that opens /dev/ad2s1e [...] I'm not sure whether my approach is correct. src/tools/tools/find-sb ls -d /usr/ports/sysutils/*ffs* Thanks. But... ffsrecov-0.5 is marked as broken: Incompatible with UFS2 header files. :-( -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finding alternate superblocks in ffs
On Sun, Oct 31, 2004 at 01:47:04PM +0100, Christoph P. Kukulies wrote: On Sun, Oct 31, 2004 at 03:26:04PM +0300, Maxim Konovalov wrote: [...] Any idea what I can do now? I wrote a little program that opens /dev/ad2s1e [...] I'm not sure whether my approach is correct. src/tools/tools/find-sb ...gave me the following: cks from last guess Found UFS1 superblock at offset 10165436416, block 19854368 Filesystem might begin at offset 10165428224, block 19854352 376192 blocks from last guess Found UFS1 superblock at offset 10358046720, block 20230560 Filesystem might begin at offset 10358038528, block 20230544 376192 blocks from last guess Found UFS1 superblock at offset 10550657024, block 20606752 Filesystem might begin at offset 10550648832, block 20606736 376192 blocks from last guess Found UFS1 superblock at offset 10743267328, block 20982944 Filesystem might begin at offset 10743259136, block 20982928 376192 blocks from last guess reached end-of-file at 10913440256 kukuboo2k# fsck_ffs -b 19854352 /dev/ad2s1e Alternate super block location: 19854352 ** /dev/ad2s1e 19854352 is not a file system superblock kukuboo2k# fsck_ffs -b 19854368 /dev/ad2s1e Alternate super block location: 19854368 ** /dev/ad2s1e ** Last Mounted on ** Phase 1 - Check Blocks and Sizes 1496 DUP I=3 1497 DUP I=3 1498 DUP I=3 CANNOT READ BLK: 21443008 CONTINUE? [yn] I got lots of these CANNOT READ BLK messages during previous attempts with different superblock numbers although they were not accompanied by kernel messages or hard errors. -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finding alternate superblocks in ffs
On Sun, Oct 31, 2004 at 02:42:18PM -0500, Brian Reichert wrote: On Sun, Oct 31, 2004 at 12:42:10PM +0100, Christoph P. Kukulies wrote: Yesterday a major desaster happened: I stumbled across the power cable of my Dell Inspiron notebook. The notebook fell to the floor. FreeBSD was running at that time. Nothing seemed to got damaged, just a palm rest popped off. Wouldn't 'newfs -n options' tell you were they would be (assuming you can recreate the options used on your FS to begin with)? you mean -N ? Indeed. That prints the superblock backups. Nice option. I was able to dd if=/dev/ad2s1e without any errors (funny that the fsck says it cannot read lotsa blocks). I moved that (10GB) dump to another machine where I might mount it on a virtual device and perform further recovery measures. Any ideas how to proceed? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
mdconfig - need some help
I'm trying to recover a filesystem. I dd'd /dev/ad2s1e into a 10 GB file and transfered it to another system. # mdconfig -a -t vnode -f ad2s1.dmp md2 # df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a257838 1687586845471%/ devfs 110 100%/dev /dev/ad0s1e257838 4752 232460 2%/tmp /dev/ad0s1f 57829724 32600992 2060235661%/usr /dev/ad0s1d25783891456 14575639%/var procfs 440 100%/proc # mount /dev/md2 /mnt mount: /dev/md2 on /mnt: incorrect super block # fsck /dev/md2 fsck: Could not determine filesystem type # fsck -t ffs /dev/md2 ** /dev/md2 Cannot find file system superblock ioctl (GCINFO): Inappropriate ioctl for device fsck_ffs: /dev/md2: can't read disk label What am I doing wrong? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: off topic - disk crash
On Fri, Mar 12, 2004 at 03:58:16PM +0100, Dag-Erling Smørgrav wrote: Clifton Royston [EMAIL PROTECTED] writes: Today an important (no backup of course) 46 GB IBM Deskstar IDE disk crashed. This specific line of drives is infamous for a failure rate that's at least a full order of magnitude above the industry average for ATA drives. Google a bit for it. Not the entire DeskStar line, just the 75GXP series. I still have several 16Gs and at least one 60GXP that have never given me any trouble, and they were fast and silent for their time, head and shoulders ahead of the competition. These days I mostly buy WD... The disk boots into FreeBSD but already at power on time the disk does seek retries or some recalibration noise. Also known as the click of death... Thanks for all the helpful tips so far. It is a DLTA 307045 (3.5) Don't know whether this is a 75GXP. I'm getting either these: ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=30583 Which don't stop the dd process. And these, ad2: FAILURE - READ_DMA status=51READY, DSC, ERROR error=40UNCORRECTABLE LBA=9156 leading to termination. Also the transfer rate is terribly slow: (80 KB/s) I was able to save 18 MB (of 46 GB) (not much so far) Any other suggestions? Could I increase the retry count? Or enforce continuation even in case of hard errors? So that with a bit of luck I could find the FS later in the dump and be able to restore at least partially some files? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: off topic - disk crash
On Sun, Mar 14, 2004 at 12:25:02PM +0100, Søren Schmidt wrote: Christoph P. Kukulies wrote: Thanks for all the helpful tips so far. It is a DLTA 307045 (3.5) Don't know whether this is a 75GXP. It is one of the dreaded models experience shows that all models after this has some kind of problems, no wonder they sold out :) I'm getting either these: ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=30583 Which don't stop the dd process. And these, ad2: FAILURE - READ_DMA status=51READY, DSC, ERROR error=40UNCORRECTABLE LBA=9156 leading to termination. Also the transfer rate is terribly slow: (80 KB/s) I was able to save 18 MB (of 46 GB) (not much so far) Any other suggestions? Use the noerror and sync flags to dd, that will get past errors and put in NULL sectors for those you cant read. However it will take a looong time and probably tear off the sorry rests of your magnetic coating on the platters :( It is now dumping and I'm at 2.7 GB meanwhile. No more errors since the last one at LBA=67 . Are these LBS identical to the block #? Maybe I'll give it another try (when this pass is through) and dump from the beginning. I'm about to get me a second identical model and maybe I then can dd the whole image including partition table so that I will not have to scan the disk for the start of the filesystems. Some time ago I wrote a little program to scan a disk for the start of a FS. Unfortunately that program is also on the crashed disk :-O -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: off topic - disk crash
On Sun, Mar 14, 2004 at 01:42:18PM +0100, Søren Schmidt wrote: Christoph P. Kukulies wrote: the whole image including partition table so that I will not have to scan the disk for the start of the filesystems. Dont get another DTLA/AVER IBM disk, you will just have the same problem again sometime in the future, stay away from IBM/Hitachi disks that is based on these models (I dont know much about the newer disks from Hitachi and frankly I wont waste my money on them to find out). Yes, I abandoned that idea now since things turn out a bit better. I have built up a recovery system with a new big disk as a FreeBSD 5.2.1 and hooked the troubled disk as in as ad2. I can mount -rf /dev/ad2s1g /mnt and find the old FS with all its entries. I copied over already some very important files and as it seems I will not be as catastrophical as I initially thought. With certain directories or files I get READ_DMA timeouts and also the system hangs totally when a certain type of error occurs. ad2: TIMEOUT - READ_DMA retryinmg (2 retries left) LBA=24703729 ad2: WARNING - READ_DMA Interrupt was seen but but timeout fired LBA=24703729 ad2: WARNING - READ_DMA Interrupt was seen but but taskqueue stalled LBA=24703729 ad0: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=9825063 What I find strange is that the failing drive on the secondary IDE channel causes the primary channel also to fail. I wonder if this has to happen or could be avoided. I can only reboot from that point on. For recovering data this additionally painful and it would be nice I could get this fixed somehow. Another question is whether the read error occurs on the actual data or only during the fstat or directory read. Is it possible to mount a FS with an alternate superblock as information base or do I have to fsck (write back to the disk risking that things get worse) -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Unix turns 0x40000000 !
Something for us all to smile or to celebrate! |Date: Fri, 09 Jan 2004 11:16:28 + (GMT) |From: Scott Howard [EMAIL PROTECTED] |Subject: Unix turns 0x4000 ! | |In just over 26 hours (Sun Jan 11 00:37:04 2004 GMT to be exact) UNIX |will bust through the 11 (binary) seconds |barrier and celebrate it's 0x4000 second birthday! | |HAPPY BIRTHDAY UNIX! :) | |This also means that we're exactly half-way between 1-Jan-1970 and |19-Jan-2038 when 32-bit Unix will die. Time for a mid-life crisis perhaps? :) | | | Scott. | | |- End forwarded message - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: total hang when cu -l /dev/cuaa0
On Fri, Oct 03, 2003 at 11:36:29PM +0200, Bernd Walter wrote: The modem coild also be something proprietary for which there is no driver available. When I run getty (or mgetty) on that port or when I do a cu -l /dev/cuaa0 the system freezes. Why do you expect anything usefull by accessing half working hardware? Well, I would expect an I/O error or no such device. Wouldn't that be at least a minimum one could expect? But a crash or hand? No. ^^ I believe I wanted to say 'hangup'. one could expect? But a crash or hand? No. Smoteihng got colbbreed drunig tpynig. ;-) You can't expect anything reliable from a device which is broken. The kernel already warned you that something seems to be questionable. In the same way you can't expect getting an IO error if someone cuts into your computer with a chainsaw - you may get one, but nobody can predict. A device disabled by the BIOS should not be accessible in any way by the kernel. It's not broken nor has anyone cut the devices with a chainsaw. I don't read dmesg before I try to open /dev/cuaa0. So an open on /dev/cuaa0 when sio is disabled in the BIOS should not result in a bad hangup. That's my point. B.Walter BWCThttp://www.bwct.de -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: total hang when cu -l /dev/cuaa0
On Fri, Oct 03, 2003 at 05:04:22PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Bernd Walter [EMAIL PROTECTED] writes: : You need a different driver for your PCI one - e.g. puc. actually, puc still uses sio/uart. puc just manages the bus resources. So puc would not help me here, wouldn't it? Where do I find puc, btw? I don't see a device puc in /sys/i386/conf/* : The modem coild also be something proprietary for which there is no : driver available. So what would be the way to go from here ? What card is supported? Or should I set out for an external modem? USB modem? I've helped people locally that have 'supported' pci modems that no longer work. Causes an interrupt storm the first time they are accessed. :-( Warner -- Chris Christoph P. U. Kukulies ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: total hang when cu -l /dev/cuaa0
On Fri, Oct 03, 2003 at 10:15:08PM +0200, Bernd Walter wrote: On Fri, Oct 03, 2003 at 08:21:28PM +0200, C. Kukulies wrote: I have disabled the SIO on my ASUS P4SX board because I have a PCI modem card inserted. But the modem card or the sio on it doesn't seem to be detected by the kernel. Instead I see two sios (sio0 and sio1) which are flagged as possibly disabled (?) - why are they seen when I disabled them in the BIOS? PCI serials shouldn't collide with legacy ones - PCI has different IO Space. Many boards don't disable interfaces completely - I wouldn't be suprised if just the irq was dropped. You need a different driver for your PCI one - e.g. puc. The modem coild also be something proprietary for which there is no driver available. When I run getty (or mgetty) on that port or when I do a cu -l /dev/cuaa0 the system freezes. Why do you expect anything usefull by accessing half working hardware? Well, I would expect an I/O error or no such device. Wouldn't that be at least a minimum one could expect? But a crash or hand? No. one could expect? But a crash or hand? No. -- Chris Christoph P. U. Kukulies ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: setting CMOS clock
On Thu, Jun 05, 2003 at 09:31:01AM -0500, Dan Nelson wrote: In the last episode (Jun 05), Christoph Kukulies said: I'm using a cron job to synchronize time against a timeserver in a local network. The timeserver is a NT box that has a DCF77 clock attached. I chose rdate (/usr/ports/sysutils/rdate) to do the synchronisation. Does this also set the CMS clock correctly or what would I have to do to set the cmos clock? The CMOS clock is automatically set whenever the system's time is updated. You might want to think about installing NTPD on your NT Ah, that's good to know. Under Linux Boxes which I had under my command in the meantime (Redhat 6.1) an additional /sbin/clock -w was necessary. machine and using NTP to synch instead. rdate can only give you time to the nearest second, and according to http://www.eecis.udel.edu/~ntp/ntpfaq/NTP-s-refclk.htm#AEN4231 , the DCF77 signal is accurate to ~3ms . Precompiled ntpd binaries for NT are available at http://www.ntp.org/links.html Thanks for the pointer. That's good to know. What NT 4.0 Resource kit is supplying calls itself TimeServ and offers time service on port 37 only. And obviously the ntpdate client times out on given this as the server. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: le0 - DE203 kernel config problem
On Wed, Apr 02, 2003 at 01:27:43PM -0500, Matthew N. Dodd wrote: On Wed, 2 Apr 2003, Christoph Kukulies wrote: I tried to get a DE203 NIC (ISA) working with 5.0R. ... Since I forgot how the card was programmed I tried and got it probed at io=0x200 ... Any clues how to proceed to get this card working? Find out what the configuration settings on the card are and use them. Trial and error is likely to produce the results you mentioned. I programmed the NIC now to 200/5 32K, C8000 , 16bit bus, not fast bus, and it gets detected but I get a kernel panic. The kernel panic occurs in process ifconfig. It seems that whenever the device is properly probed and being used, the panic occurs. I can supply more panic data, if you want. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: le0 - DE203 kernel config problem
On Thu, Apr 03, 2003 at 04:27:37AM -0500, Matthew N. Dodd wrote: On Thu, 3 Apr 2003, Christoph P. Kukulies wrote: It seems that whenever the device is properly probed and being used, the panic occurs. I can supply more panic data, if you want. I'd appreciate that. OK, I'm typing: Fatal trap 12 faul virtual address = 0x0 fault code= Supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xc8d37b10 frame pointer = 0x10:0xc8d37b2c code segment = base 0x0, limit 0xf, tzpe 0x1b = DPL 0, pres 1, def321, gran1 processor eflags = interrupt enable, res?, IOP=0 current process = 182 (ifconfig) trap number = 12 panic: page fault Sorry, couldn't read my own handwriting (resume?) in 4th but last line NIC: IO Base 200H Memmode 32K Membase C8000 IRQ 5 Fast Bus Disable 16bit Bus enabled FreeBSD 5.0-Release -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: le0 - DE203 kernel config problem
On Thu, Apr 03, 2003 at 05:48:26AM -0500, Matthew N. Dodd wrote: This should fix it: ftp://ftp.jurai.net/users/winter/patches/if_le.patch This patch worked. It makes the interface configurable and I'd bet make it work after I have configured my firewall. One thing: The patch does not pass the normal kernel compilation since it does an implicit pointer conversion, that bails out the kernel make due to the strict settings (-Werror). (line 351 of if_le.c) Thanks for the quick response this morning. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: le0 - DE203 kernel config problem
On Wed, Apr 02, 2003 at 01:27:43PM -0500, Matthew N. Dodd wrote: On Wed, 2 Apr 2003, Christoph Kukulies wrote: I tried to get a DE203 NIC (ISA) working with 5.0R. ... Since I forgot how the card was programmed I tried and got it probed at io=0x200 ... Any clues how to proceed to get this card working? Find out what the configuration settings on the card are and use them. Trial and error is likely to produce the results you mentioned. Problem is that I probably don't have a configuration disk anymore. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
