Re: bogus microuptime() warnings?
John Baldwin <[EMAIL PROTECTED]> writes: > On 09-Jan-01 Dag-Erling Smorgrav wrote: > > Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" > > with the latest -CURRENT than I used to... > Which soundcard? SoundBlaster Vibra 16X. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
device driver oddities. (fwd)
I am using 5.0-Current (actually intended to get 4.2-Stable, but anyways)... It appears there is a problem with the way the system is dealing with the mouse, keyboard, and sound devices. My source tree was updated via CVSup just a day or so ago, and compiled on that day, with no errors. Kernel has since been re-compiled for my usual settings (changes in the way sound devices are handled was noted and adapted), and of course to trim out some unneeded stuff (SCSI and RAID drivers, etc) Consider this line from the obvious Beach Boys hit (an mp3 playing under mpg123 0.59r): "I wish they all could be california... girls..." At one point, the sound, mouse, and keyboard all stalled in the middle of the word "be". It sounded like: "I wish they all could brbrbrbrbrbrbrbrbebebe california... girls..." At that moment, the mouse stops moving, for as long as the sound stalls, and the keyboard will insert a garbage character to whatever application I am focused on, if I happen to be pressing a key at that moment. This happens frequently when I move the mouse around, and moreso if something else occurs along with that movement, such as a focus change from one window to another. Occasionally, typing on the keyboard also induces a stall in the sound and mouse drivers. Machine: Compaq Presario 4764. P166 MMX, 24 Megs RAM. Sound: ESS Audiodrive 18xx series on the motherboard, non PnP. Mouse: A typical IBM three-button wheel mouse. Environment: X Free86 3.3.6, Gnome/Sawmill. (Problem is not limited to X, it also happens at the consolem, before X is even started). To me this looks like an IRQ handling problem, but I am not certain. On my hobby platform, IRQ software malfunctions would be the first thing to look for if such a problem were to occur. My applications (mostly ports and packages) from 4.1 have not yet been updated. This same problem also exists in 4.2-Release as obtained via kern.flp and mfsroot.flp images for 4.2-Release, FTP Install. There have been no hardware changes made in several months. In 4.1-Release (also obtained via FTP Install), this problem does NOT exist. I also verified that the problem goes away when 4.1 is present by "downgrading" back to 4.1-Release from 4.2-Release (using a rather brute-force method to insure a clean install). In all cases I have of course obtained kernel source during the install, and always compile it using the same settings (or equivalent, as with sound parameters in 5.0-C compared to 4.1-R). After mentioning my guess about possible IRQ problems in #freebsdhelp on IRC/EFnet, someone suggested I take a look at the output of vmstat -i and dmesg. Here are those outputs: Output from vmstat: interrupt total rate stray irq0 10 stray irq6 10 stray irq7 10 stray irq15 10 ata0 irq14 1095931 ata1 irq15 100 fdc0 irq6 10 atkbd0 irq11445611 psm0 irq12 1078321 sio0 irq4 10 sbc0 irq5 1051032 12 ep0 irq3407210 clk irq0 8750437 99 rtc irq8 11197886 127 lpt0 irq7 2455072 Total21647585 247 Output from dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #3: Tue Jan 9 03:04:54 CST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/FLUTE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 167046462 Hz CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping = 4 Features=0x8001bf real memory = 25165824 (24576K bytes) config> di sio1 config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 20930560 (20440K bytes) Preloaded elf kernel "kernel" at 0xc039e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039e09c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1000-0x101f irq 11 at device 1.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 2.0 (no driver attached) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at
device driver oddities
Addendum to previous message describing what seems like IRQ problems... One thing I forgot to mention, and which is the whole reason I decided to send this to the list, is that the ESS Audiodrive does not play in Stereo under 4.2-Release or 5.0-Current. Sound is in mono, out of both speakers. The music being tested shows very clear, clean stereo separation under 4.1-Release. The upgrade to 4.2-Release was done via Sysinstall, which I eventually downgraded back to 4.1-Release via the brute force "delete-everything-except-/pub-and-/proc-and-do-an-FTP-Install". At that point (after I compiled my kernel as usual), sound returned to normal. The upgrade path from 4.1-Release to 5.0-Current was of course done via CVSup/make buildworld/make installworld followed by a normal kernel recompile to get my preferred settings into place. -- ___ _ _ | _///@@@| | | [EMAIL PROTECTED] /'//ZZ@@| | | |'''/|'/@7 | | http://home.kscable.com/natedac |`'| `~~' | | | `| .--. | | C64/C128 - What's *YOUR* hobby? | `\|___\ | | \_ | | |___ \_| _| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: securelevel and sysctl
On Wed, 10 Jan 2001, Tomasz Paszkowski wrote: > > I'am working on module, which catches __sysctl system call, and on > securelevel grater than 3, refuse any changes of sysctl oids. Are there any You might want to take a look at SPY module (http://people.freebsd.org/~abial/spy). > problems, which might happen after blocking sysctl oids change ? > AFAIR there is no such application running in user Space,which requires > ability to change sysctl oids,is there ? Several oids are changed on system startup. Others are accessed read-only to provide system information. > Secondly I'was thinking about oids,which are needed for user space aplications > to work. I figured out,that vi use some (I didn't check which one) oid on > startup, so is there a list of oids used by user space applications ? Well, it depends on what the user applications want to access, doesn't it :-). Theoretically, this list could be all oids. Practically, it depends on the user applications that are installed... Andrzej Bialecki // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
On Tue, Jan 09, 2001 at 04:52:29PM -0800, Matt Dillon wrote: > If you just hit the up or down arrow without having partial text on the > line, it works just like normal history. Once you start using it, > you will never be able to go back. As a side note - this is usually mapped to escpae-p - it is very useful. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rebuilding sendmail without building world
How do I remake sendmail without making a buildworld? I'm experimenting with cyrus-sasl and sendmail. cd /usr/src/contrib/sendmail && make doesn't work, because there is no Build there. I could import the original source from sendmail.org, but I'd rather not; I'd prefer using the paths and flags from buildworld. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rebuilding sendmail without building world
On Wed, Jan 10, 2001 at 03:22:30PM +0100, Leif Neland wrote: > How do I remake sendmail without making a buildworld? > > I'm experimenting with cyrus-sasl and sendmail. > > cd /usr/src/contrib/sendmail && make > > doesn't work, because there is no Build there. > > I could import the original source from sendmail.org, but I'd rather > not; I'd prefer using the paths and flags from buildworld. > (cd /usr/src; grep NO_SENDMAIL */Makefile) should give you an idea. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pmtimer
Hi, > I'm not sure what pmtimer is supposed to do. Isn't it supposed to give > support for the broken statclock on laptops? I saw my friend running 4.1 > with some patches that allowed him to use the statclock (and the rtc > device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to > do anything; and I couldn't find a manpage on it Please refer to src/UPDATING for -current. The new pmtimer device is necessary for laptops. Failure to include the device will cause suspended laptops losing time when they resume. Currently pmtimer won't solve the broken statclock problem... The timer related code at suspend/resume time have been moved from APM to pmtimer so that ACPI (includes new power management system) use pmtimer at sleep/wakeup time as well. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fan speed control sony vaio lx800 slimtop
> Note also that Scott Long ([EMAIL PROTECTED]) is also working on this, > you will want to check with him to work out where he's up to... OK, I intended to try acpi_thermal hacking for the next target, now I can be a tester and feed back something for Scott's hack :-) Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rebuilding sendmail without building world
On Wed, 10 Jan 2001, Ruslan Ermilov wrote: > On Wed, Jan 10, 2001 at 03:22:30PM +0100, Leif Neland wrote: > > How do I remake sendmail without making a buildworld? > > > > I'm experimenting with cyrus-sasl and sendmail. > > > > cd /usr/src/contrib/sendmail && make > > > > doesn't work, because there is no Build there. > > > > I could import the original source from sendmail.org, but I'd rather > > not; I'd prefer using the paths and flags from buildworld. > > > (cd /usr/src; grep NO_SENDMAIL */Makefile) should give you an idea. > Yes, the idea I got was: cd /usr/src/usr.sbin/sendmail && make && make install Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fan speed control sony vaio lx800 slimtop
> > Note also that Scott Long ([EMAIL PROTECTED]) is also working on this, > > you will want to check with him to work out where he's up to... > > OK, I intended to try acpi_thermal hacking for the next target, now > I can be a tester and feed back something for Scott's hack :-) Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump that I submitted for the ACPI collection. I'm not sure where that collection is - I don't see it off www.jp.freebsd.org/acpi, if anyone wants to see that .asl file I can put it somewhere public. I also haven't found any "PNP" devices corresponding to an ACPI fan (I forget the exact number) during boot -v. Would I have to do anything special to see it? If anyone has any other ideas of what to do let me know - I'm wondering if throttling down the CPU turns down the fan. In the meantime I've made terrific progress by putting "dynamat" sound absorbing material on the bottom of the plastic drum-like base of the Vaio, it is quieter and now my desk doesn't vibrate when the fan is on high. (www.dynamat.com, new web site in progress) Next I'll open it up and put dynamat on the inside of the plastic - I assume most heat loss is by convection and this won't make much difference. Once I do get the fan throttling working I'll have a real quiet system. Peter -- Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
unsubscribe freebsd-current
Please Take me off of your list. THANK YOU unsubscribe freebsd-current > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fan speed control sony vaio lx800 slimtop
[Cc trimed] Quick news from acpi-jp :-) > Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump > that I submitted for the ACPI collection. I'm not sure where that > collection is - I don't see it off www.jp.freebsd.org/acpi, if > anyone wants to see that .asl file I can put it somewhere public. Sorry, project page haven't been updated for a long time. CVSuping ACPI data collection is also with following supfile. - *default host=cvsup.jp.FreeBSD.org *default base=/home/iwasaki/ACPI-data # XXX *default prefix=/home/iwasaki/ACPI-data # XXX *default release=cvs tag=. *default delete use-rel-suffix *default compress jp-acpi-data - Also cvsweb at http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
: :On Tue, Jan 09, 2001 at 04:52:29PM -0800, Matt Dillon wrote: : :> If you just hit the up or down arrow without having partial text on the :> line, it works just like normal history. Once you start using it, :> you will never be able to go back. : :As a side note - this is usually mapped to escpae-p - it is very useful. : : David. Yes, but not as a multi-key keystroke. Up-arrow is a thousand times easier to hit. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pmtimer
Yeah, that's what I thought. A while back someone sent me some patches that fix the broken statclock and make it work on laptops, I can't remember his name right now. However those patches are against FreeBSD 4.1-RELEASE, and I'm not sure if they'd work for -CURRENT. I suppose I could do without the statclock for now, but it'd be nice to have :-) = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Wed, 10 Jan 2001, Mitsuru IWASAKI wrote: > Hi, > > > I'm not sure what pmtimer is supposed to do. Isn't it supposed to give > > support for the broken statclock on laptops? I saw my friend running 4.1 > > with some patches that allowed him to use the statclock (and the rtc > > device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to > > do anything; and I couldn't find a manpage on it > > Please refer to src/UPDATING for -current. > The new pmtimer device is necessary for laptops. Failure to > include the device will cause suspended laptops losing time > when they resume. > > Currently pmtimer won't solve the broken statclock problem... > The timer related code at suspend/resume time have been moved from APM > to pmtimer so that ACPI (includes new power management system) use > pmtimer at sleep/wakeup time as well. > > Thanks > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADSUP! change to atapi-cd driver and burncd
The changes require that kernel and burncd are in sync... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/boot/kernel/kernel: swap_pager_getswapspace: failed
I am starting to get the following error. I've never seen it before and don't really understand why it should fail. Where should I start looking for the problem? /boot/kernel/kernel: swap_pager_getswapspace: failed This seems to have started in the last week. Thanks, ed -- EnContacto.Net - InternetSalon.Org - CafeMania.Net -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fan speed control sony vaio lx800 slimtop
> Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump > that I submitted for the ACPI collection. I'm not sure where that > collection is - I don't see it off www.jp.freebsd.org/acpi, if > anyone wants to see that .asl file I can put it somewhere public. Is there a thermal zone *anywhere* (ACPI 2.0 moves it into _SB_, for example). > Would I have to do anything special to see it? If anyone has any > other ideas of what to do let me know - I'm wondering if throttling > down the CPU turns down the fan. It's possible that the EC is solely responsible for the fan, or that Sony decided in their infinite wisdom to do it all in a driver somewhere. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: /boot/kernel/kernel: swap_pager_getswapspace: failed
On 10-Jan-01 Edwin Culp wrote: > I am starting to get the following error. I've never seen it before and > don't > really understand why it should fail. Where should I start looking for the > problem? > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > This seems to have started in the last week. > > Thanks, You are running out of swap space. Run fewer programs, buy more memory, add more swap space, or a combo of the three. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: /boot/kernel/kernel: swap_pager_getswapspace: failed
Thanks, John. I wish that it were that simple, that is if I am interpreting pstat and vmstat correctly. /root # pstat -s Device 1K-blocks UsedAvail Capacity Type /dev/rad0s2b 2620160 262016 0%Interleaved I have two another disks that aren't being used with an additional 512M of swap each that are not being mounted because this machine isn't carrying much load right now. /root # vmstat procs memory pagedisks faults cpu r b w avm fre flt re pi po fr sr ad0 ad2 in sy cs us sy id 0 2 0 118972 15100 849 0 1 0 834 4 0 0 414 3136 599 33 8 59 It really seems to be related to my upgrading to XFree86-4.0.2_3 and KDE-2. If no one else is seeing it, it isn't critical and with patience it'll show itself with a little time. Thanks, ed Quoting John Baldwin <[EMAIL PROTECTED]>: > > On 10-Jan-01 Edwin Culp wrote: > > I am starting to get the following error. I've never seen it before and > > don't > > really understand why it should fail. Where should I start looking for > the > > problem? > > > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > > > This seems to have started in the last week. > > > > Thanks, > > You are running out of swap space. Run fewer programs, buy more memory, > add > more swap space, or a combo of the three. > > -- > > John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > -- EnContacto.Net - InternetSalon.Org - CafeMania.Net -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem installing on T20
Wm Brian McCane wrote: > > I have an IBM T20 laptop that I want to run FreeBSD on. I have run [etc] You have a problem which is technically called an "IBM laptop". IBM, in their infinite wisdom, decided to hibernate on the first partition it doesn't recognize (hypothesis #1) or on the first partition identified as 165 decimal (hypothesis #2). Whatever the case is, when the shitty thing boots, the BIOS checks said partition to see if the system had hybernated. Upon finding stuff there (the FreeBSD partition), it does something which screws the system and locks up. One possible fix to enable normal operation is creating an hybernate partition explicitly and a FreeBSD partition *after* that. You should be able to find out from IBM how to create an hybernate partition. If not, check the next fix. Another fix some people have resorted to is returning the laptop for a refund and, optionally, never again buying from IBM. You might also explain to them why you are doing so, but IBM does not support FreeBSD, so, technically speaking, they are not required to make it compatible with FreeBSD. Legend goes that Linux had the same problem at first (which is the origin of hypothesis #1) and got fixed by having IBM add their partition numbers to to BIOS as recognized partition numbers. It's beyond my ability to understand why they refuse to fix the #%'&%$%'& BIOS so it would use a SAFE hybernate partition number (like the one they used before). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: /boot/kernel/kernel: swap_pager_getswapspace: failed
On 11-Jan-01 Edwin Culp wrote: > Thanks, John. I wish that it were that simple, that is if I am interpreting > pstat and vmstat correctly. It might be asking for more swap space than you have. I.e., it may need mroe than 256 meg of swap. :( > > /root # pstat -s > Device 1K-blocks UsedAvail Capacity Type > /dev/rad0s2b 2620160 262016 0%Interleaved > > I have two another disks that aren't being used with an additional 512M of > swap > each that are not being mounted because this machine isn't carrying much > load > right now. > > /root # vmstat > procs memory pagedisks faults cpu > r b w avm fre flt re pi po fr sr ad0 ad2 in sy cs us sy id > 0 2 0 118972 15100 849 0 1 0 834 4 0 0 414 3136 599 33 8 59 > > It really seems to be related to my upgrading to XFree86-4.0.2_3 and KDE-2. > If > no one else is seeing it, it isn't critical and with patience it'll show > itself > with a little time. > > Thanks, > > ed > > Quoting John Baldwin <[EMAIL PROTECTED]>: > >> >> On 10-Jan-01 Edwin Culp wrote: >> > I am starting to get the following error. I've never seen it before and >> > don't >> > really understand why it should fail. Where should I start looking for >> the >> > problem? >> > >> > /boot/kernel/kernel: swap_pager_getswapspace: failed >> > >> > This seems to have started in the last week. >> > >> > Thanks, >> >> You are running out of swap space. Run fewer programs, buy more memory, >> add >> more swap space, or a combo of the three. >> >> -- >> >> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> > > > > -- > EnContacto.Net - InternetSalon.Org - CafeMania.Net > -- -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem installing on T20
"Daniel C. Sobral" wrote: > Wm Brian McCane wrote: > > > > I have an IBM T20 laptop that I want to run FreeBSD on. I have run > > [etc] > > You have a problem which is technically called an "IBM laptop". IBM, in > their infinite wisdom, decided to hibernate on the first partition it > doesn't recognize (hypothesis #1) or on the first partition identified > as 165 decimal (hypothesis #2). Whatever the case is, when the shitty > thing boots, the BIOS checks said partition to see if the system had > hybernated. Upon finding stuff there (the FreeBSD partition), it does > something which screws the system and locks up. Well, I can definatively answer one thing. If you change the partition ID to 166 and change the boot code to boot from that, then the laptops are just happy. Paul Saab has an A20 or A21 something that has this problem and he changed nothing but the partition ID to 166 and it solved the problem. As far as I'm concerned, this pretty much clinches the need to provide an alternate partition id booting capability so that people can enter 166 (openbsd) or 175 (believed free) when sysinstall is doing the setup and the bootblocks will just deal with it. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem installing on T20
Wm Brian McCane wrote: > > I have an IBM T20 laptop that I want to run FreeBSD on. I have run BTW, I just found that this is covered on the FAQ. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem installing on T20
%Wm Brian McCane wrote: %> %> I have an IBM T20 laptop that I want to run FreeBSD on. I have run % %BTW, I just found that this is covered on the FAQ. Otay, I must be blind. Where in http://www.freebsd.org/FAQ/book.html is this? Thanks! Russell %-- %Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] % % "There is no spoon." -- Kiki % % % %To Unsubscribe: send mail to [EMAIL PROTECTED] %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem installing on T20
"Russell L. Carter" wrote: > > %Wm Brian McCane wrote: > %> > %> I have an IBM T20 laptop that I want to run FreeBSD on. I have run > % > %BTW, I just found that this is covered on the FAQ. > > Otay, I must be blind. Where in http://www.freebsd.org/FAQ/book.html > is this? MMmmm. I think I have gone blind too. Beats me. I was reading december e-mail when I just stumbled on a thread about the same problem, where it was mentioned it had been added to the FAQ. Well, I can't seem to find any reference either. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sysinstall.8 Breaking buildworld
I had some buildworld failures earlier this week. In src/share/man/man8 the Makefile includes code to get the sysinstall.8 manpage. Since the manpage lives in src/release, this requires that you CVSup src-release. I had not been. This broke buildworld which had worked in the past. sysinstall.8 is the only file in src-release that is required for a buildworld. It seems somewhat silly to me that you are required to grab the whole thing for that one file. I made the change to the Makefile which makes sysinstall.8 and src-release optional. I included it in a reply to the PR that precipitated the change, http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 Steven G. Kargl ealier, independently submitted the almost exact same thing, http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24122 In a separate PR. Anyone have a good reason why everyone _must_ have src-release to buildworld? -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
