Re: Sound configuration not in initial install
Hmm, if Linux isn't going to provide sound configuration on the initial install, then why not note that on the main package selection screen that comes up on a clean install and give directions on how to recall the initial package selector once sound has been configured. This would help people who might be able to follow a menuconfig of the kernel and get sound support installed, but who have no idea which of the many sound related .deb's to install. Allowing the end user to run the package selector (and givng brief directions on the same in the menu) will mean that it will be easier for people to run Linux successfully the first time, thus giving another person a reason to _continue_ using Linux. I know from experience that when you intially install Debian you get the choice to include Sound Support Files, but nothing is said about needing to recompile the kernel until dselect glitches on installing GOM. For someone trying to migrate from the Microsoft world this can be more than a bit confusing. - BOHICA David Webster wrote: > > During the drivers installation phase there is no facility for > installing sound card info. I find this quite odd since sound is as > ubiquitous in computing today as ethernet and TCP/IP. The failure to > not allow us to configure sound at the outset forces us newbies to go > into the daunting task of recompiling a kernel which I have yet to do > successfully as something always seems to get mucked up!! > > This is REAL shortcoming for Debian and I assume sound configuration > will be part of the base modconf come release 2.2?? > > By the way I have used both the brute force kernel recompile/install > secquences out of the HOWTO's and the Debian Kernel-Package approach, > both to dismal results. > Sadly, I don't think sound config will ever be handled in the initial install anytime in the near future. Sound is already difficult to configure and with the 2.2 kernel its gets even a little *more* complicated, because part of the sound config has been moved from the kernel to text config files in /etc/modutils/* (or etc/modules.conf). Because of this, and the fact that sound isn't essential for the initial install process, its not going to be handled by the Debian installer for some time into the future. As for your difficulty compiling a kernel, why don't you post the problem you are having, including all error messages that occur, to this list? Someone might be able to help you. -- Ed C.
Minicom Help
OK, silly question: How do I tell minicom to connect to a serial port (i.e. /dev/ttyS0) so that I can talk to the serial terminal of a 3Com hub? I have had no problem setting up and configuring minicom for the dial-in modem for the main hub bank, but currently I have a need to pre-configure some hubs for a standalone lab, thus the serial port connection. I read through the man pages as well as doing a search on the FAQ-O-MATIC and list archives, but didn't see anything relating to this in particular. Any and all help is appreciated. - BOHICA
Mail File Question
Does anyone know of a utility that will convert a Microsoft *.pst file to a generic mail file? I have about five years worth of saved correspondence &c that I would like to be able to access from either Pine or Messenger, problem being that MS only allows export as tab or comma separated files if you don't want pst. As far as I can tell, neither Pine nor Messenger can deal with .tsv or .csv files successfully (though I could be wrong). All help is appreciated. - BOHICA
Re: rawrite[23] problem on nt 4.0
Sounds like you are trying to use the "new" 1.743Mb floppy image. Every time I tried it I got the same error since rawrite will try to create a disk image that is bigger than the media, but since it doesn't do any "sanity" checking it errors out when it's own calculation of needed space doesn't match what it reads from the disk. (Nevermind that most FDD's are not even capable of dealing with 1.743Mb.) Presuming that are still there, you can find 1.44Mb images at: llug.sep.bnl.gov in the debian/incoming directory. As with all unstable products, this may or may not solve your problem. - BOHICA Richard Lyon wrote: > Yes I use rawrite2 under winnt 4.0. A couple of things you might try are: > > 1.Try a preformatted floppy. > > 2.If you are connected to a network logout and try running in standalone > mode. > > Some of laptop computers should really be called winputers. > > -Original Message- > From: Aaron Stromas <[EMAIL PROTECTED]> > To: debian-user@lists.debian.org > Date: Friday, 11 December 1998 0:03 > Subject: rawrite[23] problem on nt 4.0 > > >i need to create boot floppies to install debian 2.0 as i have the > >adaptec ultra2 scsi controller, and i'm having a problem with both > >rawrite2 and rawrite3 utilities on my nt 4.0 toshiba laptop. both > >utilities claim they "Can't figure out how many sectors/track for this > >diskette". happens with every high density 1.4m diskette i tried, > >maxell, fuji etc. any clues? tia, > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Questions...
Two of them actually: 1I just compiled and installed the new 2.0.35-3 kernel, from and to hamm (needed the PARIDE support). Although PARIDE works just fine now, I have lost all passwords. When I login, all I have to do is type any valid username, hit enter, and I immediately have full superuser access to the system. Can anyone point me in the right direction as to what I did, how not to do it again and how to fix it now that I broke it? 2Is there any way to see the error messages that currently display behind the initial setup screens? I was playing with the new slink disks on a test machine and when I got to the base install, it errored out, I suspect being unable to create one of it's files. The only piece of the error I can see says: "/localtime: No S". /etc/localtime looks to be in the right place, so I can't figure it out. - BOHICA
APT-GET and SOCKS proxy firewall
I'm having a bit of trouble with apt-get. Background: slink install from HDD connected to LAN without trouble installed socks-client via sneakernet and configured per the man page, setting http and ftp for port 1080 in socks.conf can successfully pass through firewall with minicom read the man page for sources.list and tried both set $http_proxy and http://proxy:port/ apt-get generates "403 Proxy denies fulfilling the request" when trying to update Packages.gz There is not enough space on my LAN ftp point to drop the Debian archive and the PC has no CD-ROM. Help???
How do I make CD's?
I currently have a CD-RW device up and running. I want to burn an RW with the slink dist while I'm at work and can grab the main, contrib and non-free over the WAN (T3 being _much_ faster than 56K analog). Problem is, the main/binary-i386 directory is over 800Mb, RW's only hold 650Mb. Is there a list or guide somewhere as to how I should segment this? (i.e. "admin through libs" on one and "mail through x11" on another; or "files x, y and z are not needed for initial installation") - BOHICA
Modem trouble, Please help!!
Semi-successful slink install to a laptop. On setup reboot, pppconfig ran and I setup my ISP, dialed in and was trying to get the dselect access configured when I suddenly got the following error: Usage: /sbin/getty [-hiLmw] [-l login_program] [-t timeout] [-I initstring] line baud_rate,... line [termtype] or [-hiLmw] [-l login_program] [-t timeout] [-I initstring] line baud_rate,... [termtype] This repeats about five or six times (scrolls too fast to read the first few), then I see: INIT: Id "S" respawning too fast: disabled for 5 minutes Then every 5 minutes, I see the same thing again. I looked at /sbin/getty and didn't see anything that would indicate where to set this, can't get the manpages until I get online, the FAQ-O-MATIC didn't say anything about this and the list archives came up dry. Where do I set the "spawn" time for Id "S"? What are the standard settings for spawn time? Does someone have a web page or HOWTO that I might have overlooked that addresses this? - BOHICA
RE: Modem trouble, Please help!!
ps ax | grep getty 158 2 S0:00 /sbin/getty 38400 tty2 159 3 S0:00 /sbin/getty 38400 tty3 160 4 S0:00 /sbin/getty 38400 tty4 161 5 S0:00 /sbin/getty 38400 tty5 162 6 S0:00 /sbin/getty 38400 tty6 inittab # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.8 1998/05/10 10:37:50 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # ::: 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 S:12345:respawn:/sbin/getty ttyS1 Thank You!! - BOHICA -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, December 25, 1998 10:08 To: BOHICA Cc: debian-user@lists.debian.org Subject: Re: Modem trouble, Please help!! BOHICA writes: > On setup reboot, pppconfig ran and I setup my ISP, dialed in and was > trying to get the dselect access configured when I suddenly got the > following error: > Usage: /sbin/getty [-hiLmw] [-l login_program] [-t timeout] [-I > initstring] line baud_rate,... line [termtype] or [-hiLmw] [-l > login_program] [-t timeout] [-I initstring] line baud_rate,... [termtype] Looks like there is a misconfigured getty running on your modem port (there should be none at all). Run ps ax | grep getty and post the result. If there is a getty process running on your modem port kill it and try again. *Don't* kill any gettys that are not on ports with numbers like ttyS2, ttyS3, etc. > Where do I set the "spawn" time for Id "S"? What are the standard > settings for spawn time? This begins to look like an intallation bug. Please post your /etc/inittab. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
RE: Modem trouble, Please help!!
Thanks to all who have helped thus far... OK, so how do I get the change to stick? I logged in as root, made the change in vi, saved it, exited and printed it to the screen to check... everything looked good. On reboot though, the same error popped up again so I re-displayed the file, the file had "healed" itself and removed the comment mark! I tried it again, this time invoking the su privilege from root, verified the change, rebooted, and doggone if it didn't "heal" my change again! Where/How do I change this and make it stay changed? - BOHICA -Original Message- From: Pete Harlan [mailto:[EMAIL PROTECTED] Sent: Friday, December 25, 1998 12:54 To: BOHICA Subject: Re: Modem trouble, Please help!! > S:12345:respawn:/sbin/getty ttyS1 That's it; comment that line out. --Pete
RE: Modem trouble, Please help!!
Indeed yes, PCMCIA is running, the modem card is one of the Xircom duals. The system recognizes it correctly, and I had even begun to download the Package files when the timeout "sprung" and knocked me offline. I installed from the most recent floppy build, everything seemed to go alright. I have no idea what is causing this self-healing "feature", I was hoping that someone with more experience than me would have some ideas as to where to look. - BOHICA btw: I have noticed that I no longer need any passwords to login, not even as root! Could this be related to the self-healing? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, December 25, 1998 15:22 To: BOHICA Cc: debian-user@lists.debian.org Subject: Re: Modem trouble, Please help!! BOHICA writes: > Where/How do I change this and make it stay changed? Get rid of whatever is changing it back. Something that is running at boot is changing it back. This is a serious bug. I recall that you said that this is a laptop. Are you using any pcmcia stuff? -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED] Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: Modem trouble, Please help!!
Thank you to all that helped. I never did find any script that appeared to be responsible for the miraculous "healing" of the inittab file. The final resolution was to install the 2.1 base disks with the 2.0 rescue and driver floppies, download the latest kernel and use a linux/bash emulator on my NT desktop to build a custom compilation of the kernel that included the needed Xircom support. I tried emailing the disk maintainer ([EMAIL PROTECTED]) about the problems I experienced with the latest disks, but got a bounce saying that no such user existed. If anyone knows an alternate means of reaching him, please let me know. - BOHICA -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, December 25, 1998 19:46 To: BOHICA Cc: debian-user@lists.debian.org Subject: Re: Modem trouble, Please help!! BOHICA writes: > btw: I have noticed that I no longer need any passwords to login, not > even as root! Worser and worser. > Could this be related to the self-healing? Could be. If so, I'm wrong about pcmcia. This begins to sound like a bug in boot-floppies, but I would have though someone else would have seen it by now. I believe that there are some self-removing install scripts. Perhaps one of them was not removed. Could you hunt around for odd-looking scripts? -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED] Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address.
Can anyone suggest a dialup terminal emulator?
General question: As part of my job I have to maintain several pieces of older network/switch equipment. To access them I need a VT220 - VT520 emulator that can handle: Zmodem, Ymodem, Xmodem and Ymodem 1K transfer protocols, VT/ASCII graphics, 7 or 8 bit characters, and function key remapping. It should also be able to access and dial a modem and soft set to 9600 baud. I have seen several such in the comm section, but rather than install all of them and have to run trial/error, I was hoping to glean some knowledge from the list as to which one or ones will work best for my purposes. Thanks, - BOHICA
X manager installation changes /dev/mouse from psaux to ttyS0
For both hamm and slink installs: On installing the X11 packages (WindowMaker -- hoping to follow it with fvwm2 or Gnome), my mouse and my modem stopped working. When I looked into possible causes I discovered that somewhere in the install, /dev/mouse => /dev/psaux is changed to /dev/mouse => /dev/ttyS0. This causes a few problems in that my modem is connected to what the BIOS calls COM1 (ttyS0) and the mouse is connected to a 6-pin mini DIN receptacle attached to the motherboards PS/2 mouse port. Until the X11 install runs, both the modem and the mouse work properly. After, neither works. I tried re-symlinking /dev/mouse to /dev/psaux BOHICA:/dev$ rm mouse BOHICA:/dev$ ln -s /dev/mouse /dev/psaux but for some reason this causes /dev/psaux to link to /dev/ttyS0. So now I have: /dev/mouse => /dev/ttyS0 and /dev/psaux => /dev/ttyS0 Can anyone help me resolve this? I am quite out of my depth here (not that I was too deep to begin with). - BOHICA --- please CC: me on all replies.
X11 and fvwm2: how to set screen size
General question: I have a Toshiba laptop (Portege 610CT) I have v2.1 installed and running, X11 with fvwm2 running with good screen resolution and 16bpp colors. Currently the resolution is set to 800x600, but the display still thinks that it is in 640x480 mode. This causes a lot of dynamic scrolling to get to border bars, etc. When I had (*gasp*) Windows 95/98 on the laptop, 800x600 was small, but perfectly legible without the "virtual desktop" effect and scrolling screens. The question I have is: Is there a way to force the X11 or fvwm2 to "shrink" the virtual desktop to physical screen dimensions? Any and all help is appreciated! - BOHICA -- One People, One World, One Program - Microsoft Promotional Ad Ein Volk, Ein Reich, Ein Fuhrer - Adolf Hitler [shamelessly stolen from another debian list]
Re: X11 and fvwm2: how to set screen size
Well I tried this, commented out the "Virtual" setting and indeed it kept me from "panning" to the extended screen, only problem was that the extended sections did not "condense" in to the physical limits of the screen. Went back and removed the comment mark and restarted X11, still had no ability to pan to the virtual screen size. Rebooted, same issue: the XF86Config file has been restored to the original and I still can't pan to the edges of the virtual screen. Help?!??? - BOHICA "Robert V. MacQuarrie" wrote: > On Mon, 1 Feb 1999, BOHICA wrote: > >Currently the resolution is set to 800x600, but the display still thinks > >that it is in 640x480 mode. This causes a lot of dynamic scrolling to > >get to border bars, etc. When I had (*gasp*) Windows 95/98 on the > >laptop, 800x600 was small, but perfectly legible without the "virtual > >desktop" effect and scrolling screens. > >The question I have is: Is there a way to force the X11 or fvwm2 to > >"shrink" the virtual desktop to physical screen dimensions? > > Open /etc/X11/XF86Config and look in the 'Section "Screen"' section and > comment out the 'Virtual' lines. This will make the display whatever you > have in your 'Modes' lines.. > # ** > # Screen sections > # The Colour SVGA server > Section "Screen" > Driver "svga" > #Use Device "Generic VGA" for Standard VGA 320x200x256 > #Device "Generic VGA" > Device "Matrox Millennium" > Monitor "Princeton Graphics EO90" > Subsection "Display" > Depth 16 > # Omit the Modes line for the "Generic VGA" device > Modes "1600x1200" "1024x768" "800x600" "1280x1024" "640x400" > ViewPort0 0 > # Use Virtual 320 200 for Generic VGA > Virtual 1600 1280 > ^^==(Comment out this line with a #) > > #Options "power_saver" > EndSubsection > > --Hope this helps > > # > Robert V. MacQuarrie Web Designing For Both > [EMAIL PROTECTED] Personal And Small Business Solutions > PGP Key Request: Reply to this email with the subject as "request pgpkey" > #
Re: X11 and fvwm2: how to set screen size
OK, gave that a try and completely toasted the X server (thankfully I learned early in my computing life to keep a detailed changelog), I had to boot from Rescue disk and edit the XF86Config file to get it back. At this point, the XF86Config is the same as when the system was first installed. I would be happy just to get the "panning" feature back! The X server is showing an 800x600 display resolution, but has (apparently) decided that the screen can only display 640x480, this leads to edges of windows running off the screen, etc. According to the specs from Toshiba, this particular laptop has a Chips&Tech CT65546 chipset with an active matrix LCD screen capable of [EMAIL PROTECTED] horizontal refresh rate. It operates 640x480 as default with what it calls "screen stretching" to take up the infamous black border. Can anyone enlighten me as to how to accomplish two things: primarily - Get the "panning" feature turned back on secondarily - figure out how to configure the X server such that it does not need "virtual" windows space - BOHICA Dan Willard wrote: > You should just have to set the acual screen size and the virtual > screen size to the same thing. (Provided that I remember the topic of > conversation correct). > > --Dano > > > -Original Message- > > From: BOHICA [SMTP:[EMAIL PROTECTED] > > Sent: Tuesday, February 02, 1999 6:48 AM > > To: Robert V. MacQuarrie; debian-user@lists.debian.org > > Subject: Re: X11 and fvwm2: how to set screen size > > > > Well I tried this, commented out the "Virtual" setting and indeed it > > kept me > > from "panning" to the extended screen, only problem was that the > > extended > > sections did not "condense" in to the physical limits of the screen. > > > > Went back and removed the comment mark and restarted X11, still had no > > ability to pan to the virtual screen size. Rebooted, same issue: the > > XF86Config file has been restored to the original and I still can't > > pan to > > the edges of the virtual screen. > > > > Help?!??? > > > > - BOHICA > > > > "Robert V. MacQuarrie" wrote: > > > > > On Mon, 1 Feb 1999, BOHICA wrote: > > > >Currently the resolution is set to 800x600, but the display still > > thinks > > > >that it is in 640x480 mode. This causes a lot of dynamic scrolling > > to > > > >get to border bars, etc. When I had (*gasp*) Windows 95/98 on the > > > >laptop, 800x600 was small, but perfectly legible without the > > "virtual > > > >desktop" effect and scrolling screens. > > > >The question I have is: Is there a way to force the X11 or fvwm2 to > > > >"shrink" the virtual desktop to physical screen dimensions? > > > > > > Open /etc/X11/XF86Config and look in the 'Section "Screen"' section > > and > > > comment out the 'Virtual' lines. This will make the display whatever > > you > > > have in your 'Modes' lines.. > > > # > > ** > > > # Screen sections > > > # The Colour SVGA server > > > Section "Screen" > > > Driver "svga" > > > #Use Device "Generic VGA" for Standard VGA 320x200x256 > > > #Device "Generic VGA" > > > Device "Matrox Millennium" > > > Monitor "Princeton Graphics EO90" > > > Subsection "Display" > > > Depth 16 > > > # Omit the Modes line for the "Generic VGA" device > > > Modes "1600x1200" "1024x768" "800x600" "1280x1024" > > "640x400" > > > ViewPort0 0 > > > # Use Virtual 320 200 for Generic VGA > > > Virtual 1600 1280 > > > ^^==(Comment out this line with a #) > > > > > > #Options "power_saver" > > > EndSubsection > > > > > > --Hope this helps > > > > > > > > ## > > ### > > > Robert V. MacQuarrie Web Designing For Both > > > [EMAIL PROTECTED] Personal And Small Business > > Solutions > > > PGP Key Request: Reply to this email with the subject as "request > > pgpkey" > > > > > ## > > ### > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] > > < /dev/null
Rescue disk's cfdisk reports HDD is corrupt
I've done searches at the list archive and FAQ-O-MATIC for similar problems, but it would seem I've found a new one. System Config: IBM PC 300PL 368Mb RAM 10Mb IDE HDD, 512Mb FAT, 3092 NTFS, remainder unpartitioned Windows NT 4 SP5 (required for RealWork(tm)) Goal: Install Debian on the unpartitioned region of the disk and modify boot.ini to run bootsect.lnx as an option. (Which I have done on several other machines without any difficulty.) Problem: On running install.bat from DOS (512Mb FAT partition), I cannot get cfdisk to run successfully. The error message reports that "THE PARTITION IS CORRUPT!" and then offers to wipe the partition table for me and start over - not exactly the best choice option for me. Question: Does anyone have any suggestions on what might be causing the error? Has this been seen before and I missed the post? Or is this a bug report for the maintainer/upstream developer? TIA, - BOHICA
Points to Ponder
If the author of the utility loadlin.exe (Hans Lerman) has stated on his web page (http://elserv.ffm.fgan.de/~lermen) that all versions greater than 2.1.22 should be installed with the updated version of loadlin (v1.6a) due to memory detection problems, why is Debian still distributing v1.6? Why doesn't Debian also distribute the loadlin manual and parameters documents (total 32Kb and 13Kb respectively) when the loadlin.exe file refers to them for help with settings, switches, etc.? Or at least post the link to Hans Lermen's homepage on the main debian.org website? When the SLINK distribution was frozen, why weren't the installation documents upgraded as well? They should address the fact that the 1.73Mb floppy will not work for some machines and that a separate ROOT floppy is also needed in addition to the usual disks if a floppy install is done. Why hasn't a LINUX kernel file been included with the SLINK distribution to allow for installation with the loadlin.exe program without the file system errors the floppy version of the LINUX kernel file causes? Has anyone noticed that the frozen SLINK distribution is _exactly_ the same as the proposed "new" potato distribution? - BOHICA
Jaz 1Gb on hamm dist
I have recently gotten v2.0 installed on my desktop, however, due to space restrictions on my primary disk I am keeping the binaries, etc on a Jaz 1Gb cartridges. These cartridges were low leveled by the SYMBIOS 22801 controller prior to being formatted by MS-DOS 6.22 MS-DOS 6.22 scandisk reported no errors or surface flaws. Currently the Jaz device resides at /dev/sdc2, SCSI ID 6 on the A channel of the controller. In all version of DOS that I own (going back to PC-DOS v2.04) when I boot with the Iomega drivers I can read the cartridges without any problems, however, from Linux I get a mount error that reads: MSDOS filesystem not found or too many devices mounted. Since this is the only device I am trying to mount when this error occurs and I have successfully mounted the CD-ROM I do not think I am out of mount points. I have tried the following methods: mount -t vfat /dev/sdc2 /jaz mount -t msdos /dev/sdc2 /jaz mount /dev/sdc2 /jaz mount -t nfs /dev/sdc2 /jaz All return the same error about incorrect/unknown file system. Can anyone enlighten me as to the correct method to mount this bugger? - BOHICA
RE: Jaz 1Gb on hamm dist
has different physical/logical endings: phys=(357, 116, 40) logical=(1203314, 30, 19) Partition 1 does not end on cylinder boundary: phys=(357, 116, 40) should be (357, 63, 32) /dev/sdc2 ? 648482 649505 912677269488144 6b Unknown Partition 2 has different physical/logical beginnings (non-Linux?): phys=(288, 110, 57) logical=(649504, 0, 11) Partition 2 has different physical/logical endings: phys=(269, 101, 57) logical=(912676, 1, 10) Partition 2 does not end on cylinder boundary: phys=(269, 101, 57) should be (269, 63, 32) /dev/sdc3 ? 262490 263179 945973699181456 53 Unknown Partition 3 has different physical/logical beginnings (non-Linux?): phys=(345, 32, 19) logical=(263178, 26, 16) Partition 3 has different physical/logical endings: phys=(324, 77, 19) logical=(945972, 51, 15) Partition 3 does not end on cylinder boundary: phys=(324, 77, 19) should be (324, 63, 32) /dev/sdc4 * 680024 680971 68098110668+ 49 Unknown Partition 4 has different physical/logical beginnings (non-Linux?): phys=(87, 1, 0) logical=(680970, 34, 16) Partition 4 has different physical/logical endings: phys=(335, 78, 2) logical=(680980, 61, 8) Partition 4 does not end on cylinder boundary: phys=(335, 78, 2) should be (335, 63, 32) -- end - - BOHICA -Original Message- From: Brandon Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, December 06, 1998 20:01 To: BOHICA Cc: debian-user@lists.debian.org Subject: Re: Jaz 1Gb on hamm dist On Sun, 6 Dec 1998, BOHICA wrote: > In all version of DOS that I own (going back to PC-DOS v2.04) when I boot > with the Iomega drivers I can read the cartridges without any problems, > however, from Linux I get a mount error that reads: MSDOS filesystem not > found or too many devices mounted. Can you send me (and the list too) the output of "dmesg" and "fdisk -l" with the cartridge in the drive? This will help verify you are using the correct device. Brandon +--- ---+ | Brandon Mitchell * [EMAIL PROTECTED] * http://bhmit1.home.ml.org/ | | Sometimes you have to release software with bugs. - MS Recruiter | -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: Jaz 1Gb on hamm dist
Thank You for the help, I tried /dev/sdc4 without success and then sequentially tried /dev/sdc1 and /dev/sdc2, no luck there either. Then, on a wild hunch I tried mounting /dev/sdc without specifying a number and it worked! I have no idea why it worked, but your suggestions did put me on the right path so I'm not going to look this gift horse too closely in the mouth. Again, thank you. - BOHICA -Original Message- From: Brandon Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, December 06, 1998 21:58 To: BOHICA Cc: debian-user@lists.debian.org Subject: RE: Jaz 1Gb on hamm dist I wrote: > Can you send me (and the list too) the output of "dmesg" and "fdisk -l" > with the cartridge in the drive? This will help verify you are using the > correct device. On Sun, 6 Dec 1998, BOHICA wrote: > dmesg - > > Vendor: iomegaModel: jaz 1GB Rev: H.72 > Type: Direct-Access ANSI SCSI revision: 02 > Detected scsi removable disk sdc at scsi1, channel 0, id 5, lun 0 Ok, sdc is correct. > --- fdisk -l > > Disk /dev/sdc: 64 heads, 32 sectors, 1021 cylinders > Units = cylinders of 2048 * 512 bytes > >Device Boot BeginStart End Blocks Id System > /dev/sdc1 ? 937318 937477 1203315272218546+ 20 Unknown > Partition 1 has different physical/logical beginnings (non-Linux?): > phys=(356, 97, 46) logical=(937476, 3, 15) > Partition 1 has different physical/logical endings: > phys=(357, 116, 40) logical=(1203314, 30, 19) > Partition 1 does not end on cylinder boundary: > phys=(357, 116, 40) should be (357, 63, 32) > /dev/sdc2 ? 648482 649505 912677269488144 6b Unknown > Partition 2 has different physical/logical beginnings (non-Linux?): > phys=(288, 110, 57) logical=(649504, 0, 11) > Partition 2 has different physical/logical endings: > phys=(269, 101, 57) logical=(912676, 1, 10) > Partition 2 does not end on cylinder boundary: > phys=(269, 101, 57) should be (269, 63, 32) > /dev/sdc3 ? 262490 263179 945973699181456 53 Unknown > Partition 3 has different physical/logical beginnings (non-Linux?): > phys=(345, 32, 19) logical=(263178, 26, 16) > Partition 3 has different physical/logical endings: > phys=(324, 77, 19) logical=(945972, 51, 15) > Partition 3 does not end on cylinder boundary: > phys=(324, 77, 19) should be (324, 63, 32) > /dev/sdc4 * 680024 680971 68098110668+ 49 Unknown > Partition 4 has different physical/logical beginnings (non-Linux?): > phys=(87, 1, 0) logical=(680970, 34, 16) > Partition 4 has different physical/logical endings: > phys=(335, 78, 2) logical=(680980, 61, 8) > Partition 4 does not end on cylinder boundary: > phys=(335, 78, 2) should be (335, 63, 32) > > -- end - Ack, looks like the standard dos/mac formatting trick. Try sdc4: mount /dev/sdc4 /jaz Or if it doesn't detect it: mount -t vfat /dev/sdc4 /jaz mount -t msdos /dev/sdc4 /jaz You may also want to try sdc1 and sdc3 if 4 doesn't work. HTH, Brandon +--- ---+ | Brandon Mitchell * [EMAIL PROTECTED] * http://bhmit1.home.ml.org/ | | Sometimes you have to release software with bugs. - MS Recruiter |
