scoonma

$ fdisk -l /dev/sdc results to plainly nothing, i.e. except a new command prompt.

Hi atchoum, welcome to Mandrivausers! Can you boot a standard kernel in failsafe mode?

Krita's homepage leads me to the suggestion that you should install the KOffice package first, then with the library you found it's possibly enough. See also http://www.koffice.org/krita/

Unfortunately I cannot perform that check, the device appears as unformatted under Windows. When trying to do that, an error appears: "Device cannot be formatted". Thus I cannot apply h2testw, too. So...?!?

$mount -t vfat /dev/sdc1 /mnt/tst mount: Gerätedatei /dev/sdc1 existiert nicht This means file for device /dev/sdc1 does not exist (also tried sdc2,...) My DVD-RAM device used to be sdc1 (with harddisks sda and sdb), but there's no problem with different memory sticks, so I'm rather lost.

Is this device broken (it's rather new!) ? I cannot mount the device manually as /dev/sdc1 or /dev/sg4 neither. Any hints please? $lsusb Bus 001 Device 010: ID 090c:3000 Feiya Technology Corp. # dmesg | grep -i usb | tail -n 20 usb 1-3: New USB device found, idVendor=090c, idProduct=3000 usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-3: Product: SM324BC MEMORY BAR usb 1-3: Manufacturer: Silicon Motion,Inc. usb-storage: device found at 10 usb-storage: waiting for device to settle before scanning scsi 7:0:0:0: Direct-Access USB MEMORY BAR 1000 PQ: 0 ANSI: 0 CCS usb-storage: device scan complete usb 1-3: USB disconnect, address 10 usb 1-3: new high speed USB device using ehci_hcd and address 11 usb 1-3: configuration #1 chosen from 1 choice scsi8 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 11 usb-storage: waiting for device to settle before scanning usb 1-3: New USB device found, idVendor=090c, idProduct=3000 usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-3: Product: SM324BC MEMORY BAR usb 1-3: Manufacturer: Silicon Motion,Inc. scsi 8:0:0:0: Direct-Access USB MEMORY BAR 1000 PQ: 0 ANSI: 0 CCS usb-storage: device scan complete # dmesg | grep -i scsi | tail -n 10 sd 6:0:0:0: [sdc] Attached SCSI removable disk sd 6:0:0:0: Attached scsi generic sg4 type 0 scsi7 : SCSI emulation for USB Mass Storage devices scsi 7:0:0:0: Direct-Access USB MEMORY BAR 1000 PQ: 0 ANSI: 0 CCS sd 7:0:0:0: [sdc] Attached SCSI removable disk sd 7:0:0:0: Attached scsi generic sg4 type 0 scsi8 : SCSI emulation for USB Mass Storage devices scsi 8:0:0:0: Direct-Access USB MEMORY BAR 1000 PQ: 0 ANSI: 0 CCS sd 8:0:0:0: [sdc] Attached SCSI removable disk sd 8:0:0:0: Attached scsi generic sg4 type 0 # hal-device | more 0: udi = '/org/freedesktop/Hal/devices/storage_serial_Silicon_Motion_Inc__USB_MEMORY_BAR_0_0' info.product = 'USB MEMORY BAR' (string) info.udi = '/org/freedesktop/Hal/devices/storage_serial_Silicon_Motion_Inc__USB_MEMORY_BAR_0_0' (string) info.vendor = '' (string) linux.hotplug_type = 3 (0x3) (int) storage.removable.media_size = 4009754624 (0xef000000) (uint64) block.device = '/dev/sdc' (string) storage.partitioning_scheme = 'none' (string) block.major = 8 (0x8) (int) block.minor = 32 (0x20) (int) block.is_volume = false (bool) storage.bus = 'usb' (string) storage.no_partitions_hint = false (bool) storage.media_check_enabled = true (bool) storage.automount_enabled_hint = true (bool) info.interfaces = { 'org.freedesktop.Hal.Device.Storage.Removable' } (string list) storage.drive_type = 'disk' (string) storage.model = 'USB MEMORY BAR' (string) storage.vendor = '' (string) storage.serial = 'Silicon_Motion,Inc._USB_MEMORY_BAR-0:0' (string) storage.firmware_version = '1000' (string) info.category = 'storage' (string) storage.lun = 0 (0x0) (int) info.capabilities = { 'storage', 'block' } (string list) storage.originating_device = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0' (string) storage.removable.media_available = true (bool) storage.removable = true (bool) storage.size = 0 (0x0) (uint64) storage.hotpluggable = true (bool) storage.requires_eject = false (bool) storage.removable.support_async_notification = false (bool) linux.sysfs_path = '/sys/block/sdc' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host_scsi_device_lun0' (string) info.addons = { 'hald-addon-storage' } (string list) block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_Silicon_Motion_Inc__USB_MEMORY_BAR_0_0' (string) 1: udi = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host_scsi_device_lun0_scsi_generic' linux.subsystem = 'scsi_generic' (string) info.subsystem = 'scsi_generic' (string) linux.device_file = '/dev/sg4' (string) info.product = 'SCSI Generic Interface' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host_scsi_device_lun0_scsi_generic' (string) info.category = 'scsi_generic' (string) linux.sysfs_path = '/sys/class/scsi_generic/sg4' (string) info.capabilities = { 'scsi_generic' } (string list) info.parent = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host_scsi_device_lun0' (string) scsi_generic.device = '/dev/sg4' (string) linux.hotplug_type = 2 (0x2) (int) 2: udi = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host_scsi_device_lun0' scsi.model = 'USB MEMORY BAR' (string) linux.subsystem = 'scsi' (string) info.subsystem = 'scsi' (string) info.product = 'SCSI Device' (string) scsi.vendor = '' (string) scsi.type = 'disk' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host_scsi_device_lun0' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.2/usb1/1-3/1-3:1.0/host7/target7:0:0/7:0:0:0' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial_if0_scsi_host' (string) scsi.host = 7 (0x7) (int) scsi.bus = 0 (0x0) (int) scsi.target = 0 (0x0) (int) info.linux.driver = 'sd' (string) scsi.lun = 0 (0x0) (int) linux.hotplug_type = 2 (0x2) (int) [...] 6: udi = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial' info.subsystem = 'usb_device' (string) usb_device.product = 'SM324BC MEMORY BAR' (string) linux.subsystem = 'usb' (string) linux.device_file = '/dev/bus/usb/001/010' (string) usb_device.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.2/usb1/1-3' (string) info.product = 'SM324BC MEMORY BAR' (string) usb_device.device_revision_bcd = 256 (0x100) (int) usb_device.configuration_value = 1 (0x1) (int) usb_device.max_power = 100 (0x64) (int) info.udi = '/org/freedesktop/Hal/devices/usb_device_90c_3000_noserial' (string) usb_device.num_configurations = 1 (0x1) (int) usb_device.num_ports = 0 (0x0) (int) usb_device.num_interfaces = 1 (0x1) (int) usb_device.linux.device_number = 10 (0xa) (int) usb_device.device_class = 0 (0x0) (int) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.2/usb1/1-3' (string) usb_device.device_subclass = 0 (0x0) (int) usb_device.speed = 480 (double) info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_2_0000_00_02_2' (string) usb_device.device_protocol = 0 (0x0) (int) info.vendor = 'Feiya Technology Corp.' (string) usb_device.version = 2 (double) usb_device.vendor_id = 2316 (0x90c) (int) usb_device.is_self_powered = false (bool) info.linux.driver = 'usb' (string) usb_device.product_id = 12288 (0x3000) (int) usb_device.can_wake_up = false (bool) usb_device.vendor = 'Feiya Technology Corp.' (string) usb_device.bus_number = 1 (0x1) (int) linux.hotplug_type = 2 (0x2) (int)

Err, nearly. Ctrl-Alt-Backspace will always shut down the graphical server - a new instant will be started if service dm was started before (like in default setup).

Hi there, I've already reported this as a bug (cf. https://qa.mandriva.com/show_bug.cgi?id=46930 ); however, I'm hoping someone can give additional info/hints. The error message is as stated in this topic description, also visible after leaving X (enterd by "startx" command). I'm using 2009.0 with GNOME. I've tried KDE 3.5 too, with the same problem occurring as well as another physical keyboard, with no difference either. Please help!

You'd probably have to make sure the partition is readable from the initial ramdisk. So I'd guess you'll have to recompile and install your kernel with ext4 both as module and built-in.

Either that solves the problem or it has to be searched somewhere else. I've experienced that kind of problem before. To me it seems rather access rights related - on system level you have to mount the device, but you want to use (i.e. write to) the device as user. Nowadays we have hal, so I cannot go further. Maybe scarecrow or someone else with further experience can give another hint?!? A workaround would be to login as root, then copy all the files you want. For security reasons I'd disable all network connections beforehand. Kind regards, schollsky

I'd stay away from NVIDIA driver 180.22 for now, unless you want to do real hacking. Trying the new driver with recent stable kernel on 2009 came out with same result. I'm also looking forward for the driver due to the bug fixes, but it simply doesn't integrate as well as 177.82 yet.

Hi there, filing a bug report is nearly impossible this way, so ... :-) The updated package above cripples my system in a way, that german "umlaut" characters or other special chars like "at" have vanished - okay, not from the keyboard itself, but from the screen when trying to type them. The result is that no character is displayed when pressing these keys. This is the 64bit version, and legacy terminals still work fine, but not in X - and switching VTs is not possible now (due to no ALT key working). This is from Xorg.0.log: (EE) XKB: Couldn't compile keymap Please help!

