6-in-1 usb card reader can read Memstick but not CF in fc2test3
by Yusuf Goolamabbas
Hi, I have a 6-in-1 USB card reader and a 4MB CF card and a 128MB Memory
Stick. When I plug this in my fc2test3 box, I see all the slots in my
card reader being picked up by the kernel (yeah, I don't have to monkey
with the MULTI_LUN) stuff but it only seems to detect the Memory Stick
prescence and not the CF card. When I click on the "Computer" icon on
the desktop, I am only shown a memorystick icon and I can mount that volume
by right-clicking on that icon
The same card reader when taken to a
Windows 2000/XP box has no problem reading both the CF/Memory stick
uname -a
Linux fc2test3 2.6.5-1.327 #1 Sun Apr 18 04:51:55 EDT 2004 i686 i686
i386 GNU/Linux
Output from dmesg
usb 1-2: new full speed USB device using address 2
usb 1-2: device not accepting address 2, error -71
usb 1-2: new full speed USB device using address 3
usb 1-2: device not accepting address 3, error -71
PCI: Enabling device 0000:00:0f.0 (0104 -> 0105)
PCI: Found IRQ 10 for device 0000:00:0f.0
usb 1-2: new full speed USB device using address 4
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: USB Storage-SMC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Vendor: Generic Model: USB Storage-CFC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Vendor: Generic Model: USB Storage-MMC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Vendor: Generic Model: USB Storage-MSC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 7873 512-byte hdwr sectors (4 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
sdb:scsi0: ERROR on channel 0, id 0, lun 1, CDB: Read (10) 00 00 00 1e
c0 00 00 01 00
Current sdb: sense key Medium Error
Additional sense: Unrecovered read error
end_request: I/O error, dev sdb, sector 7872
Buffer I/O error on device sdb, logical block 7872
scsi0: ERROR on channel 0, id 0, lun 1, CDB: Read (10) 00 00 00 1e c0 00
00 01 00
Current sdb: sense key Medium Error
Additional sense: Unrecovered read error
end_request: I/O error, dev sdb, sector 7872
Buffer I/O error on device sdb, logical block 7872
sdb1
Attached scsi removable disk sdb at scsi0, channel 0, id 0, lun 1
Attached scsi removable disk sdc at scsi0, channel 0, id 0, lun 2
Attached scsi removable disk sdd at scsi0, channel 0, id 0, lun 3
USB Mass Storage device found at 4
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
[root@fc2test3 root]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: Generic Model: USB Storage-SMC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: Generic Model: USB Storage-CFC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 00 Lun: 02
Vendor: Generic Model: USB Storage-MMC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 00 Lun: 03
Vendor: Generic Model: USB Storage-MSC Rev: 0180
Type: Direct-Access ANSI SCSI revision: 02
20 years
display weirdness in X on older hardware.
by d_bradsh＠bellsouth.net
Hey folks,
I have test 3 up and running on an older machine with ati mach 64. Xorg seems to be running great but a I can't seem to adjust my monitor resolution. Both 640X480 and 800X600 give the same results. Also, has anyone had the bottom task bar act strangly when you click on an icon? Mine jumps sideways back and forth really fast, but icon functionality is not compromised. Its annoying, but at least the icons work., Anyway, thanks and peace to you all. :)
Dusty
20 years
Python tkinter packages not being installed
by Sarah Fish
I have had a problem getting a game to run since I put up FC-T2 about a
month ago. It needs Tkinter and it couldn't find it. Had the same
problem with FC1, but installing the Python-tools option via the
add-packages screen took care of it. I tried that with FC-T2 with no
success early on, but didn't have time to dig into it further.
Last night I downloaded T3 and spent today setting up my system to dual
boot Win98 & FC-T3. After all that Windows nonsense, I needed my game -
bad! So after I loaded T3, I started digging into just where Tkinter was
hiding. The T3 setup ran smoothly except that the partitioning section
wasn't happy about the dual boot status. It did it, but it didn't like it.
The tcl8.4 part was installed at setup. I finally located Tkinter on
the 4th T3 disc and tried installing it. It needed two other packages,
also on disk 4, tix-8.1.4-96.1.i386.rpm and tk-8.4.5-8.i386.rpm.
Just in case anybody else needs a Pysol fix :).....
Sarah Fish
Saratoga Springs, NY
20 years
dell latitude d600 feedback - FC2 Test3
by Mike Lee
I am having the same problem on my Dell Inspiron 8000. Exact
problem.
When I go to log out, the screen keeps getting brighter and
brigher. Total system lockage.
Anyone have any tips?
Thanks.
Mike
--
Director Services - The NewMedia Group
Montana Tech Blackboard Administrator
20 years
FC2 T2 -> T3 upgrade hoses your modprobe.conf - Alan
by RaXeT
Found the reason for my network suddenly getting hosed after using the
iso upgrade install from FC2 T2 to FC2 T3:
The upgrade process deletes original entries and recreates the following
single entry in modprobe.conf:
options tg3 irq=9
So I found a copy of my original FC2 T2 and replaced it and now I'm a
happy guy!
Here is what my modprobe.conf has been all along:
include /etc/modprobe.conf.dist
alias eth0 tg3
alias usb-controller ehci-hcd
alias usb-controller1 uhci_hcd
alias scsi_hostadapter sata_promise
alias scsi_hostadapter1 sbp2
alias scsi_hostadapter2 sata_promise
alias sound-slot-0 snd-emu10k1
alias sound-slot-1 snd-intel8x0
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
alias snd-card-1 snd-intel8x0
# OSS/Free portion
alias char-major-14* soundcore
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
install fglrx /sbin/modprobe --ignore-install fglrx
install snd-card-0 /sbin/modprobe --ignore-install snd-card-0 && {
/usr/sbin/alsactl restore >/dev/null 2>&1 || :; }
remove snd-card-0 { /usr/sbin/alsactl store >/dev/null 2>&1 || :; };
/sbin/modprobe -r --ignore-remove
install sound-slot-0 /sbin/modprobe --ignore-install sound-slot-0 && {
/bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >>/dev/null
2>&1 || :; }; /sbin/modprobe -r --ignore-remove
install snd-card-1 /sbin/modprobe --ignore-install snd-card-1 && {
/usr/sbin/alsactl restore >/dev/null 2>&1 || :; }
remove snd-card-1 { /usr/sbin/alsactl store >/dev/null 2>&1 || :; };
/sbin/modprobe -r --ignore-remove
install sound-slot-1 /sbin/modprobe --ignore-install sound-slot-1 && {
/bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-1 { /bin/aumix-minimal -f /etc/.aumixrc -S >>/dev/null
2>&1 || :; }; /sbin/modprobe -r --ignore-remove
#FIX for borked Alsa
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 &&
/usr/sbin/alsactl restore
remove snd-emu10k1 /usr/sbin/alsactl store && /sbin/modprobe -r
--ignore-remove snd-emu10k1
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
/usr/sbin/alsactl restore
remove snd-intel8x0 /usr/sbin/alsactl store && /sbin/modprobe -r
--ignore-remove snd-intel8x0
20 years
unknown video and graphic boot
by Jason Dravet
I have a system that has a Matrox P650 video card in it. FC does not
recognize this card and there is no reason is should. The drivers are closed
source and poorly maintained by matrox. I can install FC2T3 on the system
using text mode (linux text nofb) and everything works. There are a few
screen problems, but nothing cannot live with.
I would like to float the idea that if the video card is not recognized by
FC2 then the default init run level should be 3. Currently the default is 5
which makes the system unusable until I boot into single user mode and
change the inittab to boot to run level 3. What do you think of this idea?
_________________________________________________________________
Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage!
http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362a...
20 years
Install Boot Tip for people without CDs and USB keys
by Phil Anderson
This only applies to you if:
- You have an existing linux installation
- You don't have (or don't want to use) a CD Drive
- You don't have (or don't want to use) a USB key
- You don't want to keep anything on your primary hard disk
This is the easiest (only????) way to install fedora 2 tests:
- Copy diskboot.img onto your existing hard disk
- Boot into single user mode
- run sync
- run dd if=diskboot.img of=/dev/hda
- Reset your computer (i.e. press the button on the case)
- Start installation!
If installation freezes looking for existing partitions (#121934):
ALT-F2
killall -9 lvm
ALT-F1
Phil
20 years
Fresh install of T3 (observations)
by Fulko.Hew＠sita.aero
I decided I'd do the fresh install of T3, I've had so
many symptoms during this experience, that I'm going to
put them all into one email, rather than to break them
out in the hope that someone can make sense of them.
Also I apologize in advance for not writting down all
the error messages along the way.
My environment: A Centrino based 'white box' laptop.
1/ Tried installing Core 2 test 3 from CDs... during install
I selected 'custom' install, and you get the python
core dump (discussed during yesterdays email exchange).
2/ Changed install choices to 'Workstation', and then later
said 'install everything'. That seemed to work.
3/ I use KDE so I tried using the desktop switcher tool
from the menu. It never came up. I then run 'switchdesk'
from the command line, and find a traceback:
File "/usr/share/switchdesk/switchdesk-gui.py", line 36, in ?
from backend import *
File "/usr/share/switchdesk/backend.py", line 18
PROGNAME = @NAME@
^
SyntaxError: invalid syntax
So I found 'switchdesk-helper' and ran it as
'switchdesk-helper KDE' and that worked.
4/ The task bar RHN applet indicated that new RPMs existed.
Clicking on it, running up2date I fetched the new version
of up2date and installed it.
5/ Running up2date again, I installed the remainder of the RPMs
NOTE: Each RPM had a GPG error!
6/ I tried running TuxRacer. it wouldn't start, and complained
about "SDL..." (sorry, I didn't write it down).
6/ I like to use xine, so I fetched apt-get from freshrpms
and installed it. Then I ran apt-get install xine.
It complained about two different versions of a 'policy'
file on the system and suggested a command to execute.
Doing that it complained about something else, and suggested
something else. After 3 rounds of that, I was able to install
xine, and it worked.
7/ I tried TuxRacer again. This time it worked fine. I'm puzzled.
8/ I'd sware that after I ran Kmix (under test2) that it left a
volume control applet on the task bar. Now I can't figure out
how to get the volume control applet _onto_ the task bar!
9/ This morning, the update icon indicated that 22 updates exist.
The alert box lists them all. But after running up2date,
it says my system 'was already up to date', ... but there are
still 22 new RPMs.
10/ Running 'yum update' basically worked, but it complained about
perl-XML-Twig, so doing 'yum --exclude perl-XML-Twig update'
gets past that error, and installed the rest.
11/ The update icon still says there are two RPMs outstanding:
perl-XML-Twig, and perl-Net-DNS, but up2date still insists
that my system is up to date.
12/ What happened to kernel 322? I was running that on test 2,
but test 3 didn't ask for it to be downloaded.
13/ My system still doesn't detect hot-plugged USB devices.
(Cold plugging is still OK).
Overall, the experience is poor, and discouraging (for a final
beta test).
20 years
Install great but confused by errors
by BC
Install went great AWESOME distro !!!! Well done guys.
But after I used up2date I rebooted and was filled with a console full of security error messages like tried to
write file "denied" I am sure this is the SELinux stuff and I just don't get it yet. Is there a link for an
SELinux newbie to read ?
I couldn't get to a console because the messages were filling the console so I re-installed. I don't have a
screenshot of the errors but they all seemed to be something with selinux and the secure filesystem. Now I am
on a fresh install doing an up2date gain -- Maybe try 2 will be better. I do see this in the messages file
tough any ideas ? Is this something I should be putting in a diffetrent group If so I am sorry and please stear
me in the right direction.
tail -f messages
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_irc_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_mozilla_rw_t
Apr 28 20:37:43 Penguin1 last message repeated 2 times
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_screen_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_screensaver_rw_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_ssh_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_xauth_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
system_u:object_r:default_context_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
system_u:object_r:amanda_recover_dir_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
system_u:object_r:staff_home_spamassassin_t
20 years
