- WLUG - wlug.mailman3.com

RE: [Wlug] kernel questions

by Skip Gaede

Hi Greg, > -----Original Message----- > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On > Behalf Of Gregory Avedissian > Sent: Saturday, December 21, 2002 11:52 AM > To: wlug(a)mail.wlug.org > Subject: [Wlug] kernel questions > > > I'm trying to get oss sound modules compiled into kernel. > make xconfig was easy enough to get through. > instructions say to then make dep and make bzImage or bzlilo. > 1. I get errors on this, because I'm above cylinder 1023 on > my dual-boot > drive. I boot linux from floppy with lilo. Error message > suggests using > lba32 option, but it doesn't say where or how to use it. How do I get > around this? The best option would be to shrink your primary partition by a few MB, leaving room to create a small primary partition for the Linux /boot partiition. You can easily do this with Partition Magic. ---------------------- Primary | ext2 | /boot ---------------------- Primary | FAT or NTFS or ??? ---------------------- Extended| swap ---------------------- Extended| ext2 or ext3 | / ---------------------- other partitions as desired... > > 2. Instructions say next to install the kernel. Is that done > by typing > make install? In addition to the make install that comes after make > modules? (see below) No, you need to copy the arch/i386/boot/bzImage --> /boot/<some unique name> and then add an entry to /etc/lilo.conf or /boot/grub/menu.lst. If you are using lilo, you then need to install the new boot sector by typing lilo. > > 3. I haven't been able to create a lilo boot disk for awhile. > I'm using > Yast2 to configure boot mode, and it keeps telling me that my > floppy is > write protected and it can't access the boot sector. I've tried this > with new floppies that have been formated with fdformat /dev/fd0. You shouldn't need to format it first, and the disk should not be mounted. Refer to help on www.tldp.org on how to make a boot disk. > > Thanks for any insight. > > Here are the instructions I'm looking at: > > 1. To make the kernel sound modules, cd to your /usr/src/linux > > directory (typically) and type make config, make menuconfig, > > or make xconfig (to start the command line, dialog, or x-based > > configuration tool). > > > > 2. Select the Sound option and a dialog will be displayed. > > > > 3. Select M (module) for "Sound card support". > > > > 4. Select your sound driver(s) as a module. For ProAudio, Sound > > Blaster, etc., select M (module) for OSS sound modules. > > [thanks to Marvin Stodolsky <stodolsk(a)erols.com>]A > > > > 5. Make the kernel (e.g., make dep ; make bzImage), and install > > the kernel. > > > > 6. Make the modules and install them (make modules; make > modules_install). > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 21, 2002

kernel questions

by Gregory Avedissian

I'm trying to get oss sound modules compiled into kernel. make xconfig was easy enough to get through. instructions say to then make dep and make bzImage or bzlilo. 1. I get errors on this, because I'm above cylinder 1023 on my dual-boot drive. I boot linux from floppy with lilo. Error message suggests using lba32 option, but it doesn't say where or how to use it. How do I get around this? 2. Instructions say next to install the kernel. Is that done by typing make install? In addition to the make install that comes after make modules? (see below) 3. I haven't been able to create a lilo boot disk for awhile. I'm using Yast2 to configure boot mode, and it keeps telling me that my floppy is write protected and it can't access the boot sector. I've tried this with new floppies that have been formated with fdformat /dev/fd0. Thanks for any insight. Here are the instructions I'm looking at: > 1. To make the kernel sound modules, cd to your /usr/src/linux > directory (typically) and type make config, make menuconfig, > or make xconfig (to start the command line, dialog, or x-based > configuration tool). > > 2. Select the Sound option and a dialog will be displayed. > > 3. Select M (module) for "Sound card support". > > 4. Select your sound driver(s) as a module. For ProAudio, Sound > Blaster, etc., select M (module) for OSS sound modules. > [thanks to Marvin Stodolsky <stodolsk(a)erols.com>]A > > 5. Make the kernel (e.g., make dep ; make bzImage), and install > the kernel. > > 6. Make the modules and install them (make modules; make modules_install).

Dec. 21, 2002

Re: [Wlug] The Package Chase

by Andy Stewart

On Friday 20 December 2002 9:25 pm, Gregory Avedissian wrote: > OK, I've been going along merrily with my SuSE 7.2 for about a year, and > I just now ran into a problem that a lot of you folks must know all too > well. Install a new program and it calls for a package you don't have. > You've all seen the lists, I'm sure. > > I'm trying to install ecawave and ALSA 0.9, and I've had to install some > gtk and gnome stuff, and I went to look at upgrading the whole gnome > package. There's a list of more than 50 things to compile, and they must > be done in the correct order. Do people actually do that? Is there any > advantage of doing that over upgrading the whole distribution? HI Greg, It might be easier to find a more recent SuSE CD and upgrade just the packages about which you care. You could probably download them, but that may be slow and cumbersome given the number of packages you describe. If its just one or two packages, I'll "do it the hard way" and download the package and upgrade it. On occasion, it turns into a rat's nest of dependencies, but typically not. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Dec. 21, 2002

