I installed openSUSE-12.2 M3 from the 64-bit DVD on this Asus P6T Deluxe V2 motherboard which has a 1.5 TB hard drive, an Intel Core i7-920 CPU, 6GB of RAM and a nvidia GTX260 graphic card. I had previously successfully booted to the 64-bit KDE openSUSE-12.2 M3 liveCD.
The nominal install failed.
It constantly hung at “Search for Linux Partitions” in the openSUSE installer (see image).
http://thumbnails72.imagebam.com/18509/af721e185080251.jpg](ImageBam)
[click on image for larger view]
I noted this on one of the background terminal pages:
http://thumbnails71.imagebam.com/18509/dd5857185080260.jpg](ImageBam)
[click on image for larger view]
which states:
end_request: I/O error, dev fd0, sector 0
Buffer I/O error on device fd0, logical block 0
This PC has no floppy device.
with a more detailed larger view here:
http://thumbnails70.imagebam.com/18509/e0b8e1185080270.jpg](ImageBam)
[click on image for larger view]
I hit a hard reset on the PC to restart. This is repeatable, as I tried it a few times, and even burned another DVD to confirm. I also confirmed md5sums, conducted the mediacheck, burned at a lower speed … etc… Now openSUSE nominally always installs on this PC. I typically never need to install via SafeSettings.
But … I then tried a SafeSettings install which worked. But since safe settings was selected, it booted to the FBDEV driver at a lower resolution than nominal.
During the safe settings install I chose the legacy grub boot loader. Noted this M3 liveCD was mislabeled as M2. I triple checked to ensure I had the correct iso file downloaded, CD burned and booted from. There is a labeling mistake here by SuSE-GmbH (or the associated packager).
After the Safesettings install was complete, I went into YaST and edited the /boot/grub/menu.lst to read M3 instead of M2. I noted a grub2 entry in the menu.lst even thou I chose the legacy grub. That’s a bit misleading IMHO for a user. I did not try to boot from that grub2 selection in the legacy grub menu.lst. I also removed all of the ‘safesettings’ entries out of the menu.lst where those were included in the nominal boot.
I then rebooted and the openSUSE-12.2 M3 booted ok to the nouveau graphic driver.
Sound: I then tested sound, which worked.
Webcam: The webcam worked (Logitech C910 using uvcvideo driver).
Wired access to Internet: I had Internet access via a wired connection to our home LAN.
I plugged in a Canon Ixus 800IS digital camera which works superbly with Digikam in every openSUSE version (since 10.x) that I have used with this camera. Well, there was no KDE hot plug detection popup. By running digikam I was able to detect the camera and download pictures. But the KDE hot plug auto detection of this camera is not working in 12.2 M3. I note that the camera is detected when I check the dmesg (showing a couple of my attempts):
1282.638002] usb 1-3: new high-speed USB device number 7 using ehci_hcd
1282.775509] usb 1-3: New USB device found, idVendor=04a9, idProduct=3119
1282.775513] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
1282.775517] usb 1-3: Product: Canon Digital Camera
1282.775519] usb 1-3: Manufacturer: Canon Inc.
1291.236023] usb 1-3: USB disconnect, device number 7
3011.880283] usb 1-3: new high-speed USB device number 8 using ehci_hcd
3012.017780] usb 1-3: New USB device found, idVendor=04a9, idProduct=3119
3012.017784] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
3012.017787] usb 1-3: Product: Canon Digital Camera
3012.017790] usb 1-3: Manufacturer: Canon Inc.
So I suspect a KDE problem in interfacing to this ?
Printing worked: I setup our Network printer (an HP Photsmart C309a All-In-One-Premium) using YaST. While it was seen by YaST, I still elected to run hp-setup as by doing so I have found it makes it quicker for me to setup the Network scanning. I chose the manual selection in this and configured the Network printer without a problem.
Scanning Worked: I then setup the Network scan function in this same HP Photosmart C309a All-In-One-Premium. I installed xsane and performed a successful test network scan.
USB stick Worked: I plugged in a USB-3.0 stick into a USB-2.0 slot, and it worked ok.
I note from the ‘inxi -F’
oldcpu@corei7-920:~> inxi -F
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
System: Host: corei7-920 Kernel: 3.3.0-2-desktop x86_64 (64 bit)
Desktop KDE 4.8.1 Distro: openSUSE 12.2 Milestone 3 (x86_64) **VERSION = 12.2** CODENAME = Mantis
Machine: Mobo: ASUSTeK model: P6T DELUXE V2 version: Rev 1.xx Bios: American Megatrends version: 1108 date: 09/21/2010
CPU: Quad core Intel Core i7 CPU 920 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx)
Clock Speeds: 1: 2672.822 MHz 2: 2672.822 MHz 3: 2672.822 MHz 4: 2672.822 MHz 5: 2672.822 MHz 6: 2672.822 MHz 7: 2672.822 MHz 8: 2672.822 MHz
Graphics: Card: NVIDIA GT200 [GeForce GTX 260] X.org: 1.10.4 drivers: nouveau (unloaded: fbdev,nv,vesa) Resolution: 189x54
Audio: Card-1: Intel 82801JI (ICH10 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA ver: 1.0.24
Card-2: Logitech HD Webcam C910 driver: USB Audio
Network: Card-1: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2
IF: eth1 state: down speed: N/A duplex: N/A mac: 00:24:8c:7e:ee:38
Card-2: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:24:8c:7e:ee:39
Drives: HDD Total Size: 1500.3GB (2.0% used) 1: /dev/sda ST31500341AS 1500.3GB
Partition: ID: / size: 15G used: 5.5G (40%) fs: rootfs ID: / size: 15G used: 5.5G (40%) fs: ext4
ID: /home size: 35G used: 921M (3%) fs: ext4 ID: swap-1 size: 6.82GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 47.0C mobo: 50.0C gpu: 0.0
Fan Speeds (in rpm): cpu: 2008 psu: 0 sys-1: 0 sys-2: 0 sys-3: 0
Info: Processes: 198 Uptime: 0:57 Memory: 1020.0/5971.9MB Runlevel: 5 Client: Shell inxi: 1.7.24
Note this IS openSUSE-12.2 M3 build 0315 DVD. So I think there is a labeling problem and its not me installing from the wrong DVD (I emphasize that because I HAVE made such a mistake in the past).
I stopped testing here …
… my main observation is that there may be something wrong with either the Partitioning detection application, or the YaST installer. I may need to write a bug report on this.