December 2007 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] 10.3 upgrade
by Stan Goodman 30 Dec '07

30 Dec '07

** Reply to message from Felix Miata <mrmazda(a)ij.net> on Thu, 01 Nov 2007 14:39:48 -0400 In brief, this is about recovery from a failed update of openSuSE from v10.2 to v10.3. I am sorry that I have had to wait so long since the event happened (in late Novermber), and thus break the train of thought of those who were helping me. The urgent matters that distracted me have been resolved, and I am free to continue. > I'm back now from my absence, and have attended to some of the crises that have > popped up while I was away. I'm ready to attack the matter of my failed update > to opensuse v10.3. What I have in mind is to install a maintenance copy of > v10.3 into part of the now unused space on my HD, and to use it to retrieve the > contents of the /home directory from the failed update. See below my plans for > what to do after that. I would be very happy for any comments. Today I installed a maintenance copy of v10.3 in a formerly unused 10GB of the HD. That installation seems to work properly, but I don't understand why the boot sequence is as it is: The maintenance copy has but one partition in addition to SWAP. In setting up the installation, I was very careful to arrange that GRUB be installed in the root partition, rather than the MBR. After setting the configuration and before confirming actual installation, I verified that this was the case. I expected therefore that the boot sequence would be: OS/2 Boot Manager, followed by whatever line of BM is chosen. What actually happens is as follows: 1) openSuSE (maintenance partition) Welcome screen, with its list of choices 2) I choose "Boot from Hard Disk" 3) OS/2 Boot Manager 4) (after appropriate choice) openSuSE (maintenance) flash screen In other words, the installation has created its own boot manager BEFORE the OS/2 Boot Manager. What has happened? How to correct this? When I undo that, and get the boot sequence right, I will go ahead to the original problem. -- Stan Goodman Qiryat Tiv'on Israel In politics, the most important thing is sincerity. Once you can fake that, you have it made. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 7

[opensuse] problem with lirc, opensuse 10.3
by Steve Jacobs 30 Dec '07

30 Dec '07