Exactly the same result here for my GF's recent account, with MDV 2009.1 & FF 3.

Yeah, I perceived it more as a Teach-In than a real party, too. However the notion Teach-In may seem oldschool today. :-)

Hi all, last weekend I installed (mostly unintentionally) the 64bit version of 2009 on a laptop at a friend of mine. Unfortunately that many aspects did work badly or not at all to leave me installing the 32bit version, and the latter works as fine as on this hardware. I've found the following issues with 64bit - Installation was performed with dual arch single CD: - Invalidating the stale suspend image very early in startup stage takes very long (more than two minutes) with an exterior HD connected at USB (2.0). The HD has 250GB capacity. Another two minutes goes to harddrake in this case. - Compared to using the 32bit version, it's not possible to install GNOME from the disk; you'll end up with IceWM (okay, maybe intended to space limitations). - It's not possible to switch to the german version of Firefox with 64bit - even after installing firefox-de package, default English is used. - Dvdrip has an apache dependancy with 64bit (but not with 32bit)?!? :blink: The list is probably incomplete, but at that point I decided to reinstall with 32bit. Before that I had discarded the install CD as source repository and switched over to 2009 Free / 64bit repositories using Easy-Urpmi, which seems correct to me. Anyone else tried 64bit in a similar environment (about 12 months old laptop in this case)? If needed I'll add some hardware specs later. Any comments welcome, scoonma

