I recently installed opensuse 11.0 (w/ KDE4), and am overall dissatisfied with the experience. Is there any way to revert to 10.3? (Note: I do not wish to simply use KDE3. I wish to completely return to 10.3.) Is there any way to achieve this without uninstalling 11.0 and installing 10.3?
amontonarpapeles wrote:
> I recently installed opensuse 11.0 (w/ KDE4), and am overall
> dissatisfied with the experience. Is there any way to revert to 10.3?
> (Note: I do not wish to simply use KDE3. I wish to completely return to
> 10.3.) Is there any way to achieve this without uninstalling 11.0 and
> installing 10.3?
>
>
Nope, you’ll need to reinstall 10.3 if that is the version you would
like to use.
Just out of interest, would you care to enlarge a little on what particularly you don’t like about 11.0?
Would just booting the v10.3 DVD and selecting Install correctly roll back from v11.0?
EdSSmith wrote:
> Would just booting the v10.3 DVD and selecting Install correctly roll
> back from v11.0?
>
>
Not really since it will format your drives.
I meant selecting Install and update system as if updating from 10.2 to 10.3 but instead updating from 11.0 to 10.3
You can try it. The question is whether it looks at package versions the way that the YaST software module does. If so, it will not upgrade.
There is a way to do what you want, but it will probably be very laborious, not to speak of the likely dependency issues you may have to resolve. In YaST, you could disable the 11.0 repositories and add the 10.3 repositories. Then in Software Management, select Package Groups, the last entry will list all the packages in the system. Right-click and select “Upgrade all in this list unconditionally” - I don’t know if this will work, but it would be quick to test. If it doesn’t, what would work would be to go through each installed package and choose the 10.3 version listed below, select it for upgrade.
I’m a bit surprised you wouldn’t just use KDE 3.5.9 - it operates nearly identically to what’s on 10.3. I’ll also throw in that you can upgrade the installed KDE 4.0 to 4.1beta2 from the Factory/11.0 repo’s. 4.1 has a lot more functionality, is more pleasing, more stable. Just fwiw.
Just the fast zypper alone is worth putting up with the occasional glitch to 11.0.
Once you have 11.0 going I can’t see why you would go back to 10.3, and slow package management
I was exited to move to 11 from 10.3 which had trouble with my graphics but otherwise was good. Now with 11, I too am strongly considering going to 10.3 since 11 broke some essential things on my machine.
Particularly, I have not been able to use any USB storage devices and my USB keyboard wast not working either. I switched the keyboard for a PS/2 keyboard but I can’t function without USB mass storage support. Is there a way only to revert the USB subsystem?
The good news is that booting, graphics and package management are faster which I do appreciate but unless I fix USB support, I’ll have to return to 10.3.
- Itai
The actual deal is I upgraded 10.3 Reiser FS. There were no warnings but I gather this is not supposed to work. The upgrade went strangely compared to the instructions and does not handle my display properly which 10.3 did.
I would rather not reformat the hard disk to another file system at this time. However, is my best bet to bite the bullet and do a clean install of 10.3, choosing the new file system?
Ouch! Take a look at your kernel log. One way to do this is, immediately after booting up, open a terminal window and as root do:
#dmesg | more
That will scroll the log. Check if the kernel sees the USB controller(s), loads the USB drivers, and detects any of the devices attached (be sure the drive is turned on). What you find may give you a clue to the problem.
Of course, you also want to make sure that the problem is not something else altogether, like a missing usbfs line ins /etc/fstab or the device not being mounted. The USB detection is handled by the kernel, so to go back to how it was managed in 10.3 requires you to install the older 10.3 kernel, which you can try. But first you want to be absolutely sure that the problem is with the USB detection, not something else.
OK, at least I’ve got some error messages now that I ran “dmesg”. Everything seems good at the start with USB drivers loaded and detecting my devices. Here are the lines than mention USB:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USB Universal Host Controller Interface driver v3.0
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 10, io base 0x0000d800
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ohci_hcd: 2006 August 04 USB 1.1 ‘Open’ Host Controller (OHCI) Driver
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.25.5-1.1-pae uhci_hcd
usb usb1: SerialNumber: 0000:00:07.2
uhci_hcd 0000:00:07.3: VIA VLink IRQ fixup, from 9 to 10
uhci_hcd 0000:00:07.3: UHCI Host Controller
uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:07.3: irq 10, io base 0x0000dc00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.25.5-1.1-pae uhci_hcd
usb usb2: SerialNumber: 0000:00:07.3
ehci_hcd 0000:00:0d.2: EHCI Host Controller
ehci_hcd 0000:00:0d.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:0d.2: irq 10, io mem 0xf7002000
ehci_hcd 0000:00:0d.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 5 ports detected
usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: EHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.25.5-1.1-pae ehci_hcd
usb usb3: SerialNumber: 0000:00:0d.2
ohci_hcd 0000:00:0d.0: OHCI Host Controller
ohci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:0d.0: irq 11, io mem 0xf7000000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: OHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.25.5-1.1-pae ohci_hcd
usb usb4: SerialNumber: 0000:00:0d.0
ehci_hcd 0000:00:0d.2: EHCI Host Controller
ehci_hcd 0000:00:0d.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:0d.2: irq 10, io mem 0xf7002000
ehci_hcd 0000:00:0d.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 5 ports detected
usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: EHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.25.5-1.1-pae ehci_hcd
usb usb3: SerialNumber: 0000:00:0d.2
ohci_hcd 0000:00:0d.0: OHCI Host Controller
ohci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:0d.0: irq 11, io mem 0xf7000000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: OHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.25.5-1.1-pae ohci_hcd
usb usb4: SerialNumber: 0000:00:0d.0
ohci_hcd 0000:00:0d.1: OHCI Host Controller
ohci_hcd 0000:00:0d.1: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:0d.1: irq 10, io mem 0xf7001000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: OHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.25.5-1.1-pae ohci_hcd
usb usb5: SerialNumber: 0000:00:0d.1
usb 3-1: new high speed USB device using ehci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: New USB device found, idVendor=11b0, idProduct=6587
usb 3-1: New USB device strings: Mfr=3, Product=4, SerialNumber=5
usb 3-1: Product: PRO-9XP
usb 3-1: Manufacturer: AFT
usb 3-1: SerialNumber: 1234622
Initializing USB Mass Storage driver…
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
handlers:
<f8dd5f81>] (usb_hcd_irq+0x0/0x57 [usbcore])
<f8dd5f81>] (usb_hcd_irq+0x0/0x57 [usbcore])
<f8dd5f81>] (usb_hcd_irq+0x0/0x57 [usbcore])
<f8dd5f81>] (usb_hcd_irq+0x0/0x57 [usbcore])
Disabling IRQ #10
usb-storage: device scan complete
usb 3-1: reset high speed USB device using ehci_hcd and address 2
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
usb 3-1: USB disconnect, address 2
sd 2:0:0:0: Device offlined - not ready after error recovery
usb 3-1: new high speed USB device using ehci_hcd and address 3
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
usb 3-1: device not accepting address 3, error -110
usb 3-1: new high speed USB device using ehci_hcd and address 4
usb 3-1: device not accepting address 4, error -110
usb 3-1: new high speed USB device using ehci_hcd and address 5
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
usb 3-1: device not accepting address 5, error -110
usb 3-1: new high speed USB device using ehci_hcd and address 6
usb 3-1: device not accepting address 6, error -110
hub 3-0:1.0: unable to enumerate USB device on port 1
usb 4-1: new full speed USB device using ohci_hcd and address 2
usb 4-1: not running at top speed; connect to a high speed hub
usb 4-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb 4-1: New USB device found, idVendor=11b0, idProduct=6587
usb 4-1: New USB device strings: Mfr=3, Product=4, SerialNumber=5
usb 4-1: Product: PRO-9XP
usb 4-1: Manufacturer: AFT
usb 4-1: SerialNumber: 1234622
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
As you can see there are some errors at the end. Unfortunately, I have no idea what they mean and if there is anything to do about them.
- Itai
idanan@
The log indicates that the kernel is seeing the USB controllers and detecting devices attached. Both USB 1.1 and 2.0 are being loaded. Couple of thoughts:
First, the obvious, just in case you haven’t tried this: Make sure you don’t have a USB mis-match, i.e., a 2.0 device on a 1.1 port. Try switching devices between ports. If you are using a USB hub, remove it for now and connect directly. If this is a desktop machine, connect only to ports on the back of the machine which are mounted directly on the motherboard itself.
Second, from a terminal window, what do you get from the >mount command? Switching to root, what happens when you try to manually mount the USB drive?
Third, try using the 10.3 kernel from before you upgraded. However you’re comfortable doing this, whether Konqueror or a terminal, go into /boot and make a new folder (say, /boot/kernel11), and copy (not move) the files (but not folders) in /boot into the new folder. Then add the 10.3 OSS and the 10.3 updates repositories in YaST. Find and install the 10.3 kernel. Now go to /boot/grub and open menu.lst in an editor. You will have boot entries for the just installed 10.3 kernel, but an entry for the 11.0 may or may not be there. If it is, check that it is correct (on the line “kernel . . .” and “initrd . . .” lines) or add it if not there. If the 10.3 installation removed the 11.0 kernel and initrd in /boot, just copy those files back in from your backup in /boot/kernel11. Now you can boot from either kernel. Boot 10.3 and see what happens. If you get your USB back, you have a kernel issue. Post back what happened.
EdSmith@
I’m not sure I follow exactly what your concern/problem is. ReiserFS upgrade or switch to ext3? It’s true ReiserFS is an issue now (I think he’s on trial for murdering his wife; that could take him offline for a while, d’ya think?). Anyway, if you have the disk space, it’s not too difficult to migrate your system to ext3. Is that what you want to do?
All right, now that I got the 10.3 kernel, my USB works. My graphics does not but that was why I wanted to upgrade from
10.3 to 11. Everything works except graphics which has me
stuck at 1024x768 16bit using VESA (yuck!).
I guess that means my USB has a kernel issue but what can be
done about it? Let me know if there is any command/log that
can be useful to determine what’s wrong with 11.
- Itai
I’ve been testing some different 11.0 combinations, with several KDE 3.5.9, 4.0, and 4.1beta. I checked /etc/fstab in 10.3 and 11.0, and they are the same. I suggest you try this:
Boot with your 11.0 kernel. In a terminal window as root, do #lsusb; you should see an entry for each of your usb hubs, and an entry for your storage device. Then do a #cat /proc/partitions and you should see your usb disk’s partitions listed starting with the next letter after your internal drives (e.g., if you have two ATA drives, sda and sdb, then you should see sdc1, sdc2, etc. depending on the number of partitions on the usb drive). Do you possibly see the partitions duplicated (in this example, an sdd1, sdd2, etc.)? And what do you see with #mount? You may a mount for sdc1 and sdd1, for the same partition. Also, try doing this after umounting the storage (if mounted), disconnecting, wait 10 seconds, reinsert.
Then try doing these tests with booting into 10.3. What I suspect is that there is a problem between the 11.0 kernel and 11.0’s version of HAL (the hardware abstraction layer). In one of my tests I picked up log errors referencing the HAL Policy Manager.
I can’t say that this duplicated mounting is exactly related to your problem. I am able to use my usb drive and the 11.0 kernel, even with this issue. But it does point to something amiss with 11.0 kernel and/or the 11.0 HAL. But there may be something different in your configuration where, whatever the source of this issue is, creates a different problem for you.
I did try googling your problem, and did find some usb related problems, but nothing the sounded like what you’re experiencing, nor what I found in my tests. But it is very early, it can take some time for these issues to bubble up. If your storage works with the 10.3 kernel, and you don’t see any of the above misbehavior, then, whatever the exact source of the problem, you will have isolated yourself from it and can go to work on the graphics driver issue awaiting a subsequent patch to the kernel and/or HAL.