Linux-Setup Digest #130, Volume #21 Sun, 29 Apr 01 13:13:10 EDT
Contents:
Re: Burning Red Hat 7.1 CDs. Bizarre failure. (Hans Deragon)
installation problem caldera e-desktop 2.4 (auke)
Re: Is it possible to dual boot without a bootloader? (Chiefy)
Re: Writing a little script (help with sed) ("Michael Pye")
Re: Writing a little script (help with sed) ("Michael Pye")
Re: how to fine-tune my dot printer (John Thompson)
Re: Epson driver (John Thompson)
Re: RH7.1 Instal. can't write boot loader (Troels Riis)
Re: Writing a little script (help with sed) ("Michael Pye")
Re: Burning Red Hat 7.1 CDs. Bizarre failure. ("Peter T. Breuer")
Re: Writing a little script (help with sed) ("Peter T. Breuer")
Re: Burning Red Hat 7.1 CDs. Bizarre failure. (Hans Deragon)
Re: Writing a little script (help with sed) ("Peter T. Breuer")
Re: Mandrake 8.0 install hang iso (Bit Twister)
Re: Writing a little script (help with sed) ("Michael Pye")
Re: Writing a little script (help with sed) ("Michael Pye")
Re: RAM detection (Bit Twister)
Re: Writing a little script (help with sed) ("Michael Pye")
Re: Burning Red Hat 7.1 CDs. Bizarre failure. ("Peter T. Breuer")
Re: lynx mouse support (Thomas Dickey)
PCMCIA modem / Lucent / Dynalink / ltmodem568.o (David Nowak)
Re: Is it possible to dual boot without a bootloader? (s)
----------------------------------------------------------------------------
From: Hans Deragon <[EMAIL PROTECTED]>
Subject: Re: Burning Red Hat 7.1 CDs. Bizarre failure.
Date: Sun, 29 Apr 2001 15:11:13 GMT
"Peter T. Breuer" a =E9crit :
> =
> Hans Deragon <[EMAIL PROTECTED]> wrote:
> > Steve Martin wrote:
> > # cdrecord -v speed=3D4 dev=3D0,0,0 -isosize -data seawolf-i386-disc=
1.iso
> =
> > ...and still got the following in /var/log/messages:
> =
> > Apr 29 08:35:54 world kernel: attempt to access beyond end of device
> > Apr 29 08:35:54 world kernel: 0b:00: rw=3D0, want=3D620786, limit=3D1=
89786
> > Apr 29 08:35:54 world kernel: dev 0b:00 blksize=3D2048 blocknr=3D3103=
92 sector=3D1241568 size=3D2048 count=3D1
> =
> You appear to have cds that hold 620784 KB (not kB) of data. How big is=
> the image you are trying to burn?
My CD-R are Maxell CD-R Branded Gold Surface 700 MB. The disk image is 6=
41 Mb.
Wait a minute. Is it possible that cdrecord does not burn all the image?=
Why
would it be so? I remember once I did:
# dd if=3D/cdrom of=3Dimage.iso
=2E.. from the defective Red Hat CD and noticed that image.iso was someth=
ing
like 180 Mb. I found it odd. Why would cdrecord not burn all the image?=
> Peter
Ciao
Hans
------------------------------
From: auke <[EMAIL PROTECTED]>
Subject: installation problem caldera e-desktop 2.4
Date: Sun, 29 Apr 2001 15:30:04 -0000
Mainboard: Asus P2B-S
CPU: Intel PIII-500
Mem: 64 Mb.
HD: Seagate 18 Gb SCSI-UW
Everytime I try to install Caldera 2.4 I get the following message:
"Kernel Panic: VFS: Unable to mount root fs on 03:03"
I cannot find out what the problem is. Is there anyone who can?
[EMAIL PROTECTED]
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (Chiefy)
Subject: Re: Is it possible to dual boot without a bootloader?
Date: 29 Apr 2001 15:39:05 GMT
29 Apr 2001 14:56 GMT, Cyber-Wizard did say to the dudes:
[snip]
> from. If I remove the 1.7Gb Linux drive from the drive bay the PC will
> not boot at all. Does anyone know how I might go about being able to
> boot into Linux by manual HDD BIOS selection?
How about restoring you old mbr, then re-install grub onto /dev/hda3
instead. Don't know how to go about such a task with said loader, but
Lilo would be easy to configure.
--
Chiefy <[EMAIL PROTECTED]>
Remember: LINUX spelled backwards is XUNIL.
------------------------------
From: "Michael Pye" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 16:30:33 +0100
"Mojo Nichols" <[EMAIL PROTECTED]> wrote
> will work. There must be a better way of getting the machine to not lose
time
> though, I have a similar problem except that my time is off by about 8
hours,
> so everytime I reboot I have to reset the clock. Does anybody now the
> "correct" way to solve this problem? Thanks
Possibly you suffer from a flat clock battery. Just have a check. Is the
time when you turn on the same as it was when you turned off?
It didn't need an equals last time I used it.
Nope, just checked the man pages. Definitely no "="...
MP
------------------------------
From: "Michael Pye" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 16:41:31 +0100
"William Burrow" <[EMAIL PROTECTED]> wrote
> Haven't tested it, but try:
>
> date -s "`date | sed s/1994/2001/`"
Cheers, I'll give it a try.
> The single quotes are back ticks, found above the TAB key.
>
> BTW, I think there is a fix for broken BIOSes out there, search
> Google.com for it.
It was actually in the middle of such a y2k fix that this one broke. The fix
was incomplete so the board can handle two digit year after the millennium
fine, but it can't remember them after powerdown...
Very strange, but it's still a useful machine for experimentation...
MP
------------------------------
From: John Thompson <[EMAIL PROTECTED]>
Subject: Re: how to fine-tune my dot printer
Date: Sun, 29 Apr 2001 06:34:13 -0500
Johnny Kim wrote:
> epson dot matrix 24-pin LQ-1550H
>
> tried redhat's 'printool' (in redhat 7.1 printconf)
> I think successfully configured my printer....
> (selected driver 'epson' because exact LQ-1550H entry not exist)
>
> but, test page printing somewhat look ugly
> i.e .. some characters look broken and vertical lines not aligned
> properly in table.
You may want to use the text-only driver, otherwise text gets
converted to bitmaps before going to the printer. DMP's (in my
experience) don't handle bitmapped fonts very well. Using
text-only will allow the printer to use it's built-in fonts which
generally come out much nicer.
--
-John ([EMAIL PROTECTED])
------------------------------
From: John Thompson <[EMAIL PROTECTED]>
Subject: Re: Epson driver
Date: Sun, 29 Apr 2001 06:37:25 -0500
Steve Kenealy wrote:
> Hi, I'm trying to find a Linux driver for an Epson 740 printer, and also
> an Epson 1240U scanner, if they exist. Any help appreciated.
Gimp-print should work nicely with the 740 printer. The newer
versions of ghostscript also have a 740-specific filter.
Sane should work for the scanner. Make sure you have the USB
support bilt for your kernel and check to see that the USB port
is detected by the kernel.
--
-John ([EMAIL PROTECTED])
------------------------------
From: Troels Riis <[EMAIL PROTECTED]>
Subject: Re: RH7.1 Instal. can't write boot loader
Date: Sun, 29 Apr 2001 17:57:18 +0200
Eric en Jolanda wrote:
> You need the root=/dev/hda3 option.
>
> If you have access to another linux machine, make a bootfloppy there.
> (for RH systems, just run `mkbootdisk <kernel-version>`)
> And boot from that using "linux root=/dev/hda3"
> (Perhaps try that from the RH CD, leave the rescue keyword?)
I have tried this. Leaving the rescue out just starts the anaconda again.
If I use rescue and mount root=.... then I get to a shell.
> /mnt/sysimage/sbin/lilo -C /mnt/sysimage/etc/lilo.conf
>
> But now it will probably complain that /dev/hda doesn't exist.
> And other inconsistencies.
Yes I have seen this with the /dev/hda does not exist a lot.
Using the /mnt/sys.... "solves" the lilo.conf position but then it needs
the boot.b in /boot. Even mounting /dev/hda1 as /mnt/sysimage/boot does
not help, then it cant write some boot~ file.
My boot looks strange, no linux or linuz files, is that lilo that
creates those ?
> The easiest way is by mounting /dev/hda3 at /
> This must be done at boottime
I assume you mean the linux root=.... thing.
I tried getting the toms boot disc, read the lilo-rescue-.. howto where they also
suggest doing
chroot /hda4 /sbin/lilo -q
or
/mnt/sysimage/sbin/lilo -r /hda4
no good!!! I cannot chroot..
If i do:
chroot /mnt/sysimage
I get:
/bin/sh: error while loading shared library: libtermcap.so.2: cannot
load shared object file: no such file or directory.
If I boot from toms floppy with hda3 mounted as root, it boots and then
stops after
VFS: Mount...
Unable to open an initial console
So though I am getting furhter I cannot go al the way, yet ?
Any ideas,
Troels
------------------------------
From: "Michael Pye" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 16:51:06 +0100
"William Burrow" <[EMAIL PROTECTED]> wrote
> Haven't tested it, but try:
>
> date -s "`date | sed s/1994/2001/`"
I get
bash: unexpected EOF while looking for "`"
bash: command substitution: line 2: syntax error
Any ideas
MP
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Burning Red Hat 7.1 CDs. Bizarre failure.
Date: Sun, 29 Apr 2001 17:41:10 +0200
Hans Deragon <[EMAIL PROTECTED]> wrote:
> "Peter T. Breuer" a 'ecrit :
>>
>> Hans Deragon <[EMAIL PROTECTED]> wrote:
>> > Steve Martin wrote:
>> > # cdrecord -v speed=4 dev=0,0,0 -isosize -data seawolf-i386-disc1.iso
>>
>> > ...and still got the following in /var/log/messages:
>>
>> > Apr 29 08:35:54 world kernel: attempt to access beyond end of device
>> > Apr 29 08:35:54 world kernel: 0b:00: rw=0, want=620786, limit=189786
>> > Apr 29 08:35:54 world kernel: dev 0b:00 blksize=2048 blocknr=310392
>sector=1241568 size=2048 count=1
>>
>> You appear to have cds that hold 620784 KB (not kB) of data. How big is
>> the image you are trying to burn?
> My CD-R are Maxell CD-R Branded Gold Surface 700 MB. The disk image is 641 Mb.
Do uou mean MB? If you really mean 10^6B, then please note that
620784KB is 635,682,816B, just under what you may mean as 641E6 B.
> Wait a minute. Is it possible that cdrecord does not burn all the image? Why
?? It burns what you tell it too. It looks to me as though your disks
are failing at the 635E6 mark during the burn. At least that's exactly
what the kernel message says! Mind you, if the limit= is the size of
the buffer it's trying to write, you're in even more trouble! Hmm ..
the message comes from ll_rw_blk.c, and I'm familiar with the code ..
if (maxsector < count || maxsector - count < sector) {
bh->b_state &= (1 << BH_Lock);
/* This may well happen - the kernel calls bread()
without checking the size of the device, e.g.,
when mounting a device. */
printk(KERN_INFO
"attempt to access beyond end of device\n");
printk(KERN_INFO "%s: rw=%d, want=%d, limit=%d\n",
kdevname(bh->b_rdev), rw,
(sector + count)>>1,
blk_size[major][MINOR(bh->b_rdev)]);
and count is bh->b_size >> 9, so it's the sector offset. Well, it's a
cert. The kernel has received a request to write (or read) beyond the
end of the device. It has either been told the wrong device size,
or the right one and the cd really is too small for what you are trying
to write to it. What is interesting is the limit= printout. That IS the
notified size of the device! And it's 189786 KB. The device registered
a size of only 194,340,864B. That's too small to write anything on.
Mind you, this is a READ request it is complaining about! (rw=0). SO
you might be seeing only the natural printout from the initial sizing
tests. Or this might be a read request after a write to check the burn.
> ... from the defective Red Hat CD and noticed that image.iso was something
> like 180 Mb. I found it odd. Why would cdrecord not burn all the image?
I dunno. Why would you think that it doesn't? Motives are always hard
to discern!
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 17:42:49 +0200
In comp.os.linux.misc Michael Pye <[EMAIL PROTECTED]> wrote:
> Possibly you suffer from a flat clock battery. Just have a check. Is the
Mine is also flat. Are spherical ones better?
;)Peter
------------------------------
From: Hans Deragon <[EMAIL PROTECTED]>
Subject: Re: Burning Red Hat 7.1 CDs. Bizarre failure.
Date: Sun, 29 Apr 2001 16:04:25 GMT
Hans Deragon wrote:
> Greetings.
>
> How does one burn the Red Hat 7.1 iso images? I am new to CD
> burning and have recently aquired an HP 9150 burner. Following
> is what I do:
>
> # cdrecord -v speed=4 dev=0,0,0 -data seawolf-i386-disc1.iso
>
> Everything seams to go nice, but then when I test it, I get the
> following:
>
> # mount -t iso9660 /dev/cdrom /cdrom
> # cd /cdrom/RedHat/base
> # cat TRANS.TBL
> cat: TRANS.TBL: Input/output error
>
> ...and in /var/log/messages, I see:
>
> Apr 27 08:35:27 snah kernel: attempt to access beyond end of device
> Apr 27 08:35:27 snah kernel: 16:40: rw=0, want=495104, limit=34848
> Apr 27 08:35:27 snah kernel: dev 16:40 blksize=2048 blocknr=247551 sector=990204
>size=2048 count=1
> Apr 27 08:35:27 snah kernel: attempt to access beyond end of device
> Apr 27 08:35:27 snah kernel: 16:40: rw=0, want=495106, limit=34848
> Apr 27 08:35:27 snah kernel: dev 16:40 blksize=2048 blocknr=247552 sector=990208
>size=2048 count=1
>
> The MD5 checksums of my iso images are ok. When I mount the
> seawolf-i386-disc1.iso on the loopback device:
>
> # mount -t iso9660 -o ro,loop=/dev/loop0 seawolf-i386-disc1.iso /test
>
> ...I have no problems.
>
> I tried burning twice. Either my HP 9150 cd burner does not cut it,
> or I am missing a parameter.
>
> Anybody got a clue?
>
> Sincerely,
> Hans Deragon
>
> P.S. If this message sounds familiar, it is. I posted this message in
> linux.redhat.install, but no one could provide me help. I hope
> by posting to this newsgroup I would target a more appropriate
> audiance for my problem.
>
> Keywords: red hat redhat 7.1 cdrom 9150 iso burn md5 kernel hans deragon
Crap. I never noticed before that cdrecord complained! I always assume that it would
stop promptly if an error occured. Here is its output:
================>
# cdrecord -v speed=4 dev=0,0,0 -isosize -data seawolf-i386-disc1.iso
Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 2.1.39
Using libscg version 'schily-0.1'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'HP '
Identifikation : 'CD-Writer+ 9100b'
Revision : '1.07'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
Drive buf size : 1024000 = 1000 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 641 MB
Total size: 736 MB (72:58.40) = 328380 sectors
Lout start: 736 MB (73:00/30) = 328380 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 4
Is not unrestricted
Is not erasable
Disk sub type: Medium Type B, low Beta category (B-) (4)
ATIP start of lead in: -11752 (97:25/23)
ATIP start of lead out: 359849 (79:59/74)
Disk type: Long strategy type (Cyanine, AZO or similar)
Manuf. index: 8
Manufacturer: Hitachi Maxell, Ltd.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 31469
Starting to write CD/DVD at speed 4 in write mode for single session.
Last chance to quit, starting real write in 1 seconds.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01: 87 of 641 MB written (fifo 100%).cdrecord: Input/output error. write_g1:
scsi sendcmd:
retryable error
status: 0x2 (CHECK CONDITION)
CDB: 2A 00 00 00 AE 03 00 00 1F 00
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
write track data: error after 91232256 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
Writing time: 162.671s
Fixating...
Fixating time: 66.581s
cdrecord: fifo had 1501 puts and 1438 gets.
cdrecord: fifo was 0 times empty and 1426 times full, min fill was 93%.
<---------------
Nothing came out in /var/log/messages. Anybody has a clue what is going on?
Sincerely,
Hans Deragon
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 18:07:17 +0200
In comp.os.linux.misc Michael Pye <[EMAIL PROTECTED]> wrote:
> "William Burrow" <[EMAIL PROTECTED]> wrote
>> Haven't tested it, but try:
>>
>> date -s "`date | sed s/1994/2001/`"
> I get
> bash: unexpected EOF while looking for "`"
> bash: command substitution: line 2: syntax error
> Any ideas
Type correctly. (Suspect yourself before blaming others).
Peter
------------------------------
From: [EMAIL PROTECTED] (Bit Twister)
Subject: Re: Mandrake 8.0 install hang iso
Reply-To: [EMAIL PROTECTED]
Date: Sun, 29 Apr 2001 16:17:04 GMT
During my install it indicated it could not create the ram disk.
Also could not write the partition table after partition and formating.
Posted my hardware on the net and other pople had no problems.
Re-downloaded ISOs, did the, md5sum iso_name_here, they verifed,
burned new cds and had no problems installing.
Have you md5sum your_isos_name_here ?
On Sun, 29 Apr 2001 14:30:03 -0000, Juan <[EMAIL PROTECTED]> wrote:
>I gotta the iso files of MK8.0 in hd, everything goes good in the install
>until the message "getting info on packages", sometimes it just hangs
>there (in recommended and expert) , other times it continues, i select the
>packages in that ugly tree, later the install gauge screen appears and it
>hangs at the begining or 2 minutes or so.
>but once i gotta installed mandrake, with the same iso (cause it didnt
>even ask the ext disk, didnt installed anything from it)
>of 10 attemps :
>6 hangs at "getting info"
>3 hangs at "installing, please wait"
>1 ok install w/o second disk
>slackware worked fine on this machine
>
>PIII SiS Motherboard 128 RAM
>win98 partition
>samsung drives(all)
>cmp sound chip
>winmodem (i know)
>
------------------------------
From: "Michael Pye" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 17:08:27 +0100
"Michael Pye" <[EMAIL PROTECTED]> wrote
> > Haven't tested it, but try:
> >
> > date -s "`date | sed s/1994/2001/`"
>
> I get
>
> bash: unexpected EOF while looking for "`"
> bash: command substitution: line 2: syntax error
>
I've sorted it. Thanks.
I prefer the "$(date | sed...)" form though, I find it less confusing...
Thanks for your help.
MP
------------------------------
From: "Michael Pye" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 17:09:21 +0100
"Peter T. Breuer" <[EMAIL PROTECTED]> wrote
> Mine is also flat. Are spherical ones better?
>
> ;)Peter
Gosh, aren't we a comedian! ;)
I think you'll find the alternatives are cylinders actually...
MP
------------------------------
From: [EMAIL PROTECTED] (Bit Twister)
Subject: Re: RAM detection
Reply-To: [EMAIL PROTECTED]
Date: Sun, 29 Apr 2001 16:18:26 GMT
On Sun, 29 Apr 2001 18:48:38 +0800, Steve Yu <[EMAIL PROTECTED]> wrote:
>Why my Mandrake 7.0 linux only detects my system has 64MB only? But mine is
>192MB.
Read the last 4 lines of this post, I'll wait. . . . . . . . . . . . .
The examples here are for 128M. Change 128 to your memory value.
================= If using lilo ===========================
edit /etc/lilo.conf and add
append="mem=128M"
save changes, exit the editor, then
/sbin/lilo to install the change into the mbr.
Next boot should have the change
example:
timeout=50
append="mem=128M"
image=/boot/vmlinuz
or
append="mem=128M hdd=ide-scsi" if you already have an append cmd
================ if using grub ===========================
edit /boot/grub/menu.lst and add
mem=128M
Next boot should have the change
example:
title linux
kernel (hd1,4)/boot/vmlinuz root=/dev/hdb5 mem=128M
============== to replace lilo with grub ====================
cd /boot/grub
sh install.sh
============== Still having problems ===========================
http://www.linuxnewbie.org/nhf/intel/hardware/ramdetect.html
--
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a, man command_here or cat command_here, before using it.
------------------------------
From: "Michael Pye" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.misc
Subject: Re: Writing a little script (help with sed)
Date: Sun, 29 Apr 2001 17:20:30 +0100
"Peter T. Breuer" <[EMAIL PROTECTED]> wrote
> Type correctly. (Suspect yourself before blaming others).
He did say it wasn't tested.
Though you were right, turns out I put the slashes in the wrong way
around...
My lesson in humility. ;)
MP
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Burning Red Hat 7.1 CDs. Bizarre failure.
Date: Sun, 29 Apr 2001 16:29:19 GMT
Hans Deragon <[EMAIL PROTECTED]> wrote:
> Hans Deragon wrote:
>> Apr 27 08:35:27 snah kernel: 16:40: rw=0, want=495104, limit=34848
>> Apr 27 08:35:27 snah kernel: dev 16:40 blksize=2048 blocknr=247551 sector=990204
>size=2048 count=1
>> Apr 27 08:35:27 snah kernel: attempt to access beyond end of device
>> Apr 27 08:35:27 snah kernel: 16:40: rw=0, want=495106, limit=34848
The limit is absurdly small. At 512B sectors it represents a 17MB
device. At 2KB sectors, it's a 34MB device. ll_rw_blk.c was bound to
complain. It looks like the size is erither modified continually by the
scsi midlayer code as the thing runs along, or the device reports the
wrong maximum.
> Crap. I never noticed before that cdrecord complained! I always assume that it
>would
> stop promptly if an error occured. Here is its output:
Well ...
> # cdrecord -v speed=4 dev=0,0,0 -isosize -data seawolf-i386-disc1.iso
> Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jrg Schilling
> TOC Type: 1 = CD-ROM
> scsidev: '0,0,0'
> scsibus: 0 target: 0 lun: 0
> Linux sg driver version: 2.1.39
> Using libscg version 'schily-0.1'
> atapi: 1
> Device type : Removable CD-ROM
> Version : 0
> Response Format: 1
> Vendor_info : 'HP '
> Identifikation : 'CD-Writer+ 9100b'
> Revision : '1.07'
> Device seems to be: Generic mmc CD-RW.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags : SWABAUDIO
> Drive buf size : 1024000 = 1000 KB
> FIFO size : 4194304 = 4096 KB
> Track 01: data 641 MB
> Total size: 736 MB (72:58.40) = 328380 sectors
> Lout start: 736 MB (73:00/30) = 328380 sectors
This is too large for your claimed 700MB, and too large for the
reported 641MB, no? If it's the data size, that is!
> Current Secsize: 2048
> ATIP info from disk:
> Indicated writing power: 4
> Is not unrestricted
> Is not erasable
> Disk sub type: Medium Type B, low Beta category (B-) (4)
> ATIP start of lead in: -11752 (97:25/23)
> ATIP start of lead out: 359849 (79:59/74)
uh ... negative initial padding?
> Disk type: Long strategy type (Cyanine, AZO or similar)
> Manuf. index: 8
> Manufacturer: Hitachi Maxell, Ltd.
> Blocks total: 359849 Blocks current: 359849 Blocks remaining: 31469
confusing arithmetic.
> Starting to write CD/DVD at speed 4 in write mode for single session.
> Last chance to quit, starting real write in 1 seconds.
> Waiting for reader process to fill input buffer ... input buffer ready.
> Performing OPC...
> Starting new track at sector: 0
> Track 01: 87 of 641 MB written (fifo 100%).cdrecord: Input/output error. write_g1:
>scsi sendcmd:
> retryable error
Error at 90MB.
> status: 0x2 (CHECK CONDITION)
> CDB: 2A 00 00 00 AE 03 00 00 1F 00
> Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
> Sense flags: Blk 0 (not valid)
The device errored.
> write track data: error after 91232256 bytes
> Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
> Writing time: 162.671s
> Fixating...
> Fixating time: 66.581s
> cdrecord: fifo had 1501 puts and 1438 gets.
> cdrecord: fifo was 0 times empty and 1426 times full, min fill was 93%.
> Nothing came out in /var/log/messages. Anybody has a clue what is going on?
direct kernel mesages somewhere visible. Looks like hardware. Slow it
down.
Peter
------------------------------
From: Thomas Dickey <[EMAIL PROTECTED]>
Subject: Re: lynx mouse support
Date: 29 Apr 2001 16:34:42 GMT
[EMAIL PROTECTED] wrote:
> gpm is working fine with mc and linuxconfig. Does this me I have gmp
> configured into the version of ncurses I'm using? If it does, do you have
> any idea what needs to be done to get lynx using it as well?
ldd would show what libraries are linked in a given application (I'm not
sure which ones you might have: though mc can be built with ncurses, it's
usually done with slang, while linuxconfig is usually ncurses - but I don't
keep track of those particular programs closely).
--
Thomas E. Dickey <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
http://dickey.his.com
ftp://dickey.his.com
------------------------------
From: David Nowak <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: PCMCIA modem / Lucent / Dynalink / ltmodem568.o
Date: Sun, 29 Apr 2001 17:46:59 +0100
Hi,
When I 'insmod' the module ltmodem568.o, it does not work and write:
ltmodem568.o: init_module: Device or resource busy
Hint: this error can be caused by incorrect module parameters, including
invalid IO or IRQ parameters
What does it mean? What can I do?
Technical details:
I have a Dynalink PCMCIA 56K Fax Modem. The command 'cardctl ident'
returns:
product info: "V90&K56Flex PCMCIA FAX MODEM", "", "", ""
Under Windows, the driver file is called LTMODEM.VDX. That is why I
think I need to use a Lucent driver (I use ltmodem-5.78e.tar.gz).
According to Windows, it uses ports 2F8-2FF and irq 3. Also my kernel
version is 2.2.17.
Thanks in advance for any help,
--
David
------------------------------
From: s <[EMAIL PROTECTED]>
Subject: Re: Is it possible to dual boot without a bootloader?
Crossposted-To: alt.os.linux.mandrake
Date: Sun, 29 Apr 2001 11:55:57 -0500
Sure. Boot into linux and make a boot floppy (there are gui frontends in
the kmenu). and then boot into dos and restore the windows mbr. Now if
you want to boot into linux, just stick in the floppy.
A lot better than changing the bios back and forth.
-s
Cyber-Wizard wrote:
> I have a 12Gb drive running Win2K and decided to learn about Linux to
> get out from under the M$ thumb. I have installed Mandrake on a 1.7Gb
> drive in a removable hard drive bay. I need this bay for other
> purposes and would like to simply select hda3 in the BIOS for booting
> into Linux when I want it. My problem is this, now that Linux is
> installed, GRUB is loading at boot no matter which drive I am booting
> from. If I remove the 1.7Gb Linux drive from the drive bay the PC will
> not boot at all. Does anyone know how I might go about being able to
> boot into Linux by manual HDD BIOS selection?
>
> Kevin Davison
> [EMAIL PROTECTED]
>
>
------------------------------
** 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 by posting to comp.os.linux.setup.
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-Setup Digest
******************************