Hm. It's really worth it to upgrade at least to version 2008.1. I'm using 2009.0 (32-bit version) with Flash 10 and Youtube without any problems by now ...

You do mean /usr/bin/gtk-window-decorator, correct? (as found in package compiz-decorator-gtk)

Will there be a Mandriva Linux Install Fest after the release of 2009.1, too? Actually I was planning to participate with well - the more users from my circle of friends the better - but on November, 22nd I have a private date which cannot be canceled - I hate these collisions... Regards, scoonma

Do you have the corresponding "task-*" packages installed? Generally, I found out it's useful to install the bash-completion package; after a re-login you can use the TAB key together with urpmi. Alternatively you could issue the urpmi command with a smaller part of the desired package, in which case you're presented a collection of possible hits for installing.

I had a very similar problem, but in Gnome. The display improved a lot after installing msttfonts package as described here: http://www.howtoforge.com/the-perfect-desk...2009.0-gnome-p5

Here's what I've experienced so far: Updating from 2008.1 to 2009.0 using the new sources works well but: only with the old kernel (2.6.24 series)! When trying the new 2.6.27.x kernel, the machine hangs early in the boot process, shortly after entering interactive stage. The root fs is mounted in r/w mode fine, but afterwards there's some errors: "Failed to open /dev/hdc2" "Failed to open /dev/hdc6" "Failed to open /dev/hdc5" This is where /home, /tmp and /usr reside here, and I'm left to enter root pw for maintenance. A short glance at /etc/fstab shows the first two lines contain no valid entries now, but error messages from /etc/termcap. So ...?

You're right of course. So I can provide some details now: - Disabling 3D from within the drak3d module (i.e. selecting "No 3d effects") after choosing login and typing in the password is not sufficient: The problem remains the same. - Enabling GNOME as standard session from the login chooser screen works ... somehow: 1) If I select my gf's handle and log in, a normal GNOME session is started, as expected. So at least she can do her work now! 2) If I select my own handle and log in, a 3D session is started, with rotating desktop cube possible - which is fine, too. However, this is not what I have expected. So the problem is not fully solved now, but I rather have a working configuration. Unfortunately I do not know why it is working - which is somehow disappointing from an advanced linux users point of view. :unsure:

Sorry, I forgot: I have compiz installed: compiz-0.7.6-1mdv2008.1

Disabling 3D would be an option, of course. Thus I could circumvent the problem. I'd rather like to solve it though. :-)

No, but that is not the problem. I could put it to be started on boot by default, but found it very inconvenient in case of trouble (like this one). The error occurs after gdm is started any way (the login/chooser screen looks alright), right after typing in the password. No desktop is being displayed, instead a request to type in user password. After that drak3d pops up. So I never get to the desktop using gdm. For that I had disabled *any* dm ("service dm stopped" as chkconfig default).