Subject: Re: no medium xterm font (fwd) - msg#02423

Previous Message by Date: click to view message preview

Re: cannot play DVD's on Fedora 10 386

On Sunday 30 August 2009 13:58:06 Kevin Kempter wrote: > On Sunday 30 August 2009 13:41:47 Mikkel L. Ellertson wrote: > > Kevin Kempter wrote: > > > I did some more digging. /dev/dvd and /dev/cdrom are both symlinks to > > > /dev/sr0 > > > > > > the symlinks (/dev/dvd and /dev/cdrom) are both owned by user:group > > > root:root and have 777 permissions > > > > > > any other thoughts? > > > > > > Thanks in advance.... > > > > Every symlink I have seen has 777 permissions. What counts are the > > permissions of the file it links to. > > > > [mikkel lib]$ ls -l /dev/dvd > > lrwxrwxrwx 1 root root 3 2009-08-20 11:35 /dev/dvd -> sr0 > > [mikkel lib]$ ls -l /dev/sr0 > > brw-rw----+ 1 mikkel root 11, 0 2009-08-20 11:35 /dev/sr0 > > > > Mikkel > > How do I change perms on the device? > > If I do a chmod a+rw /dev/sr0 it changes the perms for about 30 seconds > then they get changed back to rw for root only. ok, I've done this: 1) I added a MODE="0660" to each line in /etc/udev/rules.d/70-persistent-cd.rules 2) rebooted, checked perms of /dev/sr0 and I now have rw for all 3) tried to play a dvd via kaffiene - same error: The source can't be read Maybe you don't have enought rights for this, or source doesn't contain data (e.g: no disc in drive). (Error reading from DVD) 4) I tried multiple DVD's - same error, also tried the same DVD's in another laptop running Fedora 10 x86_64 - works fine 5) checked dmesg output and I see this: Buffer I/O error on device sr0, logical block 223 Buffer I/O error on device sr0, logical block 224 Buffer I/O error on device sr0, logical block 225 Buffer I/O error on device sr0, logical block 226 Buffer I/O error on device sr0, logical block 227 Buffer I/O error on device sr0, logical block 228 Buffer I/O error on device sr0, logical block 229 Buffer I/O error on device sr0, logical block 230 Buffer I/O error on device sr0, logical block 231 Buffer I/O error on device sr0, logical block 232 end_request: I/O error, dev sr0, sector 2040 end_request: I/O error, dev sr0, sector 1824 end_request: I/O error, dev sr0, sector 1872 end_request: I/O error, dev sr0, sector 1880 end_request: I/O error, dev sr0, sector 1872 end_request: I/O error, dev sr0, sector 2400 end_request: I/O error, dev sr0, sector 2408 end_request: I/O error, dev sr0, sector 2400 end_request: I/O error, dev sr0, sector 2400 end_request: I/O error, dev sr0, sector 2400 end_request: I/O error, dev sr0, sector 2704 end_request: I/O error, dev sr0, sector 2712 end_request: I/O error, dev sr0, sector 2704 end_request: I/O error, dev sr0, sector 2704 end_request: I/O error, dev sr0, sector 2704 end_request: I/O error, dev sr0, sector 3624 end_request: I/O error, dev sr0, sector 3632 end_request: I/O error, dev sr0, sector 3624 end_request: I/O error, dev sr0, sector 3624 end_request: I/O error, dev sr0, sector 3624 Thoughts? -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Next Message by Date: click to view message preview

Re: Latest kernel makes wireless connection to WPA2 router fail

