Re: it's time...
On 12-Aug-99 Ben Rosengart wrote: > On Wed, 11 Aug 1999, Brian F. Feldman wrote: > >> What in the world would be the point of doing this? What would be so >> great >> about not seeing the system boot up? > > One might want minimal or no boot messages, just to look nice, while > still wanting the dmesg stuff around in case something goes wrong or > they need to configure a kernel. It's certainly chrome, but I'd like > it. Surely if you don't want to see the boot messages for cosmetic reasons a splash screen is the most cosmeticly pleasing solution. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
yet more TP 600E fun...
I attempt to boot a CD off of the TP600E and I get the following errors: "Can't work out which disk we are booting from." "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" Then whenever it attmpts to access "disk0:" it goes to the floppy drive. Suggestions? -- 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
Re: recent apm changes
Hi, > MI> Please try this patch. > MI> If it still fails, it's worth to try increasing APM_SUSPEND_DELAY, > MI> something like: > MI> #define APM_SUSPEND_DELAY 3 > > Alas, it doesn't make a difference. H. OK, I'll buy new mather board same one as yours and investigate what's happend on it. Could you tell me which M/B are you using? And I'd like to have your dmesg output from kernel with APM_DEBUG option. # In your kernel config file: # options APM_DEBUG Also, I'll send you few more patches before I purchase new one if I get new ideas. > Anyway thanks for you efforts so far. Not at all. I never give up :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
> On Wed, 11 Aug 1999, Brian F. Feldman wrote: > > > What in the world would be the point of doing this? What would be so great > > about not seeing the system boot up? > > One might want minimal or no boot messages, just to look nice, while > still wanting the dmesg stuff around in case something goes wrong or > they need to configure a kernel. It's certainly chrome, but I'd like > it. Spash screen. That being said, the capability to have what comes out during a verbose boot go somewhere else for later review, while only the "normal" messages are seen on the console would be sorta cool. I think you could do this by converting the printf()'s in the kernel to something like syslog() with explicity verbosity/priority specifications. louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Brian F. Feldman wrote: > What in the world would be the point of doing this? What would be so great > about not seeing the system boot up? One might want minimal or no boot messages, just to look nice, while still wanting the dmesg stuff around in case something goes wrong or they need to configure a kernel. It's certainly chrome, but I'd like it. -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes: MI> Please try this patch. MI> If it still fails, it's worth to try increasing APM_SUSPEND_DELAY, MI> something like: MI> #define APM_SUSPEND_DELAY 3 Alas, it doesn't make a difference. I tried too with APM_SUSPEND_DELAY 5. What I see when I issue 'zzz', is a delay of 5 seconds, but in between programs keep running (and thus keep generating interrupts I guess). Then after 5 seconds the screen blanks, the power light starts flashing (indicating suspend mode), but when I hit a key, the console says (slept 00:00:02) only, and programs in fact continued running (thus it didn't go or remain in suspend mode at all). Anyway thanks for you efforts so far. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know [EMAIL PROTECTED] | the Netherlands| what I'm doing. ---+-+-- Powered by FreeBSD (-current). See http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IBM ThinkPad 600E with cardbus EtherJet 10/100 :)
> 1: any access to the serial port (/dev/cuaa0) locks the machine. Weird. I haven't tried accessing mine though, but I know there are lots of weird setup issues that must be done to get the serial port to be read correctly. > 2: I cannot get the ethernet card to work. > 2a: It is sort-a recognized by the system, It senses the insert and remove, > but it cannot get the CIS. I remember reading somewhere that the CIS > on these cards is 'somewhere else' and you can tell pccardd where that is. > 2b: I believe that this is in reality a tulip card. Then it's not supported, since it would be a CardBus ethernet card. > I am in no way opposed to beta software, and I will code as need be, I > just need to know where things already are before I get my feet wet. You need to get an old PCCARD ethernet card, since the 600E does work in PCCARD emulation mode. I absolutely *love* mine. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DEV_MODULE doesn't support dynamic major numbers any longer?
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> The cmaj and bmaj in DEV_MODULE are only used for ordering the drivers,
> and otherwise with no significance.
Yeah, I realized that later.
> The previous code was a hack and inflicted problems. The right
> solution, (until DEVFS of course) is to add two new functions:
> alloc_cmaj() and alloc_bmaj() and use those.
Like the following code? And should they be used by cdevsw_add when
d_maj and d_bmaj are some magical value such as -1?
/assar
Index: kern/kern_conf.c
===
RCS file: /src/fbsd-repository/src/sys/kern/kern_conf.c,v
retrieving revision 1.55
diff -u -w -u -w -r1.55 kern_conf.c
--- kern_conf.c 1999/08/08 18:42:47 1.55
+++ kern_conf.c 1999/08/12 13:24:04
@@ -88,6 +88,36 @@
}
/*
+ * Return an unused cdev major or -1 if there are none free.
+ */
+
+int
+alloc_cmaj (void)
+{
+int i;
+
+for (i = cdevsw_ALLOCSTART; i < NUMCDEVSW; ++i)
+ if (cdevsw[i] == NULL)
+ return i;
+return -1;
+}
+
+/*
+ * Return an unused bdev major or -1 if there are none free.
+ */
+
+int
+alloc_bmaj (void)
+{
+int i;
+
+for (i = cdevsw_ALLOCSTART; i < NUMCDEVSW; ++i)
+ if (bmaj2cmaj[i] == 254)
+ return i;
+return -1;
+}
+
+/*
* Add a cdevsw entry
*/
Index: sys/conf.h
===
RCS file: /src/fbsd-repository/src/sys/sys/conf.h,v
retrieving revision 1.69
diff -u -w -u -w -r1.69 conf.h
--- conf.h 1999/08/09 18:45:20 1.69
+++ conf.h 1999/08/12 13:21:23
@@ -248,6 +248,8 @@
DECLARE_MODULE(name, name##_mod, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+cmaj*256+bmaj)
+intalloc_bmaj __P((void));
+intalloc_cmaj __P((void));
struct cdevsw *bdevsw __P((dev_t dev));
intcdevsw_add __P((struct cdevsw *new));
intcdevsw_remove __P((struct cdevsw *old));
Re: DEV_MODULE doesn't support dynamic major numbers any longer?
In message <[EMAIL PROTECTED]>, Assar Westerlund writes: >It seems to be the case that the possibility of specifying a major >number of NOMAJ in DEV_MODULE has vanished. The cmaj and bmaj in DEV_MODULE are only used for ordering the drivers, and otherwise with no significance. You should store your majors in your cdevsw structure. I don't particular like the concept of DEV_MODULE registrating the cdevsw by magic. >cdevsw_add() doesn't have any code for handling NOMAJ any longer. >(The only mention I can find of NOMAJ in a -current kernel tree from >19990811 are these: >which makes me wonder how the promcons works...). Fine, see above. >Is this intentional that there isn't there any support for dynamically >assigning major device numbers or is it an accident that I should go >and rectify? The previous code was a hack and inflicted problems. The right solution, (until DEVFS of course) is to add two new functions: alloc_cmaj() and alloc_bmaj() and use those. -- 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: Bus error in isatty() from /usr/lib/libc.so.3
Thimble Smith wrote: > Hello. I have a reproducable problem which gdb says is ending up at > 0x2818d862 in isatty() from /usr/lib/libc.so.3. A full back trace is > below. If this is a problem in FreeBSD, I'm very glad to do any > experiments that might be helpful. If it's a problem somewhere else, > any pointers on what I might do next would be great. [...] > #1 0x2818db22 in isatty () from /usr/lib/libc.so.3 > #2 0x2818e1de in malloc () from /usr/lib/libc.so.3 > #3 0x28236e88 in _thread_fd_table_init () from /usr/lib/libc_r.so.4 > #4 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 You are linking against both libc _and_ libc_r. "Don't do that!" -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