I'm trying to build a Mythtv system, based on OpenSUSE 10.3. I've got almost everything installed and working, and am now trying, so far unsuccessfully, to get the remote control configured. My remote control is that supplied with a Hauppauge PVR-150. (Grey, not serial, not USB, with the 4 colored buttons arranged in a row at the bottom, not arranged around the 'OK' button near the top.) According to YAST lirc is installed. During my troubleshooting, I returned to YAST, and installed the 4 lirc kernel modules: default, bigsmp, xen, and xenpae. I was pretty sure I didn't need any other than 'default', but selected all of them in case I was wrong. Of course, that resulted in adding all of the additional kernels to my system & boot menu as well, but I can always either tolerate that or remove the others later, I assume. After adding the additional modules, I still have no functional lirc. I HAVE found an 'Oops' in /var/log/messages/, and also saw a message at the lirc sourceforge site mentioning a bug in lirc for the 2.6.22 kernel, and a patch to remedy the bug. ( http://sourceforge.net/mailarchive/message.php?msg_id=14912-18254%40sneakem… ) My system is running kernel 2.6.22.13-0.3. Here is an excerpt from my /var/log/messages/, shwoing the 'Oops': Dec 27 01:47:16 mythbe su: (to root) mythtv on /dev/pts/1 Dec 27 01:47:31 mythbe kernel: lirc_dev: IR Remote Control driver registered, at major 61 Dec 27 01:47:31 mythbe kernel: bttv: driver version 0.9.17 loaded Dec 27 01:47:31 mythbe kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture Dec 27 01:47:31 mythbe kernel: cx2388x v4l2 driver version 0.0.6 loaded Dec 27 01:47:31 mythbe kernel: lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150)) Dec 27 01:47:31 mythbe kernel: BUG: unable to handle kernel paging request at virtual address 00dddf01 Dec 27 01:47:31 mythbe kernel: printing eip: Dec 27 01:47:31 mythbe kernel: e0c850a9 Dec 27 01:47:31 mythbe kernel: *pdpt = 0000000002902001 Dec 27 01:47:31 mythbe kernel: *pde = 0000000000000000 Dec 27 01:47:31 mythbe kernel: Oops: 0000 [#1] Dec 27 01:47:31 mythbe kernel: SMP Dec 27 01:47:31 mythbe kernel: last sysfs file: /block/md1/md/raid_disks Dec 27 01:47:31 mythbe kernel: Modules linked in: cx8800 cx88xx bttv video_buf compat_ioctl32 btcx_risc lirc_i2c lirc_dev ip6t_LOG nf_conntrack_ipv6 xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq microcode ir_kbd_i2c ir_common snd_seq_device ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_mangle iptable_nat nf_nat iptable_filter ip6table_mangle nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables ip6table_filter ip6_tables x_tables ipv6 apparmor xfs loop dm_mod wm8775 cx25840 tuner 8139too ivtv firmware_class i2c_algo_bit cx2341x tveeprom videodev 8139cp v4l2_common mii v4l1_compat snd_intel8x0 snd_ac97_codec button ac97_bus snd_pcm usb_storage snd_timer shpchp snd i2c_i801 iTCO_wdt iTCO_vendor_support soundcore intel_agp snd_page_alloc agpgart pci_hotplug i2c_core parport_pc ide_core sr_mod cdrom parport rtc_cmos rtc_core rtc_lib sg raid456 xor raid0 sd_mod uhci_hcd ehci_hcd usbcore edd raid1 ext3 mbcache jbd fan ata_piix libata scsi_mod thermal processor Dec 27 01:47:31 mythbe kernel: CPU: 0 Dec 27 01:47:31 mythbe kernel: EIP: 0060:[<e0c850a9>] Tainted: G N VLI Dec 27 01:47:31 mythbe kernel: EFLAGS: 00210216 (2.6.22.13-0.3-bigsmp #1) Dec 27 01:47:31 mythbe kernel: EIP is at __i2c_check_addr+0x26/0x35 [i2c_core] Dec 27 01:47:31 mythbe kernel: eax: dddf0029 ebx: dddf01e1 ecx: 00dddf01 edx: 00000071 Dec 27 01:47:31 mythbe kernel: esi: 00000071 edi: dddf0029 ebp: fffffff0 esp: c93a1c08 Dec 27 01:47:31 mythbe kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Dec 27 01:47:31 mythbe kernel: Process modprobe (pid: 4460, ti=c93a0000 task=de023550 task.ti=c93a0000) Dec 27 01:47:31 mythbe kernel: Stack: dbb10400 dbb10460 e0c85c88 00000001 c0122381 dddfebd8 dbb10400 e0987cec Dec 27 01:47:31 mythbe kernel: dbb1047a dddf0059 dbb10400 e0987cec dbb1047a 00000071 e098728b e0987d52 Dec 27 01:47:31 mythbe kernel: 00000071 dbb10464 000051fd dddfebb8 00000071 00000000 c93a1cac dddfebb8 Dec 27 01:47:31 mythbe kernel: Call Trace: Dec 27 01:47:31 mythbe kernel: [<e0c85c88>] i2c_attach_client+0x29/0x175 [i2c_core] Dec 27 01:47:31 mythbe kernel: [<c0122381>] __cond_resched+0x18/0x29 Dec 27 01:47:31 mythbe kernel: [<e098728b>] ir_attach+0x24c/0x260 [lirc_i2c] Dec 27 01:47:31 mythbe kernel: [<e09875a1>] ir_probe+0xa5/0x2ad [lirc_i2c] Dec 27 01:47:31 mythbe kernel: [<c01d374a>] __next_cpu+0x12/0x20 Dec 27 01:47:31 mythbe kernel: [<e0c863a6>] i2c_register_driver+0x9e/0xce [i2c_core] Dec 27 01:47:31 mythbe kernel: [<e09874f8>] init_module+0x42/0x46 [lirc_i2c] Dec 27 01:47:31 mythbe kernel: [<c014491f>] sys_init_module+0x172c/0x1802 Dec 27 01:47:31 mythbe kernel: [<c0176593>] do_sync_read+0x0/0x10a Dec 27 01:47:31 mythbe kernel: [<e0963b78>] videobuf_read_stream+0x179/0x209 [video_buf] Dec 27 01:47:31 mythbe kernel: [<e0963b74>] videobuf_read_stream+0x175/0x209 [video_buf] Dec 27 01:47:31 mythbe kernel: [<c017665a>] do_sync_read+0xc7/0x10a Dec 27 01:47:31 mythbe kernel: [<e0963079>] videobuf_read_one+0x2ca/0x2cb [video_buf] Dec 27 01:47:31 mythbe kernel: [<e0962000>] pci_dma_sync_sg_for_cpu+0x0/0x1 [video_buf] Dec 27 01:47:31 mythbe kernel: [<e097ec82>] lirc_register_plugin+0x0/0x448 [lirc_dev] Dec 27 01:47:31 mythbe kernel: [<c0104ea2>] sysenter_past_esp+0x6b/0xa9 Dec 27 01:47:31 mythbe kernel: [<c02c0000>] xfrm4_rcv_encap+0x1d4/0x3f4 Dec 27 01:47:31 mythbe kernel: ======================= Dec 27 01:47:31 mythbe kernel: Code: d2 c3 31 c0 c3 56 89 d6 53 8b 88 b8 01 00 00 8d 98 b8 01 00 00 eb 14 0f b7 81 5a fe ff ff 39 f0 75 07 b8 f0 ff ff ff eb 0e 89 d1 <8b> 11 0f 18 02 90 39 d9 75 e2 31 c0 5b 5e c3 56 89 d6 53 89 cb Dec 27 01:47:31 mythbe kernel: EIP: [<e0c850a9>] __i2c_check_addr+0x26/0x35 [i2c_core] SS:ESP 0068:c93a1c08 My first question is, is the above the result of the bug mentioned on the sourceforge page? Secondly, I found an online how-to for installing Mythtv to Suse 10.0 that advises removing the lirc packaged with Suse, and compiling/installing lirc from source. I'm using 10.3, & I don't know whether or not the advice holds for me. Deciding to give it a shot though, I launched YAST to try and uninstall the exisiting lirc on my system. YAST warned me that many components, nearly all or all of them Myth-related, were dependent on lirc, and removal of lirc would break those components. Rather than going ahead with the task, I cancelled. (This was before adding the various kernel modules to the system.) My Second question: If I remove every lirc piece through YAST, and then download, compile, and install the latest lirc, will the installed components on my system that are dependent on lirc break? Or will they 'see' the new llirc just fine? I'm nearly ready to give up, reformat, and try again from scratch, but I'm hoping to avoid that. Thanks, Steve -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Gnome messed up
by Allen 30 Dec '07