On Sun, Aug 30, 2009 at 9:22 PM, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: Henrik Frisk writes: Hi, I'm running FC11 on a MacBook Pro. After the latest kernel updates (to 2.6.29.6-217.2.16.fc11.x86_64) I cannot connect to my wireless router anymore. If I boot up in the previous kernel it works fine. Any ideas on how I can fix this? The wireless interface on this laptop is a Broadcom Corporation BCM4322. No problems on this laptop with BCM4311 and the latest kernel. Generally, a blanket statement that something doesn't work offers very little usable information to work with. At the very least, you should gather some preliminary information yourself, such as: Right, sorry about that.  1) the output of lsmod, to determine whether the b43 kernel module is loaded.' It wasn't but it didn't change anything to add it. Here's the output of 'lsmod | grep b43' b43                   127352  0 ssb                    39572  1 b43mac80211              199632  1 b43cfg80211               37088  2 b43,mac80211input_polldev           3952  2 b43,applesmc 2) various bits of information from /var/log/messages. kernel messages from early in the boot process would report whether or not the kernel module was loaded, and if not why not. Or may be you have some error messages from NetworkManager, or wpa_supplicant, that point towards a clue. Here's the output of 'cat messages | grep Network':Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'dinergy'. Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Aug 30 22:34:34 localhost NetworkManager: <info>  (eth1): device state change: 5 -> 7 (reason 0)Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) Beginning DHCP transaction.Aug 30 22:34:34 localhost NetworkManager: <info>  dhclient started with pid 9060 Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.Aug 30 22:34:34 localhost NetworkManager: <info>  DHCP: device eth1 state changed normal exit -> preinit Aug 30 22:35:20 localhost NetworkManager: <info>  Device 'eth1' DHCP transaction took too long (>45s), stopping it.Aug 30 22:35:20 localhost NetworkManager: <info>  eth1: canceled DHCP transaction, dhcp client pid 9060 Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled...Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Timeout) started... Aug 30 22:35:20 localhost NetworkManager: <info>  (eth1): device state change: 7 -> 9 (reason 5)Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) failed for access point (dinergy)Aug 30 22:35:20 localhost NetworkManager: <info>  Marking connection 'Auto dinergy' invalid. Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) failed.Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Timeout) complete.Aug 30 22:35:20 localhost NetworkManager: <info>  (eth1): device state change: 9 -> 3 (reason 0) Aug 30 22:35:20 localhost NetworkManager: <info>  (eth1): deactivating device (reason: 0).It finds the access point but fails at connecting..thanks for any help,/h -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Previous Message by Thread: click to view message preview

How can I get touchpad info for a bug request?

Hello, I'd like to file a bug regarding my touchpad scroll area, but I don't know where to find appropriate information on it for the bug report (model, driver, etc). My xorg.conf doesn't mention touchpad. Neither does lshw-gui or hwbrowser. Can someone help me with this? signature.asc Description: To jest =?UTF-8?Q?cz=C4=99=C5=9B=C4=87?= =?UTF-8?Q?_wiadomo=C5=9Bci?= podpisana cyfrowo -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Next Message by Thread: click to view message preview

Re: no medium xterm font (fwd)

On Sun, 30 Aug 2009 15:14:38 -0500 (CDT) Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > On Sun, 30 Aug 2009, stan wrote: > > > On Sun, 30 Aug 2009 10:43:30 -0500 (CDT) > > Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > >> No two fonts have the same height. > >> Until I understand what's going on, I really don't dare tinker. > > > > Why not? I don't understand what harm this does. Are you > > restricted for space? I installed all the available font packages > > on my system, and > > I'm afraid of breaking something. > "breaking" includes making it harder for > me to fix or for others to help me fix. > My fonts technically are not broken, > but from my point of view, they need fixing. I guess. How can you break it? You would just set it back to the original font and things are the way they were. I must be missing something in your argument. I just don't see a potential for breakage here. Before you start trying fonts, write down the original font the xterm is using. Then test away. At the end, if you don't find a better font, set it back to the original value, and you are exactly where you started. > > > ran through them trying each one until I found a combination of > > font, characteristics (bold, regular, italic) and size that I > > liked. Then I made that the default. I did this for the terminals > > under X, and gvim. As I recall, there were many fixed width fonts. > > How? > I presume I can download all the fonts I want. > How do I tell xterm to use the fonts I want? Bring up an Xterm. Click Edit->Profile Preferences. Uncheck "Use system fixed width font". Click in the Font box. Try fonts. > > For that matter, how do I tell what fonts xterm is using now? > See above. > > > > I expect that because there aren't the restriction of the console, > > the fonts for the terminal are a little more freeform. > > What restrictions? > On a console, the font block sizes come from the BIOS, and are fixed the way you specified. They can't vary. You can change which block sizes to use with presets like 0x317 or 0x318, but you have only those choices of sizes. An Xterm is a console *emulation* and so has no such restrictions. You can define your fonts however you want because you are actually running a GUI application. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines