Linux-Hardware Digest #10, Volume #13 Thu, 8 Jun 00 23:13:08 EDT
Contents:
Re: Win2000 Nt Booter and Linux ("Tim R.")
Re: Turning on joystick port (Prasanth A. Kumar)
Re: SoundBlaster Live (emu10k1 module) (yet another sound card problem) (Kevin Hayes)
Re: Turning on joystick port (bernie)
Re: HELP: SIMPLE IRQ Routine Crashes (Erik Max Francis)
Re: LILO, FreeBSD, and >1024th Cylinder (John in SD)
CD-RW (john calison)
RF ruling - 3Com/USR 5690 Winmodem or not (Jake Gibbons)
Re: Win2000 Nt Booter and Linux (Doc Shipley)
Re: Heads, et al...Confused in NF, Canada...*smile* (Ian Stirling)
----------------------------------------------------------------------------
Date: Thu, 08 Jun 2000 20:02:15 -0500
From: "Tim R." <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: Win2000 Nt Booter and Linux
Zbigniew Sienkiewicz wrote:
> I don't think you can install any operating system without creating a boot
> sector on installed partition. You created your booting floppy by copying
> Linux kernel from Linux partition to a floppy.
> Why don't you try my instructions for copying a boot sector first.
> Zbigniew
>
> Tim R. <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > Zbigniew Sienkiewicz wrote:
> >
> > > Sure. Just copy a boot sector to NT and modify boot.ini to point to it.
> >
> > but i don't have a boot sector.
> > how i boot now is with a floppy that i basicly cp bzImage /dev/fd0
> > or else i use loadlin from my win95's dos
> > but i recently installed nt 4 server and would like to either use its
> > bootloader to boot linux, or else figure out how to use lilo to boot nt,
> win95,
> > and linux
> >
> > --Tim
> >
> > >
> > > To copy a boot sector:
> > > dd if=/dev/hda3 of=/linux.bst bs=512 count=1
> > > where /dev/hda3 is your Linux partition and linux.bst is a name of the
> file
> > > you're creating.
> > > To modify boot.ini add following line to it (after copying linux.bst to
> NT):
> > > C:\linux.bst="Linux"
> > > Hope it helps.
> > > Zbigniew
> > >
> > > Tim R. <[EMAIL PROTECTED]> wrote in message
> > > news:[EMAIL PROTECTED]...
> > > > I read something similor to this in a howto.
> > > > I personally don't use lilo though, is there a way to get nt's
> bootloader
> > > > to boot a kernel image?
> > > >
> > > > --tim
> > > >
> > > > [EMAIL PROTECTED] wrote:
> > > >
> > > > > That is really slick Jim. Thanks for posting!
> > > > >
> > > > > John.
> > > > >
> > > > > In article <v2LU4.2120$[EMAIL PROTECTED]>,
> > > > > "Jim Ross" <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > Jeff <[EMAIL PROTECTED]> wrote in message
> > > > > > news:[EMAIL PROTECTED]...
> > > > > > > Has Anyone successfully used the NT booter to boot into linux??
> > > > > And can
> > > > > > > anyone help me out, besides referring to the HOW-TO??
> > > > > > >
> > > > > > > Jeff
> > > > > > >
> > > > > > > Thanks in Advance!!!
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > Yes. I use it every day.
> > > > > >
> > > > > > I would install NT.
> > > > > > I would then install Linux. In doing so I would install LILO into
> the
> > > > > > beginning of root partition, NOT into the MBR (that's where OS
> Loader
> > > > > > lives).
> > > > > >
> > > > > > I would then download Bootpart.
> > > > > > http://ourworld.compuserve.com/homepages/gvollant/bootpart.htm
> > > > > > Install/Uncompress.
> > > > > > Tell Bootpart where the Linux partition you want to boot is. It
> will
> > > > > steal
> > > > > > the LILO bootsect.
> > > > > > You will take that bootsector BootPart generates in put it in your
> OS
> > > > > Loader
> > > > > > configuration file (i.e. often c:\boot.ini)
> > > > > >
> > > > > > So typing Bootpart I get
> > > > > >
> > > > > > Boot Partition 2.20 for WinNT (c) 1995-98 G. Vollant
> > > > > ([EMAIL PROTECTED])
> > > > > > WEB : http://www.winimage.com and
> http://www.winimage.com/bootpart.htm
> > > > > > Add partition in the Windows NT Multi-boot loader
> > > > > > Run "bootpart /?" for more information
> > > > > >
> > > > > > 0 : C:* type=6 (BIGDOS Fat16), size = 1534176 KB
> > > > > > 1 : C: type=f (Win95 XInt 13 extended), size = 18474750 KB
> > > > > > 2 : C: type=6 (BIGDOS Fat16), size = 2048256 KB
> > > > > > 3 : C: type=5 (Extended), size = 2048287 KB
> > > > > > 4 : C: type=6 (BIGDOS Fat16), size = 2048256 KB
> > > > > > 5 : C: type=5 (Extended), size = 16065 KB
> > > > > > 6 : C: type=83 (Linux native), size = 16033 KB
> > > > > > 7 : C: type=5 (Extended), size = 16065 KB
> > > > > > 8 : C: type=83 (Linux native), size = 16033 KB
> > > > > > 9 : C: type=5 (Extended), size = 16065 KB
> > > > > > 10 : C: type=83 (Linux native), size = 16033 KB
> > > > > > 11 : C: type=5 (Extended), size = 4731142 KB
> > > > > > 12 : C: type=83 (Linux native), size = 4731111 KB
> > > > > > 13 : C: type=5 (Extended), size = 4731142 KB
> > > > > > 14 : C: type=83 (Linux native), size = 4731111 KB
> > > > > > 15 : C: type=5 (Extended), size = 4731142 KB
> > > > > > 16 : C: type=b (Win95 Fat32), size = 4731111 KB
> > > > > > 17 : C: type=5 (Extended), size = 136552 KB
> > > > > > 18 : C: type=82 (Linux swap), size = 136521 KB
> > > > > >
> > > > > > I know a million OSes I know.
> > > > > > So, the partition I have RedHat on is 12. I know since I did the
> > > > > install
> > > > > > right? I notice these things.
> > > > > >
> > > > > > So the syntax of Bootpart is
> > > > > > BOOTPART <part_number> <filename>
> > > > > >
> > > > > > I just made up a name for the file but it's not that important
> other
> > > > > than it
> > > > > > being 8.3 filename format.
> > > > > > I use bootsect.lnx
> > > > > >
> > > > > > So I would type
> > > > > > bootpart 12 bootsect.lnx
> > > > > >
> > > > > > Copy that file bootsect.lnx to where boot.ini is (likely c:\)
> > > > > >
> > > > > > Then add an entry.
> > > > > >
> > > > > > My c:\boot.ini file
> > > > > >
> > > > > > [boot loader]
> > > > > > timeout=03
> > > > > > default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
> > > > > > [operating systems]
> > > > > > multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation
> > > > > Version
> > > > > > 4.00"
> > > > > > multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation
> > > > > Version
> > > > > > 4.00 [VGA mode]" /basevideo /sos
> > > > > > C:\="Microsoft Windows"
> > > > > >
> > > > > > c:\bootsect.lnx=" RedHat Linux 6.2"
> > > > > >
> > > > > > You can see I have NT, Windows, and Linux as an option.
> > > > > >
> > > > > > Notes:
> > > > > > The Windows 2000 and NT bootloaders seem to be the same.
> > > > > > Bootpart can do other things too but that's for another time.
> > > > > > I guess your bootsect.lnx could be located in other places but I
> keep
> > > > > all
> > > > > > mine together on C:
> > > > > > You don't need the crazy NT stuff in boot.ini for booting Linux,
> just
> > > > > you
> > > > > > know the bootsector name and label name to display just like
> > > > > dos/windows
> > > > > > would do.
> > > > > > There is a linux way of extracting the linux bootsector for nt
> > > > > loader, but
> > > > > > you would need a working linux first and bootpart seems easier
> > > > > somehow.
> > > > > > You should look for a type=83 partition to tell bootpart to use.
> > > > > > This procedure isn't as hard as all of this email/text would
> > > > > suggest. It
> > > > > > takes a second to do this when you know how.
> > > > > > You can have many Linux installations booted by OS Loader. Just
> keep
> > > > > using
> > > > > > different partitions/names.
> > > > > >
> > > > > > A simplier example of running bootpart might be with just NT and
> Linux
> > > > > > installed
> > > > > > 0 : C:* type=6 (BIGDOS Fat16), size = 5534176 KB
> > > > > > 5 : C: type=83 (Linux native), size =2731111 KB
> > > > > > 6 : C: type=82 (Linux swap), size = 136521 KB
> > > > > > Of course you would want bootpart 5 bootsect.lnx
> > > > > >
> > > > > > Jim Ross
> > > > > >
> > > > > >
> > > > >
> > > > > Sent via Deja.com http://www.deja.com/
> > > > > Before you buy.
> > > >
> >
well since i've never installed lilo on my linux partition's boot sector..i
dont't hink i could boot from it..
and getting the boot sector from that floppy would just give me a piece of the
kerenl, which surely wouldn't work the whole kernel doesn't when i try ti load
it from the nt bootloader..
------------------------------
Crossposted-To: comp.os.linux.redhat
Subject: Re: Turning on joystick port
From: [EMAIL PROTECTED] (Prasanth A. Kumar)
Date: Fri, 09 Jun 2000 01:33:57 GMT
bernie <[EMAIL PROTECTED]> writes:
> I guess I spoke to soon. I was able to use my siewinder yesterday with no
> problems. Today I rebooted my system and wasn't able to use it. I
> followed the same steps as a did before bit this time this is what Iget
>
> insmod joy-sidewinder
>
> ./joy-sidewinder.o: unresolved symbol js_unregister_device
> ./joy-sidewinder.o: unresolved symbol js_delta
> ./joy-sidewinder.o: unresolved symbol js_time_speed
> ./joy-sidewinder.o: unresolved symbol js_register_device
> ./joy-sidewinder.o: unresolved symbol js_register_port
> ./joy-sidewinder.o: unresolved symbol js_get_time
> ./joy-sidewinder.o: unresolved symbol js_unregister_port
>
> What could this mean, and what would be the fix?
>
> thanks for any more help,
> bernie
You need to 'ismod joystick' to load the base driver beforehand.
--
Prasanth Kumar
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Kevin Hayes)
Subject: Re: SoundBlaster Live (emu10k1 module) (yet another sound card problem)
Reply-To: [EMAIL PROTECTED]
Date: 9 Jun 2000 02:03:36 +1000
On Thu, 08 Jun 2000 15:13:39 -0500, Ethan Alpert <[EMAIL PROTECTED]> wrote:
>
>
>First let me say I've read everything I could possibly find. I've got a
>Dell Precision 420 with RH6.2 running an smp enabled 2.2.14 kernel. I'm
>trying to get my SoundBlaster Live card to work. The card is identified
>correctly by the system, but, I'm getting the infamous "Device or
>resource busy" error. Obviously I have an IRQ conflict, the problem is
>I can't find out which one nor can I figure out how to fix it. The
>emu10k1 module does not accept "irq=..." options in /etc/conf.modules.
>Furthermore, the HOWTO says to try booting DOS which is not an option as
>this machine was shipped with RH. Also, the documentation on emu10k1
>says to shut off PnP in the bios. In my bios screen I don't see such an
>option.
>
what bios do you have, on my award bios, i can select any irq to either
be pnp or to be a legacy setting...
>Is my only option to recompile the kernel with kernel hacking enabled
>and compile the emu10k1 with debugging on? The source code has several
>error messages which would be helpful if printed out. As far as I can
>tell the emu10k1 module should be able to share interrupts. I'm guessing
>that it must be a PCI device causing the problem since the sound modules
>are the first loaded in the rc.sysinit startup script. I'm stumped so
>any useful information would be most appreciated.
>
>
>Thanks,
>
> -ethan alpert
>
--
Kevin Hayes
Freshwater, Australia
------------------------------
From: bernie <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.redhat
Subject: Re: Turning on joystick port
Date: Fri, 09 Jun 2000 02:15:25 GMT
Thanks for the help! It works great now.
later
bernie
>
>
> You need to 'ismod joystick' to load the base driver beforehand.
>
> --
> Prasanth Kumar
> [EMAIL PROTECTED]
------------------------------
From: Erik Max Francis <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development.system
Subject: Re: HELP: SIMPLE IRQ Routine Crashes
Date: Thu, 08 Jun 2000 19:33:16 -0700
Andrey Vlasov wrote:
> are you sure that syntax of line correct
>
> printk(KERN_INFO "Servicing Interrupt %02d.\n", irq);
>
> as I never seen something like that. Normaly in C it looks
>
> printk(KERN_INFO, "Servicing Interrupt %02d.\n", irq);
> ^^^
(You should be using a fixed-width font for posting to Usenet, as the
highlight you attempted here didn't show up in the right place.)
What you replied to was correct. ANSI C indicates that juxtaposed
string literals are concatenated, and KERN_INFO is a macro which expands
to a string literal.
--
Erik Max Francis / [EMAIL PROTECTED] / http://www.alcyone.com/max/
__ San Jose, CA, US / 37 20 N 121 53 W / ICQ16063900 / &tSftDotIotE
/ \ When the solution is simple, God is answering.
\__/ Albert Einstein
7 sisters productions / http://www.7sisters.com/
Web design for the future.
------------------------------
From: John in SD <[EMAIL PROTECTED]>
Subject: Re: LILO, FreeBSD, and >1024th Cylinder
Reply-To: [EMAIL PROTECTED]
Date: Fri, 09 Jun 2000 02:43:04 GMT
The 'lba32' option will boot only those systems which support the EDD packet
calls on int 0x13. Test your BIOS with "make floppy" from the LILO 21.4.3
distribution. You will need 'nasm' for this make to be successful.
Boot the diagnostic floppy, and see if it reports EDD calls available for your
disk.
--John Coffman
On Thu, 08 Jun 2000 11:02:52 GMT, "Greg H." <[EMAIL PROTECTED]>
wrote:
>Hi all,
>
>I have a 20.5G IDE harddrive broken up basically into
>three equal parts with the exception of a single swap
>partition at the front of the drive. The second partition
>(the first 1/3) is a Slackware install, the third will
>eventually be a different Linux distribution, and the fourth
>is a FreeBSD "slice." Both installed fine and I installed
>a recent version of LILO with support for drives with
>more than 1024 cylinders. I added the proper information
>for FreeBSD to lilo.conf (Linux+FreeBSD HOWTO) and LILO
>installed to the MBR with no problems when I used the "-L"
>switch (LBA32). However, when I reboot and attempt to boot
>FreeBSD, I get "read error" and it hangs. If I hit return,
>it goes back to the LILO prompt. So, what I'm trying to
>figure out is if whether I am doing something wrong or what
>I'm doing can't be done.
>
>Any help is greatly appreciated. Thanks in advance!
>
>Greg
LILO version 21.4.3 (06-May-2000) source at
ftp: sd.dynhost.com dir: /pub/linux/lilo
------------------------------
From: john calison <[EMAIL PROTECTED]>
Subject: CD-RW
Date: Thu, 08 Jun 2000 22:43:04 -0400
I hope someone can help, I'm really stumped. I'm running RH6.1 and
a HP9300i CD-RW. I've followed the cd-writingHOWTO to the letter. I've
configured the kernel properly, edited /etc/lilo.conf and
/etc/conf.modules exactly the way the HOWTO says to. I've even used the
HOWTO script to check that all modules have been loaded and ran the
commands to make sure I have the proper device files.
The CD-RW is master on the secondary ide and the ZIP is slave on the
secondary. When I run cdrecord -scanbus, only the ZIP is shown. I
would appreciate any help as I've spent the last three days trying to
get scsi emulation to see this device.
thanks in advance,
john
------------------------------
From: Jake Gibbons <[EMAIL PROTECTED]>
Subject: RF ruling - 3Com/USR 5690 Winmodem or not
Date: Fri, 09 Jun 2000 02:45:29 GMT
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<font color="#3333FF">Long.</font>
<br>
<hr WIDTH="100%">
<br>Is the truth out there? (K, so that is becoming very cliché,
I know).
<p>I recently discovered, that am the proud owner of a Modem Blaster WINMODEM.
This came with the machine, and it really does not bother me as it was
cheap and has functioned fine under Windows for a while now. This modem
would not work under Linux.
<p>Because this modem is not a good candidate for Linux, I decided to go
ahead and get a USR 56K Voice Faxmodem PCI. The 3Com/USR model number on
the box is 5690. I chose the 5690 internal PCI modem based upon a couple
of articles about successful installation under Linux. Also, it is listed
in the LHD with a high rating, and good review (<A
HREF="http://lhd.datapower.com/db/dispproduct.php3?DISP?231">http://lhd.datapower.com/db/dispproduct.php3?DISP?231</A>).
<br>In the Linux/Modem Compatibility KB (<A
HREF="http://www.o2.net/~gromitkc/20000604a.html">http://www.o2.net/~gromitkc/20000604a.html</A>)
I later found this entry:
<br> Model 5690-00, U.S. Robotics PCI 56K FAX Voice
<br> Winmodem
<br> PCI\VEN_12B9&DEV_1006&SUBSYS_006812B9&REV_00).
<p>Anyone confused yet? I was, so I decided to buy and install the beast
anyway. It's funny how lspci can make your heart sink. It returned
a line, "... Winmodem". By now I felt ripped-off (200 Canabucks for this
when my original Winmodem was $50 - HELLO) So, I e-mailed 3com tech support,
and here is part of their response:
<p> "Based on your modem's product code [00569000] this modem
is a software
<br> based device. It will only operate in a Windows
eviroment and not in Linux."
<p>So, does anyone know if this thing really works under Linux? Is there
a difference between 5690 and 5690-00?
<br>
<p>So confused,
<br>Jake
<p>Ps. For brevity, you do not have to include all of the above in the
reply (just a suggestion).
<br>
<br> </html>
------------------------------
From: Doc Shipley <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: Win2000 Nt Booter and Linux
Date: 8 Jun 2000 21:48:13 -0500
"Tim R." wrote:
> but i recently installed nt 4 server and would like to either use its
> bootloader to boot linux, or else figure out how to use lilo to boot nt, win95,
> and linux
>
> --Tim
Tim, what distribution are you using? Give us the distro and your HDD
partition setup and it should be pretty easy to walk you through it. Is
NT on FAT or NTFS?
--
Doc Shipley
Network Support
TARL Labs, UT
Austin, Texas
------------------------------
From: Ian Stirling <[EMAIL PROTECTED]>
Crossposted-To:
comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,alt.comp.hardware.homebuilt,alt.comp.hardware.homedesigned,alt.comp.hardware.pc-homebuilt
Subject: Re: Heads, et al...Confused in NF, Canada...*smile*
Date: Fri, 09 Jun 2000 02:53:57 GMT
In alt.comp.hardware.homebuilt Hendrix <[EMAIL PROTECTED]> wrote:
>Hi guys,
<snip>
>Does this sound right...??? It sounds right to me...EXCEPT...I have a
>hard drive here that I know has only 2 platters, but yet it is rated as
>having 16 heads... It is a 2.57GB Fujitsu that is rated as having a
>geometry of 4982Cyl 16Hds 63Sec/Trk....!!! And if my previous
>calculations are correct, the head count would yield 8 platters...
You would have been right, in the dim and distant past, when there were
only MFM, or RLL drives.
After that, when IDE drives arrived, a little later things became confused.
IDE drives often have different number of sectors per track, at different
tracks, to pack the most data on.
This means that the heads/sectors/tracks was somewhat blurred, in that
for example, track "417" in software might be spread over tracks 300,301,
on the actual disk.
If the heads number was set right, then most of the time, you'd be writing
on the correct platter.
Then, once hard drives got over a few tens of megs, the capacity went over
what the BIOS could sensibly support.
This meant that for a two head drive, if you say in the BIOS it has
16 heads, you can cope with a disk eight times as big.
Then, at 500Mb or so, you hit another problem, in that even if you
max out heads/sectors, and tracks, you can't reach the disk capacity.
Then, another hack came in, to make disks up to 4G(or is it 8G?) possible.
Then, yet another hack, to allow over 8G
--
http://inquisitor.i.am/ | mailto:[EMAIL PROTECTED] | Ian Stirling.
===========================+=========================+==========================
"Looks like his brainwaves crash a little short of the beach..." - Duckman.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
