Hi Larry
 
I am not an expert in the internal of kernel device drivers but I need to contact someone who is and who can help me. The help desk staff at RedHat do not seem to have the necessary levels of expertise to sort out what is a very real problem with the linux kernels and in particular the differences between 2.0.36-0.7 (Linux 5.2) and 2.2.5-15 (Linux 6.0). My problem is that the kernels do not seem to be upwardly compatible.
 
I have a system which uses a modern BX board with built in AIC 7895 scsi controllers on which I have three scci 4.3 scci disks mounted. I also have an LS120 drive with a standard floppy. The reason for my upgrading from 5.2 to 6.0 was because of timeout problems on the scci bus where the 2.0.36 kernel keeps resetting after a timeout. The 6.0 system appears to be better in this respect but using the 2.2.5-15 kernel gives rise to more serious problems namely that the parallel port does not appear to have been configured in the kernel and I cannot gain access to my LS120 drive because it is not prperly detected by the system.
 
The essential fault appears to lie in the specification of the /proc/devices directory which is a virtual file system which forms part of the kernel. If you examine this directory on both the 2.0.36-07 (Linux Version 5.2) and 2.2.5-15 (Linux Version 6.0) kernels you will see that they are very different and that the key 'lp' item is missing from the 2.2.5-15 kernel. The label for the 'lp' item is 6 which I believe to be the major port number in the 'major minor' number port identifier sequence. The way in which the /proc directory is used by the rest of the system is critical but I have yet to find any documentation on this. To put matters right you would need to rebuild the kernel but Redhat do not provide the means to do this or of copies of the make files from which the kernels were originally constructed, so that their construction can be verified against their specification.
 
Doing a cat on the /proc/devices virtual directory for kernel 2.2.5-15
gave the following results

Character devices:    Block devices:
  1 mem                     1 ramdisk
  2 pty                        2 fd
  3 ttyp                       3 ide0
  4 ttyS                       8 sd
  5 cua                        9 md
  7 vcs                        22 ide1
 10 misc
 29 fb
 36 netlink
128 ptm
136 pts


The corresponding values for the 2.0.36-07 kernel were

Character devices:    Block devices:
  1 mem                  1 ramdisk
  2 pty                     2 fd
  3 ttyp                    3 ide0
  4 ttyp                    8 sd
  5 cua                    9 md
  6 lp                       22 ide1
  7 vcs
 10 misc

 
While the Block devices are the same the Character Devices differ significantly
 
I attach a copy of my correspondence with the RedHat Help desk
 
Thanks
 
Gerry Hooper
 
 
 
 
 
Title: Update Incident
redhat.com
BuySupportDownloadRedhat
Linux IndexKnowledgebaseDeveloper ResourcesUser GroupsApplication IndexDocumentation
Search foron   redhat.com Linux sites     powered by Google

 
 
Support home
FAQ
Search

Log out
Register product
New incident

My products
My incidents
My info
Support


Update Incident
Logged in as [EMAIL PROTECTED]

Contact Information:
[EMAIL PROTECTED]
Registration:
91b0460a956ce482Red Hat Linux 6.0/Intel
Product:
Red Hat Linux 6.0
Category:
Bugs and other Problems
Summary:
Mounting LS120 drives using 6.0 kernel
Your Previous Description:
On v5.2 I mount my LS120 drive OK
This uses an msdos filesystem supported by the 2.0.36 kernel
e.g. mount /dev/hdd /mnt/floppy2
works OK using an msdos filesystem


On v6.0 I cannot mount my LS120 drive because the 2.2.5-15 does not support the msdos filesystem. On boot the hdd device is linked to the LS120 drive as shown by the screen text but non of the filesystems can be used to mount the drive.

e.g non of these commands work
mount /dev/hdd /mnt/floppy2
mount -t ext2 /dev/hdd /mnt/floppy2
mount -t msdos /dev/hdd /mnt/floppy2
mount -t umsdos /dev/hdd /mnt/floppy2

How would you suggest that I proceed to mount my LS120 under the 2.2.5-15 kernel?

Thank You

Gerry Hooper

[EMAIL PROTECTED]

At 6/21/99 5:28 PM you wrote - Thanks for your response Marty
My apologies if you get this twice throgh a newer incident report

I have only just found the update botton on your screen


I have tried your suggestions as per original response

Both the msdos.o and vfat.o files are contained in the
/lib/modules/2.2.5-15/fs directory as you suggested.

However when I tried

mount -t vfat /dev/hdd /dev/floppy2
I get the message
fs type vfat not supported by kernel

also when I try
mount -t msdos /dev/hdd /dev/floppy2
I get the corresponding message
fs type msdos not supported by kernel

We are therefore back to square one.
How do you suggest that I proceed ?

Gerry Hooper

[EMAIL PROTECTED]


At 6/22/99 2:53 AM you wrote - I tried your suggestion to use
#insmod vfat
as root login: It did not work
I attach file showing result.
This file obtained by
#insmod vfat 2>> /tmp/gherr
Icould not mount a floppy under 2.2.5-15 kernel
Neither could I use my printer using the lpr command
I also could not produce printer output using
cat /tmp/gherr >> ttyS1
which is my printer port

I believe that the 2.2.5-15 kernel is a very sick beast
On boot up it does not recognise my printer by getting the hardware to respond
Also on boot up it does not perform a partition check on hdd

All of these things work ok on my original kernel 2.0.36

The file attached has been obtained by mounting the 2.0.36 kernel and then copying the file gherr to a mounted floppy.

This actual communication comes to you through my dual boot Windows 98 facilities

If I had to put my finger on the problems that exist with the 2.2.5-15 kernel I would look at the bits which mount the harware and check out the system during initialisation i.e at the init process

Please find attached the gherr file contents
The file attachment did not appear to work on your system so I am resending this again
At 6/22/99 2:58 PM you wrote - Hi Marty
I could not get the' add file attachment' mechanism attached to this system to work.It generated a message saying contact supervisor. I therefore sent you the error files through the RedHat sup-manager Email connection.
Basically the 2.2.5-15 Kernel only generates error messages from a command such as
#insmod vfat
(see Gherr file)

or
#insmod msdos
(see Gherr2 file)

My lpr utility also does not work

During boot up the kernel does not perform the same check actions that are carried out by the 2.0.36-37 kernel

As stated above I believe that the errors in the 2.2.5-15 kernel are in its use of the init process and that they are fatal !!

Perhaps you could get your development team to try them out on a similar architecture to my own?

Thanks

GerryAt 6/23/99 0:30 AM you wrote - Hi Marty
Thanks for your latest advice
I will try them out later to-doday
I did send you the error file through your sup-manager by Email
I have hand copied the vfat one below
The error file for msdos is very similar

/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_read_super_R7101628c
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_date_unix2dos_R83fb36a1
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_read_inode_Rf23f0483
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_put_inode_R00b60105
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_dir_operations_R060b8452
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_put_super_R6cc696f2
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_fs_panic_R240a9fc6
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_unlock_creation_R9e32cc5b
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_get_entry_R57ed075c
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_brelse_R2190b516
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_add_cluster_R71aedf1a
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_delete_inode_R6499d474
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_mark_buffer_dirty_R3a53e527
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_notify_change_Re08c2a5f
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_esc2uni_Rdf8b5a1e
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_write_inode_Rc75806f3
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_lock_creation_R4d85e995
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_scan_R84c7a6b4
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_cache_inval_inode_R173fe278
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_statfs_Rf5ee95c8
/lib/modules/preferred/fs/vfat.o: unresolved symbol fat_readdirx_Rd5f12b92

Hope this helps you to sort out the problems with the 2.2.5-15 kernel

Gerry

At 6/23/99 6:10 AM you wrote - HI MARTY
You were correct to pick up my typo error in my last input to you
/dev/ttyS1 should have read /dev/lp1
My apologies for the typing mistake

I have tried out what you have suggested and the problems remain

When using kernel 2.2.5