30 Dec '07

OK, a while back I installed a few apps from add on things in YAST2 and when I tried to load Gnome, all I saw was a LITTLE tiny panel at the top, with just the basic Gnome drop down menu. My wall paper was gone, no icons, no bar at the bottom, just a top panel with the regular Gnome drop down, and I can NOT for the life of me figure out what happened or how to fix it so it looks normal again. I'm to the point I was ready to completely delete Gnome and reinstall it but then it seems to be that if I do the system could break with all my other apps that need something from Gnome. So does anyone have any idea what happened? Is my system now doomed to having to just deal with this? WindowMaker and KDE and everything else work just fine but if I want to use Gnome I can't really, it's like everything is gone that I did with it. Has anyone ever seen this before? I'd really like to fix it back to the way it was before or even the default SUSE look where I at least have task bars and icons. Thanks all, -Allen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 13

[opensuse] TV recording programs
by John Meyer 30 Dec '07

30 Dec '07

I have a TV card and I want to record programs with it. I've tried out mythtv, but it seems a little too much for me. Are there any other alternatives out there? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

8 10

[opensuse] Going Back to 10.2
by Kai Ponte 30 Dec '07

30 Dec '07

Ugh - after mucking about for hours and even re-installing several times, I give up. The machine locks on an irregular basis. The wireless (intel 3945) seems to only work when it wants (it sees the network but refuses to attach) and the wired (broadcom something) seems to drop the connection every five or so minutes. Since kdar isn't even included, I'm going back to 10.2 and giving up on 10.3 - maybe 11.0 will be better. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] can not update
by bill biggs 30 Dec '07

30 Dec '07

I trying to update and every time I try it ask me for my root password then it just close then it says my system is up to date the it says I have update's and dose not update -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

Re: [opensuse] will pay for wireless help
by Chris Worley 30 Dec '07

30 Dec '07

On Dec 22, 2007 2:37 PM, James Gardner <jg189(a)mindspring.com> wrote: > I have a Toshiba p205d-s7454 laptop with a built in atheros wireless card. The chipset is 5006. Atheros has no plans to support Linux, why should we support them? Spend your money on hardware vendors that actively support Linux, it's the best message we can send leeches like Atheros. From: http://apcmag.com/7016/linus_torvalds_talks_future_of_linux_page_2 The good news is that a lot of hw manufacturers are actually doing the right thing. Intel in particular has improved wrt open source a lot, and for that reason I tend to suggest that when buying a machine, just make sure that you buy one with Intel graphics and wireless. That takes care of the two biggest annoyances right there. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Any fcron users
by Jeffrey L. Taylor 29 Dec '07

29 Dec '07

