accessing NetBSD filesystem
Hello, is it possible to access Fast Filesystems from a NetBSD installation on the same disk? -Hanspeter ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: accessing NetBSD filesystem
On Dec 17 at 14:42, [EMAIL PROTECTED] spoke: On Sat, Dec 17, 2005 at 01:20:06PM +0100, Hanspeter Roth wrote: is it possible to access Fast Filesystems from a NetBSD installation on the same disk? As long as they have the same Endianess, yes. You might get some warnings about the disklabel, otherwise it should be fine. How can one activate the Fast Filesystem support? Is there a kernel module to load? Shouldn't the respective entries /dev/ad0s4* appear provided the NetBSD installation is in /dev/ad0s4? -Hanspeter ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: accessing NetBSD filesystem
On Dec 17 at 20:07, Mathieu Arnold spoke: +-Le 17/12/2005 18:10 +0100, Hanspeter Roth a dit : | On Dec 17 at 14:42, [EMAIL PROTECTED] spoke: | | On Sat, Dec 17, 2005 at 01:20:06PM +0100, Hanspeter Roth wrote: | | is it possible to access Fast Filesystems from a NetBSD installation | on the same disk? | | As long as they have the same Endianess, yes. You might get some | warnings about the disklabel, otherwise it should be fine. | | How can one activate the Fast Filesystem support? Is there a kernel | module to load? Shouldn't the respective entries /dev/ad0s4* appear | provided the NetBSD installation is in /dev/ad0s4? FFS == UFS. Fdisk shows sysid 165 (0xa5) for partition 3. This is where FreeBSD is installed. And Fdisk shows sysid 169 (0xa9) for partition 4. This is where NetBSD is installed. In /dev there are ad0s3 and ad0s3[a-g] but there is only a ad0s4. So how can filesystems of my NetBSD in ad0s4 be accessed? -Hanspeter ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ath port for 4.11?
Hello, is there a port of the ath driver for FreeBsd 4.11? -Hanspeter ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Tracing Disk Access
Hello, I have set an idle timeout for the hard-disk. But when there is no user activity there are frequent disk accesses. How can one trace disk access? I'd like to know the kind of access and on which files/directories/ nodes. I'd like to log on the console or on a memory disk file. -Hanspeter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Patch to prevent write-protected floppy from being mounted writable
On Oct 31 at 14:59, Thomas Zenker spoke:
On Tue, Oct 29, 2002 at 06:34:36PM +0100, Poul-Henning Kamp wrote:
That's a slightly more involved issue because you would have to
actually try to write to it before you find out that you can't.
for stable I have a patch, which checks during open for write
protection of the floppy if FWRITE bit is set and fails with EPERM
if this is the case. This works reliably for me. The reason I haven't
sent this patch in is, there is a possible conflict with accesses
to a second floppy disk drive at the same time. Anyway, better than
panic'ing the machine...
Actually all accesses to the controller hardware are serialized
thru a state machine fdstate. The Bad Thing is, that this state
machine is bound too tight to the strategy (i.e. you get some job
done via a buffer or nothing). Best example is the interfacing of
formatting via the B_FORMAT/B_XXX kludge. The Right Thing would
be to redesign the interface to the state machine to get jobs done
from any source (with or without buffer) and maintaining state of
write protection.
Index: sys/isa/fd.c
===
RCS file: /usr/cvs/FreeBSD/src/sys/isa/fd.c,v
retrieving revision 1.176.2.8
diff -u -r1.176.2.8 fd.c
--- sys/isa/fd.c 15 May 2002 21:56:14 - 1.176.2.8
+++ sys/isa/fd.c 31 Oct 2002 13:06:05 -
@@ -1448,6 +1448,21 @@
}
}
fd-ft = fd_types + type - 1;
+ if (flags FWRITE) { /* check for write protection */
+ int r, s, st3;
+ s = splbio();
+ set_motor(fdc, fd-fdsu, TURNON); /* select drive */
+ r = fd_sense_drive_status(fdc, st3);
+ set_motor(fdc, fd-fdsu, TURNOFF);
+ fdc-state = RESETCTLR;
+ splx(s);
+ if(r != 0)
+ return(ENXIO);
+ if (st3 NE7_ST3_WP) {
+ device_printf(fd-dev, write protected\n);
+ return(EPERM);
+ }
+ }
fd-flags |= FD_OPEN;
/*
* Clearing the DMA overrun counter at open time is a bit messy.
Cheers,
-- Thomas Zenker
Hey, exactly! Thank you!
Could the core team consider this patch to get merged into 4.8?
-Hanspeter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
removing slice chair from a running system
Hello, diskspace is getting cheaper nowadays and the number of primary slices (partitions) proportionally stays the same and several OS' love primary slices. So far I have a `master' OS which permanently occupies a slice and which remaps slice entries of `slave' OS'. But when I have slave1 OS running and want to reboot to slave2 OS I first reboot the master OS and do the remapping before I reboot slave2 OS. What happens with FreeBSD if it's slice entry is removed in the MBR before it is shutdown? Can it safely shutdown and unmount like this? The slice entries in the MBR are probably needed by the boot selector, by fdisk, by disklabel and when mounting foreign filesystems and maybe by fsck. Is a valid slice entry required by FreeBSD before/during shutdown? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Patch to allow a driver to report unrecoverable write errors to the buf layer
On Oct 18 at 20:45, Maxim Sobolev spoke: again, then again ad infinitum. The same effect if you'll mount write-protected floppy in read/write mode. As of a write-protected floppy, why is it allowd to be mounted as writeable? The mount should be degraded to readonly or rejected. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: boot selector and extended partitions
On Oct 23 at 12:49, Artem 'Zazoobr' Ignatiev spoke: Do you have Lilo running from extended partition? Linux can be run in a logical partition. But Lilo can't save the last selection as default for next boot. It's default selection must be reconfigured if the default has to be changed. Well, dunno about boot0(boot selector, if I correctly understand FreeBSD's booting process), but it was hard to me to make boot1 search for FreeBSD in extended partitions - I've had to loose some Can FreeBSD be run in a logical (extended?) partition? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: boot selector and extended partitions
On Oct 23 at 14:55, Artem 'Zazoobr' Ignatiev spoke: On Wed, Oct 23, 2002 at 12:34:32PM +0200, Hanspeter Roth wrote: Can FreeBSD be run in a logical (extended?) partition? Not out-of-box, but I've made it do so. Is it an easy patch (1h :-) ? If yes would you make it available? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ati Rage 128: Dpms suspend failes
On Oct 22 at 10:37, Andrew Gallatin spoke: I've now upgraded to XFree86-Server-4.2.1_5. dpms still does not work for me: % xset dpms force off ; xset q | tail -5 I didn't care about off. My monitor seems to behave the similar when set to `off' as when set to suspend or standby. The status LED turns yellow and the screen turns blank and recovery takes a few seconds. My application is to switch the display to the alternate host. This is working now. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ati Rage 128: Dpms suspend failes
On Oct 22 at 13:08, Andrew Gallatin spoke: Lucky you! What does pciconf -lv say about your card? none0@pci1:0:0: class=0x03 card=0x7106174b chip=0x54461002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage 128 Pro AGP 4x' class= display subclass = VGA -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Ati Rage 128: Dpms suspend failes
Hello, I have two hosts connected to one monitor. My idea is attach the display to the other host by issuing `xset dpms force suspend'. This works on one host with a Matrox Millenium. On the host with an Ati Rage 128 Pro TF it works with Netbsd, but it doesn't work with FreeBSD 4.7-Release. The screen only turns blank but the LED remains green. This is the same when issuing `xset s activate'. What could be the reason on FreeBSD 4.7 that dpms force suspend doesn't work? Installed are XFree86-Server-4.2.1_3 and XFree86-libraries-4.2.1_1.) -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ati Rage 128: Dpms suspend failes
On Oct 21 at 15:10, Andrew Gallatin spoke: Eric Anholt writes: You need XFree86-Server-4.2.1_4 or later (it's at _5 now). I'm running 4.2.1_4 and dpms does not work for me. I just grabbed some diffs from the Xfree86 cvs to bring drivers/ati/r128_driver.c up to 1.57.2.1 and drivers/ati/r128_reg.h up to 1.14 and rebuilt the my r128_drv.o module. I'll see if it works the next time X crashes.. (I'm running current, so X crashes once/day or so..) I'm usually running RELEASE. I cvsuped ports-x11 and portupgraded XFree86-Servers. Now suspend works. I haven't encountered other problems so far. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Sil vs. SiI
On Oct 11 at 09:01, Soeren Schmidt spoke: The Sil 680 does support ATAPI DMA, I'll need to dig out the older I have an Enmic installed which reports atapci1: Sil 0680 ATA133 controller port [...] Is this reported literally by the controller or is it derived from a table lookup? It seems to me that on http://www.siliconimage.com/products/sii0680.asp they are talking about SiI with a capital I as opposed to a little l. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Sil vs. SiI
On Oct 18 at 11:39, Soeren Schmidt spoke: It seems Hanspeter Roth wrote: I have an Enmic installed which reports atapci1: Sil 0680 ATA133 controller port [...] Is this reported literally by the controller or is it derived from a table lookup? From a table, seems I could use better glasses :) Now I have just rebooted and there are several clearscreens. But I thought I've seen `Sil' in the controller's Bios message. But I've seen this only with my glasses. So it may not be reliable... -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: X11 fonts?
On Oct 16 at 15:43, Julian Elischer spoke: ctwm fails to find any fonts however xfontsel CAN find those fonts Maybe you need to recall mkfontdir. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Sil 0648/0649/0680 supporting DMA for ATAPI?
On Oct 11 at 09:01, Soeren Schmidt spoke: The Sil 680 does support ATAPI DMA, I'll need to dig out the older Great! CMD64[89] to be able to give a definite answer on those.. Ok. Don't bother about the older once. The SiI 680 is probably easier to acquire anyway. Thanks. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Sil 0648/0649/0680 supporting DMA for ATAPI?
On Oct 11 at 09:01, Soeren Schmidt spoke: The Sil 680 does support ATAPI DMA, I'll need to dig out the older Would this also cover Dawicontrol Ultra DMA 133 RAID which is claimed to be built upon SiI 0680? http://www.dawicontrol.com/english/html/raid133.htm -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Sil 0648/0649/0680 supporting DMA for ATAPI?
On Oct 05 at 15:05, Soeren Schmidt spoke: Too late, I've already added support for the Sil 0680 chip in both -current and -stable. BTW it was not supported before that (not even Does any of the Sil 0648/0649/0680 support DMA for ATAPI devices, particularly for Plextor CD-R PX-W4012A? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Power Off and Ati Xpert 2000
Hello, I have an ATI Xpert 2000 Pro (Rage 128 Pro) installed. Once X windows had been started, power off (shutdown -p) doesn't work anymore. The system becomes idle after the uptime message. If shutdown -p is called without X had been started power off works. Also zzz works and the machine can be woken up by hitting a key. After once running X and then calling zzz the system can only be reset by the reset key. Superprobe yields: First video: Super-VGA Chipset: ATI (chipset unknown) (Port Probed) Signature data: 3f3f (please report) Memory: 0 Kbytes RAMDAC: Generic 8-bit pseudo-color DAC (with 6-bit wide lookup tables (or in 6-bit mode)) XFree is complaining about unresolved symbol drmFreeBufs and drmR128TextureBlit but is running somehow anyway. Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmR128TextureBlit from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Is this essential? I have 4.6.2-RELEASE, XFree86-4.1.0_12,1, XFree86-Server-4.2.0_6 and XFree86-libraries-4.1.0_1. The kernel has: device apm0at nexus? flags 0x20 What are these apm flags for? Should I select a differnt flag combination? Which one? Or can I expect upgrading XFree86 and/or XFree86-libraries to solve the problem? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: How can I access the special disk sector in kernel?
On Sep 17 at 18:25, kai ouyang spoke: I want to read the 48th sector in ad0. in kernel space, if I use the 'open' , 'lseek' , 'read' and 'close', it is wrong! Does `open' fail? How does it fail? NB: you're using charset=gb2312. Why not something like us-ascii? (This list is English.) -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
poweroff_delay, kproc_shutdown_wait
Hello, what do kern.shutdown.poweroff_delay and kproc_shutdown_wait affect? Do they have something to do with APM poweroff? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: poweroff_delay, kproc_shutdown_wait
On Sep 20 at 16:37, John Baldwin spoke: My guess is that the poweroff_delay applies to APM/ACPI power off delay. It seems these are the number of miliseconds after the uptime message. Default seems to be 5000. But why not 1000 or less? Or can it be that even 5000 is too few? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
interrupting target kernel using single sio
Hello, using a single serial cable I can pass control to the remote kgdb pressing ctl-alt-del at the target host. I'm looking for a means to interrupt the target kernel from the remote host. I got suggestions using a second serial cable or using ipgdb instead. Setting remotechat didn't help me. Is it intended to be able to interrupt the target kernel from the remote kgdb by some means at all? Or is this a wrong expectation? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: interrupting target kernel using single sio
On Sep 09 at 04:52, Julian Elischer spoke: there is the following option: # Options for serial drivers that support consoles (only for sio now): options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to #DDB, if available. it isdangerous because rebooting the local machine can en up sending a break to the remote machine. I also have: options ALT_BREAK_TO_DEBUGGER I hope it doesn't disturb. Is that to say rebooting the machine where I want to run gdb? I've rebooted this machine and nothing happened. Is that to say that the target machine ignores the break on the sio? stty values are: speed 9600 baud; 0 rows; 0 columns; lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel -ignbrk -brkint -inpck -ignpar -parmrk oflags: -opost -onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = undef; eol2 = undef; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; I tried to set brkint but after examining it again it is still cleared. Is the serial port bogus or is the serial cable an incomplete implementation? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: interrupting the remote kernel
On Sep 07 at 09:47, Christian Zander spoke: What I found to work well is remote GDB debugging with the UDP wrapper (ip-gdb), it responds to CTRL-C as expected. Is there a description available about how to configure/setup the target kernel? Where is ip-gdb available? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: interrupting the remote kernel
On Sep 06 at 17:17, Nate Lawson spoke: You can do this by connecting a second serial cable for a console between your host and target or by using the remotechat option and a single cable. Once you have the serial console, option ALT_BREAK_TO_DEBUGGER allows you to initiate a break using your terminal emulator's send break command. My remote host is a laptop with only one sio port. So if it would be possible with a single serial connection I'd appreciate it. I have played a little with remotechat but with strange results. If I set remotechat before `target remote /dev/cuaa0' the latter fails. If I set remotechat after `target remote' but before continuing ctl-alt-esc on the target host doesn't work anymore. Only garbage appears in the remote gdb. Also ctl-c in gdb doesn't achieve anything. Only after three ctl-cs I can detach gdb. I have now also added option ALT_BREAK_TO_DEBUGGER but that doesn't help either nor does the sequence CR~^b in gdb. (I want to interrupt the target host while X is active.) If the hang is not a system hang, the console break will have an effect. But if the kernel is so hung that the keyboard doesn't work, the remote serial console will not do you any better. In this case you need a box with a real console (i.e. Sun). I won't by a Sun. I'm just hoping the hang is not a system hang. :-) -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
interrupting the remote kernel
Hello, I have BREAK_TO_DEBUGGER, DDB and no DDB_UNATTENDED on the target kernel and remotebreak = 1 on the remote gdb. So I'm expecting pressing ctl-C in the remote gdb should interrupt the remote kernel as if it had encountered a breakpoint. Is my expectation right? Nothing happens when pressing ctl-C once. Pressing it twice just gives me the option to detach gdb. How can I interrupt the remote kernel without breakpoints? I'm trying to locate kernel hangings. Is it possible with this approach? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: interrupting the remote kernel
On Sep 06 at 12:11, Julian Elischer spoke: hit CTL_ALT_ESC on it's keyboard... Doing this on the remote host (running gdb) tells me `No debugger in kernel'. Doing this on the target host passes control to the remote gdb. But I want to pass control to the remote debugger by issuing the interrupt command on the _remote_ host (in gdb). or do: sysctl debug.enter_debugger=gdb Doing this on the target host also passes control to the remote gdb. But I want to be able to pass control to the debugger when the target kernel `hangs', that is when no `ctl-alt-f1', `ctl-alt-del' has any effect. I thought that remotebreak on the remote gdb should allow me this. But it seems to be something else... -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
