Re: Comprehensive Disk Management GUI
On Tue, Mar 25, 2008 at 8:22 PM, Evan <[EMAIL PROTECTED]> wrote: > I have noticed a huge number of ideas on Ubuntu Brainstorm for different > disk management utilities, all of which are slightly related, but not enough > to be considered duplicates. These can all really be summed up into one > configuration GUI, and I have created a brainstorm for it at > http://brainstorm.ubuntu.com/idea/5722/ > > My proposal for the layout is something like this: > > -S.M.A.R.T. integration > I like that one. The smartctl command isn't all that easy to understandwell, except when you see "pre-fail" and go "that sounds bad" but then have no idea exactly how bad. Some sort of "badness rating" (maybe colored?) would make that easier to understand. -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com <-my blog of Ubuntu stuff apt-get moo -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Comprehensive Disk Management GUI
I have noticed a huge number of ideas on Ubuntu Brainstorm for different disk management utilities, all of which are slightly related, but not enough to be considered duplicates. These can all really be summed up into one configuration GUI, and I have created a brainstorm for it at http://brainstorm.ubuntu.com/idea/5722/ My proposal for the layout is something like this: Tab 1: Free Space -integrate Baobab (and remove it from the applications menu) -create an extensible disk cleaner with default plugins for emptying the trash, clearing the firefox cache, deleting old logfiles (using policykit), etc. Tab 2: Health -allow setting frequency of fsck, so an option something like: [x]Automatically check my disks every [35] boots. -a button for immediately checking all filesystems -S.M.A.R.T. integration Tab 3: Backup -a scheduled backup utility that can image the entire disk or zip certain folders using cron. -allow creating multiple backup 'profiles' for advanced scheduling -incremental backup would be nice, but probably difficult Tab 4: Advanced -integrate the partition editor from the installer, and enhance it to allow fstab editing as well The exact implementation of the above features is up for debate, but the concept of a unified disk management utility is far more important. As far as I know, no other operating system has a such a utility, so it would put Ubuntu clearly in the lead in this area. It could also be a candidate for the 'main feature' for 8.10 (like compiz-fusion was for 7.10). What does everybody think of putting something like this in Ubuntu? Evan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: apt pulls in -386 kernel on a -generic system, caused by dependencies (virtualbox-ose)
I can't really look now. The way I got it to install successfully was to apt-get the generic one and let its dependency on virtualbox pull in the rest of the stuff. If I try to aptitude install -s virtualbox-ose now, it says nothing to install because my manual installation of the generic one has already satisfied it. On Tue, Mar 25, 2008 at 5:58 PM, Daniel Hahler <[EMAIL PROTECTED]> wrote: > On Sunday 23 March 2008 05:36:23 Mackenzie Morgan wrote: > > > On the 21st (or 20thUTC makes Launchpad say funny things), you > marked > > this fixed, but I'm still having this problem. > > Do you still have that problem? > > I think the fixed packages may have just not been distributed by the time > you > were still experiencing it. Have you checked that you were using the fixed > version(s)? > > If it's still a problem, please file a new bug (or re-open an existing > one) > and provide the output of "dpkg -l | grep virtualbox". > The version where it has been fixed are mentioned in the bug report. > > Please note, that it has only been fixed for new installs of > virtualbox-ose: > if the 386 kernel image has been pulled in already, it will stay installed > of > course: you can just uninstall the linux-image-*-386 packages in this > case. > > > Cheers, > Daniel. > > > > > On Tue, Mar 18, 2008 at 8:42 PM, Daniel Hahler <[EMAIL PROTECTED]> > > > > wrote: > > > Hello, > > > > > > there's a major problem when installing virtualbox-ose or > > > virtualbox-ose-guest-utils in Hardy. > > > > > > These packages each depend on a virtual package > (virtualbox-ose-modules > > > and virtualbox-ose-guest-modules). > > > > > > These virtual packages get provided by packages, which themselves > depend > > > on linux-image-$ABI-$FLAVOR. > > > > > > Now, when installing virtualbox-ose-guest-utils on a system with the > > > "generic" kernel being used/installed, apt does not recognized that > > > using virtualbox-ose-guest-modules-2.6.24-12-generic would be the > better > > > match, but uses the first available "-386" instead. > > > > > > So, when users install virtualbox-ose or the guest modules, they are > > > likely installing an additional kernel image, which isn't required at > > > all and causes confusion/problems on the next boot (e.g. wireless > > > broken). > > > > > > This does not affect users with "generic" kernels on amd64, because > > > there's no 386 flavor available for them. > > > > > > More details are available on: https://launchpad.net/bugs/188579 > > > > > > Any ideas how this can get fixed? > > > > > > > > > Thanks for reading and thinking about it. > > > > > > Happy hacking, > > > Daniel. > > > > > > -- > > > http://daniel.hahler.de/ > > > > > > -- > > > Ubuntu-devel-discuss mailing list > > > Ubuntu-devel-discuss@lists.ubuntu.com > > > Modify settings or unsubscribe at: > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > > -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com <-my blog of Ubuntu stuff apt-get moo -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Xubuntu: Preparing for March 26th Meeting
On Sun, Mar 23, 2008 at 7:38 PM, Cory K. <[EMAIL PROTECTED]> wrote: > Cody A.W. Somerville wrote: > > Hello Everyone, > > > > Just a quick request to everyone planning to attend the March 26th > > Xubuntu community meeting [1]. If you could brainstorm and jot some > > ideas down prior to the meeting about: > > > > * What is the Xubuntu mission statement?; > > * What are Xubuntu's core objectives?; > > * What is the best strategy for achieving our goals?; and > > * How can we get more people involved and contributing to Xubuntu? > > > > I'm confident that our meeting will be highly successful and that > > we'll be able to come together as a community to reach an important > > level of consensus on some of these very important issues. If anyone > > has any comments, questions, or concerns about the meeting then please > > feel free to contact me or another member of the Xubuntu team [2]. > > > > Thank you, > > > > Cody A.W. Somerville > > Xubuntu Team Lead > > I'll be sure to be there. ;) > > Cody, as the current defacto lead (I hope the meeting cements that role) > I think that points 1&2 should be defined by you and your core team. I'm > not saying you shouldn't look for input from a wider community, just > ultimately it's your show and you have to go with your gut. Everyone > will have an opinion as to what Xubuntu *should* be. :P I completely agree with you. After getting a feel from the community, myself and other key contributors will make the final decision. I believe that once a direction for Xubuntu has been set, we'll be able to develop a concrete roadmap and avoid certain conflicts that have arisen in the past due to the current ambiguity. Points 3&4 I think can be much more up for debate and planning. > > I would also like to see a blog/planet/forums posting about this meeting > because I feel this can be a significant part of Xubuntu development. So > getting a wide word out I would think is best. Excellent idea. I wish I had done this sooner. -Cory \m/ > > PS: Now that I look under you name, are you "officially" the lead? A > clear transfer of power been made somewhere? This is currently in progress and will be officially announced after the meeting. > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss Thanks, Cody :) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: apt pulls in -386 kernel on a -generic system, caused by dependencies (virtualbox-ose)
On Sunday 23 March 2008 05:36:23 Mackenzie Morgan wrote: > On the 21st (or 20thUTC makes Launchpad say funny things), you marked > this fixed, but I'm still having this problem. Do you still have that problem? I think the fixed packages may have just not been distributed by the time you were still experiencing it. Have you checked that you were using the fixed version(s)? If it's still a problem, please file a new bug (or re-open an existing one) and provide the output of "dpkg -l | grep virtualbox". The version where it has been fixed are mentioned in the bug report. Please note, that it has only been fixed for new installs of virtualbox-ose: if the 386 kernel image has been pulled in already, it will stay installed of course: you can just uninstall the linux-image-*-386 packages in this case. Cheers, Daniel. > > On Tue, Mar 18, 2008 at 8:42 PM, Daniel Hahler <[EMAIL PROTECTED]> > > wrote: > > Hello, > > > > there's a major problem when installing virtualbox-ose or > > virtualbox-ose-guest-utils in Hardy. > > > > These packages each depend on a virtual package (virtualbox-ose-modules > > and virtualbox-ose-guest-modules). > > > > These virtual packages get provided by packages, which themselves depend > > on linux-image-$ABI-$FLAVOR. > > > > Now, when installing virtualbox-ose-guest-utils on a system with the > > "generic" kernel being used/installed, apt does not recognized that > > using virtualbox-ose-guest-modules-2.6.24-12-generic would be the better > > match, but uses the first available "-386" instead. > > > > So, when users install virtualbox-ose or the guest modules, they are > > likely installing an additional kernel image, which isn't required at > > all and causes confusion/problems on the next boot (e.g. wireless > > broken). > > > > This does not affect users with "generic" kernels on amd64, because > > there's no 386 flavor available for them. > > > > More details are available on: https://launchpad.net/bugs/188579 > > > > Any ideas how this can get fixed? > > > > > > Thanks for reading and thinking about it. > > > > Happy hacking, > > Daniel. > > > > -- > > http://daniel.hahler.de/ > > > > -- > > Ubuntu-devel-discuss mailing list > > Ubuntu-devel-discuss@lists.ubuntu.com > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [Policykit] No possibilty to unlock the save option in Gedit while
"(``-_-´´) -- Fernando" a écrit : > On Monday 24 March 2008 15:01:07 Milan Bouchet-Valat wrote: > >> Here we can just agree, but nobody codes directly into gedit. >> >> Cheers >> > > But isn't this a problem with PolicyKit and not Gedit? > AFAIK PolicyKit already allows to do this, gedit just needs to use it to get the adequate rights. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: ddcprobe giving strange values
Bastian Wissler schrieb: Hello, I discovered that ddcprobe from the most recent xresprobe-package (xresprobe (0.4.24ubuntu8)) is not giving proper results. 1440x1440 pixels is not supported on our TFT-Monitor - yet ddcprobe prints out this kind of resolution. As attachment I added two files (ddcprobe and hwinfo.suse103) with a computer with 2 displays - ddcprobe just gets the first, but not the second. With hwinfo from SUSE, there is some info about all of them. Yet ddcprobe is a better solution for most of the monitors here. On my Laptop with ATI X600 graphics and 15.4' TFT display `cat ddcprobe.out` with "edidfail" is the output. How can I get behind this problems? Is there some command-line option or a patch available? Thanks in advance, Bastian. There is some more misbehavior regarding ddcprobe: On an ASUS Pundit with onboard NVIDIA graphics we get no output at all: "edidfail", but with hwinfo we get all information - but we would like to use ddcprobe, because it is a lot faster. see the Attachment for outputs of ddcprobe, lspci and hwinfo. Should I provide more information about hardware or software? All these tests come from a pre-boot busybox environment, but on my laptop I have a complete linux system running when ddcprobe fails. Thanks, Bastian. Test using ddcprobe ... on a ASUS Pundit with onboard ATI graphics vbe: VESA 3.0 detected. oem: NVIDIA vendor: NVIDIA Corporation product: Crush50 Board - c51pv0 Chip Rev memory: 32768kb mode: 640x400x256 mode: 640x480x256 mode: 800x600x16 mode: 800x600x256 mode: 1024x768x16 mode: 1024x768x256 mode: 1280x1024x16 mode: 1280x1024x256 mode: 320x200x64k mode: 320x200x16m mode: 640x480x64k mode: 640x480x16m mode: 800x600x64k mode: 800x600x16m mode: 1024x768x64k mode: 1024x768x16m mode: 1280x1024x64k mode: 1280x1024x16m edid: edidfail The systems configuration 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev c0) Results (correct) produced by OpenSuSE10.3 hwsetup --monitor 36: None 00.1: 10002 LCD Monitor [Created at monitor.94] Unique ID: jyhG.FrS2vZKL1SD Hardware Class: monitor Model: "DELL 1907FP" Vendor: DEL "DELL" Device: eisa 0x4015 "DELL 1907FP" Serial ID: "CC28965DAEXY" Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Size: 376x301 mm Detailed Timings #0: Resolution: 1280x1024 Horizontal: 1280 1328 1440 1688 (+48 +160 +408) +hsync Vertical: 1024 1025 1028 1066 (+1 +4 +42) +vsync Frequencies: 108.00 MHz, 63.98 kHz, 60.02 Hz Driver Info #0: Max. Resolution: 1280x1024 Vert. Sync Range: 56-76 Hz Hor. Sync Range: 30-81 kHz Bandwidth: 108 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
ddcprobe giving strange values
Hello, I discovered that ddcprobe from the most recent xresprobe-package (xresprobe (0.4.24ubuntu8)) is not giving proper results. 1440x1440 pixels is not supported on our TFT-Monitor - yet ddcprobe prints out this kind of resolution. As attachment I added two files (ddcprobe and hwinfo.suse103) with a computer with 2 displays - ddcprobe just gets the first, but not the second. With hwinfo from SUSE, there is some info about all of them. Yet ddcprobe is a better solution for most of the monitors here. On my Laptop with ATI X600 graphics and 15.4' TFT display `cat ddcprobe.out` with "edidfail" is the output. How can I get behind this problems? Is there some command-line option or a patch available? Thanks in advance, Bastian. vbe: VESA 2.0 detected. oem: ATI MOBILITY RADEON X600 memory: 65536kb mode: 320x200x32k mode: 320x200x64k mode: 320x200x16m mode: 1600x1200x256 mode: 640x400x256 mode: 640x480x256 mode: 640x480x32k mode: 640x480x64k mode: 640x480x16m mode: 1600x1200x32k mode: 800x600x256 mode: 800x600x32k mode: 800x600x64k mode: 800x600x16m mode: 1600x1200x64k mode: 1024x768x256 mode: 1024x768x32k mode: 1024x768x64k mode: 1024x768x16m mode: 1280x1024x256 mode: 1280x1024x32k mode: 1280x1024x64k mode: 1280x1024x16m edid: ? edidfail 19: None 00.0: 1 Monitor [Created at monitor.94] Unique ID: rdCR.mlHAFfZX755 Hardware Class: monitor Model: "LG ELECTRONICS L225W" Vendor: GSM "LG ELECTRONICS" Device: eisa 0x5662 "L225W" Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Size: 474x296 mm Detailed Timings #0: Resolution: 1680x1050 Horizontal: 1680 1784 1960 2240 (+104 +280 +560) +hsync Vertical: 1050 1053 1059 1089 (+3 +9 +39) -vsync Frequencies: 146.25 MHz, 65.29 kHz, 59.95 Hz Detailed Timings #1: Resolution: 1680x1050 Horizontal: 1680 1728 1760 1840 (+48 +80 +160) -hsync Vertical: 1050 1053 1059 1080 (+3 +9 +30) +vsync Frequencies: 119.00 MHz, 64.67 kHz, 59.88 Hz Driver Info #0: Max. Resolution: 1680x1050 Vert. Sync Range: 56-75 Hz Hor. Sync Range: 28-83 kHz Bandwidth: 146 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown 20: None 00.1: 1 Monitor [Created at monitor.94] Unique ID: jyhG.VK0lVeR3fP3 Hardware Class: monitor Model: "IIYAMA VISION MASTER PRO 410" Vendor: IVM "IIYAMA" Device: eisa 0x1740 "VISION MASTER PRO 410" Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Driver Info #0: Vert. Sync Range: 50-160 Hz Hor. Sync Range: 27-96 kHz Config Status: cfg=new, avail=yes, need=no, active=unknown vbe: VESA 3.0 detected. oem: Intel(r) 82945G Chipset Family Graphics Chip Accelerated VGA BIOS vendor: Intel Corporation product: Intel(r) 82945G Chipset Family Graphics Controller Hardware Version 0.0 memory: 7872kb mode: 1280x1024x256 mode: 1280x1024x64k mode: 1280x1024x16m mode: 1024x768x256 mode: 1024x768x64k mode: 1024x768x16m mode: 640x480x16m mode: 800x600x64k mode: 800x600x16m mode: 640x480x256 mode: 800x600x256 mode: 640x480x64k edid: edid: 1 3 id: 5662 eisa: GSM5662 serial: 0001ce83 manufacture: 9 2007 input: separate sync, sync on green, analog signal. screensize: 47 30 gamma: 2.20 dpms: RGB, active off, suspend, standby timing: [EMAIL PROTECTED] Hz (VGA 640x400, IBM) timing: [EMAIL PROTECTED] Hz (XGA2) timing: [EMAIL PROTECTED] Hz (VGA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz Interlaced (8514A) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] dtiming: [EMAIL PROTECTED] dtiming: [EMAIL PROTECTED] monitorrange: 28-83, 56-75 monitorname: L225W -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
ddcprobe giving strange values
Hello, I discovered that ddcprobe from the most recent xresprobe-package (xresprobe (0.4.24ubuntu8)) is not giving proper results. 1440x1440 pixels is not supported on our TFT-Monitor - yet ddcprobe prints out this kind of resolution. As attachment I added two files (ddcprobe and hwinfo.suse103) with a computer with 2 displays - ddcprobe just gets the first, but not the second. With hwinfo from SUSE, there is some info about all of them. Yet ddcprobe is a better solution for most of the monitors here. On my Laptop with ATI X600 graphics and 15.4' TFT display `cat ddcprobe.out` with "edidfail" is the output. How can I get behind this problems? Is there some command-line option or a patch available? Thanks in advance, Bastian. vbe: VESA 2.0 detected. oem: ATI MOBILITY RADEON X600 memory: 65536kb mode: 320x200x32k mode: 320x200x64k mode: 320x200x16m mode: 1600x1200x256 mode: 640x400x256 mode: 640x480x256 mode: 640x480x32k mode: 640x480x64k mode: 640x480x16m mode: 1600x1200x32k mode: 800x600x256 mode: 800x600x32k mode: 800x600x64k mode: 800x600x16m mode: 1600x1200x64k mode: 1024x768x256 mode: 1024x768x32k mode: 1024x768x64k mode: 1024x768x16m mode: 1280x1024x256 mode: 1280x1024x32k mode: 1280x1024x64k mode: 1280x1024x16m edid: ? edidfail 19: None 00.0: 1 Monitor [Created at monitor.94] Unique ID: rdCR.mlHAFfZX755 Hardware Class: monitor Model: "LG ELECTRONICS L225W" Vendor: GSM "LG ELECTRONICS" Device: eisa 0x5662 "L225W" Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Size: 474x296 mm Detailed Timings #0: Resolution: 1680x1050 Horizontal: 1680 1784 1960 2240 (+104 +280 +560) +hsync Vertical: 1050 1053 1059 1089 (+3 +9 +39) -vsync Frequencies: 146.25 MHz, 65.29 kHz, 59.95 Hz Detailed Timings #1: Resolution: 1680x1050 Horizontal: 1680 1728 1760 1840 (+48 +80 +160) -hsync Vertical: 1050 1053 1059 1080 (+3 +9 +30) +vsync Frequencies: 119.00 MHz, 64.67 kHz, 59.88 Hz Driver Info #0: Max. Resolution: 1680x1050 Vert. Sync Range: 56-75 Hz Hor. Sync Range: 28-83 kHz Bandwidth: 146 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown 20: None 00.1: 1 Monitor [Created at monitor.94] Unique ID: jyhG.VK0lVeR3fP3 Hardware Class: monitor Model: "IIYAMA VISION MASTER PRO 410" Vendor: IVM "IIYAMA" Device: eisa 0x1740 "VISION MASTER PRO 410" Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Resolution: [EMAIL PROTECTED] Driver Info #0: Vert. Sync Range: 50-160 Hz Hor. Sync Range: 27-96 kHz Config Status: cfg=new, avail=yes, need=no, active=unknown vbe: VESA 3.0 detected. oem: Intel(r) 82945G Chipset Family Graphics Chip Accelerated VGA BIOS vendor: Intel Corporation product: Intel(r) 82945G Chipset Family Graphics Controller Hardware Version 0.0 memory: 7872kb mode: 1280x1024x256 mode: 1280x1024x64k mode: 1280x1024x16m mode: 1024x768x256 mode: 1024x768x64k mode: 1024x768x16m mode: 640x480x16m mode: 800x600x64k mode: 800x600x16m mode: 640x480x256 mode: 800x600x256 mode: 640x480x64k edid: edid: 1 3 id: 5662 eisa: GSM5662 serial: 0001ce83 manufacture: 9 2007 input: separate sync, sync on green, analog signal. screensize: 47 30 gamma: 2.20 dpms: RGB, active off, suspend, standby timing: [EMAIL PROTECTED] Hz (VGA 640x400, IBM) timing: [EMAIL PROTECTED] Hz (XGA2) timing: [EMAIL PROTECTED] Hz (VGA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz Interlaced (8514A) timing: [EMAIL PROTECTED] Hz (VESA) timing: [EMAIL PROTECTED] Hz (VESA) ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] ctiming: [EMAIL PROTECTED] dtiming: [EMAIL PROTECTED] dtiming: [EMAIL PROTECTED] monitorrange: 28-83, 56-75 monitorname: L225W -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
RE: Graphical Installer & bootloader
De: Sarah Hobbs Enviado el: lun 24/03/2008 14:54 Para: Ming CC: ubuntu-devel-discuss@lists.ubuntu.com Asunto: Re: Graphical Installer & bootloader >The bootloader (grub), however, is still text, and I suspect will be so, until grub2 comes out. This for me is fundamental. I would like to see a Ncurses based Grub installer and configurator (to edit menu.lst by the root). Using this with a Ncurses GNU parted would be very useful as a rescue disk / installator / partitor / bootloader , for floppy disk, hard disk or USB keydrive ;-) Regards. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
RE: Graphical Installer & bootloader
De: Ming Enviado el: lun 24/03/2008 7:54 Para: ubuntu-devel-discuss@lists.ubuntu.com Asunto: Graphical Installer & bootloader >Perhaps the ubuntu developers might want to consider using a graphical installer & bootloader in the next release (hardy). I'm currently using ubuntu studio gutsy, and I think the gnome desktop is great ;) my notebook's LCD is well recognized at 1280x800. So I think it's a bit ironic that it still use text-based installer & boot loader. And: * a Ncurses GNU Parted, that also can be used in Windows. * Rescued disk, with SuperGrub. ;-) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Got Hardy? With Sound?
Using Intel here: *-multimedia description: Multimedia audio controller product: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller vendor: Intel Corporation physical id: 1f.5 bus info: [EMAIL PROTECTED]:00:1f.5 version: 03 width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: driver=Intel ICH latency=0 module=snd_intel8x0 -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [Policykit] No possibilty to unlock the save option in Gedit while
On Monday 24 March 2008 15:01:07 Milan Bouchet-Valat wrote: > Here we can just agree, but nobody codes directly into gedit. > > Cheers But isn't this a problem with PolicyKit and not Gedit? -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Got Hardy? With Sound?
On Saturday 22 March 2008 03:42:01 Scott (angrykeyboarder) wrote: > Skype doesn't work with PulseAudio, period. That's been documented. But are > you running Hardy and otherwise getting sound? Not sure now, if I had it working with ALSA or PA, but its working. > I've been running Hardy for about 3 weeks now and I've *never* had sound of > any kind. I have my sound system working for weeks now, on hardy. The last three maybe 4 weeks, no prob. And even before that it usually just required a reboot or init. > > -- > Scott -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Flaw of Auto-Configuration and VESA driver cause failure at hardy installation
Hi all,
When I install Hardy desktop edtion (8.04 beta1), I failed and entered
the busybox interface instead of the graphic user guide.
I check the log file and it said
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
The root cause I think is same as
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vesa/+bug/1
74434/
I think it's a common issue. This bug frustrate user to install Ubuntu.
Now I can only install Ubuntu via alternate CD and update the driver by
myself. Then I can enter X.
The bug can be duplicated when the graphic card is only supported by
VESA driver and the monitor's hsync and vrefresh rate is just a value
that probed by X's auto configuration.
And the here is a patch from FC9 can fix the issue, can anybody help to
test it and add it to the current distribution before RC? Thanks
Patch contents:
--- xf86-video-vesa-1.3.0/src/vesa.c.jx 2007-01-30 10:31:32.0
-0500
+++ xf86-video-vesa-1.3.0/src/vesa.c2007-01-30 10:56:15.0
-0500
@@ -638,8 +638,40 @@
xf86UnloadSubModule(pDDCModule);
}
-if ((pScrn->monitor->DDC = pVesa->monitor) != NULL)
- xf86SetDDCproperties(pScrn, pVesa->monitor);
+/* UNCLEAN */
+do {
+ Bool had_cfg_ranges, have_ddc_ranges;
+
+ had_cfg_ranges = (pScrn->monitor->nHsync ||
pScrn->monitor->nVrefresh);
+ if ((pScrn->monitor->DDC = pVesa->monitor) != NULL)
+ xf86SetDDCproperties(pScrn, pVesa->monitor);
+ have_ddc_ranges = (pScrn->monitor->nHsync ||
pScrn->monitor->nVrefresh);
+
+ if (have_ddc_ranges && !had_cfg_ranges) {
+ int i;
+ for (i = 0; i < DET_TIMINGS; i++) {
+ if (pVesa->monitor->det_mon[i].type == DS_RANGES)
+ break;
+ }
+ if (i < DET_TIMINGS)
+ break;
+
+ /*
+* DDC added ranges, but they're inferred from the modes,
not
+* copied from a range section. So in the worst case, where
it's
+* not a range but a single frequency, stretch things out to
be
+* a range. Panels with only one mode listed in DDC will
+* otherwise probably not match any VESA modes. Hooray for
+* conformance.
+*/
+ if (pScrn->monitor->hsync[0].lo ==
pScrn->monitor->hsync[0].hi
+&& pScrn->monitor->hsync[0].lo > 31.5)
+ pScrn->monitor->hsync[0].lo = 31.5;
+ if (pScrn->monitor->vrefresh[0].lo ==
pScrn->monitor->vrefresh[0].hi
+&& pScrn->monitor->vrefresh[0].lo > 50.0)
+ pScrn->monitor->vrefresh[0].lo = 50;
+ }
+} while (0);
xf86DrvMsgVerb(pScrn->scrnIndex, X_INFO, DEBUG_VERB,
"Searching for matching VESA mode(s):\n");
Regards,
Wolke
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
