Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 44353 - when use nvidia-kernel do not mount any floppy on XFREE
Summary: when use nvidia-kernel do not mount any floppy on XFREE
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-11 06:04 UTC by Antonio
Modified: 2004-06-01 13:56 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio 2004-03-11 06:04:11 UTC
If on my system with geforce2 MX400 load the module nvidia present on nvidia-kernel i do not mount any floppy on XFREE
On console (ATL-F1) mount work fine.
If i try load xfree with original driver mount work fine.
nvidia driver conflict with mount ?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Donnie Berkholz (RETIRED) gentoo-dev 2004-03-13 17:21:47 UTC
I don't understand what you're saying. Could you rephrase it?
Comment 2 Antonio 2004-03-14 04:48:34 UTC
if in my system with geforce mx400 emerge nvidia-kernel;
apply opengl-update;
i do not mount floppy in any desktop manager
if switch with ALT-F1 on console mount floppy work fine

Sorry for my bad english !!
Comment 3 Andrew Bevitt 2004-04-15 08:17:06 UTC
I use floppy's under X all the time.

Can you post an error log please Antonio...?
Comment 4 Antonio 2004-04-20 04:36:48 UTC
If i mount the floppy on X this is error:

bash-2.05b$ mount /mnt/floppy/
mount: tipo fs errato, opzione non valida, superblocco su /dev/fd0 danneggiato,
       o troppi file system montati
bash-2.05b$

and this is a log:

Apr 20 13:33:27 gentoonet MSDOS FS: IO charset iso8859-15
Apr 20 13:33:27 gentoonet MSDOS FS: Using codepage 850
Apr 20 13:33:27 gentoonet FAT: bogus logical sector size 47548
Apr 20 13:33:27 gentoonet VFS: Can't find a valid FAT filesystem on dev 02:00.
Apr 20 13:33:27 gentoonet FAT: freeing iocharset=iso8859-15

This error is only when use nvidia-kernel driver
If i use standard XFree driver for nvidia i have no problem.
But if i mount the floppy in console (ALT-F1) i do not problem.
??????
Comment 5 Andrew Bevitt 2004-04-20 07:59:08 UTC
andrew@asteroid andrew $ mount /mnt/floppy/
mount: block device /dev/fd0 is write-protected, mounting read-only

andrew@asteroid andrew $ ls /mnt/floppy/
diag.exe  mslanman.dos  netmxic.inf  nt40     oemsetnt.inf  release.txt  win95
freebsd   mslanman.os2  netware      nt50     pktdrv        sco          win98
linux     ndis2         nt351        odi.bat  readme.txt    wfw311

andrew@asteroid andrew $ cat /var/log/Xorg.0.log |grep NVIDIA
(II) Module glx: vendor="NVIDIA Corporation"
(II) Module nvidia: vendor="NVIDIA Corporation"
(II) NVIDIA XFree86 Driver  1.0-5336  Wed Jan 14 18:30:46 PST 2004
<cut>

We really need _every_ single piece of information you can provide us with...
1) Disk FS (and ensure that its the same disk across drivers)
2) The floppy line in /etc/fstab
3) What happens if you specify the filesystem with -t at the mount command?
4) The shell / terminal emulator you are using
5) English Translations are helpful aswell

Heres my /etc/fstab line what happens using this
/dev/fd0        /mnt/floppy     auto            noauto,users            0 0
Comment 6 Antonio 2004-04-21 06:02:51 UTC
This is my log:

cat /var/log/XFree86.0.log | grep NVIDIA
(**) |   |-->Device "NVIDIA GeForce MX-400"
(II) Module glx: vendor="NVIDIA Corporation"
(II) Module nvidia: vendor="NVIDIA Corporation"
(II) NVIDIA XFree86 Driver  1.0-4496  Wed Jul 16 19:06:03 PDT 2003
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(--) Chipset NVIDIA GPU found
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "1"
(--) NVIDIA(0): Linear framebuffer at 0xD8000000
(--) NVIDIA(0): MMIO registers at 0xE0000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce2 MX/MX 400
(--) NVIDIA(0): VideoBIOS: 03.11.01.44.00
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): CRT-0
(--) NVIDIA(0): Display device CRT-0: maximum pixel clock at  8 bpp: 350 MHz
(--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 16 bpp: 350 MHz
(--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 32 bpp: 300 MHz
(II) NVIDIA(0): NEC: Using hsync range of 31.50-48.50 kHz
(II) NVIDIA(0): NEC: Using vrefresh range of 50.00-70.00 Hz
(II) NVIDIA(0): Clock range:  12.00 to 300.00 MHz
(II) NVIDIA(0): Not using default mode "640x350" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x175" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x400" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x200" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "720x400" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "360x200" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x864" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x432" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "832x624" (hsync out of range)
(II) NVIDIA(0): Not using default mode "416x312" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x768" (width too large for virtual size)
(WW) NVIDIA(0): Not using mode "576x384":
(WW) NVIDIA(0):   horizontal sync start (589) not a multiple of 8
(**) NVIDIA(0): Validated modes for display device CRT-0:
(**) NVIDIA(0):      Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(**) NVIDIA(0):      Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(**) NVIDIA(0):      Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(**) NVIDIA(0):      Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(**) NVIDIA(0):      Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(**) NVIDIA(0):      Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(--) NVIDIA(0): Display dimensions: (310, 230) mm
(--) NVIDIA(0): DPI set to (83, 84)
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1024x768"
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) NVIDIA(0): v4l[/dev/video0]: using hw video scaling [YUY2].
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)

My /etc/fstab:

/dev/fd0  /mnt/floppy vfat user,noauto,umask=0,iocharset=iso8859-15,codepage=850 0 0

I have this error in any shell/terminal emulator.

I have test with -t command but not OK.

Sorry for my bad english !

If i use the original driver nv with XFREE i do not have the problem.
Comment 7 Andrew Bevitt 2004-05-10 20:48:22 UTC
Antonio are you using a terminal to mount when you experience this problem, or are  you using kde / gnome / other GUI interface to automatically mount the disk for you?

Not sure this nvidia related but can you test nvidia-kernel-5336-r3 (preferably with 2.6.6 kernel, but not essential) and report back please.
Comment 8 Antonio 2004-06-01 13:56:47 UTC
I have resolved my problem with new motherboard
Tyan dual-processor AMD 1700+

Thank's