Re: junior-hacker task: "prepdisk"
In message <[EMAIL PROTECTED]>, Bruce Evans writes: >>>: It seems that our new boot blocks doesn't like the taste of disks >>>: prepared according to the meagre information we have in the handbook. >>> >>>How does this script differ from 'disklabel -w wd0 auto'? It does do >>>the fdisk stuff (your script, not the disklabel command). >> >>It differs in that you can boot from the disk afterwards with my script, >>you cant with disklabel -w wd0 auto. > >That may be because you forgot to supply the -r or -B args to disklabel, >[...] No it is because the fool BIOS belives the 5 in the MBR. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: "prepdisk"
>>: It seems that our new boot blocks doesn't like the taste of disks >>: prepared according to the meagre information we have in the handbook. >> >>How does this script differ from 'disklabel -w wd0 auto'? It does do >>the fdisk stuff (your script, not the disklabel command). > >It differs in that you can boot from the disk afterwards with my script, >you cant with disklabel -w wd0 auto. That may be because you forgot to supply the -r or -B args to disklabel, or forgot to edit the label using disklabel -e. I think no editing is required to boot from the 'c' partition (the missing d_type initialisation doesn't matter because the `d_type != DTYPE_SCSI' case defaults to DTYPE_ESDI (aka IDE)). The 'a' partition produced by `disklabel -Brw wd0 auto ' is obviosuly unbootable and unnewfsable, etc., since it is empty. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: "prepdisk"
In message <[EMAIL PROTECTED]>, Warner Losh writes: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes: >: It seems that our new boot blocks doesn't like the taste of disks >: prepared according to the meagre information we have in the handbook. > >How does this script differ from 'disklabel -w wd0 auto'? It does do >the fdisk stuff (your script, not the disklabel command). It differs in that you can boot from the disk afterwards with my script, you cant with disklabel -w wd0 auto. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: "prepdisk"
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes: : It seems that our new boot blocks doesn't like the taste of disks : prepared according to the meagre information we have in the handbook. How does this script differ from 'disklabel -w wd0 auto'? It does do the fdisk stuff (your script, not the disklabel command). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
Peter Mutsaers wrote: > > Hello, > > After Linux I gave FreeBSD a try again, when I saw some improvements > to APM had been committed. > > I hoped for a real suspend mode, but alas. Now I'm wondering what > makes the difference, and whether I could do it myself. > > Let me explain: I run my (desktop) computer in the living room. I > don't want to shut it down all the time, but it must be 100% quiet > when I'm not using it. > > In Linux, when suspend mode is activated (either through a short press > on the power button or by the (BIOS) timer ), the disks also spin down > (immediately, not waiting for their timer, which I disabled) and also > the CPU fan and/or the FAN of the box switches off. > > In FreeBSD, when I activate suspend mode, I see the light on my > computer blinking, indicating it has gone into suspend mode, but still > there is no reduction in noise whatsoever. The disks keep spinning, > the CPU fan (or whatever) too. I could activate the BIOS spindown > timer on the HDD's, but I'd rather not (since then I also get > spindowns while I'm normally working with the computer) but still the > other fan will always continue to run. > > What can I do to change this behaviour? Can anyone explain what Linux > (or Win95 for that matter) are doing to make it 100% quiet in suspend > mode? Then I could give it a try to have FreeBSD do the > same. Currently this prevents me from using FreeBSD alas. Have you looked at PAO at all? http://www.jp.freebsd.org/PAO/ I've got a -current machine (no cvsups in a few months) that wakes up immediately after suspending. (sleeps 0 seconds) -- Eric Hodel [EMAIL PROTECTED] "They cook your gonies" -Terry Lambert's uncle on why he doesn't have a microwave To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
In article [EMAIL PROTECTED]> you write:
>In FreeBSD, when I activate suspend mode, I see the light on my
>computer blinking, indicating it has gone into suspend mode, but still
>there is no reduction in noise whatsoever. The disks keep spinning,
>the CPU fan (or whatever) too. I could activate the BIOS spindown
>timer on the HDD's, but I'd rather not (since then I also get
>spindowns while I'm normally working with the computer) but still the
>other fan will always continue to run.
>
>What can I do to change this behaviour? Can anyone explain what Linux
>(or Win95 for that matter) are doing to make it 100% quiet in suspend
>mode? Then I could give it a try to have FreeBSD do the
>same. Currently this prevents me from using FreeBSD alas.
FreeBSD's APM suspend works by sending the BIOS a suspend event
for all BIOS managed devices, and the BIOS is supposed to put
all devices under it's control into the "low-power suspend" state.
I'd guess that this isn't the same as "off". You can't tell the
BIOS to turn off all devices, you need to specify which devices
to turn off.
You could play around with adding something like this to
apm_suspend_system (for your hdd:):
sc->bios.r.eax = (APM_BIOS << 8) | APM_SETPWSTATE;
sc->bios.r.ebx = 0x02ff;
sc->bios.r.ecx = state ? PMST_APMENABLED : PMST_OFF;
sc->bios.r.edx = 0;
if (apm_bioscall())
printf("Failed to turn off HDD: errcode = %d\n",
0xff & (sc->bios.r.eax >> 8));
Of course, you'd probably also need a corresponding "turn on", call
somewhere. As for your fan, I'm not sure what the deviceid for the
fan would be, the "0x02ff" above means "all 2ndary storage devices".
Perhaps "0x80FF", for all OEM devices.
At the moment, there isn't the ability to control individual devices,
but at some point, I can see this being added to the new-bus architecture;
each device can register callbacks for various power management events.
--
Jonathan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
SMP and threads...
I have a threaded appilcation that is only running on one processor. I remember there was discussion about this in the past, and there was a solution, I think it involved a patch. Any pointers? -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
recent apm changes
Hello, After Linux I gave FreeBSD a try again, when I saw some improvements to APM had been committed. I hoped for a real suspend mode, but alas. Now I'm wondering what makes the difference, and whether I could do it myself. Let me explain: I run my (desktop) computer in the living room. I don't want to shut it down all the time, but it must be 100% quiet when I'm not using it. In Linux, when suspend mode is activated (either through a short press on the power button or by the (BIOS) timer ), the disks also spin down (immediately, not waiting for their timer, which I disabled) and also the CPU fan and/or the FAN of the box switches off. In FreeBSD, when I activate suspend mode, I see the light on my computer blinking, indicating it has gone into suspend mode, but still there is no reduction in noise whatsoever. The disks keep spinning, the CPU fan (or whatever) too. I could activate the BIOS spindown timer on the HDD's, but I'd rather not (since then I also get spindowns while I'm normally working with the computer) but still the other fan will always continue to run. What can I do to change this behaviour? Can anyone explain what Linux (or Win95 for that matter) are doing to make it 100% quiet in suspend mode? Then I could give it a try to have FreeBSD do the same. Currently this prevents me from using FreeBSD alas. Thanks, -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know [EMAIL PROTECTED] | the Netherlands| what I'm doing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Promise/IDE
It seems Mike Hoskins wrote:
> and I just installed a Promise Ultra66. Here's my relevant kernel config
> stuff (following LINT's example):
>
> pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9
Thats the promise controller, try the ata driver instead an use the
following patch, let me know if it works...
Index: ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.15
diff -u -r1.15 ata-all.c
--- ata-all.c 1999/06/25 09:02:56 1.15
+++ ata-all.c 1999/08/05 18:14:11
@@ -184,6 +184,8 @@
return "Intel PIIX4 IDE controller";
case 0x4d33105a:
return "Promise Ultra/33 IDE controller";
+ case 0x4d38105a:
+ return "Promise Ultra/66 IDE controller";
case 0x522910b9:
return "AcerLabs Aladdin IDE controller";
#if 0
@@ -241,7 +243,7 @@
#endif
/* if this is a Promise controller handle it specially */
-if (type == 0x4d33105a) {
+if (type == 0x4d33105a || type == 0x4d38105a) {
iobase_1 = pci_read_config(dev, 0x10, 4) & 0xfffc;
altiobase_1 = pci_read_config(dev, 0x14, 4) & 0xfffc;
iobase_2 = pci_read_config(dev, 0x18, 4) & 0xfffc;
@@ -318,7 +320,7 @@
if (!irq)
printf("ata_pciattach: Unable to alloc interrupt\n");
- if (type == 0x4d33105a)
+ if (type == 0x4d33105a || type == 0x4d38105a)
bus_setup_intr(dev, irq, INTR_TYPE_BIO, promise_intr, scp, &ih);
else
bus_setup_intr(dev, irq, INTR_TYPE_BIO, ataintr, scp, &ih);
@@ -342,7 +344,7 @@
int rid = 0;
void *ih;
- if (type != 0x4d33105a) {
+ if (type != 0x4d33105a && type != 0x4d38105a) {
irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0, 1,
RF_SHAREABLE | RF_ACTIVE);
if (!irq)
Index: ata-dma.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v
retrieving revision 1.8
diff -u -r1.8 ata-dma.c
--- ata-dma.c 1999/05/26 23:01:57 1.8
+++ ata-dma.c 1999/08/05 18:14:55
@@ -168,6 +168,7 @@
break;
case 0x4d33105a: /* Promise Ultra/33 / FastTrack controllers */
+case 0x4d38105a: /* Promise Ultra/66 controllers */
devno = (scp->unit << 1) + (device ? 1 : 0);
if (udmamode >=2) {
printf("ata%d: %s: setting up UDMA2 mode on Promise chip ",
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic plus advice needed
> > There aren't too many systems any more that don't have an additional > > 30 MB for the time it takes to build the kernel, and it solves a > > whole lot of potential problems. > > It does cause problems when you keep the kernels for 8 different machines > in one /usr/src. You are obiviously know what you are doing (since you are doing this AND running -CURRENT to boot). So you can easily make the partition you are using for this larger when you create it. Also since you have 8 different machines (presumable of differe types, or you'd use the same kernel on all of them), you have a little $$ that you could buy a cheap 4gig drive just for kernel building. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "w" date
> I don´t know, which daemon writes to /var/run/utmp. > > Maybe I should notice, that I´m logged in via ssh. Was this version of ssh built on a 4.0 system, or 2.x? Usernames went from 8 chars to 16 chars. I was experiencing simular problems when I upgraded from 2.2.x to 3.0. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Packages
> 1) Can I use the 3.2 packages with FreeBSD 4.0 or am I doing a stupid thing? Kinda. We provide different versions at ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ because of there are some library difference between 3.x and 4.0. Not to mention anything that grubs around in the kernel. > 2) In case I decide downloading the 4.0-current packages, how can I modify > the INDEX file given I'd have to split the packages on a couple of CDs? No > Rockridge extensions, please: I don't know how to use it. AFAIK, you will need Rockridge extensions if you want any of the automatic dependencies loading to work. It isn't that hard. Just use the "-r" switch to ``mkisofs'' when you burn the image. > BTW, the dependencies among packages are quite difficult to be guessed > off-line :-) The INDEX files tells the dependencies. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Promise/IDE
Hello, Just cvsup'd and running... FreeBSD snafu.adept.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Aug 5 04:51:08 PDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/SNAFU i386 I have the following onboard... ide_pci0: at device 7.1 on pci0 and I just installed a Promise Ultra66. Here's my relevant kernel config stuff (following LINT's example): controller wdc0at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 controller wdc2at isa? port 0 irq ? flags 0xa0ffa0ff disk wd4 at wdc2 drive 0 disk wd5 at wdc2 drive 1 controller wdc3at isa? port 0 irq ? flags 0xa0ffa0ff disk wd6 at wdc3 drive 0 disk wd7 at wdc3 drive 1 Dmesg shows my onboard controller, and all attached devices. Nothing seems to be shown for the Promise card, or the attached drives (two IBM 10GXPs)... Here's dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Aug 5 04:51:08 PDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/SNAFU Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 299942803 Hz CPU: Pentium II (299.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127565824 (124576K bytes) Pentium Pro MTRR support enabled Probing for PnP devices: CSN 1 Vendor ID: CTL00c7 [0xc7008c0e] Serial 0x1c422c08 Comp ID: PNPb02f [0x2fb0d041] npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 9 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 chip1: irq 11 at device 7.2 on pci0 chip2: at device 7.3 on pci0 pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9 xl0: <3Com 3c900-COMBO Etherlink XL> irq 11 at device 16.0 on pci0 xl0: Ethernet address: 00:60:08:a0:55:09 xl0: selecting 10baseT transceiver, half duplex isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordy wcd0: drive speed 4133 - 4134KB/sec, 256KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 changing root device to wd0s1a I can decipher my AWE64 clearly from pnpinfo, but that's about it, here's the output: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00c7 (0xc7008c0e), Serial Number 0x1c422c08 PnP Version 1.0, Vendor Version 16 Device Description: Creative AWE64 PnP *** Small Vendor Tag Detected Logical Device ID: CTL0045 0x45008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7
Re: Assembler capable of supporting 3dnow!
In <[EMAIL PROTECTED]>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > I'm messing around with the latest mesa and have discovered (suprise)that our > assembler doesn't support 3dnow instructions. Are there any plans to update to > a version of binutils that does? Linux's stuff appears to support it. > A build-time dependecy on ports/devel/nasm? Martin -- Martin Cracauer <[EMAIL PROTECTED]> http://www.bik-gmbh.de/~cracauer/ "Where do you want to do today?" Hard to tell running your calendar program on a junk operating system, eh? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic plus advice needed
On Thu, Aug 05, 1999 at 10:10:49AM +0930, Greg Lehey wrote: > > So... IMHO, if we can fix this as well, it would be worth it for all > > the people who get core dumps but didn't build debug kernels. > > Do you disagree? > > I disagree that this should even be necessary. This kind of detail > was exactly the reason why I put the short-lived default debug kernel > into config. There aren't too many systems any more that don't have > an additional 30 MB for the time it takes to build the kernel, and it > solves a whole lot of potential problems. It does cause problems when you keep the kernels for 8 different machines in one /usr/src. I've never had any problems with -g generating different code as long as the stuff in vers.c doesn't change length. Being able to reproduce a kernel with debugging symbols seems like a reasonable aim to me. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "w" date
Thus spake Alexander Langer ([EMAIL PROTECTED]):
> root p0 0.10 04Nov35 - (w)
> bash-2.02# date
> Tue Aug 3 14:26:47 CEST 1999
> Take a look at the last one: p0. I logged in ~5 min before.
> The date confuses me.
I took a further look into the sources. usr.bin/w/* is not the
problem, I´d say. It probably read the time wrong from /var/run/utmp
if ((ut = fopen(_PATH_UTMP, "r")) == NULL)
err(1, "%s", _PATH_UTMP);
for (nusers = 0; fread(&utmp, sizeof(utmp), 1, ut);) {
...
I don´t know, which daemon writes to /var/run/utmp.
Maybe I should notice, that I´m logged in via ssh.
Any ideas?
BTW: My machine, that is some newer, told me a login @ 01Jan71 (or
72 or 70? I forgot, but it doesn´t matter. it´s wrong at all)
just a minute ago. That´s also wrong but exactly the opposite of year
2035.
Now, it tells me something wrong, AGAIN. But not so worse at all:
I typed the following without any breaks, it took only ~5 seconds.
bash-2.02# ssh cichlids
root@cichlids's password:
You have mail.
bash-2.02# date
Do 5 Aug 1999 12:02:59 CEST
bash-2.02# w
12:02pm up 1:29, 2 users, load averages: 1.13, 1.11, 1.08
USER TTY FROM LOGIN@ IDLE WHAT
alex v7 -10:36am 1:26 -bash (bash)
ttyp4 -12:00pm 1:28 -
bash-2.02#
Strange. the login is at 12:02 and not at 12:00 !
What´s wrong with /var/run/utmp?
Alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Packages
I recently downloaded and installed the most recent FreeBSD 4.0 -CURRENT, skipping the packages' download because of the size (I have the latest 3.2 CDROMs). The problem is that some packages (linux_base, in example), are missing from the 3.2 CDs and also that every time FreeBSD 4.0 complains about a previous release packages being used. I'm curios about packages compatibility, 'cause they look almost the same comparing 3.2 and 4.0 1) Can I use the 3.2 packages with FreeBSD 4.0 or am I doing a stupid thing? 2) In case I decide downloading the 4.0-current packages, how can I modify the INDEX file given I'd have to split the packages on a couple of CDs? No Rockridge extensions, please: I don't know how to use it. I don't have any internet link at home on the FreeBSD machine, so I can't simply download what I need when I need it. I have to do that beforehand, then burn a CD and fetch from it. No DOS partitions. BTW, the dependencies among packages are quite difficult to be guessed off-line :-) Thanks in advance, Corrado To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