cat file > /dev/lp0
cat file > /dev/lp1
cat file > /dev/lp2
cat file | lpr
all generate the same error message which is
bash: ........ Operation not supported by device

When using kernel 2.0.36
cat file > /dev/lp1
cat file | lpr

work ok.

Now to the hdd problem
I copy now my /etc/fstab file for you to look at
I believe that this is ok


/dev/sdb3 / ext2 defaults 1 1
/dev/sda2 /boot ext2 defaults 1 2
/dev/sdb5 /home ext2 defaults 1 2
/dev/sdc3 /hoop ext2 defaults 1 2
/dev/sdb6 /opt ext2 defaults 1 2
/dev/sdb2 /usr ext2 defaults 1 2
/dev/sdc2 /usr/src ext2 defaults 1 2
/dev/sdc1 /var ext2 defaults 1 2
/dev/sdc4 /work ext2 defaults 1 2
/dev/sda3 swap swap defaults 0 0
/dev/fd0 /mnt/floppy ext2 noauto 0 0
/dev/hdd/mnt/floppy2ext2noauto,user0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,ro 0 0
none /proc proc defaults 0 0


There are however significant difference in the /var/dmesg files which are created by the two kernels. I therefore attach them now for your inspection and comments

The first file is for kernel 2.0.36

Memory: sized by int13 0e801h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios_init : BIOS32 Service Directory structure at 0x000fab20
pcibios_init : BIOS32 Service Directory entry at 0xfafa0
pcibios_init : PCI BIOS revision 2.10 entry at 0xfafd0
Probing PCI hardware.
Calibrating delay loop.. ok - 331.78 BogoMIPS
Memory: 127568k/131072k available (748k kernel code, 384k reserved, 2164k data)
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: IGMP, ICMP, UDP, TCP
Linux IP multicast router 0.07.
VFS: Diskquotas version dquot_5.6.0 initialized
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
Linux version 2.0.36 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Tue Oct 13 22:17:11 EDT 1998
Starting kswapd v 1.4.2.2
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
PS/2 auxiliary pointing device detected -- driver installed.
Real Time Clock Driver v1.09
Ramdisk driver initialized : 16 ramdisks of 4096K size
ide: i82371 PIIX (Triton) on PCI bus 0 function 57
ide0: BM-DMA at 0xf000-0xf007
ide1: BM-DMA at 0xf008-0xf00f
hdb: ATAPI CDROM, ATAPI CDROM drive
hdd: LS-120 CSMO 05 UHD Floppy, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8
scsi : 0 hosts.
scsi : detected total.
Partition check:
hdd: 123264kB, 963/8/32 CHS, 533 kBps, 512 sector size, 720 rpm
hdd: no media in the drive
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
(scsi0) <Adaptec AIC-7895 Ultra SCSI host adapter> found at PCI 12/0
(scsi0) Wide Channel A, SCSI ID=7, 32/255 SCBs
(scsi0) Downloading sequencer code... 404 instructions downloaded
(scsi1) <Adaptec AIC-7895 Ultra SCSI host adapter> found at PCI 12/1
(scsi1) Wide Channel B, SCSI ID=7, 32/255 SCBs
(scsi1) Downloading sequencer code... 404 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4
<Adaptec AIC-7895 Ultra SCSI host adapter>
scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4
<Adaptec AIC-7895 Ultra SCSI host adapter>
scsi : 2 hosts.
Vendor: IBM Model: DCAS-34330W Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: IBM Model: DDRS-34560 Rev: S97B
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 5, lun 0
Vendor: IBM Model: DDRS-34560 Rev: S97B
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi0, channel 0, id 6, lun 0
(scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB]
sda: sda1 sda2 sda3
(scsi0:0:5:0) Synchronous at 20.0 Mbyte/sec, offset 15.
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8925000 [4357 MB] [4.4 GB]
sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
(scsi0:0:6:0) Synchronous at 20.0 Mbyte/sec, offset 15.
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 8925000 [4357 MB] [4.4 GB]
sdc: sdc1 sdc2 sdc3 sdc4
VFS: Mounted root (ext2 filesystem) readonly.
Trying to unmount old root ... okay
Adding Swap: 130748k swap-space (priority -1)