The Package Chase

by Gregory Avedissian

OK, I've been going along merrily with my SuSE 7.2 for about a year, and I just now ran into a problem that a lot of you folks must know all too well. Install a new program and it calls for a package you don't have. You've all seen the lists, I'm sure. I'm trying to install ecawave and ALSA 0.9, and I've had to install some gtk and gnome stuff, and I went to look at upgrading the whole gnome package. There's a list of more than 50 things to compile, and they must be done in the correct order. Do people actually do that? Is there any advantage of doing that over upgrading the whole distribution?

Dec. 21, 2002

Re: [Wlug] bioswriter

by Wes Allen

This is what I was afraid of. Oh well, maybe one of the freeBIOS' will come along and I can try flashing this thing out of existence (if my chip is supported, that is...). Wes On Thursday 19 December 2002 10:13 pm, Skip Gaede wrote: > Wes, > > The location in BIOS for the PNP setting is not cast in concrete. > Unless you know which bit does the job, it is pretty hard to > figure it out. > > When you do figure it out, each block of 16 bytes (I think) includes > a checksum. so in addition to changing the bit, you'll also need to > change the checksum. > > --Skip > > > -----Original Message----- > > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On > > Behalf Of Wes Allen > > Sent: Thursday, December 19, 2002 5:19 PM > > To: wlug(a)mail.wlug.org > > Subject: [Wlug] bioswriter > > > > > > Has anyone ever used bioswriter or a similar utility to get > > your bios settings > > from CMOS? I'm trying to read it with bioswriter with little > > success as I'm > > not sure what to do with the image file. > > > > I'm wondering there is a way to hack this bios to let me turn > > "plug and play > > os" off, as I'm fairly certain it's on by default and the > > given interface is > > pretty limited. > > > > Or am I breaking the law to edit my bios settings.... on the > > computer I OWN. > > > > Wes > > -- > > ------ > > This message may be signed using GPG, for my public key please > > send me a message with "Key Request" in the subject line. > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- ------ This message may be signed using GPG, for my public key please send me a message with "Key Request" in the subject line.

Dec. 20, 2002

RE: [Wlug] bioswriter

by Skip Gaede

Wes, The location in BIOS for the PNP setting is not cast in concrete. Unless you know which bit does the job, it is pretty hard to figure it out. When you do figure it out, each block of 16 bytes (I think) includes a checksum. so in addition to changing the bit, you'll also need to change the checksum. --Skip > -----Original Message----- > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On > Behalf Of Wes Allen > Sent: Thursday, December 19, 2002 5:19 PM > To: wlug(a)mail.wlug.org > Subject: [Wlug] bioswriter > > > Has anyone ever used bioswriter or a similar utility to get > your bios settings > from CMOS? I'm trying to read it with bioswriter with little > success as I'm > not sure what to do with the image file. > > I'm wondering there is a way to hack this bios to let me turn > "plug and play > os" off, as I'm fairly certain it's on by default and the > given interface is > pretty limited. > > Or am I breaking the law to edit my bios settings.... on the > computer I OWN. > > Wes > -- > ------ > This message may be signed using GPG, for my public key please > send me a message with "Key Request" in the subject line. > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 20, 2002

recording in linux

by Gregory Avedissian

Someone asked about recording under linux recently, and I recall that several of us said we'd never been able to do it. I just did it. In alsamixer, space bar sets the channel you want to use for capture. (line in is a reasonable choice) Had to manually edit /etc/asound.conf to turn on the input gain and set the level to 10,10. It looks like this: element("Input Gain Switch",0,101,Switch2(on)) ; Voice 0 : Min 0 Max 15 ; Voice 1 : Min 0 Max 15 element("Input Gain Volume",0,200,Volume1(10,10))

Dec. 20, 2002

bioswriter

by Wes Allen

Has anyone ever used bioswriter or a similar utility to get your bios settings from CMOS? I'm trying to read it with bioswriter with little success as I'm not sure what to do with the image file. I'm wondering there is a way to hack this bios to let me turn "plug and play os" off, as I'm fairly certain it's on by default and the given interface is pretty limited. Or am I breaking the law to edit my bios settings.... on the computer I OWN. Wes -- ------ This message may be signed using GPG, for my public key please send me a message with "Key Request" in the subject line.

Dec. 19, 2002