Has anyone used fcron from the OpenSuSE Build Service? My laptop isn't on 24x7 or even reliably on at any given time in the day. There are several jobs that need to be run every day. TIA, Jeffrey Fcron is a scheduler. It aims at replacing Vixie Cron, so it implements most of its functionalities. But contrary to Vixie Cron, fcron does not need your system to be up 7 days a week, 24 hours a day: it also works well with systems which are not running neither all the time nor regularly (contrary to anacrontab). In other words, fcron does both the job of Vixie Cron and anacron, but does even more and better :)) ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 10

[opensuse] Re: Installing OS2008 on N800
by James Knott 29 Dec '07

29 Dec '07

Piotr Zagorowski wrote: > what's the harm of using web search? > simple query leads you to nokia website, nokia website leads you to > os2008 website and on os2008 website there is maemo logo which leads > you to meamo website and there we are. it takes about 7 min.. > And what's the harm of putting a link on the page where the image is located? Or on the Nokia page that points to it? If a user goes to the Nokia or maemo page, why should it be necessary to search for anything? Put the link where someone will find it. Don't expect someone to search when the instructions should be where the update is. What is so hard to understand about that????? -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

Re: [opensuse] will pay for wireless help
by James Gardner 29 Dec '07

29 Dec '07

Mike et al: So you'll know, ubuntu didn't work for this card either. I think it is an issue with support for the atheros 5006 chipset. I understand some older atheros chips work, but this one has ben driving me nuts. Regarding my wish for more than just the usual advice from internet docs, I promise that I have read them all, and tried them all, many times. I didn't come here as a newby, who is too lazy to research, trying to get someone to read the docs for me. I've been battling this problem for three weeks. I really already did RTFM. Many times. I'm not a wireless expert, but I'm not a novice either (I'm writing this from a suse wireless laptop, but it has an intel chipset). So rather than a lot of people sending me the same docs I've seen, and then me just responding with "I've tried that" over and over. I was really hoping to find someone who has been through what I've been through and found a way to make it work. Or maybe someone who knows of a distribution that works. I prefer suse, but I need wireless more than I need suse. I think I'm in a situation now where, after all this time of trying, it is too late to return the PC. So I need to do something. So, that's where I'm coming from. And I really do appreciate the responses so far. Regards, James -----Original Message----- >From: Mike McMullin <mwmcmlln(a)mnsi.net> >Sent: Dec 23, 2007 10:23 AM >To: opensuse(a)opensuse.org >Subject: Re: [opensuse] will pay for wireless help > >On Sun, 2007-12-23 at 01:48 -0600, Rajko M. wrote: >> On Sunday 23 December 2007 01:06:05 am Jerry Houston wrote: >> > Rajko M. wrote: >> > > On Saturday 22 December 2007 05:36:03 pm Steve Reilly wrote: >> > > ... >> > > >> > >> you need to install both the kernel >> > > >> > > Do you mean kernel sources, and compile package? >> > >> > The directions tell you to install (or update) madwifi, then figure out >> > the "flavor" of your kernel, and install the module to match it. Mine's >> > "bigsmp," for example. >> > >> > It didn't work for me, at any rate. When I was done installing (and >> > rebooting), modprobe ath_pci didn't show any results, and I couldn't get >> > the card to connect at all. Since I have the PCMCIA wireless card >> > working fine, it doesn't matter much to me, but I'd be interested in >> > finding how how it goes for James. >> > >> > Perhaps there's some non-obvious step that's needed, beyond what the >> > opensuse.org web site tells us. >> >> I have some experience with Broadcom, but not at all with Atheros. >> The broadcom requires firmware that will be loaded in wireless adapter. >> Two years ago there was no way to get that and wireless didn't worked, now >> there is and laptop works fine. I'm wondering if that is the same problem >> with atheros. > > I have the Atheros chipset (I don't remember which one), on my laptop. >IIRC I required two .rpm's and to use the atheros drive when setting up >the wireless networking in YaST. If his card is like mine, he will not >need to upload any firmware. > >> It would be good if James would accept some type of 'blind shots' and report >> results. That method gives ideas, helps not to run in circles as many eyes >> see more. > > It would be good for those of us who have Atheros' cards to post up >what we did to get our cards working. Ubuntu 6.10 when I installed it, >picked up the card and configured it, SuSE10.3 (which is on it now), did >not have the drivers for it and I had to go get them and go through a >good bit of trial and error. > >-- >To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >For additional commands, e-mail: opensuse+help(a)opensuse.org > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2