The second file is for kernel 2.2.5-15

Linux version 2.2.5-15 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Apr 19 23:00:46 EDT 1999
Detected 332503754 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 331.78 BogoMIPS
Memory: 127816k/131072k available (996k kernel code, 412k reserved, 1572k data, 60k init)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium II (Deschutes) stepping 01
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.26 (19981001) Richard Gooch ([EMAIL PROTECTED])
PCI: PCI BIOS revision 2.10 entry at 0xfafd0
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
Initializing RT netlink socket
Starting kswapd v 1.5
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9)
Real Time Clock Driver v1.09
RAM disk driver initialized: 16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hdb: ATAPI CDROM, ATAPI CDROM drive
hdd: LS-120 CSMO 05 UHD Floppy, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hdb: ATAPI 36X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.54
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: using high-speed MMX checksum routine
pII_mmx : 809.244 MB/sec
p5_mmx : 784.098 MB/sec
8regs : 573.024 MB/sec
32regs : 411.480 MB/sec
using fastest function: pII_mmx (809.244 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
RAMDISK: Compressed image found at block 0
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem).
(scsi0) <Adaptec AIC-7895 Ultra SCSI host adapter> found at PCI 12/0
(scsi0) Wide Channel A, SCSI ID=7, 32/255 SCBs
(scsi0) Downloading sequencer code... 374 instructions downloaded
(scsi1) <Adaptec AIC-7895 Ultra SCSI host adapter> found at PCI 12/1
(scsi1) Wide Channel B, SCSI ID=7, 32/255 SCBs
(scsi1) Downloading sequencer code... 374 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.15/3.2.4
<Adaptec AIC-7895 Ultra SCSI host adapter>
scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.15/3.2.4
<Adaptec AIC-7895 Ultra SCSI host adapter>
scsi : 2 hosts.
(scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
Vendor: IBM Model: DCAS-34330W Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
(scsi0:0:5:0) Synchronous at 20.0 Mbyte/sec, offset 15.
Vendor: IBM Model: DDRS-34560 Rev: S97B
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 5, lun 0
(scsi0:0:6:0) Synchronous at 20.0 Mbyte/sec, offset 15.
Vendor: IBM Model: DDRS-34560 Rev: S97B
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi0, channel 0, id 6, lun 0
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB]
sda: sda1 sda2 sda3
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8925000 [4357 MB] [4.4 GB]
sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 8925000 [4357 MB] [4.4 GB]
sdc: sdc1 sdc2 sdc3 sdc4
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 60k freed
Adding Swap: 130748k swap-space (priority -1)


You will see that there is a major difference in the PARTITION CHECK SECTION

Hope this helps

Gerry








At 6/24/99 2:41 PM you wrote - Hello Marty ( 24/6/99 7.45 pm)
Thanks for your latest instructions to me.
I will try them out later when I have a little free time
In the meantime I will try to clear up some of the confusion

The situation is that I only have one machine which is a triple boot machine
At the front end I run System Commander which is a Windows 98 program.

System Commander allows me to boot between
a) A floppy drive
b) Windows 98
c) Red Hat Linux (Resident Kernel 2.2.5-15) v5.2 + Xfree 3.3.3.1

>From the floppy drive I can also boot Red Hat Linux 5.2 (Resident Kernel 2.0.36-37) + Xfree 3.3.3.1 which is the original kernel for 5.2

Kernels to Linux are meant to be upwards compatible so that in using Kernel 2.2.5-15 with the v5.2 software I thought I would be OK but apparently I am not.

The reason for going down this path will interest you.

I originally tried to install v6.0 from scratch. This failed because it did not detect my LS120 drive as does v5.2. I therefore reinstalled v5.2 and tried the alternative of using the Upgrade path to install version 6.0. This also failed because the system came back with a list of partitions that it had recognised and asked me to pick out my root partition. The only problem was that the list did not contain my root partition.