RE: [Wlug] Cross Compile Question

by Scott Venier

Depends on the language... if it's C, yes. if it's C++, no way. Scott On Thu, 19 Dec 2002, Marc Hughes wrote: > If I compile some source files with gcc2.x and some with gcc3.x, can I > link the object files together? > > -Marc > > -----Original Message----- > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org] On > Behalf Of Skip Gaede > Sent: Thursday, December 19, 2002 12:23 PM > To: wlug(a)mail.wlug.org > Subject: RE: [Wlug] Cross Compile Question > > > I recently saw that the GCC 3.x compiler isn't cross compile friendly. > Try using GCC 2.95.3. > > --Skip > > -----Original Message----- > > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On > > Behalf Of Marc Hughes > > Sent: Thursday, December 19, 2002 11:45 AM > > To: wlug(a)wlug.org > > Subject: [Wlug] Cross Compile Question > > > > > > I'm trying to make a cross-compiler on an i386 linux box to a > > ppc darwin > > (OSX) box. I downloaded binutils, configured them with > > ./configure --target=powerpc-apple --prefix=/usr/local > > Build them, and installed them. > > > > Then I went and got gcc (with g++), configured it with: ./configure > > --target=powerpc-apple-darwin --prefix=/usr/local > > > > I also made a symlink from /usr/local/powerpc-apple -> > > /usr/local/powerpc-apple-darwin since it seemed to fix a problem in > > the gcc compile. > > > > When I try to build gcc, it goes for a minute or so, and then > > I get this > > towards the end: > > > > libbackend.a(varasm.o): In function `assemble_alias': > > /data/hughesm/tmp/gcc-3.1/gcc/varasm.c:5184: undefined reference to > > `ASM_OUTPUT_DEF' > > collect2: ld returned 1 exit status > > make[1]: *** [cc1] Error 1 > > make[1]: Leaving directory `/data/hughesm/tmp/gcc-3.1/gcc' > > make: *** [all-gcc] Error 2 > > > > I'm not really asking for the exact cause of the error... I'm just > > trying to figure out if I'm even going about this the correct way. > > The documentation on cross compiling is a bit sparse. It seems odd to > > > me that the targets don't match (but there is no powerpc-apple-darwin > > in binutils, and no powerpc-apple in gcc) > > > > All that being said, I'm doing this so I can add my linux boxes to my > > OSX build farm. Check out distcc.samba.org for a wicked cool and easy > > > way to distribute compiles. > > > > -Marc > > > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 19, 2002

RE: [Wlug] Cross Compile Question

by Marc Hughes

If I compile some source files with gcc2.x and some with gcc3.x, can I link the object files together? -Marc -----Original Message----- From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org] On Behalf Of Skip Gaede Sent: Thursday, December 19, 2002 12:23 PM To: wlug(a)mail.wlug.org Subject: RE: [Wlug] Cross Compile Question I recently saw that the GCC 3.x compiler isn't cross compile friendly. Try using GCC 2.95.3. --Skip > -----Original Message----- > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On > Behalf Of Marc Hughes > Sent: Thursday, December 19, 2002 11:45 AM > To: wlug(a)wlug.org > Subject: [Wlug] Cross Compile Question > > > I'm trying to make a cross-compiler on an i386 linux box to a > ppc darwin > (OSX) box. I downloaded binutils, configured them with > ./configure --target=powerpc-apple --prefix=/usr/local > Build them, and installed them. > > Then I went and got gcc (with g++), configured it with: ./configure > --target=powerpc-apple-darwin --prefix=/usr/local > > I also made a symlink from /usr/local/powerpc-apple -> > /usr/local/powerpc-apple-darwin since it seemed to fix a problem in > the gcc compile. > > When I try to build gcc, it goes for a minute or so, and then > I get this > towards the end: > > libbackend.a(varasm.o): In function `assemble_alias': > /data/hughesm/tmp/gcc-3.1/gcc/varasm.c:5184: undefined reference to > `ASM_OUTPUT_DEF' > collect2: ld returned 1 exit status > make[1]: *** [cc1] Error 1 > make[1]: Leaving directory `/data/hughesm/tmp/gcc-3.1/gcc' > make: *** [all-gcc] Error 2 > > I'm not really asking for the exact cause of the error... I'm just > trying to figure out if I'm even going about this the correct way. > The documentation on cross compiling is a bit sparse. It seems odd to > me that the targets don't match (but there is no powerpc-apple-darwin > in binutils, and no powerpc-apple in gcc) > > All that being said, I'm doing this so I can add my linux boxes to my > OSX build farm. Check out distcc.samba.org for a wicked cool and easy > way to distribute compiles. > > -Marc > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Dec. 19, 2002