To overcome these problems I extracted the information to build a new kernel from the 6.0 disk 1 and did this following the instructions given in the book by Naba Barkati "Linux Secrets" and this worked OK. I therefore ended up with a 2.2.5-15 kernel on a v5.2 software system which itself had already been upgraded to Xfree 3.3.3.1.

At this point I tried once again to upgrade my v5.2 with the 2.2.5-kernel to the software for 6.0. This time it worked and it worked because during the upgrade process the request to select my /root partition never appeared.

This method of upgrading my system never really worked however and I could still not use my LS120 drive and the system kept freezing up on me. At this time the person at RedHat Software that I was dealing with had a user name called 'mgalgaci' . You may know him .

As a result of these problems I decided that I really could not use the software provided with version 6 of RedHat Linux and returned it to my supplier who is LinuxIT in the UK. I did however keep the boot up floppy for the 2.2.5-15 kernel and decided to continue with it to sort out the underlying problems with it. After all I would have liked to have been able to install this release of the software because otherwise I am likely to be stuck up a gum tree in the future. I therefore tried to approach the problems involved afresh which is whwn I began dealing with yourself.

I note that the dmesg file for kernel 2.2.5-15 does give an email address of
[EMAIL PROTECTED]
whereas the corresponding email address for the 2.0.36-37 kernel is
[EMAIL PROTECTED]
This suggests to me that the 2.2.5-15 kernel is still not fully developed and would explain why it had so many bugs and why it was not upwardly compatible with previous software. The 2.0.36-37 kernel appears to work differently particularly during the "partition check: ".e.g.
hdd: 123264kB, 963/8/32 CHS, 533 kBps, 512 sector size, 720 rpm

I also could not find any part of the dmesg in either kernel which verified the existence of the parallel port which uses IRQ 7 ? although both serial ports were properly identified. On my machine I also have two USB ports but again they were not picked up by either kernel? I will check out the pointer information and let you know the result.

Thank you for your assistance

Gerry Hooper

At 6/24/99 3:37 PM you wrote - Hello Again Marty
Its now 8.30 pm and I have run the tests that you requested

Under kernel 2.2.5-15

the #ls -l /lib/modules/preferred points to
/lib/modules2.2.5-15

Under Kernel 2.0.36

the #ls -l /lib/modules/preferred points to
/lib/modules/2.0.36-0.7

If I delete the /etc/printcap file under kernel 2.2.5-15
and then start Xwindows and use the printtool I get the messages
/dev/lp0: not detected
/dev/lp1: not detected
/dev/lp2: not detected

the system then indicates that it may be a hardware problem and that I should get it looked at.

Again under 2.2.5-15 I checked out the cat file > /dev/lpX
rountines but they again failed.

My recommendation is that you should refer the whole of this matter to
[EMAIL PROTECTED]
for his consideration. I am always happy to oblige by running any tests that are required because it is in my interest that I should be able to buy and install the latest release of Red Hat Linux. As matters stand I cannot perform this very simple function

Thanks once again for your patience ans assistance

Gerry Hooper


At 6/25/99 2:41 AM you wrote - Hi Marty
Thanks for your continued support (6/24/99 5:31PM)
I have carried out your instructions and attach the results
The original faults remain unchanged
I personally believe that there are some bugs in the 2.2.5-15 complied binary code
These bugs are related to the ability of the 2.2.5-15 kernel to detect hardware
They do not exist in kernel 2.0.36-37

PRINTER UPDATE

I modified the /etc/conf.modules file to contain the added line
alias parport_lowlevel parport_pc
It had no effect. I therefore re-booted the kernel: still no effect.
The print tool still gives the message
/dev/lp0: not detected
/dev/lp1: not detected
/dev/lp2: not detected
On my machine I do not have Samba (Lan Printer) or ncpfs(Netware Printer) installed but this should not affect the setting up of a Local Printer

LSMOD ETC

1. lsmod response is listed now

Module Size Used by

aic7xxx 106928 10



2. insmod /lib/modules/2.2.5-15/fs/vfat.o is listed now through 2>> facility



/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_read_super_R7101628c

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_date_unix2dos_R83fb36a1

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_read_inode_Rf23f0483

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_put_inode_R00b60105

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_dir_operations_R060b8452

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_put_super_R6cc696f2

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_fs_panic_R240a9fc6

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_unlock_creation_R9e32cc5b

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_get_entry_R57ed075c

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_brelse_R2190b516

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_add_cluster_R71aedf1a

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_delete_inode_R6499d474

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_mark_buffer_dirty_R3a53e527

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_notify_change_Re08c2a5f

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_esc2uni_Rdf8b5a1e

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_write_inode_Rc75806f3

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_lock_creation_R4d85e995

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_scan_R84c7a6b4

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_cache_inval_inode_R173fe278

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_statfs_Rf5ee95c8

/lib/modules/2.2.5-15/fs/vfat.o: unresolved symbol fat_readdirx_Rd5f12b92



3. repeated lsmod is listed now: there is no change in the values

Module Size Used by

aic7xxx 106928 10

3. the results for mount -t vfat /dev/hdd1 /dev/floppy2 are listed now

mount: fs type vfat not supported by kernel



Anything else that I can do to sort these problems out please let me know

I remain of the opinion that they should be thrown back to the person responsible for the 2.2.5-15 kernel at Red Hat because there are definite low level binary errors in this kernel

Kind Regards

Gerry



At 6/30/99 11:57 PM you wrote - Hi Marty
Its now five days since I heard from you
Does this mean that Redhat have given up on solving the problems with your 6.0 kernel?
I had an Email this morning from Stephen your sup-manager to tell me that he has sent on to you the files that I sent you on the 16th June!! Has he been away on holiday or somthing and only looks at his mail every three weeks?
Time is running out for maintenance but if there is anything you want me to do please let me know? How about sending the full record of this investigation to the Redhat Development chap listed at [EMAIL PROTECTED] on the /var/dmesg message.
Kind Regards
Gerry Hooper
[EMAIL PROTECTED]
Our Previous Response:
At 6/20/99 9:30 PM we wrote -

Good evening,

Hmm, you should have the msdos module in your /lib/modules/2.2.5-15/fs directory. Do you see it there?

Either way, you should try the 'vfat' module instead:

# mount -t vfat /dev/hdd /dev/floppy2

Let me know if this works for you.

Thanks,
Marty




At 6/24/99 1:47 AM we wrote -

Good morning,

I think I may see the problem. Where does the symlink /lib/modules/preferred point?

# ls -l /lib/modules/preferred

I bet it points to your old module directory 2.0.36. Is this the case? If so, first delete the link /lib/modules/preferred and try again loading the modules you need. I'm sorry I didn't catch this the first time.

As for your printer, try deleting your /etc/printcap and recreating it with printtool. Hopefully this will clear things up.

One more thing, do you still have 5.2 installed? I'm a bit confused about your comparisons because I get the feeling you're doing them on the same machine. Did you do a full upgrade from 5.2 using the boot diskette and all that?

Thanks,
Marty




At 6/24/99 5:31 PM we wrote -

Good afternoon,

Your printer problem is due to the way upgrades from 5.X -> 6.0 "forget" to write the following to your /etc/conf.modules:

alias parport_lowlevel parport_pc

Add the line and try printtool again.

Can you send me the following information, in the order specified?

# lsmod

# insmod /lib/modules/2.2.5-15/fs/vfat.o

# lsmod

# mount -t vfat /dev/hdd1 /dev/floppy2

Thanks,
Marty
Enter Your Results And Additional Comments:
Attachments:
Add File Attachment:
Mark My Incident As SOLVED.

(support - 2.4)

top
bottom
spacer
 






Slashdot News | Freshmeat News | Linux Week News | Red Hat News
Applications| User Groups | Linux Index | Developer Resources | Knowledge Base
Corporate: Products & Services | About Us | News & Events | Partners | Customers | Legal

copyright © 1999 Red Hat Software, Inc. All rights reserved.

Reply via email to